Feedback [Solved] UI doesn't work with timeScale = 0

Trying to do a pause menu, I realized I couldn't... I don't understand why, since UIInputModule uses Time.unscaledTime. Is there any workaround ?

 

I noticed this problem too.

One workaround I found is to not set (in Project Settings/Input System Package) "Process Events in Fixed Update Only", but instead to select "Process Events In Both Fixed And Dynamic Update".

 

Thank you sooo much ! I wouldn't think it would be so easy

 

Now that the Fixed And Dynamic option is gone, how are we supposed to handle this?

Our game is physics based, so using Fixed Update to process input seems to make sense. At the same time, we need to set timeScale to 0 to pause physics while in the menu. Setting timeScale to 0 stops FixedUpdate from being called, which I guess is why the input system is no longer updated. However, it seems to be common to pause the game by setting timeScale to 0 and this renders the Fixed Update mode useless.

I worked around this by switching to Manual Update and updating the input system in FixedUpdate and, if timeScale is 0, also in Update.

 

I don't think that's the case. Players don't interpret frames in isolation. We humans track and extrapolate/interpolate gradual movements, we react in advance all the time. Without that skill we won't be able to catch a single thrown ball. Responsive sub-frame controls can definitely be felt by skilled players. In FPS games for example skilled gamers can make difference if the internal update is 32 (if I'm not mistaken they consider it slow), 64 or 128 times per sec.
Simply put our brain instinctively makes difference where an object should be based on how much time has passed from button press to screen update.

TLDR: I do not agree. Brain can extrapolate the correct in-between frame timing based on previous frames. And for faster games on slow machines it can easily lead to missing the time window.

 

@jonas-echterhoff Thanks for the explanation!

If Fixed Update mode doesn't make sense in most cases, what are the exceptions, what is the Fixed Update mode intended for?

It would definitely be good to explain this in the documentation. Right now, it only explains what the modes are, not why you would choose either of them. Also, «if it interacts with Physics, use FixedUpdate()» is a bit of mantra, so I suspect many users will choose Fixed Update mode, maybe without even consulting the documentation.

 

As a sample data point, we are building a physics driven game in which you can record and play back inputs. In order to achieve determinism with our playback, input in the FixedUpdate is critical!

So we appreciate the options!

One thing we've struggled with is that XR HMDs and Controllers seem to forcefully override this behavior. They update OnBeforeRender (it seems their devices are just setup that way). We're ok with a bit of input delay on the hands -- is there any way to get the OculusTouchController's to update on the FixedUpdate as well?

A side effect of this is also that XR Devices never have the m_CurrentUpdateStepCount set (and wasUpdatedThisFrame is always false). This is due to the fact that only normal update type'd have it set in InputSystem.FlipBuffersForDeviceIfNecessary.

 

I would like to change my InputSettings update mode to dynamic when game is paused and back to fixed when not paused.
How do I change the update mode with code at runtime?

-Jeff

 

Below is the enum that holds the different settings, and an example of how to apply them.

https://docs.unity3d.com/Packages/c...ine.InputSystem.InputSettings.UpdateMode.html

Code (csharp):

1. InputSystem.settings.updateMode = InputSettings.UpdateMode.ProcessEventsInDynamicUpdate;