Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.3.0a3
Issue ID
1193908
Regression
Yes
90' offset on Generic animation import
Motion files have a 90' offset on Generic animation import.
Attached project contains a model file (DefaultMale) and multiple motion files (Idle, Nav, etc.). All motion files use the Stance Generic avatar. The Stance file is the only file with a static stance pose (all other motion files have animation) AND is the only motion file to not have the issue. All other motion files have the issue, a 90' offset (facing X+, instead of facing Z+).
This is a regression. This does not happen in 2019.3.0a2 & before.
repro:
- open project
- select Stance file
- look at the Inspector > Import Settings > Animation tab > animation preview (bottom of the Inspector)
- drop DefaultMale into animation preview window...
character should be facing Z+ as expected.
- select Idle file...
bug: character is facing X+
expected: character is facing Z+
note: all other motion files have the same issue, only Stance is correct.
All files are facing Z+ in 2019.3.0a2 & before.
repro in...
Version 2019.3.0a3 (91c086393aab)
Sun, 12 May 2019 04:18:43 GMT
Branch: trunk
not repro in...
Version 2019.3.0a2 (fa7740529556)
Wed, 01 May 2019 00:24:12 GMT
Branch: trunk
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
- [Mono] Crash on SystemNative_ReadDirR() when building for IOS/Android on a macOS machine
Add comment