Apple-Silicon-Guide VS mesa

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).

No problems, AMD Adrenalin it's a part of Windows AMD drivers, but on Linux you have not this soft, here is link: https://github.com/Mesa3D/mesa

# apt install libxcb-glx0-dev libx11-xcb-dev libxcb-present-dev libxshmfence-dev libxxf86vm-dev # git clone https://gitlab.freedesktop.org/mesa/mesa # cd mesa meson setup build/ -Dgallium-drivers=lima,panfrost,kmsro,swrast -Dplatforms=x11 -Dvulkan-drivers= -Dllvm=disabled The Meson build system Version: 1.0.1 Source dir: /Dati/mesa Build dir: /Dati/mesa/build Build type: native build Project name: mesa Project version: 23.3.0-devel C compiler for the host machine: cc (gcc 12.2.0 "cc (Debian 12.2.0-14) 12.2.0") C linker for the host machine: cc ld.bfd 2.40 C++ compiler for the host machine: c++ (gcc 12.2.0 "c++ (Debian 12.2.0-14) 12.2.0") C++ linker for the host machine: c++ ld.bfd 2.40 Host machine cpu family: arm Host machine cpu: armv7l Checking if "-mtls-dialect=gnu2" runs: YES Dependency vdpau skipped: feature gallium-vdpau disabled Program glslangValidator found: NO Dependency libva skipped: feature gallium-va disabled Program python3 found: YES (/usr/bin/python3) Fetching value of define "ETIME" : 62 Checking for function "bswap32" : YES Checking for function "bswap64" : YES Checking for function "clz" : YES Checking for function "clzll" : YES Checking for function "ctz" : YES Checking for function "expect" : YES Checking for function "ffs" : YES Checking for function "ffsll" : YES Checking for function "popcount" : YES Checking for function "popcountll" : YES Checking for function "unreachable" : YES Checking for function "types_compatible_p" : YES Compiler for C supports function attribute const: YES Compiler for C supports function attribute flatten: YES Compiler for C supports function attribute malloc: YES Compiler for C supports function attribute pure: YES Compiler for C supports function attribute unused: YES Compiler for C supports function attribute warn_unused_result: YES Compiler for C supports function attribute weak: YES Compiler for C supports function attribute format: YES Compiler for C supports function attribute packed: YES Compiler for C supports function attribute returns_nonnull: YES Compiler for C supports function attribute alias: YES Compiler for C supports function attribute noreturn: YES Compiler for C supports function attribute visibility:hidden: YES Checking if "__uint128_t" compiles: NO Checking for function "reallocarray" : YES Checking for function "fmemopen" : YES Checking if "gc-sections" : links: YES Compiler for C supports arguments -Werror=implicit-function-declaration: YES Compiler for C supports arguments -Werror=missing-prototypes: YES Compiler for C supports arguments -Werror=return-type: YES Compiler for C supports arguments -Werror=empty-body: YES Compiler for C supports arguments -Werror=incompatible-pointer-types: YES Compiler for C supports arguments -Werror=int-conversion: YES Compiler for C supports arguments -Wimplicit-fallthrough: YES Compiler for C supports arguments -Wmisleading-indentation: YES Compiler for C supports arguments -Wno-missing-field-initializers: YES Compiler for C supports arguments -Wno-format-truncation: YES Compiler for C supports arguments -Wno-nonnull-compare: YES Compiler for C supports arguments -fno-math-errno: YES Compiler for C supports arguments -fno-trapping-math: YES Compiler for C supports arguments -Qunused-arguments: NO Compiler for C supports arguments -fno-common: YES Compiler for C supports arguments -Wno-microsoft-enum-value: NO Compiler for C supports arguments -Wno-unused-function: YES Compiler for C supports arguments -Werror=format: YES Compiler for C supports arguments -Wformat-security: YES Compiler for C supports arguments -Werror=thread-safety: NO Compiler for C supports arguments -ffunction-sections: YES Compiler for C supports arguments -fdata-sections: YES Compiler for C++ supports arguments -Werror=return-type: YES Compiler for C++ supports arguments -Werror=empty-body: YES Compiler for C++ supports arguments -Wmisleading-indentation: YES Compiler for C++ supports arguments -Wno-non-virtual-dtor: YES Compiler for C++ supports arguments -Wno-missing-field-initializers: YES Compiler for C++ supports arguments -Wno-format-truncation: YES Compiler for C++ supports arguments -fno-math-errno: YES Compiler for C++ supports arguments -fno-trapping-math: YES Compiler for C++ supports arguments -Qunused-arguments: NO Compiler for C++ supports arguments -flifetime-dse=1: YES Compiler for C++ supports arguments -Wno-microsoft-enum-value: NO Compiler for C++ supports arguments -Werror=format: YES Compiler for C++ supports arguments -Wformat-security: YES Compiler for C++ supports arguments -ffunction-sections: YES Compiler for C++ supports arguments -fdata-sections: YES Compiler for C supports arguments -Wno-override-init: YES Compiler for C supports arguments -Wno-initializer-overrides: NO Compiler for C supports arguments -Werror=pointer-arith: YES Compiler for C supports arguments -Werror=vla: YES Compiler for C supports arguments -Werror=gnu-empty-initializer: NO Compiler for C++ supports arguments -Werror=pointer-arith: YES Compiler for C++ supports arguments -Werror=vla: YES Compiler for C++ supports arguments -Werror=gnu-empty-initializer: NO Checking for function "__builtin_ia32_clflushopt" : NO Checking if "GCC atomic builtins" compiles: YES Checking if "GCC atomic builtins required -latomic" : links: YES Checking if "GCC 64bit atomics" with dependency : links: YES Library ws2_32 found: NO Header "sys/sysmacros.h" has symbol "major" : YES Header "sys/sysmacros.h" has symbol "minor" : YES Header "sys/sysmacros.h" has symbol "makedev" : YES Header "sys/mkdev.h" has symbol "major" : NO Check usable header "sched.h" : YES Checking for function "sched_getaffinity" : YES Check usable header "xlocale.h" : NO Check usable header "linux/futex.h" : YES Check usable header "endian.h" : YES Check usable header "dlfcn.h" : YES Check usable header "sys/shm.h" : YES Check usable header "cet.h" : NO Check usable header "pthread_np.h" : NO Check usable header "renderdoc_app.h" : NO Check usable header "sys/inotify.h" : YES Checking for function "strtof" : YES Checking for function "mkostemp" : YES Checking for function "memfd_create" : YES Checking for function "random_r" : YES Checking for function "flock" : YES Checking for function "strtok_r" : YES Checking for function "getrandom" : YES Checking for function "qsort_s" : NO Checking for function "posix_fallocate" : YES Checking if "GNU qsort_r" : links: YES Header "time.h" has symbol "struct timespec" : YES Checking for function "thrd_create" : YES Header "errno.h" has symbol "program_invocation_name" : YES Header "math.h" has symbol "issignaling" : YES Checking for function "posix_memalign" : YES Checking whether type "struct dirent" has member "d_type" : YES Checking if "strtod has locale support" : links: YES Checking if "Bsymbolic" : links: YES Checking if "version-script" : links: YES Checking if "dynamic-list" : links: YES Compiler for C supports link arguments -Wl,--build-id=sha1: YES Checking for function "dlopen" : YES Checking for function "dladdr" with dependency : YES Checking for function "dl_iterate_phdr" : YES Checking for function "clock_gettime" : YES Found pkg-config: /usr/bin/pkg-config (1.8.1) Run-time dependency zlib found: YES 1.2.13 Run-time dependency libzstd found: YES 1.5.4 Run-time dependency threads found: YES Checking for function "pthread_setaffinity_np" with dependency threads: YES Run-time dependency expat found: YES 2.5.0 Library m found: YES Run-time dependency libdrm found: YES 2.4.114 Run-time dependency libudev found: YES 251 Run-time dependency libelf found: YES 0.188 Run-time dependency valgrind found: NO (tried pkgconfig) Program bison found: YES (/usr/bin/bison) Program bison found: YES 3.8.2 (/usr/bin/bison) Program flex found: YES (/usr/bin/flex) Run-time dependency libunwind found: YES 1.6.2 Run-time dependency x11 found: YES 1.8.4 Run-time dependency xext found: YES 1.3.4 Run-time dependency xfixes found: YES 6.0.0 Run-time dependency xcb-glx found: YES 1.15 Run-time dependency xcb-shm found: YES 1.15 Run-time dependency xcb found: YES 1.15 Found CMake: /usr/bin/cmake (3.25.1) Run-time dependency xcb-keysyms found: NO (tried pkgconfig and cmake) Run-time dependency x11-xcb found: YES 1.8.4 Run-time dependency xcb-dri2 found: YES 1.15 Run-time dependency xcb-dri3 found: YES 1.15 Run-time dependency xcb-present found: YES 1.15 Dependency xcb-shm found: YES 1.15 (cached) Run-time dependency xcb-sync found: YES 1.15 Run-time dependency xshmfence found: YES 1.3 Run-time dependency glproto found: YES 1.4.17 Run-time dependency dri2proto found: YES 2.8 Run-time dependency xxf86vm found: YES 1.1.4 Run-time dependency xcb-xfixes found: YES 1.15 Run-time dependency xcb-randr found: YES 1.15 Run-time dependency xrandr found: YES 1.5.2 Library sensors found: NO Program nm found: YES (/usr/bin/nm) Program symbols-check.py found: YES (/usr/bin/python3 /Dati/mesa/bin/symbols- check.py) Program install_megadrivers.py found: YES (/usr/bin/python3 /Dati/mesa /bin/install_megadrivers.py) Program decode.py found: YES (/Dati/mesa/src/compiler/isaspec/decode.py) Program encode.py found: YES (/Dati/mesa/src/compiler/isaspec/encode.py) Program ln found: YES (/bin/ln) Checking for function "mincore" : YES Build targets in project: 214 mesa 23.3.0-devel Directories prefix : /usr/local libdir : lib/arm-linux-gnueabihf includedir : include Common C and C++ arguments c_cpp_args : -mtls-dialect=gnu2 OpenGL OpenGL : YES ES1 : YES ES2 : YES Shared glapi : YES GLVND : NO DRI Platform : drm Driver dir : /usr/local/lib/arm-linux-gnueabihf/dri GLX Enabled : YES Provider : dri EGL Enabled : YES Drivers : builtin:egl_dri2 builtin:egl_dri3 Platforms : x11 surfaceless drm xcb GBM Enabled : YES Backends path : /usr/local/lib/arm-linux-gnueabihf/gbm Vulkan Drivers : NO Video Codecs : NO APIs : NO LLVM Enabled : NO Gallium Enabled : YES Drivers : lima panfrost kmsro swrast Platforms : x11 surfaceless drm xcb Frontends : mesa Off-screen rendering (OSMesa): NO HUD lm-sensors : NO Perfetto Enabled : NO User defined options gallium-drivers : lima,panfrost,kmsro,swrast llvm : disabled platforms : x11 vulkan-drivers : Found ninja-1.11.1 at /usr/bin/ninja

$ echo "deb-src [signed-by="/usr/share/keyrings/ubuntu-archive-keyring.gpg"] http://ports.ubuntu.com/ubuntu-ports jammy main restricted universe multiverse" >> /etc/apt/sources.list $ sudo apt update $ sudo apt build-dep mesa $ clone https://gitlab.freedesktop.org/mesa/mesa $ cd mesa $ meson build -Dgbm=enabled -Dopengl=true -Degl=enabled -Degl-native-platform=x11 -Dgles1=disabled -Dgles2=enabled -Ddri3=enabled -Dglx=dri -Dllvm=enabled -Dshared-llvm=disabled -Dplatforms=x11,wayland -Dgallium-drivers=swrast,virgl,zink -Dvulkan-drivers=swrast -Dosmesa=true -Dglvnd=true -Dxmlconfig=disabled $ sudo ninja -C build install

Basically there's this one driver for all intel/amd gpus (https://gitlab.freedesktop.org/mesa/mesa) and NVIDIA decided to make their own barely working driver (full of bugs) and also try to make their own standards & protocols instead of using the ones intel/amd have already created

For the curious (I was), I believe this is the associated commit: https://github.com/Mesa3D/mesa/commit/f2e535e4fed5bdc13e11a4...

So you're running Mesa 23 by compiling the code at https://gitlab.freedesktop.org/mesa/mesa/ then?

no it uses amdgpu driver which is build into / part of the kernel (device drivers), and you can use 2 userspace graphics drivers, one being mesa the other one being amdvlk

Good luck, check out https://gitlab.freedesktop.org/mesa/mesa and https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm?h=v6.2-rc1 this is for Linux, but I don't believe that the size of that project, would be different for windows.