Home
last modified time | relevance | path

Searched refs:micromap (Results 1 – 20 of 20) sorted by relevance

/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_EXT_opacity_micromap/
Dmicromaps.adoc5 [[micromap]] anchor
9 [[micromap-def]]
19 An _opacity micromap_ is a type of micromap which stores information to
20 control intersection opacity as described in <<ray-opacity-micromap,Ray
24 A _displacement micromap_ is a type of micromap which stores information to
25 displace sub-triangle vertices as described in <<displacement-micromap,
29 A micromap is considered to be constructed if a <<micromap-building,micromap
30 build command>> or <<micromap-copying,copy command>> has been executed with
34 [[micromap-building]]
37 [open,refpage='vkCmdBuildMicromapsEXT',desc='Build a micromap',type='protos']
[all …]
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/proposals/
DVK_EXT_opacity_micromap.adoc10 VK_EXT_opacity_micromap adds a micromap object to associate micro-geometry information with geometr…
11 structure as well as a specific application of an opacity micromap to acceleration sub-triangle opa…
38 acceleration structures. The micromap information is defined on the domain of subdivided triangles …
40 with a given subdivision level and format. For an opacity micromap, the micromap contains either 1-…
43 Once the micromap is built an extension structure can attach it to
45 …pping information from each triangle in the geometry to a specified triangle index in the micromap.
61 vkCreateMicromapEXT(device, mmCreateInfo, null, &micromap)
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/appendices/
DVK_EXT_opacity_micromap.adoc33 The opacity micromap compactly encodes opacity information which can be read
42 controls described in <<ray-opacity-micromap,Ray Opacity Micromap>>.
46 * a slink:VkMicromapEXT structure to store the micromap,
48 opacity micromap array, and
51 micromap to the geometry of the acceleration structure.
139 (4) Should there be indirect micromap build?
144 for a micromap.
147 (5) Should micromaps have a micromap device address?
DVK_NV_displacement_micromap.adoc32 * a new elink:VkMicromapTypeEXT format for the displacement micromap,
35 displacement micromap to the geometry of the acceleration structure,
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/commonvalidity/
Dwrite_micromap_properties_common.adoc6 // Common to micromap property query
Dbuild_micromap_common.adoc6 // Common to micromap build commands
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/
Draytraversal.adoc408 If the geometry includes an opacity micromap, the opacity of the
410 <<ray-opacity-micromap,Ray Opacity Micromap>>.
455 [[ray-opacity-micromap]]
459 structure may: have an opacity micromap associated with it to give
463 micromap and ename:VK_GEOMETRY_INSTANCE_DISABLE_OPACITY_MICROMAPS_EXT is not
464 set in its instance then the micromap is used to determine geometry opacity
467 The opacity information in the micromap object is accessed using the
477 image::{images}/micromap-subd.svg[align="center",title="Example ordering for micromap data",align="…
488 The result of the opacity micromap lookup and operations is to treat the
494 If either is set, the opacity micromap information is interpreted in 2 state
[all …]
Daccelstructures.adoc100 micromap information to the update operation.
111 * Change the subdivision level or format of the micromap triangle
116 set in pname:flags, the application must: provide a micromap to the update
120 neither opacity micromap update flag is set the application must: provide
121 the original micromap to the update operation.
130 micromap to the update operation.
133 micromaps and the displacement micromap update flag is not set the
134 application must: provide the original micromap to the update operation.
821 …ctureTrianglesOpacityMicromapEXT',desc='Structure specifying an opacity micromap in a bottom-level…
834 micromap
[all …]
Dresources.adoc6642 equivalent pname:micromap.
6651 an equivalent pname:micromap.
7470 [open,refpage='VkMicromapEXT',desc='Opaque handle to a micromap object',type='handles']
7483 [open,refpage='vkCreateMicromapEXT',desc='Create a new micromap object',type='protos']
7487 To create a micromap, call:
7494 structure containing parameters affecting creation of the micromap.
7498 the resulting micromap object is returned.
7500 Similar to other objects in Vulkan, the micromap creation merely creates an
7502 The type and quantity of geometry that can be built into a micromap is
7505 The micromap data is stored in the object referred to by
[all …]
Dfeatures.adoc5627 …MicromapFeaturesEXT',desc='Structure describing the ray tracing opacity micromap features that can…
5639 * [[features-micromap]] pname:micromap indicates whether the
5640 implementation supports the micromap array feature.
5643 micromap arrays.
5645 whether the implementation supports host side micromap array commands.
5655 …omapFeaturesNV',desc='Structure describing the ray tracing displacement micromap features that can…
5668 whether the implementation supports the displacement micromap feature.
7836 * <<features-micromap, pname:micromap>>, if the
Dsynchronization.adoc505 of <<micromap, micromap commands>>.
899 For opacity micromap build operations, only one pipeline stage occurs, so no
1239 micromap object.
1243 micromap object.
Dpipelines.adoc4832 which reference an opacity micromap array.
4837 which reference a displacement micromap array.
5084 reference an opacity micromap array.
5089 which reference a displacement micromap array.
Dlimits.adoc4064 …iceOpacityMicromapPropertiesEXT',desc='Structure describing the opacity micromap properties of a p…
4089 …cementMicromapPropertiesNV',desc='Structure describing the displacement micromap properties of a p…
/hardware/google/gfxstream/guest/mesa/include/vulkan/
Dvulkan_beta.h800 VkMicromapEXT micromap; member
Dvulkan_core.h16148 VkBool32 micromap; member
16208 VkMicromapEXT micromap; member
16218 typedef void (VKAPI_PTR *PFN_vkDestroyMicromapEXT)(VkDevice device, VkMicromapEXT micromap, const V…
16241 VkMicromapEXT micromap,
/hardware/google/gfxstream/common/vulkan/include/vulkan/
Dvulkan_beta.h805 VkMicromapEXT micromap; member
Dvulkan.hpp4797 …void vkDestroyMicromapEXT( VkDevice device, VkMicromapEXT micromap, const VkAllocationCallbacks * … in vkDestroyMicromapEXT() argument
4799 return ::vkDestroyMicromapEXT( device, micromap, pAllocator ); in vkDestroyMicromapEXT()
Dvulkan_raii.hpp7921 …ESPACE::VULKAN_HPP_RAII_NAMESPACE::Device const & device, VkMicromapEXT micromap, VULKAN_HPP_NAMES… in MicromapEXT() argument
7922 …: m_device( *device ), m_micromap( micromap ), m_allocator( static_cast<const VULKAN_HPP_NAMESPACE… in MicromapEXT()
Dvulkan_hash.hpp8996 VULKAN_HPP_HASH_COMBINE( seed, physicalDeviceOpacityMicromapFeaturesEXT.micromap ); in operator ()()
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/
DChangeLog.adoc201 <<ray-opacity-micromap, Ray Opacity Micromap>> (internal issue 3337).
584 * Add VU to disable ftext:vkCmdBeginQuery* with micromap queries (internal
1477 * Clarify language for acceleration structure and micromap scratch access