Search Issue Tracker
By Design
Votes
0
Found in
4.3.0b2
Issue ID
564385
Regression
No
When exported, an animation seems to be ignoring extra data for a bone in the hierarchy
Steps to reproduce :
- import the project attached
- open the scene and press play
- find Elum_Target in the Hierarchy and notice axis of the point appears between the feet
- open the .max file found in the project folder and notice the up axis of the point has a different possition
*Note :
Screenshot attached in the user's reply.
Explanation :
This is normal because you are using a humanoid rig which retarget the motion and then compute a new root position from this data, since your Elum_Target transform is parented to the root, the final position is not the same.
IF you want to same exact motion, change your rig type to generic.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The cursor moves into wrong place when renaming folder/asset
- Assertion error "(dx - width < padding) || (dy - height < padding)" when using Pack Preview
- [Memory Profiler] The EntryType.NativeAllocationSites_MemoryLabelIndex of snapshots only reports -1 or 0 instead of the MemLabel used for allocations made from any call site.
- [Vulkan] Artifacts appear in the Player when using Screen Space shadows with orthographic camera
- Errors OnGUIDepth changed & GUIUtility:ProcessEvent when opening Textures with Third Party App
Add comment