Apple-Silicon-Guide VS Proton

Congratulations for buying a NON-PC that's IN-capable of playing games on its own except these games https://www.pcgamingwiki.com/wiki/List_of_macOS_ARM_games. You paid top dollars for a crippled machine, all thanks to Apple. Any ARM user "Must" use one of the PC Emulators told in https://github.com/mikeroyal/Apple-Silicon-Guide which is usually Rosetta (default by Apple) for you so that you can play ANY game you see but NOT in its native speed but in Emulated (slower but not much) speed.

Steam sells only Windows games with "exceptions" for Linux games (SteamOS) and MacOS games (only means Intel-Macs, not ARM-Macs). Since you now own a non-PC now it's time to EMULATE a PC in your ARM device so first READ through https://github.com/mikeroyal/Apple-Silicon-Guide which forms the basis of how to do Gaming in any ARM device.

GPT (Game Porting Kit) is NOT what you think it's and definitely not what Apple advertises to be a Proton competitor (Proton is for SAME CPU but Different OSes, GPT is for Different CPU + Different OSes, totally irrelevant). GPT is just "another Windows EMULATOR" as there are lots of them in the https://github.com/mikeroyal/Apple-Silicon-Guide but a better one compared to previous attempts for the same thing.

Unless you sell your Mac for a PC (M1 devices are not PC), you'll need these emulation tools because nothing will change.

So there are 2 paths ahead of you; either buy a Normal Laptop (Intel or AMD) and enjoy all the PC games that can you find or buy a Apple Laptop and instead use Windows Emulation (current best solution with all emulation tools listed at https://github.com/mikeroyal/Apple-Silicon-Guide) to play any PC games you may want, with glitches of course due to emulation Basically you choose either Gaming or Apple but can't do both for a satisfactory performance because the money you'll be giving to a Apple Laptop will get you a better PC Gaming Laptop for the same price range.

All the solutions told in https://github.com/mikeroyal/Apple-Silicon-Guide are one way or another an emulation for Windows because there are no other ways. Sad thing is, Apple did the same scam back then 2000's with https://en.wikipedia.org/wiki/PowerPC as it can be referred as M0 of is time (predecessor to M1) but that caused them to Bankrupt so later to be saved by https://www.cnbc.com/2017/08/29/steve-jobs-and-bill-gates-what-happened-when-microsoft-saved-apple.html but Apple is stupid enough to repeat same mistake again and deceive their fans.

Thing is, Proton is between Operating Systems for the "same" PC Architecture of Intel CPU Instruction Set that governs all the CPUs (Intel, AMD, whatever) except only the ARM so Proton is extremely fast because it's a Code Conversion layer rather than an Emulation. Instead Apple using Mobile CPUs (where M comes from) on PC Architecture is very very different because this is between "different" PC Achitectures so code conversion won't suffice and instead Full Emulation is done from Intel-to-ARM via software on a https://en.wikipedia.org/wiki/Virtual_machine that all ARM solutions told in https://github.com/mikeroyal/Apple-Silicon-Guide based upon.

In case anyone didn't understand his -Enigmatic- talk, he's talking about https://www.applegamingwiki.com/wiki/Game_Porting_Toolkit the latest band-aid from Apple as all previous attempts are at https://github.com/mikeroyal/Apple-Silicon-Guide to make Windows Warframe to -force- it work on M1-M2 series Macintosh models via emulation (and no GPTK doesn't work like Steam's Proton because Proton is a conversion layer between OSes so fast but Apple needs emulation between different CPU Architectures).

Basically, you own a "Mobile" CPU (where M comes from) running with the PC counterparts and no PC game is written for that CPU because all games are always written for https://en.wikipedia.org/wiki/X86_instruction_listings (Intel and AMD) so players yourself now -Must- use Emulation Software that you can pick any from https://github.com/mikeroyal/Apple-Silicon-Guide. So you'll basically be running Windows in a Virtual Machine in your M1 Mac and run the game inside that virtual machine (any Windows game, it doesn't differ for you to be Mac anymore) for a lesser performance compared to running the game on a true PC that you used to have but no longer because of a poor and uninformed choice to switch to Mac.

So educate yourself by reading true articles like https://www.pcworld.com/article/394895/what-is-valve-proton-steam-deck-games-software-explained.html to learn the differences and be careful from now on where and how you get your information because you're inclined to believe in https://en.wikipedia.org/wiki/Information_pollution created by Apple. Apple is creating Yet-Another-Windows-Emulator claiming to be faster from tons of other Emulators told in https://github.com/mikeroyal/Apple-Silicon-Guide which doesn't change the fact that games won't be running Natively so they'll either be slow or problematic (no emulation is perfect).

The "Metaverse" is a complete joke, and among gamers, Valve has a way better reputation than Meta. Why would they want to dilute that brand?

They already have their own platform (Steam), OS (SteamOS), VR headset (Index), their own Windows translation layer (Proton, https://github.com/ValveSoftware/Proton), their own partnership with cloud gaming (Steam Cloud Play using GeForce Now , https://partner.steamgames.com/doc/features/cloudgaming), etc.

IMO: As someone with thousands of games on Steam, there's no way in hell I'd want that linked to Facebook. I think they eventually removed the requirement to have a FB account to use a Quest, but they still require a Meta account. Yuck.

This reeks of Facebook recognizing the Metaverse as the failure that it was and opening it up because it's no longer relevant...

Or Valve's Proton[0], a tool for playing Windows games on Linux.

https://github.com/ValveSoftware/Proton

Did you mount it with the correct flags?

there is a hack to try and use your existing windows game install from an NTFS drive, but i don't recommend it as steam will try to save file names that are not allowed on NTFS...plus ext4 is faster.

From a quick search, here's what I found. It looks like you're encountering some common issues that can occur with games running on Linux through Proton, especially with the recent updates to games like Satisfactory that might affect compatibility. The log entries you're seeing related to D3DCompile2 failing to compile shader and the issues with Ternary operator and LinearToSrgbBranching not being defined, suggest that there's a problem with shader compilation. This can often be related to the version of Proton or the graphics drivers you are using. Some users have reported that the game does launch with the -vulkan option but with graphical glitches and lower performance, which indicates that the Vulkan renderer is working but possibly not optimally on your setup. From the discussions in the community, users have suggested ensuring that the latest drivers for your graphics card are installed and, if using an Intel GPU, that the Mesa drivers are up to date since Intel XeSS references were found in the logs. If you're using NVIDIA graphics, make sure you have the latest drivers and possibly set the PROTON_ENABLE_NVAPI=1 %command% to enable DLSS if you're under Vulkan. If you're using an Optimus laptop with both Intel and NVIDIA GPUs, make sure your Optimus setup is correctly configured. Some users have found success by specifying DXVK_FILTER_DEVICE_NAMES=GeForce to force the game to use the NVIDIA GPU. It's also worth noting that if you're encountering issues with DirectX 11, you might want to try forcing the game to use DirectX 10 if possible or look into DXVK configurations that could resolve compatibility issues. Lastly, if none of these solutions work, you could try running a trace with apitrace to gather more detailed logs that might point to the specific issue. If you're still stuck, it would be a good idea to report the issue to the Proton GitHub page or seek further assistance in the game's community forums where others might have encountered and solved similar issues. For more information and to find others who might have resolved similar issues, check out the community discussions on GitHub​​, Steam Community​​, and the DXVK GitHub page​​.