lucannez64andClaude Opus 5.5 1c30c99e51 Prefer VRAM for GPU-only Metal memory and mark the GL import dedicated ...

Indium and QuartzCore took the first memory type a resource allowed. The
Vulkan spec orders a type with no flags before every DEVICE_LOCAL type,
and NVIDIA exposes such system-RAM types, so on NVIDIA private buffers,
textures and framebufferOnly drawables could land in system RAM. They
now take the first allowed DEVICE_LOCAL type and fall back to the old
choice; shared and managed resources are unchanged.

The drawable's exported image is a dedicated Vulkan allocation, but the
OpenGL import never set GL_DEDICATED_MEMORY_OBJECT_EXT, which
EXT_external_objects requires. Mesa ignores it; it is the suspected
cause of the black screen on NVIDIA in issue #3. The import's GL errors
were never checked (reportGLErrors is compiled out), so a failure was
silent.

/tmp/metal-device.log now lists the selected device's memory heaps and
types, the memory type chosen per resource kind (with the old choice and
changed=yes/no), and the result of the first drawable and semaphore
imports into OpenGL (later ones only on failure).

Practice match on the RX 6600: all choices changed=no, import
dedicated=yes with no GL errors, semaphore ok, match=yes. Not run on
NVIDIA.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

2026-10-16 02:04:43 +02:00

..

SETUP.md

Log the Metal GPU and create a Vulkan device only for it

2026-10-16 00:24:58 +02:00

STATUS.md

Remove Riot client/game automation, inspection and capture tooling

2026-10-15 13:00:01 +02:00

TESTING.md

Keep Iridium LLVM headers and runtime library on the same major

2026-10-15 23:22:15 +02:00

TROUBLESHOOTING.md

Prefer VRAM for GPU-only Metal memory and mark the GL import dedicated

2026-10-16 02:04:43 +02:00