Search Issue Tracker
By Design
Votes
0
Found in
5.4.0f2
Issue ID
817978
Regression
No
Normalized time in AnimatorStateInfo is late to update it's value after state has changed
Steps to reproduce:
1. Open users attached project.
2. Observe "TestScript" script.
3. Open "Animator" window.
4. Enter play mode.
5. Observe animators misty state.
6. Check console for "State Started" line.
--- Even though new state has started (check console) normalized time is late to update it's value. (Check attached photo)
Reproduced with: 5.4.0f2, 5.3.6f1, 5.3.5f1, 5.2.0f3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Add comment