Search Issue Tracker
Fixed in 5.1.1
Votes
8
Found in
5.1.0f3
Issue ID
703251
Regression
Yes
"Invalid optimized game object" errors are spammed when an optimized, animated object is set as a child of any other object
Steps to reproduce:
1. Open the attached project
2. Select 'test' model in the project window and open 'Rig' tab in the model importer
3. Enable 'Optimize Game Objects'
4. Add any bone to 'Extra Transforms to Expose' list
5. Setup animation clip in the 'Animations' tab (or you can use the one that is already created)
6. Create 'Animator Controller' asset and add the animation clip to it
7. Create any game object
8. Drag the 'test' model onto that GO to create it as a child of the newly created object
9. Attach created animator controller to the 'test' object 'Animator' component
10. Play the scene
11. Notice the errors are spammed in the console
Note: If you make the 'test' object invisible (that is, hide the game view, open the scene view and drag the camera so that you can not see the object) the errors stop until you focus on the game object in the scene or open the game view again. This also does not happen if the 'test' game object is not set to be a child of any other object.
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
- [Android] Error "Blitter is already initialized" is present when Adaptive Probe Volumes are used with OpenGLES3
- VFX Graph effect instance stops rendering when a second instance of the same effect starts 2 frames later
- Operations on the Color32 array are not reflected in WebGL Player when HDR is off
- Rigidbody moves away from the original GameObject when Center of Mass is set in every frame
- WebGL Player does not proceed beyond logo screen when "Target WebAssembly 2023" is enabled
gekidoslair
Jul 17, 2015 05:18
definitely still getting this error - it's horrible, makes trying to test scenes unworkable because the console eventually blows up and kills unity.
RetroTK2
Jul 01, 2015 11:54
Still getting this bug, but only on one of the characters.
Unparenting the character stops the error log. The bug itself doesn't seem to cause any issues, but the fact that it logs as an error means that I can't run my integration tests.
As a hotfix would it be possible to change the Error Log to a Warning Log?
Thanks Guys.
RetroTK2
Jul 01, 2015 11:54
Still getting this bug, but only on one of the characters.
Unparenting the character stops the error log. The bug itself doesn't seem to cause any issues, but the fact that it logs as an error means that I can't run my intergration tests.
As a hotfix would it be possible to change the Error Log to a Warning Log?
Thanks Guys.