AAA Gaming on Asahi Linux

Overall reaction & technical achievement

  • Commenters are impressed that fully reverse‑engineered, open GPU and x86 layers on Apple Silicon can now run many AAA Windows games on Linux.
  • The stack combines x86 translation (e.g., FEX), DirectX→Vulkan translation, and a VM to cope with 4K vs 16K page sizes, yet still reaches playable performance.
  • Some highlight this as evidence of how far Linux gaming and translation layers (Wine/Proton‑style tech) have come.

Performance, overhead, and limits

  • Newer AAA titles often don’t hit 60 fps; emulation and virtualization add CPU, GPU, and RAM overhead.
  • 16 GB of RAM is described as a practical minimum because games run inside a VM to fix page‑size assumptions.
  • Emulation overhead and page‑size workarounds can cause noticeable memory pressure on lower‑RAM machines.
  • Some games run better on Asahi than via macOS tools in specific anecdotes; others report the opposite.

Asahi vs macOS (Game Porting Toolkit, Crossover, Whisky)

  • Several argue macOS with Apple’s Game Porting Toolkit, Crossover, and Whisky still offers broader game compatibility, more features (e.g., ray tracing), and less overhead today.
  • Others report poor experiences on macOS (visual glitches, low fps) and significantly better results on Asahi for particular titles.
  • Consensus: Asahi’s achievement is big, but macOS + existing tools generally remains ahead for Apple‑hardware gaming right now.

Apple GPU architecture, Vulkan, and Metal

  • Discussion of missing hardware tessellation and geometry shaders on Apple GPUs; these are emulated with compute or mesh shaders.
  • This complicates Vulkan and certain emulators; some see this as a reason Apple prefers Metal and avoids official Vulkan.
  • Opinions split on whether this is mostly technical (API design, die area, developer experience) or mainly about platform lock‑in.

Hardware support and project priorities

  • Users lament slow progress on M3/M4 support, DP‑alt‑mode, Thunderbolt, and microphones compared to the fast graphics advances.
  • Others note different contributors work on different subsystems; lack of progress in some areas reflects who shows up, not simple priority trade‑offs.
  • M3/M4 GPUs differ significantly (new instruction encodings, ray tracing, “dynamic caching”), so support will take time; lack of an M3 Mac mini also hurts CI.

Distros, ecosystem, and philosophy

  • Fedora Asahi Remix is the “first‑class” target; NixOS and Arch can work but require more manual effort, especially for the newest gaming stack.
  • Broader discussion touches on Proton’s role in making Linux gaming viable vs native ports, and on why Linux users still want access to Windows‑only games.
  • Some debate ARM vs x86 efficiency; claims conflict and are left unresolved in the thread.

Referrer and HN‑specific behavior

  • Side discussion about the project site previously serving an anti‑HN page based on HTTP referrer.
  • This leads to explanations of the Referer/Referrer‑Policy mechanisms and privacy trade‑offs; some consider referrer‑based blocking childish but technically straightforward.