Emulator Issues #12276
closed
"Enable progressive scan" option is reset when closing the emulator
0%
Description
Game Name?
[Put Game Name here]
Game ID? (right click the game in the game list, Properties, Info tab)
[Put Game ID here]
MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)
[Put MD5 Hash here]
What's the problem? Describe what went wrong.
The "enable progressive scan" option doesn't stick. It gets disabled again after you close and re-open the emulator.
What steps will reproduce the problem?
Enable progressive scan, close the emulator, re-open it.
Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.
Yes, 5.0-12665
Is the issue present in the latest stable version?
Not sure
If the issue isn't present in the latest stable version, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)
[First broken version number here (if applicable)]
If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible. Screenshots showing what it is supposed to look like from either console or older builds of Dolphin will help too. For more information on how to use the fifoplayer, please check here: https://wiki.dolphin-emu.org/index.php?title=FifoPlayer
[Attach any fifologs if possible, write a description of fifologs and screenshots here to assist people unfamiliar with the game.]
What are your PC specifications? (CPU, GPU, Operating System, more)
Windows 10 64 bit (only relevant spec for this)
Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)
[Anything else here]
Updated by JMC4789 about 4 years ago
- Status changed from New to Invalid
This issue lacks a bisect and none of us can reproduce the issue. Without a bisect we cannot address this issue.
If you can find the build that introduced this issue, we'll happily reopen this issue. Unfortunately, we have a problem with the issue tracker getting stacked up with open issues where no one can reproduce the problem and there's no bisect to tell us what build caused the change.
Updated by pneumatic over 2 years ago
It seems Dolphin writes the progressive setting into save states, and writes it back to global settings after loading the save state.
For some reason it doesn't appear in the GUI until after restarting Dolphin.
Steps to reproduce:
- Tick progressive scan
- Restart Dolphin
- Load game (I was using "Sonic & Sega All Stars Racing")
- Save state with hotkey
- Exit game
- Untick progressive scan
- Restart Dolphin
- Load game and previous save state
- Exit game
- Restart Dolphin
- In graphics settings the progressive scan option is now ticked
This also happens with the PAL60 setting. I was using "Crisis Day of Disaster" for that.
System: Dolphin 5.0-15445, Win7 x64, i5-4570, GTX 1070.
Updated by pneumatic over 2 years ago
This also appears to affect the Wii remote settings.
I'm not sure if it's a bug or not -- for all I know Dolphin might intend to write global settings back to and from savestates.
But it's confusing to the user, and the fact it doesn't show up in the GUI until after a restart leads me to believe it's more likely to be a bug.
Updated by pneumatic over 2 years ago
This also appears to affect the Wii remote settings.
I'm not sure if it's a bug or not -- for all I know Dolphin might intend to read/write global settings from/to savestates.
But it's confusing to the user, and the fact it doesn't show up in the GUI until after a restart leads me to believe it's more likely to be a bug.
Updated by AdmiralCurtiss over 2 years ago
This is likely related to how Wii settings are stored both in the SYSCONF in the Wii NAND and in our actual config code. Thanks for the reproduction steps, that'll help figure out what's going on here.