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
- Crash when total memory consumption is over 2GB
- Red dots are rendered when copying texture with ASTC format and CompressGpu
- [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
SmashedAvocado
Apr 10, 2017 00:40
Vote regression here: https://issuetracker.unity3d.com/issues/in-order-to-call-gettransforminfoexpectuptodate-dot-dot-dot-error-message-appears-while-toggling-skinned-mesh-renderer-component
opdenis
Apr 08, 2017 19:04
>> This issue is still occurring with the public build (5.6.0f3).
+1
But it says "Voting disabled for resolved issues (Fixed)"
jtbentley
Apr 08, 2017 05:36
This issue is still occurring with the public build (5.6.0f3). Is this fixed in one of the betas?
deadly004
Apr 08, 2017 02:34
Still active unity 5.6.0f2 i just got the error.
StrongCube
Apr 07, 2017 11:38
Still here in 5.6.0f3
Maybe time for fixed?
WorldEater
Apr 07, 2017 08:13
Still here in 5.6.0f3. Shows up whenever rigidbodys are set to interpolate.
FargleBargle
Apr 06, 2017 20:50
Is anyone at Unity still working on this? It's marked as resolved, and voting is disabled, but clearly a number of people still have this problem in the release version (5.6.0f3). I'm not seeing any new bug reports though, even though I filed one myself a few days ago. This is still the only hit I get when I search for this problem.
Ruhan-
Apr 06, 2017 16:44
My solution sadly did not hold, BUT I found a SOLID way to reproduce this bug.
It isn't rigidbodies, perhaps that was it during the beta version but you can reproduce easily now even on a brand new project with NOTHING inside on the "stable" release of 5.6.0f3 following these steps.
Took me a painstaking amount of time toggling components to narrow this down.
I filed a bug report so will be helpful if you guys voted on it. Will post back once the report is verified
Try the steps I mention and you'll see :)
1. Create a brand new project, lets start fresh.(no need to import anything)
2. In the scene, create a Spotlight > Change "Shadow Type" to "Soft Shadows"
3. Keeping that Spotlight selected > Create > 3D Object > Cube (to make it a child of the light)
4. Change Cube's position to (0, 0, 1)[x, y, z] {so it is directly below Spot Light}
5. Add "Skinned Mesh Renderer" component to this Cube. (leave Mesh Renderer as is)
6. Keeping this Cube selected > Create Empty Child (creates empty GameObject as child of Cube)
7. Select Cube, drag the empty GameObject to the "Root Bone" of the "Skinned Mesh Renderer" component.
8. In the Scene View, making sure the cube is visible, toggle "Skinned Mesh Renderer" rapidly and if everything was done right, you should see the following error message
"In order to call GetTransformInfoExpectUpToDate, RendererUpdateManager.UpdateAll must be called first."
The important elements of this bug reproduction are Spotlight, Realtime/Mixed Shadows(hard/soft), "Skinned Mesh Renderer" with "Root Bone" assigned.
InteractivaStudios
Apr 05, 2017 14:54
Still happening in Unity 5.6f3 , wasn't happening in Unity 5.5
Cygon4
Apr 05, 2017 12:08
I've got this issue, too, on Unity 5.6.0f1 Linux.
For me, a mirror plane (of the non-rendertarget veriety) seems to the be issue. The mirror stopped working and whenever it enters the camera, I get the warning once (and then only again when it was off-camera for a moment).