Diagnose spots a game running its own DLSS beside the Feeder
Some games have their own DLSS that the tool can't find by scanning the game folder. It then sets the game up as one with no DLSS, and the Feeder runs beside the game's own DLSS. Two DLSS sessions in one game can crash it. Kingdom Come: Deliverance II is the known case: the menu worked, and loading a save crashed the moment the game created its own DLSS (#118).
Diagnose now says so when the game's ReShade.log shows a DLSS session of its own (rendered below the output size) while the Feeder is feeding frames, and tells you what to do: on the Setup page, set the dropdown next to the game name, which reads "Auto: no DLSS", to Force native DLSS, and press Install.
It stays quiet when work_resolution in dlss5-feed.cfg is below 100%, because the Feeder's own session renders smaller then too.
Save report now includes RenoDX-DLSS5-crash.log, which the DLSS 5 add-on writes when it crashes the game.
Upstream: OptiScaler ShyVortex v0.9.33 has the same layout, so it's picked up as before.
Everything from v0.14.8 is included.