Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implements naive multithreading for input handlers.
Adds the option to choose between single-threaded and multi-threaded pad handlers.
This may improve latency if you play with 2 or more different pad handlers.
It probably won't make a difference if you only play with 2 or more pads of the same type (e.g. only DualShock3).
But I also added a config only option "Pad handler sleep (microseconds)" for the hardcore input latency fanatics.
This setting can be used in both single and multithreaded modes.
By fiddling with that value (0-100000), you may notice faster response times.
I observed a theoretical decrease in latency by 700-800 microseconds in the best case scenario.
Keep in mind that setting this value to something close to 0 will increase your cpu usage on each used core drastically and will probably drain your pad battery rather quickly.
I'd like to emphasize that I don't know if this might result in damaged pads if used over extended periods of time.