ludic/changes/pin-icd-always.md at 314b8ce19430d5a59a5af279bb21a540564e72ee

Orkuncakilkaya 01df9b9d77 runtime (macOS): with a layer asked for, the loader is pinned to our MoltenVK whatever the shell set - the SDK's setup-env.sh exports VK_DRIVER_FILES and VK_ICD_FILENAMES at its own, and the one left set loaded a second MoltenVK; VK_DRIVER_FILES overwritten, VK_ICD_FILENAMES cleared, R3D_VK_ANY_DRIVER=1 to keep the shell's

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-09-30 00:47:07 +03:00

494 B

Raw Blame History

bump: patch type: fix A validation run sees the game's MoltenVK. With a layer asked for, the loader was pinned to ludic.render3d's MoltenVK only when the shell named no driver - but the SDK's setup-env.sh exports both VK_DRIVER_FILES and VK_ICD_FILENAMES at the SDK's own MoltenVK, so a shell with one left set loaded that one beside ours. The pin now overwrites VK_DRIVER_FILES and clears VK_ICD_FILENAMES; R3D_VK_ANY_DRIVER=1 keeps the shell's driver for a run that means to try another.

494 B Raw Blame History

494 B

Raw Blame History