Keep FSR 3.1 running when the render scale changes more than a few times.

Each render and output size gets its own FSR 3.1 context, and there were six, never freed. Stepping through the render scales in the menu, plus the game's second scenes, used them up; the seventh size found no context, and FSR 3.1 went off for the rest of the run, leaving the game's own upscaler stand-in to show the picture. When all six are taken, the least recently used one not used in the last few calls is now destroyed once the GPU is idle, as DLSS's sizes already are.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
chrg6
2026-11-09 12:20:05 -05:00
parent cb234fade1
commit a5763d14af
2 changed files with 37 additions and 8 deletions

View File

@@ -47,6 +47,8 @@ cards).
video memory.
- Shader preparation no longer crashes the RADV driver (AMD GPUs on Linux) on a texture size query.
- Things that moved no longer leave a trail when neither DLSS nor FSR 3.1 is on.
- FSR 3.1 no longer turns itself off for the rest of the session once the render scale has been changed a few times
in the menu.
- With frame generation on, the mouse turned the camera as fast as if the game drew every frame on screen: twice as
fast with FSR 3.1 frame generation.
- The game's own Restart no longer brings the launcher back over the game, where Play could start a second copy.