Skip to content

REST Enhanced v1.6.9.580 (ReShade 5.x)

Vulkan safety and automatic scene-colour matching improvements for ReShade 5.x.

  • Skip manual Vulkan effect rendering inside active passes and on targets without required copy support, avoiding the unsafe Auto Scene Colour off path seen in Enshrouded.
  • Extend automatic target matching to same-aspect scene images down to quarter output dimensions, supporting combinations of DLSS/upscaling and reduced render scale. Manual matching modes are unchanged.
  • Preserve Vulkan attachment usage instead of automatically adding sampling access where native transient restrictions are unknown.
  • Add optional FP16 scene-copy support for eligible images that already support sampling. It stays disabled by default; enable REST_VULKAN_SCENE_TRANSFERS=1 for the game process before launch and restart. No resource shim may be active. See setup and limitations and the safety review.
  • Add an optional bounded Vulkan trace for diagnosing shader targets and safe injection boundaries, disabled during normal use.

Validation

Both x64 and x86 builds passed automated rendering-safety, lifecycle, shader-hunting, binary and packaging checks. The maintainer confirmed BG3 D3D11/Vulkan and Enshrouded SDR/HDR passes on both Modern v1.7.5.680 and Legacy v1.6.9.580.

Detailed Modern Enshrouded checks also covered DLSS Quality at 100%/67% render scale, group/Auto toggles, shader hunting, a windowed/fullscreen round-trip and clean exit. Legacy's Enshrouded pass was maintainer-reported; individual operations and exact host versions were not separately recorded. See the validation record.

Enshrouded's tested setup used --keep-vulkan-layers, the optional scene-copy switch and the process-only RESHADE_DISABLE_GRAPHICS_HOOK=1 exit workaround. Select a suitable earlier scene shader: the final UI draw remains too late for pre-UI effects. These results verify placement and stability in the tested configurations, not HDR colour accuracy or universal Vulkan allocation compatibility. The existing depth-stencil-in-use warning persists. Warframe issue #22 remains separate.