Savage Wind Without AVX2: Older CPU Compatible Mode
Let setup choose compatible mode automatically. This is for processors with SSE4.2 but no AVX2 or FMA.
On this page
This mode is slower because your processor has to do extra work.
Use Automatic Compatible Mode
- Check that your CPU supports SSE4.2, your graphics driver supports Vulkan 1.3 and about 35 GB is free for preparation; use System Requirements for the full requirements.
- For an existing Alpha 2 installation, follow the Alpha 3 upgrade: use a new program folder, set up the game files again and carry over your backed-up save afterward.
- Let the standard package finish building the game code. Setup chooses the processor target automatically: AVX2, FMA and BMI2 use the faster target; other supported processors get x86-64-v2 compatible mode.
Earlier requirements and processor selection
Early builds stopped at a CPU check; Alpha 2 required AVX2, so older news, screenshots and installation videos can show that requirement. Issue 9, issue 11 and issue 12 include older-CPU requests such as the i5-3470, which has SSE4.2 and AVX1 but lacks AVX2 and hardware FMA.
Compatible mode reproduces the game's multiply-and-add calculations in software with the required rounding on processors without hardware FMA.
The generated code's identity includes its CPU target, so setup can rebuild it when an installation moves between CPU classes.
Check the Selected Mode
- Open Savage Wind Configuration; on Linux use the AppImage's
--configoption from Installation Guide → Linux. - Open the game-files page and look for Game code: compatible mode. Its full label says the CPU lacks AVX2/FMA and this mode is slower.
- Check
savagewind.logfor the selected target; the i5-3470 report recordstarget: compatible (-march=x86-64-v2, no FMA instructions). - For heavily swinging frame rates on that older CPU, choose Video → Frame rate → 30 for steadier play.
i5-3470 performance report conditions
The Alpha 3 test used Windows, an i5-3470 with four cores/four threads, RTX 2060, NVIDIA 617.42, BotW 1.8.2, 1440×900, VSync On, compatible mode and a precompiled shader cache; the run moved from windowed to borderless fullscreen.
The maintainer's log analysis gives 58.9 FPS in shrines and lighter areas, about 44 FPS average outdoors, and 25–35 FPS in the heaviest spots. The GPU mostly waited for the CPU, with software FMA limiting those areas; a 30 FPS cap was recommended for that machine and run.
Report a Build or Launch Failure
Use issue 9. A separate GTX 10-series startup crash can affect the graphics side of the same computer.
- Exact CPU, GPU, driver, operating system and Savage Wind version.
- Mode label and selected target from the failing run's log.
- Whether setup failed to build or the built game failed to start, including the setup result.
Exact CPU, GPU, driver, operating system and Savage Wind version: Mode label and selected target from the failing run's log: Whether setup failed to build or the built game failed to start, including the setup result:
| Project / run | Log to attach |
|---|---|
| Savage Wind / setup or play | savagewind.log from the failing run. |
What's Next
Sources
Checked 2026-10-28.
- Original older-CPU request github.com
- Automatic compatible mode and setup label github.com
- i5-3470 hardware and Alpha 3 report github.com
- Maintainer log analysis and 30 FPS advice github.com
- Released compatible-mode label github.com
Zelda PC Guide