Search Issue Tracker

Fixed in 2017.2.0f3

Fixed in 5.6.X, 2017.1.X



Found in


Issue ID




"In order to call GetTransformInfoExpectUpToDate..." error message appears while toggling Skinned Mesh Renderer component

Graphics - General


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)

  1. DoenitZ

    May 27, 2017 23:11

    Hi to everyone, this problem is related to RigidBody interpolation that is not set to None. I have checked this, and it's not happening when the RigidBody interpolate is set to None. If you need to fix this, I have created this small script: that will change all of your assets RigidBody interpolation to None. If you don't need interpolation, or you can live without it, this will make the message dissapears until unity fix the problem. I know it's not the best solution, but it can save some time if you can't wait for unity's next patch release. Bear in mind that you can't undo this, so use it carefully

  2. Edy

    May 26, 2017 16:10

    I'm suffering this as well with Unity 5.6.1p1. No spotlights nor skinned meshes here, just rigidbodies. How's possible that so obvious issue has passed through your QA tests?

  3. gringan

    May 24, 2017 18:51

    I have same issue but i also have Unity crash if i hit play.

    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.

  4. FaberVi

    May 24, 2017 14:15

    Same problem. 5.6.1p1..

  5. planeta_vr

    May 23, 2017 19:18

    Happen for me after adding spotlight as well. In 5.6.0f3

  6. 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.

  7. 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!

  8. 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?)

  9. monremobile

    May 18, 2017 23:01

    It happens with all rigidbodies with "interpolate" enabled

    Very annoying bug.

  10. 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.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.