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

  1. 1bbde5ba808a58e37884399b72328302?d=mm


    Apr 15, 2021 17:22

    It had happened to me when the directional light was inside an animated game object that was being initiated in Awake(); before pressing the "Play" button.

  2. E6d216d02201dfaeb4ef3f14f0b812f4?d=mm


    Apr 01, 2021 22:23

    It's NOT a resolved issue. using 2020.3.0f1 URP

  3. 25ef62cb527dfbe5d756e0c59ac2eaf7?d=mm


    Jan 24, 2021 21:14

    Using 2019.4.17f1, had same error. Resolved it with DivinosDev Jul 23, 2019 07:18, too. (Thanks for sharing!)
    Just a bit more info, upgraded project to URP a while ago, and probably had the error since, but not sure, as it is in a scene I haven't been working on.

  4. 2605b29b7b080293491dad330a760d4e?d=mm


    Jan 22, 2021 15:09

    Seeing this issue in 2019.4.18f1

  5. 92acf01c488ed67c85f8d808a08abab6?d=mm


    May 30, 2020 05:46

    Solved by deleting directional light and make a new one.

  6. 514155156cd744b245cff7667cd08a95?d=mm


    Jan 05, 2020 17:39

    For me,

    Problem: An error occurred right after loading a new scene.
    "In order to call GetTransformInfoExpectUpToDate, RendererUpdateManager.UpdateAll must be called first."

    Solution: Set the camera in the scene being loaded inactive. After the scene is loaded set it active again with a slight delay (a few ms).

    Note: I was using SRP scenes that were converted to HDRP

  7. 359a53acc08676bbd89cfbab56238d79?d=mm


    Oct 03, 2019 08:11

    2018.4.10f1 Appeared with LWRP

  8. B48f59299c49c9ed6ef6e20e437a1fde?d=mm


    Oct 02, 2019 21:13

    also experiencing this problem with Unity 2019.1.2

  9. F578411e8e1346ee01b1642caa4abfb8?d=mm


    Sep 22, 2019 05:03

    I'm still having this problem in Unity 2019.2.6 using LWRP. The layout change thing does seem to help though.

  10. A72985a7d6dd029c03e832b5d96a7a2f?d=mm


    Aug 29, 2019 12:02

    I take back what I wrote, as the error is also back. :( LWRP project here too. In my case, a GameObject is also not instantiated like before the error occurred.

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.