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. 6df0b56702d4e28a0220a8c75138668c?d=mm


    Oct 27, 2017 19:59

    Same thing happening on Unity 2017.1.1p4! WTF

  2. D106237d0c3e8c3b667ee6d4f048f784?d=mm


    Sep 21, 2017 19:29

    Unity 2017.1.0p5 Personal (64bit) still happening.
    Suppose when Debug.Breaks() pause game... but I can not grantee that cause.
    Rarity: sometimes, very rare.

  3. 27e48159b1ed6c45da66739348b084e9?d=mm


    Sep 10, 2017 11:05

    Still getting this in Unity 2017

  4. Cdb28f894ef30712fa947bae33579c06?d=mm


    Jul 26, 2017 06:51

    Hum it always happen in light,.
    When my spotlight spot angle go higher than 70 angle, same bug will show up when the game start and end.

  5. 683aeabc4f48cfe48becc0a2b6eeb06c?d=mm


    Jul 17, 2017 10:15

    Got this today in 5.6.1f1 when I tried to use object pooling on things with physics.
    Temporary, not very satisfactory solution, remove object pooling.
    Perhaps there's some kind of physics reset needed?
    I did try reset on the inertia tensor + zero rigid body velocity + angular velocity but no difference.

  6. 3d600b1590819f67f7fc4e19a37cdb0a?d=mm


    Jul 15, 2017 16:56

    Bueno en mi caso con la versión 5.6.2f1 tenía el error :

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

    Lo que hice fué agregar un RigidBody al objeto con el error y luego lo quité, con eso el error

  7. Ef2d96bcd86fc532eb44dc10359590da?d=mm


    Jul 13, 2017 08:58

    Still getting this in Unity 2017.

    All Rigidbody Interpolate is set to none, so I assume it's this issue.

  8. 5d472a6ee79e618327e55170c0637fbe?d=mm


    Jul 13, 2017 00:12

    I had this error. I found an object that was set at x: 0, y: 0, z:-999999. There was a message in the inspector that said "Due to floating-point precision limitations, it is recommended to bring the world coordinates of the GameObject within a smaller range." I changed z to -99999, and now I'm not longer getting this error.

  9. 56cf68531706f263c5b6f7c0be223866?d=mm


    Jun 29, 2017 15:57

    5.6.2f1 , i have 22 x this error on my project.

    Please i need help, i m solo developer , cant find how to fix this since 3 months. i tryed to upgrade 3 x. Was hoping 5.6.2 will fix all problems.

  10. 416af258d2c98aca2e96e081fa82468d?d=mm


    Jun 21, 2017 07:41

    5.6.1p4 version
    This problem is still not resolved.

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.