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

  1. 359a53acc08676bbd89cfbab56238d79?d=mm

    Excadrix13

    Oct 03, 2019 08:11

    2018.4.10f1 Appeared with LWRP

  2. B48f59299c49c9ed6ef6e20e437a1fde?d=mm

    Twyker_gp

    Oct 02, 2019 21:13

    also experiencing this problem with Unity 2019.1.2

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

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

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

  6. 3a3e6c17c4ad5992f12d50ecc9782dc3?d=mm

    castor76

    Aug 27, 2019 03:02

    This is not fixed for 2019.2.1 using LWRP

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

  8. 53bac73f6961e58d1e951eaeb226052e?d=mm

    yakandco

    Jul 18, 2019 08:54

    Tried deleting the layout but it didn't fix my case, I've been getting this in various 2019.1.x versions, currently on 2019.1.8 and still no fix.

  9. Db0e7008b21f50fe16d90cadb36d993c?d=mm

    nobluff67

    Jun 13, 2019 00:41

    My solution was ridiculously easy thanks to previous post from DGOYETTE, with the exception of how I resolved the issue. I changed layouts, hit play, then changed layout back. Error gone.

  10. 31b1c20e5168001902d5234006186ec4?d=mm

    dgoyette

    Jun 11, 2019 15:37

    I suddenly started getting this error in 2019.1.4, after having been using that version of Unity for several weeks without getting this error. It started occurring around the same time that I started having Unity crash fairly often doing completely normal things in the editor. Interesting, the crash reports I was getting, as well the error message in this issue, generally complained about some kind of OnGUI occurrence.

    I believe the root cause of these kinds of issues has to do with some kind of corruption of the editor Layout. When I start seeing crashes, or errors like this, Igo to "Window -> Layouts -> Revert Factory Settings..." and delete the layout. After doing so, I stopped getting this error entering playmode.

    So, for those still experiencing this issue in 2019+, try to delete your layout, and see if that helps.

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.