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
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
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Shadows are not cast when you first Blit the Shadow map and then set it back to Buffer
- Changes to instanced detail mesh material don't immediately apply
- [uGUI] Vertices retrieved from GetUIVertexStream method cannot be modified when adjusting them through script
- Scroll bar scrolls less in the Package Manager packages than elsewhere when pressing on the empty scroll bar area to scroll
- Undo.RegisterCreatedObjectUndo dirties the scene, but no actual changes to Scene are made
HasithaCJ
May 30, 2020 05:46
Solved by deleting directional light and make a new one.
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
Excadrix13
Oct 03, 2019 08:11
2018.4.10f1 Appeared with LWRP
Twyker_gp
Oct 02, 2019 21:13
also experiencing this problem with Unity 2019.1.2
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.
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.
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!
castor76
Aug 27, 2019 03:02
This is not fixed for 2019.2.1 using LWRP
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.
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.