I'm testing and comparing html5 build and native macOS build, and the native build feels slightly less responsive compared to the html5 build.
This is hard to quantify because the difference is so small, and I feel like I'm going crazy trying to test this, but I do notice a difference.
I'm testing the same keyboard inputs and expect the same results on both builds, and the difference is most noticable when switching from the html5 build to the native build.
I do most of the testing using html5 because it builds faster, and the times I created a native build to ensure that everything works the same I noticed that the native build "feels" more sluggish and unresponsive.
Screen updates seems fast and performance in general seems snappy, just that the response to key inputs seems slightly slower.
Overall the html5 build seems most responsive.
Windowed native build using metal feels least responsive.
Fullscreen native build using metal feels more responsive, but it's hard to tell if it is same as html5.
Native build using opengl feels more responsive in both window and fullscreen, but it's hard to tell if it is same as html5.
I have tried to add timers to the code and measure time between inputs and update/render calls, but I don't see anything of concern, and the native build has shorter times from capturing the input to the next update.
So if there is a delay/lag anywhere it seems like it would be before the key input reaches my code.
I have looked at the numerical values produced by my code, and apart from minor rounding differences, all builds seems to result in the same values, so the code itself should be behaving same on all builds.
Is this expected or known?
Is there something that could cause this?
Is there something I can do to solve this?
Am I crazy?