Fixing VkGetPhysicalDeviceCooperativeMatrix Missing Wrapper

Introduction

This article addresses the issue of a missing wrapper for the Vulkan function vkGetPhysicalDeviceCooperativeMatrixFlexibleDimensionsPropertiesNV. This problem was encountered while using DXVK 1.10.3 and Proton 10.2 on a Raspberry Pi 5 running the latest vanilla ARM64 Trixie. The error manifests as a warning message indicating the absence of a wrapper for the specified function, followed by an assertion failure in winevulkan.dll and subsequent failures of Vulkan calls. Let’s dive into the details of the issue, its potential causes, and possible solutions.

Understanding the Issue: Missing Vulkan Function Wrapper

The core problem revolves around the Vulkan function wrapper vkGetPhysicalDeviceCooperativeMatrixFlexibleDimensionsPropertiesNV not being available. This function is related to the VK_KHR_cooperative_matrix extension, which allows for more efficient matrix operations on compatible hardware. However, in this specific scenario, the GPU in question does not support this extension in hardware. This raises a critical question: why is the absence of the wrapper causing such significant issues if the extension isn't even supposed to be in use?

When a Vulkan application attempts to call a function, it relies on a wrapper to interface with the underlying Vulkan implementation. If the wrapper is missing, the application cannot properly invoke the function, leading to errors and potentially crashes. In this case, the warning message "Warning, no wrapper for vkGetPhysicalDeviceCooperativeMatrixFlexibleDimensionsPropertiesNV" clearly indicates that the wrapper is absent. The subsequent assertion failure in winevulkan.dll further confirms the severity of the problem. The error message !status being false at ../src-wine/dlls/winevulkan/loader.c:372 suggests that the function loading or initialization process within Wine's Vulkan implementation has failed.

The Specific Scenario: Raspberry Pi 5 and Dead Space.exe

This issue was observed on a Raspberry Pi 5, a popular single-board computer, running the latest vanilla ARM64 Trixie operating system. The user was attempting to run the game Dead Space.exe using Proton, a compatibility layer that allows Windows games to run on Linux. DXVK, a Vulkan-based translation layer for Direct3D 9/10/11, was also in use. This combination of software and hardware provides a complex environment where various components interact to enable gaming on non-Windows platforms.

The fact that the GPU does not support VK_KHR_cooperative_matrix in hardware adds another layer to the puzzle. Ideally, if the extension is not supported, the application should gracefully handle the absence of the feature or use alternative methods. However, the assertion failure and subsequent Vulkan call failures indicate that the application or a component within the graphics stack is not handling this situation correctly. This could be due to a bug in the application, DXVK, Proton, or the Vulkan implementation itself.

Potential Causes and Solutions

Several factors could contribute to the missing wrapper issue. Let's explore some of the most likely causes and potential solutions:

1. Incomplete or Corrupted Vulkan Installation

One possibility is that the Vulkan installation on the Raspberry Pi 5 is incomplete or corrupted. This could result in some function wrappers being missing. To address this, you can try the following:

• Reinstall Vulkan: Ensure that Vulkan is properly installed on your system. You can typically do this through your distribution's package manager. For Debian-based systems like Trixie, you might use apt to reinstall the necessary Vulkan packages.
• Verify Vulkan Installation: Use tools like vulkaninfo to verify that Vulkan is installed correctly and that the necessary extensions are supported. This tool can provide detailed information about your Vulkan setup, including the available extensions and function pointers.

2. Driver Issues

Vulkan relies heavily on drivers to interface with the GPU. Outdated or faulty drivers can lead to various issues, including missing function wrappers. To resolve this, consider the following steps:

• Update Drivers: Ensure that you are using the latest drivers for your GPU. On a Raspberry Pi 5, this might involve updating the Mesa drivers, which provide open-source graphics drivers for Linux. You can typically update drivers through your distribution's package manager or by using a dedicated driver update tool.
• Try Different Driver Versions: In some cases, the latest drivers might not be the most stable. If you are experiencing issues with the latest drivers, try using an older version that is known to be more reliable.

3. DXVK or Proton Bugs

DXVK and Proton are complex software projects, and bugs can occasionally occur. It's possible that a bug in either of these components is causing the missing wrapper issue. To investigate this possibility, you can:

• Update DXVK and Proton: Make sure you are using the latest versions of DXVK and Proton. Newer versions often include bug fixes and improvements that can address compatibility issues.
• Report the Issue: If you suspect a bug in DXVK or Proton, report the issue to the respective project's issue tracker. This allows the developers to investigate the problem and potentially provide a fix.

4. Winevulkan.dll Problem

The error message specifically mentions winevulkan.dll, which is a part of Wine's Vulkan implementation. This suggests that there might be an issue with this particular DLL. Potential solutions include:

• Reinstall Wine: Reinstalling Wine might help replace any corrupted or missing files, including winevulkan.dll.
• Check Wine Configuration: Ensure that Wine is configured correctly to use Vulkan. You might need to adjust Wine settings to prioritize Vulkan over other graphics APIs.

5. Application-Specific Issue

It's also possible that the issue is specific to the game Dead Space.exe or its interaction with the graphics stack. In this case, you can try:

• Check Game Compatibility: Verify that the game is known to be compatible with Proton and DXVK. Consult online resources and community forums to see if other users have encountered similar issues and if any workarounds are available.
• Try Different Compatibility Settings: Proton offers various compatibility settings that can be adjusted to improve game performance and stability. Experiment with different settings to see if any of them resolve the issue.

Attempting WineD3D as an Alternative

The user also mentioned attempting to use WineD3D as an alternative rendering backend. WineD3D translates Direct3D calls to OpenGL instead of Vulkan. However, they encountered an issue where WineD3D failed to load libvkd3d-1.dll and libvkd3d-shader-1.dll, even though both files were present. This suggests a problem with WineD3D's configuration or its ability to locate the necessary libraries.

Addressing WineD3D Issues

• Ensure WineD3D is Properly Installed: Verify that WineD3D is installed correctly and that the necessary libraries are in the correct locations. You might need to install additional packages or configure Wine to use WineD3D as the default rendering backend.
• Check Library Paths: Ensure that Wine can find the libvkd3d-1.dll and libvkd3d-shader-1.dll files. You might need to adjust the LD_LIBRARY_PATH environment variable or Wine's library search paths to include the directory containing these files.

Conclusion

The missing wrapper for vkGetPhysicalDeviceCooperativeMatrixFlexibleDimensionsPropertiesNV is a complex issue that can stem from various sources, including Vulkan installation problems, driver issues, bugs in DXVK or Proton, or application-specific problems. By systematically investigating potential causes and trying the suggested solutions, you can hopefully resolve this issue and get your application or game running smoothly. Remember to keep your system and software up to date, and don't hesitate to consult online resources and community forums for further assistance.

For more information on Vulkan and its extensions, you can visit the Khronos Group's official Vulkan website.