KhronosGroup / KhronosGroup/Vulkan-Profiles

vkGetPhysicalDevice*Properties functions don't have a way to return anything

Open
#341 0 comments 0 reactions 1 assignee View on GitHub

@christophe-lunarg is already working on this.

Since Aug 21, 2025.

Definition enhancement future Layer Library OS - Platform Independent P2
Dominant language
Python
Stars
176
Forks
84
Avg merge
9h 34m
Merged PRs (30d)
37

Description

some functions such as vkGetPhysicalDeviceImageFormatProperties or vkGetPhysicalDeviceMultisamplePropertiesEXT don't have a way for the Profiles system to capture and return back a value

Example:

the VkPhysicalDeviceSampleLocationsPropertiesEXT is the "minimum value" , so for example VkPhysicalDeviceSampleLocationsPropertiesEXT::maxSampleLocationGridSize might be (2, 2) which means it is that for all sample counts, but using the function you may find that the VK_SAMPLE_COUNT_8_BIT actually supports a VkMultisamplePropertiesEXT::maxSampleLocationGridSize up to (4, 4)

Use Case:

Currently the desired use case for this is the Validation Layers testing to be able to simulate this aspect of a driver, for now it might be a better solution to add this logic in the MockICD driver instead, but opening issue for future discussions/considerations

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.