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
- [URP][Lighting] The skybox doesn't render after changing the settings of the Material when using the URP Render Pipeline
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
Add comment