bradgrantham-lunarg

Is reproducing this as simple as "XR_ENABLE_API_LAYERS=XR_APILAYER_LUNARG_core_validation;XR_APILAYER_LUNARG_core_validation"? It's not clear from https://github.com/KhronosGroup/OpenXR-SDK-Source/pull/155 what precipitates the issue. It's conceivable that someone could do, e.g. "XR_ENABLE_API_LAYERS=XR_APILAYER_LUNARG_api_dump;SOME_WEIRD_LAYER;XR_APILAYER_LUNARG_api_dump" (i.e. layer enabled twice _on purpose_...

Yeah, I'm not sure it is a valid use case after thinking about it. They both read the same environment variable for the type and destination of the output -...

Layers appear to be enabled in the order they are discovered in manifests. That is to say, if there are no implicit layers, and then `XR_API_LAYER_PATH=location-of-layer-B-manifest;location-of-layer-A-manifest` and `XR_ENABLE_API_LAYERS=layer-A;layer-B`, layerB is...

An issue (number 1531) has been filed in the internal Khronos GitLab, to correspond to the new issue relating to order of API layer load and initialization. If you have...

> https://github.com/KhronosGroup/Vulkan-Samples/actions/runs/8381317875/workflow?pr=887 > The CI output is utterly useless. It's a gigantic one liner that tells you roughly where the problem is, but not not WHAT it actually is. It...

We have clang-format in https://github.com/LunarG/gfxreconstruct CI GH Actions and I regularly cut-and-paste the diff reported in our CI (e.g. https://github.com/LunarG/gfxreconstruct/actions/runs/8354729132/job/22868539456) as a patch to fix clang-format on my machine. It's...

Yaman no longer is available at that login. We probably won't carry forward this PR, we don't have any resource to handle the long to-do list. We noted this failure...