macOS Game Mode now engages for Wine games. The helper that runs the game declares itself a game to macOS, so a full-screen game gets the highest priority on the CPU and GPU and quieter background work, as native games do. Thanks to @dtacci, who found that macOS needs the category and wrote the fix (highball#339).
A game can now open on the display you pick. Wine always put game windows on the main display. A game's page now has a Display choice in its Advanced section, and while the game runs Highball moves its windows to that display, once per window, so a window you drag elsewhere stays where you put it. Moving windows needs the Accessibility permission, which Highball asks for when you choose a display. Thanks to @tuandinh0801, who built it (highball#360).
A new Wine 11 engine, r26, carries Apple's D3DMetal from Game Porting Toolkit 4.0 beta 3 on the D3DMetal 4 line. Beta 3 fixes one of the Shader Model 6.7 operations that beta 2 ignored and adds D3D12GetInterface, which some newer games ask for. Environments on r24 can pick r26 under Advanced, Engine. r27 is r25 under a new number, with nothing changed. Nothing moves until you pick it.
Also in this version:
- A variable you set in an environment, or one a game's fix sets, now wins over the graphics mode's own default for that variable.
- The vkd3d mode keeps vkd3d-proton's shader pipeline cache in the environment, one folder per engine build, so a game's later starts on the same engine skip the pipeline compiles.
- A new environment starts on the first graphics mode its engine actually ships, instead of a mode that would fall back at every launch.
- A play report's "Played for N min through Highball" goes to the form's Session field, so Notes stays free for what you want to say.
The first Steam start or two on a new engine revision can take longer while macOS prepares its graphics caches, then it is as fast as before. Wine 11 environments never change engine by themselves, so nothing moves until you pick the new one.