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
- CSS is not applied when using USS type selector "GridBackground"
- Player .exe remains open as a background task after closing it when Active Input Handling is set to "Input System Package (New)"
- Exception block is being rewritten to throw an incorrect number of exceptions when running a project built using IL2CPP Scripting Backend
- [Android] [Vulkan] Warning "AndroidPlayer "<device>" VULKAN: GENERAL WARNING: The following warning was triggered: VKDBGUTILWARN003." spammed every frame when the application is actively running on a device
- Skinning Editor missing tooltips
id0
Jun 07, 2017 13:44
Fixed? Not even close! 5.6.1 p2
rad1c
Jun 04, 2017 10:19
5.6.1f1 here, defect exists, NOT resolved
mushdevstudio
Jun 03, 2017 10:16
Unfortunately it is still happening in 5.6.1.p2
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.p2:
https://youtu.be/kEam0xkTNAE
MichaelJT
Jun 02, 2017 00:47
Kind of annoying. Fixed by disabling interpolation on objects which are presently stationary, but means I need to write more code to check when they're moving/when they start moving again.
FNDEBOER
Jun 01, 2017 13:04
Same here, still a problem in 5.6.1f1
c3534l
Jun 01, 2017 03:56
It says this is a resolved issue, but I'm getting it on damn near everything in 5.6.1f1. It's becoming very annoying to test new features when some things consistently fail on start.
as87dgs6asg0a
May 31, 2017 22:13
Im on 5.6.1f1 and i'm still getting this
DoenitZ
May 27, 2017 23:05
Well... this error is VERY bad... I have created this: https://pastebin.com/5igadpKh
It will change all of your rigidbody assets Interpolation to None. Do NOT use it if you actually need interpolation. Hope it save some time to people that have huge projects like mine, and do not need interpolation, or can live without it for the moment...
I know it's not the way to go, but I need to keep on working, and can't wait for the next patch release, sadly...
Cheers!
worx93
May 25, 2017 17:49
This is crazy. My team has been waiting to upgrade to 5.6, and get access to Vulkan for months. We wanted to take advantage of the performance increase before our game launches. But this error makes it completely unusable. I don't understand why such a major issue hasn't been dealt with by now.
Jakeiiii
May 25, 2017 09:19
Just updated to Unity 5.6.1f1 (64-Bit) on Windows 10, getting this error randomly in the editor.