Give Feedback
0 of 0
About this mod
This tweak fixes some minor image quality issues in FSR, XeSS, and DLSS that are most obvious when paused.
- Permissions and credits
If you pause the game you sometimes notice visual artefacts in semi-transparent effects. In DLSS the most obvious is water spashes which become pixelated when paused. With FSR candles sometimes seem to jump around. There is one simple setting that seems to fix this...
This is really simple ini file that you can put in your Witcher 3 install directory in bin\config\platform\pc\ or add to your dx12user.settings file:
[Rendering]
UseNonJitteredCameraForTransparency=false
This has been tested in patches 4.04, 4.03 and 4.02.
Tip: FSR users - try XeSS instead!
FSR seems to make a mess of the fountain with or without this setting. However, Intel's XeSS looks better and works on all modern Graphics cards, including AMD cards from RX 6000 onwards. For Nvidia owners, DLSS is still the best option.
Tech info:
It's hard to tell if it makes a difference in gameplay, but it's obvious when time is paused. The effects where I've noticed it are animated normally, which prevents small errors in FSR/XeSS/DLSS image reconstruction from being noticable.
FSR, XeSS and DLSS render at a lower resolution then upscale. They get the extra data by rendering the image offset by a fraction of a pixel and jitter the offset each frame. If objects aren't moving then one can use samples from the previous frames to reconstruct a higher resolution image. The hard bit is detecting and gracefully handing moving/changing objects. However, if you fail to jitter correctly at every rendering pass then final reconstruction won't look as good as it should. DLSS and FSR handle bad input pretty well most of the time but it makes their job harder). In this case I believe Witcher 3 was jittering the offset correctly for opaque objects but not transparent ones.
I'm not sure why CDPR created a configuration setting for this then apparently set it wrong. It is possible that there are other cases which look better with it set
to their default: true. If you find one share screenshots!
P.S. There's various tweaks to the rendering process and extra bits of data the game engine has to pass to the upscaler. Subtle bugs in jitter or motion vectors is probably why game reviewers sometimes report that DLSS and FSR work better in some titles than others.
All my MODs:
FSR DLSS improve quality by enabling jitter on transparent - https://www.nexusmods.com/witcher3/mods/8186
Faster Ray Tracing Ultra Performance RT - https://www.nexusmods.com/witcher3/mods/7891
Improved Ray Traced Shadows - https://www.nexusmods.com/witcher3/mods/7685
This is really simple ini file that you can put in your Witcher 3 install directory in bin\config\platform\pc\ or add to your dx12user.settings file:
[Rendering]
UseNonJitteredCameraForTransparency=false
This has been tested in patches 4.04, 4.03 and 4.02.
Tip: FSR users - try XeSS instead!
FSR seems to make a mess of the fountain with or without this setting. However, Intel's XeSS looks better and works on all modern Graphics cards, including AMD cards from RX 6000 onwards. For Nvidia owners, DLSS is still the best option.
Tech info:
It's hard to tell if it makes a difference in gameplay, but it's obvious when time is paused. The effects where I've noticed it are animated normally, which prevents small errors in FSR/XeSS/DLSS image reconstruction from being noticable.
FSR, XeSS and DLSS render at a lower resolution then upscale. They get the extra data by rendering the image offset by a fraction of a pixel and jitter the offset each frame. If objects aren't moving then one can use samples from the previous frames to reconstruct a higher resolution image. The hard bit is detecting and gracefully handing moving/changing objects. However, if you fail to jitter correctly at every rendering pass then final reconstruction won't look as good as it should. DLSS and FSR handle bad input pretty well most of the time but it makes their job harder). In this case I believe Witcher 3 was jittering the offset correctly for opaque objects but not transparent ones.
I'm not sure why CDPR created a configuration setting for this then apparently set it wrong. It is possible that there are other cases which look better with it set
to their default: true. If you find one share screenshots!
P.S. There's various tweaks to the rendering process and extra bits of data the game engine has to pass to the upscaler. Subtle bugs in jitter or motion vectors is probably why game reviewers sometimes report that DLSS and FSR work better in some titles than others.
All my MODs:
FSR DLSS improve quality by enabling jitter on transparent - https://www.nexusmods.com/witcher3/mods/8186
Faster Ray Tracing Ultra Performance RT - https://www.nexusmods.com/witcher3/mods/7891
Improved Ray Traced Shadows - https://www.nexusmods.com/witcher3/mods/7685