It’s a bit of a headscratcher for me lately. Takes about 2-10ms of performance.
Goes up and down pretty wildly in the profiler.
Have about 14 virtual and some freelook cams which i switch via changing priority in the scene.
Is there a better way of switching the cams which is more performant? Turning the gameobjects on/off doesn’t seem to make it better.
Working with 2017.03 latest patch
Using FixedUpdate Mode
Is there any chance you could export this scene for me to look? 2-10 ms is way too much.
I actually had a similar problem, but it disappeared after I restarted the unity editor. Since then I’ve not been able to reproduce it. I’ll let you know if I’ll bump into this again.
We found a fix pretty quickly with gregory via pm. Mine was reproducable, and was likely to be a combination of too many vcams in a cpu/physics heavy scene. The best workaround so far is basically always having all vcam gameobjects off except the one we’re using.
Can confirm this bug. Takes about 1000ms while using Unity’s Recorder. Couldn’t fix it no matter what.
FixedUpdate mode means that virtual cameras are updated every physics frame. If you’re doing something (e.g. recording) that bumps up your frame time, you end up causing many more physics frames to be computed every frame, which if you have lots of vcams ends up taking longer, which causes more physics frames to be computed per frame… you get the picture.
I am facing similar problem, help someone please.
Can you try, as an experiment, to remove the CinemachineConfiner? Does that improve performance?
Again same issue on our project, 2017.4 LTS, cinemachine 2.1.10
What can be done to troubleshoot ?
Basically the camera is facing several hundreds of cubes and a unity terrain, that’s basically it. One VCAM is active.
Those numbers look way off.
Can you give more details about your scene, like physics timestep, now many vcams, etc.
Also: can you show image of your vcam inspector?
We’re not using physics except for particles or other actions, but there are none at that time. Maybe you can give me some hints on how it behaves.
The scene is not optimised as it is not the focus at the moment, quite texture heavy, lots of draw calls (several thousands) and tris (several millions)
The Cinemachine Setup is as Follow
Blend List
→ 6 Cameras
→ Last Is Active and is a StateDrivenCamera
What happens when you change your Brain update mode to LateUpdate?
The update mode was on “SmartUpdate” putting it to “LateUpdate” did not change the result, same for “FixedUpdate”
That doesn’t make sense. Can you please show me the profiler (like you did above) when the Brain is on LateUpdate? I don’t care about FixedUpdate for now.
