winlator-nightly-wcp: nightly WCP packages for Winlator

A nightly repackaging job, not a fork of the emulator

What this repository is, precisely, is a build pipeline that turns upstream components into WCP packages for Android emulation, aimed at Winlator, Mobox and similar tools. The builds are checked and generated automatically every night at 9:00 PM CST, and only when new updates exist in the official repositories, so an unchanged upstream produces no new release. The catalog Winlator reads is a separate artefact, contents.json, refreshed at 12:00 AM CST. The README is also candid about its own status: it points at another repository as the place where this one has been updated and continued, the WinNative-components project, and states that this repository is still maintained while small bugs have been corrected in the newer one. That makes it worth treating as a mirror with a successor rather than as the place to file issues.

Winlator reads a raw URL, not a file you download

There is no installer to run. The whole integration is one setting. In Winlator you open Settings, go to Downloadable Content URL, and paste a raw file URL:

https://raw.githubusercontent.com/Xnick417x/winlator-nightly-wcp/refs/heads/main/contents.json

Winlator fetches that file, reads the catalog and offers the packages from there. The driver manager is wired the same way, by pasting the main repository URL instead. One failure mode is documented and it is a display problem rather than a network one: if the contents do not show up, turn the phone to landscape view. Two catalog files sit at the repository root, contents.json and default.json, which is consistent with a machine-generated index rather than a hand-maintained release page.

Almost every component ships in a standard and an ARM64EC flavour

The download table is organised by component and variant, and the variant is part of the file name rather than a download option. DXVK is published as a GPLAsync build at 3.0.2 and an ARM64EC build at the same version, in two separate releases. VKD3D-Proton is published as a standard build and an ARM64EC build at 3.0.1. FEXCore is offered for ARM64EC only, at a 2609 version stamped with a commit hash. Box64 has a standard build and a non-standard bionic build that is explicitly labelled work in progress, both at 0.4.5 but from different upstream commits, and WOWBox64 is a separate component at 0.4.5. There is also a DXVK pre-regress pair, standard and ARM64EC, sitting at 3.0.1 while the main DXVK nightlies are at 3.0.2, which is the channel to use when you want the older line.

Nightly tags carry a commit hash, weekly bundles do not

Release naming is the thing to learn first, because every download link encodes it. Nightly tags are named for the component and the upstream commit, such as dxvk-nightly-8dd0c490, vkd3d-nightly-0894a2d5, fex-nightly-2609-0df84d384, box64-nightly-0.4.5-970ba6225, bionic-box64-nightly-0.4.5-b9fd03e3a and wowbox64-nightly-0.4.5-970ba6225, and the attached files repeat the upstream version with the same hash, for example Vkd3d-3.0.1-0894a2d5.wcp. That is what makes a nightly traceable back to a specific upstream commit. Against those, the weekly channel ships one all-in-one archive, a 7z file under a tag named for the date, currently Weekly-2026-09-25. Each row also carries a history link built as a release search with exclusion filters, because a plain release list would mix the standard, ARM64EC, bionic, pre-regress and weekly variants together.

Stable builds live under their own release tags

Nightlies are only half the catalogue. A separate table points at stable releases, and each component has its own tag: Stable-Dxvk, Stable-Arm64ec-Dxvk, Stable-VKD3D, Stable-arm64ec-VKD3D, Stable-FEX, Stable-Box64, Stable-wowbox64, and Sarek for DXVK Sarek. Two more tags carry layer bundles rather than components: Wine for the Wine layers built against bionic, and GameNative for the Proton layers built against bionic, both linked as asset downloads from their tags rather than as individual files. Two entries in the drivers section are promises rather than downloads, with Qualcomm and stable Turnip both marked coming soon. So the practical read is that the stable side covers the DXVK, VKD3D, FEXCore and Box64 families plus Sarek, while the driver layer is the part that is not finished.

Turnip is the one component delivered as a zip

Everything else in the main download table is a .wcp package. Turnip is different: it ships as zip archives, and it is split by GPU generation rather than by standard and ARM64EC. The a6xx and a7xx build is Turnip-26.2.0-b41cd59.zip, and the experimental a8xx build is Turnip-26.2.0-b41cd59-A8xx.zip from the same upstream commit. Both are listed under a nightly-Turnip release tag with their own history link, so the two variants are kept apart in the same way as the standard and ARM64EC pairs elsewhere. If you are looking for a specific driver generation, that suffix is the thing to check, since the version numbers are identical and only the archive name differs.

The tree is a catalog, a profile folder and a patch folder

The repository itself is tiny, which fits a build job. At the root there is contents.json and default.json for the catalog, a logo image, mesa_hash.txt for the Mesa component's hashing, a Profiles/ directory, a patch/ directory, and .github/ holding the workflows. Those workflows are the build schedule made visible: separate ones for the DXVK GPLAsync nightly, for VKD3D including arm, for FEXCore, for Box64 together with WOWBox64, and one for the bionic Box64 build that the status list marks as work in progress. One small thing is worth flagging if you are checking the licensing: the licence file at the root is spelled LISCENSE rather than LICENSE. The primary language is recorded as Shell, and the last push is 30 September 2026, the same morning the WOWBox64, VKD3D and VKD3D ARM64EC nightlies were published.

Editorial conclusion

This repository fits someone running Winlator or a similar Android emulator who wants the translation and graphics components rebuilt nightly instead of waiting for an upstream release, and who is comfortable pasting a raw JSON URL into an app setting. Three things to know before you point Winlator at it. The builds are automated, so a bad night upstream reaches you the same morning, and the per-component history links exist because variants are easy to mix up. The README also names a successor repository, WinNative-components, and says small bugs are corrected there, so new installations are better served by that project. And two of the advertised components are not there yet, with Qualcomm drivers and stable Turnip builds both marked coming soon. The last push is 30 September 2026, with the WOWBox64, VKD3D and VKD3D ARM64EC nightlies published that morning.

Frequently asked questions

Official sources

1. Official README
2. Project repository
3. Release notes