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

  1. D0ebd839dcb75b2e883a79f42dd6732d?d=mm

    mushdevstudio

    Jun 20, 2017 01:32

    Can definitely confirm still happing in 5.6.1p4

    Why is Rigidbody Interpolation broken after version 5.5.4 ?

    https://youtu.be/d-TyIUvObUs

    Can anyone else please replicate this for me so I know i am not going nuts.

    Start a new project in Unity 5.6.1
    Create a 3D object cube
    Create a second 3D object cube
    Drag second cube down under the first cube and leave a gap
    Add a rigid body to the first cube
    Set RigidBody Interpolation to Interpolate
    Press play
    As soon as the first cube drops and makes contact with the second cube the console starts spamming "In order to call GetTransformInfoExpectUpToDate, RendererUpdateManager.UpdateAll must be called first."
    Which ends up having a severe impact on the performance of the game.

    Any ideas what can be done?

  2. E51b0bd62744e701d600ced7ba8939cf?d=mm

    x4000

    Jun 18, 2017 14:18

    Yes, still happening in 5.6.1p1. In my case it seems to happen whenever I _stop_ editor playback, which is super strange.

  3. 4590dae4f89be3a21edc119a38c11c7e?d=mm

    Arcana96

    Jun 15, 2017 23:46

    Issue is still happening on 5.6.1p1. I get the issue when I'm moving around objects without a rigidbody attached in editor. Mostly happens when I ctrl+z after moving something.

  4. Fd459f8a15274fffc7a6cbbfec1a800f?d=mm

    iaing

    Jun 14, 2017 14:45

    There are two issues where the symptom is this error reported to the console.

    This version is related to multiple animators in the same hierarchy and is fixed from 5.6.0f3.

    The other issue which can cause this error is related to the interpolation setting of rigid bodies. This is still waiting for the fix to be backported to Unity 5.6. Please track that issue here:

    https://issuetracker.unity3d.com/issues/in-order-to-call-gettransforminfoexpectuptodate-dot-dot-dot-error-message-appears-while-using-rigidbody-interpolate-slash-extrapolate

  5. Fcd7dccc5fb77e9e7a100bb95f4f95b9?d=mm

    daniel-griffiths

    Jun 13, 2017 11:50

    Got this happening in 5.6.1f1, is there a version that it is is fixed?

  6. D0ebd839dcb75b2e883a79f42dd6732d?d=mm

    mushdevstudio

    Jun 10, 2017 09:04

    Unfortunately it is still happening in 5.6.1.p3
    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.p3:
    1) create new 3D cube game object
    2) add rigid body to cube - set interpolation to interpolate
    3) add collider to cube
    4) add another new 3D cube game object
    5) move second cube below first cube so the first one will fall onto second one
    6) press play
    7) if it does not produce the error the very first time then run again a few times.

    https://youtu.be/kEam0xkTNAE

  7. E23403aaa04231977b9b19085d6c4c74?d=mm

    id0

    Jun 07, 2017 13:44

    Fixed? Not even close! 5.6.1 p2

  8. 040e156173ba5d6e7fa458011862611e?d=mm

    rad1c

    Jun 04, 2017 10:19

    5.6.1f1 here, defect exists, NOT resolved

  9. D0ebd839dcb75b2e883a79f42dd6732d?d=mm

    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

  10. 0666550579d2db934dcd72730d0051fb?d=mm

    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.

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.