EmblemWeave: one zip, nine build tools, your dump
Latest release
v0.1.41Published 2026-11-20· 2 packages below
Copies a prompt your AI agent can run to install EmblemWeave.
Which package should I choose?
The release zip carries the launcher, docs, engine sources and the bundled shader translator. A second Linux tar.gz ships the translator for Linux builds. Unzip anywhere and run EmblemWeave.exe: fresh installs are portable by default, keeping settings, saves, builds and logs in data beside the executable, and the game folder is never written to. The game itself compiles on your PC after Game Setup, which is why the zip is small.
| Package | Architecture | Size |
|---|---|---|
| EmblemWeave-v0.1.41-shader-translator-linux-x64.tar.gz ↗ | x86_64 | 32.6 MB |
| EmblemWeave-v0.1.41-windows-x64.zip ↗ | x86_64 | 89.0 MB |
What this build needs
Windows 10 or 11 64-bit, a Vulkan 1.3 GPU, 8 GB of memory (16 recommended) and about 30 GB of disk for the decoded game data. Building needs nine pieces: Visual Studio C++ tools, the Windows 10/11 SDK, LLVM, CMake, Ninja, Python with zbic, a C compiler, and the bundled translator. The launcher installs seven of them itself. The SDK is the one to add by hand when an existing Build Tools install lacks it. A CPU without SSE4.2, POPCNT or CMPXCHG16B is refused with a message naming the missing features.
Getting started
Read the docs
Upstream maintains pages for system requirements, the Linux plan and known limitations, linked from the repository.
Get the launcher
Download the Windows x64 release from the upstream GitHub releases page.
Provide your own game
Point the launcher at your own legally obtained dump. The project states it only ever reads your files.
Troubleshoot
The development status page documents playable-build evidence and known limitations, and the repository carries guidance for when the build or the game stops.
Common problems
-
Setup stops at eight of nine tools
The Windows 10/11 SDK is the only entry the launcher cannot add itself. A fresh install through the launcher includes it. An existing install may not, so add Windows 11 SDK under Individual components in Visual Studio Installer and press Check again.
-
The window closes at once, or the picture stays black while sound plays
Usually the Vulkan driver or an incomplete shader cache. Read %APPDATA%\EmblemWeave\play\fefw.log, update the driver, and press Build the game to translate the missing shaders.
-
GPU DEVICE LOST in the first seconds on Intel graphics
Two known driver paths cause it and the launcher guards both. Install the newest Intel driver and rebuild the game afterward, since a launcher update alone does not replace the built game.
-
The build fails on a path with an ampersand or an apostrophe
Releases from 0.1.39 build through a temporary junction for such paths. Update, or move the folder somewhere plain.
-
Python errors naming python311.dll conflicts
A machine-wide PYTHONPATH or PYTHONHOME variable leaks into the build. Current releases clear both themselves. Older ones need them removed from the user environment.
How it differs
EmblemWeave continues the fefw-recomp engine as one application: recompilation, mod management, a save editor and an in-game menu under a single launcher, while metrist38's fefw-recomp keeps the original flow. Its docs publish the deepest toolchain guidance of the entries here, down to per-message fixes for the compiler chain.
Recent upstream releases
- EmblemWeave 0.1.41 ↗ Published 2026-11-20 · 2 packages
See every release on the upstream page ↗
Last checked 2026-11-22. Release data fetched 2026-11-22. A release sync refreshes metadata from upstream; it does not re-verify compatibility.
Download FAQ
Which dump shapes can I point it at?
A .nup, .nx, plaintext .nsp or plaintext .xci package, or an extracted exefs and romfs folder. Retail encrypted packages are refused with the first unreadable NCA named. The project neither ships nor asks for keys.
Where do the upscaler files come from?
The AMD, NVIDIA and Intel files cannot be shipped, so the launcher downloads them on request or finds ones you already have under Graphics > Upscaler files. Without them the game falls back to its own temporal upscaler.
Can this PC build the game at all?
Run EmblemWeave.exe --check-toolchain: exit code 0 means the build can start, 1 names the missing piece, and 2 means the pieces disagree, usually one install's headers with another's libraries.
Is EmblemWeave a continuation of fefw-recomp?
The engine is. The README states the launcher continues from a snapshot of the fefw-recomp engine, which it describes as no longer online upstream. The launcher around it is a separate project maintained by XiONDiGiTaL, with its own release line, mod management and in-game enhancement menus documented on its upstream pages.
Before installing
- Use the launcher's own updater: it keeps the built game, fetched tools and the data folder, and records the build as carried forward.
- Never copy a lone fefw.exe into another engine folder
- the executable, engine sources and fetched tools belong together, and mixing releases is what the Repair card exists to fix.
- Game build update 131072 is the tested one
- other builds recompile but are unverified.