Why doesnt it save my Graphic settings -_-

[Silvy]

I dont want half of it looking poopy and the other half nice :/

[Tanidar]

Please try to start the game with other Windows account and check if the game saves your settings there. The game saves its settings and progress into %appdata%\Games\sherlock holmes versus jack the ripper folder (%appdata% is the system shortcut to your C:\Users\<profile name>\AppData\Roaming\ folder)

[ARGH!!]

Originally posted by Tanidar:

Please try to start the game with other Windows account and check if the game saves your settings there. The game saves its settings and progress into %appdata%\Games\sherlock holmes versus jack the ripper folder (%appdata% is the system shortcut to your C:\Users\<profile name>\AppData\Roaming\ folder)

What are the exact files that are mean to be saved there because some files are saved there but the graphics problem isn't going away.

Anyway it might be a graphics card problem as seen by the numerous complaints.
In this thread.
https://steamcommunity.com/app/11040/discussions/0/152393186501850207/

[Nasty Pirate]

Fixes don't work.

[Wakane]

That d3d9.dll trick doesn't work for me either. GTX 1070 Win10 x64

[thetargos]

I came across this thread looking for an answer while playing this game on Linux through Proton, as it exhibits the same behavior already described. Oddly enough, as dug around, the issue indeed seems to to only affect systems running Pascal+ GPUs. I was able to play this title just fine with my Maxwell (GTX950m) based laptop just fine, without any further fiddling around. And on my wife's system, all of them with nvidia GPUs.

What I find interesting about this in particular is that the way Proton works (by means of applying a compatibility layer on top, in order to run unmodified Windows executable programs) also affects the rendering in the same way it does in native Windows, which leads me to believe to be either a driver bug (considering both the Linux and Windows drivers from nvidia share much code) or a codepath execution difference on the silicon itself. I have tested this on three systems: My main rig with a Pascal GTX1080, my laptop with a GTX 950m, both running the same driver version and set to the same Proton version, and thirdly my Wife's system, which sports a GTX760, but in her case, for simplicity on her, I did not install the binary nvidia driver, and instead runs with the open source nouveau driver, which makes use of Mesa for OpenGL and has no Vulkan support (yet), so Proton support is limited to the same basic functionality of wine without DXVK (i.e no Vulkan backend for translating DX, which is what Proton does with DX10-11); anyway, neither my laptop (Maxwell) nor my wife's system (Keppler, nouveau driver, Mesa GL) exhibit this problem.

Alas, I have not found yet a solution for this, and while the game "runs" just great, its apperance could be MUCH better.