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
SnickersDaBunny
Apr 02, 2017 22:57
Still present for me in 5.6.0f3 Release.
maurovanetti
Apr 02, 2017 16:42
Error still there in 5.6.0f3, I fixed it by setting all Rigidbody components' interpolation property to None, which is good practice anyway: https://docs.unity3d.com/ScriptReference/RigidbodyInterpolation.html
Still, the documentation suggests that Rigidbodies followed by the camera have ther interpolation set to Interpolate, which makes me wonder if the error will pop up again in that case.
TenCCBuilder
Apr 01, 2017 21:31
Same for me on 5.6.0f3. Not a clear repro yet, no rigid bodies with interpolation so it is definitely something else.
With this issue closed, do we need to create a new one or is someone monitoring this still?
darky
Apr 01, 2017 21:13
I have trouble with this too, please fix it properly!
Mad_Fox
Apr 01, 2017 13:50
I've just imported my project in 5.6.0f3, and this issue is still there, the interpolation "fix" doesn't work (also i need interpolation)
Ruhan-
Apr 01, 2017 11:39
I am getting this constantly on 5.6.0f3
Just updated along with Visual Studio 2017 Community
It even goes so far as to break certain elements of my game code where the logic just gets stuck. I know it's the cause as it gets stuck exactly when the exception begins appearing.
There's not even a call stack I can look in to :\
ALL of my Rigidbodies don't use any interpolation, all set to None. So that definitely doesn't work for me.
I need a fix very soon >.<
decerto
Apr 01, 2017 03:35
Getting this on 5.6.0f3.
daisySa
Apr 01, 2017 01:58
Also getting this on 5.6.0f3. Setting Interpolation to None doesn't resolve the issue in our case.
softone
Mar 31, 2017 19:33
I can also confirm that this is happening in 5.6.0f3.
Makes debugging a bit harder when you get thousands of these in a couple of seconds...
arkano22
Mar 31, 2017 19:18
Still happening in 5.6.0f3.