I don’t think SKIF is the problem. SKIF is just a frontend (the launcher/app) - SKIF does not get injected into your games. SK gets injected into your games. I’d actually recommend updating to newer versions (of SKIF and SK - the installer found in the SK discord as well as the “check for updates” feature in SKIF updates both SKIF and SK) since often new versions can actually even work better as not only are new features added but also optimizations.
You can also revert back by downloading a previous version of the special k dlls (since, again, SK is what gets injected into the game - not SKIF). You could keep a backup or simply check in our discord’s #nightly-builds or #installers channels where we have previous versions of the standalone SK dlls as well as previous versions of the installers - which include both SKIF and SK etc.
Regarding catching potential bugs or issues before updates are released, I believe this is often the case and new releases tend to be really stable; however, unfortunately keeping compatibility and testing for all the many games where special k works is kinda tricky…
If a game somehow worked better with a previous version of SK, it often gets fixed after we realize it or after someone reports it, but otherwise or in the meantime and if the problem is just with one game or only a few, you could use global injection for your games where global injection with the latest SK is working for you (i also especially mention this because earlier you said “SK works with all of my other games”), and then use an older version of SK with local injection for the game where the older SK was better.
That said, have you tried local injection for this particular game ? The witcher 3 is a d3d11 game… so you can try copy/pasting the SpecialK64.dll from your special k folder into your game folder and then rename that local SpecialK64.dll to dxgi.dll - this may or may not fix your issue, but anyway it’s something to try if you haven’t already. You can try local with the latest version of SK or with an older version of SK. In some cases, even with the latest or same version of SK, local injection can work better. Though global injection is often the most compatible.
Also, keep in mind that Kaldaein has recently been working on new HDR features and adjustments, and he has fixed and improved several aspects of SK’s HDR. In the process, a few issues also cropped up and i believe most got fixed already. I imagine it’s possible that somehow in these changes something affected SK’s HDR compatibility with the witcher 3, so that may need a closer look by Kaldaien. He’s still working on improving SK’s HDR more to get it to an even higher level of quality. This may take some time, but totally worth it in my opinion. He fixed HDR for the game Tales of Arise recently for example - and it’s looking really good…
maybe @Kaldaien can see something from the logs stuff you posted for the witcher 3. For now, i’d suggest that you try local injection for this game and/or an older version of SK which you can find in the SK discord. i also suggest resetting your config (the SpecialK.ini) after changing to a different version of SK - sometimes that can avoid a potential issue. we also have a dedicated discord channel for HDR where you can also find information and post questions you have etc
and, for logs, there might be more info to work with if you attach your latest crash.log, SpecialK.log, and modules.log (here or post them in the SK discord in the support channel)
