Seed the MFG ceiling into the driver's parameter object as well

Intercepting NVNGX_Parameters::Get only reaches the custom backend. With DLSS
enabled and the driver's NGX module loaded, GetCapabilityParameters and
AllocateParameters hand back the driver's own object and OptiScaler seeds it
through InitNGXParameters instead, so the read cannot be intercepted at all.
That is Cyberpunk's arrangement, and the arrangement the interception was written
for.

Seed DLSSG.MultiFrameCountMax there when the patches landed. The existing frame
generation block owns the count whenever it runs, so this is held below it and
skipped while OptiScaler generates the frames itself.

Author: y4my4my4m

OptiScaler/NVNGX_Parameter.cpp

@@ -834,6 +834,19 @@ void InitNGXParameters(NVSDK_NGX_Parameter* InParams, API api)
             InParams->Set("FrameGeneration.MinDriverVersionMajor", 0);
         }
     }
+
+    // Where DLSS is enabled and the driver's NGX module is loaded, the object handed back is the
+    // driver's own rather than an NVNGX_Parameters, so the read cannot be intercepted -- seeding it
+    // is the only way in. Held below the block above, which owns the count whenever it runs.
+    if (State::Instance().activeFgNvngx == FGNvngxReplacement::None)
+    {
+        // Streamline asks for capabilities several times while it maps its plugins, so a seed that
+        // finds the snippet absent gets another attempt before the count is validated.
+        MfgUnlock::TryApply();
+
+        if (auto unlockedMax = MfgUnlock::UnlockedMax(); unlockedMax > 0)
+            InParams->Set("DLSSG.MultiFrameCountMax", (int) unlockedMax);
+    }
 }
 
 NVNGX_Parameters* GetNGXParameters(API api, bool isPersistent)