The Input System Update Mode controls when the input system processes queued input events.
You can find and change the Update Mode by going to Project Settings > Input System Package > Input Settings > Update Mode.
The choice of Update Mode that best suits your project relates to whether you're using Update or FixedUpdate to respond to input events. You should choose this based on the specifics of the game you're making. You can read more about Update and FixedUpdate in Time and Framerate Management.
When a small amount of latency is not an issue
In cases where a small amount of input latency (a few frames) isn't an issue, set the update mode to match where you read your input. If your input code is in Update
(usually non-physics-based scenarios), use Process Events in Dynamic Update. If your input code is in FixedUpdate
(usually physics-based scenarios), use Process Events in Fixed Update.
When minimum latency is a necessity
In cases where minimum latency is a necessity, set the update mode to Process Events in Dynamic Update, even if you're using code in FixedUpdate to apply physics forces based on input. This strategy comes with some additional issues that you must be aware of. Refer to the section Optimizing for fixed-timestep scenarios for more information.
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.