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

  1. id0

    Jun 07, 2017 13:44

    Fixed? Not even close! 5.6.1 p2

  2. rad1c

    Jun 04, 2017 10:19

    5.6.1f1 here, defect exists, NOT resolved

  3. mushdevstudio

    Jun 03, 2017 10:16

    Unfortunately it is still happening in 5.6.1.p2
    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.p2:

  4. MichaelJT

    Jun 02, 2017 00:47

    Kind of annoying. Fixed by disabling interpolation on objects which are presently stationary, but means I need to write more code to check when they're moving/when they start moving again.


    Jun 01, 2017 13:04

    Same here, still a problem in 5.6.1f1

  6. c3534l

    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.

  7. as87dgs6asg0a

    May 31, 2017 22:13

    Im on 5.6.1f1 and i'm still getting this

  8. DoenitZ

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

  9. worx93

    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.

  10. Jakeiiii

    May 25, 2017 09:19

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

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.