Bug Cinemachine 2d follow stutter

Hi Guys,

I'm currently building a 2d jump and run game in Unity and I'm using Cinemachine. But unfortunately it's stuttering (in the Editor and as a build on my android Phone even more). I already tried setting aim to composer but it didnt help. Do you know what I could do? One thing i often read is decreasing the fixed timestep to 0.01, but this could cause perfomance issues, couldn't it?

Daniel

 

Version:




Scene:


Player:


I hope this helps. Unfortunately i can't upload my video file. It' s just a simple project using physics for the player movement. Should I provide code?

Daniel

 

I have the same problem, I've been searching for days and can't find

 

I sent the project in privat conversation. Hope this helps.

Daniel

 

Hmm. In my Editor the game is ok but if i build it on my phone (android, it should be a mobile game) then it jitters. Are there maybe any settings in the phone i can change?

 

Android is a funky beast. And Gregory tests on a powerful machine. So he's unlikely to see what you're seeing.

Do you have any of the Jobification options for Physics2D checked? Let me know what it looks like in the Editor Project Settings under Physics2D Job Options roll down section.

Do you have ANY 3D physics in your game? If not, remove the 3D Physics packages, all of them. They're busy even when they're not.

Whilst you're in there, remove every package you don't need.

How much of the tick boxes in the Layer Collision Matrix can you turn off? Turn off all that you can get away with turning off!

Android devices are all uniquely S***, in different ways, too. For all manner of reasons. As are differing versions of the Android OS, and OEM mods etc. None of the audio plugin and synth makers focus on Android, despite it being a huge potential market, because timings are a bit of a mess on Android and its devices, despite often having many cores sitting around doing nothing.

 

Hi Unifikation,

this is what my Job Options look like:



I don't use any 3D physics in my Game. I'm sorry that i have to ask, but what do you mean by 3d physics packages? The package manager?

 

No problem! A lot of the essential stuff of Unity is hidden... I often think that's by design...

In the Package Manager, there's various ways to see the ones you've been gifted in your project, by Unity, and the "Essential" ones, too. Almost all of both of these groups can be stripped out, and must be if you're wanting to target Android and iOS, and stay sane.

So, yes. In the Package Manager, prepare to spend a good long while trying to find out what it's telling you about what's in your project, and what you can get rid of. Prune it to the absolute minimum.

This will have an added benefit, rapidly decreasing your time to enter Play mode!

Especially if you can jettison Burst, URP and all but the 2D physics.

Speaking of 2D physics, in the screenshot, tick the "Use Multithreading" box, first one underneath the Job Options drop down. This has been a bit of a boon for me.

Also, set your physics fixedUpdate time to 1/framerate where framerate is the most common framerate you'll target. This is likely 60 on Android. The default of 1/50th is an old remnant of a time and place (Europe in the 90's and 2000's) when PAL's 50Hz scan rate and 50fps frame rate was likely a consideration.

 

@Unifikation
ok so i set the fixed timestep to 1/60 and appplication.targetFramerate to 61. And i removed some packages which seemed unnecessary to me but unfortunately the jitter hasn't improved. I wasnt able to remove URP as i haven't installed this package. Here are some photos of my package manager:

 

btw the profiler looks like this:

I think physics shouldn't be active here but only physics 2d. Is this
correct?

 

Yeah, it's a long time ago, for me, but I remember that ACTUALLY getting rid of 3D physics was nowhere near as straightforward as I thought it'd be. Sorry, I can't remember exactly where I found the last remnants of it that had to be stripped out.

Also, in your packages, you can get rid of all those monitoring packages (web request, analytics, ads etc) and the testing frame work from Unity, whilst developing.

One more thing... latest Cinemachine is 2.9.5, and there's always little gremlins that Gregory is getting rid of in each update.

And... one more thing... have you checked that "use multithreading" under 2D physics? Android devices have a lot of cores, usually, so this is generally a good thing.

But I think you're right, that memory usage, followed by a dump/cleanup is very likely causing your stutter. Just gotta track down where that 3d physics is...

Are you using Volumes for anything?

 

@Unifikation @Gregoryl

I was able to fix it. I found out that my phone was running at 120 fps while I built my Game at 60 fps . Now everything is butter smooth. Thank you Unifikation and Gregoryl very very much for your help!

Daniel