Search Issue Tracker

Fixed in 2017.1.0f3

Fixed in 5.6

Votes

21

Found in

5.6.0b8

Issue ID

879941

Regression

Yes

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.
UnityEditor.DockArea:OnGUI()

fix in progress in this PR

https://ono.unity3d.com/unity/unity/pull-request/41589/_/animation/case879941

Comments (110)

  1. D40ed9727d7be0dbf1b368d8092082a3?d=mm

    cozyurt_unity

    Jul 13, 2020 17:27

    kedi ve köpek mamaları kedi kumu çeşitleri www.patilimama.com

  2. 92acf01c488ed67c85f8d808a08abab6?d=mm

    HasithaCJ

    May 30, 2020 05:46

    Solved by deleting directional light and make a new one.

  3. 514155156cd744b245cff7667cd08a95?d=mm

    Skunk-Software

    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

  4. 359a53acc08676bbd89cfbab56238d79?d=mm

    Excadrix13

    Oct 03, 2019 08:11

    2018.4.10f1 Appeared with LWRP

  5. B48f59299c49c9ed6ef6e20e437a1fde?d=mm

    Twyker_gp

    Oct 02, 2019 21:13

    also experiencing this problem with Unity 2019.1.2

  6. F578411e8e1346ee01b1642caa4abfb8?d=mm

    SaturnCO

    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.

  7. A72985a7d6dd029c03e832b5d96a7a2f?d=mm

    pixelR

    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.

  8. A72985a7d6dd029c03e832b5d96a7a2f?d=mm

    pixelR

    Aug 29, 2019 09:15

    I'm using unit 2019.1.10f1 now and had this error until I tried DivinosDev's solution of layout switching, now it seems that it's gone. Thank you, DivinosDev!

  9. 3a3e6c17c4ad5992f12d50ecc9782dc3?d=mm

    castor76

    Aug 27, 2019 03:02

    This is not fixed for 2019.2.1 using LWRP

  10. 4990b86569ab9af1872176dd4133355f?d=mm

    DivinosDev

    Jul 23, 2019 07:18

    If you are on Unity 2019.x (LWRP) then you can try doing this. It worked for me. Change your current layout to something else. Hit play. Then while in play mode, change the layout back to what your default was. Exit play mode and then enter it again. The error should go away.

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.