Emulator

Game Name?

N/A

Game ID? (right click the game in the game list, properties, info tab)

N/A

MD5 Hash? (right click the game in the game list, properties, info tab, MD5 Hash: Compute)

N/A

What's the problem? Describe what went wrong.

Within Graphics settings, I am unable to select dubois-LCD-Amber-Blue Post-Processing Effect. It will change to dubois, and if a game is running, no PPE is visually applied. To get it working again, I have to select a different PPE (dubois-LCD-Green-Magenta), which then applies the effect. Selecting the entry for dubois will afterwords work at this point, but selecting dubois-LCD-Amber-Blue will immediately reproduce the issue.

I tried using arrow keys instead to access dubois-LCD-Amber-Blue, and I get a neverending scroll of dubois and dubois-LCD-Magenta-Green, since moving up to Amber-Blue resets immediately to dubois.

If I edit GFX.ini to manually set dubois-LCD-Amber-Blue, the PPE will work properly in-game, but only until clicking the Graphics settings button. The PPE will stop working and will show "dubois" in the PPE field.

What steps will reproduce the problem?

Extract the latest automated binary build to an arbitrary folder, and insert a blank file named portable.txt.

Open Graphics settings, set backend to OpenGL.

Set Stereoscopy 3D Mode to Anaglyph.

Begin a game with known good Anaglyph support.

Set Post-Processing Effect to dubois-LCD-Amber-Blue. The entry will default to 'dubois'. Notice that no effect is applied in-game.

Set Post-Processing Effect to dubois-LCD-Green-Magenta. The effect will now be applied.

Set Post-Processing Effect to dubois. The red/blue effect will now be applied.

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-8569

Is the issue present in the latest stable version?

No, 5.0

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.)

I don't have the resources to do this, but I do know that it was working as of the DolphinWx.exe generation of Dolphin builds (for example, 5.0-8101 works with it fine).

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

N/A

What are your PC specifications? (CPU, GPU, Operating System, more)

Intel Core i7-4720HQ 2.60GHz, turbo disabled
12GB DDR3, 1333MHz
Intel HD 4600
nVidia GeForce GTX 950m, 2GB DDR3 variant
Windows 10 Pro v1803

Intel Core i5-2500K, 4.2GHz
16GB DDR3, 1600MHz
AMD RX 480, 4GB variant
Windows 10 Pro v1803

AMD A8-5557M, 2.1GHz, 3.1GHz turbo boost
16GB DDR3, 1600MHz
AMD Radeon HD 8550G, 768MB shared
Windows 10 v1803

Happening with all three machines.

Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)

Please let me know if I can supply additional needed materials.

Thanks!