Search Issue Tracker
Fixed in 2017.2.0f3
Fixed in 5.6.X, 2017.1.X
Votes
131
Found in
5.6.0f3
Issue ID
899009
Regression
Yes
"In order to call GetTransformInfoExpectUpToDate..." error message appears while toggling Skinned Mesh Renderer component
How to reproduce:
1. Create a new project
2. Change "Directional Light" type from Directional to Spot, make sure that it's Shadow Type settings would be set to Soft or Hard Shadows
3. Add a 3D Object as a child of "Directional Light" GameObject
4. Add a Skinned Mesh Renderer component to a 3D Object
5. Create an empty GameObject as a child of 3D Object
6. Go back to 3D Object Inspector settings and set an empty GameObject as a Root Bone
7. Toggle on and off 3D Objects Skinned Mesh Renderer component repeatedly
Expected result: No error is appearing
Actual result: "In order to call GetTransformInfoExpectUpToDate, RendererUpdateManager.UpdateAll must be called first." error message appears in the Console
Note: The important parts of this bug reproduction are Spotlight, Realtime/Mixed Shadows(hard/soft), "Skinned Mesh Renderer" with "Root Bone" assigned
Regression introduced in - 5.6.0b8
Reproducible with - 2017.1.0b1, 5.6.0f3, 5.6.0b8
Not reproducible with - 5.6.0b7, 5.5.3f1, 5.4.5f1
--------------
Fixed in 2017.2.0a4. Backports to 5.6 and 2017.1 were made.
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Konst
Apr 21, 2017 05:56
still annoying in 5.6.0p1 win10
ricanteja
Apr 20, 2017 20:47
Unity 5.6.0f3 64bit Windows 7 here
SpookyCat
Apr 20, 2017 09:54
Happens in 5.6.0p1 still making it impossible for us to use 5.6, when will this be fixed?
Morgenstern_1
Apr 19, 2017 14:02
We're encountering this issue (not the interpolation version) and it's making it next to impossible to debug anything while running in the editor as there are hundreds of errors. Is there any progress update on this?
lihaifeng
Apr 19, 2017 08:37
"RendererUpdateManager only synchronizes renderers that are added to the scene, so AssertIsTransformInfoUpToDate can only be called on renderers that are added to the scene"--------how to solve the problem?please!
Velo222
Apr 19, 2017 06:59
Just wanted to add that it seems to be an issue with Rigidbody interpolation as well (as others have stated), not just the skinned mesh renderer. Just wanted to agree with the below comment that setting all of my gameobject's Rigidbody interpolation settings to "None" makes the error go away. If I set them back to "Interpolate", the error shows up again.
mushdevstudio
Apr 19, 2017 00:14
+1
Please revert what ever was changed with interpolation since 5.3.3p1 as that runs so perfectly.
This is preventing many of us from using 5.6 :(
When we turn off all interpolation for all rigidbodies the error message goes away but the objects become all jerky and really un playable :(
djgriff
Apr 17, 2017 20:06
+ this
Michieal
Apr 17, 2017 05:00
I'm getting the same error. I'm kinda glad to see that I am not the only one.
@Gurg : Any eta's on this being fixed?
thank you.
Noogy
Apr 14, 2017 22:51
Glad to see this bug in the tracker, it popped up for me recently as well. Started happening immediately after converting my game to 5.6.0f3