Jump to content

Wataru Matsunaga

GROUND CREW
  • Posts

    1
  • Joined

  • Last visited

About Wataru Matsunaga

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Wataru Matsunaga's Achievements

Newbie

Newbie (1/14)

  • Conversation Starter Rare
  • Dedicated Rare
  • Week One Done Rare
  • One Month Later Rare
  • One Year In Rare

Recent Badges

1

Reputation

  1. Version 1.0.0

    4 downloads

    SF2 COMPLETE - NPC EXTERNAL DECOY POD FIX (EXPERIMENTAL) ======================================================== Unofficial experimental fix for AI-controlled aircraft using externally mounted chaff/flare dispenser pods in Strike Fighters 2. TESTED GAME: STRIKE FIGHTERS 2 COMPLETE (SF2 COMPLETE) This modification was tested in SF2 Complete. Compatibility with other Strike Fighters 2 editions, patch levels, or DLL builds has NOT been verified. The modification was prepared from an AircraftObject.dll with a July 2, 2013 PE build timestamp. The timestamp alone does not establish compatibility with other DLL files. 1. PURPOSE ---------- In some versions of Strike Fighters 2, AI-controlled aircraft appear unable to release chaff or flares from externally mounted dispenser pods. This experimental modification attempts to correct that behavior without requiring a simulated built-in dispenser or a separate dummy pod. 2. HOW THE FIX WAS DEVELOPED ---------------------------- The modification was developed by comparing an older AircraftObject.dll from the original Strike Fighters series (2008) with a newer one from Strike Fighters 2 (2013), and examining the countermeasure-handling code. The investigation suggested that two release-count fields used by the newer DLL were initialized for internal dispensers, but not for external dispenser pods. A small 28-byte change to the newer AircraftObject.dll sets the external dispenser's default chaff and flare release counts to four each, matching the defaults used for internal dispensers. This is a proposed fix based on binary analysis, NOT a fully established root-cause finding. The modification does not force continuous dispensing, bypass threat detection, or otherwise intentionally alter the AI's decision to release countermeasures. 3. IN-GAME TEST IN SF2 COMPLETE ------------------------------- In SF2 Complete, an AI-controlled MiG-21MF equipped with an external decoy dispenser was observed releasing both chaff and flares while engaged in combat. Screenshot description (see the accompanying screenshot): The MiG-21MF's INI files were edited to allow a decoy dispenser pod to be mounted on its centerline pylon, where that pod was not available in the original aircraft configuration. For easy visual identification, a makeshift decoy pod used the visual model of a UB-13 rocket pod. Syrian MiG-21MF fighters were then placed in combat against Israeli F-15A Baz fighters. The screenshot shows a MiG-21MF releasing flares from the external pod; chaff release was also observed. This was a test setup, not a claim of a historically authentic loadout. The special MiG-21MF INI edits and UB-13-based visual model are NOT required by the DLL modification and are not included unless separately provided. IMPORTANT LIMITATIONS: * Chaff and flare release were observed with the modified DLL installed. * Whether the dispensed countermeasures successfully decoy incoming missiles has not been verified. * Results with other aircraft, pods, missions, and game builds are unknown. * The modified DLL has not yet been compared with the original DLL under identical in-game test conditions. 4. INSTALLATION AND BACKUP -------------------------- BACK UP YOUR ORIGINAL AircraftObject.dll BEFORE MAKING ANY CHANGES. Close the game before installation. Keep the original DLL in a safe location outside the game's active DLL directory. Rename the supplied file: AircraftObject_decoy_ReleaseCount_trial.dll to: AircraftObject.dll Install it in the Objects folder of your SF2 Complete game installation (NOT in the Mods folder): <SF2 Complete game folder>\Objects\AircraftObject.dll Replace the existing AircraftObject.dll only after backing it up. This modification is build-specific. Do not replace a DLL from another version of the game. If your original DLL differs from the version for which this modification was prepared, do not install the modified DLL. 5. UNINSTALLATION ----------------- Close the game and restore your backed-up, unmodified AircraftObject.dll. Do not overwrite or delete your only original copy. 6. TROUBLESHOOTING AND FEEDBACK ------------------------------- If the game fails to start, crashes, or behaves unexpectedly, restore the original DLL immediately. Do not mix DLL files from different SF2 builds. Community testing is welcome. Please report the game edition and build, aircraft, dispenser pod, missile type, whether chaff or flares were released, and whether the original DLL behaves differently in the same scenario. Reports of successful missile decoying are especially useful. 7. GENERAL NOTICE ----------------- ORIGINAL DLL CREDIT The original AircraftObject.dll was developed by Third Wire Productions. All credit for the original DLL and its underlying code belongs to Third Wire Productions. This is an unofficial fan-made modification and does not claim authorship or ownership of the original DLL. This is an unofficial, experimental, community-made modification. It is not produced, endorsed, or supported by Third Wire Productions. Use it at your own risk. No guarantees are made regarding stability, compatibility, correctness, or effectiveness. Always preserve your original game files and respect the game's license and applicable copyright rules. Redistribution of proprietary game files, including modified DLLs, may require permission from the rights holder. No warranty is provided, to the extent permitted by applicable law. Thank you, ChatGPT 2026/10/13
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..