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
Toylips
Sep 10, 2017 11:05
Still getting this in Unity 2017
IssacTeoh
Jul 26, 2017 06:51
Hum it always happen in light,.
When my spotlight spot angle go higher than 70 angle, same bug will show up when the game start and end.
KB
Jul 17, 2017 10:15
Got this today in 5.6.1f1 when I tried to use object pooling on things with physics.
Temporary, not very satisfactory solution, remove object pooling.
Perhaps there's some kind of physics reset needed?
I did try reset on the inertia tensor + zero rigid body velocity + angular velocity but no difference.
alemarchena
Jul 15, 2017 16:56
Bueno en mi caso con la versión 5.6.2f1 tenía el error :
In order to call GetTransformInfoExpectUpToDate, RendererUpdateManager.UpdateAll must be called first
Lo que hice fué agregar un RigidBody al objeto con el error y luego lo quité, con eso el error
desapareció.
Saludos
MrDonk
Jul 13, 2017 08:58
Still getting this in Unity 2017.
All Rigidbody Interpolate is set to none, so I assume it's this issue.
elliselkins
Jul 13, 2017 00:12
I had this error. I found an object that was set at x: 0, y: 0, z:-999999. There was a message in the inspector that said "Due to floating-point precision limitations, it is recommended to bring the world coordinates of the GameObject within a smaller range." I changed z to -99999, and now I'm not longer getting this error.
5.6.2f1
gringan
Jun 29, 2017 15:57
5.6.2f1 , i have 22 x this error on my project.
Please i need help, i m solo developer , cant find how to fix this since 3 months. i tryed to upgrade 3 x. Was hoping 5.6.2 will fix all problems.
limjongkook
Jun 21, 2017 07:41
5.6.1p4 version
This problem is still not resolved.
mushdevstudio
Jun 20, 2017 01:32
Can definitely confirm still happing in 5.6.1p4
Why is Rigidbody Interpolation broken after version 5.5.4 ?
https://youtu.be/d-TyIUvObUs
Can anyone else please replicate this for me so I know i am not going nuts.
Start a new project in Unity 5.6.1
Create a 3D object cube
Create a second 3D object cube
Drag second cube down under the first cube and leave a gap
Add a rigid body to the first cube
Set RigidBody Interpolation to Interpolate
Press play
As soon as the first cube drops and makes contact with the second cube the console starts spamming "In order to call GetTransformInfoExpectUpToDate, RendererUpdateManager.UpdateAll must be called first."
Which ends up having a severe impact on the performance of the game.
Any ideas what can be done?
x4000
Jun 18, 2017 14:18
Yes, still happening in 5.6.1p1. In my case it seems to happen whenever I _stop_ editor playback, which is super strange.