STATIC RECOMPILATION / XiONDiGiTaL

EmblemWeave

EmblemWeave is a Windows recompilation launcher for Fire Emblem: Fortune’s Weave, continuing the preserved fefw-recomp engine with mod management, save profiles and in-game settings.

Latest release: v0.1.41Last checked:

The overview

XiØN’s launcher builds and runs the game from your own dump using the bundled fefw-recomp baseline, which translates to C++ and renders with Vulkan. The reviewed historical README and UPSTREAM document describe Goldoire’s original repository removal and Obersteinn’s preservation of its 0.2.0 package. fefw-recomp has since resumed updates separately at metrist38/fefw-recomp. EmblemWeave’s separate Rust runtime is still being developed and does not yet render the game’s geometry. Its reported playable path uses the baseline engine.

System and game requirements

  • Windows 10 / 11 64-bit, Vulkan 1.3 driver and an x86-64 CPU. The README lists 8 GB RAM minimum and 16 GB recommended, about 30 GB for game data plus additional build space. Check the baseline engine’s CPU checks rather than assuming every older processor will work.
  • The tested manifest is for game update 131072, main build db93b0125f48…. Game Setup validates ExeFS hashes. A different build can be recompiled according to the README, but that does not establish runtime compatibility.
  • Use your own .nup or extracted ExeFS/RomFS. The README also describes .nx and plaintext .nsp repacks; encrypted retail NSP files are not decrypted or accepted as plaintext. Prefer the documented tested input if a package format fails.
  • Building requires Visual Studio 2022+ C++ tools and Windows SDK, LLVM 23, CMake 3.25+, Ninja, NASM, Git, PowerShell 7 and uv. Decode uses Python and zbic. The release includes a self-contained shader translator, so the normal ZIP does not require the .NET SDK.

Features described by the developer

  • Save profiles, backup-aware profile switching, emulator save imports and a save editor for supported fields. Back up saves before editing or importing.
  • RomFS mod management from GameBanana, archives or folders. ExeFS-only code mods are recognized but not installed. Atmosphere data cheats and compatible Cheat Engine tables are documented; instruction patches do not work on recompiled code.
  • F10 or Back + RB opens EmblemWeave’s overlay; the baseline engine’s F1 menu remains available. Display controls include resolution, render scale, aspect ratio and frame cap. FSR 3.1 and DLSS/DLAA require separate vendor DLLs; FSR 4 is not offered.
  • Live build progress, game log and diagnostics. --check-toolchain checks dependencies and --verify-log extracts the first build error. Some quality, shader and per-channel audio options are placeholders pending the independent renderer/mixer.

Getting started

  1. Download EmblemWeave-<version>-windows-x64.zip from the project releases, extract the whole folder and run EmblemWeave.exe. The separate shader-translator-linux-x64 archive is not needed for Windows.

  2. In Game Setup select your own package or folder, validate the dump and decode main where prompted. The original game folder is read-only. Confirm the required toolchain on the Requirements page.

  3. On Overview choose Build the game, let the baseline engine compile and prepare shaders, then choose Play. The first build takes time; later builds reuse unchanged work.

  4. Keep backups of %APPDATA%/EmblemWeave/save before importing or editing. Settings are in config.json, build work in work/, the play folder holds fefw.ini and fefw.log, and task logs live under logs/.

EmblemWeave — Downloads

Find maintainer-hosted files, package selection advice and recent releases on the dedicated download page.

Choose a package and check releases

Moving from fefw-recomp

The original Goldoire repository was removed; fefw-recomp now receives separate updates at metrist38/fefw-recomp. If you choose to move to EmblemWeave, follow this guide. Keep your previous install and saves backed up, extract EmblemWeave into a separate folder, and build from your own dump. The old tool used save/ beside its launcher; EmblemWeave uses %APPDATA%/EmblemWeave/save. Use the Saves page’s folder import where applicable and confirm the correct profile before playing. No automatic in-place upgrade or universal save compatibility is promised.

View source

What works now and what is still in development

EmblemWeave — What works now and what is still in development
ComponentDocumented status
Baseline fefw-recomp engineBuilds fefw.exe and provides the reported playable Vulkan/audio/movie path.
Independent Rust runtimeRuns native code and presentation/command infrastructure, but game geometry is not yet drawn and voices are not mixed to speakers.
Linux release archiveShader translator only. No native Linux launcher/game package is established by that asset.
View source

Steam Deck: documented Proton route

The Steam Deck guide says to build and test once on Windows, copy the complete launcher/engine build plus play and save folders, then configure Proton paths. It explicitly says the maintainer has not tested this recipe on a Deck. Build the game and dependency installation cannot run there. Treat this as an unverified route, not native Linux support.

View source

Recompilation questions

Is EmblemWeave a continuation of fefw-recomp?

EmblemWeave wraps and continues the preserved fefw-recomp engine. Its historical README and UPSTREAM notes describe the original repository removal and preservation of the 0.2.0 package. fefw-recomp has since resumed updates at metrist38/fefw-recomp. EmblemWeave is XiØN’s separate launcher project, with its own releases.

Does EmblemWeave include the game or guarantee 60 FPS?

No. Build from your own legally obtained dump. About 60 FPS with sound and movies on an RX 7900 XT is the developer’s report, not a Switch2e test or a promise for other hardware. The current playable path uses the baseline engine.

Is the Linux shader-translator download a Linux launcher?

No. The user launcher is Windows x64. The Linux asset only contains the shader translator. The Steam Deck guide describes building on Windows and running through Proton, with a maintainer-untested procedure.

Sources & review

Reviewed · README 6a2613e

COMMUNITY

Comments

Share a question, correction or experience with this project.

Search by game, project or maintainer. Use Tab to choose a result.