I am getting the same error 999+ times in the console when I start my game, after having upgraded my project from Unity 5.5 to Unity 5.6.0f3.
The error is: “In order to call GetTransformInfoExpectUpToDate, RendererUpdateManager.UpdateAll must be called first.” There is no more information other than that (i.e. no script that its called from or anything is given).
The error occurs about 3 to 4 seconds after the start of my game – and like I said I get 999+ of them immediately.
I have a lot of asset store packages in my project, so I don’t know if it’s because of one of them, or if I might have to wait for the next Unity 5.6 version update in order to fix it?
I hope so I just noticed my Physics layers didn’t get imported correctly either It’s just the default Physics matrix, and none of my objects have been assigned a layer at all.
I usually don’t upgrade projects to new major versions for reasons like this. You never know what’ll go wrong and unless there’s a feature I really need in the new version, I’m not upgrading. I just started a new project on 5.6 and it’ll stay on 5.6 no matter how long the project takes.
Ya that’s a good call. I usually try not to update either, unless I have to. I just got too excited to upgrade with this project, this time, and I guess I paid the price for it lol. I’ll just have to deal with it, or reassign everything back to their proper layers (and create all the layers). I have the project backed up, but it was a couple weeks ago, so I will lose some work if I revert back to my saved one Oh well, live and learn I guess.
Yep, it’s a known issue now, and I reported it, as well as other people before me. So Unity knows about it, and they should be getting along to fixing it sometime. I havn’t looked at the latest patch releases recently though, so it may have already been fixed in one of the latest patches – I’m not sure though.
I’ll have to upgrade to one of those versions if it does get fixed though.
I saw in the tracker that this was “fixed” in 2017.1. So, naturally, I update to 2017.1.0b5, deal with all the outdated API garbage to-be-expected, and still get it:
I am stuck on version 5.5 because 5.6 breaks rigid body interpolation - so weird to break something so fundamental to 3D games programming. The fix is apparently 2017.1 but I have tried beta and it distorts and twists some of my animated models so looks like 5.5.3p3 is the last good build. This unfortunately means that I can not build Android as Vulkan and also that the new IAP won’t work because they require API24 for targetSDK and 5.5.3p3 does not support API 24 - wow after 3 years of work I am so frustrated by this!
Rigidbody interpolation works fine for me in 5.6. However, upgrading projects has never worked very well for me, start a new project and see for yourself, it does work. If something broke in the project upgrade I have no idea how to fix it though. I suspect the same is true for the incorrect model deformation in 2017.1, you can try reimporting your assets and maybe that’ll fix it.
Thanks for your advice UziMonkey. One of the first things I did when having this error was to make a brand new 5.6 project to reproduce and yes it would throw the exactly the same error even now in 5.6.1p1. I can see that the “Fixed” status has been changed to “Fix in review” - so hopefully the Unity wizards can weave their magic on this one and have 5.6 end on a good note.
In regards to upgrading a project - my current project was originally started in 4.2 and whilst there have been a few issues and hurdles here and there I have successfully upgraded to each version of Unity and have seen with my own eyes the wonderful work that the Unity team have done to in regards to optimisations and improvements. I think this is why I am so cut up about not being able to compile Android with Vulcan (5.5 doesn’t have this option).
Basically just start a new 5.6 project - add a cube - give it a rigid body and set interpolation to interpolate. Add a second cube and place it below the first cube so that when you run the project the first cube falls onto the second one. As soon as the cubes touch you will start getting the dreaded “In order to call GetTransformInfoExpectUpToDate, RendererUpdateManager.UpdateAll must be called first.” error.
Please note that sometimes it does not occur but if you run your project at least 4 times you will encounter it.
Why is Rigidbody Interpolation broken after version 5.5.4 ?
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.
I just noticed my Physics layers didn’t get imported correctly either 
It’s just the default Physics matrix, and none of my objects have been assigned a layer at all.
That is my fault.
Just sharing in case it’s helpful to anyone