Erfan

> Support is optional for all 5 (host) or all 10 (device and host). If you enable `VK_KHR_acceleration_structure` extension, It enables you to use the device functions. But in order...

> > VkDeviceOrHostAddressConstKHR > > what decides which one this is? > > what function I call? (Cmd vs no Cmd) Yes, Vulkan takes `VkDeviceOrHostAddressConstKHR` for Infos like `VkAccelerationStructureGeometryInstancesDataKHR` or...

> So raytracing requires BDA? Yes, `VK_KHR_ray_tracing_pipeline` requires `VK_KHR_acceleration_structure` and `VK_KHR_acceleration_structure` > Requires Vulkan 1.1 Requires VK_EXT_descriptor_indexing Requires VK_KHR_buffer_device_address Requires VK_KHR_deferred_host_operations See https://www.khronos.org/registry/vulkan/specs/1.2-extensions/man/html/VK_KHR_ray_tracing_pipeline.html

> Do we have any guarantees on whether host commands or device commands will always be available? These CPU-based commands are optional, but the device versions of these commands (vkCmd*)...

> from my reading it looks like host commands are optional, but device commands are always there > > what queue do we need to dispatch the device commands? Good...

> ok so its just like computing mip-maps, just do it on the compute queue. Shouldn't user allocate the command buffer from compute queue and give it to the functions...

> cpu2gpu converter already has this option/works this way Understood

> So no need to worry about that. I believe you're refering to the `Comptability Check` section?

> The most important things for performance are the abilitity to build a single unified AS (no TLAS, everything is one BLAS) with no/little instancing. Note that in Vulkan's Perspective...

> # All the Acceleration Structure flags are REALLY IMPORTANT and should be exposed I agree.