EmblemWeave 0.1.27
CMake is found the way the build finds it, .nx archives play again, and an SDK unzipped whole is found one folder down
Install
- Download EmblemWeave-v0.1.27-windows-x64.zip below and unzip it into a folder of its own.
- Run
EmblemWeave.exe. - On Game Setup, choose your dump. On Overview, press Build the game (once), then Play.
sha256 of the zip: 90c5e12773e19b1f97f570b498b292c4f1b01b671a8731be0fd348018fce3ac5
CMake installed, still "not found on PATH" (#30)
The Requirements page and the build's own check asked two different questions: deps looked along the PATH the build gets
(which adds C:\Program Files\CMake\bin, winget's Links folder and the other tool folders), while the toolchain probe ran a bare
cmake --version with the launcher's own PATH only. A CMake installed where the launcher does not put PATH was therefore reported
as installed by Requirements and as missing by the build, on the same screen.
Every version probe now runs with the same PATH every build step gets, so the two agree. tool_path is also computed once per
session, because each probe used to re-run clang-cl --version through find_clang.
.nx archives (#28)
The .nx reader was still there, but it handed the archive itself to the engine as the RomFS, which worked with the older engine.
Its replacement reads a .nup and a folder, not NXFormat, so a .nx was accepted by the launcher and then failed at the RomFS.
An .nx now writes its RomFS out once, into work/nx/<title>-v<version>/romfs, records the source stamp beside it, and hands
that folder over, the way a .nsp is unpacked. Detect reports the copy with progress, a cancelled copy is removed rather than left
half-written, and the RomFS check says the tree was written out instead of "read in place".
Upscalers in an SDK's own layout (#29)
Players who unzipped a whole SDK into upscalers\fsr kept getting "not recognised", because the FidelityFX release keeps its DLLs
in bin\, one folder down, and the launcher looked only at the top folder. Each vendor folder is now also searched one level deep
(bin, x64, the archive's own name), for FSR, Streamline and XeSS alike, and the folder reported on Graphics is the one that
actually holds the files.
Verified
cargo build --releaseandcargo test -p emblemweave: 119 passed, 0 failed.--check-toolchainand--print-requirementsboth report CMake 4.4.4 atC:\Program Files\CMake\bin\cmake.exewith the new
probe, and the Requirements page opens without an error.- The Graphics section was seen on the running launcher with the DLLs one level down:
FSR 3.1 found in …\play\upscalers\fsr\bin. - Not checked: a real
.nxarchive (none here), and a CMake installed somewhere new: the PATH it now shares with the build is the
onedepsalready reported.