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 (66)

  1. 3c12bebd350c71aa61283a99c0ced2e9?d=mm


    Jun 27, 2017 11:58

    "><img >

  2. 49ce3d9dc999844556df4ea4e40a5d04?d=mm


    Jun 22, 2017 08:43

    You're not nuts @MUSHDEVSTUDIO ;o)
    Confirmed in Version 5.6.2f1.

  3. D0ebd839dcb75b2e883a79f42dd6732d?d=mm


    Jun 20, 2017 01:30

    Can definitely confirm still happing in 5.6.1p4

    Why is Rigidbody Interpolation broken after version 5.5.4 ?

    Can anyone else please replicate this for me so I know i am not going nuts.

    Start a new project in Unity 5.6.1
    Create a 3D object cube
    Create a second 3D object cube
    Drag second cube down under the first cube and leave a gap
    Add a rigid body to the first cube
    Set RigidBody Interpolation to Interpolate
    Press play
    As soon as the first cube drops and makes contact with the second cube the console starts spamming "In order to call GetTransformInfoExpectUpToDate, RendererUpdateManager.UpdateAll must be called first."
    Which ends up having a severe impact on the performance of the game.

    Any ideas what can be done?

  4. 992773a174a93a525417a633db816b50?d=mm


    Jun 18, 2017 05:51

    I have a project editor in good, there is this error, packaged out of all behavioral scripts are lost, I do not know how to solve

  5. 2a521f78dcda0f453ba44ab1e1f95a70?d=mm


    Jun 12, 2017 09:16

    I get this in 5.6.1.p1 when an object containing a rigidbody enters the camera frustum in play mode.

    It seems to degrade performance (probably due to spamming the console thousands of times).

    I got so sick of it, I rewrote my code to avoid using rigidbodies for moving objects.

  6. D0ebd839dcb75b2e883a79f42dd6732d?d=mm


    Jun 10, 2017 09:55

    It is so easy to reproduce.

    Unfortunately it is still happening in 5.6.1.p3
    5.5.3p4 is the last good version that Rigidbody Interpolation worked perfectly.

    Here is the easiest way for anybody to recreate issue using 5.6.1.p3:
    1) create new 3D cube game object
    2) add rigid body to cube - set interpolation to interpolate
    3) add collider to cube
    4) add another new 3D cube game object
    5) move second cube below first cube so the first one will fall onto second one
    6) press play
    7) if it does not produce the error the very first time then run again a few times.

  7. 0935ab8a457b17bf1689ccd9190a63d8?d=mm


    Jun 06, 2017 18:44

    So does this mean, they wont fix it in unity 5.6 anymore? :-(

  8. B59ceefa5fadf6a56e12381a6e9c6023?d=mm


    Jun 06, 2017 14:16

    Still happening for me, even after setting all rigidbody interpolation to none.

  9. Adfaea3d6e8857ee41c09f189d42822b?d=mm


    Jun 05, 2017 08:57

    Which future release is this fixed in??

  10. 7f6a9bffcb467f064a551635006be3d8?d=mm


    Jun 04, 2017 19:39

    "Fixed in future release"
    So, which future release?
    Here goes another month waiting to have this issue resolved... on p3 with some luck...

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.