Mesa introduces common Vulkan layer to handle cross-driver game engine workarounds

Mesa developers have merged a new common Vulkan layer into the Mesa 27.0-devel branch. This infrastructure is designed to host workarounds for bugs found in specific games, engines, or applications that affect multiple Vulkan drivers simultaneously.

By moving these fixes into the Mesa Vulkan Runtime rather than duplicating them in individual drivers, the project can more efficiently handle non-compliant API usage. The initial implementation targets the RADV and NVK drivers, providing a centralized way to intercept and correct invalid calls before they reach the hardware-specific driver logic.

Unified driver workarounds in Mesa

• Shared Infrastructure: The new layer resides within the Mesa Vulkan Runtime, allowing drivers to opt-in to centralized fixes for application-level bugs.
• Initial Driver Support: The Radeon RADV and NVIDIA NVK drivers are the first to utilize this common layer for handling cross-driver issues.
• API Compliance Fixes: The layer is being used to resolve a specific issue in Metro Exodus where the game passes NULL to pWaitSemaphores, which violates the Vulkan API specification.
• Development Origin: The work was contributed by Valve developer Samuel Pitoiset to streamline how Mesa handles illegal application behavior.

Why it matters

This change improves stability for Linux gamers by ensuring that broken game engine implementations do not require redundant, driver-specific patches. It simplifies the maintenance burden for developers of drivers like RADV and NVK when addressing widespread software bugs.