Mark Young
Mark Young
I have seen the same issue in my own personal shader. In my case, though, the value was a `uint` not used by a loop but that was only used...
Weird, I thought I had put the source location in there... [My Fork of Sascha's Vulkan samples)[https://github.com/MarkY-LunarG/Vulkan] Branch: marky_move_raytrace_reflect_to_desc_templates
If we implement it as a layer, we are planning on this being lower (closer to the Implementation). But that will either take forcing the loading location in the loader...
Actually, my proposal is to allow users to filter themselves. By default, it will not filter just sort. I plan to release a doc internal soon on my sorting algorithm...
The option is there to force a device first using the new `VK_LOADER_DEVICE_SELECT` option which you set with vendorID hex value ":" deviceID hex value. Just like the Mesa device...
Linux consistent sorting enabled
This is something we're looking at starting in about a month or two. We have already started designing it, but are going through internal discussions on making it as clean...
First, sorry, this actually got dropped in priority as we were working on other items. > Who would choose the integers? The system integrator or the layers' developers? The layer...
Closing to re-open moving to Gradle 8.1
Rebased the changes and did a cleanup change on top afterwards to remove some extra if's and branching.