Repository navigation
Releases
v0.2.10 — audio distortion fix
Fixes the distorted sound in loud scenes.
If you have v0.2.9: open the start screen and press Y (controller), U (keyboard) or click Update available — no manual download needed.
You need your own disc image. No game data is included.
What's new since v0.2.9
- No more crackling in loud scenes. When many sounds play at once, the game's mix gets louder than the audio output can carry; on the GameCube the sound chip turns it down for a moment, but here the overflow was being cut off, which you heard as distortion. The game now eases the volume down just before a loud moment and back up afterwards, like the console does. In a recording of Mission 1's loudest stretch, the cut-off samples went from about a fifth of the audio to none. Quiet passages sound exactly as before.
Everything from v0.2.9 is included: the built-in updater, the faster clang-built Steam Deck version and the start-up crash fix.
Downloads
| Platform | File |
|---|---|
| Windows 10/11, x64 | sfa-recomp-windows-x64.zip |
| Linux x86_64 / Steam Deck | sfa-recomp-linux-x86_64.tar.gz |
Getting started
- Extract the package to a folder. When updating by hand, extract over the old folder: your saves and settings in
user/are kept. - Put your disc image next to the program, or pick it with Browse… on the start screen.
- Run
sfa.exe(Windows) orsfa.sh(Linux; starts fullscreen). On the Steam Deck, addsfa.shto Steam as a non-Steam game to play in Game Mode. - Press Play (START on a controller).
Known issues
- With the 60 fps option, a few heavy parts of Mission 2 (and possibly later missions) still run at 48–52 fps on the Steam Deck, so the game drops back to its own 30 fps there for a while instead of playing in slow motion.
- The shader cache only helps from the second time you see an effect. Short pauses can still happen around loading screens.
- Not tested yet: the scenes after each boss in automated runs, the ending, VS mode and the bonus games.
Reporting problems
If the game stops or crashes, it writes a report to user/crash.log next to the program. When it isn't started from a terminal (Steam, file manager, Game Mode), the full output of the last run is in user/sfa.log. Please attach both to an issue.
v0.2.9 — built-in updates
Built-in updates: this is the last version you need to download by hand.
You need your own disc image. No game data is included. Dump your disc to an .iso or .gcm (compressed formats such as RVZ need converting to ISO first, e.g. in Dolphin).
What's new since v0.2.8
- The start screen updates the game for you. When it opens, it checks GitHub for a newer release. If there is one, an Update available banner appears at the top right: press Y on a controller (or U on the keyboard, or click it). The program downloads the new version for your system, checks it arrived complete, replaces its own files and restarts. Your saves, settings and shader cache in
user/are kept.- It works on Windows 10/11 and on the Steam Deck (Desktop and Game Mode), using the
curl(orwget) andtartools those systems already have. - The version you're running is shown in the corner of the start screen.
- Without internet it simply says it couldn't check and carries on. To turn the check off, set
check_updates=0inuser/launcher.cfg.
- It works on Windows 10/11 and on the Steam Deck (Desktop and Game Mode), using the
- Install this version by hand once (as before). Every later release can be installed from the start screen.
Everything from v0.2.8 is included: the faster clang-built Steam Deck version, the start-up crash fix, the lower overhead on every platform and the better crash reports.
Downloads
| Platform | File |
|---|---|
| Windows 10/11, x64 | sfa-recomp-windows-x64.zip |
| Linux x86_64 / Steam Deck | sfa-recomp-linux-x86_64.tar.gz |
Getting started
- Extract the package to a folder. When updating, extract over the old folder: your saves and settings in
user/are kept. - Put your disc image next to the program, or pick it with Browse… on the start screen.
- Run
sfa.exe(Windows) orsfa.sh(Linux; starts fullscreen). On the Steam Deck, addsfa.shto Steam as a non-Steam game to play in Game Mode. - Press Play (START on a controller).
Known issues
- Not yet tested on a Steam Deck itself: the speed-up from v0.2.8 and the updater were tested on Windows and on Linux on a laptop.
- If the program's folder isn't writable (for example inside Program Files), updating fails with a message; move the folder somewhere writable, or update by hand.
- The 60 fps option is experimental: where 60 can't be held, on-foot missions drop back to the game's 30.
- The shader cache only helps from the second time you see an effect. Short pauses can still happen around loading screens.
- Not tested yet: the scenes after each boss in automated runs (the final boss of Mission 1 has been beaten in real play), the ending, VS mode and the bonus games.
Reporting problems
If the game stops or crashes, it writes a report to user/crash.log next to the program. When it isn't started from a terminal (Steam, file manager, Game Mode), the full output of the last run is in user/sfa.log. Please attach both to an issue.
v0.2.8 — faster Steam Deck build, crash fix
A much faster Steam Deck build, a crash fix, and less overhead everywhere.
You need your own disc image. No game data is included. Dump your disc to an .iso or .gcm (compressed formats such as RVZ need converting to ISO first, e.g. in Dolphin).
What's new since v0.2.7
- Steam Deck / Linux: the game's code runs about 42% faster. The Linux version is now built with clang, the compiler already used for Windows. Built with the previous compiler (GCC), the same game code took far longer: in a Mission 2 test it kept the CPU busy 28–29% of the time, against 16.5–17.4% now. A profiling log from a Steam Deck showed the game's own code was what held on-foot missions back from 60 fps, so this is aimed squarely at that.
- Crash fix. A race in the graphics code added in v0.2.2 could crash the game, most often during the intro: in testing, 3–6 of every 40 boots on Linux. It's fixed: 0 of 40 boots crashed afterwards, and the picture is unchanged (190 million vertices checked against the single-threaded result).
- Less overhead on every platform. A new instruction-level profiler found two expensive leftovers: a math library call made on every quantized vector load and store (6–7% of the game's CPU time), and a slow lookup on every indirect function call (1.7%). Both are gone: about 9% less CPU time for the game's code on Windows as well.
- Better crash reports. If something does go wrong,
user/crash.lognow also includes where in the program it happened, which makes problems much quicker to track down.
Everything from earlier releases is included: the 60 fps option (flight stays at 60), the Mission 1 hitch fix, the shader cache and vertex work on more CPU cores.
Downloads
| Platform | File |
|---|---|
| Windows 10/11, x64 | sfa-recomp-windows-x64.zip |
| Linux x86_64 / Steam Deck | sfa-recomp-linux-x86_64.tar.gz |
Getting started
- Extract the package to a folder. When updating, extract over the old folder: your saves and settings in
user/are kept. - Put your disc image next to the program, or pick it with Browse… on the start screen.
- Run
sfa.exe(Windows) orsfa.sh(Linux; starts fullscreen). On the Steam Deck, addsfa.shto Steam as a non-Steam game to play in Game Mode. - Press Play (START on a controller). Try Frame rate: 60 fps on the Deck: on-foot missions now have a real chance of holding it.
Known issues
- Not yet tested on a Steam Deck itself. The speed-up was measured on a laptop running Linux; a Deck profiling log (launch option
SFA_PROFILE=1 SFA_FPS=1 SFA_FPS_LOG=1 %command%) would confirm it. - The 60 fps option is experimental: where 60 can't be held, on-foot missions drop back to the game's 30.
- The shader cache only helps from the second time you see an effect. Short pauses can still happen around loading screens.
- Not tested yet: the scenes after each boss in automated runs (the final boss of Mission 1 has been beaten in real play), the ending, VS mode and the bonus games.
Reporting problems
If the game stops or crashes, it writes a report to user/crash.log next to the program. When it isn't started from a terminal (Steam, file manager, Game Mode), the full output of the last run is in user/sfa.log. Please attach both to an issue.
v0.2.7 — flight stays at 60
60 fps option: flight stages stay at 60.
You need your own disc image. No game data is included. Dump your disc to an .iso or .gcm (compressed formats such as RVZ need converting to ISO first, e.g. in Dolphin).
What's new since v0.2.6
- Flight stages no longer drop to 30 with the 60 fps option on. When a scene was too heavy to hold 60, the option went back to "the game's own frame rate", but it mistakenly used 30 even in flight stages, where the game itself runs at 60. On the Steam Deck that turned Mission 1's flight, which holds 59–60 fps for long stretches, into 30 fps after its first heavy moment. Now, in stages the game runs at 60, the option never goes lower than the Original setting would. On-foot stages still fall back to the game's 30 at normal speed when 60 can't be held.
Everything from earlier releases is included: the Mission 1 hitch fix (v0.2.6), the shader cache (v0.2.5), the 60 fps option (v0.2.3/v0.2.4) and vertex work on more CPU cores (v0.2.2).
About 60 fps on the Steam Deck
A profiling log from the Deck shows its limit is the speed of the game's own code: flight mostly holds 60, but on-foot missions need about 25 ms of work per frame, where 60 fps allows 16.7. Making the recompiled code faster across the board is the next step and is in progress.
Downloads
| Platform | File |
|---|---|
| Windows 10/11, x64 | sfa-recomp-windows-x64.zip |
| Linux x86_64 / Steam Deck | sfa-recomp-linux-x86_64.tar.gz |
Getting started
- Extract the package to a folder. When updating, extract over the old folder: your saves and settings in
user/are kept. - Put your disc image next to the program, or pick it with Browse… on the start screen.
- Run
sfa.exe(Windows) orsfa.sh(Linux; starts fullscreen). On the Steam Deck, addsfa.shto Steam as a non-Steam game to play in Game Mode. - Press Play (START on a controller).
Known issues
- The 60 fps option is experimental: on-foot missions often can't hold 60 on the Steam Deck and drop back to 30.
- The shader cache only helps from the second time you see an effect.
- Short pauses can still happen around loading screens.
- Not tested yet: the scenes after each boss in automated runs (the final boss of Mission 1 has been beaten in real play), the ending, VS mode and the bonus games.
Reporting problems
If the game stops or crashes, it writes a report to user/crash.log next to the program. When it isn't started from a terminal (Steam, file manager, Game Mode), the full output of the last run is in user/sfa.log. Please attach both to an issue.
v0.2.6 — Mission 1 hitch fix
Mission 1's biggest hitches fixed.
You need your own disc image. No game data is included. Dump your disc to an .iso or .gcm (compressed formats such as RVZ need converting to ISO first, e.g. in Dolphin).
What's new since v0.2.5
- No more big stutter when Mission 1's fleet appears. When a part of Mission 1 starts, the game works out the flight paths of the whole enemy fleet at once: hundreds of curved paths, each measured in 1,000 small steps. That made one frame take 85–114 ms, a clearly visible freeze, at the same moments every time. That calculation now runs as native PC code that does exactly the same maths, so results are identical. In checks, 2,000 paths matched the game's own calculation bit for bit. The longest frames at those moments are now 34–40 ms, at most a single skipped frame.
- On CPUs with FMA instructions (almost every PC since 2013, and the Steam Deck), it uses them for extra speed; other CPUs use a slightly slower path with the same results.
Everything from earlier releases is included: the shader cache (v0.2.5), the experimental 60 fps option (v0.2.3/v0.2.4) and vertex work on more CPU cores (v0.2.2).
Downloads
| Platform | File |
|---|---|
| Windows 10/11, x64 | sfa-recomp-windows-x64.zip |
| Linux x86_64 / Steam Deck | sfa-recomp-linux-x86_64.tar.gz |
Getting started
- Extract the package to a folder. When updating, extract over the old folder: your saves and settings in
user/are kept. - Put your disc image next to the program, or pick it with Browse… on the start screen.
- Run
sfa.exe(Windows) orsfa.sh(Linux; starts fullscreen). On the Steam Deck, addsfa.shto Steam as a non-Steam game to play in Game Mode. - Press Play (START on a controller). Frame rate: Original gives the smoothest result on most hardware; 60 fps is experimental.
Known issues
- The shader cache only helps from the second time you see an effect, so the first playthrough of each area can still have short hitches.
- Short pauses can still happen around loading screens.
- The 60 fps option is experimental: on-foot missions often can't hold 60 and drop back to 30.
- Not tested yet: the scenes after each boss in automated runs (the final boss of Mission 1 has been beaten in real play), the ending, VS mode and the bonus games.
Reporting problems
If the game stops or crashes, it writes a report to user/crash.log next to the program. When it isn't started from a terminal (Steam, file manager, Game Mode), the full output of the last run is in user/sfa.log. Please attach both to an issue.
v0.2.5 — shader cache
Fewer hitches: the game now remembers its graphics effects between sessions.
You need your own disc image. No game data is included. Dump your disc to an .iso or .gcm (compressed formats such as RVZ need converting to ISO first, e.g. in Dolphin).
What's new since v0.2.4
- Shader cache. The first time the game shows an effect, the PC has to prepare its shader, which can cause a short hitch. When several appear at once, for example 28 at once when Mission 1's effects first appear, that's a noticeable stutter. Those effects are now saved to
user/shaders.bin. On later starts they're prepared in the background during the logos and menus, so they're ready before you need them. In testing, the second run through Mission 1 prepared nothing during play. - The file fills in as you play, is small (about 9 KB after Mission 1), and is safe to delete.
Everything from earlier releases is included: the experimental 60 fps option (v0.2.3/v0.2.4) and vertex work on more CPU cores (v0.2.2).
Downloads
| Platform | File |
|---|---|
| Windows 10/11, x64 | sfa-recomp-windows-x64.zip |
| Linux x86_64 / Steam Deck | sfa-recomp-linux-x86_64.tar.gz |
Getting started
- Extract the package to a folder. When updating, extract over the old folder: your saves and settings in
user/are kept. - Put your disc image next to the program, or pick it with Browse… on the start screen.
- Run
sfa.exe(Windows) orsfa.sh(Linux; starts fullscreen). On the Steam Deck, addsfa.shto Steam as a non-Steam game to play in Game Mode. - Press Play (START on a controller). Frame rate: Original gives the smoothest result on most hardware; 60 fps is experimental.
Known issues
- The shader cache only helps from the second time you see an effect. The first playthrough of each area can still have short hitches.
- A short hitch can still happen when many new textures load at once, and around loading screens.
- The 60 fps option is experimental: on-foot missions often can't hold 60 and drop back to 30.
- Not tested yet: the scenes after each boss in automated runs (the final boss of Mission 1 has been beaten in real play), the ending, VS mode and the bonus games.
Reporting problems
If the game stops or crashes, it writes a report to user/crash.log next to the program. When it isn't started from a terminal (Steam, file manager, Game Mode), the full output of the last run is in user/sfa.log. Please attach both to an issue.
v0.2.4 — 60 fps option fix
A small fix to the 60 fps option, and better news about on-foot missions.
You need your own disc image. No game data is included. Dump your disc to an .iso or .gcm (compressed formats such as RVZ need converting to ISO first, e.g. in Dolphin).
What's new since v0.2.3
- 60 fps option: no needless fallback at the start of a stage. The option checks whether your PC keeps up, and if not, returns to the game's own frame rate for a while (so the game never runs in slow motion). It used to count the very first second of play, where loading hitches and new effects briefly slow things down, and then gave up on 60 for 20 seconds right at the start. It now starts checking 5 seconds into play.
- On-foot missions can run at 60. v0.2.3's notes said on-foot missions need a fast CPU. That was wrong: those measurements were taken while the test laptop was busy with other work. Measured again on a quiet machine, Mission 2 ran at 59–60 fps with the option on for most of a 2-minute test, on a laptop i5 (i5-1135G7). The game's own logic uses only about a quarter of the CPU at 30 fps. The Steam Deck's CPU is slower, so it may still fall back to 30 at times there.
Everything from v0.2.3 and v0.2.2 is included: the 60 fps option and vertex work on more CPU cores.
Downloads
| Platform | File |
|---|---|
| Windows 10/11, x64 | sfa-recomp-windows-x64.zip |
| Linux x86_64 / Steam Deck | sfa-recomp-linux-x86_64.tar.gz |
Getting started
- Extract the package to a folder. When updating, extract over the old folder: your saves and settings in
user/are kept. - Put your disc image next to the program, or pick it with Browse… on the start screen.
- Run
sfa.exe(Windows) orsfa.sh(Linux; starts fullscreen). On the Steam Deck, addsfa.shto Steam as a non-Steam game to play in Game Mode. - Choose Frame rate: 60 fps on the start screen if you like, then press Play (START on a controller).
Known issues
- The 60 fps option is experimental. It has been tested in Mission 2 (on foot), not yet across the whole game or on the Steam Deck. In one stretch of the test, the game itself dropped to 30 fps for a few seconds without the option's fallback being involved; this is being looked into.
- Not tested yet: the scenes after each boss in automated runs (the final boss of Mission 1 has been beaten in real play), the ending, VS mode and the bonus games.
- The first time a new effect appears there can be a short hitch while its shader compiles.
Reporting problems
If the game stops or crashes, it writes a report to user/crash.log next to the program. When it isn't started from a terminal (Steam, file manager, Game Mode), the full output of the last run is in user/sfa.log. Please attach both to an issue.
v0.2.3 — experimental 60 fps option
An experimental 60 fps option.
You need your own disc image. No game data is included. Dump your disc to an .iso or .gcm (compressed formats such as RVZ need converting to ISO first, e.g. in Dolphin).
What's new since v0.2.2
- Frame rate: Original or 60 fps. The start screen has a new switch. On the GameCube, flight stages run at 60 fps while on-foot missions and in-engine cutscenes run at 30. With 60 fps on, the game runs at 60 everywhere.
- Game speed stays correct. The game moves its clock forward a fixed step each frame, and the option switches it to the 60 fps step. In testing the clock advanced exactly 1/60 s per frame, and cutscenes, subtitles and the HUD looked right.
- No slow motion. If your PC can't keep up (below about 54 fps for 2 seconds of play), the game goes back to its own frame rate for a while and then tries 60 again. The wait gets longer each time it fails, so it doesn't keep switching back and forth.
- Correction (see v0.2.4): an earlier version of these notes said on-foot missions need a fast CPU. That was measured while the test laptop was busy with other work. On a quiet machine, Mission 2 holds 60 fps on a laptop i5; the Steam Deck may still fall back to 30 at times.
- The option is off by default and saved with your other settings. It also works when the start screen is skipped;
SFA_60FPS=1orSFA_60FPS=0as a launch option overrides it.
Everything from v0.2.2 is included: vertex work on more CPU cores, for smoother busy scenes on slower CPUs.
Downloads
| Platform | File |
|---|---|
| Windows 10/11, x64 | sfa-recomp-windows-x64.zip |
| Linux x86_64 / Steam Deck | sfa-recomp-linux-x86_64.tar.gz |
Getting started
- Extract the package to a folder. When updating, extract over the old folder: your saves and settings in
user/are kept. - Put your disc image next to the program, or pick it with Browse… on the start screen.
- Run
sfa.exe(Windows) orsfa.sh(Linux; starts fullscreen). On the Steam Deck, addsfa.shto Steam as a non-Steam game to play in Game Mode. - Choose a frame rate if you like, then press Play (START on a controller).
Known issues
- The 60 fps option is experimental. It has been tested in Mission 2 (on foot), not yet across the whole game or on the Steam Deck.
- Not tested yet: the scenes after each boss in automated runs (the final boss of Mission 1 has been beaten in real play), the ending, VS mode and the bonus games.
- The first time a new effect appears there can be a short hitch while its shader compiles.
Reporting problems
If the game stops or crashes, it writes a report to user/crash.log next to the program. When it isn't started from a terminal (Steam, file manager, Game Mode), the full output of the last run is in user/sfa.log. Please attach both to an issue.
v0.2.2 — graphics work on more cores
Smoother busy scenes on slower CPUs such as the Steam Deck's.
You need your own disc image. No game data is included. Dump your disc to an .iso or .gcm (compressed formats such as RVZ need converting to ISO first, e.g. in Dolphin).
What's new since v0.2.1
- Graphics work spread over more CPU cores. In busy scenes the slowest part was the thread that turns the game's drawing commands into PC graphics, mostly reading and positioning vertices: Mission 10's opening flight has about 9,000 objects and 43,000 vertices a frame. That vertex work now runs on up to 4 extra threads. In Mission 10 the busiest thread's time per frame dropped by 40–60%. Where frames dropped below 60 fps on the Deck in heavy scenes, this should help.
- Same picture. Each vertex is calculated exactly as before. In checked test runs (Missions 1, 4 and 10), about 700 million vertices were compared against the old single-thread result with no differences.
- Whole game checked. Automated runs played every story stage of all ten missions, including each mission's last part, on Windows and Linux with no crashes.
- Note: Mission 10's first 40 seconds (the story scene where Star Wolf joins) run at 30 fps on purpose: the game draws its cutscenes at that rate. Gameplay is 60.
Downloads
| Platform | File |
|---|---|
| Windows 10/11, x64 | sfa-recomp-windows-x64.zip |
| Linux x86_64 / Steam Deck | sfa-recomp-linux-x86_64.tar.gz |
Getting started
- Extract the package to a folder. When updating, extract over the old folder: your saves and settings in
user/are kept. - Put your disc image next to the program, or pick it with Browse… on the start screen.
- Run
sfa.exe(Windows) orsfa.sh(Linux; starts fullscreen). On the Steam Deck, addsfa.shto Steam as a non-Steam game to play in Game Mode. - Press Play (START on a controller).
Known issues
- Not yet tested on the Steam Deck itself. If anything looks wrong, setting the launch option
SFA_GX_WORKERS=0 %command%turns the extra threads off, andSFA_GX_DEFER=0 %command%goes back to the old code path entirely. - Not tested yet: the scenes after each boss in automated runs (the final boss of Mission 1 has been beaten in real play), the ending, VS mode and the bonus games.
- The first time a new effect appears there can be a short hitch while its shader compiles.
Reporting problems
If the game stops or crashes, it writes a report to user/crash.log next to the program. When it isn't started from a terminal (Steam, file manager, Game Mode), the full output of the last run is in user/sfa.log. Please attach both to an issue.
v0.2.1 — final boss fix
A fix for Mission 1's final boss, and a speed-up.
You need your own disc image. No game data is included. Dump your disc to an .iso or .gcm (compressed formats such as RVZ need converting to ISO first, e.g. in Dolphin).
What's fixed since v0.2.0
- Mission 1's final boss no longer disappears after you destroy its wings. On the GameCube, tiny floating-point results are rounded to exactly zero: the game's startup code switches the processor into that mode, and the game relies on it. The recompiled game didn't do the same. When the boss reached the point it was flying to, the leftover distance stayed a tiny nonzero number, its position overflowed to infinity, and it couldn't be drawn. The debris it sheds then piled up by the thousand. The PC's processor now runs in the matching mode (as Dolphin does). The fix covers all of the game's math, not only this boss.
- Faster: very tiny numbers are slow for PC processors, and they now become zero. Mission 1's first stage ran about 50% faster in a like-for-like test.
Downloads
| Platform | File |
|---|---|
| Windows 10/11, x64 | sfa-recomp-windows-x64.zip |
| Linux x86_64 / Steam Deck | sfa-recomp-linux-x86_64.tar.gz |
Getting started
- Extract the package to a folder. When updating, extract over the old folder: your saves and settings in
user/are kept. - Put your disc image next to the program, or pick it with Browse… on the start screen.
- Run
sfa.exe(Windows) orsfa.sh(Linux; starts fullscreen). On the Steam Deck, addsfa.shto Steam as a non-Steam game to play in Game Mode. - Press Play (START on a controller).
Known issues
- The final boss fix was verified in automated fights (the boss stays visible and fighting after losing its wings), not yet in a full playthrough to the end of the fight.
- Not tested yet: later parts and bosses of missions 2–10, VS mode and the bonus games.
- On the Steam Deck, the busiest Mission 1 scenes may dip below 60 fps.
- The first time a new effect appears there can be a short hitch while its shader compiles.
Reporting problems
If the game stops or crashes, it writes a report to user/crash.log next to the program. When it isn't started from a terminal (Steam, file manager, Game Mode), the full output of the last run is in user/sfa.log. Please attach both to an issue.