Sorting in Vulkan any extension not perfect
Opened this issue · 5 comments
Sorting in Vulkan any extension not perfect
Khronos first with khr ist ok.
EXT is here next.
But then there is some chaos.
sorting in OpenGL extensions is alphabetically.
Can you give some examples?
From what I see it follows the order in features.txt
in Extensions that are not part of any Vulkan Version.
An example:
VK_KHR_Map_Memory2 is last in table.
VK_Google is before VK_AMD
mostly VK_KHR are at the begin of the table.
so it is partly sorted, and features are added at the end without new sorting.
Yes, it's kinda intentional actually.
As you can see here, the extensions aren't sorted in the original features.txt file and Mesamatrix simply follows the same order.
I could sort the extensions alphabetically, but I don't know how much this order is important in the original file...
Khronos with KHR is first and EXT is second priority for the Mesa Guys in development.
And then alphabetical of the others in sorting is logic.
They will do little action and sort, if you give them a hint or issue.
I'd rather the source being changed upstream instead of arbitrarily change the order in Mesamatrix. I'm not expert enough in 3d drivers programming to know which extensions should be higher up in the list, also, it could change without me knowing, and also it's no regular sorting (KHR, then EXT, then the rest).
I think it would be better to open an issue in mesa and ask the devs if they would be willing to re-order the extensions in features.txt (or if they have a preferred sorting order that they'd like to see in Mesamatrix)