Search Issue Tracker

Fixed in 2017.1.0f3

Fixed in 5.6.X



Found in


Issue ID




Errors message at editor play

Graphics - General


Errors message at editor play

Repros: open scene1 press play in the editor and see following errors in the console:

In order to call GetTransformInfoExpectUpToDate, RendererUpdateManager.UpdateAll must be called first.

In order to call GetTransformInfoExpectUpToDate, RendererUpdateManager.UpdateAll must be called first.

fix in progress in this PR

Comments (118)

  1. Cb0856ae1cd53cfce217cc99f4b063c9?d=mm


    Jun 01, 2017 13:04

    Same here, still a problem in 5.6.1f1

  2. C5965f5d9f7bd1405739c633d44ad0c3?d=mm


    Jun 01, 2017 03:56

    It says this is a resolved issue, but I'm getting it on damn near everything in 5.6.1f1. It's becoming very annoying to test new features when some things consistently fail on start.

  3. 68bdf122af6c3c42def0fc1ccacdd614?d=mm


    May 31, 2017 22:13

    Im on 5.6.1f1 and i'm still getting this

  4. 7f6a9bffcb467f064a551635006be3d8?d=mm


    May 27, 2017 23:05

    Well... this error is VERY bad... I have created this:
    It will change all of your rigidbody assets Interpolation to None. Do NOT use it if you actually need interpolation. Hope it save some time to people that have huge projects like mine, and do not need interpolation, or can live without it for the moment...
    I know it's not the way to go, but I need to keep on working, and can't wait for the next patch release, sadly...

  5. 5fbeeaa7dd0c9c0d8068ad8700d27a35?d=mm


    May 25, 2017 17:49

    This is crazy. My team has been waiting to upgrade to 5.6, and get access to Vulkan for months. We wanted to take advantage of the performance increase before our game launches. But this error makes it completely unusable. I don't understand why such a major issue hasn't been dealt with by now.

  6. A87b439705d5345d062b57757b82ae86?d=mm


    May 25, 2017 09:19

    Just updated to Unity 5.6.1f1 (64-Bit) on Windows 10, getting this error randomly in the editor.

  7. 4bd8925d4c45ac67a8c674a9229e5c9d?d=mm


    May 25, 2017 05:41

    The problem only goes away when not using interpolate...

  8. B3540152fef02b6040b071a96f929c8c?d=mm


    May 22, 2017 22:04

    Still happen in 5.6.1f1 with rigidboy with interpolate/extrapolate

  9. E8d7deb571cdc9f488c451d38f1c323c?d=mm


    May 22, 2017 09:37

    Still happening in 5.6.1p1 with interpolation rigidbody

  10. 8087cfeaf426b75e9d375f6edc73f883?d=mm


    May 18, 2017 00:10

    To add some further context to this. I believe in some cases this might be linked to this bug:

    If I cancel a build part way through, meshes in the scene are replaced by combined meshes. If I then revert prefabs back to the prefab, it successfully fixes the mesh filter issue but kicks out the error referenced in this bug.

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.