#
✕ nick:alyssa
#asahi-gpu · 2026-09-27 16:59
alyssaI thought dougallj already r/e'd those instructions, just needs wiring up (which is seriously nontrivial)
#asahi-gpu · 2026-08-26 01:16
alyssaaccording to https://www.pcgamingwiki.com/wiki/No_Man's_Sky#API it's a native Vulkan title on windows (not DXVK)
#asahi-gpu · 2026-08-26 01:15
alyssasorry, sloppy language on my part
#asahi-gpu · 2026-08-26 01:15
alyssawaltmck: By Proton I meant DXVK / vkd3d-proton
#asahi-gpu · 2026-08-25 23:15
alyssabut it's not clear to me what exactly the least incorrect patch would be
#asahi-gpu · 2026-08-25 23:15
alyssawaltmck: also worst case, we could upstream a driconf for the game
#asahi-gpu · 2026-08-25 22:45
alyssawaltmck: Proton games are all broken in the same way, native Vulkan games are each broken in their own unique and special way :p
#asahi-gpu · 2026-08-25 19:58
alyssawaltmck: presumbaly the first 32k queries will work and the rest will not
#asahi-gpu · 2026-08-25 15:35
alyssaHope this helps
#asahi-gpu · 2026-08-25 15:33
alyssaThe relevant limit is "Maximum visibility query offset", which on all M1-M5 chips is 256 KB = 32k queries at 64-bits each
#asahi-gpu · 2026-08-25 15:32
alyssaSee https://developer.apple.com/metal/Metal-Feature-Set-Tables.pdf
#asahi-gpu · 2026-08-25 15:24
alyssawhich comes out to 16k/32k queries depending if 32-bit/64-bit
#asahi-gpu · 2026-08-25 15:24
alyssa#define PVR_SUBALLOCATOR_VIS_TEST_SIZE (128 * 1024)
#asahi-gpu · 2026-08-25 15:24
alyssaYou'll see the powervr vk driver has a similar limit, in the form of:
#asahi-gpu · 2026-08-25 15:22
alyssa(the hardware pool)
#asahi-gpu · 2026-08-25 15:22
alyssa& yes, this is unusual, a bad design inherited from PowerVR
#asahi-gpu · 2026-08-25 15:20
alyssa& I never saw a workload needing more than that anyway
#asahi-gpu · 2026-08-25 15:20
alyssa(not impossible but complicated + perf impacts)
#asahi-gpu · 2026-08-25 15:20
alyssaso hk limits to 32k occlusion queries VkDevice-wide, because doing otherwise would require major shenanigans
#asahi-gpu · 2026-08-25 15:18
alyssaso architecturally M1 can only do 32k queries in a hardware pool
#asahi-gpu · 2026-08-25 15:18
alyssa </struct>
#asahi-gpu · 2026-08-25 15:18
alyssa <field name="Index" size="15" start="17" type="uint"/>
#asahi-gpu · 2026-08-25 15:18
alyssa <!-- 64-bit index into occlusion result buffer -->
#asahi-gpu · 2026-08-25 15:18
alyssa <struct name="Fragment occlusion query" size="4">
#asahi-gpu · 2026-08-25 15:18
alyssawaltmck:
#asahi-gpu · 2026-07-31 15:53
alyssaThanks haha
#asahi-gpu · 2026-07-31 15:27
alyssaOf course
#asahi-gpu · 2026-07-31 15:24
alyssasomebody thought it was funny to have multiple Asahi Alyssa's affiliated with Intel
#asahi-gpu · 2026-07-31 15:24
alyssasobek[m]: as I understand that's why she started work on Asahi
#asahi-gpu · 2026-07-31 15:22
alyssanoopwafel: ^
#asahi-gpu · 2026-07-31 15:22
alyssaAlyssa Milburn had a branch somewhere
#asahi-gpu · 2026-07-31 15:22
alyssajannau: it turns out "they don't"
#asahi-gpu · 2026-07-10 13:54
alyssanot sure
#asahi-gpu · 2026-07-10 12:30
alyssahttps://www.khronos.org/blog/an-introduction-to-vulkan-video
#asahi-gpu · 2026-07-10 11:27
alyssacloc mesa/src/intel/compiler/jay
#asahi-gpu · 2026-07-10 11:23
alyssachaos_princess: it'll circle back here if someone ever does vulkan video :P
#asahi-gpu · 2026-07-09 19:26
alyssa(M3 kernel I mean)
#asahi-gpu · 2026-07-09 19:26
alyssaMain reason I didn't touch M3 when I was still active in the project was just that nobody else was seriously working on kernel stuff at the time and, well, 2025 was a hard year for all of us
#asahi-gpu · 2026-07-09 19:26
alyssaand that's all common code in Mesa now and all of that will Just Work on future platforms
#asahi-gpu · 2026-07-09 19:25
alyssaHonestly one of the biggest challenges was just geometry/tessellation emulation
#asahi-gpu · 2026-07-09 19:21
alyssaso I guess in a sense, StanfordAppliedCyber[m] noopwafel chaos_princess are all right in a way :)
#asahi-gpu · 2026-07-09 19:20
alyssaIf all the r/e was done, I expect the mesa side for m3 to be a few months to get something reasonbale, since you're building on top of years of my m1 work
#asahi-gpu · 2026-07-09 19:19
alyssait's not that gpu drivers are horribly impenetrable, it's just there's a metric ton of random details & rare features that you do need to support for conformance
#asahi-gpu · 2026-07-09 19:19
alyssaStanfordAppliedCyber[m]: writing enough Mesa code to spin cubes took me a few weeks while I was in school. writing enough to play D3D games at good speed took years
#asahi-gpu · 2026-07-09 19:18
alyssam1/m2 are basically the same, m3/m4 basically the same, m5 new but one would reasonably assume m6 will be close
#asahi-gpu · 2026-07-09 19:17
alyssaagx seems to follow a tick/tock cadence
#asahi-gpu · 2026-07-08 14:13
alyssaIntel indeed
#asahi-gpu · 2026-07-08 14:08
alyssaNeat
#asahi-gpu · 2026-07-08 11:35
alyssaI'd think until the hv issues are sorted looking into m4/a18 is kinda futile?
#asahi-gpu · 2026-05-26 17:45
alyssaand I believe I explained at the time what you needed to do to fix your issue

plus ›