Discussion [(semi-)SOLVED] Cinemachine Freelook Has Bad Jitter at High Speed [Reinstall Cinemachine can help]

The bobbling is a wanted effect (noise) that I added. Although the jitter is visible with and without the noise effect.

Sorry I missunderstood your request, it says Late Update:


Side note, with SmartUpdate the jitter happens at high frames (like 120+). If I force a Vsync or lower the FPS to less than monitor refresh hz the jitter is gone. I'm building now for Nintendo Switch to see if the jitter is noticeable with this setup.

 

The jitter here is more noticeable:
https://drive.google.com/file/d/1OTcdRgYNl7uhOCDZapTqwUlNZm3vhYGw/view?usp=sharing

 

Jitter is 100% gone with all damping set to 0:

 

Yes, everything is smooth except the target, but now with the damping set to zero no more jitter however i need a bit of damping. lol

My character Animator moves and its properties values are updated in Update callback.

 

No jitter when setting all rigs damping to 0:
https://drive.google.com/file/d/1H4X_XLM8FA6xh6xszuoKYkKHYntaR4J4/view?usp=sharing

 

The character is moved in the OnAnimatorMove with this simple rootmotion code:

Code (CSharp):

1. navMeshAgent.velocity = animator.velocity;
2.          
3.             var positionY = Mathf.Lerp(transform.position.y, navMeshAgent.nextPosition.y, Time.deltaTime * 6f);
4.             transform.position = navMeshAgent.enabled ? new Vector3(navMeshAgent.nextPosition.x, positionY,  navMeshAgent.nextPosition.z) : animator.rootPosition;
5.             transform.rotation = animator.rootRotation;

So in conclusion, without damping no jitter and theres also no jitter with my camera controller. So i suspect is somewhere in the damping/interpolation of Vcams?

 

I don't think is the animation, it only happens with cinemachine and in some circumstances.
I just did a nintendo switch build, there's no jitter and damping is enabled on my vcam:

I get the jitter in editor but only when there's damping or with with high FPS (like more than 120). With my camera controller I don't get any jitter no matter what FPS and it has more damping than my vcam setup.
So what's going on here?

 

No inspector is visible. Again only happens if the FPS is high or damping is enabled. In the editor if I lower the FPS the jitter is gone. Has something to do with deltaTime computation?
Im on 2019.4.40f1 and CM 2.9.1

 

I'll do a PC build and report back later on.

 

We can't upgrade to 2020/2021, it has performance drawbacks for our game, we are saddly locked to 2019.
However when I tried in 2020/2021 not long ago, my camera controller exibit the same issue cinemachine vcams has with characters jittering and damping in 2019. It might have something to do with deltaTime. However i don't have that issue with my camera controller damping in 2019.
As of now, Nintendo Switch builds with cinemachine are fine, don't know other platforms (PS4/XONE), need to build to those. If the problem persist on those platforms, I might have to let go the posiblity of using cinemachine which will be really sad, it has nice features.

 

I got another issue with cinemachine, after mounting a small cut-scene for testing (with timeline) I got a huge spike from hell when transitioning from the cut vcam to the gameplay vcam (the FreeLook camera we where discussing earlier):

Deep profile:


I think i will both ditch timeline and cinemachine all together. Maybe in the future I will give it another try.

 

Hi everyone.
Thought I'd share how I solved this on my end. Checked the cinemachine settings , tried just a fixed cockpit camera (no cinemachine) , checked framerates and used the profiler to check my game loop. No luck. Noticed that my space ship has tremendous acceleration compared to the one in the tutorial I was following ( I may not have gotten every detail right, I like to learn while breaking stuff).
Tuned the thrust down and realised that it was taking longer for the shake to start, After some more experimentation I realised that I traveled very far on each test run.
I realised that the numbers for my position vector were getting very large ( 8000 + per axis). So I exited play mode. Set my initial position to a large number as described above, and the camera shake started instantly when my ship moved.
My guess is that as the vector3 numbers for the position of the gameobject or rigidbody gets too big, the precision of the physics calculations start to suffer.
Would like to know if any one else can duplicate this and if I am on the right track. Feel free to correct me on the technical details.
Either way , my problem was solved by just letting my space ship move at a lower speed and keeping my objectives within a certain area.
Hope this helps someone.

Editing this post with new information. A friend sent me this link explaining the issue http://davenewson.com/posts/2013/unity-coordinates-and-scales.html

 

Any news about this?

 

@Gregoryl
You guys found something about the blending cameras huge spike?

 

@Gregoryl
The spike still present on cinemachine v2.9.2 with timeline v1.8.0:

Deep profile:

Also cinemachine inspector is destroyed in this version:

 

Two defines, one for Post process stack 2 and the suggested cinemachine experimental damping to avoid jittery:

 

Yeah I just tried that and removing the CINEMACHINE_EXPERIMENTAL_DAMPING fixes the spike of death. The jittery is only visible in editor not at runtime (not a big deal).

 

Would like to mention that the stutter/jitter issues we had in Editor with Cinemachine is also gone in v 2.9.3 and 2.9.4. Also, the inspector that was broken got fixed too.
Good job on fixing those issues so fast!

 

Just wanted to add that I'm having the same issue in Unity 2021.3.15 where there is stuttering with the damping in editor but not in build. I'm currently trying to install the latest update of cinemachine, but the package manager is just showing that I have the latest version, when I don't, I only have 2.8.9.
I tried editing the manifest.json file to force it, where it tells me it's not built for the version I'm using, even though the changelog for cinemachine states that 2.9.4 is for versions 2019.4 and up?
Also it didn't fix the stuttering. I'm fine with waiting for the update, I just figured I'd mention the changelog thing.

 

Make sure you don't have the script define CINEMACHINE_EXPERIMENTAL_DAMPING (check in Player Settings). This was the real cause of stuttering and the spike of hell I was having.

 

It wasn't ever enabled for me:

The jitter is gone in build, it's just in editor where it appears. I'm not sure when update 2.9 for cinemachine is coming to my version of unity, but I'm fine with waiting until that comes and fixes it.

 

You gotta click "show all versions", is there (im on 2019.4)

 

In version 2.9.2 (or .3) the Editor jitter was completly gone. Make sure you upgrade to the latest version of Cinemachine. Is working fine for me since.

 

The "show all versions" toggle isn't available for me, it was apparently removed from version 2021. I did try editing the manifest file to force download version 2.9.2, but that didn't fix the jitter. Anyway this latest version is quite recent, and I'm comfortable waiting for its release on my version, as fixing the jitter isn't a pressing issue at the moment. Thanks though.

 

See I can't get any version of 2.9. The package manager only gives me the option for Cinemachine 2.8.9, even if I make a new empty project. I'm using Unity version 2021.3.15f1.

 

Thank you, that worked. If I still find judder then I'll make that thread like you mentioned.

 

i am having similar problem of cinemachine jittering at high speed(when sprinting). In my case jittering only occurs in android build. in pc no jittering occurs. And jittering occurs when frame rate is less than 30fps in android. when getting solid 30 fps no jittering occurs. And also jittering only occurs when moving in forward direction. when moving backward or sideward no jittering occurs. i posted a video showing this problem

 

This happens also when the player is moving at high speed 100 meters a second

 

I am having similar problem help me

 

Turning off the cinemachine collider solved the problem. But i need cinemachine collider

 

Removing the default from the collider layer solved it

 

@abhinavpv Thanks for this info! May come in handy for me also soon!

 

hello, I am facing the same issue.
Have you been able to solve this?
Thanks

 

@yonatanab1 It's been over 2 years since I worked on this so my memory is fuzzy on it. I can see from the posts I made here that uninstalling and reinstalling Cinemachine helped me some. Maybe that is something to start with. See what happens. Sorry, I can't be of more help at this time.
I am getting ready to get back into that project for a game I am developing. I may hit the problem again. So if you come up with a better fix if you can post it here I would greatly appreciate it. I am sure others would also. I still get hits on this thread from people looking for a solution.