05-05-2018, 04:05 PM
Pages: 1 2
05-05-2018, 06:48 PM
Show us screenshots of your graphics settings please.
05-05-2018, 10:34 PM
(05-05-2018, 04:05 PM)aid.noodle Wrote: [ -> ]The speed up emulation hotkey (tab) works fine in windowed mode, but not in fullscreen mode. Any quick fix?
That is probably because you have IR Auto selected which makes the IR as close as possible to window or screen size
What Speed up emulation does is just remove the framerate cap. Your CPU is fast enough to speed up the game... but you will still be dependant on your GPU for speed as well... that is where the IR comes in, since your Iris 6100 iGPU is just slow, even in Bootcamp.
05-05-2018, 10:35 PM
(05-05-2018, 04:05 PM)aid.noodle Wrote: [ -> ]The speed up emulation hotkey (tab) works fine in windowed mode, but not in fullscreen mode. Any quick fix?
That is probably because you have IR Auto selected which makes the IR as close as possible to window or screen size, OR vsync is enabled.
What Speed up emulation does is just remove the framerate cap. Your CPU is fast enough to speed up the game... but you will still be dependant on your GPU for speed as well... that is where the IR comes in, since your Iris 6100 iGPU is just slow, even in Bootcamp.
05-06-2018, 01:04 AM
(05-05-2018, 10:34 PM)mstreurman Wrote: [ -> ]That is probably because you have IR Auto selected which makes the IR as close as possible to window or screen sizeI sometimes use between 1x and 1.5x IR at full speed, and toggling VSync off didn't help when trying to use the speed up emulation feature in fullscreen mode.
What Speed up emulation does is just remove the framerate cap. Your CPU is fast enough to speed up the game... but you will still be dependant on your GPU for speed as well... that is where the IR comes in, since your Iris 6100 iGPU is just slow, even in Bootcamp.
05-06-2018, 05:18 AM
Show us screenshots of your graphics settings. With that information we'll not need to make guesses and will be able to pretty much just tell you what's going on.
@mstreurman Even with a likely answer, ask for the information needed to know concretely what is going on! It's always better to say it concretely than to just guess.
@mstreurman Even with a likely answer, ask for the information needed to know concretely what is going on! It's always better to say it concretely than to just guess.
05-06-2018, 05:50 AM
(05-06-2018, 05:18 AM)MayImilae Wrote: [ -> ]Show us screenshots of your graphics settings. With that information we'll not need to make guesses and will be able to pretty much just tell you what's going on.
@mstreurman Even with a likely answer, ask for the information needed to know concretely what is going on! It's always better to say it concretely than to just guess.
05-06-2018, 06:08 AM
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.
05-06-2018, 06:19 AM
Interesting! I thought for sure you were running Auto Internal Resolution!
So, you have a lot of random settings on! So, let's start with portable.txt. Place a text file named "portable" next to Dolphin's EXE. This will make Dolphin not use your settings and create new local settings directory that are just defaults (until you delete the portable.txt). Now that you've done that, without changing *any settings*, run the game you'e been testing with and see if pressing Tab to speed up the game still doesn't work in fullscreen.
So, you have a lot of random settings on! So, let's start with portable.txt. Place a text file named "portable" next to Dolphin's EXE. This will make Dolphin not use your settings and create new local settings directory that are just defaults (until you delete the portable.txt). Now that you've done that, without changing *any settings*, run the game you'e been testing with and see if pressing Tab to speed up the game still doesn't work in fullscreen.
05-06-2018, 08:15 AM
(05-06-2018, 06:19 AM)MayImilae Wrote: [ -> ]Interesting! I thought for sure you were running Auto Internal Resolution!That helped solved the problem, thanks, but I don't know what even caused this issuse from the beginning.
So, you have a lot of random settings on! So, let's start with portable.txt. Place a text file named "portable" next to Dolphin's EXE. This will make Dolphin not use your settings and create new local settings directory that are just defaults (until you delete the portable.txt). Now that you've done that, without changing *any settings*, run the game you'e been testing with and see if pressing Tab to speed up the game still doesn't work in fullscreen.
Pages: 1 2