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
- Object references are not loaded after you git checkout to another branch
- Only one of multiple copies of the same StateMachineBehaviour script is visible when added to the Animation state
- [XR][Vulkan][Oculus] Crash in hybrid renderer BeginRenderPass
- [Mobile]Dynamic batching is not working when working with sub mesh on a mobile device
- [Hub] Warning pop-up contains <strong></strong> when attempting to add a project to the list of projects while it's already open
Ryukai3
May 22, 2017 22:04
Still happen in 5.6.1f1 with rigidboy with interpolate/extrapolate
CodeGize
May 22, 2017 09:37
Still happening in 5.6.1p1 with interpolation rigidbody
mephistonight
May 18, 2017 00:10
To add some further context to this. I believe in some cases this might be linked to this bug:
https://issuetracker.unity3d.com/issues/gameobjects-mesh-is-stuck-at-combined-mesh-root-scene-and-cannot-be-moved-after-aborting-a-build-process
If I cancel a build part way through, meshes in the scene are replaced by combined meshes. If I then revert prefabs back to the prefab, it successfully fixes the mesh filter issue but kicks out the error referenced in this bug.
Cygon4
May 17, 2017 19:32
Still happening in 5.6.1xf1 on Linux.
I hope Unity 5.6 will get a good send-off with bugfixes until it reaches a similar stability as 4.6.
Skyway-Interactive
May 17, 2017 10:21
This error pops up for me first time on 5.6.1f1. The errors all started when I started toggling a spot light's shadows from None to Soft. I wanted shadows so I turned them on. The error came and went away just by toggling on or off soft to none. The scene has only two lights total. Now if the spot light is off and then turned on once the scene has loaded it has no problems, but if it's on in the editor I get errors every time.
JonnyFunFun
May 17, 2017 01:31
This is marked as fixed in 2017.1, however I'm still seeing hundreds of similar errors flooding my console with 2017.1.0b5:
Assertion failed: In order to call GetTransformInfoExpectUpToDate, RendererUpdateManager.UpdateAll must be called first.
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)
manu97
May 11, 2017 12:27
Issue is not fixed, still getting thousands of these errors (2)
yuliyF
May 10, 2017 13:59
Still happening in 5.6.0f4.
pixelgriffin
May 08, 2017 03:15
I can confirm this issue still exists in 5.6.0f3. However, I have no spotlights. Despite what others might be saying AFAIK my errors are resulting from interpolation on a rigidbody.
Using SteamVR's interaction system moving an object erratically and letting go a few times will cause these errors to spew out.
I have confirmed that this ONLY happens when the object's rigidbody interpolation is set to something other than none after being let go of.
Interestingly enough, when the object has interpolation on its rigidbody will not interact with other collision meshes, it is effectively non existent in terms of colliders, despite the colliders still maintaining their proper properties.
thegamerguynz
May 04, 2017 07:20
Issue is not fixed, still getting thousands of these errors