Timeline, cinemachine and time scale - Fixed timestep

I have a timeline when a boss appear. Before playing the timeline I just stop the time setting TimeScale to 0 and play a cutscene to show the boss. In order to make it work the update metod of the Timeline and the animator (on the camera) is set to "unscaled time". This was working great, but suddenly it stopped to work.

After a lot of search, I found that the "Fixed timestep" also affect the cinemachine camera. So if i change the fixed timestep of my game the behaviour of the camera change.

Is there any way to make the timeline or cinemachine to ignore the fixed timestep? Since I put the Unscaled tme on the update metod, I don't expect it to be influenced by fixed timestep

 

Yes, Thank you very much! Didn't expect it at the brain. Since maybe I want to have cameras affected by timescale and cameras who don't

 

Hello, I have the same issue but I found that Ignore time scale does not work when I set Time.timeScale = 0 to pause the game.
Only if I set the Update Method to LateUpdate works,but the player character movement will be very wired becuz I am using rigidbody move...

 

good to hear that ! so in my case.. use smart update?

I update CM to 2.6.0 preview 5, but the issue still exsits...
When I pause the game（time scale = 0）
1、if select smart update with Ignore time scale. the vcam damping will stop when pause.and continue when resume.
2、if select late update with Ignore time scale. the vcam will damping during pause ( that's what I want), but the player character use rigid body move look like weird...

and...
I found that some problem with the cinemachine impulse.
For example if I want to have a camera impulse during game pause ( like talking with the NPC, I will pause the game, then I need to have a camera shake ), I used cinemachine impulse.I trigger it at pause state, but the impulse will come after the game is resume.(Ignore time scale is checked)

 

Thank you for the reply ! It helps a lot !

 

Hi there!

I am currently doing a sort of slow motion where basically nothing is moving but the player!
It does work pretty well expect for the camera :/
Since it is tracking a rigidbody, switching to LateUpdate does make it work for ignoring timescale but it does look pretty bad then.

Any chance this will be updated in the future to include FixedUpdate as well?

EDIT: After checking the source code, the GetEffectiveDeltaTime has a boolean as a parameter that basically ignores the ignore scaled time parameter using the FixedUpdate or SmartUpdate. Any reason why there is such a parameter?

Thanks in advance

 

Well I might find another option but currently I basically set the timescale to something very low (along with fixedtimescale) and run the player on unscaled deltatime.

I might just actually only impact the enemies: keep the same timescale and just freeze the enemies. Might make more sense

 

Sounds good thanks

 

@Gregoryl , you are a life-saver! I used both impulses and manual zooming with timeScale 0, I was totally stuck until I read your answers. The following lines fixed my issues!

Code (CSharp):

1.  
2. CinemachineImpulseManager.Instance.IgnoreTimeScale = true;
3. Camera.main.GetComponent<CinemachineBrain>().m_UpdateMethod = CinemachineBrain.UpdateMethod.LateUpdate;
4. Camera.main.GetComponent<CinemachineBrain>().m_IgnoreTimeScale = true;
5.  

 

Finally I find this solution works , many thanks !!!

 

I just found out the IgnoreTimeScale setting is not working on Cinemachine 2.6.11 and up when using a Freelook camera with the speed setting set on "MaxSpeed".
The issue does not happen when using "InputValueGain" (but this setting has a bug which makes it framerate dependant), nor does it happen on 2.6.10.

 

I think I'm having a similar issue @Gregoryl - previously I had IgnoreTimeScale disabled to make the camera stop moving when the time scale was 0, but changing the FreeLookCamera to use Input Value Gain instead of Max Speed results in the camera ignoring the time scale, despite the setting on the Cinemachine brain.

I'll think fix this later in my project when I start using the new input system, but there is definitely is a bug there when using the old input system.