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

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 (111)

  1. 29a0a6c72cf3d87617183a65d1ff80b4?d=mm

    Aqualancer

    Apr 01, 2017 11:39

    I am getting this constantly on 5.6.0f3
    Just updated along with Visual Studio 2017 Community

    It even goes so far as to break certain elements of my game code where the logic just gets stuck. I know it's the cause as it gets stuck exactly when the exception begins appearing.
    There's not even a call stack I can look in to :\

    ALL of my Rigidbodies don't use any interpolation, all set to None. So that definitely doesn't work for me.
    I need a fix very soon >.<

  2. 99b07bf0a576ab31e2f7262c78b7900c?d=mm

    decerto

    Apr 01, 2017 03:35

    Getting this on 5.6.0f3.

  3. 104e7a27c612efac575ba55db7ae50cf?d=mm

    daisySa

    Apr 01, 2017 01:58

    Also getting this on 5.6.0f3. Setting Interpolation to None doesn't resolve the issue in our case.

  4. B75a6bf247575c84e8cd08ca4936199f?d=mm

    softone

    Mar 31, 2017 19:33

    I can also confirm that this is happening in 5.6.0f3.

    Makes debugging a bit harder when you get thousands of these in a couple of seconds...

  5. 8cbc139951261b97a600be0287f3d4be?d=mm

    arkano22

    Mar 31, 2017 19:18

    Still happening in 5.6.0f3.

  6. 3361a352d9e72c7c299a093fad471e91?d=mm

    Johannski

    Mar 31, 2017 16:10

    Still appearing in Unity 5.6.0f2

  7. 471bcbbec345abc90f0af904ff697e1f?d=mm

    cAyouMontreal

    Mar 24, 2017 13:21

    Issue still there in 5.6.0b11.

  8. 38f7c2e090482ca69268050474032d4f?d=mm

    josephquested

    Mar 22, 2017 04:51

    I am still getting this error in 5.6.0b11. However, it doesn't seem to be doing anything. Nothing that I can notice anyway.

  9. 58d6dfe6a233a018e8ffd07d64c602df?d=mm

    pragmascript

    Mar 20, 2017 00:14

    _NOT_ fixed for me in 5.6.0f1

  10. 7b328696dc5caae88b50a4c0afd62a1e?d=mm

    MrDVolo

    Mar 19, 2017 13:17

    Agree with 'RODOLPHITO', not fixed in 5.6.0f1.
    'Fixed in Unity 5.6.0' meaning fixed in official release (currently internal)?

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.