You could try disabling borderless fullscreen, it's a graphics setting, under advanced.
Or you could try the other graphics backends to see if the issue happens there too.
Or you could try using the wx GUI instead of the default one(qt). You'd need to run the other .exe file for that.
Or you could see if it's a problem with Dolphin not registering the button for some reason in full screen. In the contoller settings, there's a background input setting. this makes Dolphin register all input, for controllers and hotkeys, even when the OS'es focus is on another program/window.
Or you could try disabling Render to Main and the progressive scan option. Both are unusual and not tested as well as other settings. There shouldn't be a reason to use the progressive scan option for normal users anyways.
Just to be clear, i was not able to reproduce this issue. The only issue i found was flickering when starting or stopping to hold TAB. And that only happens in Vulkan(not Opengl, D3D not tested) and if Vsync is enabled. It might be related to vsync being turned off when you disable the speed limit and being turned on again when you continue at normal speed.
Or you could try the other graphics backends to see if the issue happens there too.
Or you could try using the wx GUI instead of the default one(qt). You'd need to run the other .exe file for that.
Or you could see if it's a problem with Dolphin not registering the button for some reason in full screen. In the contoller settings, there's a background input setting. this makes Dolphin register all input, for controllers and hotkeys, even when the OS'es focus is on another program/window.
Or you could try disabling Render to Main and the progressive scan option. Both are unusual and not tested as well as other settings. There shouldn't be a reason to use the progressive scan option for normal users anyways.
Just to be clear, i was not able to reproduce this issue. The only issue i found was flickering when starting or stopping to hold TAB. And that only happens in Vulkan(not Opengl, D3D not tested) and if Vsync is enabled. It might be related to vsync being turned off when you disable the speed limit and being turned on again when you continue at normal speed.