Search Issue Tracker
Fixed in 2017.1.0f3
Fixed in 5.6
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
- LineRenderer points lists suffers from performance issues when list is large
- Shaders take a lot of memory at runtime even when only one variant is used
- Lego Microgame crashes the Linux Editor at "ScanFilter::Merge" when selecting a WebGL build location
- GameObject reference is null when creating it inside Reset() function and assigning Script as component
- GameObject/Prefab inspector preview is slow for complex hierarchies
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.
Arcana96
Jun 15, 2017 23:46
Issue is still happening on 5.6.1p1. I get the issue when I'm moving around objects without a rigidbody attached in editor. Mostly happens when I ctrl+z after moving something.
iaing
Jun 14, 2017 14:45
There are two issues where the symptom is this error reported to the console.
This version is related to multiple animators in the same hierarchy and is fixed from 5.6.0f3.
The other issue which can cause this error is related to the interpolation setting of rigid bodies. This is still waiting for the fix to be backported to Unity 5.6. Please track that issue here:
https://issuetracker.unity3d.com/issues/in-order-to-call-gettransforminfoexpectuptodate-dot-dot-dot-error-message-appears-while-using-rigidbody-interpolate-slash-extrapolate
daniel-griffiths
Jun 13, 2017 11:50
Got this happening in 5.6.1f1, is there a version that it is is fixed?
mushdevstudio
Jun 10, 2017 09:04
Unfortunately it is still happening in 5.6.1.p3
5.5.3p4 is the last good version that Rigidbody Interpolation worked perfectly.
Here is the easiest way for anybody to recreate issue using 5.6.1.p3:
1) create new 3D cube game object
2) add rigid body to cube - set interpolation to interpolate
3) add collider to cube
4) add another new 3D cube game object
5) move second cube below first cube so the first one will fall onto second one
6) press play
7) if it does not produce the error the very first time then run again a few times.
https://youtu.be/kEam0xkTNAE
id0
Jun 07, 2017 13:44
Fixed? Not even close! 5.6.1 p2