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
- deadlock in AssetDatabase_AcceleratorClient_Scheduling.ScheduledRequest_Status_InProgress
- Texture Compression settings on Android and WebGL Platforms are reset to default when building the project using a script
- Camera active Texture is not written if another camera has a Script using "OnRenderImage"
- The Camera's background color is white when the device Appearance is "Light Mode"
- Some GameObjects ignore the Default Parent when creating them in the Hierarchy
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
benperry
May 03, 2017 12:24
It would be great if this fix was back ported to 5.6
y4my4m
Apr 29, 2017 04:05
Still happening 5.6.0f3
gringan
Apr 26, 2017 15:56
I just updated in 5.6.0f3
I have this 7 x this message when i open my project : ( 5 sec after load, if i click console )
In order to call GetTransformInfoExpectUpToDate, RendererUpdateManager.UpdateAll must be called first.
if i click play, unity crash.
My project works perfectly in 5.5.2f1
Thanks for your help.
Atheos-ws
Apr 18, 2017 04:16
Still happening in 5.6.0f3.
SteamVR
Gurg
Apr 12, 2017 19:08
The animation bug for this has actually been fixed, hence why this is closed. However, as ANDYSUM pointed out, https://issuetracker.unity3d.com/issues/in-order-to-call-gettransforminfoexpectuptodate-dot-dot-dot-error-message-appears-while-toggling-skinned-mesh-renderer-component is still not fixed and is what people are probably running into if on 5.6 version of Unity.