Skip to content

Dev 1.1.0 - #49

Closed
foobisdweik wants to merge 21 commits into
NotProtonNot:dev-1.1.0from
foobisdweik:dev-1.1.0
Closed

foobisdweik wants to merge 21 commits into
NotProtonNot:dev-1.1.0from
foobisdweik:dev-1.1.0

Conversation

@foobisdweik

Copy link
Copy Markdown

No description provided.

LaganYT and others added 21 commits October 8, 2026 02:20
Downloads the pinned 20260125 release on first use, runs it unattended with
the verbs the user types, and writes its output to winetricks.log in the
prefix. Refuses while the game is running, and refuses annihilate and prefix=.

(cherry picked from commit ae4ebdc)
Steam on an external drive was reported as not found. The Status page now has a Choose button for Steam's location, and Repair Steam copies Valve's bundle onto that drive before swapping it in, since the swap cannot cross drives.

Closes #29

(cherry picked from commit 347bc48)
NSOpenPanel returns app bundles as directory URLs, so choosing /Applications/Steam.app saved it with a slash instead of clearing the setting, and Steam's stop patterns came out as Steam.app//.

(cherry picked from commit 01c59cb)
Two things kept a copy of CrossOver from being offered as a runner source:

- Discovery only looked at bundles whose name starts with "CrossOver".
  Copies made by other tools are named whatever those tools name them, so
  a bundle is now recognised by what it carries (its CrossOver tree with
  lib/wine), which looksLikeCrossOver already checked.
- "Already listed" compared builds, so picking a second copy of a build
  that was already listed was refused. It now compares bundles: only the
  same bundle is already listed, and another copy is added by hand, which
  also makes it the preferred source for that build.

(cherry picked from commit 1ad8368)
A runner was identified only by its build, so a modified copy of
CrossOver could not be installed next to the original.

A copy can now name itself with a notproton-variant file in its CrossOver
directory. It then becomes the runner <build>-<name>, with its own tools,
and is checked and ntdll-patched like the build it copies. Without the
file nothing changes.

(cherry picked from commit 250c474)
Some games need a specific D3DMetal. A copy of CrossOver 26 can carry more
than one toolkit (lib64/apple_gptk next to apple_gptk_3, apple_gptk_4,
...), but it only loads apple_gptk.

Each other toolkit with a D3DMetal major that apple_gptk lacks is now
offered as its own runner, <build>-d3dm<N>. Making that runner copies the
toolkit over apple_gptk in the runner's copy; the source is not touched.
CrossOver 27 already picks a D3DMetal per game with
CX_GRAPHICS_BACKEND_VERSION, so only lib64 is looked at.

(cherry picked from commit 927ab8a)
A rebuild ties the prefix to the chosen tool, but Steam keeps launching
the game with the tool it has for it. When the two differ the next launch
is refused, and the alert points back at the rebuild.

After a rebuild the app reads the game's tool from Steam's config.vdf and,
if it is another one, says which tool to choose in the game's Properties.
The file is only read, never written.

(cherry picked from commit e35d5a7)
The CrossOver row did not say which D3DMetal its runner gets, and the
toolkit rows only said it by name. The row now shows the D3DMetal in
lib64/apple_gptk, read from the runner's copy once it is set up, since
the source can switch toolkits afterwards.

Setting up a toolkit runner now checks that its copy runs the D3DMetal
in its name, and stops with a reinstall hint if it does not.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 49b54e7)
A toolkit runner's tools said which D3DMetal they run and the runner
next to them did not, so Steam's compatibility list showed "CrossOver
26.3" beside "CrossOver 26.3 · D3DMetal 3". Each tool now names the
D3DMetal its runner's copy runs, read from lib64/apple_gptk in that
copy. A toolkit runner already names it, so it is not repeated.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 8af107f)
@foobisdweik foobisdweik closed this Oct 8, 2026
@foobisdweik
foobisdweik deleted the dev-1.1.0 branch October 8, 2026 12:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants