Bug Why is CinemachineFreeLook Camera framerate dependant ?

Hi guys,

I'm using a third person cinemachine free look camera in my game and it seems to be framerate dependant when I test it.
I have an option to activate VSync or not (if On, it changes FPS to feat screen Hz).

If option is Off (so many FPS), camera movement are normal.
If option is On (so 60 FPS) camera movement are very slow.

I'm using Cinemachine 2.9.5 on Unity 2021.3.20.
Parameters used :

• Input Value Gain for each Axis.
• X axis Speed to 1 and Accel/Decel time to 0.01
• Y axis with 0.015 Speed and Accel/Decel time to0.05
• New Input system and Cinemachine Input provider.
• Cinemachine Brain Update method to Smart Update (others create some shuderring)

I have read all potentials Issues on this subject but nothing for me.
What I have already tried :

• Create a processor for Input system to decrease inputs using deltatime
• Modify GetAxisValue return value in Custom Input Provider

Have you some ideas on this please ?
Thanks guys.

 

Hi, thanks for reply.

I've realised a test project with the same parameters listed above.
It seems to come from Input provider when using gamepad, mouse seems to be OK, but Gamepad mode is not.

You can test the build given in this zip with the rest of the project.
WeTransfer link https://we.tl/t-YFm9vN9HiO, this forum not allow big Zip file.

To reproduce,

• Open the build given with the zip project
• Just put the gamepad right stick to right/left side => Get the sensitivity in mind
• Press F1 Key on your keyboard (Enable/Disable VSync)
• Put again the gamepad right stick to a side => Slower than before.

Thanks

 

Hi !

Thanks for the solution, it seems to work for the Test project.
I had already create and test this type of processor, but it was not working...

..and I know why :

During few tests I found a bug in Input Action Asset.

When you add a processor and save the input asset, sometimes the processor disappears.
I had to do it 5 times to have the processor saved with the inputs.

That's why my previous try with processor failed, it was not saved

Thanks

 

Oh, that's a great idea! I was just asking about this in another thread. I hadn't thought of just adding a processor. Thanks!

 

I'm having this exact issue. I tried adding this Processor to the Input System, but then the input doesn't register at all. I did some testing and realized it is the *Time.deltaTime part. If I remove it and add my own multiplier, it works again, but back to depending on framerate. Any ideas?

 

Whenever I add the Time.deltaTime the camera just won't respond to input, at all. Without it, it responds slowly but depends on framerate.

Code (CSharp):

1. using UnityEngine;
2. using UnityEngine.InputSystem;
3. #if UNITY_EDITOR
4. using UnityEditor;
5. [InitializeOnLoad]
6. #endif
7. public class DeltaTimeProcessor : InputProcessor<Vector2>
8. {
9. #if UNITY_EDITOR
10.     static DeltaTimeProcessor()
11.     {
12.         Initialize();
13.     }
14. #endif
15.     [RuntimeInitializeOnLoadMethod(RuntimeInitializeLoadType.BeforeSceneLoad)]
16.     static void Initialize()
17.     {
18.         InputSystem.RegisterProcessor<DeltaTimeProcessor>();
19.     }
20.     public override Vector2 Process(Vector2 value, InputControl control)
21.     {
22.         return value * Player_Controller.lookStickSensitivity/* * Time.deltaTime*/;
23.     }
24. }
25.  

I just added my own multiplier so the camera will respond faster, but it does still depend on framerate. The multiplier is a simple float. Whenever I leave the deltaTime, it will stop responding, when I remove it, it works.

 

Time Scale is set to 1.
Everything in the Input System Package Settings is exactly as in your screenshot, triple-checked.

 

Breakpoint returns Time.deltaTime as 0.016 at 60fps. Player_Controller.lookStickSensitivity is at 10.

 

Sure, I'll look into it. I will let you know once I upload it somewhere.

 

Did you also add a multiplier (scale vector) to the gamepad stick? It will move so slowly after the delta multiplication that it will appear as though it's broken and nothing is happening. It is working but the numbers just become tiny (for obvious reasons). Try adding that scale vector (you might need a huge number ~1000), and see if that helps. Hope you can fix it, that's what worked for me.

 

I can't seem to catch a break, now I can't upload the repro project to the sharing website. Lol.

 

It seems in Cinemachine 2.9.7 the input is always multiplied by deltaTime, this now creates issues for mouse input which is already a delta and shouldn't be multiplied by deltaTime.

As far as I can tell the only way around this is to directly drive axis.Value.

 

I am also having this problem after upgrading Cinemachine. Controller input is framerate independent, but the mouse is not. Have you found a fix for this?

 

Thank you for the quick reply! That seems to work!

Is this going to be fixed at some point? Will this processor break after an update at some point?

 

This:

plus this:

worked! It also seemed that I had some conflict regarding parent/child objects within my cameras, because I made some adjustments and now the original Time.deltaTime solution worked! I'm sorry I couldn't upload a repro project. Been hella busy and the times I tried to upload it would get stuck at 99%.. for hours. But it is finally solved for me! I really appreciate the support everyone.