Repository navigation
Mac compatibility badges from what this Mac has seen - #305
marcshawco wants to merge 4 commits into
Conversation
… block Works out how each game should be run on this Mac and how likely it is to run, and shows it where Steam shows the Steam Deck's. - machine.c, tuning.c: read the Mac (chip, GPU cores, memory, macOS, display) and turn it into settings the defaults whitelist accepts. - game.c: read an installed game's files: word size, which Direct3D it loads, anti-cheat, launcher, engine, native macOS build. - verdict.c: a tier from the sessions the run script now records. - advice.c: Mac + game + history into settings, launch arguments, a badge and a reason. D3D12 goes to D3DMetal, D3D11 to DXMT, D3D9 to DXVK. - rules.c: launch rules from ~/Library/Application Support/notproton/rules, on the plugin grammar (new conf kind). - catalog.c: one pass over the library. Uses Valve's Steam Deck results from appinfo.vdf (appinfo --compat) for games that are not installed. - webpatch.c: badge on library tiles, stat on the game page, "Use Recommended" on the Compatibility page, two switches in Preferences. - store.c, store_page.js: the same on store and wishlist pages, through the web helper's debugger on 127.0.0.1:27101. Has its own switch. - compat_run.sh: records sessions, applies advice and rule arguments at launch after anything the user set. Also fixes two things found on the way: a DXMT_CONFIG with two clauses was dropped on its way to the page (is_setting_value refused ';'), and `make dobby` failed in a path with spaces. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
docs/mac-compatibility.md covers what each badge means, where the answers come from, the switches, launch rules, how the store part works and what its debugger port costs, and the files involved. README points to it. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
|
I don't want to use the Steam web debugger. That is developer functionality that could go away at any time and opens a user up to certain kinds of attacks. Relying on Steam Deck data for anti-cheat is not really reliable for us; there are many games (all EAC games, among others) that work on Linux/Proton but do not work on macOS. There are also games that work specifically on SteamOS but do not work on any other Linux distro. I wish the Obelisk person would drop the bulk of their project and focus on the really good part - their light Linux translation layer. I'd like to have something like that as a plugin or otherwise part of NotProton, as that would get a lot of anti-cheat titles working. That'd be cool. The hard part with auto-applying CrossOver compatibility settings is getting the data in the first place. Where would I source which compatibility settings are correct? Just because the game starts with a specific graphics backend does not mean that the game started correctly - it could have visual issues, etc. A human needs to look and see. Plus, lots of games need fixes (MacGameFix, etc) in order to work correctly. I can't really auto-apply those, it's not my project, I shouldn't get between the author of that tool and their users.... The rest of the idea itself is not a bad idea. The biggest problem is using the Steam web debugger. That's not how the rest of NotProton works. :\ |
|
I hope I didn't come off too harsh. There is a great idea here, my objections are all about implementation. I'd like to do something to flag the games that need fixes via MacGameFix with an indicator showing that. There is a good idea here! In a perfect world, I'd want to put together a web service with user-generated (and validated by NotProton) compatibility/performance data and surface that in Steam. It's just a large lift for a hobby project. :( |
|
Not harsh at all, thanks for looking. You’re right about the debugger, and about the Deck data: an EAC game that’s Deck Verified would show as “likely” on Mac, which is wrong. I’ll pull the two small fixes (DXMT_CONFIG with two clauses, and make dobby in a path with spaces) into their own PR, and either close this one or cut it down to local-only badges from what’s actually been run on the Mac, with no debugger, no Deck data and no auto-apply. Would that smaller version be worth a look? Happy to try the MacGameFix indicator afterwards if you can point me at where its list of fixed games lives. |
Would be worth a look! I believe the list of fixed games is in the readme. I have not looked at the project deeply enough to know more than that. |
Removes the Steam web debugger and the store/wishlist block, the Steam Deck data, the per-game settings and their auto-apply, the launch rules, and the "Use Recommended" row. What is left are the badges from this Mac's own sessions and each game's install folder. The DXMT_CONFIG and Dobby path fixes moved to their own PR (NotProtonNot#306). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Cut down as discussed above: no web debugger, no Steam Deck data, no auto-applied settings, no launch rules. The two small fixes are in #306.
What is left is a badge on each installed game, worked out only from this Mac:
Where it shows: the corner of the library tile, a
MACstat next to Play Time on the game page, and the verdict with its numbers on the Compatibility page's rebuild row. There is a switch under Steam → Preferences → Compatibility.How it works:
session_health).record_historynow keeps a running count beside the prefix.game.cwalks the install folder for anti-cheat and launcher file names and a.appbundle. File names only, cached beside the prefix.catalog.cdoes one pass over installed games on a thread and hands the map to the library.Details in
docs/mac-compatibility.md.Notes:
SharedJSContext, where an added<style>never reaches the visible window.Tested: 29 make targets pass, plus new
verdict-check,game-check,badge-check,catalog-check. Checked by hand in Steam build 1794536281 on an M4 Max with one library. Not tested with multiple libraries or accounts, FEX, or Intel.🤖 Generated with Claude Code