Andreas Süßenbach comments

Results 120 comments of


                                            Andreas Süßenbach

Vulkan-Headers CI tests failing against current Vulkan-Docs branch

@oddhack I think, I fixed this issue with #2236. But the build ([cmake-unix (ubuntu-latest, 3.22.1)](https://github.com/KhronosGroup/Vulkan-Headers/actions/runs/16665329727/job/47343465545#logs) is still failing! I don't know, how the generation of the Vulkan-Hpp files could be...

Fix vector size for presentCompleteSemaphores.

> but tutorial text needs to be adjusted to If you could give me a hint, where the corresponding tutorial text is, I could try to adjust it accordingly.

Fix vector size for presentCompleteSemaphores.

@SaschaWillems Ok, I've adjusted some documentation. Please have a closer look at it!

Fix vector size for presentCompleteSemaphores.

Anything else I'd need to adjust?

shader_debugprintf: support new VVL-DEBUG-PRINTF message and fix VVL version check for API selection

AFAIK, those two extensions (`VK_EXT_layer_settings` and `VK_EXT_validation_features`) are not supported by any NVIDIA GPU, but are provided by a layer injected by for example the VulkanConfigurator. That might explain why...

Split helper classes into separate header files

`ArrayProxy` and `Flags` could probably be moved into some `vulkan_hpp_helper_classes.hpp`, or so. But do you mean `ResultValue` with `Result`? That class uses `vk::Result`, which means you would need at least...

Update/merge Vulkan-Video C++ named module with main C++ named module

> My thought is to combine (2) and (3). I thinks, that's a viable approach. Would you create a PR resolving this?

const-ref for optional allocator arguments?

Thanks for reporting this issue. I'll have a closer look at it asap, but that still might take a little. But at first sight, it sounds reasonable.

const-ref for optional allocator arguments?

@rwols Would you like to check if #2386 actually resolves this issue?

Validation layer warnings on ray tracing samples

I don't know where that `OpTypeImage`, mentioned in the VVL warning above comes from, or how I could change that to some bgra-format. The warning is resolved if I -...