Search Issue Tracker
Fixed in 4.3.2
Votes
6
Found in
4.3.0f4
Issue ID
575612
Regression
No
Transform.rotation of game object is no longer valid, due to a bad input value
The "transform.rotation of 'gameObject' is no longer valid, due to a bad input value." error is shown in the console while playing a scene in the editor and having 5 or more game objects connected in a tree manner in objects' hierarchy.
Reproduced with:
Unity Version 4.3.0f4 (e01000627d60)
Comments (3)
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
- UI Toolkit meshes are fully rendered and rasterized when opacity is 0
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
pragmascript
Aug 11, 2014 00:24
same issue in 4.5.2. does NOT seem to be fixed.
bruntos
Jun 02, 2014 17:03
Thanks most helpful!!
Oliver Eberlei
Nov 23, 2013 12:42
I've noticed that this happens when you put a rigged gameObject with an Animator component into the hierarchy of another rigged character and the child has "Apply Root Motion" enabled in it's Animator component. Disabling "Apply Root Motion" on the child object fixes the issue for me.
Hope this helps.