Skip to content

protium v0.4.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 09 Oct 21:11
· 13 commits to main since this release
v0.4.0
This tag was signed with the committer’s verified signature.
Benehiko Alano Terblanche
GPG key ID: 9D1A105736C278C4
Verified
Learn about vigilant mode.
991691c
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Game controllers reach Windows games, over Bluetooth and USB.

Changed

  • The runtime is now wine-11.0-cx26.3-p4, built with the two controller
    patches below. protium runtime install installs it beside the
    wine-11.0-cx26.3-p2 you have and does not make it the default. With no
    default set, every command then stops and asks you to pick a runtime; with
    -p2 set as the default, protium keeps using -p2, without the controller
    fixes. Either way, switch with
    protium use --runtime wine-11.0-cx26.3-p4. A prefix moves between -p2
    and -p4 freely: the new patches change only how controllers are read.
  • protium run now writes two registry values into a prefix that lacks
    them,     Enable SDL=0 and DisableInput=1 under the winebus service. It
    says so the one time it does.

Fixed

  • A paired controller did nothing in a game. Wine saw it and then dropped
    it, because winebus refuses a gamepad over the one path this build has —
    IOHID — unless told SDL and evdev are not there. protium now says so in
    every prefix: when it creates one, and the first time protium run
    launches something in an older one. A prefix that is already running needs
    protium prefix stop once. See docs/controllers.md.
  • An Xbox controller over Bluetooth had no right stick, its stick moved
    the triggers, its triggers did nothing, and its bumpers read as Back and
    Start. patches/0003 reads the layout it uses.
  • An Xbox controller on USB was not a controller at all. macOS hands it
    to Wine as raw Xbox protocol (GIP) packets, which nothing in Wine read.
    patches/0004 decodes them; over USB the controller reports every 8 ms,
    against 30 ms over Bluetooth. Rumble is not implemented.

What is in this download

For Apple silicon Macs:

  • protium-v0.4.0-macos-aarch64.tar.gz: the protium binary and its
    licence texts. This is the one you download.
  • wine-…-macos-x86_64.tar.gz: the Wine runtime this release was built with.
    You need not download it yourself: protium runtime install fetches it and
    installs it only if its SHA-256 matches the one compiled into protium. It
    loads on macOS 15 and later. It was checked on macOS 15 by the workflow that
    built it, and played on macOS 26. Its licence texts are inside it, in
    licenses/.
  • The source archives that runtime was built from: CrossOver's published
    sources, which carry Wine and the libraries it links in, and FreeType,
    GnuTLS, Nettle and GMP.

It does not hold D3DMetal, which comes from Apple's Game Porting Toolkit
and which you download yourself (see the README); protium d3dmetal install
then installs it into the runtime. Apple's D3DMetal 4.0b2 needs macOS 26.4 or
later. Wine Mono, Wine's .NET runtime, is fetched by
protium prefix new when it creates a prefix.

This software is based in part on the work of the Independent JPEG Group.

Verifying this download

Every release is signed by the GitHub Actions workflow that built it. The
signature covers SHA256SUMS, which pins the archive by hash, and travels
beside it as SHA256SUMS.sigstore.json. Download the archive, SHA256SUMS and
SHA256SUMS.sigstore.json into one directory, then run these two steps from
it, in this order.

1. Check the signature over the checksums. Install
cosign
(brew install cosign), then:

cosign verify-blob SHA256SUMS \
  --bundle SHA256SUMS.sigstore.json \
  --certificate-identity https://github.com/Benehiko/protium/.github/workflows/release.yml@refs/tags/v0.4.0 \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

It must print Verified OK. Anything else means SHA256SUMS was not signed by
the release workflow for this tag: stop, and do not run anything from the
download.

The identity is the workflow file in this repository at this tag, and the
issuer is GitHub Actions. There is no person's key or account behind it, and
the signature is recorded in Sigstore's public transparency log.

2. Check the archive against the checksums.

shasum -a 256 -c --ignore-missing SHA256SUMS

The archive must be listed as OK. SHA256SUMS also lists the runtime and its
sources, and --ignore-missing skips the ones you did not download.

Step 1 is what makes step 2 mean anything: checksums downloaded from the same
page as the archive only prove the two agree, not that either came from us.

Installing

Once both checks pass:

tar -xzf protium-v0.4.0-macos-aarch64.tar.gz
sudo install -m 755 protium-v0.4.0-macos-aarch64/protium /usr/local/bin/protium
protium version

Any directory on your PATH will do in place of /usr/local/bin; without
sudo, ~/.local/bin works if it is on your PATH.

Then let protium tell you what is left to do:

protium runtime install   # the Wine this release was built with, and Rosetta 2
protium d3dmetal install  # Apple's D3DMetal, from the toolkit DMG in ~/Downloads
protium status            # where the installation is, and the next step

protium d3dmetal install also takes a path: the Game Porting Toolkit .dmg,
the evaluation environment inside it, either one mounted, or its redist/lib
folder. It opens a disk image in your terminal, where hdiutil asks you to
accept Apple's licence.

To build the same Wine on your Mac instead, run protium doctor build and then
protium build in place of protium runtime install.

If you downloaded the runtime archive from this page yourself, give its path:
protium runtime install ~/Downloads/wine-…-macos-x86_64.tar.gz. It is checked
against the same SHA-256, and the installed files are not quarantined. Do not
unpack it in Finder and copy the folder into place: that skips the check, and
Archive Utility passes the download's quarantine on to every file it extracts.

The README covers where to get Apple's download, and protium shell-init
prints the line that makes prefixes automatic in every new terminal.

"cannot be opened" or "Apple could not verify"

protium is signed ad hoc, not with an Apple Developer ID, and is not
notarized. A web browser marks what it downloads as quarantined, and macOS
refuses to run a quarantined binary it cannot trace to a registered developer.
The message reads "protium" cannot be opened because the developer cannot be
verified, or, on macOS 15 and later, Apple could not verify "protium" is free
of malware.

Verify the download first (above), then clear the quarantine from the
unpacked directory, before installing:

tar -xzf protium-v0.4.0-macos-aarch64.tar.gz
xattr -dr com.apple.quarantine protium-v0.4.0-macos-aarch64

Or, after the first refusal: System Settings → Privacy & Security → scroll to
the message about protium → Open Anyway.

Downloads made with curl or gh release download are not quarantined and
need neither step.

Assets 11
Loading