Search Issue Tracker
Fixed in 2017.1.0f3
Fixed in 5.6.X
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
- [Linux] "Trying to load color backbuffer into a complex RenderPass setup" error is thrown after entering Play mode in AR Mobile template project
- [Android] Neither of the callbacks are called when several videos with VideoPlayer are spawned on the target on the Google Pixel devices
- Texture2D memory allocation size is significantly increased when running on iOS device
- No data received in Profiler when connecting to WebGL Player without "Autoconnect Profiler" option enabled
- Screen Space Ambient Occlusion is ignored when toggling "Post Processing" visibility in the Scene window overlay
willyx78
Jan 25, 2024 10:29
Tilemap Renderer with Mode=chunck and detect chunck culling bounds=manual, give me the error.
vidextreme
Dec 13, 2023 23:57
If you are using TileMaps, this exception maybe caused by calling the tilemap.SetTile() or tilemap.SetTiles() right after instantiating the TileMap. This exception disappears, at least in my case, when I call .SetTile() on next frame or update after the Tilemap was created.
Daviiid
Aug 04, 2022 12:22
I've got this error as well. Should I just ignore it?
Walley7
Jun 07, 2022 07:12
P.S. The issue also persisted through restarts, so something in the data was setting it off.
Walley7
Jun 07, 2022 07:12
Encountered this issue when attempting to use tiles with bottom centre pivots. It doesn't show up immediately but at some point calls to tilemap.SetTilesBlock were starting to set it off (I'm dynamically streaming tile data to and from a tilemap in the editor). The only thing that solved it was to re-pivot the tiles to the centre. Everything else failed - re-creating the tilemap, re-creating the pivot, creating a brand new scene - any time I used those bottom pivot tiles this error starts recurring whenever I used SetTilesBlock.
This suggests to me that the tilemap features aren't very compatible with non-default pivots at the moment.
Threepwood
Apr 03, 2022 10:27
Not resolved. Seeing it in 2019.4.32f1 URP.
Updated various assets to current. Tried various fixes below in thread. Nothing worked. Soon as my camera renders the scene I get this error.
anycolourulike
Nov 03, 2021 16:45
Still an issue
teknic
Oct 16, 2021 02:50
Not resolved in 2019.4.22
Zucc0
Jun 29, 2021 10:48
Not resolved yet. Using 2019.4.16f1 URP
KDKGameDevInProgress
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.