Spencer Fricke
Spencer Fricke
https://github.com/KhronosGroup/SPIRV-Tools/pull/5458 shows a failure with `Test/hlsl.format.rwtexture.frag` and shows ``` Failing ToSpirv/HlslCompileTest.FromFile/hlsl_format_rwtexture_frag error: [VUID-StandaloneSpirv-Image-04965] Image Format type (float or int) does not match Sample Type operand %42 = OpTypeImage %int 1D...
The argument says > -ps -- Parse input files, create pipelines; Don't execute. but if I run `amber tests/cases/draw_rect.amber -ps --log-graphics-call` it is never calling `vkCreateGraphicsPipelines` like I would expect...
closes https://github.com/KhronosGroup/Vulkan-Guide/issues/252
(I don't have a good way to reproduce this, so **please feel free** to close this issue if you find it not possible to fix easily or something not supported......
For https://github.com/KhronosGroup/Vulkan-Docs/issues/2276 (internal spec change https://gitlab.khronos.org/vulkan/vulkan/-/merge_requests/6666) The following case was never being validated ``` vkCmdSet() vkCmdBindPipeline() // static vkCmdBindPipeline() // dynamic vkCmdDraw() ``` This also adds better error messaging to...
Some Settings in GPU-AV don't work in vkconfig example: `const char *VK_LAYER_GPUAV_VALIDATE_INDIRECT_TRACE_RAYS_BUFFERS = "gpuav_indirect_trace_rays_buffers";` I tried to used `VK_LAYER_GPUAV_VALIDATE_INDIRECT_TRACE_RAYS_BUFFERS=0` but wasn't working... realize the `_VALIDATE_` is not part of the...
`DISABLED_MaxFragmentDualSrcAttachmentsDynamicBlendEnable` was added to test to using dynamic blend state to test for `VUID-RuntimeSpirv-Fragment-06427` to fix https://github.com/KhronosGroup/Vulkan-ValidationLayers/issues/5199 this is still not working. The current issue is managing the interactions with...
Same idea as `PositiveGpuAVOOB/VertexFragmentMultiEntrypoint`/`NegativeGpuAVOOB.VertexFragmentMultiEntrypoint` (from https://github.com/KhronosGroup/Vulkan-ValidationLayers/pull/7778/files) We should add a simple RTX test in `PositiveGpuAVRayTracing`/`NegativeGpuAVRayTracing` to test we handle this correctly The biggest issue is the `rt::Pipeline::SetRayGenShader` test framework interface...
These VUs we already have in `vkCmdBuildAccelerationStructuresKHR` and think they are just simply missing a case from the other 2 calls - [x] VUID-vkBuildAccelerationStructuresKHR-pInfos-03675 - [x] VUID-vkBuildAccelerationStructuresKHR-pInfos-03668 - [x] VUID-vkBuildAccelerationStructuresKHR-pInfos-03761...
Add support for - VUID-RuntimeSpirv-OpRayQueryInitializeKHR-06352 - VUID-RuntimeSpirv-OpTraceRayKHR-06359 As described in https://gitlab.khronos.org/vulkan/vulkan/-/issues/3799 these VUs should report 1. When trying to access, the AS has not been built yet 2. If it...