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
- [URP] Exceeding the platform's supported light limit gives shadow distortion when using Deferred Rendering Path
- URP Sample Buffer Image Tile is moved when the Offset Value is changed
- Static constructor in a struct returns false when running tests with IL2CPP
- Console throws warnings and a MissingReferenceException error for XR packages when doing a clean project import
- [Linux][IL2CPP] Dedicated server crashes when calling Socket.Send
DangerouZ720
Dec 27, 2017 15:55
still not fixed on version 2017.3.0p1
Albertomelladoc
Nov 03, 2017 10:04
This issue is still happening in 2017.1.0f3, 2017.1.1f1 and 2017.3.0b1 for me.
Error message -> Assertion failed: In order to call GetTransformInfoExpectUpToDate, RendererUpdateManager.UpdateAll must be called first.
The errors dont prevent execution or cause any trouble, but they are pretty annoying.
Best Regards
Jog
Oct 27, 2017 19:59
Same thing happening on Unity 2017.1.1p4! WTF
Samixon
Sep 21, 2017 19:29
Unity 2017.1.0p5 Personal (64bit) still happening.
Suppose when Debug.Breaks() pause game... but I can not grantee that cause.
Rarity: sometimes, very rare.
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