There is something off with the D3D timer used here by MP. I have no idea why and cannot reproduce it. It must come down to some system configuration/component/driver that requires some special handling on the MP side.Sorry I haven't been able to provide any useful data. Only thing I can think to add is that prior to installing this build I was using the first "internal" 1.4 build which included your branch. Quite a lot has changed since then. Having said that, it doesn't explain why @HomeY still sees this problem. There must be something we're missing?
We need to find something you and HomeY have in common on their system and then find another user to confirm the issue.
The user is probably not aware of the issue at all. I cannot reproduce it regardless how hard I try. I called some friends asking to do an install and start MP (they do not use MP normally). Works perfect.
Also maybe some process plugins doing bad things here?
What happens only with stock MP?
What is when the refresh rate changer is not activated?
Same when using the Full Screen Splash Screen or not using it?
Windowed vs. Fullsceen mode?
Autostart involved and the system was not fully ready yet?
Any special GPU settings to MP?
And so on and so on. Too many possibilities for me to handle it over a thread. Would take me forever to find this out this way.
Only thing clear yet: when the refresh rate changer was run once everything is fine. Great, does not help me.
I can only offer currently one workaround to try: Set Windows refresh rate to 60Hz, set a default refresh rate for MP to 50Hz. Then the refresh rate changer ran at least once when MP started and the problem should not occur.
There is clearly something when this does not happen on the system or everyone would see it (including me).
Last edited: