Search Issue Tracker
Fixed in 5.1.1
Votes
0
Found in
Issue ID
649221
Regression
No
Animator: Setting speed for a state to a max value produces error
Animator: Setting speed for a state to a max value produces errors in console
1. Set speed for a state to a max allowed number (3.402823e+38)
2. Run the scene
---> Errors in console
"transform.position assign attempt for 'Horse' is not valid. Input position is { NaN, NaN, NaN }."
Reproducible in Unity 5.0 b14
OS: Windows 8.1 x64
Comments (1)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Unapplied changes on the "MainPanel" GameObject in the "BlobShadow" of URP Samples
- [Vulkan][Android] The Player crashes on devices with SP9863A chipset
- "Output properties of this Camera do not match the output properties" warning is shown In the "SplitScreen" scene of URP Samples
- "Gun" Prefab used in "MixedFOV" scene of URP Samples has unapplied changes
- "FirstPersonController uses the legacy input system" message is logged when entering the Play Mode in "MixedFOV" scene of URP Samples
dboehle
Jul 22, 2015 07:14
This also appears to happen when setting a speed to 0. Same OS, Unity 5.1.2f1.
The Editor log shows this as the only line in the stack trace:
(Filename: C:/buildslave/unity/build/Runtime/Graphics/Transform.cpp Line: 857)