Just something I want to note down for future implementation. We are running the input thread at 1000hz but not gaining full benefits because the processing is limited to how often the update thread runs, in most cases. A simple way to get more precision in scenarios where it's of utmost importance (ie. gameplay), having a timestamp in the event itself would allow for applying inputs more accuracy at a calculation level.
An implementation such as osu!'s FrameStabilityContainer could even intercept input events and update the time of all children to ease implementation.
Came up on twitter.
Just something I want to note down for future implementation. We are running the input thread at 1000hz but not gaining full benefits because the processing is limited to how often the update thread runs, in most cases. A simple way to get more precision in scenarios where it's of utmost importance (ie. gameplay), having a timestamp in the event itself would allow for applying inputs more accuracy at a calculation level.
An implementation such as osu!'s
FrameStabilityContainercould even intercept input events and update the time of all children to ease implementation.Came up on twitter.