Search Issue Tracker
Fixed in 2017.2.0f3
Fixed in 5.6.X, 2017.1.X
Votes
131
Found in
5.6.0f3
Issue ID
899009
Regression
Yes
"In order to call GetTransformInfoExpectUpToDate..." error message appears while toggling Skinned Mesh Renderer component
How to reproduce:
1. Create a new project
2. Change "Directional Light" type from Directional to Spot, make sure that it's Shadow Type settings would be set to Soft or Hard Shadows
3. Add a 3D Object as a child of "Directional Light" GameObject
4. Add a Skinned Mesh Renderer component to a 3D Object
5. Create an empty GameObject as a child of 3D Object
6. Go back to 3D Object Inspector settings and set an empty GameObject as a Root Bone
7. Toggle on and off 3D Objects Skinned Mesh Renderer component repeatedly
Expected result: No error is appearing
Actual result: "In order to call GetTransformInfoExpectUpToDate, RendererUpdateManager.UpdateAll must be called first." error message appears in the Console
Note: The important parts of this bug reproduction are Spotlight, Realtime/Mixed Shadows(hard/soft), "Skinned Mesh Renderer" with "Root Bone" assigned
Regression introduced in - 5.6.0b8
Reproducible with - 2017.1.0b1, 5.6.0f3, 5.6.0b8
Not reproducible with - 5.6.0b7, 5.5.3f1, 5.4.5f1
--------------
Fixed in 2017.2.0a4. Backports to 5.6 and 2017.1 were made.
Comments (65)
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
- "GPU Time Threshold" in VFX Graph Heatmap Parameters can be set to a negative value
- List of supported Platforms for 3D Templates in Unity Hub is outdated
- Mesh filter animation tint is not added if keyframe recording is not enabled
- Light.shadowMatrixOverride is ignored when using GPU Resident Drawer
- Setting the the "PreWarm Delta Time" to the smallest value always sets the "PreWarm Step Count" to the different random values
gringan
May 24, 2017 18:51
I have same issue but i also have Unity crash if i hit play.
https://forum.unity3d.com/threads/unity-5-6-0f3-error-message-at-load-of-my-project.468191/
https://www.youtube.com/watch?v=Bt1vbyjZdy4
Please i need help. I tryed to update with 5.6.1f1 and its the same.
Thanks for helping me. I work on this project as solo developer since one year. I really would like to fix this.
FaberVi
May 24, 2017 14:15
Same problem. 5.6.1p1..
planeta_vr
May 23, 2017 19:18
Happen for me after adding spotlight as well. In 5.6.0f3
rawrrrz
May 22, 2017 07:03
First noticed it in 5.6.1f1 after changing a light from Directional to Spot. Still happening in 2017.1.0b6 as well. Changed from Spot back to Directional, and the error disappeared.
Also, there are no rigidbodies in my project, so while that may have been the issue for some, it's definitely an issue with Spotlights for me.
mushdevstudio
May 21, 2017 23:08
Hazneliel - you are wrong. I turn rigid body interpolation to none and the error goes away. I do not have any spotlights.
I am stuck on version 5.5 because 5.6 breaks rigid body interpolation - so weird to break something so fundamental to 3D games programming. The fix is apparently 2017.1 but I have tried beta and it distorts and twists some of my animated models so looks like 5.5.3p3 is the last good build. This unfortunately means that I can not build Android as Vulkan and also that the new IAP won't work because they require API24 for targetSDK and 5.5.3p3 does not support API 24 - wow after 3 years of work I am so frustrated by this!
Marcos-Elias
May 19, 2017 04:56
Is this bad for production? My project seems to be working even with this message on console, but I don't know if this will cause any problem to the players (is it logged also on player, or cause any performance harm?)
monremobile
May 18, 2017 23:01
It happens with all rigidbodies with "interpolate" enabled
(5.6.1f1)
Very annoying bug.
Skyway-Interactive
May 18, 2017 02:19
Had this appear for the first time in 5.6.1f1 I had not seen this in 5.6.0f3. Turning a spot light's shadows from none to soft I could recreate the error every time.
Ruhan-
May 16, 2017 13:08
Still occurring in 5.6.1f1
I know it's not not a fix on the change log but there are other SkinnedMeshRenderer related fixes in it so thought I'd give it a shot.
We can only hope it gets fixed on a patch release of 5.6.1 for now :\ but otherwise 5.6.2f1 will definitely take a while...
ferruccio
May 15, 2017 15:50
Getting the same error. I do not use a spotlight but I use interpolation on some rigidbodies. Deactivating interpolation solves the issue, but I really need interpolation.