This is a maintenance release of the XeMFG backend. Install / update files now installs a missing frame-generation library, a refused start names the file that is missing or different, and the panel warns when a game's VSync keeps frame pacing from applying. The DLSS-G backend is unchanged.
Changes
- A missing
libxess_fg.dllis installed. When the game folder had nolibxess_fg.dll, Install / update files installed onlylibxell.dll, reported the repair as complete, and XeMFG still did not start. Games without Intel's frame-generation library (for example S.T.A.L.K.E.R. 2, Red Dead Redemption 2 and Elden Ring) needed a manual copy. The installer now always installs a missing file. - The panel names the refused file. A refused start used to say only that the Intel pair was unsupported. The panel now lists each file's state, such as libxess_fg.dll: missing or libxess_fg.dll: 1.2.2.118, not the supported 1.3.1.78, and offers Install / update files beside the notice.
MFGAdaUnlock-XeMFG.logrecords aruntime_filesline with each file's path, state, version and SHA-256. - Installer log and cleanup. The installer writes a log of every step in the game installation's
.mfg-dependency-backupsfolder (helper-<date>-<id>.log), or in the temporary folder when the game folder needs administrator rights, and names the log in its messages. It removes its temporary files when it finishes, and removes folders left in the temporary folder by earlier versions after a day. - VSync warning. When a game presents with VSync while frame generation is on, NVIDIA flip metering and XeMFG's pacing do not apply. General → Smoothness and display now warns and suggests turning VSync off in the game's settings, or turning on Force game VSync off when the game has no such setting. The option stays off until you turn it on.
- Clearer logs. Tags a game removes whenever it pauses frame generation, and HUD tags filtered every frame because their format differs from the output, no longer use up the log entries kept for refused required inputs. A
native_summaryline is written every 10 seconds while XeMFG presents, with the frame count, frame-generation state, refused inputs, filtered HUD tags and the game's VSync; when the lines stop, presentation stopped.
Compatibility
Existing configuration is kept. If Install / update files did not fix a game before, run it again.
Validation
The automated suite ran 175 tests with no failures, including new tests for a missing file in the install plan, the installer log and temporary cleanup, the runtime_files record of refused starts, a game presenting with VSync with and without Force game VSync off, native_summary, and a Witcher 3 session that lost the graphics device in the replay corpus. 3 artifact-provenance tests skipped because they need the experimental addon and installed PE inputs, which are not part of this build.
Field sessions on NVIDIA driver 621.01 (RTX 4070 SUPER):
- Elden Ring, missing
libxess_fg.dll: the log and the panel named the missing file. The installer planned it (missing → install), verified the download, kept the supportedlibxell.dll, wrote its log in the game folder, removed its temporary folders and completed. The next session started XeMFG. - Dragon's Dogma 2,
libxess_fg.dll1.2.2.118 in the game folder and the mod loader's_storage_folder: the log named the version and the acceptedlibxell.dll1.3.0.5. The installer replaced both copies, kept bothlibxell.dllcopies and completed. The next session started XeMFG. - Elden Ring, VSync: the warning appeared when frame generation was requested and disappeared after Force game VSync off was turned on; flip metering then became active and frame generation ran at 4x.
- Summary:
native_summarywas written every 10 seconds in every session. - Dragon's Dogma 2, regression check: after the repair, frame generation ran through Streamline at 6x and 4x with flip metering active and no device or present failure. Its UI tag (
R8G8B8A8_UNORM_SRGBon aR10G10B10A2_UNORMoutput) is filtered every frame, as in earlier versions.
These are functional checks; no image-quality or physical-latency measurement was made.
Installation and rollback
Close the game, replace the previous addon with renodx-mfgunlock.addon64, keep only one MFG Unlock addon installed, and restart.
For rollback, close the process, restore your previous addon or the 1.5.4 release, and restart.
Building this version
The addon is the mfgunlock_native_xemfg target of tests/CMakeLists.txt, published as renodx-mfgunlock.addon64; see Building the XeMFG backend.