I have the active input system set to “Both” and the new input system is set to use fixed update.
If I understand things correctly, if anything the old system should be a frame behind the new system, since the old system populates the inputs on update, and the new one does it on fixed update.
Instead I’m seeing the opposite, where when I press a key, the new input system doesn’t recognize it has been pressed until one fixedupdate later.
My images don’t appear to show up for some reason (even though they show up when I try to edit the post), so here they are again just in case:
My understanding is that this is likely by design due to the way that there is a separate thread that checks for input changes and processes those inputs. Those inputs will always register on the next scripting Update() rather than the original input system that checked as part of each scripting update. Which as you probably know caused other problems such as missed input events due to low framerate.
If you haven’t yet, I’d recommend filing a bug report and putting the number here if you can, and let us know the results of the bug.
Wasn’t there a setting where you chose if input events would be processed in Update or FixedUpdate?
Also AFAIK, the goal was that the new input manager is No worse than the old system latency wise.
