Better make sure you have a Mac with apple silicon, Intel Metal hasn't been updated at all in Ventura. OpenGL has been deprecated since Mavericks and is stuck on a broken 4.1 in newer OS releases and doesn't even work, its completely broken due to apple, and its apple's own implementation which is broken, OpenGL is dead on Mac unless you just want to learn it for the sake of learning it now. You essentially can't install a newer openGL in MacOS anymore. OpenGL is still newer and updatable on windows, so if you have an intel Mac you should start on a newer OpenGL, essentially installable on the bootcamp side, but again not really feasible with all the other recent APIs out there. Metal2 is also being deprecated on intel machines older than 2018, and even the 2018 Macs only have symlink updates to be able to dev for metal3. At least that is what I've found. The whole thing is ridiculous really. I'm sure you can start on a metal2 machine and work your way up as needed. You can also start with DX12 and then learn metal while using the new porting toolkit to see what changes are needed while learning Metal. With a little bit of imagination you can predict where apple is going with its 'need for power' behind their features. And now with vision's features you should expect to see that concept come to the Mac. I do not expect MacOS as we know it to be around much longer at the rate apple is going with pushing UI and processing power needed for it. I doubt it will even be called MacOS anymore once the keyboard, mouse, and UI are deprecated, which was supposed to be with the iMac Pro, but since it was and intel machine... I believe they are holding off doing anything drastic to the Mac until they see what users do with vision, but mark my words, it's going to happen. It's predictable.

Are you all using x86 shell to do this and installing rosetta2 using brew? you can't use ARM anything with GPTK builds and can't use arm arch. Incase it wasn't mentioned. I am having some issues finding out why my game wont load, I don't see any debug commands for GPTK, do wine debug terms apply here? I try to use this in terminal and get no reports. % export WINEDEBUG=+all % gameportingtoolkit ~/my-game-prefix /Users/imac/my-game-prefix/drive_c/(my game) Nothing happens and the game returns with a generation error. I think this has to do with a dll trying to find CPU id. But I have no idea where to bypass this or how to even start debugging it. Any ideas?