github XiONDiGiTaL/EmblemWeave v0.1.39
EmblemWeave 0.1.39

latest releases: v0.1.41, v0.1.40
3 days ago

EmblemWeave 0.1.39

Standard mode, DLC discovery, special-character build paths, and an updater that keeps the built game.

Install

  1. Download EmblemWeave-v0.1.39-windows-x64.zip below and unzip it into a folder of its own.
  2. Run EmblemWeave.exe.
  3. On Game Setup, choose your dump. On Overview, press Build the game (once), then Play.

sha256 of the zip: 77cd672944e96fc7cae006089036333cd773fb00558f88fac69a3e4956a6130f

sha256 of EmblemWeave-v0.1.39-shader-translator-linux-x64.tar.gz (the shader translator for Linux, not needed on Windows): 1eb3c089c43a16557978fe6154f3e0dfe39df039fabf50f1b38bbf4f01151036

The Linux tarball is built by CI on Linux, so its executable bit is recorded. Extract it in engine/fefw-recomp/tools/shaders/prebuilt/ and run ./linux-x64/spirv_harness.

Launcher

  • Standard mode is the new default. New installations start with Play, setup, saves, mods, everyday graphics and audio,
    controls, requirements, troubleshooting and help. Build details, diagnostics, logs and engine internals move behind
    Advanced mode, which is one switch on Appearance; a direct Build details, Diagnostics or Game Log link reveals it
    automatically. The modes share the same installation and configuration, so switching never moves files, changes saves or
    invalidates a build; the choice is remembered across restarts, and a configuration from an older release stays in Advanced
    so existing users do not suddenly lose pages.
  • Graphics has a Standard view built on the same settings. Performance, Balanced and Quality presets set render scale,
    FSR 1.0 or native output, sharpening, VSync and a frame cap without exposing upscaler-DLL paths, frame generation, ReShade
    or shader-compiler tuning. Advanced mode restores the full page unchanged, including every existing upscaler and cache
    control. A current value chosen in Advanced remains visible when it is not one of Standard's two upscalers.
  • A build folder containing &, (, % and the other cmd.exe separators is built through a temporary junction.
    The real project, saves and outputs stay where they are; the build reaches them through a folder name in the temporary
    folder that cmd.exe cannot split. A short 8.3 name alone was not enough, because CMake writes an absolute
    WORKING_DIRECTORY and target folder back into their long spelling. The junction is removed when the build ends, and
    when one cannot be made the build stops with the character, the affected path and the remedy instead of letting ninja
    report a truncated CMakeFiles\G_\Games\PC_Ports_ path.
  • Requirements explains updates and existing builds. It names the settings/saves/mods folder, the engine/build folder
    and the game's run folder, and says that updates keep them and that Build reuses an existing build unless the engine
    revision, toolchain or build settings changed. That is the practical answer to "do I need to rebuild the game?"
  • Dumped add-on content is found and used. Game Setup scans dlc/<title id>/romfs beside the ExeFS, RomFS or game
    root (or an explicit path), shows the packs on Setup and Overview, and writes the folder as [aoc] dir so the engine's
    aoc:u and OpenDataStorageByDataId serve them. An empty value is written when no packs exist. Add-on packages
    inside a .nup are unpacked once into a managed dlc/ folder beside the copied ExeFS, with byte progress and
    cancellation; a marker reuses a finished unpack, and packs outside this game's add-on title-id block are ignored.
  • Updates install the release, not only the executable. Overview now says Update available when a newer release exists,
    with the same Update now action on the notification and on About. The updater writes the new launcher, docs and engine
    sources over this install while keeping data, the built game, the fetched tools and third-party sources; portable.txt is
    never changed, so the storage mode stays as it was. If the running executable cannot be replaced, the old launcher starts
    and logs\update.log records why. An update from an older launcher that moved only its executable is finished from the
    download cache on first start, so those engine sources catch up without another download.
  • Import from folder… now adapts to the folder it is given. The save folder, its account folder, an install folder above
    either, the title's own folder, a whole NAND save tree, and the contents of 000 without their parent all land in
    account/DEFAULT_USER/000, where the game reads them. A folder that holds no save is refused before the current save is
    touched, and an account folder whose save an older import left nested is found again. Import profile on the Saves page
    uses the same resolver, so an old save folder or a flat 000 folder becomes a profile that loads instead of one that fails
    verification later.
  • The build toolchain is carried: clang-cl, lld-link, CMake, Ninja and an embeddable Python are downloaded into
    engine/fefw-recomp/tools/bin on first run (or with EmblemWeave.exe --fetch-tools), each archive checked against a
    pinned SHA-256 before it is unpacked. The Requirements page reports those four as Carried, and every probe and
    build step finds them before anything installed on the PC.

Engine

  • The frame rate counter can be hidden without a keyboard: hold one button of a pad pair and press the other. [fps] combo
    picks the pair — l3_r3 (default), minus_plus for a handheld's Minus and Plus, shoulders, or none. The F1 page
    lists it under the counter's hotkey. Like F2, the press never reaches the game.
  • nxrt/platform.h gained the host services (memory, threads, synchronisation, time, files) with a Windows and a POSIX
    backend, and the time subsystem moved behind it — phase 2 of docs/LINUX.md. On Windows the tick and the sleep are the
    same calls as before.

ReShade

  • Four presets and three filter shaders ship in engine/fefw-recomp/reshade/: Vivid (a little more saturation and
    contrast, deeper blacks), Bright (the same lift, lighter overall), Game Boy (four-shade DMG palette with ordered
    dithering) and Retro CRT (scanlines, aperture grille, glow, vignette). The effects are self-contained: they do not
    include ReShade.fxh, so they compile on a bare ReShade install with no shader repository.
  • The Graphics page's ReShade drawer has a preset picker. Applying one copies the shaders and the preset beside
    fefw.exe, points ReShade.ini's PresetPath at it and registers every preset for ReShade's own shortcuts, so F3
    and F4 step through the looks in game and Home opens ReShade's overlay. EmblemWeave.exe --apply-preset <name>
    does the same from a console.

Don't miss a new EmblemWeave release

NewReleases is sending notifications on new releases.