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

hip_to_root raised "none type" object has no attribute 'action' when processing error #95

Open
AutomaticFX opened this issue Jan 4, 2023 · 6 comments

Comments

@AutomaticFX
Copy link

Hello - happy new year all.
new to using this blender/mixamo add-on feature. am using a character from BigMediumSmall Post Apocalypse bundle. the character, named D2, was already set up as FBX in a folder for import into Mixamo, and it uploaded to mixamo no problem. we downloaded a number of animations without issue. they all work fine in UE5. we wanted to add root bone so followed process per instructions, however, getting the above mentioned error:
hip_to_root raised "none type" object has no attribute 'action' when processing error D2_Mixamo.fbx
would appreciate any further insight/ suggestions into fixing this issue.
Thank you!

@EestC
Copy link

EestC commented Mar 1, 2023

Same here please do you get it fixed

@casote
Copy link

casote commented Jul 31, 2023

Same here.

@rishflab
Copy link

I have the same issue

@enziop
Copy link
Owner

enziop commented Feb 15, 2024

Please supply direct links, to the animations that produce problems. I can not even find the Packs you mentioned. So i can not reproduce the Issue.

@rishflab
Copy link

rishflab commented Feb 15, 2024

https://www.mixamo.com/#/?page=1&query=zombie+walk&type=Motion%2CMotionPack If I remember correctly, this was the anim I was using. I think it occurs for any root motion anim.

I was using a skeleton generated using the mixamo autorigger on these models https://maxparata.itch.io/voxel-zombies

@Auxigator
Copy link

Ran into this issue when batch converting. Problem occurs when the rigged character (without any animation) is included in the input folder. Removing it fixed the issue for me!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants