[Broyojo]

Bumps VERSION to 0.3.2. Merge it last, after any other PR you want in the release. #143 (fill mode) isn't merged, so it isn't in the build. src/mesa is back on the merged queue, and fill mode is parked on the kk-fill-mode branch there.

In main since 0.3.1:

• Retina follow-ups: raw mouse movement in points (wine: Report raw mouse movement in points, as before Retina mode (#131) #144, fixes Mouselook is about twice as sensitive since 0.3.1 (Retina mode doubles relative mouse movement) #131), cursor size (wine: Keep a game's cursor at its size in points in Retina mode #99), and modes that share no factor with the screen (wine: Don't abort on a mode whose size shares no factor with the screen's #132)
• Cloud saves kept on a first launch (steam-run: Keep the Cloud saves Steam syncs before a first launch (#113) #116, for Cloud saves not working across multiple games #113)
• DOOM (2016): depth bounds emulation (mesa: Emulate the depth bounds test before Apple GPU family 10 (#128) #140), buffer descriptor range clamp (mesa: Clamp a buffer descriptor's range to its buffer (#128) #141), and hadron-steam staying up for the second process (hadron-steam: Stay the running Steam until the game's last process exits (#128) #142), all for DOOM (2016): working AppID-scoped KosmicKrisp workaround and RetinaMode=n on M1 Max #128
• Hogwarts Legacy: the fixed-base loader restart (wine: Start the loader again while a fixed-base executable's range is in use (#95) #139) and the RtlIsEcCode bound (wine: Return FALSE from RtlIsEcCode above the user space (#95) #109), for Hogwarts Legacy (990080): random c0000018 for the fixed-base EXE, then recursive access violations in RtlIsEcCode before the menu #95
• BELOW: top-down allocations (wine: Keep top-down allocations above 4 GB while there is room (#105) #108, for BELOW (250680): LuaJIT low-address allocation fails; proposed Wine MEM_TOP_DOWN placement fix #105)
• Unvanquished: aliased keyboard layouts (wine: Don't take a second keyboard layout for an IME (#111) #119), and Zink by default for a bare wine (wine: Use Zink and KosmicKrisp when Wine is started on its own (#112) #118)
• mtld3d copies kept current in prefixes (play: Keep a prefix's mtld3d copies up to the runtime's #138)
• no window while updating a prefix (wine: Don't show a window while updating a prefix (#107) #110)
• log cap (play: Keep a game's log to its start and its end past 64 MB #100)
• checkout/test-copy runtime joining (steam-run: Join the Wine in a game's prefix from a checkout or test copy too #103)

dist/ is rebuilt from main: Mesa (KosmicKrisp and Zink), Wine and the launcher were rebuilt on 2026-10-26. Before that, dist/ lacked #140–142. scripts/check-patches.sh passes for every queue. DXMT, FEX, mtld3d, vkd3d-proton and DXVK haven't changed since 0.3.1.

The draft notes are in the session scratchpad and will go in this PR once the tests below confirm what they claim.

Before publishing (the release checklist, run from the release build itself):

• Portal 2 and Subnautica mouselook (wine: Report raw mouse movement in points, as before Retina mode (#131) #144) and cursor size (wine: Keep a game's cursor at its size in points in Retina mode #99)
• DOOM (2016) with Vulkan on this M-series Mac (mesa: Emulate the depth bounds test before Apple GPU family 10 (#128) #140–142)
• a first launch of a game without an install script, keeping its Cloud saves (steam-run: Keep the Cloud saves Steam syncs before a first launch (#113) #116)
• one D3D9 game whose prefix already exists, picking up the current mtld3d (play: Keep a prefix's mtld3d copies up to the runtime's #138)
• one D3D11 game and one D3D12 game, as a regression check
• Repair after updating from 0.3.1
• then your OK, and Mike's, to send the build to Apple

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-27T01:00:59.894189Z	c3dd1ef	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.