Verjuice

Known issues — v0.1.0

The honest list. Each entry says what the limitation is, and what you can do today. Verjuice never reports a workaround as a fix or a refusal as a crash.

macOS

Graphics launches through the mac-wine route are not yet verified

The Windows-Steam route is verified end to end (Vampire Hunters, on an M5 Pro). A title launched directly under Verjuice's own Wine runtime has only been verified with console programs so far. If a graphics title fails on this route, the launch log (Advanced drawer) is the evidence that helps fix it fastest.

--heal covers the mac-wine route only

The mac-steam route hands off to the Steam client, and the session watcher the Linux route uses reads /proc, which macOS does not have — so mac-steam launches run unsupervised. Workaround: if a mac-steam title crashes at startup, run verjuice plan "title" and check the plan's notes; per-title fixes still apply at launch. Supervision for this route is planned.

Winetricks does not run on macOS

A per-title fix that needs a winetricks verb is refused honestly ("cited, not applied") rather than reported as applied. The refusal names the verb and the reason. macOS verb support is planned.

D3DMetal (DirectX 12) is unavailable

The Wine runtime Verjuice fetches does not include Apple's Game Porting Toolkit payload, so DirectX 12 titles have no D3DMetal path yet. DirectX 9/10/11 titles are covered by DXMT/DXVK. GPTK stays user-supplied by design (Apple licence); support for importing it is planned.

The bundle is unsigned

Gatekeeper refuses the first open of a downloaded copy. See the download page for the one-time override and the checksum that stands in for the signature. Signing and notarization are planned.

Linux

Steam runner pins are partial

Switching the Proton build a Steam-owned title runs under requires editing Steam's per-title compatibility mapping while Steam is closed. The refuse paths are hardware-proven and the apply path is offline-verified; the full apply-on-hardware proof is pending. If the pin does not take, Steam's own compatibility setting for that title is the fallback.

Both platforms

Epic: real-account launch needs a one-time login

Enumerating an Epic library needs no account; launching a title with your account needs a one-time legendary auth login, done by you, in your terminal. A manifest-enumeration scan-root divergence was fixed in this build but has not been re-verified on the host that showed it — if Epic titles vanish from your library, that is the first thing to report.

Anti-cheat walls are walls

Titles whose anti-cheat vendors do not permit Wine/Proton get a cited refusal — never a fix attempt, never a bypass. This is deliberate and will not change. The refusal names the title's status and its source (AreWeAntiCheatYet, checked per title).

Unverified database entries are marked, not blurred

Titles marked codified (unverified) carry sourced fixes that have not run on this machine. The marker is never mixed with verified. If a codified fix works for you, that is exactly the report that upgrades it.

Reporting a problem

Run verjuice doctor for a read-only health check, and verjuice doctor --export to build a diagnostic bundle you can attach to a report — it redacts your home path and credentials before you send it anywhere (details). Reports go to support@verjuice.app.