Game over screen bug with Launchbox/Bigbox when using RetroArch with non-gl output and a slangp shader.

[sodaboy581]

Game over screen bug with Launchbox/Bigbox when using RetroArch with non-gl output and a slangp shader.

I can reproduce this 100% of the time using the latest Launchbox and latest Retroarch with the mame_libretro core.  (I opt to use the MAME core vs. standalone MAME because I prefer the way RetroArch does filters, controls and all my synced settings across cores.)

This doesn't matter if you use RetroArch downloaded by Launchbox or an external RetroArch.

Steps to reproduce are:

1. Change RetroArch's video output from GL to something else like Vulkan, d3d11, or d3d12.

2. Load a game and apply a shader.  Save that shader as a global shader.  (Probably works for a game only shader as well.)

3. Quit the game and load any of the majority of 2D arcade titles with the mame_libretro core.  Neogeo titles are good or CPS-2 ones.  (Strangely, this bug does not apply to 3D games like Tekken Tag, Bloody Roar 2, etc.)

4. Notice how the game starts to load and then shortly after, the Game Over screen pops up before the game has appeared.

This behavior is caused by RetroArch behavior, I believe, but probably something Launchbox needs to detect for.

If you eyeball the task bar as you load the game, you'll see the RetroArch icon appear, then disappear, then reappear again when the game starts playing.

Again, this only happens when output mode is not GL and you're applying a shader at RetroArch startup while utilizing the mame_libretro core.

Just wanted to report this!

Because it annoys me so much, I went back to gl and using crt-lottes but I'd really love to go back to d3d11 with crt-royale.

Thanks for looking into it!