Picking preset C in the .ini file while game doesnt have preset C

[FowlizM]

What happens if i go to .ini file and change the Preset=A to Preset=C?
Does it go back to first gen and use preset a? if so, how can i make it so that it tries to use C and goes to B if c isnt possible, only then it tries A if even b isnt possible.

Or does it just override the game's framegen preset even if it doesnt have preset c?

The place im talking about:

[pballada]

You can set Preset=C even if the game itself never offered preset C. Here's how it works, from the README (0.4.x).

Why the game's presets don't matter here

The mod doesn't use the game's DLSS-G files. It loads the runtime bundled in the dlssg_sm86\ folder: "随包运行库换成 310.9.16 … 只有这一个版本", i.e. "the bundled runtime is now 310.9.16, the only version". The preset is applied by that runtime and the project's own kernels, so [DLSSG] Preset=C works in any game that runs the mod. Preset C is FG Lite: "每生成帧 GPU 时间 2X 约 −30..−37 %、4X 约 −46 %，画质略低（主要在 HUD 与遮挡边缘）", meaning about 30–37 % less GPU time per generated frame at 2X and about 46 % less at 4X, with slightly lower quality, mainly around the HUD and occluded edges.

There's no fallback chain (C, then B, then A)

Preset takes a single value, A, B or C. Since 0.4.1 Auto was removed (it runs as A), and the default is A. What happens with each:

• C is always applied by the bundled runtime, so it doesn't need a fallback.
• B only takes effect when the game provides both a HUD-less image and a UI plane ("只在游戏同时提供 HUD-less 画面与 UI 平面时生效，多数游戏不提供"). Most games don't, and then the log records preset_ineffective.
• An invalid value (for example a typo) makes only that key fall back to its default, with a configuration_warning in the log. The rest of the mod keeps running.

Checking that it took

Set [Logging] Level=2 in dlssg_sm86.ini, start the game, and look in dlssg_sm86\logs\dlssg_sm86.log. Warnings such as preset_ineffective or configuration_warning show up there. If you want numbers, [Logging] FrameTiming=1 also writes per-frame GPU times to frame_timing.txt, so you can compare A against C.

If the game shows artefacts around the HUD with C, switch back to A.

Also make sure the key is under [DLSSG], not the old [Compatibility] section, which 0.4.1 no longer reads.