[Patched] Custom Graphic Scaling Behave Weirdly

Title.

Whatever % i try to set in (using the CUSTOM rendering % selector), if i close and reopen the menu OR reboot the game, the % will change to something else increasing EVERY TIME i do those actions.

Example.. if i put it to 20%.. if i close and reopen the menu/client, it will become 24%. The next menu/client reopening it goes up to 29%, then 31. And so on, till it stop at approximately 33%..

Does it still happen while dynamic resolution scaling is turned off?

You can also try increasing the target FPS if you have to have dynamic resolution scaling on.

Dynamic scaling is off, yes and it still happens.

You could try turning off the feature: save to steam cloud

Risks to consider

Turning off this feature means your progress will only save to your local machine. If you play on multiple devices (like a PC and a Steam Deck), your progress will not carry over automatically.

Eh? What the cloud have to do with the GRAPHIC SETTINGS??? You have answered on the wrong topic i guess.

What do the cloud do each time you reopen/restart and close/exit the menu/client/game?

I dont know if no rest for the wicked has its graphics settings or controls saved/synchronized through the steam cloud, i know some games do.

Therefore i thought you wanted some kind of alternative method to try even though it not 100% guaranteed it will fix your problem.

Manual Reset: Disable Cloud Sync in the game’s properties launch the game and change to the settings you desire and save, then exit the game re-enable steam Cloud in game’s properties to force a fresh upload of your local files.

I say this again i dont know if it works i would like to try but im not at home for the next coming days😂

No, the game have not the settings saved by cloud, because i play on 2 different PCs and they have each their own settings

Im not gonna take anymore of your time

I can confirm this also happens on Live, thanks BryanFury for bringing attention to this!

It’s been relayed.

Silas

Hello.
You should see a fix for this starting with hotfix 8.

Thanks!