Skip to content

FNV GameNative 4GB + xNVSE Patcher v0.1.2-alpha

Pre-release
Pre-release

Choose a tag to compare

View all tags
@CyberShonk CyberShonk released this 19 Jun 18:04
v0.1.2-alpha
9003394
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

This alpha release fixes a persistence problem caused by GameNative’s cached unpacked executable.

GameNative may copy FalloutNV.exe.unpacked.exe back over the normal FalloutNV.exe launch target. Previous versions patched only FalloutNV.exe, allowing GameNative’s unpatched cached copy to replace it later.

Version 0.1.2-alpha now manages both executable copies as a coordinated pair so the Large Address Aware and xNVSE loader changes can persist across normal GameNative launches.

What this release fixes

The patcher now handles:

  • FalloutNV.exe
  • FalloutNV.exe.unpacked.exe

Both files are validated, backed up, patched, installed, and verified together.

The cached executable is installed first so GameNative’s potential overwrite source is secured before the normal launch executable is replaced.

Users should no longer need to rename executables, select a custom launch target, or rerun the patcher after every launch.

Changes in v0.1.2-alpha

  • Added managed support for GameNative’s persistent FalloutNV.exe.unpacked.exe cache.
  • Added separate non-.exe backups for the normal and cached executables.
  • Added pair validation that refuses mismatched clean executable files before writing.
  • Added --verify reporting for both executable copies.
  • Added explicit reporting of whether the GameNative cache is persistently covered.
  • Added upgrade handling for installations where v0.1.1-alpha patched only FalloutNV.exe.
  • Added coordinated rollback if installation of either patched file fails.
  • Updated --restore to restore both managed executable backups.
  • Added synthetic tests that simulate GameNative copying its cached executable back over FalloutNV.exe.

Requirements

  • A legitimate Steam copy of Fallout: New Vegas installed through GameNative.
  • GameNative’s Unpack Files process must have completed at least once.
  • Both FalloutNV.exe and FalloutNV.exe.unpacked.exe must be present.
  • The current xNVSE files must be installed in the game folder.
  • nvse_steam_loader.dll and nvse_1_4.dll must be present beside FalloutNV.exe.

Basic usage

  1. Enable GameNative’s Unpack Files option.
  2. Launch Fallout: New Vegas once and allow GameNative to finish unpacking it.
  3. Close the game.
  4. Place FNVGameNativePatcher.exe in the folder containing FalloutNV.exe.
  5. Run the patcher once.
  6. Continue launching the normal FalloutNV.exe entry through GameNative.

Available commands:

FNVGameNativePatcher.exe
FNVGameNativePatcher.exe --verify
FNVGameNativePatcher.exe --restore
FNVGameNativePatcher.exe --help

The patcher creates:

FalloutNV.exe.gn4gb-backup
FalloutNV.exe.unpacked.exe.gn4gb-backup

Do not delete these files if you may need to restore the original GameNative-unpacked executables.

Upgrading from v0.1.1-alpha

Run FNVGameNativePatcher.exe normally.

The patcher recognizes the previous state where only FalloutNV.exe was patched and prepares the cached executable without applying duplicate changes to the existing patched file.

Run the following afterward to confirm both files are covered:

FNVGameNativePatcher.exe --verify

Safety limits

The patcher does not attempt to repair every possible executable problem.

It makes no changes when:

  • The required GameNative cached executable is missing.
  • The two clean executable copies do not match.
  • The Steam .bind wrapper is still present.
  • Either executable is malformed or unsupported.
  • Actual Authenticode certificate data remains inside the file.
  • Authenticode metadata is malformed rather than merely stale.
  • ASLR or DYNAMIC_BASE is enabled.
  • Required xNVSE files are missing.
  • A safe PE section-header slot is unavailable.
  • The complete pair cannot be prepared and verified safely.

Patch preparation occurs before managed files are replaced. If installation fails partway through, the patcher attempts to roll both files back to their previous state.

Only the specific stale, out-of-bounds Authenticode pointer observed in the tested GameNative unpacking output is repaired automatically.

Validation status

The following automated scenarios pass locally:

  • Clean executable-pair patching.
  • Repeat-run safety.
  • Simulated GameNative cache overwrite.
  • Verification of both executable copies.
  • Byte-for-byte restoration of both managed backups.
  • Mismatched-pair refusal.
  • Missing-cache refusal.
  • Upgrade handling from the v0.1.1-alpha primary-only patch state.
  • Rollback and no-write refusal behavior.

The underlying Large Address Aware and xNVSE loader transformation was previously confirmed on an AYN Thor using GameNative.

The new v0.1.2-alpha persistent-cache workflow still requires real-device validation across GameNative launches.

Alpha status

This remains an experimental prerelease.

Additional testing is needed across Android devices, GameNative versions, Proton configurations, and Fallout: New Vegas installations.

Back up important files and saves before testing. Use --verify after patching and report the complete output if either executable is not recognized as patched.

Included files

  • FNVGameNativePatcher.exe
  • FNVGameNativePatcher.exe.sha256
  • Source code is available in this repository

This release does not include Fallout: New Vegas, xNVSE, Steamless, GameNative, or files from the established FNV 4GB Patcher.

Assets 4
Loading