STA64 – Building a Native 64-bit Future for Star Trek:Armada
Program aborts? Network configuration? Graphic errors? Bugs? Post your question here.
posted on Yesterday, 10:07 am
STA64 is a long-term project to create an independently written, native 64-bit engine capable of running Star Trek: Armada, Armada II and Fleet Operations content.
Unlike A2FOExtensions, STA64 is not another DLL added to the original game. It is intended to become a complete replacement for the old 32-bit executable while continuing to use content from a legally owned installation.
The main goals are:
- Remove the memory ceiling and architectural restrictions of the original 32-bit engine.
- Preserve compatibility with established formats such as ODF, SOD, BZN, FPQ, SPR, CFG, TGA, DDS and Armada technology trees.
- Retain Armada’s data-driven modding approach and Fleet Operations’ ParentMod system.
- Support Armada I gameplay and content, Armada II systems and Fleet Operations additions within one engine.
- Provide native 64-bit builds for Windows and Linux.
- Keep the simulation deterministic so that matches behave consistently across platforms and can eventually support reliable multiplayer.
- Introduce modern rendering, audio and asset capabilities while continuing to support existing community content.
- Support modern formats such as glTF/GLB alongside the original Armada formats.
- Eventually integrate useful A2FOExtensions features directly into the new engine, without depending on binary hooks or the original executable.
STA64 is being developed as a clean-room implementation. Existing games, documentation and observed behaviour can be used to understand how Armada works, but the new engine code is independently written. Proprietary game assets will
not be included; users will supply their own installation.
The current Alpha 1 is an engine-foundation milestone, not yet a playable replacement. It can:
- Discover an installed Armada II or Fleet Operations data tree.
- Resolve mods and inherited ParentMod chains.
- Load content with case-insensitive, deterministic precedence.
- Read Armada I and Armada II maps.
- Open a Fleet Operations-styled native launcher and diagnostic map viewer.
- Bootstrap maps through an independent fixed-tick simulation.
- Produce matching deterministic simulation results on Windows and Linux.
Future milestones will progressively add complete object simulation, construction, movement, combat, weapons, resources, AI, pathfinding, missions, rendering, audio, user interface and multiplayer.
The eventual goal is for players and modders to load their existing Armada-based content through a modern, maintainable and expandable 64-bit engine—without being permanently constrained by an executable designed more than two decades
ago.
Unlike A2FOExtensions, STA64 is not another DLL added to the original game. It is intended to become a complete replacement for the old 32-bit executable while continuing to use content from a legally owned installation.
The main goals are:
- Remove the memory ceiling and architectural restrictions of the original 32-bit engine.
- Preserve compatibility with established formats such as ODF, SOD, BZN, FPQ, SPR, CFG, TGA, DDS and Armada technology trees.
- Retain Armada’s data-driven modding approach and Fleet Operations’ ParentMod system.
- Support Armada I gameplay and content, Armada II systems and Fleet Operations additions within one engine.
- Provide native 64-bit builds for Windows and Linux.
- Keep the simulation deterministic so that matches behave consistently across platforms and can eventually support reliable multiplayer.
- Introduce modern rendering, audio and asset capabilities while continuing to support existing community content.
- Support modern formats such as glTF/GLB alongside the original Armada formats.
- Eventually integrate useful A2FOExtensions features directly into the new engine, without depending on binary hooks or the original executable.
STA64 is being developed as a clean-room implementation. Existing games, documentation and observed behaviour can be used to understand how Armada works, but the new engine code is independently written. Proprietary game assets will
not be included; users will supply their own installation.
The current Alpha 1 is an engine-foundation milestone, not yet a playable replacement. It can:
- Discover an installed Armada II or Fleet Operations data tree.
- Resolve mods and inherited ParentMod chains.
- Load content with case-insensitive, deterministic precedence.
- Read Armada I and Armada II maps.
- Open a Fleet Operations-styled native launcher and diagnostic map viewer.
- Bootstrap maps through an independent fixed-tick simulation.
- Produce matching deterministic simulation results on Windows and Linux.
Future milestones will progressively add complete object simulation, construction, movement, combat, weapons, resources, AI, pathfinding, missions, rendering, audio, user interface and multiplayer.
The eventual goal is for players and modders to load their existing Armada-based content through a modern, maintainable and expandable 64-bit engine—without being permanently constrained by an executable designed more than two decades
ago.
Who is online
Users browsing this forum: No registered users and 7 guests