Limit each frame ms time on WaitForSingleObject

[MolotovCherry]

Currently hard coded to 16ms, which is fine for 60hz. We should share the monitor's refresh rate over and wait for the maximum of 1 frame for the refresh rate. Not a big deal right now, but could be a good optimization

It's not clear whether making such a change would result in any actual performance improvements, so this issue remains open until a resolution is found.

So far seems to be fine without any change

[TsuZing]

Is this the reason for performance decline? I'm streaming game on 120Hz virtual display, game's fps doesn't reach 120fps and unstable. Keep game running and press Win+shift+← to switch game to physical display, game can stable at 120fps.

[MolotovCherry]

Is this the reason for performance decline? I'm streaming game on 120Hz virtual display, game's fps doesn't reach 120fps and unstable. Keep game running and press Win+shift+← to switch game to physical display, game can stable at 120fps.

No, I highly doubt it. That is a 16ms maximum wait time (timeout). That is, it will go return when ready even before. Do keep in mind that performance "optimizations" don't always result in performance, but can actually result in worse performance. Testing would have to be done (and it works great for me, so I have nothing to test with)

... But in either case, the current driver has other performance optimizations which aren't present in the stable version. Particularly under high CPU load (which is likely your case). This had to do with setting up AvSetMmThreadCharacteristicsW for the thread under load