Chaser
There appears to be a regression that is causing color depth / banding issues in Proton 6.3-8 and 7.0-1. it makes the game look like it's running at 16-bit color depth when it is not. Running the game in Proton 5.13-6 actually solves the color depth problem. This is running on Steam Deck btw.
Hello @Blitzy, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.)
Thank you @kisak-valve
I've attached logs and comparison screens for both Proton 7.0-1 and 5.13-6.
On a side note:
I dont think it matters since its still just running through Proton but this is the GOG release of Chaser running through Steam. However, I have noticed this color depth / banding issue in lots of older games running directly from Steam.
I have noticed it in:
- Deus Ex GOTY
- Prey 2006
- Quake 4
I find Prey 2006 and Quake 4 interesting because those would be running OpenGL, so it may not be dxvk specific? Im unsure as I'm new to Proton and how it works behind the scenes.
Chaser - Color Depth / Banding Issue Comparison
Proton 7.0-1
Proton 5.13-6
steam-chaser-proton_5.13-6.log
@Blitzy Thank you for the screenshots -- that helped me find what to look for. This should be fixed in the experimental version released today. Hopefully it should be the same or better than the behavior in 5.13 - it is implemented in a slightly different way now.
Tracking note: Regression fixed in Proton 7.0-2rc2
Proton versions
proton 7.0x1 2022-04proton 5.13-6x2 2022-03proton 7.0-1x1 2022-03proton 6.3-8x1 2022-03
Launch options
PROTON_LOG=1x1 2022-03PROTON_USE_D9VK=1```x1 2019-12WINEDLLOVERRIDES="d3d8=n"x1 2019-12
Whitelist Request
System Information
Works great out of the box, works even better with d3d8to9 (https://github.com/crosire/d3d8to9). You must use
WINEDLLOVERRIDES="d3d8=n" PROTON_USE_D9VK=1as launch options.