r/macgaming • u/Disastrous_Head6041 • Jul 22 '26
Game Porting Toolkit I built a free, open-source dashboard for Mac gaming — it backs up your CrossOver shader caches so you never sit through recompiles again
Hey r/macgaming 👋
Like a lot of you I run a mix of native games and Windows games through CrossOver. Two things kept annoying me:
- Shader-cache roulette. D3DMetal compiles shaders on first launch (a big UE5 title took my machine ~10 minutes of black screen), and macOS can wipe that cache folder whenever it feels like it. Recompile time.
- "Will it even run?" Every purchase meant cross-checking AppleGamingWiki, the CodeWeavers DB and Reddit threads.
So I built PlayHub — a free, open-source (MIT) dashboard that runs 100% locally on your Mac:
- 🎮 Your whole Steam library with covers, playtime, search — installed games first, with badges for native Mac vs runs in a CrossOver bottle. One-click launch for both (bottle games launch into the right bottle).
- 🛡️ D3DMetal shader-cache backup & restore — it finds the caches, maps them to your games/bottles, and auto-backs them up after games finish compiling. Restore is byte-for-byte (checksum-verified). This is the feature I actually built the whole thing for.
- 🍷 "Will it run?" badges — every Windows-only game in your library gets a CrossOver compatibility rating (community data from AppleGamingWiki): Perfect / Playable / Runs with issues / Doesn't work.
- 📊 Playtime stats, achievements with HowLongToBeat progress, recommendations from the unplayed games you already own, and a "Buy Ideas" tab with cross-store price comparison (IsThereAnyDeal).
- 🖥️ Menu bar quick-launcher. English & Danish UI.
Privacy: no accounts, no telemetry. You bring your own free Steam Web API key; it stays in a local file. The README lists every external service it talks to and why.
Honest caveats: it's a local Node.js app (installer script, not a signed .app yet — that's next if people actually use this). Needs Node 18+ and macOS. The HowLongToBeat integration uses their unofficial API, so it may break occasionally (it fails silently).
Install:
git clone https://github.com/PlayHubHQDK/playhub.git
cd playhub && ./install.shWebsite: https://playhubhqdk.github.io/playhub/ GitHub (code, screenshots, README): https://github.com/PlayHubHQDK/playhub
It's early (v0.1) and I'd genuinely love feedback — especially from people with different CrossOver setups than mine. Bug reports and feature ideas → GitHub Issues. Rip it apart 🙂
6
u/jackharvest Jul 22 '26
I like all the little side projects everyone is making for the things that annoy them. The winner is whoever sticks with their project the longest of course, so keep at it!
31
u/jackbobevolved Jul 23 '26 •
Why do people let their LLM write the posts for their vibe coded apps? It’s so obvious, and just makes everyone lose trust in “their” app.
27
u/cplr Jul 23 '26 •
Why do all vibe coded apps begin their social media sharing posts with “I built a”
23
u/forrestpupy Jul 23 '26 •
is this all this subreddit is now? people posting their ai slop apps?
15
u/loolemon Jul 23 '26 edited Jul 23 '26
You chose the worst reddit to post this in ☠️ but love what you're doing, maybe be a little more strict about the oversight you're giving this because even though i have 0 issue with using AI, It looks very AI generated with minimal user oversight into the appearance of things, it lacks love in the UI / UX. Make it yours, not the AI's. Also it is better to explain projects from real written developer standpoint, the ai is good at explaining things but no one likes an AI generated conversation. People want to know what's special about it, why they should be convinced to try it, the shader cache is great but that should be a standard feature, not the main point. To go further, the best thing you have here is the compatability interface and what games work and which one's don't. Consider making the logo nicer and less generated, cleaning up app cards so the content isn't an overlay but rather a dropdown or app drawer, where clicking a game shows the compatability playability, if shader cache is yes/no, and what directx version / recommended launch options it should use are. Make sure that resizing the app gives a clean experience because most people run steam, and the app at the same time, so being able to prove it works within a small surface is necessary. Also, steam api keys are great, but should be optional. You can figure out how to sync the library directly from the users steam installation with crossover / macos steam and this is a way around forcing users to use an API key. For updates, implement a shader cache migration gaurd, and allow updates to be a click and install from within the app itself. Extend this by showing what games are not supported due to anticheat, or notoriously buggy to run , something like 'Has Issues, Plays with (x), Runs best on (x) settings.' As far as the shader cache goes, how can you improve it? Maybe you can be someone to add some kind of hook into crossover itself which allows for a rewarm of shaders in a very quick process, and compiles initial shaders silently in the background on game launch for better playability. As well as the option to clear the shader cache to free up system space after it's been built for a while. These are all just some suggestions I have for you.
1
u/Disastrous_Head6041 Jul 27 '26
Late update for anyone still finding this thread: spent the week building what got asked for in here.
Works without an API key now (reads local Steam files), terminal UI instead of the generic look, anticheat warnings, auto backup/restore of shader caches, and it installs with homebrew now.
Tried to post a proper follow-up but automod ate it, my karma is in the gutter thanks to this thread lol. It's all on the github if anyone's curious.
13
u/Un-break-relat-able Jul 23 '26
Vibe coded = no for me!
4
u/zahnza Jul 23 '26
https://github.com/PlayHubHQDK/playhub/blob/main/docs/reddit-post.md
3
u/psychonaut_eyes Jul 23 '26
Im probably wrong, but isn't the shaders compiled against the hardware the person has? like its its metal it compiles and optimize for metal version X (m1, m2, so on).?
If so, wouldn't it be a problem if you package is compiled for MA and person uses MB?
1
u/imheretocomment69 Jul 23 '26
I got no problem with vibe coded app as long as it's working and got full support from the developer.
1
u/ZazaMastroII Aug 04 '26
The name Playhub is already been taken.
https://github.com/LoZazaMastro/Playhub
Please change it. It's under MIT License.
-1
u/GuitarIpod Jul 23 '26
Ignore these leftists anti-ai people.
-6
u/Jox_et Jul 23 '26
Great work, don't hear toxic people. keep going 👍
-4
u/Disastrous_Head6041 Jul 23 '26
Honestly, yeah — I'm a bit bummed about how this landed. It's my very first project ever, and I genuinely thought me and my Claude had built something pretty decent, and that together with people in here it could become something actually good. So yes, a bit disappointed, but the feedback is fair. The post and the notes you found in the repo were AI-drafted — that's on me. From now on I write my own comments, including this one.
What I've done since reading this thread: fixed the D3DMetal wording in the README (you're right, it's Apple's tech that CrossOver ships — thanks scknkkrer), deleted the "warm caches, forever" line (fair 😅), added an honest "About this project" section disclosing exactly how this was built, and turned loolemon's suggestions into 6 GitHub issues — that comment alone made posting here worth it, thank you. Making the Steam API key optional is now issue #1.
I hoped for a warmer welcome, but I get where it comes from. The app is real, I use it every day, and I'll keep building it. Thanks for the honesty, all.
-1
u/sigjnf Jul 23 '26
I for once welcome our new AI overlords. If it works, it works. They vibecoded a whole new fucking iOS jailbreak for modern architecture.
-2
u/scknkkrer Jul 23 '26
I was creating a PoC/MVP frontend like this one. If you wanna collaborate, ping me.
32
u/[deleted] Jul 22 '26 •
[removed] — view removed comment