| Safe Haskell | None |
|---|---|
| Language | Haskell2010 |
Vulkan.Extensions.VK_KHR_ray_query
Description
Name
VK_KHR_ray_query - device extension
VK_KHR_ray_query
- Name String
VK_KHR_ray_query
- Extension Type
- Device extension
- Registered Extension Number
- 349
- Revision
- 1
- Extension and Version Dependencies
- Requires Vulkan 1.1
- Requires
VK_KHR_spirv_1_4 - Requires
VK_KHR_acceleration_structure
- Contact
Other Extension Metadata
- Last Modified Date
- 2020-11-12
- Interactions and External Dependencies
- This extension requires SPV_KHR_ray_query
- This extension provides API support for GLSL_EXT_ray_query
- Contributors
- Matthäus Chajdas, AMD
- Greg Grebe, AMD
- Nicolai Hähnle, AMD
- Tobias Hector, AMD
- Dave Oldcorn, AMD
- Skyler Saleh, AMD
- Mathieu Robart, Arm
- Marius Bjorge, Arm
- Tom Olson, Arm
- Sebastian Tafuri, EA
- Henrik Rydgard, Embark
- Juan Cañada, Epic Games
- Patrick Kelly, Epic Games
- Yuriy O’Donnell, Epic Games
- Michael Doggett, Facebook/Oculus
- Andrew Garrard, Imagination
- Don Scorgie, Imagination
- Dae Kim, Imagination
- Joshua Barczak, Intel
- Slawek Grajewski, Intel
- Jeff Bolz, NVIDIA
- Pascal Gautron, NVIDIA
- Daniel Koch, NVIDIA
- Christoph Kubisch, NVIDIA
- Ashwin Lele, NVIDIA
- Robert Stepinski, NVIDIA
- Martin Stich, NVIDIA
- Nuno Subtil, NVIDIA
- Eric Werness, NVIDIA
- Jon Leech, Khronos
- Jeroen van Schijndel, OTOY
- Juul Joosten, OTOY
- Alex Bourd, Qualcomm
- Roman Larionov, Qualcomm
- David McAllister, Qualcomm
- Spencer Fricke, Samsung
- Lewis Gordon, Samsung
- Ralph Potter, Samsung
- Jasper Bekkers, Traverse Research
- Jesse Barker, Unity
- Baldur Karlsson, Valve
Description
Rasterization has been the dominant method to produce interactive graphics, but increasing performance of graphics hardware has made ray tracing a viable option for interactive rendering. Being able to integrate ray tracing with traditional rasterization makes it easier for applications to incrementally add ray traced effects to existing applications or to do hybrid approaches with rasterization for primary visibility and ray tracing for secondary queries.
Ray queries are available to all shader types, including graphics, compute and ray tracing pipelines. Ray queries are not able to launch additional shaders, instead returning traversal results to the calling shader.
This extension adds support for the following SPIR-V extension in Vulkan:
SPV_KHR_ray_query
New Structures
New Enum Constants
KHR_RAY_QUERY_SPEC_VERSIONExtending
StructureType:
New SPIR-V Capabilities
Sample Code
Example of ray query in a GLSL shader
rayQueryEXT rq;
rayQueryInitializeEXT(rq, accStruct, gl_RayFlagsNoneEXT, 0, origin, tMin, direction, tMax);
while(rayQueryProceedEXT(rq)) {
if (rayQueryGetIntersectionTypeEXT(rq, false) == gl_RayQueryCandidateIntersectionTriangleEXT) {
//...
rayQueryConfirmIntersectionEXT(rq);
}
}
if (rayQueryGetIntersectionTypeEXT(rq, true) == gl_RayQueryCommittedIntersectionNoneEXT) {
//...
}Issues
- What are the changes between the public provisional (VK_KHR_ray_tracing v8) release and the final (VK_KHR_acceleration_structure v11 / VK_KHR_ray_query v1) release?
refactor VK_KHR_ray_tracing into 3 extensions, enabling implementation flexibility and decoupling ray query support from ray pipelines:
- VK_KHR_acceleration_structure (for acceleration structure operations)
- VK_KHR_ray_tracing_pipeline (for ray tracing pipeline and shader stages)
- VK_KHR_ray_query (for ray queries in existing shader stages)
- Update SPIRV capabilities to use
RayQueryKHR - extension is no longer provisional
Version History
Revision 1, 2020-11-12 (Mathieu Robart, Daniel Koch, Andrew Garrard)
- Decomposition of the specification, from VK_KHR_ray_tracing to VK_KHR_ray_query (#1918,!3912)
- update to use
RayQueryKHRSPIR-V capability - add numerical limits for ray parameters (#2235,!3960)
- relax formula for ray intersection candidate determination (#2322,!4080)
- restrict traces to TLAS (#2239,!4141)
- require
HitTto be in ray interval forOpRayQueryGenerateIntersectionKHR(#2359,!4146) - add ray query shader stages for AS read bit (#2407,!4203)
See Also
PhysicalDeviceRayQueryFeaturesKHR
Document Notes
For more information, see the Vulkan Specification
This page is a generated document. Fixes and changes should be made to the generator scripts, not directly.
Synopsis
- data PhysicalDeviceRayQueryFeaturesKHR = PhysicalDeviceRayQueryFeaturesKHR {}
- type KHR_RAY_QUERY_SPEC_VERSION = 1
- pattern KHR_RAY_QUERY_SPEC_VERSION :: forall a. Integral a => a
- type KHR_RAY_QUERY_EXTENSION_NAME = "VK_KHR_ray_query"
- pattern KHR_RAY_QUERY_EXTENSION_NAME :: forall a. (Eq a, IsString a) => a
Documentation
data PhysicalDeviceRayQueryFeaturesKHR Source #
VkPhysicalDeviceRayQueryFeaturesKHR - Structure describing the ray query features that can be supported by an implementation
Members
This structure describes the following feature:
Description
If the PhysicalDeviceRayQueryFeaturesKHR structure is included in the
pNext chain of the
PhysicalDeviceFeatures2
structure passed to
getPhysicalDeviceFeatures2,
it is filled in to indicate whether each corresponding feature is
supported. PhysicalDeviceRayQueryFeaturesKHR can also be used in the
pNext chain of DeviceCreateInfo to selectively
enable these features.
Valid Usage (Implicit)
See Also
Constructors
| PhysicalDeviceRayQueryFeaturesKHR | |
Instances
type KHR_RAY_QUERY_SPEC_VERSION = 1 Source #
pattern KHR_RAY_QUERY_SPEC_VERSION :: forall a. Integral a => a Source #
type KHR_RAY_QUERY_EXTENSION_NAME = "VK_KHR_ray_query" Source #
pattern KHR_RAY_QUERY_EXTENSION_NAME :: forall a. (Eq a, IsString a) => a Source #