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
DanRoman
Apr 04, 2017 20:38
I'm getting this error when the camera turns towards particle system objects
JoeHoran
Apr 04, 2017 17:29
If you're using Steam VR, you'll need to edit line 167 on Throwable.cs
rb.interpolation = RigidbodyInterpolation.None;
Still an issue with 5.6.0f3 so this shouldn't be closed.
JoeHoran
Apr 04, 2017 17:24
This is still an issue in 5.6.0f3
- Using SteamVR
- All rigidbodies interpolation set to none
zworp
Apr 04, 2017 13:07
Still happening in 5.6.0f3.
ImperativeGames
Apr 03, 2017 12:11
Not so bad in 5.6 (it was thousands and thousands in mere seconds), but still happening.
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)