github mavismmg/MFGAdaUnlock-RenoDx 1.10.1
MFG Unlock 1.10.1 - XeMFG DLSS-G with RenoDX HDR fixed, Streamline files from the panel, Add frame generation fixes

57 minutes ago

Fixes from the first week of reports on 1.10.0. Everything here comes from field reports; the games named were tested by their reporters, not by us, unless said otherwise.

XeMFG DLSS-G with RenoDX HDR (regression in 1.10.0)

Phantom Blade Zero and NTE showed artifacts with XeMFG DLSS-G in 1.10.0, and Wuthering Waves showed only the real frames, while 1.9.0 worked with the same settings. All three reports used RenoDX's HDR.

1.10.0 added a HUD composition to XeMFG DLSS-G (the HUD fix): XeFG interpolates the game's image before the HUD, and the real frame's HUD goes over each generated frame. A pixel counted as HUD wherever the final image differed from the image before the HUD. RenoDX changes the final image after the game's image before the HUD, so most of the screen counted as HUD and was pasted from the real frame.

  • The composition is used only when the image before the HUD has the same kind of format as the back buffer (8-bit, 10-bit or 16-bit float).
  • A guard counts the share of the screen marked as HUD. When most recent frames are mostly HUD, the composition turns off for the session and XeFG interpolates the final image, as in 1.9.0.
  • The support report's xmx_hud line says which applies and why.

Add frame generation

  • Streamline files from the panel. Under Add frame generation, Install / update Streamline files opens the external helper, which downloads NVIDIA's Streamline 2.14.16 files from the SDK's GitHub release. It reads only the six DLLs and the license out of the 276 MB archive (about 5 MB) and checks each file against a hash pinned in the helper. It shows what it will install and installs it into MFGUnlock-Streamline after the game exits, with a backup and a rollback journal. The panel shows when files are missing or different. Copying the files by hand still works.
  • Games without Reflex (Ninja Gaiden 4). DLSS frame generation presents and paces through Reflex, so 1.10.0 added it but left it off in a game that never uses Reflex. MFG Unlock now turns Reflex on for such a game and sends the latency markers on the game's own frame tokens. The present markers are sent around the game's Present on Streamline's swap chain. Reflex's sleep runs only for a game that numbers its frames itself. Tested on NVIDIA's Streamline Sample made into an SR-only game without Reflex: DLSS-G ran (+600 MiB) and Streamline reported no "Reflex not detected".
  • Another addon's Streamline (Shadow of the Tomb Raider). An sl.interposer.dll loaded by another addon (RenoDX's DLSS addon) that never started Streamline made the addon say "the game has its own Streamline". Only a started Streamline counts now. MFG Unlock loads its own copy beside the other one and moves its hooks to that copy.
  • RenoDX HDR upgrade in a game running in SDR (Red Dead Redemption 2 in Vulkan). Streamline sits above ReShade, so RenoDX changed the format of the real swap chain under it while DLSS-G's buffers kept the game's format, and the game crashed. The addon now compares the swap chain the game asked for with the one created. When they differ, it runs the game without Streamline for the session and says why in the panel and the support report. Use the game's own HDR with RenoDX, or turn RenoDX's swap chain upgrade off. Not yet confirmed by the reporter.
  • Loading screens. Frames without DLSS SR had no Reflex markers while DLSS-G stayed on ("Reflex not detected" about 300 times in Metro Exodus). DLSS-G now pauses after three such frames and resumes with DLSS SR.
  • HUD fix trace for testers. [DLSSG] HudTrace=3 logs the draws, dispatches and copies of three frames after DLSS SR, to find where a game draws its HUD when the HUD fix finds nothing (Metro Exodus in HDR repeats its crosshair).

Support report

  • chain_streamline and chain_provider name MFG Unlock's own files ("MFG Unlock's Streamline (MFGUnlock-Streamline)") instead of "the game's files".

  • chain_slinit and chain_force_fg no longer count Add frame generation's own slInit as the game's. In 1.10.0 they said "the game asks for DLSS frame generation itself" for Metro Exodus.

  • Streamline 1.x games (The Last of Us Part I) are named as such ("Streamline 1.x, not supported"), and the log says why nothing is hooked.

  • FP16 HDR. NVIDIA's DLSS-G does not generate on an FP16 (scRGB) swap chain: "DLSS-G currently does NOT support FP16 pixel format and scRGB color space" (DLSS-G programming guide, section 11). It reports no error either. Kingdom Come: Deliverance II's own HDR is such a swap chain, so Add frame generation produced no frames there, with NVIDIA's generator and with XeMFG DLSS-G, in 1.10.0 too. The panel and the support report now say so and suggest turning the game's HDR off or using the XeMFG method (Direct3D 12).

Tested

  • Phantom Blade Zero, XeMFG DLSS-G with RenoDX HDR: clean again, as in 1.9.0.
  • Kingdom Come: Deliverance II, Add frame generation with XeMFG DLSS-G and the HUD fix (SDR): no regression. With the game's HDR, see FP16 HDR above.
  • NVIDIA's Streamline Sample as an SR-only game, with and without Reflex: DLSS-G and XeMFG DLSS-G run (automated).

Known limits

  • Metro Exodus in HDR: the crosshair still repeats with the HUD fix (it finds no image before the HUD there); HudTrace is for the next step.
  • The Last of Us Part I: Streamline 1.x, not supported.
  • RenoDX's HDR on a game running in SDR, with Add frame generation: the addon steps aside (no frame generation) instead of crashing. Red Dead Redemption 2 with RenoDX was not tested by us for this release.
  • Games whose own HDR uses FP16 (scRGB): no frame generation through DLSS-G (NVIDIA's limit).

Full documentation: https://github.com/mavismmg/MFGAdaUnlock-RenoDx/blob/main/README.md

Don't miss a new MFGAdaUnlock-RenoDx release

NewReleases is sending notifications on new releases.