Want a feature not available yet in MetalSharp? List it here.

[aaf2tbz]

I've pretty much done just about everything I can think of for a game launcher and I've borderline run out of new ideas. We support GOG, Epic, Ubisoft, Steam, Installers/EXE's and Emulators. The only thing not supported yet is Battle.Net and it's because the MacOS permission handling with Wine does not work through it, so it's not really an option.

Just about every game in my Steam Library runs and the only games really left to handle are games that require a version of OpenGL greater than 2.2. Obviously there will be edge cases and games I'll need to explicitly test and support as time goes on for users, but mostly, it plays just about anything.

If you would like to see any new features added to MetalSharp to improve your experience, leave a comment here!
It can be getting a specific installer to work, mods, Ui/UX requests, anything. Let me know what YOU want from your launcher!

Here are my own planned upcoming updates;

• Support OpenGL 3.3+
• Use DxWrapper to convince dx1-dx7 to load into DX9 at higher resolutions
• Release Arm64ec Wine with FEX for 0 rosetta MacOS 28 support
• Confirm more running games
• FSR 4 / DLSS 5 Support
• Finish VKD3D-Proton D3D12 / Custom MoltenVK

[Rastafabisch]

I'd suggest to look into taking advantage of Metal4, where it makes sense as well as migrating MoltenVK to KosmicKrisp, as it is a far newer much much more active developed Vulkan translation layer without special restrictions (reduced feature set) but rather with the goal to reach spec for spec compatibility with upstream Vulkan. Also this should ease up the path to Vulkan games such as Detroit: Become Human.

I would also love to see migrating away from electron as it's a CPU, performance and disks space hog. ~300MB wasted Space, 20% CPU usage just for having a static window in the background, and overall unreliability (not limited to MetalSharp, e.g. steam install just does not work for me, but neither does auto-updating the signal app for instance), etc. Maybe a tradeoff with taking for multi OS applications but not for native environments. Also totally unnecessary as you could leverage the webkit framework, if html code is the desired path. Though I'd argue leveraging native UI frameworks will elevate the user experience even further, and as such advocate for SwiftUI. I'd would be and feel much more native.

For further ideas you may want to take a look at madeira. especially madeira-Dock.

[aaf2tbz]

Appreciate the feedback! I won't go with swift because eventually there will be a linux release alongside the normal arm64 macos release but I have been considering using GPUI instead. (Navigating away from using html would also help with dealing with html application security risks). As for KosmikKrisp, I will look into what's feasible there! I have integrated a lot of metal 4 custom code into metalsharp but i'm also trying to remain backwards compatible with Metal 3.1 / 3.2 as well.