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

Graphics - General

-

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

Comments (116)

  1. 68bdf122af6c3c42def0fc1ccacdd614?d=mm

    as87dgs6asg0a

    May 31, 2017 22:13

    Im on 5.6.1f1 and i'm still getting this

  2. 7f6a9bffcb467f064a551635006be3d8?d=mm

    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!

  3. 5fbeeaa7dd0c9c0d8068ad8700d27a35?d=mm

    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.

  4. A87b439705d5345d062b57757b82ae86?d=mm

    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.

  5. 4bd8925d4c45ac67a8c674a9229e5c9d?d=mm

    Ezalbot

    May 25, 2017 05:41

    The problem only goes away when not using interpolate...

  6. B3540152fef02b6040b071a96f929c8c?d=mm

    Ryukai3

    May 22, 2017 22:04

    Still happen in 5.6.1f1 with rigidboy with interpolate/extrapolate

  7. E8d7deb571cdc9f488c451d38f1c323c?d=mm

    CodeGize

    May 22, 2017 09:37

    Still happening in 5.6.1p1 with interpolation rigidbody

  8. 8087cfeaf426b75e9d375f6edc73f883?d=mm

    mephistonight

    May 18, 2017 00:10

    To add some further context to this. I believe in some cases this might be linked to this bug:

    https://issuetracker.unity3d.com/issues/gameobjects-mesh-is-stuck-at-combined-mesh-root-scene-and-cannot-be-moved-after-aborting-a-build-process

    If I cancel a build part way through, meshes in the scene are replaced by combined meshes. If I then revert prefabs back to the prefab, it successfully fixes the mesh filter issue but kicks out the error referenced in this bug.

  9. 2c77da3d1d53514294331467d2589139?d=mm

    Cygon4

    May 17, 2017 19:32

    Still happening in 5.6.1xf1 on Linux.

    I hope Unity 5.6 will get a good send-off with bugfixes until it reaches a similar stability as 4.6.

  10. B650c41010689c70982c7c332686dae7?d=mm

    Skyway-Interactive

    May 17, 2017 10:21

    This error pops up for me first time on 5.6.1f1. The errors all started when I started toggling a spot light's shadows from None to Soft. I wanted shadows so I turned them on. The error came and went away just by toggling on or off soft to none. The scene has only two lights total. Now if the spot light is off and then turned on once the scene has loaded it has no problems, but if it's on in the editor I get errors every time.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.