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

  1. SmashedAvocado

    Mar 16, 2017 01:39

    After some pain: Workaround seems to be to set "Interpolation: None" on some or all rigid bodies.

    I had about 20 boxes with Interpolation: Extrapolate, and the error was pressent. After setting those to "None", the error goes away.

  2. ImperativeGames

    Mar 14, 2017 12:12

    Workaround is not looking in log or what? Very hard to debug...

  3. TheMasonX

    Mar 11, 2017 06:53

    I take it there's still no workaround? Also, does anybody know what (if anything) this actually breaks/prevents from occuring? I've only seen it in a fresh project I'm using to test some Leap Motion ideas. I've had it since I first tried to play, but no trace and no context mean no idea why it's happening, and things seem to be working alright enough that I'm unsure if anything isn't working or if it's just logging errors.

  4. Kopter

    Mar 10, 2017 14:34

    Had this start happening in b10, still there in b11.

  5. dracolique

    Mar 09, 2017 14:15

    Still happening for me in 5.6.0b11

  6. Vincent13122

    Mar 09, 2017 07:37

    Having the same problem in beta 11, please fix this

  7. Mafutta

    Mar 06, 2017 19:30

    I sometimes see my (Gaia) + Speedtrees create strange artifacts (like triangular branches) appearing detached from the tree until player gets close enough, then they slowly disappear. Not sure if its related to this issue but weird.

  8. mangax

    Mar 03, 2017 20:46

    i encountered it in beta 10

  9. hakankaraduman

    Mar 02, 2017 15:27

    severity : 3 - workaround is possible.

    what is the workaround?

  10. shawww

    Feb 23, 2017 11:48

    +1 on this in Unity 5.6.0b9 – had a really strange import crash, reimported library and no while moving objects around in my scene it'll hang and give this error after a few seconds.

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.