Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Imported 3D model with amature (exported glTF), objects that has been parented into the amature to be misplaced (wrong position) #2330

Open
DrageonDB opened this issue Aug 29, 2024 · 4 comments
Labels
bug Something isn't working importer This involves or affects the import process

Comments

@DrageonDB
Copy link

Describe the bug
I tried to import an exported glTF (character), resulting many objects that has been parented into the amature to be misplaced.

To Reproduce
Steps to reproduce the behavior:

  1. Import this model (link below) into Blender
  2. Then compare this with glTF viewer
  3. Hide amature
  4. Look the character

Expected behavior
It should be show like this: (glTF viewer)
Screenshot 2024-08-29 101039

Screenshots
This is an observed result: (Blender)
Screenshot 2024-08-29 100908

.blend file/ .gltf (mandatory)
https://www.mediafire.com/file/yhthl5wlyo4ovcv/Wendiir_Neorgreth_%2528Free_download_-_.blend_and_texture_files_included%2529.zip/file

Version

  • OS: Windows 11 23H2
  • Blender Version: 4.2.1 LTS
@DrageonDB
Copy link
Author

DrageonDB commented Aug 29, 2024

Admin edit : I deleted the comment with a malicious file

I don't recommend to download this bug fix. This file may be malicious and could potentially harm your computer. This file is VERY questionable.

@julienduroure
Copy link
Collaborator

First analysis :
Seems we have an issue with multiple armatures management at import.
Meshes that are misplaced are all parented to a bone that are part of a rig itself parented to a bone of an another rig
Main rig : Rig
Additional rigs: Eyes, TongueBone

@julienduroure julienduroure added bug Something isn't working importer This involves or affects the import process labels Aug 29, 2024
@DrageonDB
Copy link
Author

DrageonDB commented Aug 29, 2024

And then not only sub-rigs that affected, but the objects that parented into this main amature are affected too. I saw tasset in this model got moved a little bit to back, spiked poleyn, and even greaves and vambraces.

@julienduroure
Copy link
Collaborator

Note the the rig (in the .blend) has some dependency cycles, so we can't guarantee that everything is exported correctly


Dependency cycle detected:
  OBRig/tailSpine/BONE_CONSTRAINTS() depends on
  OBRig/tailSpine.001/BONE_READY() via 'Damped Track'
  OBRig/tailSpine.001/BONE_POSE_PARENT() via 'Pose -> Ready'
  OBRig/tailSpine/BONE_READY() via 'Parent Bone -> Child Bone'
  OBRig/tailSpine/BONE_CONSTRAINTS() via 'Constraints -> Ready'

I still have to check how deep this deps cycle impact the export

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working importer This involves or affects the import process
Projects
None yet
Development

No branches or pull requests

3 participants
@julienduroure @DrageonDB and others