Skip to content

Blueprinter 1.8.21 NO 0.34 Compatibility Hotfix

Choose a tag to compare

View all tags
@Kelly-D-Ripper Kelly-D-Ripper released this 28 Jul 15:29
· 2 commits to main since this release
2.8.2
3993bdf
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Blueprinter 1.8.21 – Nuclear Option 0.34 Compatibility Hotfix

This release adds a companion BepInEx compatibility plugin for running legacy
Blueprinter aircraft on Nuclear Option 0.34.

The primary goal of v2.8.2 is stability: affected aircraft can spawn, fly, land,
and leave the mission without the Blueprinter-related crashes addressed by this
hotfix.

What was broken?

Blueprinter 1.8.21 was restoring older Unity prefab data on Nuclear Option 0.34.
Some non-serialized runtime references were consequently null, stale, or
incompatible with the current game.

The failures included:

  • Invalid camera access from JetNozzle.AudioEffects during aircraft and camera
    transitions.
  • Missing tyre-noise and skid AudioSource references in legacy landing gear.
  • Null Aryx weapon-display runtime collections.
  • Obsolete serialized Material texture paths.
  • Dynamically loaded network prefabs not being retained reliably.
  • Stale Unity UI registry entries surviving mission teardown and crashing the
    game while returning to the main menu or closing.

What does the hotfix do?

  • Keeps dynamically loaded Blueprinter network prefabs strongly referenced.
  • Repairs missing legacy landing-gear audio references.
  • Skips only the unsafe jet-nozzle audio calculation when no valid camera object
    exists. Aircraft thrust and physics are unchanged.
  • Reinitializes vulnerable Aryx weapon-display collections.
  • Translates obsolete Blueprinter Material texture paths.
  • Releases the stale Unity GraphicRegistry only when an Aryx mission unloads.
  • Supports clients and dedicated servers.

Known HUD limitation

Some legacy HUD and MFD elements may be missing, static, or inaccurate.

This release intentionally does not reconstruct or rebind the HUD. Experimental
HUD repairs caused native spawn crashes and severe frame-time regressions.
Aircraft stability is therefore prioritized over restoring those displays.

Compatibility coverage

Assembly compatibility checks cover:

  • F-16M King Viper 1.1.8
  • FS-41 Eclipse 1.1.1
  • F-99 Shrike 1.0.9
  • MC-260 Chimera 1.1.4
  • RAH-72 Knockout 1.0.7

The FS-41, F-16 and F-99 Shrike has also completed an in-game smoke test covering spawn, flight, and a
clean mission exit on Nuclear Option 0.34.

Requirements

  • Nuclear Option 0.34
  • BepInEx 5
  • Blueprinter 1.8.21

Keep Blueprinter and the aircraft mods installed. This hotfix is a companion
plugin, not a replacement for them.

Installation

  1. Close Nuclear Option and any dedicated server.

  2. Download KellysBlueprinterServerFix.dll.

  3. Place in the BepInEx/plugins/ Nuclear Option directory.

  4. Confirm the DLL is located at:

    BepInEx/plugins/KellysBlueprinterServerFix/KellysBlueprinterServerFix.dll

  5. Start the game and confirm the BepInEx log reports:

    Kelly's Blueprinter Compatibility Fix 2.8.2 loaded

Install the hotfix on every client using these aircraft and on the dedicated
server.

Verification

  • Clean optimized and deterministic build
  • Reproducible release archive
  • Serialized Material-path tests
  • Harmony patch-signature validation against Nuclear Option 0.34
  • Target discovery against five Aryx aircraft assemblies
  • FS-41 runtime smoke test

SHA-256

B34BCA8EA52D90AA178879FC44A33137DB45AA4C5D2433952FE3330579583650

Thanks to Aryx and the Nuclear Option modding community for the aircraft,
testing, and crash reports that made this compatibility work possible.

Assets 3
Loading