m k      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuv w x y z { | } ~                          !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNO P Q R S T U V W X Y Z [!\!]"^"_#`#a$b$c$d$e$f$g$h$i$j$k$l$m$n$o$p$q$r$s$t$u$v$w%x%y%z%{%|%}%~%%%%%%%%%%%%%%%%%%%%%%%%%%%%&&'''(())**********************************************+,,,,,-----.//////////////////////////////////////////// / / / / /////////////////// /!/"/#/$/%/&/'/(/)/*/+/,/-/.///0/1/2/3/4/5/6/7/8/9/:/;/</=/>/?/@/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/[/\/]/^/_/`/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/{/|/}/~/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// / / / / /////////////////// /!/"/#/$/%/&/'/(/)/*/+/,/-/.///0/1/2/3/4/5/6/7/8/9/:/;/</=/>/?/@/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/[/\/]/^/_/`/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/{/|/}/~//////////////////////////////////////////////////////////////////////////00000000000000000000000000000000000000011111111111111111111222222 2 2 2 2 2222222222222222222 2!2"2#3$3%3&3'3(3)3*3+3,3-3.3/303132333435363738393:3;3<3=3>3?3@3A3B3C3D3E3F3G3H3I3J3K3L3M3N3O3P3Q3R3S3T3U3V3W3X3Y3Z3[3\3]3^3_3`3a3b3c3d3e3f3g3h3i3j3k3l3m3n3o3p3q3r3s4t4u4v4w4x4y4z4{4|4}4~4444444444444444444444444444444444455555555555555555555555555555555555555555555555566666666666666666666777777777777777777778888888899999999 9 9 9 9 9999999999999999999 9!9"9#9$9%9&9'9(9)9*9+9,9-9.9/90:1:2:3:4:5:6:7:8:9:::;:<:=:>:?:@:A:B:C;D;E;F;G;H;I;J;K;L;M;N;O;P;Q;R;S;T;U;V;W<X<Y<Z<[<\<]<^<_=`=a=b=c=d=e=f=g=h=i=j=k=l=m=n=o=p=q=r=s=t=u=v=w=x>y>z>{>|>}>~>>>>>>??????????????????????@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@AAAAAAAAAAAAAAAAAAAAAAAAAABBBBBBBBBBBBBBBBBBBBBBBBBBCCCCCCCCCC C C C C CCCCCCCCCCCCCCCCCCC C!C"C#C$C%C&C'C(C)C*C+C,C-C.C/C0C1C2C3C4C5C6C7C8C9C:C;C<C=C>C?C@CACBCCCDCECFCGCHCICJCKCLCMCNCOCPCQCRCSCTCUCVCWCXCYCZC[C\C]C^C_C`CaCbCcCdCeCfCgChCiCjCkClCmCnCoCpCqCrCsCtCuCvCwCxCyCzC{C|C}D~DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDEEEEEEEEEEEEEEEEEEEFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFGGGGGGGGGGG G G G G GGGGGGGGGHHHHHHHHHH H!H"H#H$H%H&H'H(H)H*H+H,H-H.H/H0H1H2H3H4H5H6H7H8H9H:H;H<H=H>H?H@HAHBHCHDHEHFHGHHHIHJHKHLHMHNHOHPHQHRHSHTHUHVHWHXHYHZH[H\H]H^H_H`HaHbHcHdHeHfHgHhHiHjHkHlHmHnHoHpHqHrHsHtHuHvHwHxHyHzH{H|H}H~HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H !H "H #H $H %H &H 'H (H )H *H +H ,H -H .H /H 0H 1H 2H 3H 4H 5H 6H 7H 8H 9H :H ;H <H =H >H ?H @H AH BH CH DH EH FH GH HH IH JH KH LH MH NH OH PH QH RH SH TH UH VH WH XH YH ZH [H \H ]H ^H _H `H aH bH cH dH eH fH gH hH iH jH kH lH mH nH oH pH qH rH sH tH uH vH wH xH yH zH {H |H }H ~H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H !H "H #H $H %H &H 'H (H )H *H +H ,H -H .H /H 0H 1H 2H 3H 4H 5H 6H 7H 8H 9H :H ;H <H =H >H ?H @H AH BH CH DH EH FH GH HI II JI KJ LJ MJ NJ OJ PJ QJ RJ SJ TJ UJ VJ WJ XJ YJ ZJ [J \J ]J ^J _J `J aK bK cK dK eK fK gK hK iK jK kK lK mK nK oK pK qK rK sK tK uK vK wK xK yK zK {K |K }K ~K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K L L L L L L L L L L L L L L L L L L L L L L M M M M M M M M M M M M M M M M M M M M M M N N N N N N N N N N N N N N N N N N N N N N O O O O O O O O O O O O O O O O O O O O O O O O O O O O P P P P P P P P P P P P !P "P #P $P %P &P 'P (P )P *P +P ,P -P .P /P 0Q 1Q 2Q 3Q 4Q 5Q 6Q 7Q 8Q 9Q :Q ;Q <Q =Q >Q ?Q @Q AQ BQ CQ DQ EQ FQ GQ HQ IQ JR KR LR MR NR OR PR QR RR SR TR UR VR WR XR YR ZR [R \R ]R ^R _R `R aR bR cR dS eS fS gS hS iS jS kS lS mS nS oS pS qS rS sS tS uS vS wS xS yS zS {S |S }S ~T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T U U U U U U U U U U U U U U U U U U U U U U U V V V V V V V V V V V V V V V V W W W W W W W W W W W W W W W W W W W W W W W W W W W X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X !X "X #X $X %X &X 'X (X )X *X +X ,X -X .X /X 0X 1X 2X 3X 4X 5X 6X 7X 8X 9X :X ;X <X =X >X ?X @X AX BX CX DX EX FX GX HX IX JX KX LX MX NX OX PX QX RX SX TX UY VY WY XZ YZ ZZ [Z \Z ][ ^[ _[ `[ a[ b[ c[ d[ e[ f[ g[ h[ i[ j[ k[ l[ m[ n[ o[ p[ q[ r[ s[ t[ u[ v[ w[ x[ y[ z[ {[ |[ }[ ~[ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ _ _ _ _ _ _ _ _ _ _ _ _ _ !_ "_ #_ $_ %_ &_ '_ (_ )_ *_ +_ ,_ -_ ._ /_ 0_ 1_ 2_ 3_ 4_ 5_ 6_ 7_ 8_ 9_ :_ ;_ <_ =_ >_ ?_ @_ A_ B_ C_ D_ E_ F_ G_ H_ I_ J_ K_ L_ M_ N_ O_ P_ Q_ R_ S_ T_ U_ V_ W_ X_ Y_ Z_ [_ \_ ]_ ^_ __ `_ a` b` c` da ea fa ga hb ib jb kb lb mb nb ob pb qb rb sb tb ub vb wb xb yb zb {b |b }b ~b b b b b b b b b b b c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d e e e f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f g g g g g g g g g g g g g g ggghhhhhhh h h h h hhhhhhhhhhhhhhhiiii i!i"i#i$i%i&i'i(i)i*i+i,i-j.j/j0j1j2j3j4j5j6j7j8j9j:j;k<k=k>k?k@kAkBkCkDkEkFkGkHkIkJkKkLkMkNkOkPkQkRkSkTkUkVkWkXkYlZl[l\l]m^m_m`nanbncndnenfngnhninjnknlnmnnnonpnqnrnsntouovowoxoyozo{o|p}p~pppppppppppppppppppppppqqqqqqqqqqqrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr r r r r rrrrrrrrrrrrrrrrrrr r!r"r#r$r%r&r'r(r)s*s+s,s-s.s/s0s1s2s3s4s5s6s7s8s9s:s;s<s=s>s?s@sAsBsCsDsEsFsGsHsIsJsKsLsMsNsOsPsQsRsSsTsUsVsWsXsYsZs[s\s]s^s_s`sasbscsdsesfsgshsisjskslsmsnsospsqsrssstsusvswsxsyszs{s|s}s~sssssssssssttttttttttttttttttttttttttttttttttttuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuvvvvvvvvvvvvvvvvvvvvwwwwwwwwwwwwwwwwwwwwwwww w w w w wwwwwwwwwwwwwwwwwww w!w"w#w$w%w&w'w(w)w*w+w,w-w.w/w0w1w2w3w4w5w6w7w8w9x:x;x<x=x>x?x@xAxBxCxDxExFxGxHxIxJxKxLxMxNxOxPxQxRxSxTxUxVxWxXxYxZx[x\x]x^x_x`xaxbxcxdxexfxgxhxixjxkxlxmxnxoxpxqxrxsxtxuxvxwxxxyxzx{x|x}x~xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy y y y y yyyyyyyyyyzzzzzzzzz z!z"z#z$z%z&z'z(z)z*z+z,z-z.z/{0{1{2{3{4{5{6{7{8{9{:|;|<|=|>|?|@|A|B|C|D|E|F|G}H}I}J}K}L}M}N}O}P}Q}R}S}T}U}V}W}X}Y}Z}[}\}]}^~_~`~a~b~c~d~e~f~g~h~i~j~k~l~m~n~o~p~q~r~s~t~u~v~w~x~y~z~{~|~}~~~~~~~~~~~~~~~~~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~     None%Kejkd<VkPipelineCacheHeaderVersion - Encode pipeline cache versionSee AlsoG, G $VK_PIPELINE_CACHE_HEADER_VERSION_ONE. specifies version one of the pipeline cache. 1VK_NULL_HANDLE - Reserved non-valid object handleSee Also!No cross-references are available   NoneKejkVkFlags - Vulkan bitmasks DescriptionYBitmasks are passed to many commands and structures to compactly represent options, but VkFlags. is not used directly in the API. Instead, a Vk*Flags type which is an alias of VkFlags,, and whose name matches the corresponding  Vk*FlagBits( that are valid for that type, is used.See AlsoHBVkObjectType - Specify an enumeration to track object handle types Description'  e Vulkan Handle Type # VK_OBJECT_TYPE_UNKNOWN d Unknown/Undefined Handle  VK_OBJECT_TYPE_INSTANCE  /,  VK_OBJECT_TYPE_PHYSICAL_DEVICE  /&  VK_OBJECT_TYPE_DEVICE  /.  VK_OBJECT_TYPE_QUEUE  @>  VK_OBJECT_TYPE_SEMAPHORE  @:  VK_OBJECT_TYPE_COMMAND_BUFFER  @6  VK_OBJECT_TYPE_FENCE  @>  VK_OBJECT_TYPE_DEVICE_MEMORY  f6  VK_OBJECT_TYPE_BUFFER  j2  VK_OBJECT_TYPE_IMAGE  j3  VK_OBJECT_TYPE_EVENT  }>  VK_OBJECT_TYPE_QUERY_POOL  F:  VK_OBJECT_TYPE_BUFFER_VIEW  4  VK_OBJECT_TYPE_IMAGE_VIEW  w6  VK_OBJECT_TYPE_SHADER_MODULE  ?6  VK_OBJECT_TYPE_PIPELINE_CACHE  G.  VK_OBJECT_TYPE_PIPELINE_LAYOUT  H2  VK_OBJECT_TYPE_RENDER_PASS  H6  VK_OBJECT_TYPE_PIPELINE  H8  $VK_OBJECT_TYPE_DESCRIPTOR_SET_LAYOUT  b'  VK_OBJECT_TYPE_SAMPLER  _:  VK_OBJECT_TYPE_DESCRIPTOR_POOL  -  VK_OBJECT_TYPE_DESCRIPTOR_SET  .  VK_OBJECT_TYPE_FRAMEBUFFER  9  VK_OBJECT_TYPE_COMMAND_POOL  2  VK_OBJECT_TYPE_SURFACE_KHR  K,  VK_OBJECT_TYPE_SWAPCHAIN_KHR  (  VK_OBJECT_TYPE_DISPLAY_KHR  X,  VK_OBJECT_TYPE_DISPLAY_MODE_KHR  X(  (VK_OBJECT_TYPE_DEBUG_REPORT_CALLBACK_EXT  3  )VK_OBJECT_TYPE_DESCRIPTOR_UPDATE_TEMPLATE    VK_OBJECT_TYPE_OBJECT_TABLE_NVX    +VK_OBJECT_TYPE_INDIRECT_COMMANDS_LAYOUT_NVX    #VK_OBJECT_TYPE_VALIDATION_CACHE_EXT  4 +VkObjectType and Vulkan Handle RelationshipSee AlsoC, C*VkStructureType - Vulkan structure types (stype) Description8Each value corresponds to a particular structure with a sTypeD member with a matching name. As a general rule, the name of each VkStructureTypeO value is obtained by taking the name of the structure, stripping the leading Vk%, prefixing each capital letter with _P, converting the entire resulting string to upper case, and prefixing it with VK_STRUCTURE_TYPE_#. For example, structures of type VkImageCreateInfo correspond to a VkStructureType of #VK_STRUCTURE_TYPE_IMAGE_CREATE_INFO, and thus its sType member must) equal that when it is passed to the API. The values -VK_STRUCTURE_TYPE_LOADER_INSTANCE_CREATE_INFO and +VK_STRUCTURE_TYPE_LOADER_DEVICE_CREATE_INFOv are reserved for internal use by the loader, and do not have corresponding Vulkan structures in this Specification.See Also, , , , U, /, ^, p, ^, p, , x, r, , , u, , , , , , , , H, , , D, D, D, 3, C, C, C, C, C, k, k, k, , , , , , , , , ~, , , , , , =, , , , , , ~ ,  ,  ,  , X , , , X, }, ;, , , 1, , h, 7, , , 9, , , , , 1 , 5!, z", B#, $, s%, &, H', (, N), *,  +, s,, -, u., x/, u0, 1, w2, 3, 4, B5, 6, 7, 8, 9, h:, A;, <, =, />, M?, f@, A, fB, C, nD, nE, F, G, H, I, J, uK, L, SM, [N, O, P, Q, R, S, T, U, ]V, W, 9X, Y, Z, 5[, s\, =], ^, s_, `, sa, b, c, d, e, sf, g, h, i, [j, 2k, xl, m, n, so, dp, Tq, r, s, Gt, u, Hv, %w, $x, Hy, ]z, H{, H|, b}, H~, , H,  , [, H, , H, , H, H, *, J, , W, , , F, s, , , , , [, [, _, 2, x, x, x, E, A, , ?, 4, , s, u, @, \, T, T, , , , 4, , L, R, i, g, Q, , P, O&VkResult - Vulkan command return codes Description VK_SUCCESS Command successfully completed VK_NOT_READY' A fence or query has not yet completed VK_TIMEOUT> A wait operation has not completed in the specified time VK_EVENT_SET An event is signaledVK_EVENT_RESET An event is unsignaled VK_INCOMPLETE, A return array was too small for the resultVK_SUBOPTIMAL_KHRH A swapchain no longer matches the surface properties exactly, but can; still be used to present to the surface successfully.VK_ERROR_OUT_OF_HOST_MEMORY% A host memory allocation has failed.VK_ERROR_OUT_OF_DEVICE_MEMORY, A device memory allocation has failed.VK_ERROR_INITIALIZATION_FAILED] Initialization of an object could not be completed for implementation-specific reasons.VK_ERROR_DEVICE_LOST8 The logical or physical device has been lost. See ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#devsandqueues-lost-deviceLost DeviceVK_ERROR_MEMORY_MAP_FAILED' Mapping of a memory object has failed.VK_ERROR_LAYER_NOT_PRESENT> A requested layer is not present or could not be loaded.VK_ERROR_EXTENSION_NOT_PRESENT- A requested extension is not supported.VK_ERROR_FEATURE_NOT_PRESENT& A requested feature is not supported.VK_ERROR_INCOMPATIBLE_DRIVER The requested version of Vulkan is not supported by the driver or is otherwise incompatible for implementation-specific reasons.VK_ERROR_TOO_MANY_OBJECTS= Too many objects of the type have already been created.VK_ERROR_FORMAT_NOT_SUPPORTED9 A requested format is not supported on this device.VK_ERROR_FRAGMENTED_POOLS A pool allocation has failed due to fragmentation of the pool s memory. This must| only be returned if no attempt to allocate host or device memory was made to accomodate the new allocation. This should# be returned in preference to VK_ERROR_OUT_OF_POOL_MEMORYk, but only if the implementation is certain that the pool allocation failure was due to fragmentation.VK_ERROR_SURFACE_LOST_KHR" A surface is no longer available.!VK_ERROR_NATIVE_WINDOW_IN_USE_KHR The requested window is already in use by Vulkan or another API in a manner which prevents it from being used again.VK_ERROR_OUT_OF_DATE_KHR A surface has changed in such a way that it is no longer compatible with the swapchain, and further presentation requests using the swapchain will fail. Applications mustw query the new surface properties and recreate their swapchain if they wish to continue presenting to the surface.!VK_ERROR_INCOMPATIBLE_DISPLAY_KHR The display used by a swapchain does not use the same presentable image layout, or is incompatible in a way that prevents sharing an image.VK_ERROR_INVALID_SHADER_NVp One or more shaders failed to compile or link. More details are reported back to the application via ({html_spec_relative}#VK_EXT_debug_report if enabled.VK_ERROR_OUT_OF_POOL_MEMORY0 A pool memory allocation has failed. This must only be returned if no attempt to allocate host or device memory was made to accomodate the new allocation. If the failure was definitely due to fragmentation of the pool, VK_ERROR_FRAGMENTED_POOL should be returned instead. VK_ERROR_INVALID_EXTERNAL_HANDLEE An external handle is not a valid handle of the specified type.VK_ERROR_FRAGMENTATION_EXTA A descriptor pool creation has failed due to fragmentation.If a command returns a run time error, unless otherwise specified any output parameters will have undefined contents, except that if the output parameter is a structure with sType and pNextG fields, those fields will be unmodified. Any structures chained from pNext1 will also have undefined contents, except that sType and pNext will be unmodified.Out of memory errors do not damage any currently existing Vulkan objects. Objects that have already been successfully created can# still be used by the application.Performance-critical commands generally do not have return codes. If a run time error occurs in such commands, the implementation will defer reporting the error until a specified point. For commands that record into command buffers (vkCmd*#) run time errors are reported by vkEndCommandBuffer.See Also$No cross-references are available, "VkFormat - Available image formatsSee Also, , , *,  +, w2, s_, so, x, K, , H, 0, /, s, t, /, rVkBool32 - Vulkan boolean type DescriptionVK_TRUE represents a boolean True (integer 1) value, and VK_FALSE a boolean False (integer 0) value.6All values returned from a Vulkan implementation in a VkBool32 will be either VK_TRUE or VK_FALSE. Applications must not pass any other values than VK_TRUE or VK_FALSE& into a Vulkan implementation where a VkBool32 is expected.See Also, k, k, , , , X, nE, P, Q, R, S, T, U, /, =], ^, /, b, c, g, h, [j, 2k, xl, n, /, dp, r, u, H, Hv, %w, $x, Hy, H|, H~, H, [, J, , _, x, , , K, zxVK_FORMAT_ASTC_12x12_SRGB_BLOCK specifies a four-component, ASTC compressed format where each 128-bit compressed texel block encodes a 1212 rectangle of unsigned normalized RGBA texel data with sRGB nonlinear encoding applied to the RGB components.y VK_FORMAT_ASTC_12x12_UNORM_BLOCK specifies a four-component, ASTC compressed format where each 128-bit compressed texel block encodes a 1212 rectangle of unsigned normalized RGBA texel data.zVK_FORMAT_ASTC_12x10_SRGB_BLOCK specifies a four-component, ASTC compressed format where each 128-bit compressed texel block encodes a 1210 rectangle of unsigned normalized RGBA texel data with sRGB nonlinear encoding applied to the RGB components.{ VK_FORMAT_ASTC_12x10_UNORM_BLOCK specifies a four-component, ASTC compressed format where each 128-bit compressed texel block encodes a 1210 rectangle of unsigned normalized RGBA texel data.|VK_FORMAT_ASTC_10x10_SRGB_BLOCK specifies a four-component, ASTC compressed format where each 128-bit compressed texel block encodes a 1010 rectangle of unsigned normalized RGBA texel data with sRGB nonlinear encoding applied to the RGB components.} VK_FORMAT_ASTC_10x10_UNORM_BLOCK specifies a four-component, ASTC compressed format where each 128-bit compressed texel block encodes a 1010 rectangle of unsigned normalized RGBA texel data.~VK_FORMAT_ASTC_10x8_SRGB_BLOCK specifies a four-component, ASTC compressed format where each 128-bit compressed texel block encodes a 108 rectangle of unsigned normalized RGBA texel data with sRGB nonlinear encoding applied to the RGB components.VK_FORMAT_ASTC_10x8_UNORM_BLOCK specifies a four-component, ASTC compressed format where each 128-bit compressed texel block encodes a 108 rectangle of unsigned normalized RGBA texel data.VK_FORMAT_ASTC_10x6_SRGB_BLOCK specifies a four-component, ASTC compressed format where each 128-bit compressed texel block encodes a 106 rectangle of unsigned normalized RGBA texel data with sRGB nonlinear encoding applied to the RGB components.VK_FORMAT_ASTC_10x6_UNORM_BLOCK specifies a four-component, ASTC compressed format where each 128-bit compressed texel block encodes a 106 rectangle of unsigned normalized RGBA texel data.VK_FORMAT_ASTC_10x5_SRGB_BLOCK specifies a four-component, ASTC compressed format where each 128-bit compressed texel block encodes a 105 rectangle of unsigned normalized RGBA texel data with sRGB nonlinear encoding applied to the RGB components.VK_FORMAT_ASTC_10x5_UNORM_BLOCK specifies a four-component, ASTC compressed format where each 128-bit compressed texel block encodes a 105 rectangle of unsigned normalized RGBA texel data.VK_FORMAT_ASTC_8x8_SRGB_BLOCK specifies a four-component, ASTC compressed format where each 128-bit compressed texel block encodes an 88 rectangle of unsigned normalized RGBA texel data with sRGB nonlinear encoding applied to the RGB components.VK_FORMAT_ASTC_8x8_UNORM_BLOCK specifies a four-component, ASTC compressed format where each 128-bit compressed texel block encodes an 88 rectangle of unsigned normalized RGBA texel data.VK_FORMAT_ASTC_8x6_SRGB_BLOCK specifies a four-component, ASTC compressed format where each 128-bit compressed texel block encodes an 86 rectangle of unsigned normalized RGBA texel data with sRGB nonlinear encoding applied to the RGB components.VK_FORMAT_ASTC_8x6_UNORM_BLOCK specifies a four-component, ASTC compressed format where each 128-bit compressed texel block encodes an 86 rectangle of unsigned normalized RGBA texel data.VK_FORMAT_ASTC_8x5_SRGB_BLOCK specifies a four-component, ASTC compressed format where each 128-bit compressed texel block encodes an 85 rectangle of unsigned normalized RGBA texel data with sRGB nonlinear encoding applied to the RGB components.VK_FORMAT_ASTC_8x5_UNORM_BLOCK specifies a four-component, ASTC compressed format where each 128-bit compressed texel block encodes an 85 rectangle of unsigned normalized RGBA texel data.VK_FORMAT_ASTC_6x6_SRGB_BLOCK specifies a four-component, ASTC compressed format where each 128-bit compressed texel block encodes a 66 rectangle of unsigned normalized RGBA texel data with sRGB nonlinear encoding applied to the RGB components.VK_FORMAT_ASTC_6x6_UNORM_BLOCK specifies a four-component, ASTC compressed format where each 128-bit compressed texel block encodes a 66 rectangle of unsigned normalized RGBA texel data.VK_FORMAT_ASTC_6x5_SRGB_BLOCK specifies a four-component, ASTC compressed format where each 128-bit compressed texel block encodes a 65 rectangle of unsigned normalized RGBA texel data with sRGB nonlinear encoding applied to the RGB components.VK_FORMAT_ASTC_6x5_UNORM_BLOCK specifies a four-component, ASTC compressed format where each 128-bit compressed texel block encodes a 65 rectangle of unsigned normalized RGBA texel data.VK_FORMAT_ASTC_5x5_SRGB_BLOCK specifies a four-component, ASTC compressed format where each 128-bit compressed texel block encodes a 55 rectangle of unsigned normalized RGBA texel data with sRGB nonlinear encoding applied to the RGB components.VK_FORMAT_ASTC_5x5_UNORM_BLOCK specifies a four-component, ASTC compressed format where each 128-bit compressed texel block encodes a 55 rectangle of unsigned normalized RGBA texel data.VK_FORMAT_ASTC_5x4_SRGB_BLOCK specifies a four-component, ASTC compressed format where each 128-bit compressed texel block encodes a 54 rectangle of unsigned normalized RGBA texel data with sRGB nonlinear encoding applied to the RGB components.VK_FORMAT_ASTC_5x4_UNORM_BLOCK specifies a four-component, ASTC compressed format where each 128-bit compressed texel block encodes a 54 rectangle of unsigned normalized RGBA texel data.VK_FORMAT_ASTC_4x4_SRGB_BLOCK specifies a four-component, ASTC compressed format where each 128-bit compressed texel block encodes a 44 rectangle of unsigned normalized RGBA texel data with sRGB nonlinear encoding applied to the RGB components.VK_FORMAT_ASTC_4x4_UNORM_BLOCK specifies a four-component, ASTC compressed format where each 128-bit compressed texel block encodes a 44 rectangle of unsigned normalized RGBA texel data. VK_FORMAT_EAC_R11G11_SNORM_BLOCK specifies a two-component, ETC2 compressed format where each 128-bit compressed texel block encodes a 44 rectangle of signed normalized RG texel data with the first 64 bits encoding red values followed by 64 bits encoding green values. VK_FORMAT_EAC_R11G11_UNORM_BLOCK specifies a two-component, ETC2 compressed format where each 128-bit compressed texel block encodes a 44 rectangle of unsigned normalized RG texel data with the first 64 bits encoding red values followed by 64 bits encoding green values.VK_FORMAT_EAC_R11_SNORM_BLOCK specifies a one-component, ETC2 compressed format where each 64-bit compressed texel block encodes a 44 rectangle of signed normalized red texel data.VK_FORMAT_EAC_R11_UNORM_BLOCK specifies a one-component, ETC2 compressed format where each 64-bit compressed texel block encodes a 44 rectangle of unsigned normalized red texel data."VK_FORMAT_ETC2_R8G8B8A8_SRGB_BLOCK specifies a four-component, ETC2 compressed format where each 128-bit compressed texel block encodes a 44 rectangle of unsigned normalized RGBA texel data with the first 64 bits encoding alpha values followed by 64 bits encoding RGB values with sRGB nonlinear encoding applied.#VK_FORMAT_ETC2_R8G8B8A8_UNORM_BLOCK specifies a four-component, ETC2 compressed format where each 128-bit compressed texel block encodes a 44 rectangle of unsigned normalized RGBA texel data with the first 64 bits encoding alpha values followed by 64 bits encoding RGB values."VK_FORMAT_ETC2_R8G8B8A1_SRGB_BLOCK specifies a four-component, ETC2 compressed format where each 64-bit compressed texel block encodes a 44 rectangle of unsigned normalized RGB texel data with sRGB nonlinear encoding, and provides 1 bit of alpha.#VK_FORMAT_ETC2_R8G8B8A1_UNORM_BLOCK specifies a four-component, ETC2 compressed format where each 64-bit compressed texel block encodes a 44 rectangle of unsigned normalized RGB texel data, and provides 1 bit of alpha. VK_FORMAT_ETC2_R8G8B8_SRGB_BLOCK specifies a three-component, ETC2 compressed format where each 64-bit compressed texel block encodes a 44 rectangle of unsigned normalized RGB texel data with sRGB nonlinear encoding. This format has no alpha and is considered opaque.!VK_FORMAT_ETC2_R8G8B8_UNORM_BLOCK specifies a three-component, ETC2 compressed format where each 64-bit compressed texel block encodes a 44 rectangle of unsigned normalized RGB texel data. This format has no alpha and is considered opaque.VK_FORMAT_BC7_SRGB_BLOCK specifies a four-component, block-compressed format where each 128-bit compressed texel block encodes a 44 rectangle of unsigned normalized RGBA texel data with sRGB nonlinear encoding applied to the RGB components.VK_FORMAT_BC7_UNORM_BLOCK specifies a four-component, block-compressed format where each 128-bit compressed texel block encodes a 44 rectangle of unsigned normalized RGBA texel data.VK_FORMAT_BC6H_SFLOAT_BLOCK specifies a three-component, block-compressed format where each 128-bit compressed texel block encodes a 44 rectangle of signed floating-point RGB texel data.VK_FORMAT_BC6H_UFLOAT_BLOCK specifies a three-component, block-compressed format where each 128-bit compressed texel block encodes a 44 rectangle of unsigned floating-point RGB texel data.VK_FORMAT_BC5_SNORM_BLOCK specifies a two-component, block-compressed format where each 128-bit compressed texel block encodes a 44 rectangle of signed normalized RG texel data with the first 64 bits encoding red values followed by 64 bits encoding green values.VK_FORMAT_BC5_UNORM_BLOCK specifies a two-component, block-compressed format where each 128-bit compressed texel block encodes a 44 rectangle of unsigned normalized RG texel data with the first 64 bits encoding red values followed by 64 bits encoding green values.VK_FORMAT_BC4_SNORM_BLOCK specifies a one-component, block-compressed format where each 64-bit compressed texel block encodes a 44 rectangle of signed normalized red texel data.VK_FORMAT_BC4_UNORM_BLOCK specifies a one-component, block-compressed format where each 64-bit compressed texel block encodes a 44 rectangle of unsigned normalized red texel data.VK_FORMAT_BC3_SRGB_BLOCK specifies a four-component, block-compressed format where each 128-bit compressed texel block encodes a 44 rectangle of unsigned normalized RGBA texel data with the first 64 bits encoding alpha values followed by 64 bits encoding RGB values with sRGB nonlinear encoding.VK_FORMAT_BC3_UNORM_BLOCK specifies a four-component, block-compressed format where each 128-bit compressed texel block encodes a 44 rectangle of unsigned normalized RGBA texel data with the first 64 bits encoding alpha values followed by 64 bits encoding RGB values.VK_FORMAT_BC2_SRGB_BLOCK specifies a four-component, block-compressed format where each 128-bit compressed texel block encodes a 44 rectangle of unsigned normalized RGBA texel data with the first 64 bits encoding alpha values followed by 64 bits encoding RGB values with sRGB nonlinear encoding.VK_FORMAT_BC2_UNORM_BLOCK specifies a four-component, block-compressed format where each 128-bit compressed texel block encodes a 44 rectangle of unsigned normalized RGBA texel data with the first 64 bits encoding alpha values followed by 64 bits encoding RGB values.VK_FORMAT_BC1_RGBA_SRGB_BLOCK specifies a four-component, block-compressed format where each 64-bit compressed texel block encodes a 44 rectangle of unsigned normalized RGB texel data with sRGB nonlinear encoding, and provides 1 bit of alpha.VK_FORMAT_BC1_RGBA_UNORM_BLOCK specifies a four-component, block-compressed format where each 64-bit compressed texel block encodes a 44 rectangle of unsigned normalized RGB texel data, and provides 1 bit of alpha.VK_FORMAT_BC1_RGB_SRGB_BLOCK specifies a three-component, block-compressed format where each 64-bit compressed texel block encodes a 44 rectangle of unsigned normalized RGB texel data with sRGB nonlinear encoding. This format has no alpha and is considered opaque.VK_FORMAT_BC1_RGB_UNORM_BLOCK specifies a three-component, block-compressed format where each 64-bit compressed texel block encodes a 44 rectangle of unsigned normalized RGB texel data. This format has no alpha and is considered opaque.VK_FORMAT_D32_SFLOAT_S8_UINT specifies a two-component format that has 32 signed float bits in the depth component and 8 unsigned integer bits in the stencil component. There are optionally: 24-bits that are unused.VK_FORMAT_D24_UNORM_S8_UINT specifies a two-component, 32-bit packed format that has 8 unsigned integer bits in the stencil component, and 24 unsigned normalized bits in the depth component.VK_FORMAT_D16_UNORM_S8_UINT specifies a two-component, 24-bit format that has 16 unsigned normalized bits in the depth component and 8 unsigned integer bits in the stencil component.VK_FORMAT_S8_UINTd specifies a one-component, 8-bit unsigned integer format that has 8-bits in the stencil component.VK_FORMAT_D32_SFLOATi specifies a one-component, 32-bit signed floating-point format that has 32-bits in the depth component.VK_FORMAT_X8_D24_UNORM_PACK32 specifies a two-component, 32-bit format that has 24 unsigned normalized bits in the depth component and, optionally:, 8 bits that are unused.VK_FORMAT_D16_UNORMh specifies a one-component, 16-bit unsigned normalized format that has a single 16-bit depth component. VK_FORMAT_E5B9G9R9_UFLOAT_PACK32 specifies a three-component, 32-bit packed unsigned floating-point format that has a 5-bit shared exponent in bits 27..31, a 9-bit B component mantissa in bits 18..26, a 9-bit G component mantissa in bits 9..17, and a 9-bit R component mantissa in bits 0..8.!VK_FORMAT_B10G11R11_UFLOAT_PACK32 specifies a three-component, 32-bit packed unsigned floating-point format that has a 10-bit B component in bits 22..31, an 11-bit G component in bits 11..21, an 11-bit R component in bits 0..10. See  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-fp10&{html_spec_relative}#fundamentals-fp10 and  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-fp11&{html_spec_relative}#fundamentals-fp11.VK_FORMAT_R64G64B64A64_SFLOAT specifies a four-component, 256-bit signed floating-point format that has a 64-bit R component in bytes 0..7, a 64-bit G component in bytes 8..15, a 64-bit B component in bytes 16..23, and a 64-bit A component in bytes 24..31.VK_FORMAT_R64G64B64A64_SINT specifies a four-component, 256-bit signed integer format that has a 64-bit R component in bytes 0..7, a 64-bit G component in bytes 8..15, a 64-bit B component in bytes 16..23, and a 64-bit A component in bytes 24..31.VK_FORMAT_R64G64B64A64_UINT specifies a four-component, 256-bit unsigned integer format that has a 64-bit R component in bytes 0..7, a 64-bit G component in bytes 8..15, a 64-bit B component in bytes 16..23, and a 64-bit A component in bytes 24..31.VK_FORMAT_R64G64B64_SFLOAT specifies a three-component, 192-bit signed floating-point format that has a 64-bit R component in bytes 0..7, a 64-bit G component in bytes 8..15, and a 64-bit B component in bytes 16..23.VK_FORMAT_R64G64B64_SINT specifies a three-component, 192-bit signed integer format that has a 64-bit R component in bytes 0..7, a 64-bit G component in bytes 8..15, and a 64-bit B component in bytes 16..23.VK_FORMAT_R64G64B64_UINT specifies a three-component, 192-bit unsigned integer format that has a 64-bit R component in bytes 0..7, a 64-bit G component in bytes 8..15, and a 64-bit B component in bytes 16..23.VK_FORMAT_R64G64_SFLOAT specifies a two-component, 128-bit signed floating-point format that has a 64-bit R component in bytes 0..7, and a 64-bit G component in bytes 8..15.VK_FORMAT_R64G64_SINT specifies a two-component, 128-bit signed integer format that has a 64-bit R component in bytes 0..7, and a 64-bit G component in bytes 8..15.VK_FORMAT_R64G64_UINT specifies a two-component, 128-bit unsigned integer format that has a 64-bit R component in bytes 0..7, and a 64-bit G component in bytes 8..15.VK_FORMAT_R64_SFLOATf specifies a one-component, 64-bit signed floating-point format that has a single 64-bit R component.VK_FORMAT_R64_SINT_ specifies a one-component, 64-bit signed integer format that has a single 64-bit R component.VK_FORMAT_R64_UINTa specifies a one-component, 64-bit unsigned integer format that has a single 64-bit R component.VK_FORMAT_R32G32B32A32_SFLOAT specifies a four-component, 128-bit signed floating-point format that has a 32-bit R component in bytes 0..3, a 32-bit G component in bytes 4..7, a 32-bit B component in bytes 8..11, and a 32-bit A component in bytes 12..15.VK_FORMAT_R32G32B32A32_SINT specifies a four-component, 128-bit signed integer format that has a 32-bit R component in bytes 0..3, a 32-bit G component in bytes 4..7, a 32-bit B component in bytes 8..11, and a 32-bit A component in bytes 12..15.VK_FORMAT_R32G32B32A32_UINT specifies a four-component, 128-bit unsigned integer format that has a 32-bit R component in bytes 0..3, a 32-bit G component in bytes 4..7, a 32-bit B component in bytes 8..11, and a 32-bit A component in bytes 12..15.VK_FORMAT_R32G32B32_SFLOAT specifies a three-component, 96-bit signed floating-point format that has a 32-bit R component in bytes 0..3, a 32-bit G component in bytes 4..7, and a 32-bit B component in bytes 8..11.VK_FORMAT_R32G32B32_SINT specifies a three-component, 96-bit signed integer format that has a 32-bit R component in bytes 0..3, a 32-bit G component in bytes 4..7, and a 32-bit B component in bytes 8..11.VK_FORMAT_R32G32B32_UINT specifies a three-component, 96-bit unsigned integer format that has a 32-bit R component in bytes 0..3, a 32-bit G component in bytes 4..7, and a 32-bit B component in bytes 8..11.VK_FORMAT_R32G32_SFLOAT specifies a two-component, 64-bit signed floating-point format that has a 32-bit R component in bytes 0..3, and a 32-bit G component in bytes 4..7.VK_FORMAT_R32G32_SINT specifies a two-component, 64-bit signed integer format that has a 32-bit R component in bytes 0..3, and a 32-bit G component in bytes 4..7.VK_FORMAT_R32G32_UINT specifies a two-component, 64-bit unsigned integer format that has a 32-bit R component in bytes 0..3, and a 32-bit G component in bytes 4..7.VK_FORMAT_R32_SFLOATf specifies a one-component, 32-bit signed floating-point format that has a single 32-bit R component.VK_FORMAT_R32_SINT_ specifies a one-component, 32-bit signed integer format that has a single 32-bit R component.VK_FORMAT_R32_UINTa specifies a one-component, 32-bit unsigned integer format that has a single 32-bit R component.VK_FORMAT_R16G16B16A16_SFLOAT specifies a four-component, 64-bit signed floating-point format that has a 16-bit R component in bytes 0..1, a 16-bit G component in bytes 2..3, a 16-bit B component in bytes 4..5, and a 16-bit A component in bytes 6..7.VK_FORMAT_R16G16B16A16_SINT specifies a four-component, 64-bit signed integer format that has a 16-bit R component in bytes 0..1, a 16-bit G component in bytes 2..3, a 16-bit B component in bytes 4..5, and a 16-bit A component in bytes 6..7.VK_FORMAT_R16G16B16A16_UINT specifies a four-component, 64-bit unsigned integer format that has a 16-bit R component in bytes 0..1, a 16-bit G component in bytes 2..3, a 16-bit B component in bytes 4..5, and a 16-bit A component in bytes 6..7.VK_FORMAT_R16G16B16A16_SSCALED specifies a four-component, 64-bit signed scaled integer format that has a 16-bit R component in bytes 0..1, a 16-bit G component in bytes 2..3, a 16-bit B component in bytes 4..5, and a 16-bit A component in bytes 6..7.VK_FORMAT_R16G16B16A16_USCALED specifies a four-component, 64-bit unsigned scaled integer format that has a 16-bit R component in bytes 0..1, a 16-bit G component in bytes 2..3, a 16-bit B component in bytes 4..5, and a 16-bit A component in bytes 6..7.VK_FORMAT_R16G16B16A16_SNORM specifies a four-component, 64-bit signed normalized format that has a 16-bit R component in bytes 0..1, a 16-bit G component in bytes 2..3, a 16-bit B component in bytes 4..5, and a 16-bit A component in bytes 6..7.VK_FORMAT_R16G16B16A16_UNORM specifies a four-component, 64-bit unsigned normalized format that has a 16-bit R component in bytes 0..1, a 16-bit G component in bytes 2..3, a 16-bit B component in bytes 4..5, and a 16-bit A component in bytes 6..7.VK_FORMAT_R16G16B16_SFLOAT specifies a three-component, 48-bit signed floating-point format that has a 16-bit R component in bytes 0..1, a 16-bit G component in bytes 2..3, and a 16-bit B component in bytes 4..5.VK_FORMAT_R16G16B16_SINT specifies a three-component, 48-bit signed integer format that has a 16-bit R component in bytes 0..1, a 16-bit G component in bytes 2..3, and a 16-bit B component in bytes 4..5.VK_FORMAT_R16G16B16_UINT specifies a three-component, 48-bit unsigned integer format that has a 16-bit R component in bytes 0..1, a 16-bit G component in bytes 2..3, and a 16-bit B component in bytes 4..5.VK_FORMAT_R16G16B16_SSCALED specifies a three-component, 48-bit signed scaled integer format that has a 16-bit R component in bytes 0..1, a 16-bit G component in bytes 2..3, and a 16-bit B component in bytes 4..5.VK_FORMAT_R16G16B16_USCALED specifies a three-component, 48-bit unsigned scaled integer format that has a 16-bit R component in bytes 0..1, a 16-bit G component in bytes 2..3, and a 16-bit B component in bytes 4..5.VK_FORMAT_R16G16B16_SNORM specifies a three-component, 48-bit signed normalized format that has a 16-bit R component in bytes 0..1, a 16-bit G component in bytes 2..3, and a 16-bit B component in bytes 4..5.VK_FORMAT_R16G16B16_UNORM specifies a three-component, 48-bit unsigned normalized format that has a 16-bit R component in bytes 0..1, a 16-bit G component in bytes 2..3, and a 16-bit B component in bytes 4..5.VK_FORMAT_R16G16_SFLOAT specifies a two-component, 32-bit signed floating-point format that has a 16-bit R component in bytes 0..1, and a 16-bit G component in bytes 2..3.VK_FORMAT_R16G16_SINT specifies a two-component, 32-bit signed integer format that has a 16-bit R component in bytes 0..1, and a 16-bit G component in bytes 2..3.VK_FORMAT_R16G16_UINT specifies a two-component, 32-bit unsigned integer format that has a 16-bit R component in bytes 0..1, and a 16-bit G component in bytes 2..3.VK_FORMAT_R16G16_SSCALED specifies a two-component, 32-bit signed scaled integer format that has a 16-bit R component in bytes 0..1, and a 16-bit G component in bytes 2..3.VK_FORMAT_R16G16_USCALED specifies a two-component, 32-bit unsigned scaled integer format that has a 16-bit R component in bytes 0..1, and a 16-bit G component in bytes 2..3.VK_FORMAT_R16G16_SNORM specifies a two-component, 32-bit signed normalized format that has a 16-bit R component in bytes 0..1, and a 16-bit G component in bytes 2..3.VK_FORMAT_R16G16_UNORM specifies a two-component, 32-bit unsigned normalized format that has a 16-bit R component in bytes 0..1, and a 16-bit G component in bytes 2..3.VK_FORMAT_R16_SFLOATf specifies a one-component, 16-bit signed floating-point format that has a single 16-bit R component.VK_FORMAT_R16_SINT_ specifies a one-component, 16-bit signed integer format that has a single 16-bit R component.VK_FORMAT_R16_UINTa specifies a one-component, 16-bit unsigned integer format that has a single 16-bit R component.VK_FORMAT_R16_SSCALEDf specifies a one-component, 16-bit signed scaled integer format that has a single 16-bit R component.VK_FORMAT_R16_USCALEDh specifies a one-component, 16-bit unsigned scaled integer format that has a single 16-bit R component.VK_FORMAT_R16_SNORMb specifies a one-component, 16-bit signed normalized format that has a single 16-bit R component.VK_FORMAT_R16_UNORMd specifies a one-component, 16-bit unsigned normalized format that has a single 16-bit R component.!VK_FORMAT_A2B10G10R10_SINT_PACK32 specifies a four-component, 32-bit packed signed integer format that has a 2-bit A component in bits 30..31, a 10-bit B component in bits 20..29, a 10-bit G component in bits 10..19, and a 10-bit R component in bits 0..9.!VK_FORMAT_A2B10G10R10_UINT_PACK32 specifies a four-component, 32-bit packed unsigned integer format that has a 2-bit A component in bits 30..31, a 10-bit B component in bits 20..29, a 10-bit G component in bits 10..19, and a 10-bit R component in bits 0..9.$VK_FORMAT_A2B10G10R10_SSCALED_PACK32 specifies a four-component, 32-bit packed signed scaled integer format that has a 2-bit A component in bits 30..31, a 10-bit B component in bits 20..29, a 10-bit G component in bits 10..19, and a 10-bit R component in bits 0..9.$VK_FORMAT_A2B10G10R10_USCALED_PACK32 specifies a four-component, 32-bit packed unsigned scaled integer format that has a 2-bit A component in bits 30..31, a 10-bit B component in bits 20..29, a 10-bit G component in bits 10..19, and a 10-bit R component in bits 0..9."VK_FORMAT_A2B10G10R10_SNORM_PACK32 specifies a four-component, 32-bit packed signed normalized format that has a 2-bit A component in bits 30..31, a 10-bit B component in bits 20..29, a 10-bit G component in bits 10..19, and a 10-bit R component in bits 0..9."VK_FORMAT_A2B10G10R10_UNORM_PACK32 specifies a four-component, 32-bit packed unsigned normalized format that has a 2-bit A component in bits 30..31, a 10-bit B component in bits 20..29, a 10-bit G component in bits 10..19, and a 10-bit R component in bits 0..9.!VK_FORMAT_A2R10G10B10_SINT_PACK32 specifies a four-component, 32-bit packed signed integer format that has a 2-bit A component in bits 30..31, a 10-bit R component in bits 20..29, a 10-bit G component in bits 10..19, and a 10-bit B component in bits 0..9.!VK_FORMAT_A2R10G10B10_UINT_PACK32 specifies a four-component, 32-bit packed unsigned integer format that has a 2-bit A component in bits 30..31, a 10-bit R component in bits 20..29, a 10-bit G component in bits 10..19, and a 10-bit B component in bits 0..9.$VK_FORMAT_A2R10G10B10_SSCALED_PACK32 specifies a four-component, 32-bit packed signed scaled integer format that has a 2-bit A component in bits 30..31, a 10-bit R component in bits 20..29, a 10-bit G component in bits 10..19, and a 10-bit B component in bits 0..9.$VK_FORMAT_A2R10G10B10_USCALED_PACK32 specifies a four-component, 32-bit packed unsigned scaled integer format that has a 2-bit A component in bits 30..31, a 10-bit R component in bits 20..29, a 10-bit G component in bits 10..19, and a 10-bit B component in bits 0..9."VK_FORMAT_A2R10G10B10_SNORM_PACK32 specifies a four-component, 32-bit packed signed normalized format that has a 2-bit A component in bits 30..31, a 10-bit R component in bits 20..29, a 10-bit G component in bits 10..19, and a 10-bit B component in bits 0..9."VK_FORMAT_A2R10G10B10_UNORM_PACK32 specifies a four-component, 32-bit packed unsigned normalized format that has a 2-bit A component in bits 30..31, a 10-bit R component in bits 20..29, a 10-bit G component in bits 10..19, and a 10-bit B component in bits 0..9.VK_FORMAT_A8B8G8R8_SRGB_PACK32T specifies a four-component, 32-bit packed unsigned normalized format that has an 8-bit A component in bits 24..31, an 8-bit B component stored with sRGB nonlinear encoding in bits 16..23, an 8-bit G component stored with sRGB nonlinear encoding in bits 8..15, and an 8-bit R component stored with sRGB nonlinear encoding in bits 0..7.VK_FORMAT_A8B8G8R8_SINT_PACK32 specifies a four-component, 32-bit packed signed integer format that has an 8-bit A component in bits 24..31, an 8-bit B component in bits 16..23, an 8-bit G component in bits 8..15, and an 8-bit R component in bits 0..7.VK_FORMAT_A8B8G8R8_UINT_PACK32 specifies a four-component, 32-bit packed unsigned integer format that has an 8-bit A component in bits 24..31, an 8-bit B component in bits 16..23, an 8-bit G component in bits 8..15, and an 8-bit R component in bits 0..7.!VK_FORMAT_A8B8G8R8_SSCALED_PACK32 specifies a four-component, 32-bit packed signed scaled integer format that has an 8-bit A component in bits 24..31, an 8-bit B component in bits 16..23, an 8-bit G component in bits 8..15, and an 8-bit R component in bits 0..7.!VK_FORMAT_A8B8G8R8_USCALED_PACK32 specifies a four-component, 32-bit packed unsigned scaled integer format that has an 8-bit A component in bits 24..31, an 8-bit B component in bits 16..23, an 8-bit G component in bits 8..15, and an 8-bit R component in bits 0..7.VK_FORMAT_A8B8G8R8_SNORM_PACK32 specifies a four-component, 32-bit packed signed normalized format that has an 8-bit A component in bits 24..31, an 8-bit B component in bits 16..23, an 8-bit G component in bits 8..15, and an 8-bit R component in bits 0..7.VK_FORMAT_A8B8G8R8_UNORM_PACK32 specifies a four-component, 32-bit packed unsigned normalized format that has an 8-bit A component in bits 24..31, an 8-bit B component in bits 16..23, an 8-bit G component in bits 8..15, and an 8-bit R component in bits 0..7.VK_FORMAT_B8G8R8A8_SRGB; specifies a four-component, 32-bit unsigned normalized format that has an 8-bit B component stored with sRGB nonlinear encoding in byte 0, an 8-bit G component stored with sRGB nonlinear encoding in byte 1, an 8-bit R component stored with sRGB nonlinear encoding in byte 2, and an 8-bit A component in byte 3.VK_FORMAT_B8G8R8A8_SINT specifies a four-component, 32-bit signed integer format that has an 8-bit B component in byte 0, an 8-bit G component in byte 1, an 8-bit R component in byte 2, and an 8-bit A component in byte 3.VK_FORMAT_B8G8R8A8_UINT specifies a four-component, 32-bit unsigned integer format that has an 8-bit B component in byte 0, an 8-bit G component in byte 1, an 8-bit R component in byte 2, and an 8-bit A component in byte 3.VK_FORMAT_B8G8R8A8_SSCALED specifies a four-component, 32-bit signed scaled format that has an 8-bit B component in byte 0, an 8-bit G component in byte 1, an 8-bit R component in byte 2, and an 8-bit A component in byte 3.VK_FORMAT_B8G8R8A8_USCALED specifies a four-component, 32-bit unsigned scaled format that has an 8-bit B component in byte 0, an 8-bit G component in byte 1, an 8-bit R component in byte 2, and an 8-bit A component in byte 3.VK_FORMAT_B8G8R8A8_SNORM specifies a four-component, 32-bit signed normalized format that has an 8-bit B component in byte 0, an 8-bit G component in byte 1, an 8-bit R component in byte 2, and an 8-bit A component in byte 3.VK_FORMAT_B8G8R8A8_UNORM specifies a four-component, 32-bit unsigned normalized format that has an 8-bit B component in byte 0, an 8-bit G component in byte 1, an 8-bit R component in byte 2, and an 8-bit A component in byte 3.VK_FORMAT_R8G8B8A8_SRGB; specifies a four-component, 32-bit unsigned normalized format that has an 8-bit R component stored with sRGB nonlinear encoding in byte 0, an 8-bit G component stored with sRGB nonlinear encoding in byte 1, an 8-bit B component stored with sRGB nonlinear encoding in byte 2, and an 8-bit A component in byte 3.VK_FORMAT_R8G8B8A8_SINT specifies a four-component, 32-bit signed integer format that has an 8-bit R component in byte 0, an 8-bit G component in byte 1, an 8-bit B component in byte 2, and an 8-bit A component in byte 3.VK_FORMAT_R8G8B8A8_UINT specifies a four-component, 32-bit unsigned integer format that has an 8-bit R component in byte 0, an 8-bit G component in byte 1, an 8-bit B component in byte 2, and an 8-bit A component in byte 3.VK_FORMAT_R8G8B8A8_SSCALED specifies a four-component, 32-bit signed scaled format that has an 8-bit R component in byte 0, an 8-bit G component in byte 1, an 8-bit B component in byte 2, and an 8-bit A component in byte 3. VK_FORMAT_R8G8B8A8_USCALED specifies a four-component, 32-bit unsigned scaled format that has an 8-bit R component in byte 0, an 8-bit G component in byte 1, an 8-bit B component in byte 2, and an 8-bit A component in byte 3. VK_FORMAT_R8G8B8A8_SNORM specifies a four-component, 32-bit signed normalized format that has an 8-bit R component in byte 0, an 8-bit G component in byte 1, an 8-bit B component in byte 2, and an 8-bit A component in byte 3. VK_FORMAT_R8G8B8A8_UNORM specifies a four-component, 32-bit unsigned normalized format that has an 8-bit R component in byte 0, an 8-bit G component in byte 1, an 8-bit B component in byte 2, and an 8-bit A component in byte 3. VK_FORMAT_B8G8R8_SRGB specifies a three-component, 24-bit unsigned normalized format that has an 8-bit B component stored with sRGB nonlinear encoding in byte 0, an 8-bit G component stored with sRGB nonlinear encoding in byte 1, and an 8-bit R component stored with sRGB nonlinear encoding in byte 2. VK_FORMAT_B8G8R8_SINT specifies a three-component, 24-bit signed integer format that has an 8-bit B component in byte 0, an 8-bit G component in byte 1, and an 8-bit R component in byte 2.VK_FORMAT_B8G8R8_UINT specifies a three-component, 24-bit unsigned integer format that has an 8-bit B component in byte 0, an 8-bit G component in byte 1, and an 8-bit R component in byte 2.VK_FORMAT_B8G8R8_SSCALED specifies a three-component, 24-bit signed scaled format that has an 8-bit B component in byte 0, an 8-bit G component in byte 1, and an 8-bit R component in byte 2.VK_FORMAT_B8G8R8_USCALED specifies a three-component, 24-bit unsigned scaled format that has an 8-bit B component in byte 0, an 8-bit G component in byte 1, and an 8-bit R component in byte 2.VK_FORMAT_B8G8R8_SNORM specifies a three-component, 24-bit signed normalized format that has an 8-bit B component in byte 0, an 8-bit G component in byte 1, and an 8-bit R component in byte 2.VK_FORMAT_B8G8R8_UNORM specifies a three-component, 24-bit unsigned normalized format that has an 8-bit B component in byte 0, an 8-bit G component in byte 1, and an 8-bit R component in byte 2.VK_FORMAT_R8G8B8_SRGB specifies a three-component, 24-bit unsigned normalized format that has an 8-bit R component stored with sRGB nonlinear encoding in byte 0, an 8-bit G component stored with sRGB nonlinear encoding in byte 1, and an 8-bit B component stored with sRGB nonlinear encoding in byte 2.VK_FORMAT_R8G8B8_SINT specifies a three-component, 24-bit signed integer format that has an 8-bit R component in byte 0, an 8-bit G component in byte 1, and an 8-bit B component in byte 2.VK_FORMAT_R8G8B8_UINT specifies a three-component, 24-bit unsigned integer format that has an 8-bit R component in byte 0, an 8-bit G component in byte 1, and an 8-bit B component in byte 2.VK_FORMAT_R8G8B8_SSCALED specifies a three-component, 24-bit signed scaled format that has an 8-bit R component in byte 0, an 8-bit G component in byte 1, and an 8-bit B component in byte 2.VK_FORMAT_R8G8B8_USCALED specifies a three-component, 24-bit unsigned scaled format that has an 8-bit R component in byte 0, an 8-bit G component in byte 1, and an 8-bit B component in byte 2.VK_FORMAT_R8G8B8_SNORM specifies a three-component, 24-bit signed normalized format that has an 8-bit R component in byte 0, an 8-bit G component in byte 1, and an 8-bit B component in byte 2.VK_FORMAT_R8G8B8_UNORM specifies a three-component, 24-bit unsigned normalized format that has an 8-bit R component in byte 0, an 8-bit G component in byte 1, and an 8-bit B component in byte 2.VK_FORMAT_R8G8_SRGB specifies a two-component, 16-bit unsigned normalized format that has an 8-bit R component stored with sRGB nonlinear encoding in byte 0, and an 8-bit G component stored with sRGB nonlinear encoding in byte 1.VK_FORMAT_R8G8_SINT specifies a two-component, 16-bit signed integer format that has an 8-bit R component in byte 0, and an 8-bit G component in byte 1.VK_FORMAT_R8G8_UINT specifies a two-component, 16-bit unsigned integer format that has an 8-bit R component in byte 0, and an 8-bit G component in byte 1.VK_FORMAT_R8G8_SSCALED specifies a two-component, 16-bit signed scaled integer format that has an 8-bit R component in byte 0, and an 8-bit G component in byte 1.VK_FORMAT_R8G8_USCALED specifies a two-component, 16-bit unsigned scaled integer format that has an 8-bit R component in byte 0, and an 8-bit G component in byte 1.VK_FORMAT_R8G8_SNORM specifies a two-component, 16-bit signed normalized format that has an 8-bit R component in byte 0, and an 8-bit G component in byte 1. VK_FORMAT_R8G8_UNORM specifies a two-component, 16-bit unsigned normalized format that has an 8-bit R component in byte 0, and an 8-bit G component in byte 1.!VK_FORMAT_R8_SRGB specifies a one-component, 8-bit unsigned normalized format that has a single 8-bit R component stored with sRGB nonlinear encoding."VK_FORMAT_R8_SINT] specifies a one-component, 8-bit signed integer format that has a single 8-bit R component.#VK_FORMAT_R8_UINT_ specifies a one-component, 8-bit unsigned integer format that has a single 8-bit R component.$VK_FORMAT_R8_SSCALEDd specifies a one-component, 8-bit signed scaled integer format that has a single 8-bit R component.%VK_FORMAT_R8_USCALEDf specifies a one-component, 8-bit unsigned scaled integer format that has a single 8-bit R component.&VK_FORMAT_R8_SNORM` specifies a one-component, 8-bit signed normalized format that has a single 8-bit R component.'VK_FORMAT_R8_UNORMb specifies a one-component, 8-bit unsigned normalized format that has a single 8-bit R component.(VK_FORMAT_A1R5G5B5_UNORM_PACK16 specifies a four-component, 16-bit packed unsigned normalized format that has a 1-bit A component in bit 15, a 5-bit R component in bits 10..14, a 5-bit G component in bits 5..9, and a 5-bit B component in bits 0..4.)VK_FORMAT_B5G5R5A1_UNORM_PACK16 specifies a four-component, 16-bit packed unsigned normalized format that has a 5-bit B component in bits 11..15, a 5-bit G component in bits 6..10, a 5-bit R component in bits 1..5, and a 1-bit A component in bit 0.*VK_FORMAT_R5G5B5A1_UNORM_PACK16 specifies a four-component, 16-bit packed unsigned normalized format that has a 5-bit R component in bits 11..15, a 5-bit G component in bits 6..10, a 5-bit B component in bits 1..5, and a 1-bit A component in bit 0.+VK_FORMAT_B5G6R5_UNORM_PACK16 specifies a three-component, 16-bit packed unsigned normalized format that has a 5-bit B component in bits 11..15, a 6-bit G component in bits 5..10, and a 5-bit R component in bits 0..4.,VK_FORMAT_R5G6B5_UNORM_PACK16 specifies a three-component, 16-bit packed unsigned normalized format that has a 5-bit R component in bits 11..15, a 6-bit G component in bits 5..10, and a 5-bit B component in bits 0..4.-VK_FORMAT_B4G4R4A4_UNORM_PACK16 specifies a four-component, 16-bit packed unsigned normalized format that has a 4-bit B component in bits 12..15, a 4-bit G component in bits 8..11, a 4-bit R component in bits 4..7, and a 4-bit A component in bits 0..3..VK_FORMAT_R4G4B4A4_UNORM_PACK16 specifies a four-component, 16-bit packed unsigned normalized format that has a 4-bit R component in bits 12..15, a 4-bit G component in bits 8..11, a 4-bit B component in bits 4..7, and a 4-bit A component in bits 0..3./VK_FORMAT_R4G4_UNORM_PACK8 specifies a two-component, 8-bit packed unsigned normalized format that has a 4-bit R component in bits 4..7, and a 4-bit G component in bits 0..3.0VK_FORMAT_UNDEFINED, specifies that the format is not specified.# !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./012#210/.-,+*)('&%$#"!      ~}|{zyxwvutsrqponmlkjihgfedcba`_^]\[ZYXWVUTSRQPONMLKJIHGFEDCBA@?>=<;:9876543210/.-,+*)('&%$#"! Safe%ejkL=VK_API_VERSION_1_1 - Return API version number for Vulkan 1.1See Also/, /M=VK_API_VERSION_1_0 - Return API version number for Vulkan 1.0See Also/, /N1VK_MAKE_VERSION - Construct an API version number Descriptionmajor is the major version number.minor is the minor version number.patch is the patch version number. This macro can be used when constructing the /:: apiVersion parameter passed to /.See Also/, /O5VK_HEADER_VERSION - Vulkan header file version numberSee Also!No cross-references are availableP3VK_VERSION_MAJOR - Extract API major version numberSee Also!No cross-references are availableQ3VK_VERSION_MINOR - Extract API minor version numberSee Also!No cross-references are availableLMNOPQRONMLPQRNone"bejkSgVkPhysicalDevice16BitStorageFeatures - Structure describing features supported by VK_KHR_16bit_storageValid Usage (Implicit)sType must be 8VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_16BIT_STORAGE_FEATURESSee AlsoVkBool32, UsType is the type of this structure.VpNext is NULL1 or a pointer to an extension-specific structure.WstorageBuffer16BitAccess# specifies whether objects in the  StorageBuffer storage class with the Block decoration can have 16-bit integer and 16-bit floating-point members. If this feature is not enabled, 16-bit integer or 16-bit floating-point members mustJ not be used in such objects. This also specifies whether shader modules can declare the StorageBuffer16BitAccess capability.X"uniformAndStorageBuffer16BitAccess# specifies whether objects in the Uniform storage class with the Block decoration and in the  StorageBuffer( storage class with the same decoration can have 16-bit integer and 16-bit floating-point members. If this feature is not enabled, 16-bit integer or 16-bit floating-point members mustJ not be used in such objects. This also specifies whether shader modules can declare the "UniformAndStorageBuffer16BitAccess capability.YstoragePushConstant16" specifies whether objects in the  PushConstant storage class can have 16-bit integer and 16-bit floating-point members. If this feature is not enabled, 16-bit integer or floating-point members mustJ not be used in such objects. This also specifies whether shader modules can declare the StoragePushConstant16 capability.ZstorageInputOutput16" specifies whether objects in the Input and Output storage classes can have 16-bit integer and 16-bit floating-point members. If this feature is not enabled, 16-bit integer or 16-bit floating-point members mustJ not be used in such objects. This also specifies whether shader modules can declare the StorageInputOutput16 capability. STUVWXYZ[ [STUVWXYZNone"bejk%_VkPhysicalDeviceShaderDrawParameterFeatures - Structure describing shader draw parameter features that can be supported by an implementation DescriptionIf the +VkPhysicalDeviceShaderDrawParameterFeatures structure is included in the pNext chain of s\I, it is filled with a value indicating whether the feature is supported.Valid Usage (Implicit)sType must be @VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_SHADER_DRAW_PARAMETER_FEATURESSee AlsoVkBool32, cshaderDrawParameters9 specifies whether shader draw parameters are supported._`abcdd_`abcNone"bejkhVkPhysicalDeviceVariablePointerFeatures - Structure describing variable pointers features that can be supported by an implementationMembersThe members of the 'VkPhysicalDeviceVariablePointerFeatures, structure describe the following features: DescriptionvariablePointersStorageBuffer? specifies whether the implementation supports the SPIR-V VariablePointersStorageBufferC capability. When this feature is not enabled, shader modules must not declare the SPV_KHR_variable_pointers extension or the VariablePointersStorageBuffer capability.variablePointers? specifies whether the implementation supports the SPIR-V VariablePointersC capability. When this feature is not enabled, shader modules must not declare the VariablePointers capability.If the 'VkPhysicalDeviceVariablePointerFeatures structure is included in the pNext chain of s\K, it is filled with values indicating whether each feature is supported. 'VkPhysicalDeviceVariablePointerFeatures can also be used in the pNext chain of ~ to enable the features. Valid UsageIf variablePointers is enabled then variablePointersStorageBuffer must also be enabled.Valid Usage (Implicit)sType must be ;VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_VARIABLE_POINTER_FEATURESSee AlsoVkBool32, hijklmnnhijklmSafeejk.rssrSafeejktuut Safeejk vwwv Safeejkxxyyx Safeejkz{{z None"Kbejk|sVkPipelineRasterizationStateRasterizationOrderAMD - Structure defining rasterization order for a graphics pipelineValid Usage (Implicit)sType must be FVK_STRUCTURE_TYPE_PIPELINE_RASTERIZATION_STATE_RASTERIZATION_ORDER_AMDrasterizationOrder must be a valid  valueIf the /{html_spec_relative}#VK_AMD_rasterization_order~ device extension is not enabled or the application does not request a particular rasterization order through specifying a 1VkPipelineRasterizationStateRasterizationOrderAMDT structure then the rasterization order used by the graphics pipeline defaults to !VK_RASTERIZATION_ORDER_STRICT_AMD.See Also, ~sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.rasterizationOrder is a < value specifying the primitive rasterization order to use.NVkRasterizationOrderAMD - Specify rasterization order for a graphics pipelineSee Also|"VK_RASTERIZATION_ORDER_RELAXED_AMD< specifies that operations for each primitive in a subpass may not occur in  ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#drawing-primitive-orderprimitive order.!VK_RASTERIZATION_ORDER_STRICT_AMD< specifies that operations for each primitive in a subpass must occur in  ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#drawing-primitive-orderprimitive order. |}~ |}~ SafeejkCNone"bejk*VkPhysicalDeviceShaderCorePropertiesAMD - Structure describing shader core properties that can be supported by an implementationMembersThe members of the 'VkPhysicalDeviceShaderCorePropertiesAMDC structure describe the following implementation-dependent limits: DescriptionshaderEngineCount is an unsigned integer value indicating the number of shader engines found inside the shader core of the physical device. shaderArraysPerEngineCount is an unsigned integer value indicating the number of shader arrays inside a shader engine. Each shader array has its own scan converter, set of compute units, and a render back end (color and depth buffers). Shader arrays within a shader engine share shader processor input (wave launcher) and shader export (export buffer) units. Currently, a shader engine can have one or two shader arrays.computeUnitsPerShaderArray is an unsigned integer value indicating the number of compute units within a shader array. A compute unit houses a set of SIMDs along with a sequencer module and a local data store.simdPerComputeUnit is an unsigned integer value indicating the number of SIMDs inside a compute unit. Each SIMD processes a single instruction at a time. wavefrontSizea is an unsigned integer value indicating the number of channels (or threads) in a wavefront. sgprsPerSimdw is an unsigned integer value indicating the number of physical Scalar General Purpose Registers (SGPRs) per SIMD.minSgprAllocation_ is an unsigned integer value indicating the minimum number of SGPRs allocated for a wave.maxSgprAllocation_ is an unsigned integer value indicating the maximum number of SGPRs allocated for a wave.sgprAllocationGranularity\ is an unsigned integer value indicating the granularity of SGPR allocation for a wave. vgprsPerSimdw is an unsigned integer value indicating the number of physical Vector General Purpose Registers (VGPRs) per SIMD.minVgprAllocation_ is an unsigned integer value indicating the minimum number of VGPRs allocated for a wave.maxVgprAllocation_ is an unsigned integer value indicating the maximum number of VGPRs allocated for a wave.vgprAllocationGranularity\ is an unsigned integer value indicating the granularity of VGPR allocation for a wave.Valid Usage (Implicit)sType must be <VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_SHADER_CORE_PROPERTIES_AMDIf the 'VkPhysicalDeviceShaderCorePropertiesAMD structure is included in the pNext chain of sf9, it is filled with the implementation-dependent limits.See AlsoSafeejk+Safeejk,ASafeejk,Safeejk-None"bejk6 VkTextureLODGatherFormatPropertiesAMD - Structure informing whether or not texture gather bias/LOD functionality is supported for a given image format and a given physical device.See AlsoVkBool32, sType is the type of this structure.pNext is NULL.supportsTextureGatherLODBiasAMDf tells if the image format can be used with texture gather bias/LOD functions, as introduced by the 3{html_spec_relative}#VK_AMD_texture_gather_bias_lodV extension. This field is set by the implementation. User-specified value is ignored.None"Kbejk gVkPipelineRasterizationConservativeStateCreateInfoEXT - Structure specifying conservative raster state Valid Usage extraPrimitiveOverestimationSize must be in the range of 0.0 to 6VkPhysicalDeviceConservativeRasterizationPropertiesEXT::#maxExtraPrimitiveOverestimationSize inclusiveValid Usage (Implicit)sType must be KVK_STRUCTURE_TYPE_PIPELINE_RASTERIZATION_CONSERVATIVE_STATE_CREATE_INFO_EXTflags must be 0conservativeRasterizationMode must be a valid  valueSee Also, , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.flags is reserved for future use.conservativeRasterizationMode0 is the conservative rasterization mode to use. extraPrimitiveOverestimationSize~ is the extra size in pixels to increase the generating primitive during conservative rasterization at each of its edges in X and YG equally in screen space beyond the base overestimation specified in 6VkPhysicalDeviceConservativeRasterizationPropertiesEXT::primitiveOverestimationSize.VkPhysicalDeviceConservativeRasterizationPropertiesEXT - Structure describing conservative raster properties that can be supported by an implementationMembersThe members of the 6VkPhysicalDeviceConservativeRasterizationPropertiesEXTC structure describe the following implementation-dependent limits: DescriptionprimitiveOverestimationSize is the size in pixels the generating primitive is increased at each of its edges during conservative rasterization overestimation mode. Even with a size of 0.0, conservative rasterization overestimation rules still apply and if any part of the pixel rectangle is covered by the generating primitive, fragments are generated for the entire pixel. However implementations maym make the pixel coverage area even more conservative by increasing the size of the generating primitive.#maxExtraPrimitiveOverestimationSize is the maximum size in pixels of extra overestimation the implementation supports in the pipeline state. A value of 0.0 means the implementation does not support any additional overestimation of the generating primitive during conservative rasterization. A value above 0.0 allows the application to further increase the size of the generating primitive during conservative rasterization overestimation.+extraPrimitiveOverestimationSizeGranularityr is the granularity of extra overestimation that can be specified in the pipeline state between 0.0 and #maxExtraPrimitiveOverestimationSize inclusive. A value of 0.0 means the implementation can use the smallest representable non-zero value in the screen space pixel fixed-point grid.primitiveUnderestimation1 is true if the implementation supports the 4VK_CONSERVATIVE_RASTERIZATION_MODE_UNDERESTIMATE_EXT: conservative rasterization mode in addition to 3VK_CONSERVATIVE_RASTERIZATION_MODE_OVERESTIMATE_EXT7. Otherwise the implementation only supports 3VK_CONSERVATIVE_RASTERIZATION_MODE_OVERESTIMATE_EXT.%conservativePointAndLineRasterization is true if the implementation supports conservative rasterization of point and line primitives as well as triangle primitives. Otherwise the implementation only supports triangle primitives.degenerateTrianglesRasterized is false if the implementation culls primitives generated from triangles that become zero area after they are quantized to the fixed-point rasterization pixel grid. degenerateTrianglesRasterized3 is true if these primitives are not culled and the provoking vertex attributes and depth value are used for the fragments. The primitive area calculation is done on the primitive generated from the clipped triangle if applicable. Zero area primitives are backfacing and the application can) enable backface culling if desired.degenerateLinesRasterized is false if the implementation culls lines that become zero length after they are quantized to the fixed-point rasterization pixel grid. degenerateLinesRasterized is true if zero length lines are not culled and the provoking vertex attributes and depth value are used for the fragments.'fullyCoveredFragmentShaderInputVariable is true if the implementation supports the SPIR-V builtin fragment shader input variable FullyCoveredEXT which specifies that conservative rasterization is enabled and the fragment pixel square is fully covered by the generating primitive.*conservativeRasterizationPostDepthCoverageV is true if the implementation supports conservative rasterization with the  zhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#shaders-fragment-earlytest-postdepthcoverage@PostDepthCoverage@1 execution mode enabled. When supported the  SampleMask built-in input variable will reflect the coverage after the early per-fragment depth and stencil tests are applied even when conservative rasterization is enabled. Otherwise  zhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#shaders-fragment-earlytest-postdepthcoverage@PostDepthCoverage@ execution mode must= not be used when conservative rasterization is enabled.Valid Usage (Implicit)sType must be KVK_STRUCTURE_TYPE_PHYSICAL_DEVICE_CONSERVATIVE_RASTERIZATION_PROPERTIES_EXTIf the 6VkPhysicalDeviceConservativeRasterizationPropertiesEXT structure is included in the pNext chain of tH, it is filled with the implementation-dependent limits and properties.See AlsoVkBool32, QVkPipelineRasterizationConservativeStateCreateFlagsEXT - Reserved for future use Description6VkPipelineRasterizationConservativeStateCreateFlagsEXTQ is a bitmask type for setting a mask, but is currently reserved for future use.See AlsoQVkConservativeRasterizationModeEXT - Specify the conservative rasterization modeSee Also4VK_CONSERVATIVE_RASTERIZATION_MODE_UNDERESTIMATE_EXTO specifies that conservative rasterization is enabled in underestimation mode.3VK_CONSERVATIVE_RASTERIZATION_MODE_OVERESTIMATE_EXTN specifies that conservative rasterization is enabled in overestimation mode./VK_CONSERVATIVE_RASTERIZATION_MODE_DISABLED_EXT^ specifies that conservative rasterization is disabled and rasterization proceeds as normal.Safeejk None"KbejkJVkDeviceQueueGlobalPriorityCreateInfoEXT - Specify a system wide priority Description$A queue created without specifying (VkDeviceQueueGlobalPriorityCreateInfoEXT will default to #VK_QUEUE_GLOBAL_PRIORITY_MEDIUM_EXT.Valid Usage (Implicit)sType must be >VK_STRUCTURE_TYPE_DEVICE_QUEUE_GLOBAL_PRIORITY_CREATE_INFO_EXTglobalPriority must be a valid  valueSee Also, sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.globalPriorityG is the system-wide priority associated to this queue as specified by JVkQueueGlobalPriorityEXT - Values specifying a system-wide queue priority DescriptionPriority values are sorted in ascending order. A comparison operation on the enum values can be used to determine the priority order. VK_QUEUE_GLOBAL_PRIORITY_LOW_EXTD is below the system default. Useful for non-interactive tasks.#VK_QUEUE_GLOBAL_PRIORITY_MEDIUM_EXT% is the system default priority.!VK_QUEUE_GLOBAL_PRIORITY_HIGH_EXT is above the system default.%VK_QUEUE_GLOBAL_PRIORITY_REALTIME_EXT9 is the highest priority. Useful for critical tasks.See AlsoSafeejkSafeejk       Safeejk    SafeejkSafeejk]SafeejkNone"KbejkRVkValidationFlagsEXT - Specify validation checks to disable for a Vulkan instanceValid Usage (Implicit)sType must be &VK_STRUCTURE_TYPE_VALIDATION_FLAGS_EXTpDisabledValidationChecks must( be a valid pointer to an array of disabledValidationCheckCount  valuesdisabledValidationCheckCount must be greater than 0See Also, sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.disabledValidationCheckCount$ is the number of checks to disable.pDisabledValidationChecks is a pointer to an array of 9 values specifying the validation checks to be disabled.;VkValidationCheckEXT - Specify validation checks to disableSee AlsoVK_VALIDATION_CHECK_SHADERS_EXT/ specifies that shader validation is disabled. VK_VALIDATION_CHECK_ALL_EXT4 specifies that all validation checks are disabled.   None"bejk )VkPhysicalDeviceVertexAttributeDivisorPropertiesEXT - Structure describing max value of vertex attribute divisor that can be supported by an implementationMembersThe members of the 3VkPhysicalDeviceVertexAttributeDivisorPropertiesEXTC structure describe the following implementation-dependent limits: DescriptionmaxVertexAttribDivisor is the maximum value of the number of instances that will repeat the value of vertex attribute data when instanced rendering is enabled.Valid Usage (Implicit)sType must be IVK_STRUCTURE_TYPE_PHYSICAL_DEVICE_VERTEX_ATTRIBUTE_DIVISOR_PROPERTIES_EXTSee Also.~VkPipelineVertexInputDivisorStateCreateInfoEXT - Structure specifying vertex attributes assignment during instanced renderingValid Usage (Implicit)sType must be EVK_STRUCTURE_TYPE_PIPELINE_VERTEX_INPUT_DIVISOR_STATE_CREATE_INFO_EXTpVertexBindingDivisors must( be a valid pointer to an array of vertexBindingDivisorCount )VkVertexInputBindingDivisorDescriptionEXT structuresvertexBindingDivisorCount must be greater than 0See Also, 40sType is the type of this structure1pNext is NULL0 or a pointer to an extension-specific structure2vertexBindingDivisorCount# is the number of elements in the pVertexBindingDivisors array.3pVertexBindingDivisors is a pointer to an array of )VkVertexInputBindingDivisorDescriptionEXTA structures, which specifies the divisor value for each binding.4gVkVertexInputBindingDivisorDescriptionEXT - Structure specifying a divisor used in instanced rendering Description|If this structure is not used to define a divisor value for an attribute then the divisor has a logical default value of 1. Valid Usagebinding must be less than VkPhysicalDeviceLimits::maxVertexInputBindingsdivisor must be a value between 0 and 3VkPhysicalDeviceVertexAttributeDivisorPropertiesEXT::maxVertexAttribDivisor, inclusive.H:: inputRate must be of type VK_VERTEX_INPUT_RATE_INSTANCE for this binding.See Also.6binding: is the binding number for which the divisor is specified.7divisor is the the number of successive instances that will use the same value of the vertex attribute when instanced rendering is enabled. For example, if the divisor is N, the same vertex attribute will applied to N successive instances before moving on to the next vertex attribute. If a value of 0 is used for the divisor, then the first vertex attribute will be applied to all instances. The maximum value of divisor is implementation dependent and can be queried using 3VkPhysicalDeviceVertexAttributeDivisorPropertiesEXT::maxVertexAttribDivisor.)*+,-./0123456789:;;:984567./0123)*+,-Noneejk EFGHIJKLMN NMLKJIHGFE None"bejkO7VkImageFormatListCreateInfoKHR - Specify that an image can* be used with a particular set of formats DescriptionIf viewFormatCount is zero,  pViewFormats0 is ignored and the image is created as if the VkImageFormatListCreateInfoKHR% structure were not included in the pNext list of *. Valid UsageIf viewFormatCount is not 0!, all of the formats in the  pViewFormats array must5 be compatible with the format specified in the format field of VkImageCreateInfo, as described in the  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#resources-image-views-compatibilitycompatibility table.If VkImageCreateInfo::flags does not contain "VK_IMAGE_CREATE_MUTABLE_FORMAT_BIT, viewFormatCount must be 0 or 1.If viewFormatCount is not 0, VkImageCreateInfo::format must be in  pViewFormats.Valid Usage (Implicit)sType must be 3VK_STRUCTURE_TYPE_IMAGE_FORMAT_LIST_CREATE_INFO_KHRIf viewFormatCount is not 0,  pViewFormats must( be a valid pointer to an array of viewFormatCount valid  valuesSee Also, QsType is the type of this structure.RpNext is NULL1 or a pointer to an extension-specific structure.SviewFormatCount! is the number of entries in the  pViewFormats array.T pViewFormats. is an array which lists of all formats which can, be used when creating views of this image. OPQRSTUVW WVUOPQRST!Safeejk[\\["Safeejk]^^]#Safeejk_``_$None"Kbejk.amVkPipelineCoverageToColorStateCreateInfoNV - Structure specifying whether fragment coverage replaces a color DescriptionIf coverageToColorEnable is VK_TRUEf, the fragment coverage information is treated as a bitmask with one bit for each sample (as in the  `https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fragops-samplemask Sample Mask section), and this bitmask replaces the first component of the color value corresponding to the fragment shader output location with Location equal to coverageToColorLocation and Index3 equal to zero. If the color attachment format has fewer bits than the sample coverage, the low bits of the sample coverage bitmask are taken without any clamping. If the color attachment format has more bits than the sample coverage, the high bits of the sample coverage bitmask are filled with zeros.If  ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#primsrast-sampleshadingSample Shading is in use, the coverage bitmask only has bits set for samples that correspond to the fragment shader invocation that shades those samples.This pipeline stage occurs after sample counting and before blending, and is always performed after fragment shading regardless of the setting of EarlyFragmentTests.If coverageToColorEnable is VK_FALSEO, these operations are skipped. If this structure is not present, it is as if coverageToColorEnable is VK_FALSE. Valid UsageIf coverageToColorEnable is VK_TRUE6, then the render pass subpass indicated by H':: renderPass and H'::subpass must: have a color attachment at the location selected by coverageToColorLocation, with a  of VK_FORMAT_R8_UINT, VK_FORMAT_R8_SINT, VK_FORMAT_R16_UINT, VK_FORMAT_R16_SINT, VK_FORMAT_R32_UINT, or VK_FORMAT_R32_SINTValid Usage (Implicit)sType must be AVK_STRUCTURE_TYPE_PIPELINE_COVERAGE_TO_COLOR_STATE_CREATE_INFO_NVflags must be 0See AlsoVkBool32, h, csType is the type of this structuredpNext is NULL0 or a pointer to an extension-specific structureeflags is reserved for future use.fcoverageToColorEnableP controls whether the fragment coverage value replaces a fragment color output.gcoverageToColorLocation@ controls which fragment shader color output value is replaced.hEVkPipelineCoverageToColorStateCreateFlagsNV - Reserved for future use Description+VkPipelineCoverageToColorStateCreateFlagsNVQ is a bitmask type for setting a mask, but is currently reserved for future use.See Alsoa abcdefghijkl hilkjabcdefg%None"KbejkdwpVkPipelineCoverageModulationStateCreateInfoNV - Structure specifying parameters controlling coverage modulation DescriptionIf coverageModulationTableEnable is VK_FALSE, then for each color sample the associated bits of the fragment s coverage are counted and divided by the number of associated bits to produce a modulation factor R in the range (0,1] (a value of zero would have been killed due to a color coverage of 0). Specifically: N = value of rasterizationSamplesM = value of ::samples for any color attachments0R = popcount(associated coverage bits) / (N / M)If coverageModulationTableEnable is VK_TRUE, the value R is computed using a programmable lookup table. The lookup table has N / M elements, and the element of the table is selected by:R = pCoverageModulationTable&[popcount(associated coverage bits)-1]Note that the table does not have an entry for popcount(associated coverage bits) = 0, because such samples would have been killed.The values of pCoverageModulationTable mayq be rounded to an implementation-dependent precision, which is at least as fine as 1 / N, and clamped to [0,1].For each color attachment with a floating point or normalized color format, each fragment output color value is replicated to M values which can each be modulated (multiplied) by that color sample s associated value of R. Which components are modulated is controlled by coverageModulationMode.IIf this structure is not present, it is as if coverageModulationMode is #VK_COVERAGE_MODULATION_MODE_NONE_NV. Valid UsageIf coverageModulationTableEnable is VK_TRUE, coverageModulationTableCount mustq be equal to the number of rasterization samples divided by the number of color samples in the subpass.Valid Usage (Implicit)sType must be CVK_STRUCTURE_TYPE_PIPELINE_COVERAGE_MODULATION_STATE_CREATE_INFO_NVflags must be 0coverageModulationMode must be a valid  valuecoverageModulationTableCount must be greater than 0See AlsoVkBool32, , , ysType is the type of this structure.zpNext is NULL1 or a pointer to an extension-specific structure.{flags is reserved for future use.|coverageModulationMode? controls which color components are modulated and is of type .}coverageModulationTableEnableF controls whether the modulation factor is looked up from a table in pCoverageModulationTable.~coverageModulationTableCount is the number of elements in pCoverageModulationTable.pCoverageModulationTableY is a table of modulation factors containing a value for each number of covered samples.HVkPipelineCoverageModulationStateCreateFlagsNV - Reserved for future use Description.VkPipelineCoverageModulationStateCreateFlagsNVQ is a bitmask type for setting a mask, but is currently reserved for future use.See Alsow?VkCoverageModulationModeNV - Specify the discard rectangle modeSee Alsow#VK_COVERAGE_MODULATION_MODE_RGBA_NVH specifies that all components are multiplied by the modulation factor.$VK_COVERAGE_MODULATION_MODE_ALPHA_NVL specifies that the alpha component is multiplied by the modulation factor."VK_COVERAGE_MODULATION_MODE_RGB_NV] specifies that the red, green, and blue components are multiplied by the modulation factor.#VK_COVERAGE_MODULATION_MODE_NONE_NVG specifies that no components are multiplied by the modulation factor.wxyz{|}~wxyz{|}~&Safeejke'Noneejkf"(Safeejkf)Safeejkg*None"Kbejke pVkPipelineViewportSwizzleStateCreateInfoNV - Structure specifying swizzle applied to primitive clip coordinates Valid Usage viewportCount must match the  viewportCount set in !VkPipelineViewportStateCreateInfoValid Usage (Implicit)sType must be @VK_STRUCTURE_TYPE_PIPELINE_VIEWPORT_SWIZZLE_STATE_CREATE_INFO_NVflags must be 0 viewportCount must be greater than 0See Also, , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.flags is reserved for future use. viewportCount9 is the number of viewport swizzles used by the pipeline.pViewportSwizzles is a pointer to an array of - structures, defining the viewport swizzles.=VkViewportSwizzleNV - Structure specifying a viewport swizzleValid Usage (Implicit)x must be a valid  valuey must be a valid  valuez must be a valid  valuew must be a valid  valueSee Also, x is a U value specifying the swizzle operation to apply to the x component of the primitivey is a U value specifying the swizzle operation to apply to the y component of the primitivez is a U value specifying the swizzle operation to apply to the z component of the primitivew is a U value specifying the swizzle operation to apply to the w component of the primitiveEVkPipelineViewportSwizzleStateCreateFlagsNV - Reserved for future use Description+VkPipelineViewportSwizzleStateCreateFlagsNVQ is a bitmask type for setting a mask, but is currently reserved for future use.See AlsoNVkViewportCoordinateSwizzleNV - Specify how a viewport coordinate is swizzled Description(These values are described in detail in  mhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vertexpostproc-viewport-swizzleViewport Swizzle.See Also+Safe,FSTjk'Annotate a type with a name,None-STejk-None-STejkC.None-STjkSvkEnumerateInstanceVersion - Query instance-level version before instance creation Parameters pApiVersion points to a uint32_tr, which is the version of Vulkan supported by instance-level functionality, encoded as described in the  ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-versionnum&API Version Numbers and Semantics section.Valid Usage (Implicit) pApiVersion must be a valid pointer to a uint32_t value Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESSSee Also!No cross-references are available/None "-KSTbejkk4VkDeviceSize - Vulkan device memory size and offsetsSee Also, p, p, , , , , , , , , , f@, fB, , j, Z, , `, r, r, r, , j, j, , , , , , l, , l, , , m, f, F, f5VkSampleCountFlags - Bitmask of VkSampleCountFlagBits DescriptionVkSampleCountFlags7 is a bitmask type for setting a mask of zero or more .See Also, , [j, 9VkFormatFeatureFlags - Bitmask of VkFormatFeatureFlagBits DescriptionVkFormatFeatureFlags7 is a bitmask type for setting a mask of zero or more .See Also, , 5VkImageCreateFlags - Bitmask of VkImageCreateFlagBits DescriptionVkImageCreateFlags7 is a bitmask type for setting a mask of zero or more .See Also, *, s_, 0, 3VkImageUsageFlags - Bitmask of VkImageUsageFlagBits DescriptionVkImageUsageFlags7 is a bitmask type for setting a mask of zero or more .See Also*, , 3, s_, so, , \, K, , 0, , r3VkMemoryHeapFlags - Bitmask of VkMemoryHeapFlagBits DescriptionVkMemoryHeapFlags7 is a bitmask type for setting a mask of zero or more .See Also, ;VkMemoryPropertyFlags - Bitmask of VkMemoryPropertyFlagBits DescriptionVkMemoryPropertyFlags7 is a bitmask type for setting a mask of zero or more .See Also, )VkQueueFlags - Bitmask of VkQueueFlagBits Description VkQueueFlags7 is a bitmask type for setting a mask of zero or more .See Also, ]VkPhysicalDeviceLimits - Structure reporting implementation-dependent physical device limitsMembersmaxImageDimension1D is the maximum dimension (width0) supported for all images created with an  imageType of VK_IMAGE_TYPE_1D.lmaxImageDimension2D is the maximum dimension (width or height0) supported for all images created with an  imageType of VK_IMAGE_TYPE_2D and without #VK_IMAGE_CREATE_CUBE_COMPATIBLE_BIT set in flags.maxImageDimension3D is the maximum dimension (width, height , or depth+) supported for all images created with an  imageType of VK_IMAGE_TYPE_3D.maxImageDimensionCube is the maximum dimension (width or height+) supported for all images created with an  imageType of VK_IMAGE_TYPE_2D and with #VK_IMAGE_CREATE_CUBE_COMPATIBLE_BIT set in flags.maxImageArrayLayers' is the maximum number of layers ( arrayLayers) for an image.maxTexelBufferElementsx is the maximum number of addressable texels for a buffer view created on a buffer which was created with the (VK_BUFFER_USAGE_UNIFORM_TEXEL_BUFFER_BIT or (VK_BUFFER_USAGE_STORAGE_TEXEL_BUFFER_BIT set in the usage member of the VkBufferCreateInfo structure.maxUniformBufferRange is the maximum value that can be specified in the range member of any * structures passed to a call to  for descriptors of type !VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER or )VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER_DYNAMIC.maxStorageBufferRange is the maximum value that can be specified in the range member of any * structures passed to a call to  for descriptors of type !VK_DESCRIPTOR_TYPE_STORAGE_BUFFER or )VK_DESCRIPTOR_TYPE_STORAGE_BUFFER_DYNAMIC.maxPushConstantsSize is the maximum size, in bytes, of the pool of push constant memory. For each of the push constant ranges indicated by the pPushConstantRanges member of the VkPipelineLayoutCreateInfo structure, (offset + size) must* be less than or equal to this limit.maxMemoryAllocationCountM is the maximum number of device memory allocations, as created by f, which can simultaneously exist.maxSamplerAllocationCountC is the maximum number of sampler objects, as created by _, which can' simultaneously exist on a device.bufferImageGranularityk is the granularity, in bytes, at which buffer or linear image resources, and optimal image resources can/ be bound to adjacent offsets in the same VkDeviceMemory# object without aliasing. See  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#resources-bufferimagegranularityBuffer-Image Granularity for more details.sparseAddressSpaceSize is the total amount of address space available, in bytes, for sparse memory resources. This is an upper bound on the sum of the size of all sparse resources, regardless of whether any memory is bound to them.maxBoundDescriptorSets4 is the maximum number of descriptor sets that can+ be simultaneously used by a pipeline. All  DescriptorSet$ decorations in shader modules must have a value less than maxBoundDescriptorSets . See  ahttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-sets({html_spec_relative}#descriptorsets-sets.maxPerStageDescriptorSamplers- is the maximum number of samplers that can^ be accessible to a single shader stage in a pipeline layout. Descriptors with a type of VK_DESCRIPTOR_TYPE_SAMPLER or )VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLERd count against this limit. Only descriptors in descriptor set layouts created without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXTc bit set count against this limit. A descriptor is accessible to a shader stage when the  stageFlags member of the VkDescriptorSetLayoutBinding@ structure has the bit for that shader stage set. See  dhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-sampler+{html_spec_relative}#descriptorsets-sampler and  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-combinedimagesampler8{html_spec_relative}#descriptorsets-combinedimagesampler.#maxPerStageDescriptorUniformBuffers4 is the maximum number of uniform buffers that canc be accessible to a single shader stage in a pipeline layout. Descriptors with a type of !VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER or )VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER_DYNAMICd count against this limit. Only descriptors in descriptor set layouts created without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXTc bit set count against this limit. A descriptor is accessible to a shader stage when the  stageFlags member of the VkDescriptorSetLayoutBinding@ structure has the bit for that shader stage set. See  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-uniformbuffer1{html_spec_relative}#descriptorsets-uniformbuffer and  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-uniformbufferdynamic8{html_spec_relative}#descriptorsets-uniformbufferdynamic.#maxPerStageDescriptorStorageBuffers4 is the maximum number of storage buffers that canc be accessible to a single shader stage in a pipeline layout. Descriptors with a type of !VK_DESCRIPTOR_TYPE_STORAGE_BUFFER or )VK_DESCRIPTOR_TYPE_STORAGE_BUFFER_DYNAMICd count against this limit. Only descriptors in descriptor set layouts created without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXTl bit set count against this limit. A descriptor is accessible to a pipeline shader stage when the  stageFlags member of the VkDescriptorSetLayoutBinding@ structure has the bit for that shader stage set. See  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-storagebuffer1{html_spec_relative}#descriptorsets-storagebuffer and  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-storagebufferdynamic8{html_spec_relative}#descriptorsets-storagebufferdynamic."maxPerStageDescriptorSampledImages3 is the maximum number of sampled images that canc be accessible to a single shader stage in a pipeline layout. Descriptors with a type of )VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLER,  VK_DESCRIPTOR_TYPE_SAMPLED_IMAGE , or 'VK_DESCRIPTOR_TYPE_UNIFORM_TEXEL_BUFFERd count against this limit. Only descriptors in descriptor set layouts created without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXTl bit set count against this limit. A descriptor is accessible to a pipeline shader stage when the  stageFlags member of the VkDescriptorSetLayoutBinding@ structure has the bit for that shader stage set. See  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-combinedimagesampler8{html_spec_relative}#descriptorsets-combinedimagesampler,  ihttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-sampledimage0{html_spec_relative}#descriptorsets-sampledimage, and  ohttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-uniformtexelbuffer6{html_spec_relative}#descriptorsets-uniformtexelbuffer."maxPerStageDescriptorStorageImages3 is the maximum number of storage images that canc be accessible to a single shader stage in a pipeline layout. Descriptors with a type of  VK_DESCRIPTOR_TYPE_STORAGE_IMAGE , or 'VK_DESCRIPTOR_TYPE_STORAGE_TEXEL_BUFFERd count against this limit. Only descriptors in descriptor set layouts created without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXTl bit set count against this limit. A descriptor is accessible to a pipeline shader stage when the  stageFlags member of the VkDescriptorSetLayoutBinding@ structure has the bit for that shader stage set. See  ihttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-storageimage0{html_spec_relative}#descriptorsets-storageimage, and  ohttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-storagetexelbuffer6{html_spec_relative}#descriptorsets-storagetexelbuffer.%maxPerStageDescriptorInputAttachments6 is the maximum number of input attachments that canc be accessible to a single shader stage in a pipeline layout. Descriptors with a type of #VK_DESCRIPTOR_TYPE_INPUT_ATTACHMENTd count against this limit. Only descriptors in descriptor set layouts created without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXTl bit set count against this limit. A descriptor is accessible to a pipeline shader stage when the  stageFlags member of the VkDescriptorSetLayoutBindingq structure has the bit for that shader stage set. These are only supported for the fragment stage. See  lhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-inputattachment3{html_spec_relative}#descriptorsets-inputattachment.maxPerStageResources) is the maximum number of resources that canh be accessible to a single shader stage in a pipeline layout. Descriptors with a type of )VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLER,  VK_DESCRIPTOR_TYPE_SAMPLED_IMAGE,  VK_DESCRIPTOR_TYPE_STORAGE_IMAGE, 'VK_DESCRIPTOR_TYPE_UNIFORM_TEXEL_BUFFER, 'VK_DESCRIPTOR_TYPE_STORAGE_TEXEL_BUFFER, !VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER, !VK_DESCRIPTOR_TYPE_STORAGE_BUFFER, )VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER_DYNAMIC, )VK_DESCRIPTOR_TYPE_STORAGE_BUFFER_DYNAMIC , or #VK_DESCRIPTOR_TYPE_INPUT_ATTACHMENTd count against this limit. Only descriptors in descriptor set layouts created without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT bit set count against this limit. For the fragment shader stage the framebuffer color attachments also count against this limit.maxDescriptorSetSamplers- is the maximum number of samplers that can be included in descriptor bindings in a pipeline layout across all pipeline shader stages and descriptor set numbers. Descriptors with a type of VK_DESCRIPTOR_TYPE_SAMPLER or )VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLERd count against this limit. Only descriptors in descriptor set layouts created without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT1 bit set count against this limit. See  dhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-sampler+{html_spec_relative}#descriptorsets-sampler and  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-combinedimagesampler8{html_spec_relative}#descriptorsets-combinedimagesampler.maxDescriptorSetUniformBuffers4 is the maximum number of uniform buffers that can be included in descriptor bindings in a pipeline layout across all pipeline shader stages and descriptor set numbers. Descriptors with a type of !VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER or )VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER_DYNAMICd count against this limit. Only descriptors in descriptor set layouts created without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT1 bit set count against this limit. See  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-uniformbuffer1{html_spec_relative}#descriptorsets-uniformbuffer and  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-uniformbufferdynamic8{html_spec_relative}#descriptorsets-uniformbufferdynamic.%maxDescriptorSetUniformBuffersDynamic< is the maximum number of dynamic uniform buffers that can be included in descriptor bindings in a pipeline layout across all pipeline shader stages and descriptor set numbers. Descriptors with a type of )VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER_DYNAMICd count against this limit. Only descriptors in descriptor set layouts created without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT1 bit set count against this limit. See  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-uniformbufferdynamic8{html_spec_relative}#descriptorsets-uniformbufferdynamic.maxDescriptorSetStorageBuffers4 is the maximum number of storage buffers that can be included in descriptor bindings in a pipeline layout across all pipeline shader stages and descriptor set numbers. Descriptors with a type of !VK_DESCRIPTOR_TYPE_STORAGE_BUFFER or )VK_DESCRIPTOR_TYPE_STORAGE_BUFFER_DYNAMICd count against this limit. Only descriptors in descriptor set layouts created without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT1 bit set count against this limit. See  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-storagebuffer1{html_spec_relative}#descriptorsets-storagebuffer and  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-storagebufferdynamic8{html_spec_relative}#descriptorsets-storagebufferdynamic.%maxDescriptorSetStorageBuffersDynamic< is the maximum number of dynamic storage buffers that can be included in descriptor bindings in a pipeline layout across all pipeline shader stages and descriptor set numbers. Descriptors with a type of )VK_DESCRIPTOR_TYPE_STORAGE_BUFFER_DYNAMICd count against this limit. Only descriptors in descriptor set layouts created without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT1 bit set count against this limit. See  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-storagebufferdynamic8{html_spec_relative}#descriptorsets-storagebufferdynamic.maxDescriptorSetSampledImages3 is the maximum number of sampled images that can be included in descriptor bindings in a pipeline layout across all pipeline shader stages and descriptor set numbers. Descriptors with a type of )VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLER,  VK_DESCRIPTOR_TYPE_SAMPLED_IMAGE , or 'VK_DESCRIPTOR_TYPE_UNIFORM_TEXEL_BUFFERd count against this limit. Only descriptors in descriptor set layouts created without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT1 bit set count against this limit. See  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-combinedimagesampler8{html_spec_relative}#descriptorsets-combinedimagesampler,  ihttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-sampledimage0{html_spec_relative}#descriptorsets-sampledimage, and  ohttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-uniformtexelbuffer6{html_spec_relative}#descriptorsets-uniformtexelbuffer.maxDescriptorSetStorageImages3 is the maximum number of storage images that can be included in descriptor bindings in a pipeline layout across all pipeline shader stages and descriptor set numbers. Descriptors with a type of  VK_DESCRIPTOR_TYPE_STORAGE_IMAGE , or 'VK_DESCRIPTOR_TYPE_STORAGE_TEXEL_BUFFERd count against this limit. Only descriptors in descriptor set layouts created without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT1 bit set count against this limit. See  ihttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-storageimage0{html_spec_relative}#descriptorsets-storageimage, and  ohttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-storagetexelbuffer6{html_spec_relative}#descriptorsets-storagetexelbuffer. maxDescriptorSetInputAttachments6 is the maximum number of input attachments that can be included in descriptor bindings in a pipeline layout across all pipeline shader stages and descriptor set numbers. Descriptors with a type of #VK_DESCRIPTOR_TYPE_INPUT_ATTACHMENTd count against this limit. Only descriptors in descriptor set layouts created without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT1 bit set count against this limit. See  lhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-inputattachment3{html_spec_relative}#descriptorsets-inputattachment.maxVertexInputAttributes< is the maximum number of vertex input attributes that canP be specified for a graphics pipeline. These are described in the array of !VkVertexInputAttributeDescriptionS structures that are provided at graphics pipeline creation time via the pVertexAttributeDescriptions member of the $VkPipelineVertexInputStateCreateInfo structure. See  ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fxvertex-attrib${html_spec_relative}#fxvertex-attrib and  \https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fxvertex-input#{html_spec_relative}#fxvertex-input.maxVertexInputBindings3 is the maximum number of vertex buffers that cant be specified for providing vertex attributes to a graphics pipeline. These are described in the array of VkVertexInputBindingDescriptionN structures that are provided at graphics pipeline creation time via the pVertexBindingDescriptions member of the $VkPipelineVertexInputStateCreateInfo structure. The binding member of VkVertexInputBindingDescription must( be less than this limit. See  \https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fxvertex-input#{html_spec_relative}#fxvertex-input.maxVertexInputAttributeOffset8 is the maximum vertex input attribute offset that can7 be added to the vertex input binding stride. The offset member of the !VkVertexInputAttributeDescription structure must4 be less than or equal to this limit. See  \https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fxvertex-input#{html_spec_relative}#fxvertex-input.maxVertexInputBindingStride6 is the maximum vertex input binding stride that can2 be specified in a vertex input binding. The stride member of the VkVertexInputBindingDescription structure must/ be less than or equal to this limit. See  \https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fxvertex-input#{html_spec_relative}#fxvertex-input.maxVertexOutputComponentsD is the maximum number of components of output variables which can( be output by a vertex shader. See  \https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#shaders-vertex#{html_spec_relative}#shaders-vertex.maxTessellationGenerationLevel is the maximum tessellation generation level supported by the fixed-function tessellation primitive generator. See  Zhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#tessellation!{html_spec_relative}#tessellation.maxTessellationPatchSize> is the maximum patch size, in vertices, of patches that cane be processed by the tessellation control shader and tessellation primitive generator. The patchControlPoints member of the %VkPipelineTessellationStateCreateInfoW structure specified at pipeline creation time and the value provided in the OutputVertices" execution mode of shader modules must4 be less than or equal to this limit. See  Zhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#tessellation!{html_spec_relative}#tessellation..maxTessellationControlPerVertexInputComponentsC is the maximum number of components of input variables which canP be provided as per-vertex inputs to the tessellation control shader stage./maxTessellationControlPerVertexOutputComponentsO is the maximum number of components of per-vertex output variables which can; be output from the tessellation control shader stage..maxTessellationControlPerPatchOutputComponentsN is the maximum number of components of per-patch output variables which can; be output from the tessellation control shader stage.+maxTessellationControlTotalOutputComponentsh is the maximum total number of components of per-vertex and per-patch output variables which can6 be output from the tessellation control shader stage.(maxTessellationEvaluationInputComponentsC is the maximum number of components of input variables which canS be provided as per-vertex inputs to the tessellation evaluation shader stage.)maxTessellationEvaluationOutputComponentsO is the maximum number of components of per-vertex output variables which can> be output from the tessellation evaluation shader stage.maxGeometryShaderInvocationso is the maximum invocation count supported for instanced geometry shaders. The value provided in the  Invocations" execution mode of shader modules must4 be less than or equal to this limit. See  Vhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#geometry{html_spec_relative}#geometry.maxGeometryInputComponentsC is the maximum number of components of input variables which can9 be provided as inputs to the geometry shader stage.maxGeometryOutputComponentsD is the maximum number of components of output variables which can/ be output from the geometry shader stage.maxGeometryOutputVertices. is the maximum number of vertices which can# be emitted by any geometry shader. maxGeometryTotalOutputComponents^ is the maximum total number of components of output, across all emitted vertices, which can/ be output from the geometry shader stage.maxFragmentInputComponentsC is the maximum number of components of input variables which can9 be provided as inputs to the fragment shader stage.maxFragmentOutputAttachments8 is the maximum number of output attachments which can, be written to by the fragment shader stage.maxFragmentDualSrcAttachments8 is the maximum number of output attachments which can be written to by the fragment shader stage when blending is enabled and one of the dual source blend modes is in use. See  ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#framebuffer-dsb${html_spec_relative}#framebuffer-dsb and  lhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-dualSrcBlend dualSrcBlend."maxFragmentCombinedOutputResourcesW is the total number of storage buffers, storage images, and output buffers which can+ be used in the fragment shader stage.maxComputeSharedMemorySizeV is the maximum total storage size, in bytes, of all variables declared with the WorkgroupLocal3 storage class in shader modules (or with the shared= storage qualifier in GLSL) in the compute shader stage.maxComputeWorkGroupCount8[3] is the maximum number of local workgroups that can be dispatched by a single dispatch command. These three values represent the maximum number of local workgroups for the X, Y, and Z dimensions, respectively. The workgroup count parameters to the dispatch commands mustA be less than or equal to the corresponding limit. See  Vhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#dispatch{html_spec_relative}#dispatch.maxComputeWorkGroupInvocations is the maximum total number of compute shader invocations in a single local workgroup. The product of the X, Y, and Z sizes as specified by the  LocalSizeO execution mode in shader modules and by the object decorated by the  WorkgroupSize decoration must* be less than or equal to this limit.maxComputeWorkGroupSize[3] is the maximum size of a local compute workgroup, per dimension. These three values represent the maximum local workgroup size in the X, Y, and Z dimensions, respectively. The x, y, and z sizes specified by the  LocalSize8 execution mode and by the object decorated by the  WorkgroupSize# decoration in shader modules must7 be less than or equal to the corresponding limit.subPixelPrecisionBitsa is the number of bits of subpixel precision in framebuffer coordinates xf and yf. See  Whttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#primsrast{html_spec_relative}#primsrast.subTexelPrecisionBits is the number of bits of precision in the division along an axis of an image used for minification and magnification filters. 2subTexelPrecisionBits is the actual number of divisions along each axis of the image represented. Sub-texel values calculated during image sampling will snap to these locations when generating the filtered results.mipmapPrecisionBits is the number of bits of division that the LOD calculation for mipmap fetching get snapped to when determining the contribution from each mip level to the mip filtered results. 2mipmapPrecisionBits# is the actual number of divisions.NoteFor example, if this value is 2 bits then when linearly filtering between two levels, each level could: contribute: 0%, 33%, 66%, or 100% (this is just an example and the amount of contribution should0 be covered by different equations in the spec).maxDrawIndexedIndexValue! is the maximum index value that can be used for indexed draw calls when using 32-bit indices. This excludes the primitive restart index value of 0xFFFFFFFF. See  shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-fullDrawIndexUint32fullDrawIndexUint32.maxDrawIndirectCountT is the maximum draw count that is supported for indirect draw calls. See  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-multiDrawIndirectmultiDrawIndirect.maxSamplerLodBias? is the maximum absolute sampler LOD bias. The sum of the  mipLodBias member of the VkSamplerCreateInfo structure and the BiasI operand of image sampling operations in shader modules (or 0 if no BiasZ operand is provided to an image sampling operation) are clamped to the range [-maxSamplerLodBias,+maxSamplerLodBias ]. See  ahttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#samplers-mipLodBias({html_spec_relative}#samplers-mipLodBias.maxSamplerAnisotropy is the maximum degree of sampler anisotropy. The maximum degree of anisotropic filtering used for an image sampling operation is the minimum of the  maxAnisotropy member of the VkSamplerCreateInfo$ structure and this limit. See  dhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#samplers-maxAnisotropy+{html_spec_relative}#samplers-maxAnisotropy. maxViewports5 is the maximum number of active viewports. The  viewportCount member of the !VkPipelineViewportStateCreateInfo6 structure that is provided at pipeline creation must* be less than or equal to this limit.maxViewportDimensions[2] are the maximum viewport dimensions in the X (width) and Y (height) dimensions, respectively. The maximum viewport dimensions must: be greater than or equal to the largest image which can; be created and used as a framebuffer attachment. See  ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vertexpostproc-viewportControlling the Viewport.viewportBoundsRangeH[2] is the [minimum, maximum] range that the corners of a viewport must be contained in. This range must be at least [-2 size, 2 size - 1], where size = max(maxViewportDimensions[0], maxViewportDimensions[1]). See  ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vertexpostproc-viewportControlling the Viewport.NoteThe intent of the viewportBoundsRange limit is to allow a maximum sized viewport to be arbitrarily shifted relative to the output target as long as at least some portion intersects. This would give a bounds limit of [-size + 1, 2 size - 1] which would allow all possible non-empty-set intersections of the output target and the viewport. Since these numbers are typically powers of two, picking the signed number range using the smallest possible number of bits ends up with the specified range.viewportSubPixelBits is the number of bits of subpixel precision for viewport bounds. The subpixel precision that floating-point viewport bounds are interpreted at is given by this limit.minMemoryMapAlignment is the minimum required alignment, in bytes, of host visible memory allocations within the host address space. When mapping a memory allocation with f, subtracting offsetk bytes from the returned pointer will always produce an integer multiple of this limit. See  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-device-hostaccess-{html_spec_relative}#memory-device-hostaccess.minTexelBufferOffsetAlignment is the minimum required# alignment, in bytes, for the offset member of the VkBufferViewCreateInfoo structure for texel buffers. When a buffer view is created for a buffer which was created with (VK_BUFFER_USAGE_UNIFORM_TEXEL_BUFFER_BIT or (VK_BUFFER_USAGE_STORAGE_TEXEL_BUFFER_BIT set in the usage member of the VkBufferCreateInfo structure, the offset must+ be an integer multiple of this limit.minUniformBufferOffsetAlignment is the minimum required# alignment, in bytes, for the offset member of the VkDescriptorBufferInfo? structure for uniform buffers. When a descriptor of type !VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER or )VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER_DYNAMIC is updated, the offset must[ be an integer multiple of this limit. Similarly, dynamic offsets for uniform buffers must be multiples of this limit.minStorageBufferOffsetAlignment is the minimum required# alignment, in bytes, for the offset member of the VkDescriptorBufferInfo? structure for storage buffers. When a descriptor of type !VK_DESCRIPTOR_TYPE_STORAGE_BUFFER or )VK_DESCRIPTOR_TYPE_STORAGE_BUFFER_DYNAMIC is updated, the offset must[ be an integer multiple of this limit. Similarly, dynamic offsets for storage buffers must be multiples of this limit.minTexelOffset% is the minimum offset value for the  ConstOffset" image operand of any of the  OpImageSample* or  OpImageFetch* image instructions.maxTexelOffset% is the maximum offset value for the  ConstOffset" image operand of any of the  OpImageSample* or  OpImageFetch* image instructions.minTexelGatherOffset% is the minimum offset value for the Offset or  ConstOffsets image operands of any of the OpImage*Gather image instructions.maxTexelGatherOffset% is the maximum offset value for the Offset or  ConstOffsets image operands of any of the OpImage*Gather image instructions.minInterpolationOffset3 is the minimum negative offset value for the offset operand of the InterpolateAtOffset extended instruction.maxInterpolationOffset3 is the maximum positive offset value for the offset operand of the InterpolateAtOffset extended instruction.subPixelInterpolationOffsetBits9 is the number of subpixel fractional bits that the x and y offsets to the InterpolateAtOffset extended instruction may* be rounded to as fixed-point values.maxFramebufferWidth2 is the maximum width for a framebuffer. The width member of the VkFramebufferCreateInfo structure must* be less than or equal to this limit.maxFramebufferHeight3 is the maximum height for a framebuffer. The height member of the VkFramebufferCreateInfo structure must* be less than or equal to this limit.maxFramebufferLayers@ is the maximum layer count for a layered framebuffer. The layers member of the VkFramebufferCreateInfo structure must% be less than or equal to this limit.framebufferColorSampleCounts is a bitmask1 of  indicating the color sample counts that are supported for all framebuffer color attachments with floating- or fixed-point formats. There is no limit that specifies the color sample counts that are supported for all color attachments with integer formats.framebufferDepthSampleCounts is a bitmask1 of  indicating the supported depth sample counts for all framebuffer depth/stencil attachments, when the format includes a depth component.framebufferStencilSampleCounts is a bitmask1 of  indicating the supported stencil sample counts for all framebuffer depth/stencil attachments, when the format includes a stencil component.$framebufferNoAttachmentsSampleCounts is a bitmask1 of S indicating the supported sample counts for a framebuffer with no attachments.maxColorAttachments6 is the maximum number of color attachments that can1 be used by a subpass in a render pass. The colorAttachmentCount member of the VkSubpassDescription structure must% be less than or equal to this limit.sampledImageColorSampleCounts is a bitmask1 of L indicating the sample counts supported for all 2D images created with VK_IMAGE_TILING_OPTIMAL, usage containing VK_IMAGE_USAGE_SAMPLED_BIT&, and a non-integer color format.sampledImageIntegerSampleCounts is a bitmask1 of L indicating the sample counts supported for all 2D images created with VK_IMAGE_TILING_OPTIMAL, usage containing VK_IMAGE_USAGE_SAMPLED_BIT#, and an integer color format.sampledImageDepthSampleCounts is a bitmask1 of L indicating the sample counts supported for all 2D images created with VK_IMAGE_TILING_OPTIMAL, usage containing VK_IMAGE_USAGE_SAMPLED_BIT, and a depth format.sampledImageStencilSampleCounts is a bitmask1 of E indicating the sample supported for all 2D images created with VK_IMAGE_TILING_OPTIMAL, usage containing VK_IMAGE_USAGE_SAMPLED_BIT, and a stencil format.storageImageSampleCounts is a bitmask1 of Q indicating the sample counts supported for all 2D images created with VK_IMAGE_TILING_OPTIMAL, and usage containing VK_IMAGE_USAGE_STORAGE_BIT.maxSampleMaskWordsO is the maximum number of array elements of a variable decorated with the  SampleMask built-in decoration.timestampComputeAndGraphicsc specifies support for timestamps on all graphics and compute queues. If this limit is set to VK_TRUE%, all queues that advertise the VK_QUEUE_GRAPHICS_BIT or VK_QUEUE_COMPUTE_BIT in the VkQueueFamilyProperties:: queueFlags support VkQueueFamilyProperties::timestampValidBits of at least 36. See  `https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#queries-timestampsTimestamp Queries.timestampPeriod is the number of nanoseconds required8 for a timestamp query to be incremented by 1. See  `https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#queries-timestampsTimestamp Queries.maxClipDistances3 is the maximum number of clip distances that canP be used in a single shader stage. The size of any array declared with the  ClipDistance- built-in decoration in a shader module must% be less than or equal to this limit.maxCullDistances3 is the maximum number of cull distances that canP be used in a single shader stage. The size of any array declared with the  CullDistance- built-in decoration in a shader module must% be less than or equal to this limit.maxCombinedClipAndCullDistancesE is the maximum combined number of clip and cull distances that canj be used in a single shader stage. The sum of the sizes of any pair of arrays declared with the  ClipDistance and  CullDistanceK built-in decoration used by a single shader stage in a shader module must* be less than or equal to this limit.discreteQueuePriorities0 is the number of discrete priorities that canB be assigned to a queue based on the value of each member of VkDeviceQueueCreateInfo::pQueuePriorities. This must be at least 2, and levels mustd be spread evenly over the range, with at least one level at 1.0, and another at 0.0. See  dhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#devsandqueues-priority+{html_spec_relative}#devsandqueues-priority.pointSizeRange[2] is the range [minimum,maximumZ] of supported sizes for points. Values written to variables decorated with the  PointSize/ built-in decoration are clamped to this range.lineWidthRange[2] is the range [minimum,maximum>] of supported widths for lines. Values specified by the  lineWidth member of the &VkPipelineRasterizationStateCreateInfo or the  lineWidth parameter to vkCmdSetLineWidth are clamped to this range.pointSizeGranularity_ is the granularity of supported point sizes. Not all point sizes in the range defined by pointSizeRangew are supported. This limit specifies the granularity (or increment) between successive supported point sizes.lineWidthGranularity_ is the granularity of supported line widths. Not all line widths in the range defined by lineWidthRangew are supported. This limit specifies the granularity (or increment) between successive supported line widths. strictLinesk specifies whether lines are rasterized according to the preferred method of rasterization. If set to VK_FALSE , lines may< be rasterized under a relaxed set of rules. If set to VK_TRUE>, lines are rasterized as per the strict definition. See  chttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#primsrast-lines-basic%Basic Line Segment Rasterization.standardSampleLocations_ specifies whether rasterization uses the standard sample locations as documented in  ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#primsrast-multisampling Multisampling. If set to VK_TRUEJ, the implementation uses the documented sample locations. If set to VK_FALSE, the implementation may% use different sample locations. optimalBufferCopyOffsetAlignment: is the optimal buffer offset alignment in bytes for vkCmdCopyBufferToImage and vkCmdCopyImageToBufferK. The per texel alignment requirements are enforced, but applications shouldF use the optimal alignment for optimal performance and power use."optimalBufferCopyRowPitchAlignment= is the optimal buffer row pitch alignment in bytes for vkCmdCopyBufferToImage and vkCmdCopyImageToBuffer. Row pitch is the number of bytes between texels with the same X coordinate in adjacent rows (Y coordinates differ by one). The per texel alignment requirements are enforced, but applications shouldF use the optimal alignment for optimal performance and power use.nonCoherentAtomSizeJ is the size and alignment in bytes that bounds concurrent access to  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-device-hostaccesshost-mapped device memory.]V::maxDiscardRectanglesh is the maximum number of active discard rectangles. This limit can be queried by setting the pNext pointer from a sf$ object to an instance of ]V and using vkGetPhysicalDeviceProperties2 to fill out the members.e::pointClippingBehavior] defines the clipping behavior of points. This limit can be queried by setting the pNext pointer from a sf$ object to an instance of e and using vkGetPhysicalDeviceProperties2 to fill out the members.3VkPhysicalDeviceVertexAttributeDivisorPropertiesEXT::maxVertexAttribDivisor is the maximum value of the number of instances that will repeat the value of vertex attribute data when instanced rendering is enabled. This limit can be queried by setting the pNext pointer from a sf$ object to an instance of s and using vkGetPhysicalDeviceProperties2 to fill out the members. Description 1For all bitmasks of , the sample count limits defined above represent the minimum supported sample counts for each image type. Individual images mayE support additional sample counts, which are queried using  as described in  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-supported-sample-countsSupported Sample Counts.See AlsoVkBool32,  VkDeviceSize, , QaVkPhysicalDeviceSparseProperties - Structure specifying physical device sparse memory propertiesSee AlsoVkBool32, SresidencyStandard2DBlockShape is VK_TRUE if the physical device will access all single-sample 2D sparse resources using the standard sparse image block shapes (based on image format), as described in the  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#sparsememory-sparseblockshapessingle3Standard Sparse Image Block Shapes (Single Sample)F table. If this property is not supported the value returned in the imageGranularity member of the VkSparseImageFormatProperties/ structure for single-sample 2D images is not requiredJ to match the standard sparse image block dimensions listed in the table.T(residencyStandard2DMultisampleBlockShape is VK_TRUE if the physical device will access all multisample 2D sparse resources using the standard sparse image block shapes (based on image format), as described in the  phttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#sparsememory-sparseblockshapesmsaa*Standard Sparse Image Block Shapes (MSAA)G table. If this property is not supported, the value returned in the imageGranularity member of the VkSparseImageFormatProperties- structure for multisample 2D images is not requiredJ to match the standard sparse image block dimensions listed in the table.UresidencyStandard3DBlockShape is VK_TRUE if the physical device will access all 3D sparse resources using the standard sparse image block shapes (based on image format), as described in the  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#sparsememory-sparseblockshapessingle4Standard Sparse Image Block Shapes (Single Sample)G table. If this property is not supported, the value returned in the imageGranularity member of the VkSparseImageFormatProperties! structure for 3D images is not requiredJ to match the standard sparse image block dimensions listed in the table.VresidencyAlignedMipSize is VK_TRUE if images with mip level dimensions that are not integer multiples of the corresponding dimensions of the sparse image block mayq be placed in the mip tail. If this property is not reported, only mip levels with dimensions smaller than the imageGranularity member of the VkSparseImageFormatPropertiesr structure will be placed in the mip tail. If this property is reported the implementation is allowed to return +VK_SPARSE_IMAGE_FORMAT_ALIGNED_MIP_SIZE_BIT in the flags member of VkSparseImageFormatProperties, indicating that mip level dimensions that are not integer multiples of the corresponding dimensions of the sparse image block will be placed in the mip tail.WresidencyNonResidentStrict' specifies whether the physical device canO consistently access non-resident regions of a resource. If this property is VK_TRUE, access to non-resident regions of resources will be guaranteed to return values as if the resource were populated with 0; writes to non-resident regions will be discarded.XuVkPhysicalDeviceFeatures - Structure describing the fine-grained features that can be supported by an implementationMembersThe members of the VkPhysicalDeviceFeatures, structure describe the following features: DescriptionrobustBufferAccess~ specifies that accesses to buffers are bounds-checked against the range of the buffer descriptor (as determined by VkDescriptorBufferInfo::range, VkBufferViewCreateInfo::range:, or the size of the buffer). Out of bounds accesses must^ not cause application termination, and the effects of shader loads, stores, and atomics mustI conform to an implementation-dependent behavior as described below.WA buffer access is considered to be out of bounds if any of the following are true:The pointer was formed by OpImageTexelPointerz and the coordinate is less than zero or greater than or equal to the number of whole elements in the bound range.The pointer was not formed by OpImageTexelPointer and the object pointed to is not wholly contained within the bound range. This includes accesses performed via /variable pointers/ where the buffer descriptor being accessed cannot be statically determined. Uninitialized pointers and pointers equal to OpConstantNull are treated as pointing to a zero-sized object, so all accesses through such pointers are considered to be out of bounds.Note If a SPIR-V OpLoad instruction loads a structure and the tail end of the structure is out of bounds, then all members of the structure are considered out of bounds even if the members at the end are not statically used. If any buffer access in a given SPIR-V block is determined to be out of bounds, then any other access of the same type (load, store, or atomic) in the same SPIR-V block that accesses an address less than 16 bytes away from the out of bounds address may" also be considered out of bounds.GOut-of-bounds buffer loads will return any of the following values:Values from anywhere within the memory range(s) bound to the buffer (possibly including bytes of memory past the end of the buffer, up to the end of the bound range).Zero values, or (0,0,0,x) vectors for vector reads where x is a valid value represented in the type of the vector components and may be any of:h0, 1, or the maximum representable positive integer value, for signed or unsigned integer components)0.0 or 1.0, for floating-point componentsOut-of-bounds writes mayG modify values within the memory range(s) bound to the buffer, but must! not modify any other memory.Out-of-bounds atomics mayG modify values within the memory range(s) bound to the buffer, but must@ not modify any other memory, and return an undefined value.Vertex input attributes are considered out of bounds if the offset of the attribute in the bound vertex buffer range plus the size of the attribute is greater than either:vertexBufferRangeSize, if  bindingStride == 0; or(vertexBufferRangeSize - (vertexBufferRangeSize %  bindingStride))where vertexBufferRangeSizeM is the byte size of the memory range bound to the vertex buffer binding and  bindingStride is the byte stride of the corresponding vertex input binding. Further, if any vertex input attribute using a specific vertex input binding is out of bounds, then all vertex input attributes using that vertex input binding for that vertex shader invocation are considered out of bounds.bIf a vertex input attribute is out of bounds, it will be assigned one of the following values:Values from anywhere within the memory range(s) bound to the buffer, converted according to the format of the attribute.KZero values, format converted according to the format of the attribute.6Zero values, or (0,0,0,x) vectors, as described above.If robustBufferAccess, is not enabled, out of bounds accesses mayt corrupt any memory within the process and cause undefined behavior up to and including application termination.6fullDrawIndexUint32g specifies the full 32-bit range of indices is supported for indexed draw calls when using a  of VK_INDEX_TYPE_UINT32. maxDrawIndexedIndexValue& is the maximum index value that may[ be used (aside from the primitive restart index, which is always 232-1 when the  is VK_INDEX_TYPE_UINT32&). If this feature is supported, maxDrawIndexedIndexValue must be 232-1; otherwise it must) be no smaller than 224-1. See  vhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-limits-maxDrawIndexedIndexValuemaxDrawIndexedIndexValue.imageCubeArray+ specifies whether image views with a w of VK_IMAGE_VIEW_TYPE_CUBE_ARRAY can- be created, and that the corresponding SampledCubeArray and ImageCubeArray SPIR-V capabilities can be used in shader code.independentBlend specifies whether the #VkPipelineColorBlendAttachmentStatee settings are controlled independently per-attachment. If this feature is not enabled, the #VkPipelineColorBlendAttachmentState) settings for all color attachments must+ be identical. Otherwise, a different #VkPipelineColorBlendAttachmentState can2 be provided for each bound color attachment.geometryShader\ specifies whether geometry shaders are supported. If this feature is not enabled, the VK_SHADER_STAGE_GEOMETRY_BIT and %VK_PIPELINE_STAGE_GEOMETRY_SHADER_BIT enum values must> not be used. This also specifies whether shader modules can declare the Geometry capability.tessellationShader| specifies whether tessellation control and evaluation shaders are supported. If this feature is not enabled, the (VK_SHADER_STAGE_TESSELLATION_CONTROL_BIT, +VK_SHADER_STAGE_TESSELLATION_EVALUATION_BIT, 1VK_PIPELINE_STAGE_TESSELLATION_CONTROL_SHADER_BIT, 4VK_PIPELINE_STAGE_TESSELLATION_EVALUATION_SHADER_BIT , and 9VK_STRUCTURE_TYPE_PIPELINE_TESSELLATION_STATE_CREATE_INFO enum values must> not be used. This also specifies whether shader modules can declare the  Tessellation capability.sampleRateShading specifies whether  ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#primsrast-sampleshadingSample Shading\ and multisample interpolation are supported. If this feature is not enabled, the sampleShadingEnable member of the $VkPipelineMultisampleStateCreateInfo structure must be set to VK_FALSE and the minSampleShadingD member is ignored. This also specifies whether shader modules can declare the SampleRateShading capability. dualSrcBlendx specifies whether blend operations which take two sources are supported. If this feature is not enabled, the VK_BLEND_FACTOR_SRC1_COLOR, $VK_BLEND_FACTOR_ONE_MINUS_SRC1_COLOR, VK_BLEND_FACTOR_SRC1_ALPHA , and $VK_BLEND_FACTOR_ONE_MINUS_SRC1_ALPHA enum values mustF not be used as source or destination blending factors. See  ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#framebuffer-dsb${html_spec_relative}#framebuffer-dsb.logicOp\ specifies whether logic operations are supported. If this feature is not enabled, the  logicOpEnable member of the #VkPipelineColorBlendStateCreateInfo structure must be set to VK_FALSE , and the logicOp member is ignored.multiDrawIndirecta specifies whether multiple draw indirect is supported. If this feature is not enabled, the  drawCount parameter to the vkCmdDrawIndirect and vkCmdDrawIndexedIndirect commands must be 0 or 1. The maxDrawIndirectCount member of the VkPhysicalDeviceLimits structure must; also be 1 if this feature is not supported. See  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-limits-maxDrawIndirectCountmaxDrawIndirectCount.drawIndirectFirstInstance8 specifies whether indirect draw calls support the  firstInstance5 parameter. If this feature is not enabled, the  firstInstance member of all VkDrawIndirectCommand and VkDrawIndexedIndirectCommand* structures that are provided to the vkCmdDrawIndirect and vkCmdDrawIndexedIndirect commands must be 0. depthClampY specifies whether depth clamping is supported. If this feature is not enabled, the depthClampEnable member of the &VkPipelineRasterizationStateCreateInfo structure must be set to VK_FALSE. Otherwise, setting depthClampEnable to VK_TRUE! will enable depth clamping.depthBiasClamp^ specifies whether depth bias clamping is supported. If this feature is not enabled, the depthBiasClamp member of the &VkPipelineRasterizationStateCreateInfo structure must be set to 0.0 unless the VK_DYNAMIC_STATE_DEPTH_BIAS( dynamic state is enabled, and the depthBiasClamp parameter to vkCmdSetDepthBias must be set to 0.0.fillModeNonSolido specifies whether point and wireframe fill modes are supported. If this feature is not enabled, the VK_POLYGON_MODE_POINT and VK_POLYGON_MODE_LINE enum values must not be used. depthBounds^ specifies whether depth bounds tests are supported. If this feature is not enabled, the depthBoundsTestEnable member of the %VkPipelineDepthStencilStateCreateInfo structure must be set to VK_FALSE. When depthBoundsTestEnable is set to VK_FALSE , the minDepthBounds and maxDepthBounds members of the %VkPipelineDepthStencilStateCreateInfo structure are ignored. wideLinesk specifies whether lines with width other than 1.0 are supported. If this feature is not enabled, the  lineWidth member of the &VkPipelineRasterizationStateCreateInfo structure must be set to 1.0 unless the VK_DYNAMIC_STATE_LINE_WIDTH( dynamic state is enabled, and the  lineWidth parameter to vkCmdSetLineWidth must be set to 1.0. When this feature is supported, the range and granularity of supported line widths are indicated by the lineWidthRange and lineWidthGranularity members of the VkPhysicalDeviceLimits structure, respectively. largePoints specifies whether points with size greater than 1.0 are supported. If this feature is not enabled, only a point size of 1.0 written by a shader is supported. The range and granularity of supported point sizes are indicated by the pointSizeRange and pointSizeGranularity members of the VkPhysicalDeviceLimits structure, respectively. alphaToOne specifies whether the implementation is able to replace the alpha value of the color fragment output from the fragment shader with the maximum representable alpha value for fixed-point colors or 1.0 for floating-point colors. If this feature is not enabled, then the alphaToOneEnable member of the $VkPipelineMultisampleStateCreateInfo structure must be set to VK_FALSE. Otherwise setting alphaToOneEnable to VK_TRUE( will enable alpha-to-one behavior. multiViewporta specifies whether more than one viewport is supported. If this feature is not enabled, the  viewportCount and  scissorCount members of the !VkPipelineViewportStateCreateInfo structure must be set to 1. Similarly, the  viewportCount parameter to the vkCmdSetViewport command and the  scissorCount parameter to the vkCmdSetScissor command must be 1, and the  firstViewport parameter to the vkCmdSetViewport command and the  firstScissor parameter to the vkCmdSetScissor command must be 0.samplerAnisotropy` specifies whether anisotropic filtering is supported. If this feature is not enabled, the anisotropyEnable member of the VkSamplerCreateInfo structure must be VK_FALSE.textureCompressionETC2 specifies whether all of the ETC2 and EAC compressed texture formats are supported. If this feature is enabled, then the #VK_FORMAT_FEATURE_SAMPLED_IMAGE_BIT, VK_FORMAT_FEATURE_BLIT_SRC_BIT and 1VK_FORMAT_FEATURE_SAMPLED_IMAGE_FILTER_LINEAR_BIT features must be supported in optimalTilingFeatures for the following formats: !VK_FORMAT_ETC2_R8G8B8_UNORM_BLOCK  VK_FORMAT_ETC2_R8G8B8_SRGB_BLOCK #VK_FORMAT_ETC2_R8G8B8A1_UNORM_BLOCK "VK_FORMAT_ETC2_R8G8B8A1_SRGB_BLOCK #VK_FORMAT_ETC2_R8G8B8A8_UNORM_BLOCK "VK_FORMAT_ETC2_R8G8B8A8_SRGB_BLOCK VK_FORMAT_EAC_R11_UNORM_BLOCK VK_FORMAT_EAC_R11_SNORM_BLOCK  VK_FORMAT_EAC_R11G11_UNORM_BLOCK  VK_FORMAT_EAC_R11G11_SNORM_BLOCK and  canL be used to check for additional supported properties of individual formats.textureCompressionASTC_LDR specifies whether all of the ASTC LDR compressed texture formats are supported. If this feature is enabled, then the #VK_FORMAT_FEATURE_SAMPLED_IMAGE_BIT, VK_FORMAT_FEATURE_BLIT_SRC_BIT and 1VK_FORMAT_FEATURE_SAMPLED_IMAGE_FILTER_LINEAR_BIT features must be supported in optimalTilingFeatures for the following formats: VK_FORMAT_ASTC_4x4_UNORM_BLOCK VK_FORMAT_ASTC_4x4_SRGB_BLOCK VK_FORMAT_ASTC_5x4_UNORM_BLOCK VK_FORMAT_ASTC_5x4_SRGB_BLOCK VK_FORMAT_ASTC_5x5_UNORM_BLOCK VK_FORMAT_ASTC_5x5_SRGB_BLOCK VK_FORMAT_ASTC_6x5_UNORM_BLOCK VK_FORMAT_ASTC_6x5_SRGB_BLOCK VK_FORMAT_ASTC_6x6_UNORM_BLOCK VK_FORMAT_ASTC_6x6_SRGB_BLOCK VK_FORMAT_ASTC_8x5_UNORM_BLOCK VK_FORMAT_ASTC_8x5_SRGB_BLOCK VK_FORMAT_ASTC_8x6_UNORM_BLOCK VK_FORMAT_ASTC_8x6_SRGB_BLOCK VK_FORMAT_ASTC_8x8_UNORM_BLOCK VK_FORMAT_ASTC_8x8_SRGB_BLOCK VK_FORMAT_ASTC_10x5_UNORM_BLOCK VK_FORMAT_ASTC_10x5_SRGB_BLOCK VK_FORMAT_ASTC_10x6_UNORM_BLOCK VK_FORMAT_ASTC_10x6_SRGB_BLOCK VK_FORMAT_ASTC_10x8_UNORM_BLOCK VK_FORMAT_ASTC_10x8_SRGB_BLOCK  VK_FORMAT_ASTC_10x10_UNORM_BLOCK VK_FORMAT_ASTC_10x10_SRGB_BLOCK  VK_FORMAT_ASTC_12x10_UNORM_BLOCK VK_FORMAT_ASTC_12x10_SRGB_BLOCK  VK_FORMAT_ASTC_12x12_UNORM_BLOCK VK_FORMAT_ASTC_12x12_SRGB_BLOCK and  canL be used to check for additional supported properties of individual formats.textureCompressionBCz specifies whether all of the BC compressed texture formats are supported. If this feature is enabled, then the #VK_FORMAT_FEATURE_SAMPLED_IMAGE_BIT, VK_FORMAT_FEATURE_BLIT_SRC_BIT and 1VK_FORMAT_FEATURE_SAMPLED_IMAGE_FILTER_LINEAR_BIT features must be supported in optimalTilingFeatures for the following formats: VK_FORMAT_BC1_RGB_UNORM_BLOCK VK_FORMAT_BC1_RGB_SRGB_BLOCK VK_FORMAT_BC1_RGBA_UNORM_BLOCK VK_FORMAT_BC1_RGBA_SRGB_BLOCK VK_FORMAT_BC2_UNORM_BLOCK VK_FORMAT_BC2_SRGB_BLOCK VK_FORMAT_BC3_UNORM_BLOCK VK_FORMAT_BC3_SRGB_BLOCK VK_FORMAT_BC4_UNORM_BLOCK VK_FORMAT_BC4_SNORM_BLOCK VK_FORMAT_BC5_UNORM_BLOCK VK_FORMAT_BC5_SNORM_BLOCK VK_FORMAT_BC6H_UFLOAT_BLOCK VK_FORMAT_BC6H_SFLOAT_BLOCK VK_FORMAT_BC7_UNORM_BLOCK VK_FORMAT_BC7_SRGB_BLOCK and  canL be used to check for additional supported properties of individual formats.occlusionQueryPrecise specifies whether occlusion queries returning actual sample counts are supported. Occlusion queries are created in a  VkQueryPool by specifying the  queryType of VK_QUERY_TYPE_OCCLUSION in the VkQueryPoolCreateInfo# structure which is passed to vkCreateQueryPool8. If this feature is enabled, queries of this type can enable VK_QUERY_CONTROL_PRECISE_BIT in the flags parameter to vkCmdBeginQuery. If this feature is not supported, the implementation supports only boolean occlusion queries. When any samples are passed, boolean queries will return a non-zero result value, otherwise a result value of zero is returned. When this feature is enabled and VK_QUERY_CONTROL_PRECISE_BITU is set, occlusion queries will report the actual number of samples passed.pipelineStatisticsQuery| specifies whether the pipeline statistics queries are supported. If this feature is not enabled, queries of type !VK_QUERY_TYPE_PIPELINE_STATISTICS cannot' be created, and none of the F bits can be set in the pipelineStatistics member of the VkQueryPoolCreateInfo structure.vertexPipelineStoresAndAtomics. specifies whether storage buffers and images support stores and atomic operations in the vertex, tessellation, and geometry shader stages. If this feature is not enabled, all storage image, storage texel buffers, and storage buffer variables used by these stages in shader modules must be decorated with the  NonWriteable decoration (or the readonly memory qualifier in GLSL).fragmentStoresAndAtomics specifies whether storage buffers and images support stores and atomic operations in the fragment shader stage. If this feature is not enabled, all storage image, storage texel buffers, and storage buffer variables used by the fragment stage in shader modules must be decorated with the  NonWriteable decoration (or the readonly memory qualifier in GLSL).&shaderTessellationAndGeometryPointSize specifies whether the  PointSize built-in decoration is available in the tessellation control, tessellation evaluation, and geometry shader stages. If this feature is not enabled, members decorated with the  PointSize built-in decoration must not be read from or written to and all points written from a tessellation or geometry shader will have a size of 1.0. This also specifies whether shader modules can declare the TessellationPointSize[ capability for tessellation control and evaluation shaders, or if the shader modules can declare the GeometryPointSizeQ capability for geometry shaders. An implementation supporting this feature must+ also support one or both of the  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-tessellationShader@tessellationShader@ or  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-geometryShader@geometryShader@ features.shaderImageGatherExtended specifies whether the extended set of image gather instructions are available in shader code. If this feature is not enabled, the OpImage*Gather& instructions do not support the Offset and  ConstOffsets; operands. This also specifies whether shader modules can declare the ImageGatherExtended capability.!shaderStorageImageExtendedFormats specifies whether the extended storage image formats are available in shader code. If this feature is not enabled, the formats requiring the StorageImageExtendedFormatsb capability are not supported for storage images. This also specifies whether shader modules can declare the StorageImageExtendedFormats capability.shaderStorageImageMultisample specifies whether multisampled storage images are supported. If this feature is not enabled, images that are created with a usage that includes VK_IMAGE_USAGE_STORAGE_BIT must be created with samples equal to VK_SAMPLE_COUNT_1_BIT2. This also specifies whether shader modules can declare the StorageImageMultisample capability.#shaderStorageImageReadWithoutFormat specifies whether storage images require a format qualifier to be specified when reading from storage images. If this feature is not enabled, the  OpImageRead instruction must not have an  OpTypeImage of Unknown2. This also specifies whether shader modules can declare the StorageImageReadWithoutFormat capability.$shaderStorageImageWriteWithoutFormat specifies whether storage images require a format qualifier to be specified when writing to storage images. If this feature is not enabled, the  OpImageWrite instruction must not have an  OpTypeImage of Unknown2. This also specifies whether shader modules can declare the StorageImageWriteWithoutFormat capability.'shaderUniformBufferArrayDynamicIndexing2 specifies whether arrays of uniform buffers can be indexed by dynamically uniformx integer expressions in shader code. If this feature is not enabled, resources with a descriptor type of !VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER or )VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER_DYNAMIC must be indexed only by constant integral expressions when aggregated into arrays in shader code. This also specifies whether shader modules can declare the !UniformBufferArrayDynamicIndexing capability.&shaderSampledImageArrayDynamicIndexing= specifies whether arrays of samplers or sampled images can be indexed by dynamically uniform integer expressions in shader code. If this feature is not enabled, resources with a descriptor type of VK_DESCRIPTOR_TYPE_SAMPLER, )VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLER , or  VK_DESCRIPTOR_TYPE_SAMPLED_IMAGE must be indexed only by constant integral expressions when aggregated into arrays in shader code. This also specifies whether shader modules can declare the  SampledImageArrayDynamicIndexing capability.'shaderStorageBufferArrayDynamicIndexing2 specifies whether arrays of storage buffers can be indexed by dynamically uniform integer expressions in shader code. If this feature is not enabled, resources with a descriptor type of !VK_DESCRIPTOR_TYPE_STORAGE_BUFFER or )VK_DESCRIPTOR_TYPE_STORAGE_BUFFER_DYNAMIC must be indexed only by constant integral expressions when aggregated into arrays in shader code. This also specifies whether shader modules can declare the !StorageBufferArrayDynamicIndexing capability.&shaderStorageImageArrayDynamicIndexing1 specifies whether arrays of storage images can be indexed by dynamically uniform integer expressions in shader code. If this feature is not enabled, resources with a descriptor type of  VK_DESCRIPTOR_TYPE_STORAGE_IMAGE must be indexed only by constant integral expressions when aggregated into arrays in shader code. This also specifies whether shader modules can declare the  StorageImageArrayDynamicIndexing capability.shaderClipDistance specifies whether clip distances are supported in shader code. If this feature is not enabled, any members decorated with the  ClipDistance built-in decoration musth not be read from or written to in shader modules. This also specifies whether shader modules can declare the  ClipDistance capability.shaderCullDistance specifies whether cull distances are supported in shader code. If this feature is not enabled, any members decorated with the  CullDistance built-in decoration musth not be read from or written to in shader modules. This also specifies whether shader modules can declare the  CullDistance capability. shaderFloat64 specifies whether 64-bit floats (doubles) are supported in shader code. If this feature is not enabled, 64-bit floating-point types mustM not be used in shader code. This also specifies whether shader modules can declare the Float64 capability. shaderInt64 specifies whether 64-bit integers (signed and unsigned) are supported in shader code. If this feature is not enabled, 64-bit integer types mustM not be used in shader code. This also specifies whether shader modules can declare the Int64 capability. shaderInt16 specifies whether 16-bit integers (signed and unsigned) are supported in shader code. If this feature is not enabled, 16-bit integer types mustM not be used in shader code. This also specifies whether shader modules can declare the Int16 capability.shaderResourceResidency specifies whether image operations that return resource residency information are supported in shader code. If this feature is not enabled, the  OpImageSparse* instructions mustM not be used in shader code. This also specifies whether shader modules can declare the SparseResidency; capability. The feature requires at least one of the sparseResidency* features to be supported.shaderResourceMinLod specifies whether image operations that specify the minimum resource LOD are supported in shader code. If this feature is not enabled, the MinLod image operand mustR not be used in shader code. This also specifies whether shader modules can declare the MinLod capability. sparseBinding# specifies whether resource memory can be managed at opaque sparse block level instead of at the object level. If this feature is not enabled, resource memory must4 be bound only on a per-object basis using the vkBindBufferMemory and vkBindImageMemory1 commands. In this case, buffers and images must not be created with #VK_BUFFER_CREATE_SPARSE_BINDING_BIT and "VK_IMAGE_CREATE_SPARSE_BINDING_BIT set in the flags member of the VkBufferCreateInfo and VkImageCreateInfo: structures, respectively. Otherwise resource memory can! be managed as described in  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#sparsememory-sparseresourcefeaturesSparse Resource Features.sparseResidencyBuffer specifies whether the device canV access partially resident buffers. If this feature is not enabled, buffers must not be created with %VK_BUFFER_CREATE_SPARSE_RESIDENCY_BIT set in the flags member of the VkBufferCreateInfo structure.sparseResidencyImage2D specifies whether the device canw access partially resident 2D images with 1 sample per pixel. If this feature is not enabled, images with an  imageType of VK_IMAGE_TYPE_2D and samples set to VK_SAMPLE_COUNT_1_BIT must not be created with $VK_IMAGE_CREATE_SPARSE_RESIDENCY_BIT set in the flags member of the VkImageCreateInfo structure.sparseResidencyImage3D specifies whether the device can_ access partially resident 3D images. If this feature is not enabled, images with an  imageType of VK_IMAGE_TYPE_3D must not be created with $VK_IMAGE_CREATE_SPARSE_RESIDENCY_BIT set in the flags member of the VkImageCreateInfo structure.sparseResidency2Samples, specifies whether the physical device cans access partially resident 2D images with 2 samples per pixel. If this feature is not enabled, images with an  imageType of VK_IMAGE_TYPE_2D and samples set to VK_SAMPLE_COUNT_2_BIT must not be created with $VK_IMAGE_CREATE_SPARSE_RESIDENCY_BIT set in the flags member of the VkImageCreateInfo structure.sparseResidency4Samples, specifies whether the physical device cans access partially resident 2D images with 4 samples per pixel. If this feature is not enabled, images with an  imageType of VK_IMAGE_TYPE_2D and samples set to VK_SAMPLE_COUNT_4_BIT must not be created with $VK_IMAGE_CREATE_SPARSE_RESIDENCY_BIT set in the flags member of the VkImageCreateInfo structure.sparseResidency8Samples, specifies whether the physical device cans access partially resident 2D images with 8 samples per pixel. If this feature is not enabled, images with an  imageType of VK_IMAGE_TYPE_2D and samples set to VK_SAMPLE_COUNT_8_BIT must not be created with $VK_IMAGE_CREATE_SPARSE_RESIDENCY_BIT set in the flags member of the VkImageCreateInfo structure.sparseResidency16Samples, specifies whether the physical device cant access partially resident 2D images with 16 samples per pixel. If this feature is not enabled, images with an  imageType of VK_IMAGE_TYPE_2D and samples set to VK_SAMPLE_COUNT_16_BIT must not be created with $VK_IMAGE_CREATE_SPARSE_RESIDENCY_BIT set in the flags member of the VkImageCreateInfo structure.sparseResidencyAliased' specifies whether the physical device canf correctly access data aliased into multiple locations. If this feature is not enabled, the #VK_BUFFER_CREATE_SPARSE_ALIASED_BIT and "VK_IMAGE_CREATE_SPARSE_ALIASED_BIT enum values must not be used in flags members of the VkBufferCreateInfo and VkImageCreateInfo structures, respectively.variableMultisampleRatew specifies whether all pipelines that will be bound to a command buffer during a subpass with no attachments must have the same value for $VkPipelineMultisampleStateCreateInfo::rasterizationSamples. If set to VK_TRUEj, the implementation supports variable multisample rates in a subpass with no attachments. If set to VK_FALSE2, then all pipelines bound in such a subpass mustq have the same multisample rate. This has no effect in situations where a subpass uses any attachments.inheritedQueries3 specifies whether a secondary command buffer may% be executed while a query is active.See AlsoVkBool32, ~, s\, HVkImageFormatProperties - Structure specifying a image format propertiesMembers maxExtent+ are the maximum image dimensions. See the  ihttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-extentperimagetypeAllowed Extent Values< section below for how these values are constrained by type. maxMipLevels. is the maximum number of mipmap levels.  maxMipLevels must be equal to #log2(max(width, height, depth))# + 1, where width, height, and depth2 are taken from the corresponding members of  maxExtentM, except when one of the following conditions is true, in which case it may instead be 1:(vkGetPhysicalDeviceImageFormatProperties::tiling was VK_IMAGE_TILING_LINEARthe s_::pNext' chain included an instance of Y( with a handle type included in the  handleTypes: member for which mipmap image support is not requiredmaxArrayLayers- is the maximum number of array layers. maxArrayLayers must> either be equal to 1 or be greater than or equal to the maxImageArrayLayers member of  . A value of 1 is valid only if tiling is VK_IMAGE_TILING_LINEAR or if type is VK_IMAGE_TYPE_3D. sampleCounts is a bitmask of R specifying all the supported sample counts for this image as described  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-supported-sample-countsbelow.maxResourceSizeo is an upper bound on the total image size in bytes, inclusive of all image subresources. Implementations mayj have an address space limit on total size of a resource, which is advertised by this property. maxResourceSize must be at least 231. DescriptionNotefThere is no mechanism to query the size of an image before creating it, to compare that size against maxResourceSizef. If an application attempts to create an image that exceeds this limit, the creation will fail and  will return VK_ERROR_OUT_OF_DEVICE_MEMORY. While the advertised limit must be at least 231, it mayQ not be possible to create an image that approaches that size, particularly for VK_IMAGE_TYPE_1D.%If the combination of parameters to (vkGetPhysicalDeviceImageFormatProperties4 is not supported by the implementation for use in , then all members of VkImageFormatProperties will be filled with zero.NoteFilling VkImageFormatProperties with zero for unsupported formats is an exception to the usual rule that output structures have undefined contents on error. This exception was unintentional, but is preserved for backwards compatibility.See Also VkDeviceSize, , 0, s,, , AVkFormatProperties - Structure specifying image format properties DescriptionNote{If no format feature flags are supported, the format itself is not supported, and images of that format cannot be created.If format- is a block-compression format, then buffers must* not support any features for the format.See Also, s%, linearTilingFeatures is a bitmask of 9 specifying features supported by images created with a tiling parameter of VK_IMAGE_TILING_LINEAR.optimalTilingFeatures is a bitmask of 9 specifying features supported by images created with a tiling parameter of VK_IMAGE_TILING_OPTIMAL.bufferFeatures is a bitmask of + specifying features supported by buffers.1VkMemoryHeap - Structure specifying a memory heapSee Also VkDeviceSize, , size/ is the total memory size in bytes in the heap.flags is a bitmask of * specifying attribute flags for the heap./VkMemoryType - Structure specifying memory typeSee Also,  propertyFlags is a bitmask of % of properties for this memory type. heapIndexC describes which memory heap this memory type corresponds to, and must be less than memoryHeapCount from the  structure.ZVkPhysicalDeviceMemoryProperties - Structure specifying physical device memory properties DescriptionThe  VkPhysicalDeviceMemoryProperties" structure describes a number of  memory heaps as well as a number of  memory types that can be used to access memory allocated in those heaps. Each heap describes a memory resource of a particular size, and each memory type describes a set of memory properties (e.g. host cached vs uncached) that can be used with a given memory heap. Allocations using a particular memory type will consume resources from the heap indicated by that memory type s heap index. More than one memory type may share each heap, and the heaps and memory types provide a mechanism to advertise an accurate size of the physical memory resources while allowing the memory to be used with a variety of different properties.'The number of memory heaps is given by memoryHeapCount and is less than or equal to VK_MAX_MEMORY_HEAPS/. Each heap is described by an element of the  memoryHeaps array as a W structure. The number of memory types available across all memory heaps is given by memoryTypeCount and is less than or equal to VK_MAX_MEMORY_TYPES6. Each memory type is described by an element of the  memoryTypes array as a  structure.At least one heap must include VK_MEMORY_HEAP_DEVICE_LOCAL_BIT in ::flagsW. If there are multiple heaps that all have similar performance characteristics, they may all include VK_MEMORY_HEAP_DEVICE_LOCAL_BIT. In a unified memory architecture (UMA) system there is often only a single memory heap which is considered to be equally local  to the host and to the device, and such an implementation must$ advertise the heap as device-local.Each memory type returned by  must have its  propertyFlags$ set to one of the following values: 0#VK_MEMORY_PROPERTY_HOST_VISIBLE_BIT | $VK_MEMORY_PROPERTY_HOST_COHERENT_BIT#VK_MEMORY_PROPERTY_HOST_VISIBLE_BIT | "VK_MEMORY_PROPERTY_HOST_CACHED_BIT#VK_MEMORY_PROPERTY_HOST_VISIBLE_BIT | "VK_MEMORY_PROPERTY_HOST_CACHED_BIT | $VK_MEMORY_PROPERTY_HOST_COHERENT_BIT #VK_MEMORY_PROPERTY_DEVICE_LOCAL_BIT#VK_MEMORY_PROPERTY_DEVICE_LOCAL_BIT | #VK_MEMORY_PROPERTY_HOST_VISIBLE_BIT | $VK_MEMORY_PROPERTY_HOST_COHERENT_BIT#VK_MEMORY_PROPERTY_DEVICE_LOCAL_BIT | #VK_MEMORY_PROPERTY_HOST_VISIBLE_BIT | "VK_MEMORY_PROPERTY_HOST_CACHED_BIT#VK_MEMORY_PROPERTY_DEVICE_LOCAL_BIT | #VK_MEMORY_PROPERTY_HOST_VISIBLE_BIT | "VK_MEMORY_PROPERTY_HOST_CACHED_BIT | $VK_MEMORY_PROPERTY_HOST_COHERENT_BIT#VK_MEMORY_PROPERTY_DEVICE_LOCAL_BIT | 'VK_MEMORY_PROPERTY_LAZILY_ALLOCATED_BITThere must, be at least one memory type with both the #VK_MEMORY_PROPERTY_HOST_VISIBLE_BIT and $VK_MEMORY_PROPERTY_HOST_COHERENT_BIT bits set in its  propertyFlags . There must' be at least one memory type with the #VK_MEMORY_PROPERTY_DEVICE_LOCAL_BIT bit set in its  propertyFlags.For each pair of elements X and Y returned in  memoryTypes, X must* be placed at a lower index position than Y if:,either the set of bit flags returned in the  propertyFlags member of XA is a strict subset of the set of bit flags returned in the  propertyFlags member of Y.or the  propertyFlags members of X and Y are equal, and Xm belongs to a memory heap with greater performance (as determined in an implementation-specific manner).Note)There is no ordering requirement between X and Y elements for the case their  propertyFlags members are not in a subset relation. That potentially allows more than one possible way to order the same set of memory types. Notice that the  hhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-device-bitmask-list7list of all allowed memory property flag combinations4 is written in the required order. But if instead #VK_MEMORY_PROPERTY_DEVICE_LOCAL_BIT was before #VK_MEMORY_PROPERTY_HOST_VISIBLE_BIT | $VK_MEMORY_PROPERTY_HOST_COHERENT_BIT1, the list would still be in the required order.This ordering requirement enables applications to use a simple search loop to select the desired memory type along the lines of:  // Find a memory in `memoryTypeBitsRequirement` that includes all of `requiredProperties` int32_t findProperties(const VkPhysicalDeviceMemoryProperties* pMemoryProperties, uint32_t memoryTypeBitsRequirement, VkMemoryPropertyFlags requiredProperties) { const uint32_t memoryCount = pMemoryProperties->memoryTypeCount; for (uint32_t memoryIndex = 0; memoryIndex < memoryCount; ++memoryIndex) { const uint32_t memoryTypeBits = (1 << memoryIndex); const bool isRequiredMemoryType = memoryTypeBitsRequirement & memoryTypeBits; const VkMemoryPropertyFlags properties = pMemoryProperties->memoryTypes[memoryIndex].propertyFlags; const bool hasRequiredProperties = (properties & requiredProperties) == requiredProperties; if (isRequiredMemoryType && hasRequiredProperties) return static_cast<int32_t>(memoryIndex); } // failed to find memory type return -1; } // Try to find an optimal memory type, or if it does not exist try fallback memory type // `device` is the VkDevice // `image` is the VkImage that requires memory to be bound // `memoryProperties` properties as returned by vkGetPhysicalDeviceMemoryProperties // `requiredProperties` are the property flags that must be present // `optimalProperties` are the property flags that are preferred by the application VkMemoryRequirements memoryRequirements; vkGetImageMemoryRequirements(device, image, &memoryRequirements); int32_t memoryType = findProperties(&memoryProperties, memoryRequirements.memoryTypeBits, optimalProperties); if (memoryType == -1) // not found; try fallback properties memoryType = findProperties(&memoryProperties, memoryRequirements.memoryTypeBits, requiredProperties);See Also, , sa, memoryTypeCount( is the number of valid elements in the  memoryTypes array. memoryTypes is an array of  structures describing the  memory types that canA be used to access memory allocated from the heaps specified by  memoryHeaps.memoryHeapCount( is the number of valid elements in the  memoryHeaps array. memoryHeaps is an array of  structures describing the  memory heaps from which memory can be allocated.OVkQueueFamilyProperties - Structure providing information about a queue family DescriptionThe value returned in minImageTransferGranularityu has a unit of compressed texel blocks for images having a block-compressed format, and a unit of texels otherwise.Possible values of minImageTransferGranularity are:3(0,0,0) which indicates that only whole mip levels must be transferred using the image transfer operations on the corresponding queues. In this case, the following restrictions apply to all offset and extent parameters of image transfer operations:The x, y, and z members of a r parameter must always be zero.The width, height, and depth members of a  parameter musty always match the width, height, and depth of the image subresource corresponding to the parameter, respectively.(Ax, Ay, Az) where Ax, Ay, and Az are all integer powers of two. In this case the following restrictions apply to all image transfer operations:x, y, and z of a r parameter must: be integer multiples of Ax, Ay, and Az, respectively.width of a  parameter must+ be an integer multiple of Ax, or else x + width mustM equal the width of the image subresource corresponding to the parameter.height of a  parameter must+ be an integer multiple of Ay, or else y + height mustN equal the height of the image subresource corresponding to the parameter.depth of a  parameter must+ be an integer multiple of Az, or else z + depth mustM equal the depth of the image subresource corresponding to the parameter.If the format of the image corresponding to the parameters is one of the block-compressed formats then for the purposes of the above calculations the granularity must; be scaled up by the compressed texel block dimensions.5Queues supporting graphics and/or compute operations must report (1,1,1) in minImageTransferGranularity, meaning that there are no additional restrictions on the granularity of image transfer operations for these queues. Other queues supporting image transfer operations are only required- to support whole mip level transfers, thus minImageTransferGranularity. for queues belonging to such queue families may be (0,0,0).The  [https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-deviceDevice MemoryG section describes memory properties queried from the physical device.-For physical device feature queries see the  Vhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#featuresFeatures chapter.See Also, s, ,  queueFlags is a bitmask of = indicating capabilities of the queues in this queue family. queueCount? is the unsigned integer count of queues in this queue family.timestampValidBitsQ is the unsigned integer count of meaningful bits in the timestamps written via vkCmdWriteTimestamp. The valid range for the count is 36..64 bits, or a value of 0, indicating no support for timestamps. Bits outside the valid range are guaranteed to be zeros.minImageTransferGranularityh is the minimum granularity supported for image transfer operations on the queues in this queue family.SVkInstanceCreateInfo - Structure specifying parameters of a newly created instanceValid Usage (Implicit)sType must be &VK_STRUCTURE_TYPE_INSTANCE_CREATE_INFOEach pNext: member of any structure (including this one) in the pNext chain must be either NULL/ or a pointer to a valid instance of 3, C, or Each sType member in the pNext chain must be uniqueflags must be 0If pApplicationInfo is not NULL, pApplicationInfo must$ be a valid pointer to a valid VkApplicationInfo structureIf enabledLayerCount is not 0, ppEnabledLayerNames must( be a valid pointer to an array of enabledLayerCount# null-terminated UTF-8 stringsIf enabledExtensionCount is not 0, ppEnabledExtensionNames must# be a valid pointer to an array of enabledExtensionCount# null-terminated UTF-8 stringsSee Also, , ,  sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.flags is reserved for future use.pApplicationInfo is NULL! or a pointer to an instance of VkApplicationInfo . If not NULLc, this information helps implementations recognize behavior inherent to classes of applications.  is defined in detail below.enabledLayerCount* is the number of global layers to enable.ppEnabledLayerNames is a pointer to an array of enabledLayerCountm null-terminated UTF-8 strings containing the names of layers to enable for the created instance. See the  khttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#extended-functionality-layersLayers section for further details.enabledExtensionCount. is the number of global extensions to enable.ppEnabledExtensionNames is a pointer to an array of enabledExtensionCountM null-terminated UTF-8 strings containing the names of extensions to enable.^VkAllocationCallbacks - Structure containing callback function pointers for memory allocation Valid Usage pfnAllocation must1 be a valid pointer to a valid user-defined pfnReallocation must1 be a valid pointer to a valid user-defined pfnFree must1 be a valid pointer to a valid user-defined  If either of pfnInternalAllocation or pfnInternalFree is not NULL, both must be valid callbacksSee Also, , , , , f, U, , , , H, 3, C, , , , , ~, X, X, }, z, , H, N, , w, ,  , M, S, , G, b, F, , _, x, y , E , ? ,  ,  , 4, L, R, Q, P, O, , , , 3, C, , , , , ~, }, z,  , !, w", #,  , $, H%, G&, b', F(, ), _*, x+, y,, E-, ?., K/, 0, 41, f2, 3, 4 pUserDatad is a value to be interpreted by the implementation of the callbacks. When any of the callbacks in VkAllocationCallbacksq are called, the Vulkan implementation will pass this value as the first parameter to the callback. This value can{ vary each time an allocator is passed into a command, even when the same object takes an allocator in multiple commands. pfnAllocationL is a pointer to an application-defined memory allocation function of type .pfnReallocationN is a pointer to an application-defined memory reallocation function of type .pfnFreeF is a pointer to an application-defined memory free function of type .pfnInternalAllocation is a pointer to an application-defined function that is called by the implementation when the implementation makes internal allocations, and it is of type .pfnInternalFree is a pointer to an application-defined function that is called by the implementation when the implementation frees internal allocations, and it is of type .9VkApplicationInfo - Structure specifying application infoValid Usage (Implicit)sType must be "VK_STRUCTURE_TYPE_APPLICATION_INFOpNext must be NULLIf pApplicationName is not NULL, pApplicationName must' be a null-terminated UTF-8 stringIf  pEngineName is not NULL,  pEngineName must' be a null-terminated UTF-8 stringSee Also, sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.pApplicationName is NULL[ or is a pointer to a null-terminated UTF-8 string containing the name of the application.applicationVersionf is an unsigned integer variable containing the developer-supplied version number of the application. pEngineName is NULL or is a pointer to a null-terminated UTF-8 string containing the name of the engine (if any) used to create the application. engineVersion is an unsigned integer variable containing the developer-supplied version number of the engine used to create the application. apiVersionm is the version of the Vulkan API against which the application expects to run, encoded as described in the  ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-versionnum#API Version Numbers and Semantics section. If  apiVersion is 0 the implementation mustM ignore it, otherwise if the implementation does not support the requested  apiVersion!, or an effective substitute for  apiVersion, it must return VK_ERROR_INCOMPATIBLE_DRIVER). The patch version number specified in  apiVersiona is ignored when creating an instance object. Only the major and minor versions of the instance must match those requested in  apiVersion.MVkPhysicalDeviceProperties - Structure specifying physical device properties DescriptionThe vendorID and deviceID fields are provided to allow applications to adapt to device characteristics that are not adequately exposed by other Vulkan queries.NoteThese mayJ include performance profiles, hardware errata, or other characteristics.The vendor identified by vendorIDj is the entity responsible for the most salient characteristics of the underlying implementation of the  being queried.Note@For example, in the case of a discrete GPU implementation, this shouldq be the GPU chipset vendor. In the case of a hardware accelerator integrated into a system-on-chip (SoC), this shouldC be the supplier of the silicon IP used to create the accelerator.If the vendor has a  .https://pcisig.com/membership/member-companiesPCI vendor ID, the low 16 bits of vendorID must5 contain that PCI vendor ID, and the remaining bits must/ be set to zero. Otherwise, the value returned must= be a valid Khronos vendor ID, obtained as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vulkan-styleguide%Vulkan Documentation and Extensions document in the section Registering a Vendor ID with Khronos . Khronos vendor IDs are allocated starting at 0x10000, to distinguish them from the PCI vendor ID namespace.9The vendor is also responsible for the value returned in deviceID2. If the implementation is driven primarily by a  https://pcisig.com/ PCI device with a  https://pcisig.com/PCI device ID, the low 16 bits of deviceID must5 contain that PCI device ID, and the remaining bits mustA be set to zero. Otherwise, the choice of what values to return may= be dictated by operating system or platform policies - but should uniquely identify both the device version and any major configuration options (for example, core count in the case of multicore devices).NoteThe same device ID should be used for all physical implementations of that device version and configuration. For example, all uses of a specific silicon IP GPU version and configuration shouldE use the same device ID, even if those uses occur in different SoCs.See Also, sf, Q, ,  apiVersionP is the version of Vulkan supported by the device, encoded as described in the  ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-versionnum"API Version Numbers and Semantics section. driverVersion/ is the vendor-specified version of the driver.vendorID is a unique identifier for the vendor% (see below) of the physical device.deviceIDY is a unique identifier for the physical device among devices available from the vendor. deviceType is a  specifying the type of device. deviceNameF is a null-terminated UTF-8 string containing the name of the device.pipelineCacheUUID is an array of size  VK_UUID_SIZEY, containing 8-bit values that represent a universally unique identifier for the device.limits is the P structure which specifies device-specific limits of the physical device. See  ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-limitsLimits for details.sparseProperties is the Q[ structure which specifies various sparse related properties of the physical device. See  hhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#sparsememory-physicalpropsSparse Properties for details.<VkExtent3D - Structure specifying a three-dimensional extentSee Also, 5, *, , 6, , r7, rwidth is the width of the extent.height is the height of the extent.depth is the depth of the extent.+VkDevice - Opaque handle to a device objectSee Also8, 9, :, ;, f, j, p<, q=, j, p>, q?, , , , H, , , , , ~, }, z, , H, , w, , , G, b, F, , _, x, y , E , ? ,  ,  , 4, D@, DA, , , , , , , , ~, }, z,  , !, w", #, $, H%, G&, b', F(, ), _*, x+, y,, E-, ?., 0, 41, @B, C, fD, E, F, f2, G, jH, uI, vJ, K, L, M, N, O, P, f,  , @Q, R, }S, BT, zU, V, jW, uX, vY, rZ, u[, v\, ], ^, _, `, a, b, hc, d, e, G, F, f, g, Ah, i, cj, k, l, m, 4n, Bo, p, Aq, r, fs, f, Gt, 4u, 3, 4, v, w, x, }y, zz, C{, C|, }}, ~, , , f, , , , , zDummy data to tag the  with<VkPhysicalDevice - Opaque handle to a physical device objectSee Also=, =], Z, ~, X, {, |,  , X, X, X, X, X, , , 9, :, 0, 5, 6, , s, t, , s, t, , , s, t, , s, t, S, [, , , s, t, , s, t, r, s, t, \, T, K, T, K, K, K, R, Q, P, O, Z, YDummy data to tag the  with/VkInstance - Opaque handle to a instance objectSee AlsoU, 3, C, X, N,  , M, S, L, R, Q, P, O, 3, 3, C,  , K/, =, >,  ,  , CDummy data to tag the  withDPFN_vkVoidFunction - Dummy function pointer type returned by queriesSee Also ,  =PFN_vkFreeFunction - Application-defined memory free function Parameters pUserData! is the value specified for :: pUserData4 in the allocator specified by the application.pMemory is the allocation to be freed. DescriptionpMemory may be NULL, which the callback must handle safely. If pMemory is non-NULL, it must' be a pointer previously allocated by  pfnAllocation or pfnReallocation. The application should free this memory.See AlsoJPFN_vkAllocationFunction - Application-defined memory allocation function Parameters pUserData! is the value specified for :: pUserData4 in the allocator specified by the application.size2 is the size in bytes of the requested allocation. alignment@ is the requested alignment of the allocation in bytes and must be a power of two.allocationScope is a a value specifying the allocation scope of the lifetime of the allocation, as described  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-host-allocation-scopehere. DescriptionIf  pfnAllocation0 is unable to allocate the requested memory, it must return NULL'. If the allocation was successful, it mustB return a valid pointer to memory allocation containing at least size8 bytes, and with the pointer value being a multiple of  alignment.NoteCorrect Vulkan operation cannot< be assumed if the application does not follow these rules. For example,  pfnAllocation (or pfnReallocation) could cause termination of running Vulkan instance(s) on a failed allocation for debugging purposes, either directly or indirectly. In these circumstances, it cannot+ be assumed that any part of any affected / objects are going to operate correctly (even  ), and the application mustJ ensure it cleans up properly via other means (e.g. process termination).If  pfnAllocation returns NULL, and if the implementation is unable to continue correct processing of the current command without the requested allocation, it must/ treat this as a run-time error, and generate VK_ERROR_OUT_OF_HOST_MEMORY_ at the appropriate time for the command in which the condition was detected, as described in  ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes Return Codes.If the implementation is able to continue correct processing of the current command without the requested allocation, then it may do so, and must not generate VK_ERROR_OUT_OF_HOST_MEMORY( as a result of this failed allocation.See AlsoNPFN_vkReallocationFunction - Application-defined memory reallocation function Parameters pUserData! is the value specified for :: pUserData4 in the allocator specified by the application. pOriginal must be either NULL* or a pointer previously returned by pfnReallocation or  pfnAllocation of the same allocator.size2 is the size in bytes of the requested allocation. alignment@ is the requested alignment of the allocation in bytes and must be a power of two.allocationScope is a a value specifying the allocation scope of the lifetime of the allocation, as described  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-host-allocation-scopehere. DescriptionpfnReallocation must- return an allocation with enough space for sizei bytes, and the contents of the original allocation from bytes zero to min(original size, new size) - 1 must. be preserved in the returned allocation. If size is larger than the old size, the contents of the additional space are undefined. If satisfying these requirements involves creating a new allocation, then the old allocation should be freed.If  pOriginal is NULL, then pfnReallocation must# behave equivalently to a call to * with the same parameter values (without  pOriginal).If size is zero, then pfnReallocation must# behave equivalently to a call to  with the same  pUserData parameter value, and pMemory equal to  pOriginal.If  pOriginal is non-NULL, the implementation must ensure that  alignment is equal to the  alignment used to originally allocate  pOriginal.If this function fails and  pOriginal is non-NULL the application must not free the old allocation.pfnReallocation must follow the same  ohttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkAllocationFunction_return_rules6rules for return values as @PFN_vkAllocationFunction@.See AlsoWPFN_vkInternalFreeNotification - Application-defined memory free notification function Parameters pUserData! is the value specified for :: pUserData4 in the allocator specified by the application.size( is the requested size of an allocation.allocationType is a ; value specifying the requested type of an allocation.allocationScope is a a value specifying the allocation scope of the lifetime of the allocation, as described  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-host-allocation-scopehere.See AlsocPFN_vkInternalAllocationNotification - Application-defined memory allocation notification function Parameters pUserData! is the value specified for :: pUserData4 in the allocator specified by the application.size( is the requested size of an allocation.allocationType is a ; value specifying the requested type of an allocation.allocationScope is a a value specifying the allocation scope of the lifetime of the allocation, as described  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-host-allocation-scopehere. Description(This is a purely informational callback.See AlsolVkSampleCountFlagBits - Bitmask specifying sample counts supported for an image used for storage operationsSee Also, *, so, H~, , [, [, rLVkFormatFeatureFlagBits - Bitmask specifying features supported by a buffer DescriptionThe following bits may be set in linearTilingFeatures and optimalTilingFeatures1, specifying that the features are supported by  Uhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkImageimages or  Yhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkImageView image views created with the queried ::format:#VK_FORMAT_FEATURE_SAMPLED_IMAGE_BIT# specifies that an image view can be  ihttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-sampledimagesampled from.#VK_FORMAT_FEATURE_STORAGE_IMAGE_BIT# specifies that an image view can be used as a  ihttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-storageimagestorage images.*VK_FORMAT_FEATURE_STORAGE_IMAGE_ATOMIC_BIT# specifies that an image view can: be used as storage image that supports atomic operations.&VK_FORMAT_FEATURE_COLOR_ATTACHMENT_BIT# specifies that an image view canK be used as a framebuffer color attachment and as an input attachment.,VK_FORMAT_FEATURE_COLOR_ATTACHMENT_BLEND_BIT# specifies that an image view canb be used as a framebuffer color attachment that supports blending and as an input attachment..VK_FORMAT_FEATURE_DEPTH_STENCIL_ATTACHMENT_BIT# specifies that an image view canS be used as a framebuffer depth/stencil attachment and as an input attachment.VK_FORMAT_FEATURE_BLIT_SRC_BIT specifies that an image can be used as srcImage for the vkCmdBlitImage command.VK_FORMAT_FEATURE_BLIT_DST_BIT specifies that an image can be used as dstImage for the vkCmdBlitImage command.1VK_FORMAT_FEATURE_SAMPLED_IMAGE_FILTER_LINEAR_BIT specifies that if #VK_FORMAT_FEATURE_SAMPLED_IMAGE_BIT! is also set, an image view can+ be used with a sampler that has either of  magFilter or  minFilter set to VK_FILTER_LINEAR, or  mipmapMode set to VK_SAMPLER_MIPMAP_MODE_LINEAR. If VK_FORMAT_FEATURE_BLIT_SRC_BIT/ is also set, an image can be used as the srcImage to  with a filter of VK_FILTER_LINEAR . This bit must8 only be exposed for formats that also support the #VK_FORMAT_FEATURE_SAMPLED_IMAGE_BIT or VK_FORMAT_FEATURE_BLIT_SRC_BIT.If the format being queried is a depth/stencil format, this bit only specifies that the depth aspect (not the stencil aspect) of an image of this format supports linear filtering, and that linear filtering of the depth aspect is supported whether depth compare is enabled in the sampler or not. If this bit is not present, linear filtering with depth compare disabled is unsupported and linear filtering with depth compare enabled is supported, but may compute the filtered value in an implementation-dependent manner which differs from the normal rules of linear filtering. The resulting value must be in the range [0,1] and should[ be proportional to, or a weighted average of, the number of comparison passes or failures."VK_FORMAT_FEATURE_TRANSFER_SRC_BIT specifies that an image can$ be used as a source image for  Thttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#copiescopy commands."VK_FORMAT_FEATURE_TRANSFER_DST_BIT specifies that an image can) be used as a destination image for  Thttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#copiescopy commands and  Thttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#clearsclear commands.5VK_FORMAT_FEATURE_SAMPLED_IMAGE_FILTER_MINMAX_BIT_EXT specifies VkImage can3 be used as a sampled image with a min or max 2. This bit must8 only be exposed for formats that also support the #VK_FORMAT_FEATURE_SAMPLED_IMAGE_BIT.4VK_FORMAT_FEATURE_SAMPLED_IMAGE_FILTER_CUBIC_BIT_IMG specifies that VkImage can0 be used with a sampler that has either of  magFilter or  minFilter set to VK_FILTER_CUBIC_IMG., or be the source image for a blit with filter set to VK_FILTER_CUBIC_IMG. This bit must8 only be exposed for formats that also support the #VK_FORMAT_FEATURE_SAMPLED_IMAGE_BIT. If the format being queried is a depth/stencil format, this only specifies that the depth aspect is cubic filterable.-VK_FORMAT_FEATURE_MIDPOINT_CHROMA_SAMPLES_BIT$ specifies that an application can define a  ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#samplers-YCbCr-conversionsampler Y CBCR conversionK using this format as a source, and that an image of this format can be used with a "VkSamplerYcbcrConversionCreateInfo  xChromaOffset and/or  yChromaOffset of VK_CHROMA_LOCATION_MIDPOINT. Otherwise both  xChromaOffset and  yChromaOffset must be VK_CHROMA_LOCATION_COSITED_EVEN. If a format does not incorporate chroma downsampling (it is not a 422  or 420  format) but the implementation supports sampler Y CBCR conversion for this format, the implementation must set -VK_FORMAT_FEATURE_MIDPOINT_CHROMA_SAMPLES_BIT.,VK_FORMAT_FEATURE_COSITED_CHROMA_SAMPLES_BIT$ specifies that an application can define a  ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#samplers-YCbCr-conversionsampler Y CBCR conversionK using this format as a source, and that an image of this format can be used with a "VkSamplerYcbcrConversionCreateInfo  xChromaOffset and/or  yChromaOffset of VK_CHROMA_LOCATION_COSITED_EVEN. Otherwise both  xChromaOffset and  yChromaOffset must be VK_CHROMA_LOCATION_MIDPOINT. If neither ,VK_FORMAT_FEATURE_COSITED_CHROMA_SAMPLES_BIT nor -VK_FORMAT_FEATURE_MIDPOINT_CHROMA_SAMPLES_BIT is set, the application must not define a  ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#samplers-YCbCr-conversionsampler Y CBCR conversion$ using this format as a source.BVK_FORMAT_FEATURE_SAMPLED_IMAGE_YCBCR_CONVERSION_LINEAR_FILTER_BIT specifies that the format can do linear sampler filtering (min/magFilter) whilst sampler Y CBCR conversion is enabled.SVK_FORMAT_FEATURE_SAMPLED_IMAGE_YCBCR_CONVERSION_SEPARATE_RECONSTRUCTION_FILTER_BITU specifies that the format can have different chroma, min, and mag filters.SVK_FORMAT_FEATURE_SAMPLED_IMAGE_YCBCR_CONVERSION_CHROMA_RECONSTRUCTION_EXPLICIT_BITF specifies that reconstruction is explicit, as described in  lhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#textures-chroma-reconstruction3{html_spec_relative}#textures-chroma-reconstructionI. If this bit is not present, reconstruction is implicit by default.]VK_FORMAT_FEATURE_SAMPLED_IMAGE_YCBCR_CONVERSION_CHROMA_RECONSTRUCTION_EXPLICIT_FORCEABLE_BIT$ specifies that reconstruction can0 be forcibly made explicit by setting x::forceExplicitReconstruction to VK_TRUE.VK_FORMAT_FEATURE_DISJOINT_BIT* specifies that a multi-planar image can have the VK_IMAGE_CREATE_DISJOINT_BIT3 set during image creation. An implementation must not set VK_FORMAT_FEATURE_DISJOINT_BIT for single-plane formats.The following bits may be set in bufferFeatures2, specifying that the features are supported by  Vhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkBufferbuffers or  Zhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkBufferView buffer views created with the queried ::format:*VK_FORMAT_FEATURE_UNIFORM_TEXEL_BUFFER_BIT specifies that the format can& be used to create a buffer view that can be bound to a 'VK_DESCRIPTOR_TYPE_UNIFORM_TEXEL_BUFFER descriptor.*VK_FORMAT_FEATURE_STORAGE_TEXEL_BUFFER_BIT specifies that the format can& be used to create a buffer view that can be bound to a 'VK_DESCRIPTOR_TYPE_STORAGE_TEXEL_BUFFER descriptor.1VK_FORMAT_FEATURE_STORAGE_TEXEL_BUFFER_ATOMIC_BIT= specifies that atomic operations are supported on 'VK_DESCRIPTOR_TYPE_STORAGE_TEXEL_BUFFER with this format.#VK_FORMAT_FEATURE_VERTEX_BUFFER_BIT specifies that the format can, be used as a vertex attribute format (!VkVertexInputAttributeDescription::format).See AlsoMVkImageCreateFlagBits - Bitmask specifying additional parameters of an image Description"VK_IMAGE_CREATE_SPARSE_BINDING_BITJ specifies that the image will be backed using sparse memory binding. $VK_IMAGE_CREATE_SPARSE_RESIDENCY_BIT specifies that the image canU be partially backed using sparse memory binding. Images created with this flag must also be created with the "VK_IMAGE_CREATE_SPARSE_BINDING_BIT flag."VK_IMAGE_CREATE_SPARSE_ALIASED_BIT specifies that the image will be backed using sparse memory binding with memory ranges that might also simultaneously be backing another image (or another portion of the same image). Images created with this flag must also be created with the "VK_IMAGE_CREATE_SPARSE_BINDING_BIT flag"VK_IMAGE_CREATE_MUTABLE_FORMAT_BIT specifies that the image can be used to create a  VkImageView7 with a different format from the image. For  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversion multi-planar formats, "VK_IMAGE_CREATE_MUTABLE_FORMAT_BIT specifies that a  VkImageView can be created of a plane of the image.#VK_IMAGE_CREATE_CUBE_COMPATIBLE_BIT specifies that the image can be used to create a  VkImageView of type VK_IMAGE_VIEW_TYPE_CUBE or VK_IMAGE_VIEW_TYPE_CUBE_ARRAY.'VK_IMAGE_CREATE_2D_ARRAY_COMPATIBLE_BIT specifies that the image can be used to create a  VkImageView of type VK_IMAGE_VIEW_TYPE_2D or VK_IMAGE_VIEW_TYPE_2D_ARRAY./VK_IMAGE_CREATE_SPLIT_INSTANCE_BIND_REGIONS_BIT specifies that the image can+ be used with a non-zero value of the splitInstanceBindRegionCount member of a ^! structure passed into p>m. This flag also has the effect of making the image use the standard sparse image block dimensions./VK_IMAGE_CREATE_BLOCK_TEXEL_VIEW_COMPATIBLE_BIT: specifies that the image having a compressed format can be used to create a  VkImageViewz with an uncompressed format where each texel in the image view corresponds to a compressed texel block of the image."VK_IMAGE_CREATE_EXTENDED_USAGE_BIT specifies that the image can be created with usage flags that are not supported for the format the image is created with but are supported for at least one format a  VkImageView created from the image can have.VK_IMAGE_CREATE_DISJOINT_BIT% specifies that an image with a  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversionmulti-planar format must have each plane separately bound to memory, rather than having a single memory binding for the whole image; the presence of this bit distinguishes a disjoint image) from an image without this bit set.VK_IMAGE_CREATE_ALIAS_BITi specifies that two images created with the same creation parameters and aliased to the same memory cant interpret the contents of the memory consistently with each other, subject to the rules described in the  ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#resources-memory-aliasingMemory Aliasing@ section. This flag further specifies that each plane of a disjoint image cank share an in-memory non-linear representation with single-plane images, and that a single-plane image can share an in-memory non-linear representation with a plane of a multi-planar disjoint image, according to the rules in  phttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-compatible-planes7{html_spec_relative}#features-formats-compatible-planes. If the pNext chain includes a  or 1  structure whose  handleTypes member is not 0, it is as if VK_IMAGE_CREATE_ALIAS_BIT is set.9VK_IMAGE_CREATE_SAMPLE_LOCATIONS_COMPATIBLE_DEPTH_BIT_EXTC specifies that an image with a depth or depth/stencil format canX be used with custom sample locations when used as a depth/stencil attachment.See  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#sparsememory-sparseresourcefeaturesSparse Resource Features and  khttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#sparsememory-physicalfeatures Sparse Physical Device Features for more details.See AlsoDVkImageUsageFlagBits - Bitmask specifying intended usage of an imageSee AlsoDVkMemoryHeapFlagBits - Bitmask specifying attribute flags for a heapSee AlsoKVkMemoryPropertyFlagBits - Bitmask specifying properties for a memory typeSee AlsoNVkQueueFlagBits - Bitmask specifying capabilities of queues in a queue family DescriptionVK_QUEUE_GRAPHICS_BITM specifies that queues in this queue family support graphics operations.VK_QUEUE_COMPUTE_BITL specifies that queues in this queue family support compute operations.VK_QUEUE_TRANSFER_BITM specifies that queues in this queue family support transfer operations.VK_QUEUE_SPARSE_BINDING_BITb specifies that queues in this queue family support sparse memory management operations (see  Zhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#sparsememorySparse Resources`). If any of the sparse resource features are enabled, then at least one queue family must support this bit.If an implementation exposes any queue family that supports graphics operations, at least one queue family of at least one physical device exposed by the implementation must/ support both graphics and compute operations.NoteAll commands that are allowed on a queue that supports transfer operations are also allowed on a queue that supports either graphics or compute operations. Thus, if the capabilities of a queue family include VK_QUEUE_GRAPHICS_BIT or VK_QUEUE_COMPUTE_BIT, then reporting the VK_QUEUE_TRANSFER_BIT1 capability separately for that queue family is optional.For further details see  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#devsandqueues-queuesQueues.See Also/VkInstanceCreateFlags - Reserved for future use DescriptionVkInstanceCreateFlagsQ is a bitmask type for setting a mask, but is currently reserved for future use.See Also*VkInternalAllocationType - Allocation typeSee Also, *VkSystemAllocationScope - Allocation scope Description"VK_SYSTEM_ALLOCATION_SCOPE_COMMANDT specifies that the allocation is scoped to the duration of the Vulkan command.!VK_SYSTEM_ALLOCATION_SCOPE_OBJECTv specifies that the allocation is scoped to the lifetime of the Vulkan object that is being created or used. VK_SYSTEM_ALLOCATION_SCOPE_CACHEC specifies that the allocation is scoped to the lifetime of a VkPipelineCache or VkValidationCacheEXT object.!VK_SYSTEM_ALLOCATION_SCOPE_DEVICES specifies that the allocation is scoped to the lifetime of the Vulkan device.#VK_SYSTEM_ALLOCATION_SCOPE_INSTANCEU specifies that the allocation is scoped to the lifetime of the Vulkan instance.Most Vulkan commands operate on a single object, or there is a sole object that is being created or manipulated. When an allocation uses an allocation scope of !VK_SYSTEM_ALLOCATION_SCOPE_OBJECT or  VK_SYSTEM_ALLOCATION_SCOPE_CACHEG, the allocation is scoped to the object being created or manipulated.When an implementation requires host memory, it will make callbacks to the application using the most specific allocator and allocation scope available:YIf an allocation is scoped to the duration of a command, the allocator will use the "VK_SYSTEM_ALLOCATION_SCOPE_COMMAND allocation scope. The most specific allocator available is used: if the object being created or manipulated has an allocator, that object s allocator will be used, else if the parent VkDevice; has an allocator it will be used, else if the parent  VkInstance- has an allocator it will be used. Else,;If an allocation is associated with an object of type VkValidationCacheEXT or VkPipelineCache", the allocator will use the  VK_SYSTEM_ALLOCATION_SCOPE_CACHEu allocation scope. The most specific allocator available is used (cache, else device, else instance). Else,If an allocation is scoped to the lifetime of an object, that object is being created or manipulated by the command, and that object s type is not VkDevice or  VkInstance5, the allocator will use an allocation scope of !VK_SYSTEM_ALLOCATION_SCOPE_OBJECTe. The most specific allocator available is used (object, else device, else instance). Else,pIf an allocation is scoped to the lifetime of a device, the allocator will use an allocation scope of !VK_SYSTEM_ALLOCATION_SCOPE_DEVICES. The most specific allocator available is used (device, else instance). Else,If the allocation is scoped to the lifetime of an instance and the instance has an allocator, its allocator will be used with an allocation scope of #VK_SYSTEM_ALLOCATION_SCOPE_INSTANCE.kOtherwise an implementation will allocate memory through an alternative mechanism that is unspecified.See Also6VkPhysicalDeviceType - Supported physical device types DescriptionVK_PHYSICAL_DEVICE_TYPE_OTHER< - the device does not match any other available types.&VK_PHYSICAL_DEVICE_TYPE_INTEGRATED_GPUQ - the device is typically one embedded in or tightly coupled with the host.$VK_PHYSICAL_DEVICE_TYPE_DISCRETE_GPU\ - the device is typically a separate processor connected to the host via an interlink.#VK_PHYSICAL_DEVICE_TYPE_VIRTUAL_GPUO - the device is typically a virtual node in a virtualization environment.VK_PHYSICAL_DEVICE_TYPE_CPUK - the device is typically running on the same processors as the host.The physical device type is advertised for informational purposes only, and does not directly affect the operation of the system. However, the device type mayt correlate with other advertised properties or capabilities of the system, such as how many memory heaps there are.See Also3VkImageType - Specifies the type of an image objectSee Also*, s_, so, 0, , rDVkImageTiling - Specifies the tiling arrangement of data in an imageSee Also*, s_, so, 0, , r]vkGetPhysicalDeviceImageFormatProperties - Lists physical device s image format capabilities ParametersphysicalDeviceH is the physical device from which to query the image capabilities.format is a ? value specifying the image format, corresponding to *::format.type is a = value specifying the image type, corresponding to *:: imageType.tiling is a ? value specifying the image tiling, corresponding to *::tiling.usage is a bitmask of H specifying the intended usage of the image, corresponding to *::usage.flags is a bitmask of K specifying additional parameters of the image, corresponding to *::flags.pImageFormatProperties# points to an instance of the 3 structure in which capabilities are returned. DescriptionThe format, type, tiling, usage, and flagsA parameters correspond to parameters that would be consumed by  (as members of VkImageCreateInfo).If format< is not a supported image format, or if the combination of format, type, tiling, usage, and flags$ is not supported for images, then (vkGetPhysicalDeviceImageFormatProperties returns VK_ERROR_FORMAT_NOT_SUPPORTED.9The limitations on an image format that are reported by (vkGetPhysicalDeviceImageFormatProperties" have the following property: if usage1 and usage2 of type  are such that the bits set in usage1! are a subset of the bits set in usage2, and flags1 and flags2 of type  are such that the bits set in flags1! are a subset of the bits set in flags2, then the limitations for usage1 and flags1 must- be no more strict than the limitations for usage2 and flags2, for all values of format, type, and tiling.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handleformat must be a valid  valuetype must be a valid  valuetiling must be a valid  valueusage must be a valid combination of  valuesusage must not be 0flags must be a valid combination of  valuespImageFormatProperties must be a valid pointer to a VkImageFormatProperties structure Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_FORMAT_NOT_SUPPORTEDSee Also, , , , , , RvkGetPhysicalDeviceFormatProperties - Lists physical device s format capabilities ParametersphysicalDeviceG is the physical device from which to query the format properties.format, is the format whose properties are queried.pFormatProperties is a pointer to a 8 structure in which physical device properties for format are returned.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handleformat must be a valid  valuepFormatProperties must be a valid pointer to a VkFormatProperties structureSee Also, , GvkGetPhysicalDeviceFeatures - Reports capabilities of a physical device ParametersphysicalDeviceH is the physical device from which to query the supported features. pFeatures is a pointer to a Xf structure in which the physical device features are returned. For each feature, a value of VK_TRUEK specifies that the feature is supported on this physical device, and VK_FALSE2 specifies that the feature is not supported.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handle pFeatures must be a valid pointer to a VkPhysicalDeviceFeatures structureSee Also, XcvkGetPhysicalDeviceMemoryProperties - Reports memory information for the specified physical device ParametersphysicalDevice& is the handle to the device to query.pMemoryProperties points to an instance of  VkPhysicalDeviceMemoryProperties5 structure in which the properties are returned.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handlepMemoryProperties must be a valid pointer to a  VkPhysicalDeviceMemoryProperties structureSee Also, mvkGetPhysicalDeviceQueueFamilyProperties - Reports properties of the queues of the specified physical device ParametersphysicalDeviceL is the handle to the physical device whose properties will be queried.pQueueFamilyPropertyCountw is a pointer to an integer related to the number of queue families available or queried, as described below.pQueueFamilyProperties is either NULL" or a pointer to an array of  structures. DescriptionIf pQueueFamilyProperties is NULL>, then the number of queue families available is returned in pQueueFamilyPropertyCount. Otherwise, pQueueFamilyPropertyCount mustG point to a variable set by the user to the number of elements in the pQueueFamilyPropertiesf array, and on return the variable is overwritten with the number of structures actually written to pQueueFamilyProperties. If pQueueFamilyPropertyCount? is less than the number of queue families available, at most pQueueFamilyPropertyCount structures will be written.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handlepQueueFamilyPropertyCount must be a valid pointer to a uint32_t valueIf the value referenced by pQueueFamilyPropertyCount is not 0 , and pQueueFamilyProperties is not NULL, pQueueFamilyProperties must# be a valid pointer to an array of pQueueFamilyPropertyCount VkQueueFamilyProperties structuresSee Also, GvkGetPhysicalDeviceProperties - Returns properties of a physical device ParametersphysicalDeviceL is the handle to the physical device whose properties will be queried. pProperties# points to an instance of the ? structure, that will be filled with returned information.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handle pProperties must be a valid pointer to a VkPhysicalDeviceProperties structureSee Also,  ?vkGetInstanceProcAddr - Return a function pointer for a command ParametersinstanceL is the instance that the function pointer will be compatible with, or NULL1 for commands not dependent on any instance.pName& is the name of the command to obtain. DescriptionvkGetInstanceProcAddr itself is obtained in a platform- and loader- specific manner. Typically, the loader library will export this command as a function symbol, so applications cano link against the loader library, or load it dynamically and look up the symbol using platform-specific APIs.3The table below defines the various use cases for vkGetInstanceProcAddrG and expected return value ( fp  is function pointer ) for each case.)The returned function pointer is of type =, and must be cast to the type of the command being queried. instance  pNameL  return value  *  NULLM  undefined  invalid instance T *  undefined  NULL  {  fp  NULL  |  fp  NULL   A  fp  NULL  * (any pNameE not covered above)  NULL  instance T core Vulkan command  fp1  instance ) enabled instance extension commands for instance!  fp1  instance * available device extension2 commands for instance  fp1  instance  * (any pNameE not covered above)  NULL vkGetInstanceProcAddr behavior 1The returned function pointer mustN only be called with a dispatchable object (the first parameter) that is instance or a child of instance, e.g. , , , @ , or @.2jAn available device extension  is a device extension supported by any physical device enumerated by instance.Valid Usage (Implicit)If instance is not NULL, instance must be a valid  VkInstance handlepName must" be a null-terminated UTF-8 stringSee Also,  =vkGetDeviceProcAddr - Return a function pointer for a command Parameters2The table below defines the various use cases for vkGetDeviceProcAddr* and expected return value for each case. Description)The returned function pointer is of type T, and must be cast to the type of the command being queried. The function pointer mustJ only be called with a dispatchable object (the first parameter) that is device or a child of device. device  pName  return value  NULL  *  undefined  invalid device  *  undefined  device  NULL  undefined / device / core device-level Vulkan command / fp / device / enabled device extension commands / fp / device  * (any pName not covered above)  NULL( vkGetDeviceProcAddr behaviorValid Usage (Implicit)device must be a valid VkDevice handlepName must" be a null-terminated UTF-8 stringSee Also,  ]vkEnumeratePhysicalDevices - Enumerates the physical devices accessible to a Vulkan instance Parametersinstance? is a handle to a Vulkan instance previously created with  .pPhysicalDeviceCountt is a pointer to an integer related to the number of physical devices available or queried, as described below.pPhysicalDevices is either NULL" or a pointer to an array of VkPhysicalDevice handles. DescriptionIf pPhysicalDevices is NULL@, then the number of physical devices available is returned in pPhysicalDeviceCount. Otherwise, pPhysicalDeviceCount mustG point to a variable set by the user to the number of elements in the pPhysicalDevicesc array, and on return the variable is overwritten with the number of handles actually written to pPhysicalDevices. If pPhysicalDeviceCountA is less than the number of physical devices available, at most pPhysicalDeviceCount! structures will be written. If pPhysicalDeviceCount< is smaller than the number of physical devices available,  VK_INCOMPLETE will be returned instead of  VK_SUCCESSI, to indicate that not all the available physical devices were returned.Valid Usage (Implicit)instance must be a valid  VkInstance handlepPhysicalDeviceCount must be a valid pointer to a uint32_t valueIf the value referenced by pPhysicalDeviceCount is not 0 , and pPhysicalDevices is not NULL, pPhysicalDevices must( be a valid pointer to an array of pPhysicalDeviceCount VkPhysicalDevice handles Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS  VK_INCOMPLETE ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_INITIALIZATION_FAILEDSee Also,  1vkDestroyInstance - Destroy an instance of Vulkan Parametersinstance* is the handle of the instance to destroy. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. Valid Usage All child objects created using instance must. have been destroyed prior to destroying instanceIf VkAllocationCallbacks were provided when instance1 was created, a compatible set of callbacks must be provided hereIf no VkAllocationCallbacks were provided when instance was created,  pAllocator must be NULLValid Usage (Implicit)If instance is not NULL, instance must be a valid  VkInstance handleIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structureHost SynchronizationHost access to instance must be externally synchronizedSee Also,  /vkCreateInstance - Create a new Vulkan instance Parameters pCreateInfo points to an instance of + controlling creation of the instance. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. pInstance points a  VkInstance9 handle in which the resulting instance is returned. DescriptionvkCreateInstance4 verifies that the requested layers exist. If not, vkCreateInstance will return VK_ERROR_LAYER_NOT_PRESENT. Next vkCreateInstance verifies that the requested extensions are supported (e.g. in the implementation or in any enabled instance layer) and if any requested extension is not supported, vkCreateInstance must return VK_ERROR_EXTENSION_NOT_PRESENTG. After verifying and enabling the instance layers and extensions the  VkInstance object is created and returned to the application. If a requested extension is only supported by a layer, both the layer and the extension need to be specified at vkCreateInstance" time for the creation to succeed. Valid UsageAll  |https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#extended-functionality-extensions-dependenciesrequired extensions% for each extension in the ::ppEnabledExtensionNames list must# also be present in that list.Valid Usage (Implicit) pCreateInfo must$ be a valid pointer to a valid VkInstanceCreateInfo structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structure pInstance must be a valid pointer to a  VkInstance handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_INITIALIZATION_FAILED VK_ERROR_LAYER_NOT_PRESENT VK_ERROR_EXTENSION_NOT_PRESENT VK_ERROR_INCOMPATIBLE_DRIVERSee Also, , VK_SAMPLE_COUNT_64_BIT. specifies an image with 64 samples per pixel.VK_SAMPLE_COUNT_32_BIT. specifies an image with 32 samples per pixel.VK_SAMPLE_COUNT_16_BIT. specifies an image with 16 samples per pixel.VK_SAMPLE_COUNT_8_BIT- specifies an image with 8 samples per pixel.VK_SAMPLE_COUNT_4_BIT- specifies an image with 4 samples per pixel.VK_SAMPLE_COUNT_2_BIT- specifies an image with 2 samples per pixel.VK_SAMPLE_COUNT_1_BIT. specifies an image with one sample per pixel.+#VK_IMAGE_USAGE_INPUT_ATTACHMENT_BIT specifies that the image can be used to create a  VkImageView suitable for occupying VkDescriptorSet slot of type #VK_DESCRIPTOR_TYPE_INPUT_ATTACHMENTf; be read from a shader as an input attachment; and be used as an input attachment in a framebuffer.,'VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BITS specifies that the memory bound to this image will have been allocated with the 'VK_MEMORY_PROPERTY_LAZILY_ALLOCATED_BIT (see  Thttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory{html_spec_relative}#memory for more detail). This bit can be set for any image that can be used to create a  VkImageViewK suitable for use as a color, resolve, depth/stencil, or input attachment.-+VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT specifies that the image can be used to create a  VkImageView6 suitable for use as a depth/stencil attachment in a  VkFramebuffer..#VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT specifies that the image can be used to create a  VkImageView9 suitable for use as a color or resolve attachment in a  VkFramebuffer./VK_IMAGE_USAGE_STORAGE_BIT specifies that the image can be used to create a  VkImageView suitable for occupying a VkDescriptorSet slot of type  VK_DESCRIPTOR_TYPE_STORAGE_IMAGE.0VK_IMAGE_USAGE_SAMPLED_BIT specifies that the image can be used to create a  VkImageView suitable for occupying a VkDescriptorSet slot either of type  VK_DESCRIPTOR_TYPE_SAMPLED_IMAGE or )VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLER, and be sampled by a shader.1VK_IMAGE_USAGE_TRANSFER_DST_BIT specifies that the image can3 be used as the destination of a transfer command.2VK_IMAGE_USAGE_TRANSFER_SRC_BIT specifies that the image can. be used as the source of a transfer command.3VK_MEMORY_HEAP_DEVICE_LOCAL_BITR specifies that the heap corresponds to device local memory. Device local memory mayI have different performance characteristics than host local memory, and may* support different memory property flags.4'VK_MEMORY_PROPERTY_LAZILY_ALLOCATED_BIT[ bit specifies that the memory type only allows device access to the memory. Memory types must not have both 'VK_MEMORY_PROPERTY_LAZILY_ALLOCATED_BIT and #VK_MEMORY_PROPERTY_HOST_VISIBLE_BIT1 set. Additionally, the object s backing memory may; be provided by the implementation lazily as specified in  khttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-device-lazy_allocationLazily Allocated Memory.5"VK_MEMORY_PROPERTY_HOST_CACHED_BIT bit specifies that memory allocated with this type is cached on the host. Host memory accesses to uncached memory are slower than to cached memory, however uncached memory is always host coherent.6$VK_MEMORY_PROPERTY_HOST_COHERENT_BIT9 bit specifies that the host cache management commands fD and fsm are not needed to flush host writes to the device or make device writes visible to the host, respectively.7#VK_MEMORY_PROPERTY_HOST_VISIBLE_BIT5 bit specifies that memory allocated with this type can" be mapped for host access using f.8#VK_MEMORY_PROPERTY_DEVICE_LOCAL_BIT bit specifies that memory allocated with this type is the most efficient for device access. This property will be set if and only if the memory type belongs to a heap with the VK_MEMORY_HEAP_DEVICE_LOCAL_BIT set.=&VK_INTERNAL_ALLOCATION_TYPE_EXECUTABLEF specifies that the allocation is intended for execution by the host.HVK_IMAGE_TYPE_3D% specifies a three-dimensional image.IVK_IMAGE_TYPE_2D# specifies a two-dimensional image.JVK_IMAGE_TYPE_1D# specifies a one-dimensional image.KVK_IMAGE_TILING_LINEARu specifies linear tiling (texels are laid out in memory in row-major order, possibly with some padding on each row).LVK_IMAGE_TILING_OPTIMAL} specifies optimal tiling (texels are laid out in an implementation-dependent arrangement, for more optimal memory access).p      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLpLKJIHGFEDCBA@?>=<;:9876543210/.-,+*)('&%$#"!      XYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~QRSTUVW      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOP0None "-KSTbejk:NVkExternalMemoryFeatureFlagsNV - Bitmask of VkExternalMemoryFeatureFlagBitsNV DescriptionVkExternalMemoryFeatureFlagsNV7 is a bitmask type for setting a mask of zero or more .See Also, TVkExternalMemoryHandleTypeFlagsNV - Bitmask of VkExternalMemoryHandleTypeFlagBitsNV Description!VkExternalMemoryHandleTypeFlagsNV7 is a bitmask type for setting a mask of zero or more .See Also1, , , 1 , h:, hc, ZVkExternalImageFormatPropertiesNV - Structure specifying external image format propertiesSee Also, , , imageFormatProperties$ will be filled in as when calling /, but the values returned may7 vary depending on the external handle type requested.externalMemoryFeatures is a bitmask of >, indicating properties of the external memory handle type (::externalHandleType?) being queried, or 0 if the external memory handle type is 0.exportFromImportedHandleTypes is a bitmask of ; containing a bit set for every external handle type that mayL be used to create memory from which the handles of the type specified in ::externalHandleType can; be exported, or 0 if the external memory handle type is 0.compatibleHandleTypes is a bitmask of ; containing a bit set for every external handle type that mayA be specified simultaneously with the handle type specified by ::externalHandleType when calling f1, or 0 if the external memory handle type is 0. compatibleHandleTypes will always contain ::externalHandleTypePVkExternalMemoryFeatureFlagBitsNV - Bitmask specifying external memory featuresSee Also, , WVkExternalMemoryHandleTypeFlagBitsNV - Bitmask specifying external memory handle typesSee AlsovkGetPhysicalDeviceExternalImageFormatPropertiesNV - determine image capabilities compatible with external memory handle types ParametersphysicalDeviceG is the physical device from which to query the image capabilitiesformat, is the image format, corresponding to *::format.type* is the image type, corresponding to *:: imageType.tiling, is the image tiling, corresponding to *::tiling.usage; is the intended usage of the image, corresponding to *::usage.flagsX is a bitmask describing additional parameters of the image, corresponding to *::flags.externalHandleType% is either one of the bits from , or 0.pExternalImageFormatProperties# points to an instance of the 3 structure in which capabilities are returned. DescriptionIf externalHandleType is 0, pExternalImageFormatPropertiesC::imageFormatProperties will return the same values as a call to /, and the other members of pExternalImageFormatPropertiesA will all be 0. Otherwise, they are filled in as described for .Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handleformat must be a valid  valuetype must be a valid  valuetiling must be a valid  valueusage must be a valid combination of  valuesusage must not be 0flags must be a valid combination of  valuesexternalHandleType must be a valid combination of  valuespExternalImageFormatProperties must be a valid pointer to a !VkExternalImageFormatPropertiesNV structure Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_FORMAT_NOT_SUPPORTEDSee Also, , , , , , , ,VK_EXTERNAL_MEMORY_FEATURE_IMPORTABLE_BIT_NVU specifies that the implementation supports importing handles of the specified type.,VK_EXTERNAL_MEMORY_FEATURE_EXPORTABLE_BIT_NVU specifies that the implementation supports exporting handles of the specified type.0VK_EXTERNAL_MEMORY_FEATURE_DEDICATED_ONLY_BIT_NV7 specifies that external memory of the specified type mustI be created as a dedicated allocation when used in the manner specified.5VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D11_IMAGE_KMT_BIT_NV+ specifies a handle to memory returned by  IDXGIResource::GetSharedHandle().1VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D11_IMAGE_BIT_NV4 specifies a valid NT handle to memory returned by $IDXGIResource1::CreateSharedHandle()3, or a handle duplicated from such a handle using DuplicateHandle().6VK_EXTERNAL_MEMORY_HANDLE_TYPE_OPAQUE_WIN32_KMT_BIT_NV, specifies a handle to memory returned by hc.2VK_EXTERNAL_MEMORY_HANDLE_TYPE_OPAQUE_WIN32_BIT_NV, specifies a handle to memory returned by hc., or one duplicated from such a handle using DuplicateHandle().1None"bejkPVkExportMemoryAllocateInfoNV - Specify memory handle types that may be exportedValid Usage (Implicit)sType must be 0VK_STRUCTURE_TYPE_EXPORT_MEMORY_ALLOCATE_INFO_NV handleTypes must be a valid combination of 0 valuesSee Also, sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure. handleTypes is a bitmask of 02 specifying one or more memory handle types that may% be exported. Multiple handle types mayW be requested for the same allocation as long as they are compatible, as reported by 0.[VkExternalMemoryImageCreateInfoNV - Specify that an image may be backed by external memoryValid Usage (Implicit)sType must be 6VK_STRUCTURE_TYPE_EXTERNAL_MEMORY_IMAGE_CREATE_INFO_NV handleTypes must be a valid combination of 0 valuesSee Also, sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure. handleTypes is a bitmask of 06 specifying one or more external memory handle types.2None"Kbejk  RVkSamplerReductionModeCreateInfoEXT - Structure specifying sampler reduction mode Description"If this structure is not present,  reductionMode is considered to be .VK_SAMPLER_REDUCTION_MODE_WEIGHTED_AVERAGE_EXT.Valid Usage (Implicit)sType must be 8VK_STRUCTURE_TYPE_SAMPLER_REDUCTION_MODE_CREATE_INFO_EXT reductionMode must be a valid  valueSee Also, sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure. reductionMode is an enum of type < that controls how texture filtering combines texel values.VkPhysicalDeviceSamplerFilterMinmaxPropertiesEXT - Structure describing sampler filter minmax limits that can be supported by an implementationMembersThe members of the 0VkPhysicalDeviceSamplerFilterMinmaxPropertiesEXTC structure describe the following implementation-dependent limits: Description"filterMinmaxSingleComponentFormatsm is a boolean value indicating whether a minimum set of required formats support min/max filtering.!filterMinmaxImageComponentMapping is a boolean value indicating whether the implementation supports non-identity component mapping of the image when doing min/max filtering.If the 0VkPhysicalDeviceSamplerFilterMinmaxPropertiesEXT structure is included in the pNext chain of sf9, it is filled with the implementation-dependent limits.If "filterMinmaxSingleComponentFormats is VK_TRUE, the following formats must support the 5VK_FORMAT_FEATURE_SAMPLED_IMAGE_FILTER_MINMAX_BIT_EXT feature with VK_IMAGE_TILING_OPTIMAL, if they support #VK_FORMAT_FEATURE_SAMPLED_IMAGE_BIT. VK_FORMAT_R8_UNORM VK_FORMAT_R8_SNORM VK_FORMAT_R16_UNORM VK_FORMAT_R16_SNORM VK_FORMAT_R16_SFLOAT VK_FORMAT_R32_SFLOAT VK_FORMAT_D16_UNORM VK_FORMAT_X8_D24_UNORM_PACK32 VK_FORMAT_D32_SFLOAT VK_FORMAT_D16_UNORM_S8_UINT VK_FORMAT_D24_UNORM_S8_UINT VK_FORMAT_D32_SFLOAT_S8_UINTIf the format is a depth/stencil format, this bit only specifies that the depth aspect (not the stencil aspect) of an image of this format supports min/max filtering, and that min/max filtering of the depth aspect is supported when depth compare is disabled in the sampler.If !filterMinmaxImageComponentMapping is VK_FALSEF the component mapping of the image view used with min/max filtering must have been created with the r component set to VK_COMPONENT_SWIZZLE_IDENTITY . Only the rd component of the sampled image value is defined and the other component values are undefined. If !filterMinmaxImageComponentMapping is VK_TRUEN this restriction does not apply and image component mapping works as normal.Valid Usage (Implicit)sType must be FVK_STRUCTURE_TYPE_PHYSICAL_DEVICE_SAMPLER_FILTER_MINMAX_PROPERTIES_EXTSee AlsoVkBool32, HVkSamplerReductionModeEXT - Specify reduction mode for texture filteringSee Also!VK_SAMPLER_REDUCTION_MODE_MAX_EXT specifies that texel values are combined by taking the component-wise maximum of values in the footprint with non-zero weights.!VK_SAMPLER_REDUCTION_MODE_MIN_EXT specifies that texel values are combined by taking the component-wise minimum of values in the footprint with non-zero weights..VK_SAMPLER_REDUCTION_MODE_WEIGHTED_AVERAGE_EXT specifies that texel values are combined by computing a weighted average of values in the footprint, using weights as specified in  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#textures-unnormalized-to-integerthe image operations chapter.          3None "-KSTbejk#;VkDebugReportFlagsEXT - Bitmask of VkDebugReportFlagBitsEXT DescriptionVkDebugReportFlagsEXT7 is a bitmask type for setting a mask of zero or more -.See Also$, -, 1$nVkDebugReportCallbackCreateInfoEXT - Structure specifying parameters of a newly created debug report callback Description For each VkDebugReportCallbackEXT that is created the "VkDebugReportCallbackCreateInfoEXT::flags determine when that "VkDebugReportCallbackCreateInfoEXT:: pfnCallback] is called. When an event happens, the implementation will do a bitwise AND of the event s - flags to each VkDebugReportCallbackEXT* object s flags. For each non-zero result the corresponding callback will be called. The callback will come directly from the component that detected the event, unless some other layer intercepts the calls for its own purposes (filter them in a different way, log to a system error log, etc.).An application may) receive multiple callbacks if multiple VkDebugReportCallbackEXTm objects were created. A callback will always be executed in the same thread as the originating Vulkan call.A callback may be called from multiple threads simultaneously (if the application is making Vulkan calls from multiple threads). Valid Usage pfnCallback must be a valid ,Valid Usage (Implicit)sType must be 7VK_STRUCTURE_TYPE_DEBUG_REPORT_CALLBACK_CREATE_INFO_EXTflags must be a valid combination of - valuesSee Also,, #, , 3&sType is the type of this structure.'pNext is NULL1 or a pointer to an extension-specific structure.(flags is a bitmask of -B specifying which event(s) will cause this callback to be called.) pfnCallback. is the application callback function to call.* pUserData+ is user data to be passed to the callback.+KVkDebugReportCallbackEXT - Opaque handle to a debug report callback objectSee Also3, 2Dummy data to tag the  with,RPFN_vkDebugReportCallbackEXT - Application-defined debug report callback function Parametersflags specifies the -# that triggered this callback. objectType is a /i value specifying the type of object being used or created at the time the event was triggered.object0 is the object where the issue was detected. If  objectType is 'VK_DEBUG_REPORT_OBJECT_TYPE_UNKNOWN_EXT, object is undefined.locationN is a component (layer, driver, loader) defined value that specifies the location of the trigger. This is an optional value. messageCodeL is a layer-defined value indicating what test triggered this callback. pLayerPrefixl is a null-terminated string that is an abbreviation of the name of the component making the callback.  pLayerPrefix5 is only valid for the duration of the callback.pMessageD is a null-terminated string detailing the trigger conditions. pMessage5 is only valid for the duration of the callback. pUserData& is the user data given when the + was created. Description The callback must not call vkDestroyDebugReportCallbackEXT.The callback returns a VkBool32E, which is interpreted in a layer-specified manner. The application should always return VK_FALSE. The VK_TRUE1 value is reserved for use in layer development.object must be a Vulkan object or VK_NULL_HANDLE. If  objectType is not 'VK_DEBUG_REPORT_OBJECT_TYPE_UNKNOWN_EXT and object is not VK_NULL_HANDLE, object must? be a Vulkan object of the corresponding type associated with  objectType as defined in  ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#debug-report-object-types.{html_spec_relative}#debug-report-object-types.See Also$-YVkDebugReportFlagBitsEXT - Bitmask specifying events which cause a debug report callbackSee Also#/AVkDebugReportObjectTypeEXT - Specify the type of an object handle Description' /% e Vulkan Handle Type " 'VK_DEBUG_REPORT_OBJECT_TYPE_UNKNOWN_EXT d Unknown/Undefined Handle  (VK_DEBUG_REPORT_OBJECT_TYPE_INSTANCE_EXT  ,  /VK_DEBUG_REPORT_OBJECT_TYPE_PHYSICAL_DEVICE_EXT  /&  &VK_DEBUG_REPORT_OBJECT_TYPE_DEVICE_EXT  /.  %VK_DEBUG_REPORT_OBJECT_TYPE_QUEUE_EXT  @>  )VK_DEBUG_REPORT_OBJECT_TYPE_SEMAPHORE_EXT  @:  .VK_DEBUG_REPORT_OBJECT_TYPE_COMMAND_BUFFER_EXT  @6  %VK_DEBUG_REPORT_OBJECT_TYPE_FENCE_EXT  @>  -VK_DEBUG_REPORT_OBJECT_TYPE_DEVICE_MEMORY_EXT  f6  &VK_DEBUG_REPORT_OBJECT_TYPE_BUFFER_EXT  j2  %VK_DEBUG_REPORT_OBJECT_TYPE_IMAGE_EXT  j3  %VK_DEBUG_REPORT_OBJECT_TYPE_EVENT_EXT  }>  *VK_DEBUG_REPORT_OBJECT_TYPE_QUERY_POOL_EXT  F:  +VK_DEBUG_REPORT_OBJECT_TYPE_BUFFER_VIEW_EXT  4  *VK_DEBUG_REPORT_OBJECT_TYPE_IMAGE_VIEW_EXT  w6  -VK_DEBUG_REPORT_OBJECT_TYPE_SHADER_MODULE_EXT  ?6  .VK_DEBUG_REPORT_OBJECT_TYPE_PIPELINE_CACHE_EXT  G.  /VK_DEBUG_REPORT_OBJECT_TYPE_PIPELINE_LAYOUT_EXT  H2  +VK_DEBUG_REPORT_OBJECT_TYPE_RENDER_PASS_EXT  H6  (VK_DEBUG_REPORT_OBJECT_TYPE_PIPELINE_EXT  H8  5VK_DEBUG_REPORT_OBJECT_TYPE_DESCRIPTOR_SET_LAYOUT_EXT  b'  'VK_DEBUG_REPORT_OBJECT_TYPE_SAMPLER_EXT  _:  /VK_DEBUG_REPORT_OBJECT_TYPE_DESCRIPTOR_POOL_EXT  -  .VK_DEBUG_REPORT_OBJECT_TYPE_DESCRIPTOR_SET_EXT  .  +VK_DEBUG_REPORT_OBJECT_TYPE_FRAMEBUFFER_EXT  9  ,VK_DEBUG_REPORT_OBJECT_TYPE_COMMAND_POOL_EXT  2  +VK_DEBUG_REPORT_OBJECT_TYPE_SURFACE_KHR_EXT  K,  -VK_DEBUG_REPORT_OBJECT_TYPE_SWAPCHAIN_KHR_EXT  (  9VK_DEBUG_REPORT_OBJECT_TYPE_DEBUG_REPORT_CALLBACK_EXT_EXT  +J  +VK_DEBUG_REPORT_OBJECT_TYPE_DISPLAY_KHR_EXT  X,  0VK_DEBUG_REPORT_OBJECT_TYPE_DISPLAY_MODE_KHR_EXT  X(  0VK_DEBUG_REPORT_OBJECT_TYPE_OBJECT_TABLE_NVX_EXT    <VK_DEBUG_REPORT_OBJECT_TYPE_INDIRECT_COMMANDS_LAYOUT_NVX_EXT    >VK_DEBUG_REPORT_OBJECT_TYPE_DESCRIPTOR_UPDATE_TEMPLATE_KHR_EXT   9VkDebugReportObjectTypeEXT and Vulkan Handle RelationshipNoteThe primary expected use of VK_ERROR_VALIDATION_FAILED_EXT is for validation layer testing. It is not expected that an application would see this error code during normal use of the validation layers.See AlsoD, D, 11>vkDebugReportMessageEXT - Inject a message into a debug stream Parametersinstance is the debug stream s  VkInstance.flags specifies the -+ classification of this event/message. objectType is a /^ specifying the type of object being used or created at the time the event was triggered.object2 this is the object where the issue was detected. object can be VK_NULL_HANDLE6 if there is no object associated with the event.location! is an application defined value. messageCode! is an application defined value. pLayerPrefixE is the abbreviation of the component making this event/message.pMessageC is a null-terminated string detailing the trigger conditions. DescriptionThe call will propagate through the layers and generate callback(s) as indicated by the message s flags. The parameters are passed on to the callback in addition to the  pUserDataA value that was defined at the time the callback was registered. Valid Usageobject must be a Vulkan object or VK_NULL_HANDLEIf  objectType is not 'VK_DEBUG_REPORT_OBJECT_TYPE_UNKNOWN_EXT and object is not VK_NULL_HANDLE, object mustC be a Vulkan object of the corresponding type associated with  objectType as defined in  ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#debug-report-object-types.{html_spec_relative}#debug-report-object-types.Valid Usage (Implicit)instance must be a valid  VkInstance handleflags must be a valid combination of - valuesflags must not be 0 objectType must be a valid / value pLayerPrefix must" be a null-terminated UTF-8 stringpMessage must" be a null-terminated UTF-8 stringSee Also#, /, 2HvkDestroyDebugReportCallbackEXT - Destroy a debug report callback object Parametersinstance- the instance where the callback was created.callback the VkDebugReportCallbackEXT object to destroy. callback* is an externally synchronized object and mustJ not be used on more than one thread at a time. This means that vkDestroyDebugReportCallbackEXT must. not be called when a callback is active. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. Valid UsageIf VkAllocationCallbacks were provided when callback1 was created, a compatible set of callbacks must be provided hereIf no VkAllocationCallbacks were provided when callback was created,  pAllocator must be NULLValid Usage (Implicit)instance must be a valid  VkInstance handlecallback must be a valid VkDebugReportCallbackEXT handleIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structurecallback must6 have been created, allocated, or retrieved from instanceHost SynchronizationHost access to callback must be externally synchronizedSee Also, +, 3FvkCreateDebugReportCallbackEXT - Create a debug report callback object Parametersinstance- the instance the callback will be logged on. pCreateInfo points to a $[ structure which defines the conditions under which this callback will be called. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. pCallback is a pointer to record the VkDebugReportCallbackEXT object created.Valid Usage (Implicit)instance must be a valid  VkInstance handle pCreateInfo must$ be a valid pointer to a valid "VkDebugReportCallbackCreateInfoEXT structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structure pCallback must be a valid pointer to a VkDebugReportCallbackEXT handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORYSee Also, $, +, =VK_DEBUG_REPORT_DEBUG_BIT_EXTF specifies diagnostic information from the implementation and layers.>VK_DEBUG_REPORT_ERROR_BIT_EXT[ specifies that an error that may cause undefined results, including an application crash.?+VK_DEBUG_REPORT_PERFORMANCE_WARNING_BIT_EXTA specifies a potentially non-optimal use of Vulkan, e.g. using  when setting ::loadOp to VK_ATTACHMENT_LOAD_OP_CLEAR would have worked.@VK_DEBUG_REPORT_WARNING_BIT_EXT specifies use of Vulkan that may expose an app bug. Such cases may not be immediately harmful, such as a fragment shader outputting to a location with no attachment. Other cases may point to behavior that is almost certainly bad when unintended such as using an image whose memory has not been filled. In general if you see a warning but you know that the behavior is intended/desired, then simply ignore the warning.A#VK_DEBUG_REPORT_INFORMATION_BIT_EXTo specifies an informational message such as resource details that may be handy when debugging an application.A#$%&'(*)+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcA/0cba`_^]\[ZYXWVUTSRQPONMLKJIHGFEDCB-.A@?>=<;:987654,+321$%&'(*)#4None "-KSTbejkskVkShaderModuleValidationCacheCreateInfoEXT - Specify validation cache to use during shader module creationValid Usage (Implicit)sType must be @VK_STRUCTURE_TYPE_SHADER_MODULE_VALIDATION_CACHE_CREATE_INFO_EXTvalidationCache must be a valid VkValidationCacheEXT handleSee Also, usType is the type of this structure.vpNext is NULL1 or a pointer to an extension-specific structure.wvalidationCache is the validation cache object from which the results of prior validation attempts will be written, and to which new validation results for this VkShaderModule will be written (if not already present).xeVkValidationCacheCreateInfoEXT - Structure specifying parameters of a newly created validation cache Valid UsageIf initialDataSize is not 0, it must be equal to the size of  pInitialData, as returned by vkGetValidationCacheDataEXT when  pInitialData was originally retrievedIf initialDataSize is not 0,  pInitialData must2 have been retrieved from a previous call to vkGetValidationCacheDataEXTValid Usage (Implicit)sType must be 2VK_STRUCTURE_TYPE_VALIDATION_CACHE_CREATE_INFO_EXTpNext must be NULLflags must be 0If initialDataSize is not 0,  pInitialData must( be a valid pointer to an array of initialDataSize bytesSee Also, , zsType is the type of this structure.{pNext is NULL1 or a pointer to an extension-specific structure.|flags is reserved for future use.}initialDataSize is the number of bytes in  pInitialData. If initialDataSize7 is zero, the validation cache will initially be empty.~ pInitialData is a pointer to previously retrieved validation cache data. If the validation cache data is incompatible (as defined below) with the device, the validation cache will be initially empty. If initialDataSize is zero,  pInitialData is ignored.AVkValidationCacheEXT - Opaque handle to a validation cache objectSee Alsos, , , , Dummy data to tag the  with9VkValidationCacheCreateFlagsEXT - Reserved for future use DescriptionVkValidationCacheCreateFlagsEXTQ is a bitmask type for setting a mask, but is currently reserved for future use.See AlsoxCVkValidationCacheHeaderVersionEXT - Encode validation cache versionSee Also$UNKNOWN:vkCreateValdiationCacheEXT, JvkMergeValidationCachesEXT - Combine the data stores of validation caches ParametersdeviceC is the logical device that owns the validation cache objects.dstCacheB is the handle of the validation cache to merge results into. srcCacheCount is the length of the  pSrcCaches array. pSrcCachesI is an array of validation cache handles, which will be merged into dstCache. The previous contents of dstCache# are included after the merge. DescriptionNoteVThe details of the merge operation are implementation dependent, but implementations shouldT merge the contents of the specified validation caches and prune duplicate entries. Valid UsagedstCache must( not appear in the list of source cachesValid Usage (Implicit)device must be a valid VkDevice handledstCache must be a valid VkValidationCacheEXT handle pSrcCaches must( be a valid pointer to an array of  srcCacheCount valid VkValidationCacheEXT handles srcCacheCount must be greater than 0dstCache must6 have been created, allocated, or retrieved from deviceEach element of  pSrcCaches must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to dstCache must be externally synchronized Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, HvkGetValidationCacheDataEXT - Get the data store from a validation cache Parametersdevice6 is the logical device that owns the validation cache.validationCache/ is the validation cache to retrieve data from. pDataSizeh is a pointer to a value related to the amount of data in the validation cache, as described below.pData is either NULL or a pointer to a buffer. DescriptionIf pData is NULL), then the maximum size of the data that canD be retrieved from the validation cache, in bytes, is returned in  pDataSize . Otherwise,  pDataSize mustY point to a variable set by the user to the size of the buffer, in bytes, pointed to by pDataZ, and on return the variable is overwritten with the amount of data actually written to pData.If  pDataSize$ is less than the maximum size that can0 be retrieved by the validation cache, at most  pDataSize bytes will be written to pData, and vkGetValidationCacheDataEXT will return  VK_INCOMPLETE. Any data written to pData is valid and can be provided as the  pInitialData member of the VkValidationCacheCreateInfoEXT structure passed to vkCreateValidationCacheEXT. Two calls to vkGetValidationCacheDataEXT with the same parameters musti retrieve the same data unless a command that modifies the contents of the cache is called between them. Applications can store the data retrieved from the validation cache, and use these data, possibly in a future run of the application, to populate new validation cache objects. The results of validation, however, may depend on the vendor ID, device ID, driver version, and other details of the device. To enable applications to detect when previously retrieved data is incompatible with the device, the initial bytes written to pData must2 be a header consisting of the following members: Offset  Size 2 Meaning  0 2 4  length in bytes of the entire validation cache header written as a stream of bytes, with the least significant byte first  4 2 4  a r value written as a stream of bytes, with the least significant byte first # 8   VK_UUID_SIZE4  a layer commit ID expressed as a UUID, which uniquely identifies the version of the validation layers used to generate these validation results ,Layout for validation cache header version *VK_VALIDATION_CACHE_HEADER_VERSION_ONE_EXTThe first four bytes encode the length of the entire validation cache header, in bytes. This value includes all fields in the header including the validation cache version field and the size of the length field.KThe next four bytes encode the validation cache version, as described for &. A consumer of the validation cache shouldG use the cache version to interpret the remainder of the cache header.If  pDataSizeR is less than what is necessary to store this header, nothing will be written to pData and zero will be written to  pDataSize.Valid Usage (Implicit)device must be a valid VkDevice handlevalidationCache must be a valid VkValidationCacheEXT handle pDataSize must be a valid pointer to a size_t valueIf the value referenced by  pDataSize is not 0, and pData is not NULL, pData must( be a valid pointer to an array of  pDataSize bytesvalidationCache must6 have been created, allocated, or retrieved from device Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS  VK_INCOMPLETE ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, ?vkDestroyValidationCacheEXT - Destroy a validation cache object ParametersdeviceF is the logical device that destroys the validation cache object.validationCache2 is the handle of the validation cache to destroy. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. Valid UsageIf VkAllocationCallbacks were provided when validationCache1 was created, a compatible set of callbacks must be provided hereIf no VkAllocationCallbacks were provided when validationCache was created,  pAllocator must be NULLValid Usage (Implicit)device must be a valid VkDevice handleIf validationCache is not , validationCache must be a valid VkValidationCacheEXT handleIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structureIf validationCache is a valid handle, it must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to validationCache must be externally synchronizedSee Also, , ;vkCreateValidationCacheEXT - Creates a new validation cache ParametersdeviceE is the logical device that creates the validation cache object. pCreateInfo is a pointer to a VkValidationCacheCreateInfoEXTZ structure that contains the initial parameters for the validation cache object. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter.pValidationCache is a pointer to a VkValidationCacheEXTH handle in which the resulting validation cache object is returned. DescriptionNote Applications canU track and manage the total host memory size of a validation cache object using the  pAllocator. Applications canH limit the amount of data retrieved from a validation cache object in vkGetValidationCacheDataEXT. Implementations shouldy not internally limit the total number of entries added to a validation cache object or the total host memory consumed.!Once created, a validation cache can be passed to the vkCreateShaderModule command as part of the VkShaderModuleCreateInfo pNext chain. If a *VkShaderModuleValidationCacheCreateInfoEXT object is part of the VkShaderModuleCreateInfo::pNext chain, and its validationCache field is not , the implementation will query it for possible reuse opportunities and update it with new content. The use of the validation cache object in these commands is internally synchronized, and the same validation cache object can- be used in multiple threads simultaneously.NoteImplementations should make every effort to limit any critical sections to the actual accesses to the cache, which is expected to be significantly shorter than the duration of the vkCreateShaderModule command.Valid Usage (Implicit)device must be a valid VkDevice handle pCreateInfo must$ be a valid pointer to a valid VkValidationCacheCreateInfoEXT structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structurepValidationCache must be a valid pointer to a VkValidationCacheEXT handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORYSee Also, , x, *VK_VALIDATION_CACHE_HEADER_VERSION_ONE_EXT0 specifies version one of the validation cache.stuvwxyz{|}~xyz{|}~stuvw5None "-KSTbejkSVkExternalSemaphoreFeatureFlags - Bitmask of VkExternalSemaphoreFeatureFlagBitsKHR DescriptionVkExternalSemaphoreFeatureFlags7 is a bitmask type for setting a mask of zero or more .See Also, VVkExternalSemaphoreHandleTypeFlags - Bitmask of VkExternalSemaphoreHandleTypeFlagBits Description"VkExternalSemaphoreHandleTypeFlags7 is a bitmask type for setting a mask of zero or more .See Also7, , bVkExternalSemaphoreProperties - Structure describing supported external semaphore handle features DescriptionIf  handleType/ is not supported by the implementation, then ::externalSemaphoreFeatures will be set to zero.Valid Usage (Implicit)sType must be /VK_STRUCTURE_TYPE_EXTERNAL_SEMAPHORE_PROPERTIESpNext must be NULLSee Also, , , , 6exportFromImportedHandleTypes is a bitmask of , specifying which types of imported handle  handleType can be exported from.compatibleHandleTypes is a bitmask of  specifying handle types which can" be specified at the same time as  handleType when creating a semaphore.externalSemaphoreFeatures is a bitmask of  describing the features of  handleType.\VkPhysicalDeviceExternalSemaphoreInfo - Structure specifying semaphore creation parameters.Valid Usage (Implicit)sType must be 9VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_EXTERNAL_SEMAPHORE_INFOpNext must be NULL handleType must be a valid  valueSee Also, , , 6sType is the type of this structurepNext9 is NULL or a pointer to an extension-specific structure. handleType is a _ value specifying the external semaphore handle type for which capabilities will be returned.gVkExternalSemaphoreFeatureFlagBits - Bitfield describing features of an external semaphore handle typeSee AlsoYVkExternalSemaphoreHandleTypeFlagBits - Bitmask of valid external semaphore handle types Description/VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_OPAQUE_FD_BIT specifies a POSIX file descriptor handle that has only limited valid usage outside of Vulkan and other compatible APIs. It must0 be compatible with the POSIX system calls dup, dup2, close(, and the non-standard system call dup3. Additionally, it must. be transportable over a socket using an  SCM_RIGHTS control message. It owns a reference to the underlying synchronization primitive represented by its Vulkan semaphore object.2VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_OPAQUE_WIN32_BITt specifies an NT handle that has only limited valid usage outside of Vulkan and other compatible APIs. It must' be compatible with the functions DuplicateHandle,  CloseHandle, CompareObjectHandles, GetHandleInformation, and SetHandleInformationw. It owns a reference to the underlying synchronization primitive represented by its Vulkan semaphore object.6VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_OPAQUE_WIN32_KMT_BIT specifies a global share handle that has only limited valid usage outside of Vulkan and other compatible APIs. It is not compatible with any native APIs. It does not own a reference to the underlying synchronization primitive represented its Vulkan semaphore object, and will therefore become invalid when all Vulkan semaphore objects associated with it are destroyed.1VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_D3D12_FENCE_BIT) specifies an NT handle returned by  ID3D12Device::CreateSharedHandle referring to a Direct3D 12 fence. It owns a reference to the underlying synchronization primitive associated with the Direct3D fence.-VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_SYNC_FD_BITa specifies a POSIX file descriptor handle to a Linux Sync File or Android Fence object. It can be used with any native API accepting a valid sync file or fence as input. It owns a reference to the underlying synchronization primitive associated with the file descriptor. Implementations which support importing this handle type mustb accept any type of sync or fence FD supported by the native system they are running on.NoteHandles of type -VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_SYNC_FD_BIT generated by the implementation may represent either Linux Sync Files or Android Fences at the implementation s discretion. Applications should only use operations defined for both types of file descriptors, unless they know via means external to Vulkan the type of the file descriptor, or are prepared to deal with the system-defined operation failures resulting from using the wrong type.Some external semaphore handle types can only be shared within the same underlying physical device and/or the same driver version, as defined in the following table:: Handle type  VkPhysicalDeviceIDProperties:: driverUUID  VkPhysicalDeviceIDProperties:: deviceUUID  /VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_OPAQUE_FD_BIT . Must match . Must match  2VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_OPAQUE_WIN32_BIT . Must match . Must match  6VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_OPAQUE_WIN32_KMT_BIT . Must match . Must match  1VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_D3D12_FENCE_BIT . Must match . Must match  -VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_SYNC_FD_BIT . No restriction . No restriction -External semaphore handle types compatibilitySee Also, A;, <, , A, ovkGetPhysicalDeviceExternalSemaphoreProperties - Function for querying external semaphore handle capabilities. ParametersphysicalDeviceL is the physical device from which to query the semaphore capabilities.pExternalSemaphoreInfo# points to an instance of the J structure, describing the parameters that would be consumed by E .pExternalSemaphoreProperties# points to an instance of the 3 structure in which capabilities are returned.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handlepExternalSemaphoreInfo must$ be a valid pointer to a valid %VkPhysicalDeviceExternalSemaphoreInfo structurepExternalSemaphoreProperties must be a valid pointer to a VkExternalSemaphoreProperties structureSee Also, , ,VK_EXTERNAL_SEMAPHORE_FEATURE_IMPORTABLE_BIT& specifies that handles of this type can) be imported as Vulkan semaphore objects.,VK_EXTERNAL_SEMAPHORE_FEATURE_EXPORTABLE_BIT& specifies that handles of this type can+ be exported from Vulkan semaphore objects.6None-STejkO7None"Kbejk+2=VkSemaphoreImportFlags - Bitmask of VkSemaphoreImportFlagBits DescriptionVkSemaphoreImportFlags7 is a bitmask type for setting a mask of zero or more .See AlsoA;, <, fVkExportSemaphoreCreateInfo - Structure specifying handle types that can be exported from a semaphore Valid Usage The bits in  handleTypes must7 be supported and compatible, as reported by 5!.Valid Usage (Implicit)sType must be .VK_STRUCTURE_TYPE_EXPORT_SEMAPHORE_CREATE_INFO handleTypes must be a valid combination of 5 valuesSee Also, sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure. handleTypes is a bitmask of 5@ specifying one or more semaphore handle types the application can7 export from the resulting semaphore. The application can7 request multiple handle types for the same semaphore.aVkSemaphoreImportFlagBits - Bitmask specifying additional parameters of semaphore payload import Description'These bits have the following meanings:!VK_SEMAPHORE_IMPORT_TEMPORARY_BITc specifies that the semaphore payload will be imported only temporarily, as described in  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-semaphores-importing!Importing Semaphore Payloads', regardless of the permanence of  handleType.See Also  8None-STejk+9None "-KSTbejkrGVkExternalFenceFeatureFlags - Bitmask of VkExternalFenceFeatureFlagBits DescriptionVkExternalFenceFeatureFlags7 is a bitmask type for setting a mask of zero or more .See Also, NVkExternalFenceHandleTypeFlags - Bitmask of VkExternalFenceHandleTypeFlagBits DescriptionVkExternalFenceHandleTypeFlags7 is a bitmask type for setting a mask of zero or more .See Also;, , ZVkExternalFenceProperties - Structure describing supported external fence handle features DescriptionIf  handleType/ is not supported by the implementation, then ::externalFenceFeatures will be set to zero.Valid Usage (Implicit)sType must be +VK_STRUCTURE_TYPE_EXTERNAL_FENCE_PROPERTIESpNext must be NULLSee Also, , , , :exportFromImportedHandleTypes is a bitmask of , indicating which types of imported handle  handleType can be exported from.compatibleHandleTypes is a bitmask of  specifying handle types which can# be specified at the same time as  handleType when creating a fence. externalFenceFeatures is a bitmask of  indicating the features of  handleType. TVkPhysicalDeviceExternalFenceInfo - Structure specifying fence creation parameters. DescriptionNoteHandles of type )VK_EXTERNAL_FENCE_HANDLE_TYPE_SYNC_FD_BIT generated by the implementation may represent either Linux Sync Files or Android Fences at the implementation s discretion. Applications should only use operations defined for both types of file descriptors, unless they know via means external to Vulkan the type of the file descriptor, or are prepared to deal with the system-defined operation failures resulting from using the wrong type.Valid Usage (Implicit)sType must be 5VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_EXTERNAL_FENCE_INFOpNext must be NULL handleType must be a valid  valueSee Also, , , : sType is the type of this structure pNext9 is NULL or a pointer to an extension-specific structure. handleType is a Y value indicating an external fence handle type for which capabilities will be returned._VkExternalFenceFeatureFlagBits - Bitfield describing features of an external fence handle typeSee AlsoQVkExternalFenceHandleTypeFlagBits - Bitmask of valid external fence handle types Description+VK_EXTERNAL_FENCE_HANDLE_TYPE_OPAQUE_FD_BIT specifies a POSIX file descriptor handle that has only limited valid usage outside of Vulkan and other compatible APIs. It must0 be compatible with the POSIX system calls dup, dup2, close(, and the non-standard system call dup3. Additionally, it must. be transportable over a socket using an  SCM_RIGHTS control message. It owns a reference to the underlying synchronization primitive represented by its Vulkan fence object..VK_EXTERNAL_FENCE_HANDLE_TYPE_OPAQUE_WIN32_BITt specifies an NT handle that has only limited valid usage outside of Vulkan and other compatible APIs. It must' be compatible with the functions DuplicateHandle,  CloseHandle, CompareObjectHandles, GetHandleInformation, and SetHandleInformations. It owns a reference to the underlying synchronization primitive represented by its Vulkan fence object.2VK_EXTERNAL_FENCE_HANDLE_TYPE_OPAQUE_WIN32_KMT_BIT specifies a global share handle that has only limited valid usage outside of Vulkan and other compatible APIs. It is not compatible with any native APIs. It does not own a reference to the underlying synchronization primitive represented by its Vulkan fence object, and will therefore become invalid when all Vulkan fence objects associated with it are destroyed.)VK_EXTERNAL_FENCE_HANDLE_TYPE_SYNC_FD_BITZ specifies a POSIX file descriptor handle to a Linux Sync File or Android Fence. It can be used with any native API accepting a valid sync file or fence as input. It owns a reference to the underlying synchronization primitive associated with the file descriptor. Implementations which support importing this handle type must] accept any type of sync or fence FD supported by the native system they are running on.Some external fence handle types can only be shared within the same underlying physical device and/or the same driver version, as defined in the following table:6 Handle type  VkPhysicalDeviceIDProperties:: driverUUID  VkPhysicalDeviceIDProperties:: deviceUUID  +VK_EXTERNAL_FENCE_HANDLE_TYPE_OPAQUE_FD_BIT . Must match . Must match  .VK_EXTERNAL_FENCE_HANDLE_TYPE_OPAQUE_WIN32_BIT . Must match . Must match  2VK_EXTERNAL_FENCE_HANDLE_TYPE_OPAQUE_WIN32_KMT_BIT . Must match . Must match  )VK_EXTERNAL_FENCE_HANDLE_TYPE_SYNC_FD_BIT . No restriction . No restriction )External fence handle types compatibilitySee Also, B#, $, B5, 6,  gvkGetPhysicalDeviceExternalFenceProperties - Function for querying external fence handle capabilities. ParametersphysicalDeviceH is the physical device from which to query the fence capabilities.pExternalFenceInfo# points to an instance of the  J structure, describing the parameters that would be consumed by z.pExternalFenceProperties# points to an instance of the 3 structure in which capabilities are returned.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handlepExternalFenceInfo must$ be a valid pointer to a valid !VkPhysicalDeviceExternalFenceInfo structurepExternalFenceProperties must be a valid pointer to a VkExternalFenceProperties structureSee Also, ,  (VK_EXTERNAL_FENCE_FEATURE_IMPORTABLE_BIT! specifies handles of this type can% be imported to Vulkan fence objects.(VK_EXTERNAL_FENCE_FEATURE_EXPORTABLE_BIT! specifies handles of this type can' be exported from Vulkan fence objects.          :None-STejk0123456789:;<=>?@ABA@B54321?0>=<;:9876;None"KbejkC5VkFenceImportFlags - Bitmask of VkFenceImportFlagBits DescriptionVkFenceImportFlags7 is a bitmask type for setting a mask of zero or more I.See AlsoI, B5, 6D^VkExportFenceCreateInfo - Structure specifying handle types that can be exported from a fence Valid Usage The bits in  handleTypes< must be supported and compatible, as reported by 9.Valid Usage (Implicit)sType must be *VK_STRUCTURE_TYPE_EXPORT_FENCE_CREATE_INFO handleTypes must be a valid combination of 9 valuesSee Also, FsType is the type of this structure.GpNext is NULL1 or a pointer to an extension-specific structure.H handleTypes is a bitmask of 9< specifying one or more fence handle types the application can3 export from the resulting fence. The application can3 request multiple handle types for the same fence.IYVkFenceImportFlagBits - Bitmask specifying additional parameters of fence payload importSee AlsoCLVK_FENCE_IMPORT_TEMPORARY_BITV specifies that the fence payload will be imported only temporarily, as described in  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-fences-importingImporting Fence Payloads#, regardless of the permanence of  handleType. CDEFGHIJKL IJLKDEFGHC<None-STejkPWXYZ[\]^^]YXW\[Z=None "-STbejk _WVkDeviceGroupDeviceCreateInfo - Create a logical device from multiple physical devices DescriptionThe elements of the pPhysicalDevices^ array are an ordered list of the physical devices that the logical device represents. These must be a subset of a single device group, and need not be in the same order as they were enumerated. The order of the physical devices in the pPhysicalDevices array determines the  device index of each physical device, with element i being assigned a device index of i. Certain commands and structures refer to one or more physical devices by using device indices or  device masks formed using device indices.'A logical device created without using VkDeviceGroupDeviceCreateInfo , or with physicalDeviceCount$ equal to zero, is equivalent to a physicalDeviceCount of one and pPhysicalDevices pointing to the physicalDevice parameter to ~C. In particular, the device index of that physical device is zero. Valid UsageEach element of pPhysicalDevices must be uniqueAll elements of pPhysicalDevices must3 be in the same device group as enumerated by mIf physicalDeviceCount is not 0, the physicalDevice parameter of ~ must be an element of pPhysicalDevices.Valid Usage (Implicit)sType must be 1VK_STRUCTURE_TYPE_DEVICE_GROUP_DEVICE_CREATE_INFOIf physicalDeviceCount is not 0, pPhysicalDevices must( be a valid pointer to an array of physicalDeviceCount valid VkPhysicalDevice handlesSee Also, asType is the type of this structure.bpNext is NULL1 or a pointer to an extension-specific structure.cphysicalDeviceCount# is the number of elements in the pPhysicalDevices array.dpPhysicalDevicesL is an array of physical device handles belonging to the same device group.eXVkPhysicalDeviceGroupProperties - Structure specifying physical device group propertiesSee AlsoVkBool32, , , m, >gsType is the type of this structure.hpNext is NULL1 or a pointer to an extension-specific structure.iphysicalDeviceCount0 is the number of physical devices in the group.jphysicalDevicesc is an array of physical device handles representing all physical devices in the group. The first physicalDeviceCount& elements of the array will be valid.ksubsetAllocation} specifies whether logical devices created from the group support allocating device memory on a subset of devices, via the  deviceMask member of the A. If this is VK_FALSE\, then all device memory allocations are made across all physical devices in the group. If physicalDeviceCount is 1, then subsetAllocation must be VK_FALSE.m{vkEnumeratePhysicalDeviceGroups - Enumerates groups of physical devices that can be used to create a single logical device Parametersinstance? is a handle to a Vulkan instance previously created with /.pPhysicalDeviceGroupCountv is a pointer to an integer related to the number of device groups available or queried, as described below.pPhysicalDeviceGroupProperties is either NULL" or a pointer to an array of e structures. DescriptionIf pPhysicalDeviceGroupProperties is NULL=, then the number of device groups available is returned in pPhysicalDeviceGroupCount. Otherwise, pPhysicalDeviceGroupCount mustG point to a variable set by the user to the number of elements in the pPhysicalDeviceGroupPropertiesf array, and on return the variable is overwritten with the number of structures actually written to pPhysicalDeviceGroupProperties. If pPhysicalDeviceGroupCount> is less than the number of device groups available, at most pPhysicalDeviceGroupCount! structures will be written. If pPhysicalDeviceGroupCount9 is smaller than the number of device groups available,  VK_INCOMPLETE will be returned instead of  VK_SUCCESSF, to indicate that not all the available device groups were returned.Every physical device must be in exactly one device group.Valid Usage (Implicit)instance must be a valid  VkInstance handlepPhysicalDeviceGroupCount must be a valid pointer to a uint32_t valueIf the value referenced by pPhysicalDeviceGroupCount is not 0 , and pPhysicalDeviceGroupProperties is not NULL, pPhysicalDeviceGroupProperties must( be a valid pointer to an array of pPhysicalDeviceGroupCount VkPhysicalDeviceGroupProperties structures Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS  VK_INCOMPLETE ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_INITIALIZATION_FAILEDSee Also, eo!VK_MEMORY_HEAP_MULTI_INSTANCE_BIT specifies that in a logical device representing more than one physical device, there is a per-physical device instance of the heap memory. By default, an allocation from such a heap will be replicated to each physical device s instance of the heap._`abcdefghijklmnopqqpolnmefghijk_`abcd>None-STejk xyz{|}~ zy~x}|{?None "-KSTbejkS \VkShaderModuleCreateInfo - Structure specifying parameters of a newly created shader module Valid UsagecodeSize must be greater than 0If pCode points to SPIR-V code, codeSize must be a multiple of 4pCode mustR point to either valid SPIR-V code, formatted and packed as described by the  Xhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#spirv-spec!Khronos SPIR-V Specification or valid GLSL code which mustB be written to the GL_KHR_vulkan_glsl extension specificationIf pCode" points to SPIR-V code, that code must6 adhere to the validation rules described by the  hhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#spirvenv-module-validation%Validation Rules within a Module section of the  chttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#spirvenv-capabilitiesSPIR-V Environment appendixIf pCode points to GLSL code, it mustW be valid GLSL code written to the GL_KHR_vulkan_glsl GLSL extension specificationpCode must declare the Shader capability for SPIR-V codepCode must\ not declare any capability that is not supported by the API, as described by the  hhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#spirvenv-module-validation Capabilities section of the  chttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#spirvenv-capabilitiesSPIR-V Environment appendixIf pCode, declares any of the capabilities listed as optional in the  ihttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#spirvenv-capabilities-tableSPIR-V Environment- appendix, the corresponding feature(s) must be enabled.Valid Usage (Implicit)sType must be +VK_STRUCTURE_TYPE_SHADER_MODULE_CREATE_INFOpNext must be NULL* or a pointer to a valid instance of 4flags must be 0pCode must( be a valid pointer to an array of codeSize \over 4 uint32_t valuesSee Also, , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.flags is reserved for future use.codeSize2 is the size, in bytes, of the code pointed to by pCode.pCode points to code that is used to create the shader module. The type and format of the code is determined from the content of the memory addressed by pCode.8VkShaderModule - Opaque handle to a shader module objectSee AlsoH, ,  Dummy data to tag the  with3VkShaderModuleCreateFlags - Reserved for future use DescriptionVkShaderModuleCreateFlagsQ is a bitmask type for setting a mask, but is currently reserved for future use.See Also6vkDestroyShaderModule - Destroy a shader module module Parametersdevice7 is the logical device that destroys the shader module. shaderModule/ is the handle of the shader module to destroy. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. DescriptionA shader module canJ be destroyed while pipelines created using its shaders are still in use. Valid UsageIf VkAllocationCallbacks were provided when  shaderModule1 was created, a compatible set of callbacks must be provided hereIf no VkAllocationCallbacks were provided when  shaderModule was created,  pAllocator must be NULLValid Usage (Implicit)device must be a valid VkDevice handleIf  shaderModule is not ,  shaderModule must be a valid VkShaderModule handleIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structureIf  shaderModule is a valid handle, it must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to  shaderModule must be externally synchronizedSee Also, , 9vkCreateShaderModule - Creates a new shader module object Parametersdevice6 is the logical device that creates the shader module. pCreateInfo3 parameter is a pointer to an instance of the VkShaderModuleCreateInfo structure. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. pShaderModule points to a VkShaderModuleE handle in which the resulting shader module object is returned. DescriptionEOnce a shader module has been created, any entry points it contains can3 be used in pipeline shader stages as described in  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#pipelines-computeCompute Pipelines and  `https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#pipelines-graphicsGraphics Pipelines.%If the shader stage fails to compile VK_ERROR_INVALID_SHADER_NVU will be generated and the compile log will be reported back to the application by ({html_spec_relative}#VK_EXT_debug_report if enabled.Valid Usage (Implicit)device must be a valid VkDevice handle pCreateInfo must$ be a valid pointer to a valid VkShaderModuleCreateInfo structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structure pShaderModule must be a valid pointer to a VkShaderModule handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_INVALID_SHADER_NVSee Also, , ,   @None "-KSTbejkР9VkPipelineStageFlags - Bitmask of VkPipelineStageFlagBits DescriptionVkPipelineStageFlags7 is a bitmask type for setting a mask of zero or more .See Also, , , , , , <VkSubmitInfo - Structure specifying a queue submit operation Description)The order that command buffers appear in pCommandBuffers is used to determine  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-submission-ordersubmission order, and thus all the  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-implicitimplicit ordering guaranteesJ that respect it. Other than these implicit ordering guarantees and any  ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization$explicit synchronization primitives, these command buffers may+ overlap or otherwise execute out of order. Valid UsageEach element of pCommandBuffers must# not have been allocated with !VK_COMMAND_BUFFER_LEVEL_SECONDARYIf the  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-geometryShadergeometry shaders. feature is not enabled, each element of pWaitDstStageMask must not contain %VK_PIPELINE_STAGE_GEOMETRY_SHADER_BITIf the  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-tessellationShadertessellation shaders. feature is not enabled, each element of pWaitDstStageMask must not contain 1VK_PIPELINE_STAGE_TESSELLATION_CONTROL_SHADER_BIT or 4VK_PIPELINE_STAGE_TESSELLATION_EVALUATION_SHADER_BITEach element of pWaitDstStageMask must not include VK_PIPELINE_STAGE_HOST_BIT.Valid Usage (Implicit)sType must be VK_STRUCTURE_TYPE_SUBMIT_INFOEach pNext: member of any structure (including this one) in the pNext chain must be either NULL/ or a pointer to a valid instance of , , , i, or gEach sType member in the pNext chain must be uniqueIf waitSemaphoreCount is not 0, pWaitSemaphores must( be a valid pointer to an array of waitSemaphoreCount valid  VkSemaphore handlesIf waitSemaphoreCount is not 0, pWaitDstStageMask must( be a valid pointer to an array of waitSemaphoreCount valid combinations of  valuesEach element of pWaitDstStageMask must not be 0If commandBufferCount is not 0, pCommandBuffers must( be a valid pointer to an array of commandBufferCount valid VkCommandBuffer handlesIf signalSemaphoreCount is not 0, pSignalSemaphores must( be a valid pointer to an array of signalSemaphoreCount valid  VkSemaphore handlesEach of the elements of pCommandBuffers, the elements of pSignalSemaphores, and the elements of pWaitSemaphores that are valid handles must? have been created, allocated, or retrieved from the same VkDeviceSee Also, , , , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.waitSemaphoreCountd is the number of semaphores upon which to wait before executing the command buffers for the batch.pWaitSemaphores is a pointer to an array of semaphores upon which to wait before the command buffers for this batch begin execution. If semaphores to wait on are provided, they define a  phttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-semaphores-waitingsemaphore wait operation.pWaitDstStageMaskd is a pointer to an array of pipeline stages at which each corresponding semaphore wait will occur.commandBufferCount; is the number of command buffers to execute in the batch.pCommandBuffersF is a pointer to an array of command buffers to execute in the batch.signalSemaphoreCountL is the number of semaphores to be signaled once the commands specified in pCommandBuffers have completed execution.pSignalSemaphores is a pointer to an array of semaphores which will be signaled when the command buffers for this batch have completed execution. If semaphores to be signaled are provided, they define a  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-semaphores-signalingsemaphore signal operation.1VkSemaphore - Opaque handle to a semaphore objectSee Also, r, A;, <, , A, , , 9, E , E-!Dummy data to tag the  with)VkFence - Opaque handle to a fence objectSee Also, B#, $, B5, 6, 9, z, z, zU, r, , 3, 4, zz, z"Dummy data to tag the  with:VkCommandBuffer - Opaque handle to a command buffer objectSee Also, , :, , C, , , , , , , , , , , , , , , , D, D, D, , , , , , , , l, , l, C, , , , , C, , , , , , , , , , , , , , , , ], , , [, , , , , , J, , , m, , , E, #Dummy data to tag the  with)VkQueue - Opaque handle to a queue objectSee Also, R, C, r, C, C, , , $Dummy data to tag the  with<VkPipelineStageFlagBits - Bitmask specifying pipeline stages Description!VK_PIPELINE_STAGE_TOP_OF_PIPE_BITa specifies the stage of the pipeline where any commands are initially received by the queue.)VK_PIPELINE_STAGE_COMMAND_PROCESS_BIT_NVX\ specifies the stage of the pipeline where device-side generation of commands via  is handled.#VK_PIPELINE_STAGE_DRAW_INDIRECT_BIT specifies the stage of the pipeline where Draw/DispatchIndirect data structures are consumed. This stage also includes reading commands written by ."VK_PIPELINE_STAGE_VERTEX_INPUT_BITV specifies the stage of the pipeline where vertex and index buffers are consumed.#VK_PIPELINE_STAGE_VERTEX_SHADER_BIT( specifies the vertex shader stage.1VK_PIPELINE_STAGE_TESSELLATION_CONTROL_SHADER_BIT6 specifies the tessellation control shader stage.4VK_PIPELINE_STAGE_TESSELLATION_EVALUATION_SHADER_BIT9 specifies the tessellation evaluation shader stage.%VK_PIPELINE_STAGE_GEOMETRY_SHADER_BIT* specifies the geometry shader stage.%VK_PIPELINE_STAGE_FRAGMENT_SHADER_BIT* specifies the fragment shader stage.*VK_PIPELINE_STAGE_EARLY_FRAGMENT_TESTS_BIT specifies the stage of the pipeline where early fragment tests (depth and stencil tests before fragment shading) are performed. This stage also includes  ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#renderpass-load-store-opssubpass load operations> for framebuffer attachments with a depth/stencil format.)VK_PIPELINE_STAGE_LATE_FRAGMENT_TESTS_BIT specifies the stage of the pipeline where late fragment tests (depth and stencil tests after fragment shading) are performed. This stage also includes  ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#renderpass-load-store-opssubpass store operations> for framebuffer attachments with a depth/stencil format.-VK_PIPELINE_STAGE_COLOR_ATTACHMENT_OUTPUT_BIT specifies the stage of the pipeline after blending where the final color values are output from the pipeline. This stage also includes  ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#renderpass-load-store-ops+subpass load and store operations^ and multisample resolve operations for framebuffer attachments with a color format.VK_PIPELINE_STAGE_TRANSFER_BIT` specifies the execution of copy commands. This includes the operations resulting from all  Thttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#copiescopy commands,  Thttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#clearsclear commands" (with the exception of ), and .$VK_PIPELINE_STAGE_COMPUTE_SHADER_BIT2 specifies the execution of a compute shader.$VK_PIPELINE_STAGE_BOTTOM_OF_PIPE_BITs specifies the final stage in the pipeline where operations generated by all commands complete execution.VK_PIPELINE_STAGE_HOST_BIT specifies a pseudo-stage indicating execution on the host of reads/writes of device memory. This stage is not invoked by any commands recorded in a command buffer."VK_PIPELINE_STAGE_ALL_GRAPHICS_BITf specifies the execution of all graphics pipeline stages, and is equivalent to the logical OR of: !VK_PIPELINE_STAGE_TOP_OF_PIPE_BIT #VK_PIPELINE_STAGE_DRAW_INDIRECT_BIT "VK_PIPELINE_STAGE_VERTEX_INPUT_BIT #VK_PIPELINE_STAGE_VERTEX_SHADER_BIT 1VK_PIPELINE_STAGE_TESSELLATION_CONTROL_SHADER_BIT 4VK_PIPELINE_STAGE_TESSELLATION_EVALUATION_SHADER_BIT %VK_PIPELINE_STAGE_GEOMETRY_SHADER_BIT %VK_PIPELINE_STAGE_FRAGMENT_SHADER_BIT *VK_PIPELINE_STAGE_EARLY_FRAGMENT_TESTS_BIT )VK_PIPELINE_STAGE_LATE_FRAGMENT_TESTS_BIT -VK_PIPELINE_STAGE_COLOR_ATTACHMENT_OUTPUT_BIT $VK_PIPELINE_STAGE_BOTTOM_OF_PIPE_BIT"VK_PIPELINE_STAGE_ALL_COMMANDS_BIT} is equivalent to the logical OR of every other pipeline stage flag that is supported on the queue it is used with.Note"An execution dependency with only $VK_PIPELINE_STAGE_BOTTOM_OF_PIPE_BIT. in the destination stage mask will only prevent that stage from executing in subsequently submitted commands. As this stage does not perform any actual execution, this is not observable - in effect, it does not delay processing of subsequent commands. Similarly an execution dependency with only !VK_PIPELINE_STAGE_TOP_OF_PIPE_BITX in the source stage mask will effectively not wait for any prior commands to complete./When defining a memory dependency, using only $VK_PIPELINE_STAGE_BOTTOM_OF_PIPE_BIT or !VK_PIPELINE_STAGE_TOP_OF_PIPE_BITc would never make any accesses available and/or visible because these stages do not access memory.$VK_PIPELINE_STAGE_BOTTOM_OF_PIPE_BIT and !VK_PIPELINE_STAGE_TOP_OF_PIPE_BIT are useful for accomplishing layout transitions and queue ownership operations when the required execution dependency is satisfied by other means - for example, semaphore operations between queues.See Also, m, 3vkDeviceWaitIdle - Wait for a device to become idle Parametersdevice is the logical device to idle. DescriptionvkDeviceWaitIdle is equivalent to calling vkQueueWaitIdle for all queues owned by device.Valid Usage (Implicit)device must be a valid VkDevice handleHost SynchronizationHost access to all VkQueue objects created from device must be externally synchronized Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_DEVICE_LOSTSee Also1vkQueueWaitIdle - Wait for a queue to become idle Parametersqueue is the queue on which to wait. DescriptionvkQueueWaitIdleo is equivalent to submitting a fence to a queue and waiting with an infinite timeout for that fence to signal.Valid Usage (Implicit)queue must be a valid VkQueue handleCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type m - l - g Any | -  Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_DEVICE_LOSTSee AlsoOvkQueueSubmit - Submits a sequence of semaphores or command buffers to a queue Parametersqueue< is the queue that the command buffers will be submitted to. submitCount" is the number of elements in the pSubmits array.pSubmits is a pointer to an array of D structures, each specifying a command buffer submission batch.fence is an optionalg handle to a fence to be signaled once all submitted command buffers have completed execution. If fence is not , it defines a  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-fences-signalingfence signal operation. DescriptionNote>Submission can be a high overhead operation, and applications should6 attempt to batch work together into as few calls to  vkQueueSubmit as possible. vkQueueSubmit is a  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#devsandqueues-submissionqueue submission command,, with each batch defined by an element of pSubmits as an instance of the A structure. Batches begin execution in the order they appear in pSubmits, but may complete out of order..Fence and semaphore operations submitted with  have additional ordering constraints compared to other submission commands, with dependencies involving previous and subsequent queue operations. Information about these additional constraints can be found in the  hhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-semaphores semaphore and  dhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-fencesfence sections of  ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronizationthe synchronization chapter.Details on the interaction of pWaitDstStageMask, with synchronization are described in the  phttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-semaphores-waitingsemaphore wait operation section of  ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronizationthe synchronization chapter.!The order that batches appear in pSubmits is used to determine  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-submission-ordersubmission order, and thus all the  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-implicitimplicit ordering guaranteesJ that respect it. Other than these implicit ordering guarantees and any  ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization$explicit synchronization primitives, these batches may+ overlap or otherwise execute out of order.8If any command buffer submitted to this queue is in the  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecycleexecutable state, it is moved to the  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclepending stateV. Once execution of all submissions of a command buffer complete, it moves from the  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclepending state, back to the  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecycleexecutable state.. If a command buffer was recorded with the +VK_COMMAND_BUFFER_USAGE_ONE_TIME_SUBMIT_BIT% flag, it instead moves back to the  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecycleinvalid state.If  vkQueueSubmit fails, it may return VK_ERROR_OUT_OF_HOST_MEMORY or VK_ERROR_OUT_OF_DEVICE_MEMORY". If it does, the implementation must ensure that the state and contents of any resources or synchronization primitives referenced by the submitted command buffers and any semaphores referenced by pSubmits/ is unaffected by the call or its failure. If  vkQueueSubmitd fails in such a way that the implementation is unable to make that guarantee, the implementation must return VK_ERROR_DEVICE_LOST. See  ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#devsandqueues-lost-device Lost Device. Valid UsageIf fence is not , fence must be unsignaled If fence is not , fence mustg not be associated with any other queue command that has not yet completed execution on that queueAny calls to ,  or R that have been recorded into any of the command buffer elements of the pCommandBuffers member of any element of pSubmits, must not reference any } that is referenced by any of those commands in a command buffer that has been submitted to another queue and is still in the  pending state..Any stage flag included in any element of the pWaitDstStageMask member of any element of pSubmits mustB be a pipeline stage supported by one of the capabilities of queue, as specified in the  whttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-supported'table of supported pipeline stages.Each element of the pSignalSemaphores member of any element of pSubmits must\ be unsignaled when the semaphore signal operation it defines is executed on the deviceGWhen a semaphore unsignal operation defined by any element of the pWaitSemaphores member of any element of pSubmits executes on queue, no other queue must" be waiting on the same semaphore.All elements of the pWaitSemaphores member of all elements of pSubmits must/ be semaphores that are signaled, or have  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-semaphores-signaling semaphore signal operations) previously submitted for execution.Each element of the pCommandBuffers member of each element of pSubmits must be in the  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecycle pending or executable state.If any element of the pCommandBuffers member of any element of pSubmits was not recorded with the ,VK_COMMAND_BUFFER_USAGE_SIMULTANEOUS_USE_BIT, it must not be in the  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclepending state.Any  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-secondary'secondary command buffers recorded into any element of the pCommandBuffers member of any element of pSubmits must be in the  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecycle pending or executable state.If any  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-secondary'secondary command buffers recorded into any element of the pCommandBuffers member of any element of pSubmits was not recorded with the ,VK_COMMAND_BUFFER_USAGE_SIMULTANEOUS_USE_BIT, it must not be in the  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclepending state.Each element of the pCommandBuffers member of each element of pSubmits must have been allocated from a  VkCommandPool1 that was created for the same queue family queue belongs to.Valid Usage (Implicit)queue must be a valid VkQueue handleIf  submitCount is not 0, pSubmits must( be a valid pointer to an array of  submitCount valid  VkSubmitInfo structuresIf fence is not , fence must be a valid VkFence handleBoth of fence, and queue that are valid handles must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to queue must be externally synchronizedHost access to pSubmits[].pWaitSemaphores[] must be externally synchronizedHost access to pSubmits[].pSignalSemaphores[] must be externally synchronizedHost access to fence must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type m - l - g Any | -  Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_DEVICE_LOSTSee Also, , 3vkGetDeviceQueue - Get a queue handle from a device Parametersdevice+ is the logical device that owns the queue.queueFamilyIndexB is the index of the queue family to which the queue belongs. queueIndexE is the index within this queue family of the queue to retrieve.pQueue is a pointer to a VkQueueI object that will be filled with the handle for the requested queue. Valid UsagequeueFamilyIndex must8 be one of the queue family indices specified when device was created, via the VkDeviceQueueCreateInfo structure queueIndex mustZ be less than the number of queues created for the specified queue family index when device was created, via the  queueCount member of the VkDeviceQueueCreateInfo structure~ ::flags must have been set to zero when device was createdValid Usage (Implicit)device must be a valid VkDevice handlepQueue must be a valid pointer to a VkQueue handleSee Also, ''ANone "-STbejk>UVkSemaphoreGetFdInfoKHR - Structure describing a POSIX FD semaphore export operation DescriptionGThe properties of the file descriptor returned depend on the value of  handleType. See V for a description of the properties of the defined external semaphore handle types. Valid Usage handleType must have been included in 7:: handleTypes when  semaphore s current payload was created. semaphore must[ not currently have its payload replaced by an imported payload as described below in  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-semaphores-importing!Importing Semaphore PayloadsF unless that imported payload s handle type was included in 5!::exportFromImportedHandleTypes for  handleType.If  handleType\ refers to a handle type with copy payload transference semantics, as defined below in  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-semaphores-importing!Importing Semaphore Payloads , there must be no queue waiting on  semaphore.If  handleTypeH refers to a handle type with copy payload transference semantics,  semaphore must) be signaled, or have an associated  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-semaphores-signalingsemaphore signal operation pending execution. handleType must. be defined as a POSIX file descriptor handle.Valid Usage (Implicit)sType must be +VK_STRUCTURE_TYPE_SEMAPHORE_GET_FD_INFO_KHRpNext must be NULL semaphore must be a valid  VkSemaphore handle handleType must be a valid  valueSee Also, , , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure. semaphore4 is the semaphore from which state will be exported. handleType! is the type of handle requested.aVkImportSemaphoreFdInfoKHR - Structure specifying POSIX file descriptor to import to a semaphore DescriptionThe handle types supported by  handleType are:3 Handle Type  Transference  Permanence Supported  /VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_OPAQUE_FD_BIT  Reference  Temporary,Permanent  -VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_SYNC_FD_BIT  Copy  Temporary 4Handle Types Supported by VkImportSemaphoreFdInfoKHR Valid Usage handleType must be a value included in the  vhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-semaphore-handletypes-fd>Handle Types Supported by VkImportSemaphoreFdInfoKHR table.fd must" obey any requirements listed for  handleType in  {https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#external-semaphore-handle-types-compatibility2external semaphore handle types compatibility.Valid Usage (Implicit)sType must be .VK_STRUCTURE_TYPE_IMPORT_SEMAPHORE_FD_INFO_KHRpNext must be NULL semaphore must be a valid  VkSemaphore handleflags must be a valid combination of 7 values handleType must be a valid  valueHost SynchronizationHost access to  semaphore must be externally synchronizedSee Also, , , , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure. semaphore: is the semaphore into which the payload will be imported.flags is a bitmask of 7O specifying additional parameters for the semaphore payload import operation. handleType specifies the type of fd.fd" is the external handle to import.HvkImportSemaphoreFdKHR - Import a semaphore from a POSIX file descriptor Parametersdevice2 is the logical device that created the semaphore.pImportSemaphoreFdInfo points to a ? structure specifying the semaphore and import parameters. DescriptionImporting a semaphore payload from a file descriptor transfers ownership of the file descriptor from the application to the Vulkan implementation. The application mustN not perform any operations on the file descriptor after a successful import. Applications can import the same semaphore payload into multiple instances of Vulkan, into the same instance from which it was exported, and multiple times into a given Vulkan instance. Valid Usage semaphore musta not be associated with any queue command that has not yet completed execution on that queueValid Usage (Implicit)device must be a valid VkDevice handlepImportSemaphoreFdInfo must$ be a valid pointer to a valid VkImportSemaphoreFdInfoKHR structure Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY  VK_ERROR_INVALID_EXTERNAL_HANDLESee Also, HvkGetSemaphoreFdKHR - Get a POSIX file descriptor handle for a semaphore ParametersdeviceF is the logical device that created the semaphore being exported. pGetFdInfo) is a pointer to an instance of the > structure containing parameters of the export operation.pFdI will return the file descriptor representing the semaphore payload. Description Each call to vkGetSemaphoreFdKHR must} create a new file descriptor and transfer ownership of it to the application. To avoid leaking resources, the application mustG release ownership of the file descriptor when it is no longer needed.NoteOOwnership can be released in many ways. For example, the application can call close|() on the file descriptor, or transfer ownership back to Vulkan by using the file descriptor to import a semaphore payload.<Where supported by the operating system, the implementation must= set the file descriptor to be closed automatically when an execve system call is made.-Exporting a file descriptor from a semaphore maya have side effects depending on the transference of the specified handle type, as described in  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-semaphores-importingImporting Semaphore State.Valid Usage (Implicit)device must be a valid VkDevice handle pGetFdInfo must$ be a valid pointer to a valid VkSemaphoreGetFdInfoKHR structurepFd must be a valid pointer to a int value Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_TOO_MANY_OBJECTS VK_ERROR_OUT_OF_HOST_MEMORYSee Also, BNone "-STbejkMVkFenceGetFdInfoKHR - Structure describing a POSIX FD fence export operation DescriptionGThe properties of the file descriptor returned depend on the value of  handleType. See R for a description of the properties of the defined external fence handle types. Valid Usage handleType must have been included in ;:: handleTypes when fence s current payload was created.If  handleTypeH refers to a handle type with copy payload transference semantics, fence must) be signaled, or have an associated  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-fences-signalingfence signal operation pending execution.fence must[ not currently have its payload replaced by an imported payload as described below in  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-fences-importingImporting Fence PayloadsF unless that imported payload s handle type was included in 9::exportFromImportedHandleTypes for  handleType. handleType must. be defined as a POSIX file descriptor handle.Valid Usage (Implicit)sType must be 'VK_STRUCTURE_TYPE_FENCE_GET_FD_INFO_KHRpNext must be NULLfence must be a valid VkFence handle handleType must be a valid  valueSee Also, , , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.fence0 is the fence from which state will be exported. handleType! is the type of handle requested.VkImportFenceFdInfoKHR - (None) DescriptionThe handle types supported by  handleType are:/ Handle Type  Transference  Permanence Supported  +VK_EXTERNAL_FENCE_HANDLE_TYPE_OPAQUE_FD_BIT  Reference  Temporary,Permanent  )VK_EXTERNAL_FENCE_HANDLE_TYPE_SYNC_FD_BIT  Copy  Temporary 0Handle Types Supported by VkImportFenceFdInfoKHR Valid Usage handleType must be a value included in the  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-fence-handletypes-fd:Handle Types Supported by VkImportFenceFdInfoKHR table.fd must" obey any requirements listed for  handleType in  whttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#external-fence-handle-types-compatibility.external fence handle types compatibility.If  handleType is )VK_EXTERNAL_FENCE_HANDLE_TYPE_SYNC_FD_BIT, the special value -1 for fd is treated like a valid sync file descriptor referring to an object that has already signaled. The import operation will succeed and the VkFence[ will have a temporarily imported payload as if a valid file descriptor had been provided.NoteKThis special behavior for importing an invalid sync file descriptor allows easier interoperability with other system APIs which use the convention that an invalid sync file descriptor represents work that has already completed and doesn t need to be waited for. It is consistent with the option for implementations to return a -1# file descriptor when exporting a )VK_EXTERNAL_FENCE_HANDLE_TYPE_SYNC_FD_BIT from a VkFence which is signaled.Valid Usage (Implicit)sType must be *VK_STRUCTURE_TYPE_IMPORT_FENCE_FD_INFO_KHRpNext must be NULLfence must be a valid VkFence handleflags must be a valid combination of ; values handleType must be a valid  valueHost SynchronizationHost access to fence must be externally synchronizedSee Also, , C, , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.fence6 is the fence into which the payload will be imported.flags is a bitmask of ;J specifying additional parameters for the fence payload import operation. handleType specifies the type of fd.fd" is the external handle to import.@vkImportFenceFdKHR - Import a fence from a POSIX file descriptor Parametersdevice. is the logical device that created the fence.pImportFenceFdInfo points to a ; structure specifying the fence and import parameters. DescriptionImporting a fence payload from a file descriptor transfers ownership of the file descriptor from the application to the Vulkan implementation. The application mustN not perform any operations on the file descriptor after a successful import. Applications can import the same fence payload into multiple instances of Vulkan, into the same instance from which it was exported, and multiple times into a given Vulkan instance. Valid Usagefence musta not be associated with any queue command that has not yet completed execution on that queueValid Usage (Implicit)device must be a valid VkDevice handlepImportFenceFdInfo must$ be a valid pointer to a valid VkImportFenceFdInfoKHR structure Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY  VK_ERROR_INVALID_EXTERNAL_HANDLESee Also, @vkGetFenceFdKHR - Get a POSIX file descriptor handle for a fence ParametersdeviceB is the logical device that created the fence being exported. pGetFdInfo) is a pointer to an instance of the > structure containing parameters of the export operation.pFdE will return the file descriptor representing the fence payload. Description Each call to vkGetFenceFdKHR must} create a new file descriptor and transfer ownership of it to the application. To avoid leaking resources, the application mustG release ownership of the file descriptor when it is no longer needed.NoteOOwnership can be released in many ways. For example, the application can call closex() on the file descriptor, or transfer ownership back to Vulkan by using the file descriptor to import a fence payload.If  pGetFdInfo:: handleType is )VK_EXTERNAL_FENCE_HANDLE_TYPE_SYNC_FD_BIT( and the fence is signaled at the time vkGetFenceFdKHR is called, pFd may return the value -1% instead of a valid file descriptor.<Where supported by the operating system, the implementation must= set the file descriptor to be closed automatically when an execve system call is made.)Exporting a file descriptor from a fence maya have side effects depending on the transference of the specified handle type, as described in  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-fences-importingImporting Fence State.Valid Usage (Implicit)device must be a valid VkDevice handle pGetFdInfo must$ be a valid pointer to a valid VkFenceGetFdInfoKHR structurepFd must be a valid pointer to a int value Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_TOO_MANY_OBJECTS VK_ERROR_OUT_OF_HOST_MEMORYSee Also, CNone "-KSTbejkN>`VkDebugUtilsMessengerCallbackDataEXT - Structure specifying parameters returned to the callback DescriptionNote^This structure should only be considered valid during the lifetime of the triggered callback.oSince adding queue and command buffer labels behaves like pushing and popping onto a stack, the order of both  pQueueLabels and  pCmdBufLabels^ is based on the order the labels were defined. The result is that the first label in either  pQueueLabels or  pCmdBufLabelsq will be the first defined (and therefore the oldest) while the last label in each list will be the most recent.Note pQueueLabels0 will only be non-NULL if one of the objects in pObjects' can be related directly to a defined VkQueue6 which has had one or more labels associated with it. Likewise,  pCmdBufLabels1 will only be non-NULL if one of the objects in pObjects& can be related directly to a defined VkCommandBuffer which has had one or more labels associated with it. Additionally, while command buffer labels allow for beginning and ending across different command buffers, the debug messaging framework cannot guarantee that labels in  pCmdBufLables will contain those defined outside of the associated command buffer. This is partially due to the fact that the association of one command buffer with another may not have been defined at the time the debug message is triggered.Valid Usage (Implicit)sType must be 9VK_STRUCTURE_TYPE_DEBUG_UTILS_MESSENGER_CALLBACK_DATA_EXTpNext must be NULLflags must be 0If pMessageIdName is not NULL, pMessageIdName must' be a null-terminated UTF-8 stringpMessage must" be a null-terminated UTF-8 string objectCount must be greater than 0See Also, 0, ', , 8sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.flags" is 0 and reserved for future use.pMessageIdName# is a null-terminated string that identifies the the particular message ID that is associated with the provided message. If the message corresponds to a validation layer message, then this string may contain the portion of the Vulkan specification that is believed to have been violated.messageIdNumber is the ID number of the triggering message. If the message corresponds to a validation layer message, then this number is related to the internal number associated with the message being triggered.pMessage> is a null-terminated string detailing the trigger conditions. queueLabelCount& is a count of items contained in the  pQueueLabels array.  pQueueLabels& is NULL or a pointer to an array of  active in the current VkQueue3 at the time the callback was triggered. Refer to  dhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#debugging-queue-labels Queue Labels for more information. cmdBufLabelCount& is a count of items contained in the  pCmdBufLabels array.  pCmdBufLabels& is NULL or a pointer to an array of  active in the current VkCommandBuffer3 at the time the callback was triggered. Refer to  mhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#debugging-command-buffer-labelsCommand Buffer Labels for more information.  objectCount& is a count of items contained in the pObjects array.pObjects is a pointer to an array of ' objects related to the detected issue. The array is roughly in order or importance, but the 0th element is always guaranteed to be the most important object for this message.hVkDebugUtilsMessengerCreateInfoEXT - Structure specifying parameters of a newly created debug messenger Description For each VkDebugUtilsMessengerEXT that is created the "VkDebugUtilsMessengerCreateInfoEXT::messageSeverity and "VkDebugUtilsMessengerCreateInfoEXT:: messageTypes determine when that "VkDebugUtilsMessengerCreateInfoEXT::pfnUserCallbacku is called. The process to determine if the user s pfnUserCallback is triggered when an event occurs is as follows: BThe implementation will perform a bitwise AND of the event s 6 with the messageSeverity& provided during creation of the . object. *If the value is 0, the message is skipped.@The implementation will perform bitwise AND of the event s 4 with the  messageType* provided during the creation of the . object. *If the value is 0, the message is skipped.?The callback will trigger a debug message for the current eventThe callback will come directly from the component that detected the event, unless some other layer intercepts the calls for its own purposes (filter them in a different way, log to a system error log, etc.).An application can) receive multiple callbacks if multiple VkDebugUtilsMessengerEXTl objects are created. A callback will always be executed in the same thread as the originating Vulkan call. A callback cans be called from multiple threads simultaneously (if the application is making Vulkan calls from multiple threads). Valid UsagepfnUserCallback must be a valid /Valid Usage (Implicit)sType must be 7VK_STRUCTURE_TYPE_DEBUG_UTILS_MESSENGER_CREATE_INFO_EXTflags must be 0messageSeverity must be a valid combination of 6 valuesmessageSeverity must not be 0 messageType must be a valid combination of 4 values messageType must not be 0See Also/, , , 2, , :sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.flags" is 0 and reserved for future use.messageSeverity is a bitmask of 6N specifying which severity of event(s) will cause this callback to be called.pfnUserCallback. is the application callback function to call. pUserData+ is user data to be passed to the callback.;VkDebugUtilsLabelEXT - Specify parameters of a label regionValid Usage (Implicit)sType must be 'VK_STRUCTURE_TYPE_DEBUG_UTILS_LABEL_EXTpNext must be NULL pLabelName must" be a null-terminated UTF-8 stringSee Also, , =, ;, @, >sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure. pLabelNameU is a pointer to a null-terminated UTF-8 string that contains the name of the label.colore is an optional RGBA color value that can be associated with the label. A particular implementation may{ choose to ignore this color value. The values contain RGBA values in order, in the range 0.0 to 1.0. If all elements in color# are set to 0.0 then it is ignored.RVkDebugUtilsObjectTagInfoEXT - Specify parameters of a tag to attach to an object DescriptionThe tagName parameter gives a name or identifier to the type of data being tagged. This can be used by debugging layers to easily filter for only data that can be used by that implementation. Valid Usage objectType must not be VK_OBJECT_TYPE_UNKNOWN objectHandle must not be  objectHandle must5 be a Vulkan object of the type associated with  objectType as defined in  dhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#debugging-object-types+{html_spec_relative}#debugging-object-types.Valid Usage (Implicit)sType must be 1VK_STRUCTURE_TYPE_DEBUG_UTILS_OBJECT_TAG_INFO_EXTpNext must be NULL objectType must be a valid  valuepTag must# be a valid pointer to an array of tagSize bytestagSize must be greater than 0See Also, , A sType is the type of this structure.!pNext is NULL1 or a pointer to an extension-specific structure." objectType is a 0 specifying the type of the object to be named.# objectHandle is the object to be tagged.$tagName& is a numerical identifier of the tag.%tagSize8 is the number of bytes of data to attach to the object.&pTag is an array of tagSize= bytes containing the data to be associated with the object.'RVkDebugUtilsObjectNameInfoEXT - Specify parameters of a name to give to an object Description Applications may> change the name associated with an object simply by calling vkSetDebugUtilsObjectNameEXT again with a new string. If  pObjectName> is an empty string, then any previously set name is removed. Valid Usage objectType must not be VK_OBJECT_TYPE_UNKNOWN objectHandle must not be  objectHandle must5 be a Vulkan object of the type associated with  objectType as defined in  dhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#debugging-object-types+{html_spec_relative}#debugging-object-types.Valid Usage (Implicit)sType must be 2VK_STRUCTURE_TYPE_DEBUG_UTILS_OBJECT_NAME_INFO_EXTpNext must be NULL objectType must be a valid  valueIf  pObjectName is not NULL,  pObjectName must' be a null-terminated UTF-8 stringSee Also, , , B)sType is the type of this structure.*pNext is NULL1 or a pointer to an extension-specific structure.+ objectType is a 0 specifying the type of the object to be named., objectHandle is the object to be named.- pObjectNameD is a null-terminated UTF-8 string specifying the name to apply to  objectHandle..DVkDebugUtilsMessengerEXT - Opaque handle to a debug messenger object DescriptionThe debug messenger will provide detailed feedback on the application s use of Vulkan when events of interest occur. When an event of interest does occur, the debug messenger will submit a debug message to the debug callback that was provided during its creation. Additionally, the debug messenger is responsible with filtering out debug messages that the callback isn t interested in and will only provide desired debug messages.See Also:, 9%Dummy data to tag the  with/]PFN_vkDebugUtilsMessengerCallbackEXT - Application-defined debug messenger callback function ParametersmessageSeverity specifies the 6# that triggered this callback. messageTypes specifies the 4# that triggered this callback. pCallbackData4 contains all the callback related data in the  structure. pUserData) is the user data provided when the . was created. Description The callback must not call 9.The callback returns a VkBool32E, which is interpreted in a layer-specified manner. The application should always return VK_FALSE. The VK_TRUE1 value is reserved for use in layer development.See Also4oVkDebugUtilsMessageTypeFlagBitsEXT - Bitmask specifying which types of events cause a debug messenger callbackSee Also6xVkDebugUtilsMessageSeverityFlagBitsEXT - Bitmask specifying which severities of events cause a debug messenger callbackSee Also, 88CvkSubmitDebugUtilsMessageEXT - Inject a message into a debug stream Parametersinstance is the debug stream s  VkInstance.messageSeverity is the 6% severity of this event/message. messageTypes is a bitmask of 4F specifying which type of event(s) to identify with this message. pCallbackData4 contains all the callback related data in the  structure. DescriptionThe call will propagate through the layers and generate callback(s) as indicated by the message s flags. The parameters are passed on to the callback in addition to the  pUserDataB value that was defined at the time the messenger was registered.Valid Usage (Implicit)instance must be a valid  VkInstance handlemessageSeverity must be a valid 6 value messageTypes must be a valid combination of 4 values messageTypes must not be 0 pCallbackData must$ be a valid pointer to a valid $VkDebugUtilsMessengerCallbackDataEXT structureSee Also6, , , 9BvkDestroyDebugUtilsMessengerEXT - Destroy a debug messenger object Parametersinstance- the instance where the callback was created. messenger the VkDebugUtilsMessengerEXT object to destroy.  messenger* is an externally synchronized object and mustJ not be used on more than one thread at a time. This means that vkDestroyDebugUtilsMessengerEXT must. not be called when a callback is active. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. Valid UsageIf VkAllocationCallbacks were provided when  messenger1 was created, a compatible set of callbacks must be provided hereIf no VkAllocationCallbacks were provided when  messenger was created,  pAllocator must be NULLValid Usage (Implicit)instance must be a valid  VkInstance handle messenger must be a valid VkDebugUtilsMessengerEXT handleIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structure messenger must6 have been created, allocated, or retrieved from instanceHost SynchronizationHost access to  messenger must be externally synchronizedSee Also, ., :@vkCreateDebugUtilsMessengerEXT - Create a debug messenger object Parametersinstance. the instance the messenger will be used with. pCreateInfo points to a  structure which contains the callback pointer as well as defines the conditions under which this messenger will trigger the callback. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. pMessenger is a pointer to record the VkDebugUtilsMessengerEXT object created.Valid Usage (Implicit)instance must be a valid  VkInstance handle pCreateInfo must$ be a valid pointer to a valid "VkDebugUtilsMessengerCreateInfoEXT structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structure pMessenger must be a valid pointer to a VkDebugUtilsMessengerEXT handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORYSee Also, , ., ;DvkCmdInsertDebugUtilsLabelEXT - Insert a label into a command buffer Parameters commandBuffer? is the command buffer into which the command is recorded.pInfo$ is a pointer to an instance of the A structure specifying the parameters of the label to insert.Valid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle pLabelInfo must$ be a valid pointer to a valid VkDebugUtilsLabelEXT structure commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must- support graphics, or compute operationsHost SynchronizationHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Both  Graphics Compute  See Also, <@vkCmdEndDebugUtilsLabelEXT - Close a command buffer label region Parameters commandBuffer? is the command buffer into which the command is recorded. DescriptionAn application may open a debug label region in one command buffer and close it in another, or otherwise split debug label regions across multiple command buffers or multiple queue submissions. When viewed from the linear series of submissions to a single queue, the calls to = and < must be matched and balanced. Valid UsageThere must be an outstanding vkCmdBeginDebugUtilsLabelEXT command prior to the vkCmdEndDebugUtilsLabelEXT on the queue that  commandBuffer is submitted toIf  commandBuffer& is a secondary command buffer, there must be an outstanding vkCmdBeginDebugUtilsLabelEXT command recorded to  commandBuffer6 that has not previously been ended by a call to vkCmdEndDebugUtilsLabelEXT.Valid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must- support graphics, or compute operationsHost SynchronizationHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Both  Graphics Compute  See Also=GvkCmdBeginDebugUtilsLabelEXT - Open a command buffer debug label region Parameters commandBuffer? is the command buffer into which the command is recorded. pLabelInfo) is a pointer to an instance of the F structure specifying the parameters of the label region to open.Valid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle pLabelInfo must$ be a valid pointer to a valid VkDebugUtilsLabelEXT structure commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must- support graphics, or compute operationsHost SynchronizationHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Both  Graphics Compute  See Also, >=vkQueueInsertDebugUtilsLabelEXT - Insert a label into a queue Parametersqueue8 is the queue into which a debug label will be inserted. pLabelInfo) is a pointer to an instance of the A structure specifying the parameters of the label to insert.Valid Usage (Implicit)queue must be a valid VkQueue handle pLabelInfo must$ be a valid pointer to a valid VkDebugUtilsLabelEXT structureCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type m - l - g Any | - See Also, ??vkQueueEndDebugUtilsLabelEXT - Close a queue debug label region Parametersqueue= is the queue in which a debug label region should be closed. Description The calls to @ and ? must be matched and balanced. Valid UsageThere must be an outstanding vkQueueBeginDebugUtilsLabelEXT command prior to the vkQueueEndDebugUtilsLabelEXT on the queueValid Usage (Implicit)queue must be a valid VkQueue handleCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type m - l - g Any | - See Also@@vkQueueBeginDebugUtilsLabelEXT - Open a queue debug label region Parametersqueue5 is the queue in which to start a debug label region. pLabelInfo) is a pointer to an instance of the F structure specifying the parameters of the label region to open.Valid Usage (Implicit)queue must be a valid VkQueue handle pLabelInfo must$ be a valid pointer to a valid VkDebugUtilsLabelEXT structureCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type m - l - g Any | - See Also, A@vkSetDebugUtilsObjectTagEXT - Attach arbitrary data to an object Parametersdevice' is the device that created the object.pTagInfo) is a pointer to an instance of the M structure specifying the parameters of the tag to attach to the object.Valid Usage (Implicit)device must be a valid VkDevice handlepTagInfo must$ be a valid pointer to a valid VkDebugUtilsObjectTagInfoEXT structureHost SynchronizationHost access to pTagInfo.objectHandle must be externally synchronized Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, BEvkSetDebugUtilsObjectNameEXT - Give a user-friendly name to an object Parametersdevice' is the device that created the object. pNameInfo) is a pointer to an instance of the 'K structure specifying the parameters of the name to set on the object.Valid Usage (Implicit)device must be a valid VkDevice handle pNameInfo must$ be a valid pointer to a valid VkDebugUtilsObjectNameInfoEXT structureHost SynchronizationHost access to pNameInfo.objectHandle must be externally synchronized Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also', K/VK_DEBUG_UTILS_MESSAGE_TYPE_PERFORMANCE_BIT_EXTA specifies a potentially non-optimal use of Vulkan, e.g. using  when setting ::loadOp to VK_ATTACHMENT_LOAD_OP_CLEAR would have worked.L.VK_DEBUG_UTILS_MESSAGE_TYPE_VALIDATION_BIT_EXT specifies that something has occurred during validation against the Vulkan specification that may indicate invalid behavior.M+VK_DEBUG_UTILS_MESSAGE_TYPE_GENERAL_BIT_EXTp specifies that some general event has occurred. This is typically a non-specification, non-performance event.N-VK_DEBUG_UTILS_MESSAGE_SEVERITY_ERROR_BIT_EXT[ specifies that an error that may cause undefined results, including an application crash.O/VK_DEBUG_UTILS_MESSAGE_SEVERITY_WARNING_BIT_EXT specifies use of Vulkan that may expose an app bug. Such cases may not be immediately harmful, such as a fragment shader outputting to a location with no attachment. Other cases may point to behavior that is almost certainly bad when unintended such as using an image whose memory has not been filled. In general if you see a warning but you know that the behavior is intended/desired, then simply ignore the warning.P,VK_DEBUG_UTILS_MESSAGE_SEVERITY_INFO_BIT_EXTo specifies an informational message such as resource details that may be handy when debugging an application.Q/VK_DEBUG_UTILS_MESSAGE_SEVERITY_VERBOSE_BIT_EXT specifies the most verbose output indicating all diagnostic messages from the Vulkan loader, layers, and drivers should be captured.S      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQS67QPON45MLK2301JIHGFEDC/.BA@?>=<;:98'()*+,- !"#$%&     DNone "-STbejk|}RVkDebugMarkerMarkerInfoEXT - Specify parameters of a command buffer marker regionValid Usage (Implicit)sType must be .VK_STRUCTURE_TYPE_DEBUG_MARKER_MARKER_INFO_EXTpNext must be NULL pMarkerName must" be a null-terminated UTF-8 stringSee Also, , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure. pMarkerNameV is a pointer to a null-terminated UTF-8 string that contains the name of the marker.color is an optionalW RGBA color value that can be associated with the marker. A particular implementation may{ choose to ignore this color value. The values contain RGBA values in order, in the range 0.0 to 1.0. If all elements in color# are set to 0.0 then it is ignored.SVkDebugMarkerObjectTagInfoEXT - Specify parameters of a tag to attach to an object DescriptionThe tagName parameter gives a name or identifier to the type of data being tagged. This can be used by debugging layers to easily filter for only data that can be used by that implementation. Valid Usage objectType must not be 'VK_DEBUG_REPORT_OBJECT_TYPE_UNKNOWN_EXTobject must not be object must5 be a Vulkan object of the type associated with  objectType as defined in  ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#debug-report-object-types.{html_spec_relative}#debug-report-object-types.Valid Usage (Implicit)sType must be 2VK_STRUCTURE_TYPE_DEBUG_MARKER_OBJECT_TAG_INFO_EXTpNext must be NULL objectType must be a valid / valuepTag must# be a valid pointer to an array of tagSize bytestagSize must be greater than 0See Also/, , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure. objectType is a /0 specifying the type of the object to be named.object is the object to be tagged.tagName& is a numerical identifier of the tag.tagSize8 is the number of bytes of data to attach to the object.pTag is an array of tagSize= bytes containing the data to be associated with the object.SVkDebugMarkerObjectNameInfoEXT - Specify parameters of a name to give to an object Description Applications may> change the name associated with an object simply by calling vkDebugMarkerSetObjectNameEXT< again with a new string. To remove a previously set name,  pObjectName should be set to an empty string. Valid Usage objectType must not be 'VK_DEBUG_REPORT_OBJECT_TYPE_UNKNOWN_EXTobject must not be object must5 be a Vulkan object of the type associated with  objectType as defined in  ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#debug-report-object-types.{html_spec_relative}#debug-report-object-types.Valid Usage (Implicit)sType must be 3VK_STRUCTURE_TYPE_DEBUG_MARKER_OBJECT_NAME_INFO_EXTpNext must be NULL objectType must be a valid / value pObjectName must" be a null-terminated UTF-8 stringSee Also/, , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure. objectType is a /0 specifying the type of the object to be named.object is the object to be named. pObjectNameD is a null-terminated UTF-8 string specifying the name to apply to object.GvkCmdDebugMarkerInsertEXT - Insert a marker label into a command buffer Parameters commandBuffer? is the command buffer into which the command is recorded. pMarkerInfo) is a pointer to an instance of the }B structure specifying the parameters of the marker to insert.Valid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle pMarkerInfo must$ be a valid pointer to a valid VkDebugMarkerMarkerInfoEXT structure commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must- support graphics, or compute operationsHost SynchronizationHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Both  Graphics Compute  See Also, }=vkCmdDebugMarkerEndEXT - Close a command buffer marker region Parameters commandBuffer? is the command buffer into which the command is recorded. DescriptionAn application may open a marker region in one command buffer and close it in another, or otherwise split marker regions across multiple command buffers or multiple queue submissions. When viewed from the linear series of submissions to a single queue, the calls to vkCmdDebugMarkerBeginEXT and vkCmdDebugMarkerEndEXT must be matched and balanced. Valid UsageThere must be an outstanding  command prior to the vkCmdDebugMarkerEndEXT on the queue that  commandBuffer is submitted toIf  commandBuffer& is a secondary command buffer, there must be an outstanding  command recorded to  commandBuffer6 that has not previously been ended by a call to .Valid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must- support graphics, or compute operationsHost SynchronizationHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Both  Graphics Compute  See Also>vkCmdDebugMarkerBeginEXT - Open a command buffer marker region Parameters commandBuffer? is the command buffer into which the command is recorded. pMarkerInfo) is a pointer to an instance of the }G structure specifying the parameters of the marker region to open.Valid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle pMarkerInfo must$ be a valid pointer to a valid VkDebugMarkerMarkerInfoEXT structure commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must- support graphics, or compute operationsHost SynchronizationHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Both  Graphics Compute  See Also, }AvkDebugMarkerSetObjectTagEXT - Attach arbitrary data to an object Parametersdevice' is the device that created the object.pTagInfo) is a pointer to an instance of the M structure specifying the parameters of the tag to attach to the object.Valid Usage (Implicit)device must be a valid VkDevice handlepTagInfo must$ be a valid pointer to a valid VkDebugMarkerObjectTagInfoEXT structureHost SynchronizationHost access to pTagInfo.object must be externally synchronized Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, FvkDebugMarkerSetObjectNameEXT - Give a user-friendly name to an object Parametersdevice' is the device that created the object. pNameInfo) is a pointer to an instance of the K structure specifying the parameters of the name to set on the object.Valid Usage (Implicit)device must be a valid VkDevice handle pNameInfo must$ be a valid pointer to a valid VkDebugMarkerObjectNameInfoEXT structureHost SynchronizationHost access to pNameInfo.object must be externally synchronized Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also,  }~ }~ENone "-KSTbejkvUVkSemaphoreCreateInfo - Structure specifying parameters of a newly created semaphoreValid Usage (Implicit)sType must be 'VK_STRUCTURE_TYPE_SEMAPHORE_CREATE_INFOEach pNext: member of any structure (including this one) in the pNext chain must be either NULL/ or a pointer to a valid instance of 7 or Each sType member in the pNext chain must be uniqueflags must be 0See Also, , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.flags is reserved for future use.0VkSemaphoreCreateFlags - Reserved for future use DescriptionVkSemaphoreCreateFlagsQ is a bitmask type for setting a mask, but is currently reserved for future use.See Also/vkDestroySemaphore - Destroy a semaphore object Parametersdevice3 is the logical device that destroys the semaphore. semaphore+ is the handle of the semaphore to destroy. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. Valid Usage$All submitted batches that refer to  semaphore must have completed executionIf VkAllocationCallbacks were provided when  semaphore1 was created, a compatible set of callbacks must be provided hereIf no VkAllocationCallbacks were provided when  semaphore was created,  pAllocator must be NULLValid Usage (Implicit)device must be a valid VkDevice handleIf  semaphore is not ,  semaphore must be a valid  VkSemaphore handleIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structureIf  semaphore is a valid handle, it must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to  semaphore must be externally synchronizedSee Also, , 7vkCreateSemaphore - Create a new queue semaphore object Parametersdevice2 is the logical device that creates the semaphore. pCreateInfo) is a pointer to an instance of the VkSemaphoreCreateInfoT structure which contains information about how the semaphore is to be created. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. pSemaphoreM points to a handle in which the resulting semaphore object is returned. Description7When created, the semaphore is in the unsignaled state.Valid Usage (Implicit)device must be a valid VkDevice handle pCreateInfo must$ be a valid pointer to a valid VkSemaphoreCreateInfo structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structure pSemaphore must be a valid pointer to a  VkSemaphore handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, , ,   FNone "-KSTbejkȮLVkQueryPipelineStatisticFlags - Bitmask of VkQueryPipelineStatisticFlagBits DescriptionVkQueryPipelineStatisticFlags7 is a bitmask type for setting a mask of zero or more .See Also, , 5VkQueryResultFlags - Bitmask of VkQueryResultFlagBits DescriptionVkQueryResultFlags7 is a bitmask type for setting a mask of zero or more .See Also, , VVkQueryPoolCreateInfo - Structure specifying parameters of a newly created query pool DescriptionpipelineStatistics is ignored if  queryType is not !VK_QUERY_TYPE_PIPELINE_STATISTICS. Valid UsageIf the  whttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-pipelineStatisticsQuery pipeline statistics queries feature is not enabled,  queryType must not be !VK_QUERY_TYPE_PIPELINE_STATISTICSIf  queryType is !VK_QUERY_TYPE_PIPELINE_STATISTICS, pipelineStatistics must be a valid combination of  valuesValid Usage (Implicit)sType must be (VK_STRUCTURE_TYPE_QUERY_POOL_CREATE_INFOpNext must be NULLflags must be 0 queryType must be a valid  valueSee Also, , , , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.flags is reserved for future use. queryType is a ; value specifying the type of queries managed by the pool. queryCount. is the number of queries managed by the pool.pipelineStatistics is a bitmask of a specifying which counters will be returned in queries on the new pool, as described below in  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#queries-pipestats&{html_spec_relative}#queries-pipestats.2VkQueryPool - Opaque handle to a query pool objectSee Also, , , , , , , &Dummy data to tag the  withRVkQueryPipelineStatisticFlagBits - Bitmask specifying queried pipeline statistics Description7VK_QUERY_PIPELINE_STATISTIC_INPUT_ASSEMBLY_VERTICES_BITi specifies that queries managed by the pool will count the number of vertices processed by the  Uhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#drawinginput assembly= stage. Vertices corresponding to incomplete primitives may contribute to the count. 9VK_QUERY_PIPELINE_STATISTIC_INPUT_ASSEMBLY_PRIMITIVES_BITk specifies that queries managed by the pool will count the number of primitives processed by the  Uhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#drawinginput assembly stage. If primitive restart is enabled, restarting the primitive topology has no effect on the count. Incomplete primitives may be counted.9VK_QUERY_PIPELINE_STATISTIC_VERTEX_SHADER_INVOCATIONS_BIT specifies that queries managed by the pool will count the number of vertex shader invocations. This counter s value is incremented each time a vertex shader is  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#shaders-vertex-executioninvoked.;VK_QUERY_PIPELINE_STATISTIC_GEOMETRY_SHADER_INVOCATIONS_BIT specifies that queries managed by the pool will count the number of geometry shader invocations. This counter s value is incremented each time a geometry shader is  hhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#shaders-geometry-executioninvoked. In the case of  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#geometry-invocationsinstanced geometry shadersh, the geometry shader invocations count is incremented for each separate instanced invocation.:VK_QUERY_PIPELINE_STATISTIC_GEOMETRY_SHADER_PRIMITIVES_BIT# specifies that queries managed by the pool will count the number of primitives generated by geometry shader invocations. The counter s value is incremented each time the geometry shader emits a primitive. Restarting primitive topology using the SPIR-V instructions OpEndPrimitive or OpEndStreamPrimitiveC has no effect on the geometry shader output primitives count.4VK_QUERY_PIPELINE_STATISTIC_CLIPPING_INVOCATIONS_BITk specifies that queries managed by the pool will count the number of primitives processed by the  ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vertexpostproc-clippingPrimitive Clipping stage of the pipeline. The counter s value is incremented each time a primitive reaches the primitive clipping stage.3VK_QUERY_PIPELINE_STATISTIC_CLIPPING_PRIMITIVES_BITh specifies that queries managed by the pool will count the number of primitives output by the  ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vertexpostproc-clippingPrimitive Clipping stage of the pipeline. The counter s value is incremented each time a primitive passes the primitive clipping stage. The actual number of primitives output by the primitive clipping stage for a particular input primitive is implementation-dependent but must' satisfy the following conditions:}If at least one vertex of the input primitive lies inside the clipping volume, the counter is incremented by one or more.6Otherwise, the counter is incremented by zero or more.;VK_QUERY_PIPELINE_STATISTIC_FRAGMENT_SHADER_INVOCATIONS_BIT specifies that queries managed by the pool will count the number of fragment shader invocations. The counter s value is incremented each time the fragment shader is  hhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#shaders-fragment-executioninvoked.CVK_QUERY_PIPELINE_STATISTIC_TESSELLATION_CONTROL_SHADER_PATCHES_BIT specifies that queries managed by the pool will count the number of patches processed by the tessellation control shader. The counter s value is incremented once for each patch for which a tessellation control shader is  thttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#shaders-tessellation-control-executioninvoked.JVK_QUERY_PIPELINE_STATISTIC_TESSELLATION_EVALUATION_SHADER_INVOCATIONS_BIT specifies that queries managed by the pool will count the number of invocations of the tessellation evaluation shader. The counter s value is incremented each time the tessellation evaluation shader is  whttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#shaders-tessellation-evaluation-executioninvoked.:VK_QUERY_PIPELINE_STATISTIC_COMPUTE_SHADER_INVOCATIONS_BIT specifies that queries managed by the pool will count the number of compute shader invocations. The counter s value is incremented every time the compute shader is invoked. Implementations may skip the execution of certain compute shader invocations or execute additional compute shader invocations for implementation-dependent reasons as long as the results of rendering otherwise remain unchanged.These values are intended to measure relative statistics on one implementation. Various device architectures will count these values differently. Any or all counters may) be affected by the issues described in  ihttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#queries-operation-undefinedQuery Operation.Note*For example, tile-based rendering devices mayH need to replay the scene multiple times, affecting some of the counts.If a pipeline has rasterizerDiscardEnable enabled, implementations mayN discard primitives after the final vertex processing stage. As a result, if rasterizerDiscardEnable@ is enabled, the clipping input and output primitives counters may not be incremented.nWhen a pipeline statistics query finishes, the result for that query is marked as available. The application can# copy the result to a buffer (via vkCmdCopyQueryPoolResults/), or request it be put into host memory (via vkGetQueryPoolResults).See AlsoSVkQueryResultFlagBits - Bitmask specifying how and when query results are returnedSee Also0VkQueryPoolCreateFlags - Reserved for future use DescriptionVkQueryPoolCreateFlagsQ is a bitmask type for setting a mask, but is currently reserved for future use.See AlsoAVkQueryType - Specify the type of queries managed by a query poolSee AlsoXvkGetQueryPoolResults - Copy results of queries in a query pool to a host memory region Parametersdevice0 is the logical device that owns the query pool. queryPoolL is the query pool managing the queries containing the desired results. firstQuery is the initial query index. queryCount is the number of queries.  firstQuery and  queryCount together define a range of queries. For pipeline statistics queries, each query index in the pool contains one integer value for each bit that is enabled in ::pipelineStatistics when the pool is created.dataSize2 is the size in bytes of the buffer pointed to by pData.pDataO is a pointer to a user-allocated buffer where the results will be writtenstrideK is the stride in bytes between results for individual queries within pData.flags is a bitmask of 3 specifying how and when results are returned. DescriptionIf no bits are set in flags, and all requested queries are in the available state, results are written as an array of 32-bit unsigned integer values. The behavior when not all queries are available, is described  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#queries-wait-bit-not-setbelow.If VK_QUERY_RESULT_64_BIT@ is not set and the result overflows a 32-bit value, the value may) either wrap or saturate. Similarly, if VK_QUERY_RESULT_64_BIT< is set and the result overflows a 64-bit value, the value may either wrap or saturate.If VK_QUERY_RESULT_WAIT_BIT is set, Vulkan will wait for each query to be in the available state before retrieving the numerical results for that query. In this case, vkGetQueryPoolResults& is guaranteed to succeed and return  VK_SUCCESS if the queries become available in a finite time (i.e. if they have been issued and not reset). If queries will never finish (e.g. due to being reset but not issued), then vkGetQueryPoolResults may not return in finite time.If VK_QUERY_RESULT_WAIT_BIT and VK_QUERY_RESULT_PARTIAL_BIT8 are both not set then no result values are written to pDataN for queries that are in the unavailable state at the time of the call, and vkGetQueryPoolResults returns  VK_NOT_READY3. However, availability state is still written to pData for those queries if %VK_QUERY_RESULT_WITH_AVAILABILITY_BIT is set.Note Applications must& take care to ensure that use of the VK_QUERY_RESULT_WAIT_BIT bit has the desired effect.\For example, if a query has been used previously and a command buffer records the commands vkCmdResetQueryPool, vkCmdBeginQuery, and  vkCmdEndQueryN for that query, then the query will remain in the available state until the vkCmdResetQueryPool, command executes on a queue. Applications can use fences or events to ensure that a query has already been reset before checking for its results or availability status. Otherwise, a stale value could be returned from a previous use of the query.The above also applies when VK_QUERY_RESULT_WAIT_BIT is used in combination with %VK_QUERY_RESULT_WITH_AVAILABILITY_BIT2. In this case, the returned availability status may? reflect the result of a previous use of the query unless the vkCmdResetQueryPool< command has been executed since the last use of the query.Note Applications canz double-buffer query pool usage, with a pool per frame, and reset queries at the end of the frame in which they are read.If VK_QUERY_RESULT_PARTIAL_BIT is set, VK_QUERY_RESULT_WAIT_BIT is not set, and the query s status is unavailable, an intermediate result value between zero and the final result value is written to pData for that query.VK_QUERY_RESULT_PARTIAL_BIT must not be used if the pool s  queryType is VK_QUERY_TYPE_TIMESTAMP.If %VK_QUERY_RESULT_WITH_AVAILABILITY_BIT is set, the final integer value written for each query is non-zero if the query s status was available or zero if the status was unavailable. When %VK_QUERY_RESULT_WITH_AVAILABILITY_BIT is used, implementations mustZ guarantee that if they return a non-zero availability value then the numerical results mustG be valid, assuming the results are not reset by a subsequent command.NoteSatisfying this guarantee mayp require careful ordering by the application, e.g. to read the availability status before reading the results. Valid Usage firstQuery must, be less than the number of queries in  queryPoolIf VK_QUERY_RESULT_64_BIT is not set in flags then pData and stride must be multiples of 4If VK_QUERY_RESULT_64_BIT is set in flags then pData and stride must be multiples of 8 The sum of  firstQuery and  queryCount must8 be less than or equal to the number of queries in  queryPooldataSize mustM be large enough to contain the result of each query, as described lhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#queries-operation-memorylayouthereIf the  queryType used to create  queryPool was VK_QUERY_TYPE_TIMESTAMP, flags must not contain VK_QUERY_RESULT_PARTIAL_BITValid Usage (Implicit)device must be a valid VkDevice handle queryPool must be a valid  VkQueryPool handlepData must# be a valid pointer to an array of dataSize bytesflags must be a valid combination of  valuesdataSize must be greater than 0 queryPool must6 have been created, allocated, or retrieved from device Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS  VK_NOT_READY ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_DEVICE_LOSTSee Also,  VkDeviceSize, , 0vkDestroyQueryPool - Destroy a query pool object Parametersdevice4 is the logical device that destroys the query pool. queryPool is the query pool to destroy. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. Valid Usage%All submitted commands that refer to  queryPool must have completed executionIf VkAllocationCallbacks were provided when  queryPool1 was created, a compatible set of callbacks must be provided hereIf no VkAllocationCallbacks were provided when  queryPool was created,  pAllocator must be NULLValid Usage (Implicit)device must be a valid VkDevice handleIf  queryPool is not ,  queryPool must be a valid  VkQueryPool handleIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structureIf  queryPool is a valid handle, it must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to  queryPool must be externally synchronizedSee Also, , 2vkCreateQueryPool - Create a new query pool object Parametersdevice3 is the logical device that creates the query pool. pCreateInfo) is a pointer to an instance of the VkQueryPoolCreateInfoT structure containing the number and type of queries to be managed by the pool. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. pQueryPool is a pointer to a  VkQueryPoolB handle in which the resulting query pool object is returned.Valid Usage (Implicit)device must be a valid VkDevice handle pCreateInfo must$ be a valid pointer to a valid VkQueryPoolCreateInfo structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structure pQueryPool must be a valid pointer to a  VkQueryPool handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, , , VK_QUERY_RESULT_PARTIAL_BIT9 specifies that returning partial results is acceptable.%VK_QUERY_RESULT_WITH_AVAILABILITY_BITA specifies that the availability status accompanies the results.VK_QUERY_RESULT_WAIT_BITl specifies that Vulkan will wait for each query s status to become available before retrieving its results.VK_QUERY_RESULT_64_BIT specifies the results will be written as an array of 64-bit unsigned integer values. If this bit is not set, the results will be written as an array of 32-bit unsigned integer values.VK_QUERY_TYPE_TIMESTAMP specifies a  `https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#queries-timestampstimestamp query.!VK_QUERY_TYPE_PIPELINE_STATISTICS specifies a  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#queries-pipestatspipeline statistics query.VK_QUERY_TYPE_OCCLUSION specifies an  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#queries-occlusionocclusion query.((GNone "-KSTbejk{\ ^VkPipelineCacheCreateInfo - Structure specifying parameters of a newly created pipeline cache Valid UsageIf initialDataSize is not 0, it must be equal to the size of  pInitialData, as returned by vkGetPipelineCacheData when  pInitialData was originally retrievedIf initialDataSize is not 0,  pInitialData must2 have been retrieved from a previous call to vkGetPipelineCacheDataValid Usage (Implicit)sType must be ,VK_STRUCTURE_TYPE_PIPELINE_CACHE_CREATE_INFOpNext must be NULLflags must be 0If initialDataSize is not 0,  pInitialData must( be a valid pointer to an array of initialDataSize bytesSee Also, ,  sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.flags is reserved for future use.initialDataSize is the number of bytes in  pInitialData. If initialDataSize5 is zero, the pipeline cache will initially be empty. pInitialData is a pointer to previously retrieved pipeline cache data. If the pipeline cache data is incompatible (as defined below) with the device, the pipeline cache will be initially empty. If initialDataSize is zero,  pInitialData is ignored.:VkPipelineCache - Opaque handle to a pipeline cache objectSee AlsoH, H,  ,  ,  , 'Dummy data to tag the  with4VkPipelineCacheCreateFlags - Reserved for future use DescriptionVkPipelineCacheCreateFlagsQ is a bitmask type for setting a mask, but is currently reserved for future use.See AlsoBvkMergePipelineCaches - Combine the data stores of pipeline caches Parametersdevice< is the logical device that owns the pipeline cache objects.dstCache@ is the handle of the pipeline cache to merge results into. srcCacheCount is the length of the  pSrcCaches array. pSrcCachesG is an array of pipeline cache handles, which will be merged into dstCache. The previous contents of dstCache# are included after the merge. DescriptionNoteVThe details of the merge operation are implementation dependent, but implementations shouldL merge the contents of the specified pipelines and prune duplicate entries. Valid UsagedstCache must( not appear in the list of source cachesValid Usage (Implicit)device must be a valid VkDevice handledstCache must be a valid VkPipelineCache handle pSrcCaches must( be a valid pointer to an array of  srcCacheCount valid VkPipelineCache handles srcCacheCount must be greater than 0dstCache must6 have been created, allocated, or retrieved from deviceEach element of  pSrcCaches must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to dstCache must be externally synchronized Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also,  AvkGetPipelineCacheData - Get the data store from a pipeline cache Parametersdevice4 is the logical device that owns the pipeline cache. pipelineCache- is the pipeline cache to retrieve data from. pDataSizef is a pointer to a value related to the amount of data in the pipeline cache, as described below.pData is either NULL or a pointer to a buffer. DescriptionIf pData is NULL), then the maximum size of the data that canA be retrieved from the pipeline cache, in bytes, is returned in  pDataSize. Otherwise,  pDataSize mustY point to a variable set by the user to the size of the buffer, in bytes, pointed to by pDataZ, and on return the variable is overwritten with the amount of data actually written to pData.If  pDataSize$ is less than the maximum size that can. be retrieved by the pipeline cache, at most  pDataSize bytes will be written to pData, and vkGetPipelineCacheData will return  VK_INCOMPLETE. Any data written to pData is valid and can be provided as the  pInitialData member of the VkPipelineCacheCreateInfo structure passed to vkCreatePipelineCache. Two calls to vkGetPipelineCacheData with the same parameters mustj retrieve the same data unless a command that modifies the contents of the cache is called between them. Applications can store the data retrieved from the pipeline cache, and use these data, possibly in a future run of the application, to populate new pipeline cache objects. The results of pipeline compiles, however, may depend on the vendor ID, device ID, driver version, and other details of the device. To enable applications to detect when previously retrieved data is incompatible with the device, the initial bytes written to pData must2 be a header consisting of the following members: Offset  Size A Meaning  0 ! 4  length in bytes of the entire pipeline cache header written as a stream of bytes, with the least significant byte first # 4 C 4 C a  value written as a stream of bytes, with the least significant byte first  8 2 4  a vendor ID equal to VkPhysicalDeviceProperties::vendorID written as a stream of bytes, with the least significant byte first  12 2 4  a device ID equal to VkPhysicalDeviceProperties::deviceID written as a stream of bytes, with the least significant byte first  16   VK_UUID_SIZE C a pipeline cache ID equal to VkPhysicalDeviceProperties::pipelineCacheUUID *Layout for pipeline cache header version $VK_PIPELINE_CACHE_HEADER_VERSION_ONEThe first four bytes encode the length of the entire pipeline cache header, in bytes. This value includes all fields in the header including the pipeline cache version field and the size of the length field.IThe next four bytes encode the pipeline cache version, as described for $. A consumer of the pipeline cache shouldG use the cache version to interpret the remainder of the cache header.If  pDataSizeR is less than what is necessary to store this header, nothing will be written to pData and zero will be written to  pDataSize.Valid Usage (Implicit)device must be a valid VkDevice handle pipelineCache must be a valid VkPipelineCache handle pDataSize must be a valid pointer to a size_t valueIf the value referenced by  pDataSize is not 0, and pData is not NULL, pData must( be a valid pointer to an array of  pDataSize bytes pipelineCache must6 have been created, allocated, or retrieved from device Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS  VK_INCOMPLETE ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also,  8vkDestroyPipelineCache - Destroy a pipeline cache object ParametersdeviceD is the logical device that destroys the pipeline cache object. pipelineCache0 is the handle of the pipeline cache to destroy. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. Valid UsageIf VkAllocationCallbacks were provided when  pipelineCache1 was created, a compatible set of callbacks must be provided hereIf no VkAllocationCallbacks were provided when  pipelineCache was created,  pAllocator must be NULLValid Usage (Implicit)device must be a valid VkDevice handleIf  pipelineCache is not ,  pipelineCache must be a valid VkPipelineCache handleIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structureIf  pipelineCache is a valid handle, it must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to  pipelineCache must be externally synchronizedSee Also, ,  4vkCreatePipelineCache - Creates a new pipeline cache ParametersdeviceC is the logical device that creates the pipeline cache object. pCreateInfo is a pointer to a VkPipelineCacheCreateInfoX structure that contains the initial parameters for the pipeline cache object. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter.pPipelineCache is a pointer to a VkPipelineCacheF handle in which the resulting pipeline cache object is returned. DescriptionNote Applications canS track and manage the total host memory size of a pipeline cache object using the  pAllocator. Applications canF limit the amount of data retrieved from a pipeline cache object in vkGetPipelineCacheData. Implementations shouldw not internally limit the total number of entries added to a pipeline cache object or the total host memory consumed.Once created, a pipeline cache can be passed to the vkCreateGraphicsPipelines and vkCreateComputePipelinesE commands. If the pipeline cache passed into these commands is not , the implementation will query it for possible reuse opportunities and update it with new content. The use of the pipeline cache object in these commands is internally synchronized, and the same pipeline cache object can- be used in multiple threads simultaneously.NoteImplementations should make every effort to limit any critical sections to the actual accesses to the cache, which is expected to be significantly shorter than the duration of the vkCreateGraphicsPipelines and vkCreateComputePipelines commands.Valid Usage (Implicit)device must be a valid VkDevice handle pCreateInfo must$ be a valid pointer to a valid VkPipelineCacheCreateInfo structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structurepPipelineCache must be a valid pointer to a VkPipelineCache handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, , ,       HNone "-KSTbejk2VkSampleMask - Mask of sample coverage informationSee Alsoa/VkCullModeFlags - Bitmask of VkCullModeFlagBits DescriptionVkCullModeFlags7 is a bitmask type for setting a mask of zero or more .See Also, l;VkColorComponentFlags - Bitmask of VkColorComponentFlagBits DescriptionVkColorComponentFlags7 is a bitmask type for setting a mask of zero or more .See Also, W;VkPipelineCreateFlags - Bitmask of VkPipelineCreateFlagBits DescriptionVkPipelineCreateFlags7 is a bitmask type for setting a mask of zero or more .See Also, , dVkGraphicsPipelineCreateInfo - Structure specifying parameters of a newly created graphics pipeline DescriptionThe parameters basePipelineHandle and basePipelineIndex" are described in more detail in  lhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#pipelines-pipeline-derivativesPipeline Derivatives.pStages points to an array of 1 structures, which were previously described in  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#pipelines-computeCompute Pipelines. pDynamicState points to a structure of type F.eIf any shader stage fails to compile, the compile log will be reported back to the application, and VK_ERROR_INVALID_SHADER_NV will be generated. Valid UsageIf flags contains the !VK_PIPELINE_CREATE_DERIVATIVE_BIT flag, and basePipelineIndex is -1, basePipelineHandle must& be a valid handle to a graphics  VkPipeline3If flags contains the !VK_PIPELINE_CREATE_DERIVATIVE_BIT flag, and basePipelineHandle is , basePipelineIndex must2 be a valid index into the calling command s  pCreateInfos parameterIf flags contains the !VK_PIPELINE_CREATE_DERIVATIVE_BIT flag, and basePipelineIndex is not -1, basePipelineHandle must be If flags contains the !VK_PIPELINE_CREATE_DERIVATIVE_BIT flag, and basePipelineHandle is not , basePipelineIndex must be -1The stage member of each element of pStages must be uniqueThe stage member of one element of pStages must be VK_SHADER_STAGE_VERTEX_BITThe stage member of each element of pStages must not be VK_SHADER_STAGE_COMPUTE_BITIf pStages2 includes a tessellation control shader stage, it must4 include a tessellation evaluation shader stageIf pStages: includes a tessellation evaluation shader stage, it must, include a tessellation control shader stageIf pStages_ includes a tessellation control shader stage and a tessellation evaluation shader stage, pTessellationState must$ be a valid pointer to a valid %VkPipelineTessellationStateCreateInfo structureIf pStagesQ includes tessellation shader stages, the shader code of at least one stage must contain an OpExecutionModeH instruction that specifies the type of subdivision in the pipelineIf pStagesY includes tessellation shader stages, and the shader code of both stages contain an OpExecutionModeO instruction that specifies the type of subdivision in the pipeline, they must, both specify the same subdivision modeIf pStagesQ includes tessellation shader stages, the shader code of at least one stage must contain an OpExecutionModeF instruction that specifies the output patch size in the pipelineIf pStagesR includes tessellation shader stages, and the shader code of both contain an OpExecutionModeJ instruction that specifies the out patch size in the pipeline, they must& both specify the same patch sizeIf pStages* includes tessellation shader stages, the topology member of pInputAssembly must be  VK_PRIMITIVE_TOPOLOGY_PATCH_LISTIf the topology member of pInputAssembly is  VK_PRIMITIVE_TOPOLOGY_PATCH_LIST, pStages must( include tessellation shader stagesIf pStagesm includes a geometry shader stage, and does not include any tessellation shader stages, its shader code must contain an OpExecutionModeF instruction that specifies an input primitive type that is  hhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#shaders-geometry-execution compatible/ with the primitive topology specified in pInputAssemblyIf pStagesf includes a geometry shader stage, and also includes tessellation shader stages, its shader code must contain an OpExecutionModeF instruction that specifies an input primitive type that is  hhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#shaders-geometry-execution compatibleP with the primitive topology that is output by the tessellation stagesIf pStages includes a fragment shader stage and a geometry shader stage, and the fragment shader code reads from an input variable that is decorated with  PrimitiveID%, then the geometry shader code must: write to a matching output variable, decorated with  PrimitiveID, in all execution pathsIf pStages8 includes a fragment shader stage, its shader code must< not read from any input attachment that is defined as VK_ATTACHMENT_UNUSED in subpass3The shader code for the entry points identified by pStages>, and the rest of the state identified by this structure must< adhere to the pipeline linking rules described in the  Xhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#interfacesShader Interfaces chapter%If rasterization is not disabled and subpass) uses a depth/stencil attachment in  renderPass that has a layout of /VK_IMAGE_LAYOUT_DEPTH_STENCIL_READ_ONLY_OPTIMAL or :VK_IMAGE_LAYOUT_DEPTH_READ_ONLY_STENCIL_ATTACHMENT_OPTIMAL in the VkAttachmentReference defined by subpass, the depthWriteEnable member of pDepthStencilState must be VK_FALSE%If rasterization is not disabled and subpass) uses a depth/stencil attachment in  renderPass that has a layout of /VK_IMAGE_LAYOUT_DEPTH_STENCIL_READ_ONLY_OPTIMAL or :VK_IMAGE_LAYOUT_DEPTH_ATTACHMENT_STENCIL_READ_ONLY_OPTIMAL in the VkAttachmentReference defined by subpass, the failOp, passOp and  depthFailOp members of each of the front and back members of pDepthStencilState must be VK_STENCIL_OP_KEEPIf rasterization is not disabled and the subpass uses color attachments, then for each color attachment in the subpass the  blendEnable1 member of the corresponding element of the  pAttachment member of pColorBlendState must be VK_FALSE if the formatZ of the attachment does not support color blend operations, as specified by the ,VK_FORMAT_FEATURE_COLOR_ATTACHMENT_BLEND_BIT flag in VkFormatProperties::linearTilingFeatures or VkFormatProperties::optimalTilingFeatures returned by #vkGetPhysicalDeviceFormatPropertiesRIf rasterization is not disabled and the subpass uses color attachments, the attachmentCount member of pColorBlendState must be equal to the colorAttachmentCount used to create subpassIf no element of the pDynamicStates member of  pDynamicState is VK_DYNAMIC_STATE_VIEWPORT, the  pViewports member of pViewportState must( be a valid pointer to an array of pViewportState:: viewportCount  VkViewport structuresIf no element of the pDynamicStates member of  pDynamicState is VK_DYNAMIC_STATE_SCISSOR, the  pScissors member of pViewportState must( be a valid pointer to an array of pViewportState:: scissorCount VkRect2D structuresEIf the wide lines feature is not enabled, and no element of the pDynamicStates member of  pDynamicState is VK_DYNAMIC_STATE_LINE_WIDTH, the  lineWidth member of pRasterizationState must be 1.0If the rasterizerDiscardEnable member of pRasterizationState is VK_FALSE, pViewportState must$ be a valid pointer to a valid !VkPipelineViewportStateCreateInfo structureIf the rasterizerDiscardEnable member of pRasterizationState is VK_FALSE, pMultisampleState must$ be a valid pointer to a valid $VkPipelineMultisampleStateCreateInfo structureIf the rasterizerDiscardEnable member of pRasterizationState is VK_FALSE, and subpass' uses a depth/stencil attachment, pDepthStencilState must$ be a valid pointer to a valid %VkPipelineDepthStencilStateCreateInfo structureIf the rasterizerDiscardEnable member of pRasterizationState is VK_FALSE, and subpass uses color attachments, pColorBlendState must$ be a valid pointer to a valid #VkPipelineColorBlendStateCreateInfo structureJIf the depth bias clamping feature is not enabled, no element of the pDynamicStates member of  pDynamicState is VK_DYNAMIC_STATE_DEPTH_BIAS , and the depthBiasEnable member of pRasterizationState is VK_TRUE, the depthBiasClamp member of pRasterizationState must be 0.0If the 4{html_spec_relative}#VK_EXT_depth_range_unrestricted5 extension is not enabled and no element of the pDynamicStates member of  pDynamicState is VK_DYNAMIC_STATE_DEPTH_BOUNDS, and the depthBoundsTestEnable member of pDepthStencilState is VK_TRUE, the minDepthBounds and maxDepthBounds members of pDepthStencilState must be between 0.0 and 1.0 , inclusiveIf no element of the pDynamicStates member of  pDynamicState is %VK_DYNAMIC_STATE_SAMPLE_LOCATIONS_EXT, and the sampleLocationsEnable member of a [ structure chained to the pNext chain of pMultisampleState is VK_TRUE, 0sampleLocationsInfo.sampleLocationGridSize.width must evenly divide [N::sampleLocationGridSize.width as returned by [ with a samples parameter equaling rasterizationSamplesIf no element of the pDynamicStates member of  pDynamicState is %VK_DYNAMIC_STATE_SAMPLE_LOCATIONS_EXT, and the sampleLocationsEnable member of a [ structure chained to the pNext chain of pMultisampleState is VK_TRUE, 1sampleLocationsInfo.sampleLocationGridSize.height must evenly divide [N::sampleLocationGridSize.height as returned by [ with a samples parameter equaling rasterizationSamplesIf no element of the pDynamicStates member of  pDynamicState is %VK_DYNAMIC_STATE_SAMPLE_LOCATIONS_EXT, and the sampleLocationsEnable member of a [ structure chained to the pNext chain of pMultisampleState is VK_TRUE, +sampleLocationsInfo.sampleLocationsPerPixel must equal rasterizationSamplesIf the sampleLocationsEnable member of a [ structure chained to the pNext chain of pMultisampleState is VK_TRUE, the fragment shader code must2 not statically use the extended instruction InterpolateAtSamplelayout must be  whttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-pipelinelayout-consistency consistent$ with all shaders specified in pStagesIf subpass< uses color and/or depth/stencil attachments, then the rasterizationSamples member of pMultisampleState mustI equal the maximum of the sample counts of those subpass attachmentsIf subpasss has a depth/stencil attachment and depth test, stencil test, or depth bounds test are enabled, then the rasterizationSamples member of pMultisampleState mustE be the same as the sample count of the depth/stencil attachmentIf subpass* has any color attachments, then the rasterizationSamples member of pMultisampleState mustU be greater than or equal to the sample count for those subpass attachmentsIf subpassH does not use any color and/or depth/stencil attachments, then the rasterizationSamples member of pMultisampleState must follow the rules for a fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#renderpass-noattachmentszero-attachment subpasssubpass must be a valid subpass within  renderPassIf the  renderPass has multiview enabled and subpass5 has more than one bit set in the view mask and multiviewTessellationShader is not enabled, then pStages must' not include tessellation shaders.If the  renderPass has multiview enabled and subpass5 has more than one bit set in the view mask and multiviewGeometryShader is not enabled, then pStages must not include a geometry shader.If the  renderPass has multiview enabled and subpassJ has more than one bit set in the view mask, shaders in the pipeline must not write to the Layer built-in outputIf the  renderPass) has multiview enabled, then all shaders must/ not include variables decorated with the Layer. built-in decoration in their interfaces.flags must not contain the  VK_PIPELINE_CREATE_DISPATCH_BASE flag.If pStagesZ includes a fragment shader stage and an input attachment was referenced by the  at  renderPass create time, its shader code must= not read from any aspect that was not specified in the  aspectMask of the corresponding  structure.The number of resources in layoutC accessible to each shader stage that is used by the pipeline must be less than or equal to VkPhysicalDeviceLimits::maxPerStageResourcesIf no element of the pDynamicStates member of  pDynamicState is &VK_DYNAMIC_STATE_VIEWPORT_W_SCALING_NV, and the viewportWScalingEnable member of a J structure, chained to the pNext chain of pViewportState , is VK_TRUE, the pViewportWScalings member of the J must" be a pointer to an array of J:: viewportCount valid J structuresValid Usage (Implicit)sType must be /VK_STRUCTURE_TYPE_GRAPHICS_PIPELINE_CREATE_INFO pNext must be NULL* or a pointer to a valid instance of ]zflags must be a valid combination of  valuespStages must# be a valid pointer to an array of  stageCount valid VkPipelineShaderStageCreateInfo structurespVertexInputState must$ be a valid pointer to a valid $VkPipelineVertexInputStateCreateInfo structurepInputAssemblyState must$ be a valid pointer to a valid &VkPipelineInputAssemblyStateCreateInfo structurepRasterizationState must$ be a valid pointer to a valid &VkPipelineRasterizationStateCreateInfo structureIf  pDynamicState is not NULL,  pDynamicState must$ be a valid pointer to a valid  VkPipelineDynamicStateCreateInfo structurelayout must be a valid VkPipelineLayout handle renderPass must be a valid  VkRenderPass handle stageCount must be greater than 0Each of basePipelineHandle, layout, and  renderPass that are valid handles must? have been created, allocated, or retrieved from the same VkDeviceSee Also, M, , /, F, , , a, l, , , , {, , ,  sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.flags is a bitmask of 0 specifying how the pipeline will be generated. stageCount! is the number of entries in the pStages array. pStages is an array of size  stageCount structures of type R describing the set of the shader stages to be included in the graphics pipeline.!pVertexInputState% is a pointer to an instance of the  structure."pInputAssemblyState% is a pointer to an instance of the F structure which determines input assembly behavior, as described in  Uhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#drawingDrawing Commands.#pTessellationState% is a pointer to an instance of the  structure, and is ignored if the pipeline does not include a tessellation control shader stage and tessellation evaluation shader stage.$pViewportState% is a pointer to an instance of the {G structure, and is ignored if the pipeline has rasterization disabled.%pRasterizationState% is a pointer to an instance of the l structure.&pMultisampleState% is a pointer to an instance of the a=, and is ignored if the pipeline has rasterization disabled.'pDepthStencilState% is a pointer to an instance of the / structure, and is ignored if the pipeline has rasterization disabled or if the subpass of the render pass the pipeline is created against does not use a depth/stencil attachment.(pColorBlendState% is a pointer to an instance of the M structure, and is ignored if the pipeline has rasterization disabled or if the subpass of the render pass the pipeline is created against does not use any color attachments.) pDynamicState is a pointer to FY and is used to indicate which properties of the pipeline state object are dynamic and can7 be changed independently of the pipeline state. This can be NULL>, which means no state in the pipeline is considered dynamic.*layouto is the description of binding locations used by both the pipeline and descriptor sets used with the pipeline.+ renderPassr is a handle to a render pass object describing the environment in which the pipeline will be used; the pipeline mustZ only be used with an instance of any render pass compatible with the one provided. See  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#renderpass-compatibilityRender Pass Compatibility for more information.,subpassR is the index of the subpass in the render pass where this pipeline will be used.-basePipelineHandle is a pipeline to derive from..basePipelineIndex is an index into the  pCreateInfos0 parameter to use as a pipeline to derive from./xVkPipelineDepthStencilStateCreateInfo - Structure specifying parameters of a newly created pipeline depth stencil state Valid UsageIf the  khttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-depthBoundsdepth bounds testing feature is not enabled, depthBoundsTestEnable must be VK_FALSEValid Usage (Implicit)sType must be :VK_STRUCTURE_TYPE_PIPELINE_DEPTH_STENCIL_STATE_CREATE_INFOpNext must be NULLflags must be 0depthCompareOp must be a valid   valuefront must be a valid VkStencilOpState structureback must be a valid VkStencilOpState structureSee AlsoVkBool32,  , , , =, 1sType is the type of this structure.2pNext is NULL1 or a pointer to an extension-specific structure.3flags is reserved for future use.4depthTestEnable controls whether  [https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fragops-depthdepth testing is enabled.5depthWriteEnable controls whether  ahttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fragops-depth-write depth writes are enabled when depthTestEnable is VK_TRUE). Depth writes are always disabled when depthTestEnable is VK_FALSE.6depthCompareOp( is the comparison operator used in the  [https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fragops-depth depth test.7depthBoundsTestEnable controls whether  Yhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fragops-dbtdepth bounds testing is enabled.8stencilTestEnable controls whether  ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fragops-stencilstencil testing is enabled.9front and back control the parameters of the  ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fragops-stencil stencil test.;minDepthBounds and maxDepthBounds) define the range of values used in the  Yhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fragops-dbtdepth bounds test.=?VkStencilOpState - Structure specifying stencil operation stateValid Usage (Implicit)failOp must be a valid  valuepassOp must be a valid  value depthFailOp must be a valid  value compareOp must be a valid   valueSee Also , /, ?failOp is a N value specifying the action performed on samples that fail the stencil test.@passOp is a ^ value specifying the action performed on samples that pass both the depth and stencil tests.A depthFailOp is a f value specifying the action performed on samples that pass the stencil test and fail the depth test.B compareOp is a  D value specifying the comparison operator used in the stencil test.C compareMask\ selects the bits of the unsigned integer stencil values participating in the stencil test.D writeMask| selects the bits of the unsigned integer stencil values updated by the stencil test in the stencil framebuffer attachment.E referenceP is an integer reference value that is used in the unsigned stencil comparison.FmVkPipelineDynamicStateCreateInfo - Structure specifying parameters of a newly created pipeline dynamic state Valid UsageEach element of pDynamicStates must be uniqueValid Usage (Implicit)sType must be 4VK_STRUCTURE_TYPE_PIPELINE_DYNAMIC_STATE_CREATE_INFOpNext must be NULLflags must be 0pDynamicStates must( be a valid pointer to an array of dynamicStateCount valid   valuesdynamicStateCount must be greater than 0See Also , , , HsType is the type of this structure.IpNext is NULL1 or a pointer to an extension-specific structure.Jflags is reserved for future use.KdynamicStateCount" is the number of elements in the pDynamicStates array.LpDynamicStates is an array of   values specifying which pieces of pipeline state will use the values from dynamic state commands rather than from pipeline state creation info.MtVkPipelineColorBlendStateCreateInfo - Structure specifying parameters of a newly created pipeline color blend state DescriptionEach element of the  pAttachments array is a W^ structure specifying per-target blending state for each individual color attachment. If the  phttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-independentBlendindependent blending- feature is not enabled on the device, all W elements in the  pAttachments array must be identical. Valid UsageIf the  phttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-independentBlendindependent blending. feature is not enabled, all elements of  pAttachments must be identicalIf the  ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-logicOplogic operations feature is not enabled,  logicOpEnable must be VK_FALSEIf  logicOpEnable is VK_TRUE, logicOp must be a valid  valueValid Usage (Implicit)sType must be 8VK_STRUCTURE_TYPE_PIPELINE_COLOR_BLEND_STATE_CREATE_INFOpNext must be NULL* or a pointer to a valid instance of uflags must be 0If attachmentCount is not 0,  pAttachments must( be a valid pointer to an array of attachmentCount valid #VkPipelineColorBlendAttachmentState structuresSee AlsoVkBool32, , , W, , OsType is the type of this structure.PpNext is NULL1 or a pointer to an extension-specific structure.Qflags is reserved for future use.R logicOpEnable controls whether to apply  ahttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#framebuffer-logicopLogical Operations.SlogicOp* selects which logical operation to apply.TattachmentCount is the number of #VkPipelineColorBlendAttachmentState elements in  pAttachments . This value must equal the colorAttachmentCount0 for the subpass in which this pipeline is used.U pAttachments8: is a pointer to array of per target attachment states.VblendConstants is an array of four values used as the R, G, B, and A components of the blend constant that are used in blending, depending on the  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#framebuffer-blendfactors blend factor.WcVkPipelineColorBlendAttachmentState - Structure specifying a pipeline color blend attachment state Valid UsageIf the  lhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-dualSrcBlenddual source blending feature is not enabled, srcColorBlendFactor must not be VK_BLEND_FACTOR_SRC1_COLOR, $VK_BLEND_FACTOR_ONE_MINUS_SRC1_COLOR, VK_BLEND_FACTOR_SRC1_ALPHA , or $VK_BLEND_FACTOR_ONE_MINUS_SRC1_ALPHAIf the  lhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-dualSrcBlenddual source blending feature is not enabled, dstColorBlendFactor must not be VK_BLEND_FACTOR_SRC1_COLOR, $VK_BLEND_FACTOR_ONE_MINUS_SRC1_COLOR, VK_BLEND_FACTOR_SRC1_ALPHA , or $VK_BLEND_FACTOR_ONE_MINUS_SRC1_ALPHAIf the  lhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-dualSrcBlenddual source blending feature is not enabled, srcAlphaBlendFactor must not be VK_BLEND_FACTOR_SRC1_COLOR, $VK_BLEND_FACTOR_ONE_MINUS_SRC1_COLOR, VK_BLEND_FACTOR_SRC1_ALPHA , or $VK_BLEND_FACTOR_ONE_MINUS_SRC1_ALPHAIf the  lhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-dualSrcBlenddual source blending feature is not enabled, dstAlphaBlendFactor must not be VK_BLEND_FACTOR_SRC1_COLOR, $VK_BLEND_FACTOR_ONE_MINUS_SRC1_COLOR, VK_BLEND_FACTOR_SRC1_ALPHA , or $VK_BLEND_FACTOR_ONE_MINUS_SRC1_ALPHA If either of  colorBlendOp or  alphaBlendOp is an  hhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#framebuffer-blend-advancedadvanced blend operation , then  colorBlendOp must equal  alphaBlendOpIf R::advancedBlendIndependentBlend is VK_FALSE and  colorBlendOp is an  hhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#framebuffer-blend-advancedadvanced blend operation , then  colorBlendOp must! be the same for all attachments.If R::advancedBlendIndependentBlend is VK_FALSE and  alphaBlendOp is an  hhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#framebuffer-blend-advancedadvanced blend operation , then  alphaBlendOp must! be the same for all attachments.If R::advancedBlendAllOperations is VK_FALSE, then  colorBlendOp must not be VK_BLEND_OP_ZERO_EXT, VK_BLEND_OP_SRC_EXT, VK_BLEND_OP_DST_EXT, VK_BLEND_OP_SRC_OVER_EXT, VK_BLEND_OP_DST_OVER_EXT, VK_BLEND_OP_SRC_IN_EXT, VK_BLEND_OP_DST_IN_EXT, VK_BLEND_OP_SRC_OUT_EXT, VK_BLEND_OP_DST_OUT_EXT, VK_BLEND_OP_SRC_ATOP_EXT, VK_BLEND_OP_DST_ATOP_EXT, VK_BLEND_OP_XOR_EXT, VK_BLEND_OP_INVERT_EXT, VK_BLEND_OP_INVERT_RGB_EXT, VK_BLEND_OP_LINEARDODGE_EXT, VK_BLEND_OP_LINEARBURN_EXT, VK_BLEND_OP_VIVIDLIGHT_EXT, VK_BLEND_OP_LINEARLIGHT_EXT, VK_BLEND_OP_PINLIGHT_EXT, VK_BLEND_OP_HARDMIX_EXT, VK_BLEND_OP_PLUS_EXT, VK_BLEND_OP_PLUS_CLAMPED_EXT, "VK_BLEND_OP_PLUS_CLAMPED_ALPHA_EXT, VK_BLEND_OP_PLUS_DARKER_EXT, VK_BLEND_OP_MINUS_EXT, VK_BLEND_OP_MINUS_CLAMPED_EXT, VK_BLEND_OP_CONTRAST_EXT, VK_BLEND_OP_INVERT_OVG_EXT, VK_BLEND_OP_RED_EXT, VK_BLEND_OP_GREEN_EXT , or VK_BLEND_OP_BLUE_EXTIf  colorBlendOp or  alphaBlendOp is an  hhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#framebuffer-blend-advancedadvanced blend operation, then ::colorAttachmentCount7 of the subpass this pipeline is compiled against must$ be less than or equal to R"::advancedBlendMaxColorAttachmentsValid Usage (Implicit)srcColorBlendFactor must be a valid   valuedstColorBlendFactor must be a valid   value colorBlendOp must be a valid   valuesrcAlphaBlendFactor must be a valid   valuedstAlphaBlendFactor must be a valid   value alphaBlendOp must be a valid   valuecolorWriteMask must be a valid combination of  valuesSee Also ,  , VkBool32, , MY blendEnable controls whether blending is enabled for the corresponding color attachment. If blending is not enabled, the source fragment s color for that attachment is passed through unmodified.ZsrcColorBlendFactorP selects which blend factor is used to determine the source factors (Sr,Sg,Sb).[dstColorBlendFactorU selects which blend factor is used to determine the destination factors (Dr,Dg,Db).\ colorBlendOpe selects which blend operation is used to calculate the RGB values to write to the color attachment.]srcAlphaBlendFactorG selects which blend factor is used to determine the source factor Sa.^dstAlphaBlendFactorL selects which blend factor is used to determine the destination factor Da._ alphaBlendOpf selects which blend operation is use to calculate the alpha values to write to the color attachment.`colorWriteMask is a bitmask of f specifying which of the R, G, B, and/or A components are enabled for writing, as described for the  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#framebuffer-color-write-maskColor Write Mask.auVkPipelineMultisampleStateCreateInfo - Structure specifying parameters of a newly created pipeline multisample state Valid UsageIf the  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-sampleRateShadingsample rate shading feature is not enabled, sampleShadingEnable must be VK_FALSEIf the  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-alphaToOnealpha to one feature is not enabled, alphaToOneEnable must be VK_FALSEminSampleShading must be in the range [0,1]-If the subpass has any color attachments and rasterizationSamples= is greater than the number of color samples, then sampleShadingEnable must be VK_FALSEValid Usage (Implicit)sType must be 8VK_STRUCTURE_TYPE_PIPELINE_MULTISAMPLE_STATE_CREATE_INFOEach pNext: member of any structure (including this one) in the pNext chain must be either NULL/ or a pointer to a valid instance of %w, $x, or [Each sType member in the pNext chain must be uniqueflags must be 0rasterizationSamples must be a valid  valueIf  pSampleMask is not NULL,  pSampleMask must- be a valid pointer to an array of 4\lceil{\mathit{rasterizationSamples} \over 32}\rceil  VkSampleMask valuesSee AlsoVkBool32, , , ,  VkSampleMask, csType is the type of this structure.dpNext is NULL1 or a pointer to an extension-specific structure.eflags is reserved for future use.frasterizationSamples is a C specifying the number of samples per pixel used in rasterization.gsampleShadingEnable can be used to enable  ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#primsrast-sampleshadingSample Shading.hminSampleShading4 specifies a minimum fraction of sample shading if sampleShadingEnable is set to VK_TRUE.i pSampleMask is a bitmask of static coverage information that is ANDed with the coverage information generated during rasterization, as described in  `https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fragops-samplemask Sample Mask.jalphaToCoverageEnable controls whether a temporary coverage value is generated based on the alpha component of the fragment s first color output as specified in the  Zhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fragops-covgMultisample Coverage section.kalphaToOneEnabler controls whether the alpha component of the fragment s first color output is replaced with one as described in  Zhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fragops-covgMultisample Coverage.lyVkPipelineRasterizationStateCreateInfo - Structure specifying parameters of a newly created pipeline rasterization state DescriptionThe application can also add a 1VkPipelineRasterizationStateRasterizationOrderAMD structure to the pNext chain of a &VkPipelineRasterizationStateCreateInfo structure. This structure enables selecting the rasterization order to use when rendering with the corresponding graphics pipeline as described in  \https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#primrast-orderRasterization Order. Valid UsageIf the  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-depthClampdepth clamping feature is not enabled, depthClampEnable must be VK_FALSEIf the  phttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-fillModeNonSolidnon-solid fill modes feature is not enabled,  polygonMode must be VK_POLYGON_MODE_FILL or !VK_POLYGON_MODE_FILL_RECTANGLE_NVIf the ){html_spec_relative}#VK_NV_fill_rectangle extension is not enabled,  polygonMode must not be !VK_POLYGON_MODE_FILL_RECTANGLE_NVValid Usage (Implicit)sType must be :VK_STRUCTURE_TYPE_PIPELINE_RASTERIZATION_STATE_CREATE_INFOEach pNext: member of any structure (including this one) in the pNext chain must be either NULL/ or a pointer to a valid instance of  or  Each sType member in the pNext chain must be uniqueflags must be 0 polygonMode must be a valid  valuecullMode must be a valid combination of  values frontFace must be a valid  valueSee AlsoVkBool32, , , , , , nsType is the type of this structure.opNext is NULL1 or a pointer to an extension-specific structure.pflags is reserved for future use.qdepthClampEnable controls whether to clamp the fragment s depth values instead of clipping primitives to the z planes of the frustum, as described in  ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vertexpostproc-clippingPrimitive Clipping.rrasterizerDiscardEnableW controls whether primitives are discarded immediately before the rasterization stage.s polygonMode% is the triangle rendering mode. See .tcullModeC is the triangle facing direction used for primitive culling. See .u frontFace is a P value specifying the front-facing triangle orientation to be used for culling.vdepthBiasEnable0 controls whether to bias fragment depth values.wdepthBiasConstantFactorQ is a scalar factor controlling the constant depth value added to each fragment.xdepthBiasClamp6 is the maximum (or minimum) depth bias of a fragment.ydepthBiasSlopeFactorN is a scalar factor applied to a fragment s slope in depth bias calculations.z lineWidth* is the width of rasterized line segments.{oVkPipelineViewportStateCreateInfo - Structure specifying parameters of a newly created pipeline viewport state Valid UsageIf the  mhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-multiViewportmultiple viewports feature is not enabled,  viewportCount must be 1If the  mhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-multiViewportmultiple viewports feature is not enabled,  scissorCount must be 1 viewportCount must be between 1 and VkPhysicalDeviceLimits:: maxViewports , inclusive scissorCount must be between 1 and VkPhysicalDeviceLimits:: maxViewports , inclusive scissorCount and  viewportCount must be identicalIf the viewportWScalingEnable member of a J structure chained to the pNext chain is VK_TRUE , the  viewportCount member of the J structure must be equal to  viewportCountValid Usage (Implicit)sType must be 5VK_STRUCTURE_TYPE_PIPELINE_VIEWPORT_STATE_CREATE_INFOEach pNext: member of any structure (including this one) in the pNext chain must be either NULL/ or a pointer to a valid instance of * or JEach sType member in the pNext chain must be uniqueflags must be 0 viewportCount must be greater than 0 scissorCount must be greater than 0See Also, , , , }sType is the type of this structure.~pNext is NULL1 or a pointer to an extension-specific structure.flags is reserved for future use. viewportCount1 is the number of viewports used by the pipeline. pViewports is a pointer to an array of j structures, defining the viewport transforms. If the viewport state is dynamic, this member is ignored. scissorCount is the number of  ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fragops-scissorscissors and must match the number of viewports. pScissors is a pointer to an array of VkRect2D structures which define the rectangular bounds of the scissor for the corresponding viewport. If the scissor state is dynamic, this member is ignored.wVkPipelineTessellationStateCreateInfo - Structure specifying parameters of a newly created pipeline tessellation state Valid UsagepatchControlPoints must5 be greater than zero and less than or equal to VkPhysicalDeviceLimits::maxTessellationPatchSizeValid Usage (Implicit)sType must be 9VK_STRUCTURE_TYPE_PIPELINE_TESSELLATION_STATE_CREATE_INFOpNext must be NULL* or a pointer to a valid instance of flags must be 0See Also, , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.flags is reserved for future use.patchControlPoints$ number of control points per patch.zVkPipelineInputAssemblyStateCreateInfo - Structure specifying parameters of a newly created pipeline input assembly state Description}Restarting the assembly of primitives discards the most recent index values if those elements formed an incomplete primitive, and restarts the primitive assembly using the subsequent indices, but only assembling the immediately following element through the end of the originally specified elements. The primitive restart index value comparison is performed before adding the  vertexOffset value to the index value. Valid UsageIf topology is  VK_PRIMITIVE_TOPOLOGY_POINT_LIST, VK_PRIMITIVE_TOPOLOGY_LINE_LIST, #VK_PRIMITIVE_TOPOLOGY_TRIANGLE_LIST, .VK_PRIMITIVE_TOPOLOGY_LINE_LIST_WITH_ADJACENCY, 2VK_PRIMITIVE_TOPOLOGY_TRIANGLE_LIST_WITH_ADJACENCY or  VK_PRIMITIVE_TOPOLOGY_PATCH_LIST, primitiveRestartEnable must be VK_FALSEIf the  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-geometryShadergeometry shaders feature is not enabled, topology must not be any of .VK_PRIMITIVE_TOPOLOGY_LINE_LIST_WITH_ADJACENCY, /VK_PRIMITIVE_TOPOLOGY_LINE_STRIP_WITH_ADJACENCY, 2VK_PRIMITIVE_TOPOLOGY_TRIANGLE_LIST_WITH_ADJACENCY or 3VK_PRIMITIVE_TOPOLOGY_TRIANGLE_STRIP_WITH_ADJACENCYIf the  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-tessellationShadertessellation shaders feature is not enabled, topology must not be  VK_PRIMITIVE_TOPOLOGY_PATCH_LISTValid Usage (Implicit)sType must be ;VK_STRUCTURE_TYPE_PIPELINE_INPUT_ASSEMBLY_STATE_CREATE_INFOpNext must be NULLflags must be 0topology must be a valid  valueSee AlsoVkBool32, , , , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.flags is reserved for future use.topology is a 6 defining the primitive topology, as described below.primitiveRestartEnable controls whether a special vertex index value is treated as restarting the assembly of primitives. This enable only applies to indexed draws ( and >), and the special index value is either 0xFFFFFFFF when the  indexType parameter of vkCmdBindIndexBuffer is equal to VK_INDEX_TYPE_UINT32, or 0xFFFF when  indexType is equal to VK_INDEX_TYPE_UINT16:. Primitive restart is not allowed for list  topologies.vVkPipelineVertexInputStateCreateInfo - Structure specifying parameters of a newly created pipeline vertex input state Valid UsagevertexBindingDescriptionCount must be less than or equal to VkPhysicalDeviceLimits::maxVertexInputBindingsvertexAttributeDescriptionCount must be less than or equal to VkPhysicalDeviceLimits::maxVertexInputAttributes For every binding# specified by each element of pVertexAttributeDescriptions, a VkVertexInputBindingDescription must exist in pVertexBindingDescriptions with the same value of bindingAll elements of pVertexBindingDescriptions must' describe distinct binding numbersAll elements of pVertexAttributeDescriptions must+ describe distinct attribute locationsValid Usage (Implicit)sType must be 9VK_STRUCTURE_TYPE_PIPELINE_VERTEX_INPUT_STATE_CREATE_INFOpNext must be NULL* or a pointer to a valid instance of flags must be 0If vertexBindingDescriptionCount is not 0, pVertexBindingDescriptions must( be a valid pointer to an array of vertexBindingDescriptionCount valid VkVertexInputBindingDescription structuresIf vertexAttributeDescriptionCount is not 0, pVertexAttributeDescriptions must( be a valid pointer to an array of vertexAttributeDescriptionCount valid !VkVertexInputAttributeDescription structuresSee Also, , , , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.flags is reserved for future use.vertexBindingDescriptionCount; is the number of vertex binding descriptions provided in pVertexBindingDescriptions.pVertexBindingDescriptions is a pointer to an array of VkVertexInputBindingDescription structures.vertexAttributeDescriptionCount= is the number of vertex attribute descriptions provided in pVertexAttributeDescriptions.pVertexAttributeDescriptions is a pointer to an array of !VkVertexInputAttributeDescription structures.\VkVertexInputAttributeDescription - Structure specifying vertex input attribute description Valid Usagelocation must be less than VkPhysicalDeviceLimits::maxVertexInputAttributesbinding must be less than VkPhysicalDeviceLimits::maxVertexInputBindingsoffset must be less than or equal to VkPhysicalDeviceLimits::maxVertexInputAttributeOffsetformat must@ be allowed as a vertex buffer format, as specified by the #VK_FORMAT_FEATURE_VERTEX_BUFFER_BIT flag in VkFormatProperties::bufferFeatures returned by #vkGetPhysicalDeviceFormatPropertiesValid Usage (Implicit)format must be a valid  valueSee Also, location: is the shader binding location number for this attribute.bindingA is the binding number which this attribute takes its data from.format3 is the size and type of the vertex attribute data.offsete is a byte offset of this attribute relative to the start of an element in the vertex input binding.XVkVertexInputBindingDescription - Structure specifying vertex input binding description Valid Usagebinding must be less than VkPhysicalDeviceLimits::maxVertexInputBindingsstride must be less than or equal to VkPhysicalDeviceLimits::maxVertexInputBindingStrideValid Usage (Implicit) inputRate must be a valid  valueSee Also, binding5 is the binding number that this structure describes.strideN is the distance in bytes between two consecutive elements within the buffer. inputRate is a s value specifying whether vertex attribute addressing is a function of the vertex index or of the instance index.bVkComputePipelineCreateInfo - Structure specifying parameters of a newly created compute pipeline DescriptionThe parameters basePipelineHandle and basePipelineIndex" are described in more detail in  lhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#pipelines-pipeline-derivativesPipeline Derivatives.stage points to a structure of type VkPipelineShaderStageCreateInfo. Valid UsageIf flags contains the !VK_PIPELINE_CREATE_DERIVATIVE_BIT flag, and basePipelineIndex is -1, basePipelineHandle must% be a valid handle to a compute  VkPipelineIf flags contains the !VK_PIPELINE_CREATE_DERIVATIVE_BIT flag, and basePipelineHandle is , basePipelineIndex must2 be a valid index into the calling command s  pCreateInfos parameterIf flags contains the !VK_PIPELINE_CREATE_DERIVATIVE_BIT flag, and basePipelineIndex is not -1, basePipelineHandle must be If flags contains the !VK_PIPELINE_CREATE_DERIVATIVE_BIT flag, and basePipelineHandle is not , basePipelineIndex must be -1The stage member of stage must be VK_SHADER_STAGE_COMPUTE_BIT2The shader code for the entry point identified by stage= and the rest of the state identified by this structure must< adhere to the pipeline linking rules described in the  Xhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#interfacesShader Interfaces chapterlayout must be  whttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-pipelinelayout-consistency consistent9 with the layout of the compute shader specified in stageThe number of resources in layout- accessible to the compute shader stage must be less than or equal to VkPhysicalDeviceLimits::maxPerStageResourcesValid Usage (Implicit)sType must be .VK_STRUCTURE_TYPE_COMPUTE_PIPELINE_CREATE_INFOpNext must be NULLflags must be a valid combination of  valuesstage must be a valid VkPipelineShaderStageCreateInfo structurelayout must be a valid VkPipelineLayout handleBoth of basePipelineHandle, and layout that are valid handles must? have been created, allocated, or retrieved from the same VkDeviceSee Also, , , , ,  sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.flags is a bitmask of 0 specifying how the pipeline will be generated.stage is a  describing the compute shader.layouto is the description of binding locations used by both the pipeline and descriptor sets used with the pipeline.basePipelineHandle is a pipeline to derive frombasePipelineIndex is an index into the  pCreateInfos/ parameter to use as a pipeline to derive fromkVkPipelineShaderStageCreateInfo - Structure specifying parameters of a newly created pipeline shader stage Valid UsageIf the  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-geometryShadergeometry shaders feature is not enabled, stage must not be VK_SHADER_STAGE_GEOMETRY_BITIf the  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-tessellationShadertessellation shaders feature is not enabled, stage must not be (VK_SHADER_STAGE_TESSELLATION_CONTROL_BIT or +VK_SHADER_STAGE_TESSELLATION_EVALUATION_BITstage must not be VK_SHADER_STAGE_ALL_GRAPHICS , or VK_SHADER_STAGE_ALLpName must be the name of an  OpEntryPoint in module+ with an execution model that matches stagedIf the identified entry point includes any variable in its interface that is declared with the  ClipDistance BuiltIn decoration, that variable must* not have an array size greater than VkPhysicalDeviceLimits::maxClipDistancesdIf the identified entry point includes any variable in its interface that is declared with the  CullDistance BuiltIn decoration, that variable must* not have an array size greater than VkPhysicalDeviceLimits::maxCullDistancesfIf the identified entry point includes any variables in its interface that are declared with the  ClipDistance or  CullDistance BuiltIn decoration, those variables must7 not have array sizes which sum to more than VkPhysicalDeviceLimits::maxCombinedClipAndCullDistancesdIf the identified entry point includes any variable in its interface that is declared with the  SampleMask BuiltIn decoration, that variable must* not have an array size greater than VkPhysicalDeviceLimits::maxSampleMaskWordsIf stage is VK_SHADER_STAGE_VERTEX_BIT", the identified entry point mustM not include any input variable in its interface that is decorated with  CullDistanceIf stage is (VK_SHADER_STAGE_TESSELLATION_CONTROL_BIT or +VK_SHADER_STAGE_TESSELLATION_EVALUATION_BIT-, and the identified entry point has an OpExecutionMode3 instruction that specifies a patch size with OutputVertices, the patch size must be greater than 0 and less than or equal to VkPhysicalDeviceLimits::maxTessellationPatchSizeIf stage is VK_SHADER_STAGE_GEOMETRY_BIT", the identified entry point must have an OpExecutionModeT instruction that specifies a maximum output vertex count that is greater than 0 and less than or equal to VkPhysicalDeviceLimits::maxGeometryOutputVerticesIf stage is VK_SHADER_STAGE_GEOMETRY_BIT", the identified entry point must have an OpExecutionModeJ instruction that specifies an invocation count that is greater than 0 and less than or equal to VkPhysicalDeviceLimits::maxGeometryShaderInvocationsIf stage is VK_SHADER_STAGE_GEOMETRY_BIT0, and the identified entry point writes to Layer for any primitive, it must write the same value to Layer& for all vertices of a given primitiveIf stage is VK_SHADER_STAGE_GEOMETRY_BIT0, and the identified entry point writes to  ViewportIndex for any primitive, it must write the same value to  ViewportIndex+ for all vertices of a given primitiveIf stage is VK_SHADER_STAGE_FRAGMENT_BIT", the identified entry point mustG not include any output variables in its interface decorated with  CullDistanceIf stage is VK_SHADER_STAGE_FRAGMENT_BIT0, and the identified entry point writes to  FragDepth in any execution path, it must write to  FragDepth in all execution pathsIf stage is VK_SHADER_STAGE_FRAGMENT_BIT0, and the identified entry point writes to FragStencilRefEXT in any execution path, it must write to FragStencilRefEXT in all execution pathsValid Usage (Implicit)sType must be 3VK_STRUCTURE_TYPE_PIPELINE_SHADER_STAGE_CREATE_INFOpNext must be NULLflags must be 0stage must be a valid  valuemodule must be a valid VkShaderModule handlepName must" be a null-terminated UTF-8 stringIf pSpecializationInfo is not NULL, pSpecializationInfo must$ be a valid pointer to a valid VkSpecializationInfo structureSee Also, , , , , , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.flags is reserved for future use.stage is a + value specifying a single pipeline stage.module is a VkShaderModule1 object that contains the shader for this stage.pNamen is a pointer to a null-terminated UTF-8 string specifying the entry point name of the shader for this stage.pSpecializationInfo is a pointer to , as described in  phttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#pipelines-specialization-constantsSpecialization Constants, and can be NULL.?VkSpecializationInfo - Structure specifying specialization info Description pMapEntries points to a structure of type . Valid UsageThe offset member of each element of  pMapEntries must be less than dataSizeThe size member of each element of  pMapEntries must be less than or equal to dataSize minus offsetIf  mapEntryCount is not 0,  pMapEntries must( be a valid pointer to an array of  mapEntryCount valid VkSpecializationMapEntry structuresValid Usage (Implicit)If dataSize is not 0, pData must( be a valid pointer to an array of dataSize bytesSee Also,  mapEntryCount! is the number of entries in the  pMapEntries array. pMapEntries is a pointer to an array of VkSpecializationMapEntry( which maps constant IDs to offsets in pData.dataSize is the byte size of the pData buffer.pData8 contains the actual constant values to specialize with.KVkSpecializationMapEntry - Structure specifying a specialization map entry DescriptionIf a  constantID| value is not a specialization constant ID used in the shader, that map entry does not affect the behavior of the pipeline. Valid UsageFor a  constantID4 specialization constant declared in a shader, size must match the byte size of the  constantID1. If the specialization constant is of type boolean, size must be the byte size of VkBool32See Also constantID4 is the ID of the specialization constant in SPIR-V.offsetZ is the byte offset of the specialization constant value within the supplied data buffer.sizeX is the byte size of the specialization constant value within the supplied data buffer.;VkRect2D - Structure specifying a two-dimensional subregionSee Also^, , , , , , ]z, {, , ], , offset is a ! specifying the rectangle offset.extent is a ! specifying the rectangle extent.,VkViewport - Structure specifying a viewport Description!The framebuffer depth coordinate zf mayx be represented using either a fixed-point or floating-point representation. However, a floating-point representation must be used if the depth/stencil attachment has a floating-point depth component. If an m-bit fixed-point representation is used, we assume that it represents each value \frac{k}{2^m - 1}b, where k " { 0, 1, & , 2m-1 }, as k (e.g. 1.0 is represented in binary as a string of all ones).TThe viewport parameters shown in the above equations are found from these values asox = x + width / 2oy = y + height / 2oz = minDepthpx = widthpy = heightpz = maxDepth - minDepth.The application can specify a negative term for height{, which has the effect of negating the y coordinate in clip space before performing the transform. When using a negative height, the application should also adjust the yo value to point to the lower left corner of the viewport instead of the upper left corner. Using the negative heightK allows the application to avoid having to negate the y component of the Position_ output from the last vertex processing stage in shaders that also target other graphics APIs.The width and height of the  shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-limits-maxViewportDimensions5implementation-dependent maximum viewport dimensions mustN be greater than or equal to the width and height of the largest image which can* be created and attached to a framebuffer.<The floating-point viewport bounds are represented with an  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-limits-viewportSubPixelBits#implementation-dependent precision. Valid Usagewidth must be greater than 0.0 width must be less than or equal to VkPhysicalDeviceLimits::maxViewportDimensions[0]The absolute value of height must be less than or equal to VkPhysicalDeviceLimits::maxViewportDimensions[1]x must be greater than or equal to viewportBoundsRange[0](x + width) must be less than or equal to viewportBoundsRange[1]y must be greater than or equal to viewportBoundsRange[0]y must be less than or equal to viewportBoundsRange[1](y + height) must" be greater than or equal to viewportBoundsRange[0](y + height) must be less than or equal to viewportBoundsRange[1]Unless 4{html_spec_relative}#VK_EXT_depth_range_unrestricted extension is enabled minDepth must be between 0.0 and 1.0, inclusiveUnless 4{html_spec_relative}#VK_EXT_depth_range_unrestricted extension is enabled maxDepth must be between 0.0 and 1.0, inclusiveSee Also{, x and y, are the viewport s upper left corner (x,y).width and height3 are the viewport s width and height, respectively.minDepth and maxDepth8 are the depth range for the viewport. It is valid for minDepth to be greater than or equal to maxDepth.:VkExtent2D - Structure specifying a two-dimensional extentSee AlsoX, X, X, X, [N, [j, , W, [, \, K, , gwidth is the width of the extent.height is the height of the extent.:VkOffset2D - Structure specifying a two-dimensional offsetSee AlsoX, , Wx is the x offset.y is the y offset.4VkRenderPass - Opaque handle to a render pass objectSee Also, &, , , , ), g(Dummy data to tag the  with<VkPipelineLayout - Opaque handle to a pipeline layout objectSee Also, , , , , , , , , b, b')Dummy data to tag the  with/VkPipeline - Opaque handle to a pipeline objectSee Also, , , ,  ,  ,  , cj*Dummy data to tag the  with9VkCullModeFlagBits - Bitmask controlling triangle culling DescriptionVK_CULL_MODE_NONE* specifies that no triangles are discardedVK_CULL_MODE_FRONT_BIT9 specifies that front-facing triangles are discardedVK_CULL_MODE_BACK_BIT8 specifies that back-facing triangles are discardedVK_CULL_MODE_FRONT_AND_BACK1 specifies that all triangles are discarded.[Following culling, fragments are produced for any triangles which have not been discarded.See Also_VkColorComponentFlagBits - Bitmask controlling which components are written to the framebuffer DescriptionVK_COLOR_COMPONENT_R_BIT specifies that the R value is written to the color attachment for the appropriate sample. Otherwise, the value in memory is unmodified.VK_COLOR_COMPONENT_G_BIT specifies that the G value is written to the color attachment for the appropriate sample. Otherwise, the value in memory is unmodified.VK_COLOR_COMPONENT_B_BIT specifies that the B value is written to the color attachment for the appropriate sample. Otherwise, the value in memory is unmodified.VK_COLOR_COMPONENT_A_BIT specifies that the A value is written to the color attachment for the appropriate sample. Otherwise, the value in memory is unmodified.UThe color write mask operation is applied regardless of whether blending is enabled.See AlsoHVkPipelineCreateFlagBits - Bitmask controlling how a pipeline is created Description+VK_PIPELINE_CREATE_DISABLE_OPTIMIZATION_BITQ specifies that the created pipeline will not be optimized. Using this flag may3 reduce the time taken to create the pipeline.(VK_PIPELINE_CREATE_ALLOW_DERIVATIVES_BIT specifies that the pipeline to be created is allowed to be the parent of a pipeline that will be created in a subsequent call to   or  .!VK_PIPELINE_CREATE_DERIVATIVE_BITh specifies that the pipeline to be created will be a child of a previously created parent pipeline.3VK_PIPELINE_CREATE_VIEW_INDEX_FROM_DEVICE_INDEX_BIT= specifies that any shader input variables decorated as  DeviceIndex; will be assigned values as if they were decorated as  ViewIndex. VK_PIPELINE_CREATE_DISPATCH_BASE( specifies that a compute pipeline can be used with % with a non-zero base workgroup.It is valid to set both (VK_PIPELINE_CREATE_ALLOW_DERIVATIVES_BIT and !VK_PIPELINE_CREATE_DERIVATIVE_BIT`. This allows a pipeline to be both a parent and possibly a child in a pipeline hierarchy. See  lhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#pipelines-pipeline-derivativesPipeline Derivatives for more information.See Also;VkShaderStageFlagBits - Bitmask specifying a pipeline stageSee Also, b, cj:VkPipelineShaderStageCreateFlags - Reserved for future use Description VkPipelineShaderStageCreateFlagsQ is a bitmask type for setting a mask, but is currently reserved for future use.See Also?VkPipelineVertexInputStateCreateFlags - Reserved for future use Description%VkPipelineVertexInputStateCreateFlagsQ is a bitmask type for setting a mask, but is currently reserved for future use.See AlsoAVkPipelineInputAssemblyStateCreateFlags - Reserved for future use Description'VkPipelineInputAssemblyStateCreateFlagsQ is a bitmask type for setting a mask, but is currently reserved for future use.See Also@VkPipelineTessellationStateCreateFlags - Reserved for future use Description&VkPipelineTessellationStateCreateFlagsQ is a bitmask type for setting a mask, but is currently reserved for future use.See Also<VkPipelineViewportStateCreateFlags - Reserved for future use Description"VkPipelineViewportStateCreateFlagsQ is a bitmask type for setting a mask, but is currently reserved for future use.See Also{AVkPipelineRasterizationStateCreateFlags - Reserved for future use Description'VkPipelineRasterizationStateCreateFlagsQ is a bitmask type for setting a mask, but is currently reserved for future use.See Alsol?VkPipelineMultisampleStateCreateFlags - Reserved for future use Description%VkPipelineMultisampleStateCreateFlagsQ is a bitmask type for setting a mask, but is currently reserved for future use.See Alsoa>VkPipelineColorBlendStateCreateFlags - Reserved for future use Description$VkPipelineColorBlendStateCreateFlagsQ is a bitmask type for setting a mask, but is currently reserved for future use.See AlsoM;VkPipelineDynamicStateCreateFlags - Reserved for future use Description!VkPipelineDynamicStateCreateFlagsQ is a bitmask type for setting a mask, but is currently reserved for future use.See AlsoF@VkPipelineDepthStencilStateCreateFlags - Reserved for future use Description&VkPipelineDepthStencilStateCreateFlagsQ is a bitmask type for setting a mask, but is currently reserved for future use.See Also/TVkVertexInputRate - Specify rate at which vertex attributes are pulled from buffersSee Also)VkStencilOp - Stencil comparison function DescriptionVK_STENCIL_OP_KEEP keeps the current value.VK_STENCIL_OP_ZERO sets the value to 0.VK_STENCIL_OP_REPLACE sets the value to  reference.!VK_STENCIL_OP_INCREMENT_AND_CLAMPZ increments the current value and clamps to the maximum representable unsigned value.!VK_STENCIL_OP_DECREMENT_AND_CLAMP3 decrements the current value and clamps to 0.VK_STENCIL_OP_INVERT# bitwise-inverts the current value. VK_STENCIL_OP_INCREMENT_AND_WRAPb increments the current value and wraps to 0 when the maximum value would have been exceeded. VK_STENCIL_OP_DECREMENT_AND_WRAPk decrements the current value and wraps to the maximum possible value when the value would go below 0.aFor purposes of increment and decrement, the stencil bits are considered as an unsigned integer.If the stencil test fails, the sample s coverage bit is cleared in the fragment. If there is no stencil framebuffer attachment, stencil modification cannot7 occur, and it is as if the stencil tests always pass. If the stencil test passes, the  writeMask member of the =e structures controls how the updated stencil value is written to the stencil framebuffer attachment. The least significant s bits of  writeMask , where s is the number of bits in the stencil framebuffer attachment, specify an integer mask. Where a 1 appears in this mask, the corresponding bit in the stencil value in the depth/stencil attachment is written; where a 0 appears, the bit is not written. The  writeMask value uses either the front-facing or back-facing state based on the facingness of the fragment. Fragments generated by front-facing primitives use the front mask and fragments generated by back-facing primitives use the back mask.See Also=4VkPrimitiveTopology - Supported primitive topologiesSee Also*VkLogicOp - Framebuffer logical operations DescriptionZThe logical operations supported by Vulkan are summarized in the following table in which is bitwise invert,"' is bitwise and,"( is bitwise or," is bitwise exclusive or,s is the fragment s Rs0, Gs0, Bs0 or As0 component value for the fragment output corresponding to the color attachment being updated, and9d is the color attachment s R, G, B or A component value:# Mode # Operation  VK_LOGIC_OP_CLEAR # 0 | VK_LOGIC_OP_AND | s "' d | +-----------------------------------+-----------------------------------+ | VK_LOGIC_OP_AND_REVERSE} | s "' d | +-----------------------------------+-----------------------------------+ | VK_LOGIC_OP_COPY | s | +-----------------------------------+-----------------------------------+ | VK_LOGIC_OP_AND_INVERTED| | s "' d | +-----------------------------------+-----------------------------------+ | VK_LOGIC_OP_NO_OP | d | +-----------------------------------+-----------------------------------+ | VK_LOGIC_OP_XOR | s " d | +-----------------------------------+-----------------------------------+ | VK_LOGIC_OP_OR | s "( d | +-----------------------------------+-----------------------------------+ | VK_LOGIC_OP_NOR | (s "( d) | +-----------------------------------+-----------------------------------+ | VK_LOGIC_OP_EQUIVALENT~ | (s " d) | +-----------------------------------+-----------------------------------+ | VK_LOGIC_OP_INVERT | d | +-----------------------------------+-----------------------------------+ | VK_LOGIC_OP_OR_REVERSE~ | s "( d | +-----------------------------------+-----------------------------------+ | VK_LOGIC_OP_COPY_INVERTED{ | s | +-----------------------------------+-----------------------------------+ | VK_LOGIC_OP_OR_INVERTED} | s "( d | +-----------------------------------+-----------------------------------+ | VK_LOGIC_OP_NAND | (s "' d) | +-----------------------------------+-----------------------------------+ | VK_LOGIC_OP_SET | all 1s | +-----------------------------------+-----------------------------------+Logical OperationsThe result of the logical operation is then written to the color attachment as controlled by the component write mask, described in  ihttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#framebuffer-blendoperationsBlend Operations.See AlsoM8VkFrontFace - Interpret polygon front-facing orientation DescriptionVK_FRONT_FACE_COUNTER_CLOCKWISEN specifies that a triangle with positive area is considered front-facing.VK_FRONT_FACE_CLOCKWISEN specifies that a triangle with negative area is considered front-facing.VAny triangle which is not front-facing is back-facing, including zero-area triangles.See Alsol2VkPolygonMode - Control polygon rasterization mode DescriptionVK_POLYGON_MODE_POINT: specifies that polygon vertices are drawn as points.VK_POLYGON_MODE_LINE> specifies that polygon edges are drawn as line segments.VK_POLYGON_MODE_FILLa specifies that polygons are rendered using the polygon rasterization rules in this section.!VK_POLYGON_MODE_FILL_RECTANGLE_NV3 specifies that polygons are rendered using polygon rasterization rules, modified to consider a sample within the primitive if the sample location is inside the axis-aligned bounding box of the triangle after projection. Note that the barycentric weights used in attribute interpolation canY extend outside the range [0,1] when these primitives are shaded. Special treatment is given to a sample position on the boundary edge of the bounding box. In such a case, if two rectangles lie on either side of a common edge (with identical endpoints) on which a sample position lies, then exactly one of the triangles mustF produce a fragment that covers that sample during rasterization.Polygons rendered in !VK_POLYGON_MODE_FILL_RECTANGLE_NV mode mayv be clipped by the frustum or by user clip planes. If clipping is applied, the triangle is culled rather than clipped.3Area calculation and facingness are determined for !VK_POLYGON_MODE_FILL_RECTANGLE_NV$ mode using the triangle s vertices.These modes affect only the final rasterization of polygons: in particular, a polygon s vertices are shaded and the polygon is clipped and possibly culled before these modes are applied.See Alsol SVkDynamicState - Indicate which dynamic state is taken from dynamic state commandsSee AlsoF )VkCompareOp - Stencil comparison functionSee Also/, _, = +VkBlendOp - Framebuffer blending operations DescriptionNThe semantics of each basic blend operations is described in the table below:A VkBlendOp ) RGB Components ! Alpha Component | VK_BLEND_OP_ADD | R = Rs0 Sr + Rd | A = As0 Sa + | | | Dr | Ad Da | | | G = Gs0 Sg + Gd | | | | Dg | | | | B = Bs0 Sb + Bd | | | | Db | | +--------------------------------+--------------------+----------------+ | VK_BLEND_OP_SUBTRACT | R = Rs0 Sr - Rd | A = As0 Sa - | | | Dr | Ad Da | | | G = Gs0 Sg - Gd | | | | Dg | | | | B = Bs0 Sb - Bd | | | | Db | | +--------------------------------+--------------------+----------------+ | VK_BLEND_OP_REVERSE_SUBTRACT | R = Rd Dr - Rs0 | A = Ad Da - | | | Sr | As0 Sa | | | G = Gd Dg - Gs0 | | | | Sg | | | | B = Bd Db - Bs0 | | | | Sb | | +--------------------------------+--------------------+----------------+ | VK_BLEND_OP_MIN | R = min(Rs0,Rd) | A = | | | G = min(Gs0,Gd) | min(As0,Ad) | | | B = min(Bs0,Bd) | | +--------------------------------+--------------------+----------------+ | VK_BLEND_OP_MAX | R = max(Rs0,Rd) | A = | | | G = max(Gs0,Gd) | max(As0,Ad) | | | B = max(Bs0,Bd) | | +--------------------------------+--------------------+----------------+Basic Blend Operations2In this table, the following conventions are used:dRs0, Gs0, Bs0 and As0 represent the first source color R, G, B, and A components, respectively.Rd, Gd, Bd and Ad represent the R, G, B, and A components of the destination color. That is, the color currently in the corresponding color attachment for this fragment/sample.aSr, Sg, Sb and Sa represent the source blend factor R, G, B, and A components, respectively.fDr, Dg, Db and Da represent the destination blend factor R, G, B, and A components, respectively.The blending operation produces a new set of values R, G, B and A, which are written to the framebuffer attachment. If blending is not enabled for this attachment, then R, G, B and A are assigned Rs0, Gs0, Bs0 and As0, respectively.LIf the color attachment is fixed-point, the components of the source and destination values and blend factors are each clamped to [0,1] or [-1,1] respectively for an unsigned normalized or signed normalized color attachment prior to evaluating the blend operations. If the color attachment is floating-point, no clamping occurs.See AlsoW ,VkBlendFactor - Framebuffer blending factors DescriptionAThe semantics of each enum value is described in the table below: VkBlendFactor m RGB Blend Factors (Sr,Sg,Sb) or (Dr,Dg,Db) , Alpha Blend Factor (Sa or Da)  VK_BLEND_FACTOR_ZERO  (0,0,0)  0  VK_BLEND_FACTOR_ONE  (1,1,1)  1  VK_BLEND_FACTOR_SRC_COLOR  (Rs0,Gs0,Bs0)  As0  #VK_BLEND_FACTOR_ONE_MINUS_SRC_COLOR  (1-Rs0,1-Gs0,1-Bs0)  1-As0  VK_BLEND_FACTOR_DST_COLOR  (Rd,Gd,Bd)  Ad  #VK_BLEND_FACTOR_ONE_MINUS_DST_COLOR  (1-Rd,1-Gd,1-Bd)  1-Ad  VK_BLEND_FACTOR_SRC_ALPHA  (As0,As0,As0)  As0  #VK_BLEND_FACTOR_ONE_MINUS_SRC_ALPHA  (1-As0,1-As0,1-As0)  1-As0  VK_BLEND_FACTOR_DST_ALPHA  (Ad,Ad,Ad)  Ad  #VK_BLEND_FACTOR_ONE_MINUS_DST_ALPHA  (1-Ad,1-Ad,1-Ad)  1-Ad  VK_BLEND_FACTOR_CONSTANT_COLOR  (Rc,Gc,Bc)  Ac  (VK_BLEND_FACTOR_ONE_MINUS_CONSTANT_COLOR  (1-Rc,1-Gc,1-Bc)  1-Ac  VK_BLEND_FACTOR_CONSTANT_ALPHA  (Ac,Ac,Ac)  Ac  (VK_BLEND_FACTOR_ONE_MINUS_CONSTANT_ALPHA  (1-Ac,1-Ac,1-Ac)  1-Ac  "VK_BLEND_FACTOR_SRC_ALPHA_SATURATE4 + (f,f,f); f = min(As0,1-Ad)  1  VK_BLEND_FACTOR_SRC1_COLOR  (Rs1,Gs1,Bs1)  As1  $VK_BLEND_FACTOR_ONE_MINUS_SRC1_COLOR  (1-Rs1,1-Gs1,1-Bs1)  1-As1  VK_BLEND_FACTOR_SRC1_ALPHA  (As1,As1,As1)  As1  $VK_BLEND_FACTOR_ONE_MINUS_SRC1_ALPHA  (1-As1,1-As1,1-As1)  1-As1  Blend Factors2In this table, the following conventions are used:Rs0,Gs0,Bs0 and As0 represent the first source color R, G, B, and A components, respectively, for the fragment output location corresponding to the color attachment being blended.Rs1,Gs1,Bs1 and As1 represent the second source color R, G, B, and A components, respectively, used in dual source blending modes, for the fragment output location corresponding to the color attachment being blended.Rd,Gd,Bd and Ad represent the R, G, B, and A components of the destination color. That is, the color currently in the corresponding color attachment for this fragment/sample.ZRc,Gc,Bc and Ac represent the blend constant R, G, B, and A components, respectively.See AlsoW -vkDestroyPipeline - Destroy a pipeline object Parametersdevice2 is the logical device that destroys the pipeline.pipeline* is the handle of the pipeline to destroy. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. Valid Usage%All submitted commands that refer to pipeline must have completed executionIf VkAllocationCallbacks were provided when pipeline1 was created, a compatible set of callbacks must be provided hereIf no VkAllocationCallbacks were provided when pipeline was created,  pAllocator must be NULLValid Usage (Implicit)device must be a valid VkDevice handleIf pipeline is not , pipeline must be a valid  VkPipeline handleIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structureIf pipeline is a valid handle, it must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to pipeline must be externally synchronizedSee Also, ,  @vkCreateComputePipelines - Creates a new compute pipeline object Parametersdevice: is the logical device that creates the compute pipelines. pipelineCache is either N, indicating that pipeline caching is disabled; or the handle of a valid  ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#pipelines-cachepipeline cache^ object, in which case use of that cache is enabled for the duration of the command.createInfoCount is the length of the  pCreateInfos and  pPipelines arrays. pCreateInfos is an array of VkComputePipelineCreateInfo structures. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. pPipelines\ is a pointer to an array in which the resulting compute pipeline objects are returned. Valid UsageIf the flags member of any element of  pCreateInfos contains the !VK_PIPELINE_CREATE_DERIVATIVE_BIT flag, and the basePipelineIndex$ member of that same element is not -1, basePipelineIndex must" be less than the index into  pCreateInfos! that corresponds to that elementIf the flags member of any element of  pCreateInfos contains the !VK_PIPELINE_CREATE_DERIVATIVE_BIT flag, the base pipeline must& have been created with the (VK_PIPELINE_CREATE_ALLOW_DERIVATIVES_BIT flag setValid Usage (Implicit)device must be a valid VkDevice handleIf  pipelineCache is not ,  pipelineCache must be a valid VkPipelineCache handle pCreateInfos must( be a valid pointer to an array of createInfoCount valid VkComputePipelineCreateInfo structuresIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structure pPipelines must( be a valid pointer to an array of createInfoCount  VkPipeline handlescreateInfoCount must be greater than 0If  pipelineCache is a valid handle, it must6 have been created, allocated, or retrieved from device Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_INVALID_SHADER_NVSee Also, , , ,  5vkCreateGraphicsPipelines - Create graphics pipelines Parametersdevice; is the logical device that creates the graphics pipelines. pipelineCache is either N, indicating that pipeline caching is disabled; or the handle of a valid  ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#pipelines-cachepipeline cache^ object, in which case use of that cache is enabled for the duration of the command.createInfoCount is the length of the  pCreateInfos and  pPipelines arrays. pCreateInfos is an array of VkGraphicsPipelineCreateInfo structures. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. pPipelines] is a pointer to an array in which the resulting graphics pipeline objects are returned. DescriptionThe  structure includes an array of shader create info structures containing all the desired active shader stages, as well as creation info to define all relevant fixed-function stages, and a pipeline layout. Valid UsageIf the flags member of any element of  pCreateInfos contains the !VK_PIPELINE_CREATE_DERIVATIVE_BIT flag, and the basePipelineIndex$ member of that same element is not -1, basePipelineIndex must" be less than the index into  pCreateInfos! that corresponds to that elementIf the flags member of any element of  pCreateInfos contains the !VK_PIPELINE_CREATE_DERIVATIVE_BIT flag, the base pipeline must& have been created with the (VK_PIPELINE_CREATE_ALLOW_DERIVATIVES_BIT flag setValid Usage (Implicit)device must be a valid VkDevice handleIf  pipelineCache is not ,  pipelineCache must be a valid VkPipelineCache handle pCreateInfos must( be a valid pointer to an array of createInfoCount valid VkGraphicsPipelineCreateInfo structuresIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structure pPipelines must( be a valid pointer to an array of createInfoCount  VkPipeline handlescreateInfoCount must be greater than 0If  pipelineCache is a valid handle, it must6 have been created, allocated, or retrieved from device Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_INVALID_SHADER_NVSee Also, , , ,  VK_SHADER_STAGE_ALL is a combination of bits used as shorthand to specify all shader stages supported by the device, including all additional stages which are introduced by extensions. VK_SHADER_STAGE_ALL_GRAPHICSy is a combination of bits used as shorthand to specify all graphics stages defined above (excluding the compute stage). VK_SHADER_STAGE_COMPUTE_BIT specifies the compute stage. VK_SHADER_STAGE_FRAGMENT_BIT specifies the fragment stage. VK_SHADER_STAGE_GEOMETRY_BIT specifies the geometry stage. +VK_SHADER_STAGE_TESSELLATION_EVALUATION_BIT. specifies the tessellation evaluation stage. (VK_SHADER_STAGE_TESSELLATION_CONTROL_BIT+ specifies the tessellation control stage. VK_SHADER_STAGE_VERTEX_BIT specifies the vertex stage. VK_VERTEX_INPUT_RATE_INSTANCEQ specifies that vertex attribute addressing is a function of the instance index. VK_VERTEX_INPUT_RATE_VERTEXO specifies that vertex attribute addressing is a function of the vertex index. I"VK_DYNAMIC_STATE_STENCIL_REFERENCE specifies that the  reference state in %VkPipelineDepthStencilStateCreateInfo for both front and back will be ignored and must be set dynamically with = before any draws are performed with a pipeline state with %VkPipelineDepthStencilStateCreateInfo member stencilTestEnable set to VK_TRUE J#VK_DYNAMIC_STATE_STENCIL_WRITE_MASK specifies that the  writeMask state in %VkPipelineDepthStencilStateCreateInfo for both front and back will be ignored and must be set dynamically with = before any draws are performed with a pipeline state with %VkPipelineDepthStencilStateCreateInfo member stencilTestEnable set to VK_TRUE K%VK_DYNAMIC_STATE_STENCIL_COMPARE_MASK specifies that the  compareMask state in %VkPipelineDepthStencilStateCreateInfo for both front and back will be ignored and must be set dynamically with = before any draws are performed with a pipeline state with %VkPipelineDepthStencilStateCreateInfo member stencilTestEnable set to VK_TRUE LVK_DYNAMIC_STATE_DEPTH_BOUNDS specifies that the minDepthBounds and maxDepthBounds states of / will be ignored and must be set dynamically with = before any draws are performed with a pipeline state with %VkPipelineDepthStencilStateCreateInfo member depthBoundsTestEnable set to VK_TRUE. M VK_DYNAMIC_STATE_BLEND_CONSTANTS specifies that the blendConstants state in #VkPipelineColorBlendStateCreateInfo will be ignored and must be set dynamically with = before any draws are performed with a pipeline state with #VkPipelineColorBlendAttachmentState member  blendEnable set to VK_TRUE= and any of the blend functions using a constant blend color. NVK_DYNAMIC_STATE_DEPTH_BIAS specifies that the depthBiasConstantFactor, depthBiasClamp and depthBiasSlopeFactor states in &VkPipelineRasterizationStateCreateInfo will be ignored and must be set dynamically with & before any draws are performed with depthBiasEnable in &VkPipelineRasterizationStateCreateInfo set to VK_TRUE. OVK_DYNAMIC_STATE_LINE_WIDTH specifies that the  lineWidth state in &VkPipelineRasterizationStateCreateInfo will be ignored and must be set dynamically with L before any draw commands that generate line primitives for the rasterizer. PVK_DYNAMIC_STATE_SCISSOR specifies that the  pScissors state in !VkPipelineViewportStateCreateInfo will be ignored and must be set dynamically with k before any draw commands. The number of scissor rectangles used by a pipeline is still specified by the  scissorCount member of !VkPipelineViewportStateCreateInfo. QVK_DYNAMIC_STATE_VIEWPORT specifies that the  pViewports state in !VkPipelineViewportStateCreateInfo will be ignored and must be set dynamically with b before any draw commands. The number of viewports used by a pipeline is still specified by the  viewportCount member of !VkPipelineViewportStateCreateInfo. RVK_COMPARE_OP_ALWAYS' specifies that the test always passes. SVK_COMPARE_OP_GREATER_OR_EQUAL, specifies that the test passes when R "e S. TVK_COMPARE_OP_NOT_EQUAL+ specifies that the test passes when R "` S. UVK_COMPARE_OP_GREATER+ specifies that the test passes when R > S. VVK_COMPARE_OP_LESS_OR_EQUAL+ specifies that the test passes when R "d S. WVK_COMPARE_OP_EQUAL+ specifies that the test passes when R = S. XVK_COMPARE_OP_LESS+ specifies that the test passes when R < S. YVK_COMPARE_OP_NEVER& specifies that the test never passes.\*-. !"#$%&'()+,/0123456789:;<=>?@ABCDEFGHIJKLMNOPQSRTUVWXYZ[\]^_`abcdefghijklmnopxqrstuvwyz{|}~                           ! " # $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ \ ] ^ _ ` a b c d e f g h i j k l m n o p q\   q p o n m l k j i h g f e d c b a ` _   ^ ] \ [ Z   Y X W V U T S R   Q P O N M L K J I H G F E D C B A @ ? > = < ; : 9 8 7 6 5 4 3 2 1 0 / . - , + * ) ( ' & % $ # " !                    {|}~lmnopxqrstuvwyzabcdefghijkWXYZ[\]^_`MNOPQSRTUVFGHIJKL=>?@ABCDE/0123456789:;<*-. !"#$%&'()+,INoneejkJ H I J J I HJNone "-STbejk * KVkPipelineViewportWScalingStateCreateInfoNV - Structure specifying parameters of a newly created pipeline viewport W scaling stateValid Usage (Implicit)sType must be BVK_STRUCTURE_TYPE_PIPELINE_VIEWPORT_W_SCALING_STATE_CREATE_INFO_NV viewportCount must be greater than 0See AlsoVkBool32, ,  R MsType is the type of this structure. NpNext is NULL1 or a pointer to an extension-specific structure. OviewportWScalingEnable controls whether viewport W scaling is enabled. P viewportCount$ is the number of viewports used by W scaling, and must; match the number of viewports in the pipeline if viewport W scaling is enabled. QpViewportWScalings is a pointer to an array of VkViewportWScalingNV structures, which define the WE scaling parameters for the corresponding viewport. If the viewport W3 scaling state is dynamic, this member is ignored. R6VkViewportWScalingNV - Structure specifying a viewportSee Also K,  V Txcoeff and ycoeff? are the viewport s W scaling factor for x and y respectively. VLvkCmdSetViewportWScalingNV - Set the viewport W scaling on a command buffer Parameters commandBufferD is the command buffer into which the command will be recorded. firstViewportU is the index of the first viewport whose parameters are updated by the command. viewportCountM is the number of viewports whose parameters are updated by the command.pViewportWScalings" is a pointer to an array of  R+ structures specifying viewport parameters. Description0The viewport parameters taken from element i of pViewportWScalings3 replace the current state for the viewport index  firstViewport + i, for i in [0,  viewportCount). Valid UsageThe bound graphics pipeline must! have been created with the &VK_DYNAMIC_STATE_VIEWPORT_W_SCALING_NV dynamic state enabled firstViewport must be less than /:: maxViewports The sum of  firstViewport and  viewportCount must be between 1 and /:: maxViewports, inclusiveValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handlepViewportWScalings must( be a valid pointer to an array of  viewportCount VkViewportWScalingNV structures commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must! support graphics operations viewportCount must be greater than 0Host SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Both  Graphics  See Also,  R Z&VK_DYNAMIC_STATE_VIEWPORT_W_SCALING_NV specifies that the pViewportScalings state in +VkPipelineViewportWScalingStateCreateInfoNV will be ignored and must be set dynamically with  V= before any draws are performed with a pipeline state with )VkPipelineViewportWScalingStateCreateInfo member viewportScalingEnable set to VK_TRUE K L M N P O Q R S T U V W X Y Z Z Y X W V R S T U K L M N P O QKNone "-KSTbejk!8$ aEVkSurfaceTransformFlagsKHR - Bitmask of VkSurfaceTransformFlagBitsKHR DescriptionVkSurfaceTransformFlagsKHR7 is a bitmask type for setting a mask of zero or more  t.See AlsoX, \,  g,  t bAVkCompositeAlphaFlagsKHR - Bitmask of VkCompositeAlphaFlagBitsKHR DescriptionVkCompositeAlphaFlagsKHR7 is a bitmask type for setting a mask of zero or more  v.See Also v, \,  g cXVkSurfaceFormatKHR - Structure describing a supported swapchain format-color space pairSee Also z, , T,  } eformat is a 0 that is compatible with the specified surface. f colorSpace is a presentation  z& that is compatible with the surface. gJVkSurfaceCapabilitiesKHR - Structure describing capabilities of a surface DescriptionNote9Supported usage flags of a presentable image when using )VK_PRESENT_MODE_SHARED_DEMAND_REFRESH_KHR or -VK_PRESENT_MODE_SHARED_CONTINUOUS_REFRESH_KHR% presentation mode are provided by :: sharedPresentSupportedUsageFlags.NoteFormulas such as min(N,  maxImageCount) are not correct, since  maxImageCount may be zero.See Also b, , , T,  t,  a,  ~ i minImageCount is the minimum number of images the specified device supports for a swapchain created for the surface, and will be at least one. j maxImageCount is the maximum number of images the specified device supports for a swapchain created for the surface, and will be either 0, or greater than or equal to  minImageCountS. A value of 0 means that there is no limit on the number of images, though there mayM be limits related to the total amount of memory used by presentable images. k currentExtent is the current width and height of the surface, or the special value (0xFFFFFFFF, 0xFFFFFFFF) indicating that the surface size will be determined by the extent of a swapchain targeting the surface. lminImageExtent\ contains the smallest valid swapchain extent for the surface on the specified device. The width and heightE of the extent will each be less than or equal to the corresponding width and height of  currentExtent , unless  currentExtent( has the special value described above. mmaxImageExtent[ contains the largest valid swapchain extent for the surface on the specified device. The width and heightH of the extent will each be greater than or equal to the corresponding width and height of minImageExtent. The width and heightH of the extent will each be greater than or equal to the corresponding width and height of  currentExtent , unless  currentExtent( has the special value described above. nmaxImageArrayLayers5 is the maximum number of layers presentable images canU have for a swapchain created for this device and surface, and will be at least one. osupportedTransforms is a bitmask of  tz indicating the presentation transforms supported for the surface on the specified device. At least one bit will be set. pcurrentTransform is  tn value indicating the surface s current transform relative to the presentation engine s natural orientation. qsupportedCompositeAlpha is a bitmask of  v, representing the alpha compositing modes supported by the presentation engine for the surface on the specified device, and at least one bit will be set. Opaque composition can be achieved in any alpha compositing mode by either using an image format that has no alpha component, or by ensuring that all pixels in the presentable images have an alpha value of 1.0. rsupportedUsageFlags is a bitmask of /( representing the ways the application can9 use the presentable images of a swapchain created with  x set to VK_PRESENT_MODE_IMMEDIATE_KHR, VK_PRESENT_MODE_MAILBOX_KHR, VK_PRESENT_MODE_FIFO_KHR or  VK_PRESENT_MODE_FIFO_RELAXED_KHR+ for the surface on the specified device. #VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT must, be included in the set but implementations may support additional usages. s0VkSurfaceKHR - Opaque handle to a surface object DescriptionThe VK_KHR_surface extension declares the  VkSurfaceKHR1 object, and provides a function for destroying  VkSurfaceKHRY objects. Separate platform-specific extensions each provide a function for creating a  VkSurfaceKHR object for the respective platform. From the application s perspective this is an opaque handle, just like the handles of other Vulkan objects.See AlsoTq, , U, X, N, M, S, L, R, Q, P, O,  , P, , \,  ~,  },  |,  +Dummy data to tag the  with tNVkSurfaceTransformFlagBitsKHR - presentation transforms supported on a deviceSee AlsoX, \,  g,  a,  vLVkCompositeAlphaFlagBitsKHR - alpha compositing modes supported on a device Description&These values are described as follows:!VK_COMPOSITE_ALPHA_OPAQUE_BIT_KHR: The alpha channel, if it exists, of the images is ignored in the compositing process. Instead, the image is treated as if it has a constant alpha of 1.0.)VK_COMPOSITE_ALPHA_PRE_MULTIPLIED_BIT_KHR: The alpha channel, if it exists, of the images is respected in the compositing process. The non-alpha channels of the image are expected to already be multiplied by the alpha channel by the application.*VK_COMPOSITE_ALPHA_POST_MULTIPLIED_BIT_KHR\: The alpha channel, if it exists, of the images is respected in the compositing process. The non-alpha channels of the image are not expected to already be multiplied by the alpha channel by the application; instead, the compositor will multiply the non-alpha channels of the image by the alpha channel during compositing."VK_COMPOSITE_ALPHA_INHERIT_BIT_KHR: The way in which the presentation engine treats the alpha channel in the images is unknown to the Vulkan API. Instead, the application is responsible for setting the composite alpha blending mode using native window system commands. If the application does not set the blending mode using native window system commands, then a platform-specific default will be used.See Also b,  x<VkPresentModeKHR - presentation mode supported for a surface DescriptionVK_PRESENT_MODE_IMMEDIATE_KHR specifies that the presentation engine does not wait for a vertical blanking period to update the current image, meaning this mode may result in visible tearing. No internal queuing of presentation requests is needed, as the requests are applied immediately.VK_PRESENT_MODE_MAILBOX_KHR specifies that the presentation engine waits for the next vertical blanking period to update the current image. Tearing cannot be observed. An internal single-entry queue is used to hold pending presentation requests. If the queue is full when a new presentation request is received, the new request replaces the existing entry, and any images associated with the prior entry become available for re-use by the application. One request is removed from the queue and processed during each vertical blanking period in which the queue is non-empty.VK_PRESENT_MODE_FIFO_KHR specifies that the presentation engine waits for the next vertical blanking period to update the current image. Tearing cannotD be observed. An internal queue is used to hold pending presentation requests. New requests are appended to the end of the queue, and one request is removed from the beginning of the queue and processed during each vertical blanking period in which the queue is non-empty. This is the only value of  presentMode that is required to be supported. VK_PRESENT_MODE_FIFO_RELAXED_KHRb specifies that the presentation engine generally waits for the next vertical blanking period to update the current image. If a vertical blanking period has already passed since the last update of the current image then the presentation engine does not wait for another vertical blanking period for the update, meaning this mode mayX result in visible tearing in this case. This mode is useful for reducing visual stutter with an application that will mostly present a new image before the next vertical blanking period, but may occasionally be late, and present a new image just after the next vertical blanking period. An internal queue is used to hold pending presentation requests. New requests are appended to the end of the queue, and one request is removed from the beginning of the queue and processed during or after each vertical blanking period in which the queue is non-empty.)VK_PRESENT_MODE_SHARED_DEMAND_REFRESH_KHR specifies that the presentation engine and application have concurrent access to a single image, which is referred to as a shared presentable image. The presentation engine is only required to update the current image after a new presentation request is received. Therefore the application mustc make a presentation request whenever an update is required. However, the presentation engine may? update the current image at any point, meaning this mode may result in visible tearing.-VK_PRESENT_MODE_SHARED_CONTINUOUS_REFRESH_KHR specifies that the presentation engine and application have concurrent access to a single image, which is referred to as a shared presentable image. The presentation engine periodically updates the current image on its regular refresh cycle. The application is only required to make one initial presentation request, after which the presentation engine mustc update the current image without any need for further presentation requests. The application can indicate the image contents have been updated by making a presentation request, but this does not guarantee the timing of when it will be updated. This mode mayQ result in visible tearing if rendering to the image is not timed correctly.The supported /A of the presentable images of a swapchain created for a surface may[ differ depending on the presentation mode, and can be determined as per the table below:1 Presentation mode  Image usage flags  VK_PRESENT_MODE_IMMEDIATE_KHR   g::supportedUsageFlagsV  VK_PRESENT_MODE_MAILBOX_KHR   g::supportedUsageFlagsV  VK_PRESENT_MODE_FIFO_KHR   g::supportedUsageFlagsV   VK_PRESENT_MODE_FIFO_RELAXED_KHR   g::supportedUsageFlagsV  )VK_PRESENT_MODE_SHARED_DEMAND_REFRESH_KHR  :: sharedPresentSupportedUsageFlags  -VK_PRESENT_MODE_SHARED_CONTINUOUS_REFRESH_KHR  :: sharedPresentSupportedUsageFlags Presentable image usage queriesNote%For reference, the mode indicated by VK_PRESENT_MODE_FIFO_KHRu is equivalent to the behavior of {wgl|glX|egl}SwapBuffers with a swap interval of 1, while the mode indicated by  VK_PRESENT_MODE_FIFO_RELAXED_KHR is equivalent to the behavior of {wgl|glX}SwapBuffers with a swap interval of -1 (from the {WGL|GLX}_EXT_swap_control_tear extensions).See Also,  | zBVkColorSpaceKHR - supported color space of the presentation engine Description!VK_COLOR_SPACE_SRGB_NONLINEAR_KHR1 specifies support for the sRGB color space.'VK_COLOR_SPACE_DISPLAY_P3_NONLINEAR_EXTw specifies support for the Display-P3 color space and applies an sRGB-like transfer function (defined below).'VK_COLOR_SPACE_EXTENDED_SRGB_LINEAR_EXTa specifies support for the extended sRGB color space and applies a linear transfer function.*VK_COLOR_SPACE_EXTENDED_SRGB_NONLINEAR_EXT` specifies support for the extended sRGB color space and applies an sRGB transfer function. VK_COLOR_SPACE_DCI_P3_LINEAR_EXTM specifies support for the DCI-P3 color space and applies a linear OETF.#VK_COLOR_SPACE_DCI_P3_NONLINEAR_EXTR specifies support for the DCI-P3 color space and applies the Gamma 2.6 OETF.VK_COLOR_SPACE_BT709_LINEAR_EXTL specifies support for the BT709 color space and applies a linear OETF."VK_COLOR_SPACE_BT709_NONLINEAR_EXTR specifies support for the BT709 color space and applies the SMPTE 170M OETF. VK_COLOR_SPACE_BT2020_LINEAR_EXTM specifies support for the BT2020 color space and applies a linear OETF.VK_COLOR_SPACE_HDR10_ST2084_EXT| specifies support for the HDR10 (BT2020 color) space and applies the SMPTE ST2084 Perceptual Quantizer (PQ) OETF.VK_COLOR_SPACE_DOLBYVISION_EXT specifies support for the Dolby Vision (BT2020 color space), proprietary encoding, and applies the SMPTE ST2084 OETF.VK_COLOR_SPACE_HDR10_HLG_EXTg specifies support for the HDR10 (BT2020 color space) and applies the Hybrid Log Gamma (HLG) OETF."VK_COLOR_SPACE_ADOBERGB_LINEAR_EXTO specifies support for the AdobeRGB color space and applies a linear OETF.%VK_COLOR_SPACE_ADOBERGB_NONLINEAR_EXTT specifies support for the AdobeRGB color space and applies the Gamma 2.2 OETF.VK_COLOR_SPACE_PASS_THROUGH_EXT specifies that color components are used as is . This is intended to allow applications to supply data for color spaces not described here.!The color components of Non-linear color space swap chain images have had the appropriate transfer function applied. Vulkan requires that all implementations support the sRGB transfer function when using an SRGB pixel format. Other transfer functions, such as SMPTE 170M or SMPTE2084, must- not be performed by the implementation, but canL be performed by the application shader. This extension defines enums for  z/ that correspond to the following color spaces: Name  Red Primary  Green Primary  Blue Primary  White-point  Transfer function , DCI-P3  0.680, 0.320  0.265, 0.690  0.150, 0.060 ) 0.3127, 0.3290 (D65) & Gamma 2.6 , Display-P3  0.680, 0.320  0.265, 0.690  0.150, 0.060 ) 0.3127, 0.3290 (D65) & Display-P3 , BT709  0.640, 0.330  0.300, 0.600  0.150, 0.060 ) 0.3127, 0.3290 (D65) & SMPTE 170M , sRGB  0.640, 0.330  0.300, 0.600  0.150, 0.060 ) 0.3127, 0.3290 (D65) & sRGB , extended sRGB  0.640, 0.330  0.300, 0.600  0.150, 0.060 ) 0.3127, 0.3290 (D65) & extended sRGB , HDR10_ST2084  0.708, 0.292  0.170, 0.797  0.131, 0.046 ) 0.3127, 0.3290 (D65) & ST2084 , DOLBYVISION  0.708, 0.292  0.170, 0.797  0.131, 0.046 ) 0.3127, 0.3290 (D65) & ST2084 , HDR10_HLG  0.708, 0.292  0.170, 0.797  0.131, 0.046 ) 0.3127, 0.3290 (D65) & HLG , AdobeRGB  0.640, 0.330  0.210, 0.710  0.150, 0.060 ) 0.3127, 0.3290 (D65) & AdobeRGB Color Spaces and AttributespFor Opto-Electrical Transfer Function (OETF), unless otherwise specified, the values of L and E are defined as:L - linear luminance of image 0 \leq L \leq 1 for conventional colorimetry<E - corresponding electrical signal (value stored in memory)See Also c,  |OvkGetPhysicalDeviceSurfacePresentModesKHR - Query supported presentation modes ParametersphysicalDevicem is the physical device that will be associated with the swapchain to be created, as described for  .surface; is the surface that will be associated with the swapchain.pPresentModeCountv is a pointer to an integer related to the number of presentation modes available or queried, as described below. pPresentModes is either NULL" or a pointer to an array of  x: values, indicating the supported presentation modes. DescriptionIf  pPresentModes is NULLA, then the number of presentation modes supported for the given surface is returned in pPresentModeCount. Otherwise, pPresentModeCount mustG point to a variable set by the user to the number of elements in the  pPresentModesb array, and on return the variable is overwritten with the number of values actually written to  pPresentModes. If the value of pPresentModeCountD is less than the number of presentation modes supported, at most pPresentModeCount values will be written. If pPresentModeCountL is smaller than the number of presentation modes supported for the given surface,  VK_INCOMPLETE will be returned instead of  VK_SUCCESS> to indicate that not all the available values were returned.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handlesurface must be a valid  VkSurfaceKHR handlepPresentModeCount must be a valid pointer to a uint32_t valueIf the value referenced by pPresentModeCount is not 0 , and  pPresentModes is not NULL,  pPresentModes must( be a valid pointer to an array of pPresentModeCount  x valuesBoth of physicalDevice, and surface must? have been created, allocated, or retrieved from the same  VkInstance Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS  VK_INCOMPLETE ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_SURFACE_LOST_KHRSee Also,  x,  s }PvkGetPhysicalDeviceSurfaceFormatsKHR - Query color formats supported by surface ParametersphysicalDevicem is the physical device that will be associated with the swapchain to be created, as described for  .surface; is the surface that will be associated with the swapchain.pSurfaceFormatCountp is a pointer to an integer related to the number of format pairs available or queried, as described below.pSurfaceFormats is either NULL" or a pointer to an array of VkSurfaceFormatKHR structures. DescriptionIf pSurfaceFormats is NULL;, then the number of format pairs supported for the given surface is returned in pSurfaceFormatCountX. The number of format pairs supported will be greater than or equal to 1. Otherwise, pSurfaceFormatCount mustG point to a variable set by the user to the number of elements in the pSurfaceFormatsf array, and on return the variable is overwritten with the number of structures actually written to pSurfaceFormats. If the value of pSurfaceFormatCount= is less than the number of format pairs supported, at most pSurfaceFormatCount! structures will be written. If pSurfaceFormatCountE is smaller than the number of format pairs supported for the given surface,  VK_INCOMPLETE will be returned instead of  VK_SUCCESS> to indicate that not all the available values were returned.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handlesurface must be a valid  VkSurfaceKHR handlepSurfaceFormatCount must be a valid pointer to a uint32_t valueIf the value referenced by pSurfaceFormatCount is not 0 , and pSurfaceFormats is not NULL, pSurfaceFormats must( be a valid pointer to an array of pSurfaceFormatCount VkSurfaceFormatKHR structuresBoth of physicalDevice, and surface must? have been created, allocated, or retrieved from the same  VkInstance Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS  VK_INCOMPLETE ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_SURFACE_LOST_KHRSee Also,  c,  s ~FvkGetPhysicalDeviceSurfaceCapabilitiesKHR - Query surface capabilities ParametersphysicalDevicem is the physical device that will be associated with the swapchain to be created, as described for  .surface; is the surface that will be associated with the swapchain.pSurfaceCapabilities) is a pointer to an instance of the  g7 structure in which the capabilities are returned.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handlesurface must be a valid  VkSurfaceKHR handlepSurfaceCapabilities must be a valid pointer to a VkSurfaceCapabilitiesKHR structureBoth of physicalDevice, and surface must? have been created, allocated, or retrieved from the same  VkInstance Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_SURFACE_LOST_KHRSee Also,  g,  s JvkGetPhysicalDeviceSurfaceSupportKHR - Query if presentation is supported ParametersphysicalDevice is the physical device.queueFamilyIndex is the queue family.surface is the surface. pSupported is a pointer to a VkBool32, which is set to VK_TRUE to indicate support, and VK_FALSE otherwise. Valid UsagequeueFamilyIndex must be less than pQueueFamilyPropertyCount returned by (vkGetPhysicalDeviceQueueFamilyProperties for the given physicalDeviceValid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handlesurface must be a valid  VkSurfaceKHR handle pSupported must be a valid pointer to a VkBool32 valueBoth of physicalDevice, and surface must? have been created, allocated, or retrieved from the same  VkInstance Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_SURFACE_LOST_KHRSee AlsoVkBool32, ,  s 3vkDestroySurfaceKHR - Destroy a VkSurfaceKHR object Parametersinstance, is the instance used to create the surface.surface is the surface to destroy. pAllocator is the allocator used for host memory allocated for the surface object when there is no more specific allocator available (see  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation). Description Destroying a  VkSurfaceKHR merely severs the connection between Vulkan and the native surface, and does not imply destroying the native surface, closing a window, or similar behavior. Valid UsageAll VkSwapchainKHR objects created for surface must. have been destroyed prior to destroying surfaceIf VkAllocationCallbacks were provided when surface1 was created, a compatible set of callbacks must be provided hereIf no VkAllocationCallbacks were provided when surface was created,  pAllocator must be NULLValid Usage (Implicit)instance must be a valid  VkInstance handleIf surface is not , surface must be a valid  VkSurfaceKHR handleIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structureIf surface is a valid handle, it must6 have been created, allocated, or retrieved from instanceHost SynchronizationHost access to surface must be externally synchronizedSee Also, ,  s $VK_SURFACE_TRANSFORM_INHERIT_BIT_KHR specifies that the presentation transform is not specified, and is instead determined by platform-specific considerations and mechanisms outside Vulkan. 9VK_SURFACE_TRANSFORM_HORIZONTAL_MIRROR_ROTATE_270_BIT_KHR] specifies that image content is mirrored horizontally, then rotated 270 degrees clockwise. 9VK_SURFACE_TRANSFORM_HORIZONTAL_MIRROR_ROTATE_180_BIT_KHR] specifies that image content is mirrored horizontally, then rotated 180 degrees clockwise. 8VK_SURFACE_TRANSFORM_HORIZONTAL_MIRROR_ROTATE_90_BIT_KHR\ specifies that image content is mirrored horizontally, then rotated 90 degrees clockwise. .VK_SURFACE_TRANSFORM_HORIZONTAL_MIRROR_BIT_KHR8 specifies that image content is mirrored horizontally. 'VK_SURFACE_TRANSFORM_ROTATE_270_BIT_KHR@ specifies that image content is rotated 270 degrees clockwise. 'VK_SURFACE_TRANSFORM_ROTATE_180_BIT_KHR@ specifies that image content is rotated 180 degrees clockwise. &VK_SURFACE_TRANSFORM_ROTATE_90_BIT_KHR? specifies that image content is rotated 90 degrees clockwise. %VK_SURFACE_TRANSFORM_IDENTITY_BIT_KHRF specifies that image content is presented without being transformed.8 a b c d e f g h n i j k l m o p q r s t u v w x y z { | } ~  8 z { x y v w t u s  ~ } | g h n i j k l m o p q r c d e f b aLNone "-KSTbejk! _VkViSurfaceCreateInfoNN - Structure specifying parameters of a newly created VI surface object Valid Usagewindow must be a valid nn::vi::NativeWindowHandleValid Usage (Implicit)sType must be +VK_STRUCTURE_TYPE_VI_SURFACE_CREATE_INFO_NNpNext must be NULLflags must be 0See Also,  ,  sType is the type of this structure. pNext is NULL1 or a pointer to an extension-specific structure. flags is reserved for future use. window is the nn::vi::NativeWindowHandle for the nn::vi::Layer% with which to associate the surface.  vkCreateViSurfaceNN - Create a  s object for a VI layer Parametersinstance5 is the instance with which to associate the surface. pCreateInfo) is a pointer to an instance of the VkViSurfaceCreateInfoNNS structure containing parameters affecting the creation of the surface object. pAllocator is the allocator used for host memory allocated for the surface object when there is no more specific allocator available (see  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation).pSurface points to a  VkSurfaceKHR= handle in which the created surface object is returned. Description=During the lifetime of a surface created using a particular nn::vi::NativeWindowHandle6 any attempts to create another surface for the same nn::vi::Layer* and any attempts to connect to the same nn::vi::Layer@ through other platform mechanisms will have undefined results.The  currentExtentt of a VI surface is always undefined. Applications are expected to choose an appropriate size for the swapchain s  imageExtent1 (e.g., by matching the the result of a call to nn::vi::GetDisplayResolution).Valid Usage (Implicit)instance must be a valid  VkInstance handle pCreateInfo must$ be a valid pointer to a valid VkViSurfaceCreateInfoNN structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structurepSurface must be a valid pointer to a  VkSurfaceKHR handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY !VK_ERROR_NATIVE_WINDOW_IN_USE_KHRSee Also, ,  s,  MNone "-KSTbejk"R fVkMacOSSurfaceCreateInfoMVK - Structure specifying parameters of a newly created macOS surface object Valid UsagepView must be a valid NSView and must be backed by a CALayer instance of type  CAMetalLayer.Valid Usage (Implicit)sType must be /VK_STRUCTURE_TYPE_MACOS_SURFACE_CREATE_INFO_MVKpNext must be NULLflags must be 0See Also , ,  sType is the type of this structure. pNext is NULL1 or a pointer to an extension-specific structure. flags is reserved for future use. pView is a reference to a NSView/ object which will display this surface. This NSView must be backed by a CALayer instance of type  CAMetalLayer. JvkCreateMacOSSurfaceMVK - Create a VkSurfaceKHR object for a macOS NSView Parametersinstance5 is the instance with which to associate the surface. pCreateInfo) is a pointer to an instance of the  S structure containing parameters affecting the creation of the surface object. pAllocator is the allocator used for host memory allocated for the surface object when there is no more specific allocator available (see  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation).pSurface points to a  VkSurfaceKHR= handle in which the created surface object is returned.Valid Usage (Implicit)instance must be a valid  VkInstance handle pCreateInfo must$ be a valid pointer to a valid VkMacOSSurfaceCreateInfoMVK structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structurepSurface must be a valid pointer to a  VkSurfaceKHR handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY !VK_ERROR_NATIVE_WINDOW_IN_USE_KHRSee Also, ,  ,  s NNone "-KSTbejk"3 bVkIOSSurfaceCreateInfoMVK - Structure specifying parameters of a newly created iOS surface object Valid UsagepView must be a valid UIView and must be backed by a CALayer instance of type  CAMetalLayer.Valid Usage (Implicit)sType must be -VK_STRUCTURE_TYPE_IOS_SURFACE_CREATE_INFO_MVKpNext must be NULLflags must be 0See Also , ,  sType is the type of this structure. pNext is NULL1 or a pointer to an extension-specific structure. flags is reserved for future use. pView is a reference to a UIView/ object which will display this surface. This UIView must be backed by a CALayer instance of type  CAMetalLayer. FvkCreateIOSSurfaceMVK - Create a VkSurfaceKHR object for an iOS UIView Parametersinstance5 is the instance with which to associate the surface. pCreateInfo) is a pointer to an instance of the  S structure containing parameters affecting the creation of the surface object. pAllocator is the allocator used for host memory allocated for the surface object when there is no more specific allocator available (see  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation).pSurface points to a  VkSurfaceKHR= handle in which the created surface object is returned.Valid Usage (Implicit)instance must be a valid  VkInstance handle pCreateInfo must$ be a valid pointer to a valid VkIOSSurfaceCreateInfoMVK structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structurepSurface must be a valid pointer to a  VkSurfaceKHR handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY !VK_ERROR_NATIVE_WINDOW_IN_USE_KHRSee Also,  , ,  s ONone "-KSTbejk"_ dVkXlibSurfaceCreateInfoKHR - Structure specifying parameters of a newly created Xlib surface object Valid Usagedpy must point to a valid Xlib Display.window must be a valid Xlib Window.Valid Usage (Implicit)sType must be .VK_STRUCTURE_TYPE_XLIB_SURFACE_CREATE_INFO_KHRpNext must be NULLflags must be 0See Also,  ,   sType is the type of this structure. pNext is NULL1 or a pointer to an extension-specific structure. flags is reserved for future use. dpy is a pointer to an Xlib Display connection to the X server. window is an Xlib Window to associate the surface with. pvkGetPhysicalDeviceXlibPresentationSupportKHR - Query physical device for presentation to X11 server using Xlib ParametersphysicalDevice is the physical device.queueFamilyIndex is the queue family index.dpy is a pointer to an Xlib Display connection to the server.visualId is an X11 visual (VisualID). Description This platform-specific function can( be called prior to creating a surface. Valid UsagequeueFamilyIndex must be less than pQueueFamilyPropertyCount returned by (vkGetPhysicalDeviceQueueFamilyProperties for the given physicalDeviceValid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handledpy must be a valid pointer to a Display valueSee Also #vkCreateXlibSurfaceKHR - Create a  s> object for an X11 window, using the Xlib client-side library Parametersinstance/ is the instance to associate the surface with. pCreateInfo) is a pointer to an instance of the VkXlibSurfaceCreateInfoKHRW structure containing the parameters affecting the creation of the surface object. pAllocator is the allocator used for host memory allocated for the surface object when there is no more specific allocator available (see  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation).pSurface points to a  VkSurfaceKHR= handle in which the created surface object is returned.Valid Usage (Implicit)instance must be a valid  VkInstance handle pCreateInfo must$ be a valid pointer to a valid VkXlibSurfaceCreateInfoKHR structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structurepSurface must be a valid pointer to a  VkSurfaceKHR handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, ,  s,                    PNone "-KSTbejk" bVkXcbSurfaceCreateInfoKHR - Structure specifying parameters of a newly created Xcb surface object Valid Usage connection must point to a valid X11 xcb_connection_t.window must be a valid X11  xcb_window_t.Valid Usage (Implicit)sType must be -VK_STRUCTURE_TYPE_XCB_SURFACE_CREATE_INFO_KHRpNext must be NULLflags must be 0See Also,  ,  " sType is the type of this structure. pNext is NULL1 or a pointer to an extension-specific structure. flags is reserved for future use.  connection is a pointer to an xcb_connection_t to the X server. window is the  xcb_window_t3 for the X11 window to associate the surface with.  Opaque data !nvkGetPhysicalDeviceXcbPresentationSupportKHR - Query physical device for presentation to X11 server using XCB ParametersphysicalDevice is the physical device.queueFamilyIndex is the queue family index. connection is a pointer to an xcb_connection_t to the X server.  visual_id is an X11 visual (xcb_visualid_t). Description This platform-specific function can( be called prior to creating a surface. Valid UsagequeueFamilyIndex must be less than pQueueFamilyPropertyCount returned by (vkGetPhysicalDeviceQueueFamilyProperties for the given physicalDeviceValid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handle connection must be a valid pointer to a xcb_connection_t valueSee Also ""vkCreateXcbSurfaceKHR - Create a  s< object for a X11 window, using the XCB client-side library Parametersinstance/ is the instance to associate the surface with. pCreateInfo) is a pointer to an instance of the VkXcbSurfaceCreateInfoKHRS structure containing parameters affecting the creation of the surface object. pAllocator is the allocator used for host memory allocated for the surface object when there is no more specific allocator available (see  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation).pSurface points to a  VkSurfaceKHR= handle in which the created surface object is returned.Valid Usage (Implicit)instance must be a valid  VkInstance handle pCreateInfo must$ be a valid pointer to a valid VkXcbSurfaceCreateInfoKHR structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structurepSurface must be a valid pointer to a  VkSurfaceKHR handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, ,  s,              ! " # $ %     % $ # " !       QNone "-KSTbejk" 0fVkWin32SurfaceCreateInfoKHR - Structure specifying parameters of a newly created Win32 surface object Valid Usage hinstance must be a valid Win32  HINSTANCE.hwnd must be a valid Win32 HWND.Valid Usage (Implicit)sType must be /VK_STRUCTURE_TYPE_WIN32_SURFACE_CREATE_INFO_KHRpNext must be NULLflags must be 0See Also,  7,  < 2sType is the type of this structure. 3pNext is NULL1 or a pointer to an extension-specific structure. 4flags is reserved for future use. 5 hinstance and hwnd are the Win32  HINSTANCE and HWND/ for the window to associate the surface with. ;pvkGetPhysicalDeviceWin32PresentationSupportKHR - query queue family support for presentation on a Win32 display ParametersphysicalDevice is the physical device.queueFamilyIndex is the queue family index. Description This platform-specific function can( be called prior to creating a surface. Valid UsagequeueFamilyIndex must be less than pQueueFamilyPropertyCount returned by (vkGetPhysicalDeviceQueueFamilyProperties for the given physicalDeviceValid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handleSee Also <$vkCreateWin32SurfaceKHR - Create a  s# object for an Win32 native window Parametersinstance/ is the instance to associate the surface with. pCreateInfo) is a pointer to an instance of the VkWin32SurfaceCreateInfoKHRS structure containing parameters affecting the creation of the surface object. pAllocator is the allocator used for host memory allocated for the surface object when there is no more specific allocator available (see  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation).pSurface points to a  VkSurfaceKHR= handle in which the created surface object is returned.Valid Usage (Implicit)instance must be a valid  VkInstance handle pCreateInfo must$ be a valid pointer to a valid VkWin32SurfaceCreateInfoKHR structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structurepSurface must be a valid pointer to a  VkSurfaceKHR handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, ,  s,  0 0 1 2 3 4 5 6 7 8 9 : ; < = > ? : 9 7 8 ? > = < ; 0 1 2 3 4 5 6RNone "-KSTbejk" JjVkWaylandSurfaceCreateInfoKHR - Structure specifying parameters of a newly created Wayland surface object Valid Usagedisplay must point to a valid Wayland  wl_display.surface must point to a valid Wayland  wl_surface.Valid Usage (Implicit)sType must be 1VK_STRUCTURE_TYPE_WAYLAND_SURFACE_CREATE_INFO_KHRpNext must be NULLflags must be 0See Also,  Q,  V LsType is the type of this structure. MpNext is NULL1 or a pointer to an extension-specific structure. Nflags is reserved for future use. Odisplay and surface are pointers to the Wayland  wl_display and  wl_surface to associate the surface with. S Opaque data T Opaque data UevkGetPhysicalDeviceWaylandPresentationSupportKHR - Query physical device for presentation to Wayland ParametersphysicalDevice is the physical device.queueFamilyIndex is the queue family index.display is a pointer to the  wl_display+ associated with a Wayland compositor. Description This platform-specific function can( be called prior to creating a surface. Valid UsagequeueFamilyIndex must be less than pQueueFamilyPropertyCount returned by (vkGetPhysicalDeviceQueueFamilyProperties for the given physicalDeviceValid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handledisplay must be a valid pointer to a  wl_display valueSee Also V&vkCreateWaylandSurfaceKHR - Create a  s object for a Wayland window Parametersinstance/ is the instance to associate the surface with. pCreateInfo) is a pointer to an instance of the  JS structure containing parameters affecting the creation of the surface object. pAllocator is the allocator used for host memory allocated for the surface object when there is no more specific allocator available (see  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation).pSurface points to a  VkSurfaceKHR= handle in which the created surface object is returned.Valid Usage (Implicit)instance must be a valid  VkInstance handle pCreateInfo must$ be a valid pointer to a valid VkWaylandSurfaceCreateInfoKHR structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structurepSurface must be a valid pointer to a  VkSurfaceKHR handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, ,  s,  J J K L M N O P Q R S T U V W X Y T S Q R Y X W V U J K L M N O PSNone "-KSTbejk# dbVkMirSurfaceCreateInfoKHR - Structure specifying parameters of a newly created Mir surface object Valid Usage connection must point to a valid  MirConnection.surface must point to a valid  MirSurface.Valid Usage (Implicit)sType must be -VK_STRUCTURE_TYPE_MIR_SURFACE_CREATE_INFO_KHRpNext must be NULLflags must be 0See Also k, ,  p fsType is the type of this structure. gpNext is NULL1 or a pointer to an extension-specific structure. hflags is reserved for future use. i connection and surface are pointers to the  MirConnection and  MirSurface. for the window to associate the surface with. m Opaque data n Opaque data o]vkGetPhysicalDeviceMirPresentationSupportKHR - Query physical device for presentation to Mir ParametersphysicalDevice is the physical device.queueFamilyIndex is the queue family index. connection is a pointer to the  MirConnection1, and identifies the desired Mir compositor. Description This platform-specific function can( be called prior to creating a surface. Valid UsagequeueFamilyIndex must be less than pQueueFamilyPropertyCount returned by (vkGetPhysicalDeviceQueueFamilyProperties for the given physicalDeviceValid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handle connection must be a valid pointer to a  MirConnection valueSee Also p"vkCreateMirSurfaceKHR - Create a  s object for a Mir window Parametersinstance/ is the instance to associate the surface with. pCreateInfo) is a pointer to an instance of the  dS structure containing parameters affecting the creation of the surface object. pAllocator is the allocator used for host memory allocated for the surface object when there is no more specific allocator available (see  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation).pSurface points to a  VkSurfaceKHR= handle in which the created surface object is returned.Valid Usage (Implicit)instance must be a valid  VkInstance handle pCreateInfo must$ be a valid pointer to a valid VkMirSurfaceCreateInfoKHR structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structurepSurface must be a valid pointer to a  VkSurfaceKHR handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, ,  d,  s d e f g h i j k l m n o p q r s n m k l s r q p o d e f g h i jTNone "-STbejk#bN ~NVkSurfaceFormat2KHR - Structure describing a supported swapchain format tupleValid Usage (Implicit)sType must be &VK_STRUCTURE_TYPE_SURFACE_FORMAT_2_KHRpNext must be NULLSee Also,  c,  sType is the type of this structure. pNext is NULL1 or a pointer to an extension-specific structure.  surfaceFormat is an instance of  cV describing a format-color space pair that is compatible with the specified surface. KVkSurfaceCapabilities2KHR - Structure describing capabilities of a surfaceValid Usage (Implicit)sType must be ,VK_STRUCTURE_TYPE_SURFACE_CAPABILITIES_2_KHRpNext must be NULL* or a pointer to a valid instance of See Also,  g,  sType is the type of this structure. pNext is NULL1 or a pointer to an extension-specific structure. surfaceCapabilities is a structure of type  g7 describing the capabilities of the specified surface. kVkPhysicalDeviceSurfaceInfo2KHR - Structure specifying a surface and related swapchain creation parameters DescriptionThe members of VkPhysicalDeviceSurfaceInfo2KHR" correspond to the arguments to K, with sType and pNext added for extensibility.Valid Usage (Implicit)sType must be 4VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_SURFACE_INFO_2_KHRpNext must be NULLsurface must be a valid  VkSurfaceKHR handleSee Also,  s,  ,  sType is the type of this structure. pNext is NULL1 or a pointer to an extension-specific structure. surface; is the surface that will be associated with the swapchain. QvkGetPhysicalDeviceSurfaceFormats2KHR - Query color formats supported by surface ParametersphysicalDevicem is the physical device that will be associated with the swapchain to be created, as described for  . pSurfaceInfo# points to an instance of the  b structure, describing the surface and other fixed parameters that would be consumed by  .pSurfaceFormatCountq is a pointer to an integer related to the number of format tuples available or queried, as described below.pSurfaceFormats is either NULL" or a pointer to an array of  ~ structures. DescriptionIf pSurfaceFormats is NULL<, then the number of format tuples supported for the given surface is returned in pSurfaceFormatCountY. The number of format tuples supported will be greater than or equal to 1. Otherwise, pSurfaceFormatCount mustG point to a variable set by the user to the number of elements in the pSurfaceFormatsf array, and on return the variable is overwritten with the number of structures actually written to pSurfaceFormats. If the value of pSurfaceFormatCount> is less than the number of format tuples supported, at most pSurfaceFormatCount! structures will be written. If pSurfaceFormatCount` is smaller than the number of format tuples supported for the surface parameters described in  pSurfaceInfo,  VK_INCOMPLETE will be returned instead of  VK_SUCCESS> to indicate that not all the available values were returned.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handle pSurfaceInfo must$ be a valid pointer to a valid VkPhysicalDeviceSurfaceInfo2KHR structurepSurfaceFormatCount must be a valid pointer to a uint32_t valueIf the value referenced by pSurfaceFormatCount is not 0 , and pSurfaceFormats is not NULL, pSurfaceFormats must( be a valid pointer to an array of pSurfaceFormatCount VkSurfaceFormat2KHR structures Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS  VK_INCOMPLETE ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_SURFACE_LOST_KHRSee Also,  ,  ~ dvkGetPhysicalDeviceSurfaceCapabilities2KHR - Reports capabilities of a surface on a physical device ParametersphysicalDevicem is the physical device that will be associated with the swapchain to be created, as described for  . pSurfaceInfo# points to an instance of the  b structure, describing the surface and other fixed parameters that would be consumed by  .pSurfaceCapabilities# points to an instance of the  7 structure in which the capabilities are returned. Description*vkGetPhysicalDeviceSurfaceCapabilities2KHR behaves similarly to K, with the ability to specify extended inputs via chained input structures, and to return extended information via chained output structures.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handle pSurfaceInfo must$ be a valid pointer to a valid VkPhysicalDeviceSurfaceInfo2KHR structurepSurfaceCapabilities must be a valid pointer to a VkSurfaceCapabilities2KHR structure Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_SURFACE_LOST_KHRSee Also,  ,   ~   ~  UNone "-KSTbejk#- jVkAndroidSurfaceCreateInfoKHR - Structure specifying parameters of a newly created Android surface object Valid Usagewindow must point to a valid Android  ANativeWindow.Valid Usage (Implicit)sType must be 1VK_STRUCTURE_TYPE_ANDROID_SURFACE_CREATE_INFO_KHRpNext must be NULLflags must be 0See Also , ,  sType is the type of this structure. pNext is NULL1 or a pointer to an extension-specific structure. flags is reserved for future use. window is a pointer to the  ANativeWindow to associate the surface with.  Opaque data &vkCreateAndroidSurfaceKHR - Create a  s% object for an Android native window Parametersinstance/ is the instance to associate the surface with. pCreateInfo) is a pointer to an instance of the VkAndroidSurfaceCreateInfoKHRS structure containing parameters affecting the creation of the surface object. pAllocator is the allocator used for host memory allocated for the surface object when there is no more specific allocator available (see  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation).pSurface points to a  VkSurfaceKHR= handle in which the created surface object is returned. Description=During the lifetime of a surface created using a particular  ANativeWindow= handle any attempts to create another surface for the same  ANativeWindow* and any attempts to connect to the same  ANativeWindow- through other platform mechanisms will fail.NoteIn particular, only one  VkSurfaceKHR canA exist at a time for a given window. Similarly, a native window cannot be used by both a  VkSurfaceKHR and  EGLSurface simultaneously.If successful, vkCreateAndroidSurfaceKHR increments the  ANativeWindow s reference count, and vkDestroySurfaceKHR will decrement it.On Android, when a swapchain s  imageExtent does not match the surface s  currentExtentZ, the presentable images will be scaled to the surface s dimensions during presentation. minImageExtent is (1,1), and maxImageExtentR is the maximum image size supported by the consumer. For the system compositor,  currentExtent: is the window size (i.e. the consumer s preferred size).Valid Usage (Implicit)instance must be a valid  VkInstance handle pCreateInfo must$ be a valid pointer to a valid VkAndroidSurfaceCreateInfoKHR structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structurepSurface must be a valid pointer to a  VkSurfaceKHR handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY !VK_ERROR_NATIVE_WINDOW_IN_USE_KHRSee Also,  , ,  s VNoneejk#  WNone"bejk#V uVkRectLayerKHR - Structure containing a rectangle, including layer, changed by vkQueuePresentKHR for a given VkImage Valid Usage The sum of offset and extent must be no greater than the  imageExtent member of the VkSwapchainCreateInfoKHR structure given to  .layer must be less than imageArrayLayers member of the VkSwapchainCreateInfoKHR structure given to  .rSome platforms allow the size of a surface to change, and then scale the pixels of the image to fit the surface. VkRectLayerKHRf specifies pixels of the swapchain s image(s), which will be constant for the life of the swapchain.See Also, ,  offset+ is the origin of the rectangle, in pixels. extent) is the size of the rectangle, in pixels. layerJ is the layer of the image. For images with only one layer, the value of layer must be 0. nVkPresentRegionKHR - Structure containing rectangular region changed by vkQueuePresentKHR for a given VkImageValid Usage (Implicit)If rectangleCount is not 0, and  pRectangles is not NULL,  pRectangles must( be a valid pointer to an array of rectangleCount VkRectLayerKHR structuresSee Also ,  rectangleCount is the number of rectangles in  pRectanglesC, or zero if the entire image has changed and should be presented.  pRectangles is either NULL or a pointer to an array of VkRectLayerKHR structures. The VkRectLayerKHRr structure is the framebuffer coordinates, plus layer, of a portion of a presentable image that has changed and must be presented. If non-NULL, each entry in  pRectangleso is a rectangle of the given image that has changed since the last image was presented to the given swapchain. YVkPresentRegionsKHR - Structure hint of rectangular regions changed by vkQueuePresentKHR Valid UsageswapchainCount must be the same value as VkPresentInfoKHR::swapchainCount, where VkPresentInfoKHR$ is in the pNext-chain of this VkPresentRegionsKHR structure.Valid Usage (Implicit)sType must be %VK_STRUCTURE_TYPE_PRESENT_REGIONS_KHRIf pRegions is not NULL, pRegions must( be a valid pointer to an array of swapchainCount valid VkPresentRegionKHR structuresswapchainCount must be greater than 0See Also ,  sType is the type of this structure. pNext is NULL1 or a pointer to an extension-specific structure. swapchainCountA is the number of swapchains being presented to by this command. pRegions is NULL or a pointer to an array of VkPresentRegionKHR elements with swapchainCount entries. If not NULL, each element of pRegionsr contains the region that has changed since the last present to the swapchain in the corresponding entry in the VkPresentInfoKHR:: pSwapchains array.  XNone "-KSTbejk%6 GVkDisplayPlaneAlphaFlagsKHR - Bitmask of VkDisplayPlaneAlphaFlagBitsKHR DescriptionVkDisplayPlaneAlphaFlagsKHR7 is a bitmask type for setting a mask of zero or more  .See Also ,  pVkDisplaySurfaceCreateInfoKHR - Structure specifying parameters of a newly created display plane surface object DescriptionNoteCreating a display surface must] not modify the state of the displays, planes, or other resources it names. For example, it must not apply the specified mode to be set on the associated display. Application of display configuration occurs as a side effect of presenting to a display surface. Valid Usage planeIndex mustf be less than the number of display planes supported by the device as determined by calling ,vkGetPhysicalDeviceDisplayPlanePropertiesKHRIf the planeReorderPossible member of the VkDisplayPropertiesKHR structure returned by 'vkGetPhysicalDeviceDisplayPropertiesKHR' for the display corresponding to  displayMode is VK_TRUE then planeStackIndex mustf be less than the number of display planes supported by the device as determined by calling ,vkGetPhysicalDeviceDisplayPlanePropertiesKHR; otherwise planeStackIndex must equal the currentStackIndex member of VkDisplayPlanePropertiesKHR returned by ,vkGetPhysicalDeviceDisplayPlanePropertiesKHR- for the display plane corresponding to  displayModeIf  alphaMode is %VK_DISPLAY_PLANE_ALPHA_GLOBAL_BIT_KHR then  globalAlpha must be between 0 and 1 , inclusive alphaMode must be 0( or one of the bits present in the supportedAlpha member of VkDisplayPlaneCapabilitiesKHR returned by  vkGetDisplayPlaneCapabilitiesKHR- for the display plane corresponding to  displayModeThe width and height members of  imageExtent must be less than the maxImageDimensions2D member of VkPhysicalDeviceLimitsValid Usage (Implicit)sType must be 1VK_STRUCTURE_TYPE_DISPLAY_SURFACE_CREATE_INFO_KHRpNext must be NULLflags must be 0 displayMode must be a valid VkDisplayModeKHR handle transform must be a valid  t value alphaMode must be a valid   valueSee Also ,  ,  , , ,  t,   sType is the type of this structure. pNext is NULL1 or a pointer to an extension-specific structure. flags! is reserved for future use, and must be zero.  displayMode is a  A handle specifying the mode to use when displaying this surface.  planeIndex, is the plane on which this surface appears. planeStackIndex is the z-order of the plane.  transform is a  t[ value specifying the transformation to apply to images as part of the scanout operation.  globalAlpha6 is the global alpha value. This value is ignored if  alphaMode is not %VK_DISPLAY_PLANE_ALPHA_GLOBAL_BIT_KHR.  alphaMode is a  5 value specifying the type of alpha blending to use.  imageExtent= The size of the presentable images to use with the surface. bVkDisplayPlaneCapabilitiesKHR - Structure describing capabilities of a mode and plane combination DescriptionThe minimum and maximum position and extent fields describe the implementation limits, if any, as they apply to the specified display mode and plane. Vendors may support displaying a subset of a swapchain s presentable images on the specified display plane. This is expressed by returning minSrcPosition, maxSrcPosition,  minSrcExtent, and  maxSrcExtent? values that indicate a range of possible positions and sizes may be used to specify the region within the presentable images that source pixels will be read from when creating a swapchain on the specified display mode and plane.Vendors may also support mapping the presentable images  content to a subset or superset of the visible region in the specified display mode. This is expressed by returning minDstPosition, maxDstPosition,  minDstExtent and  maxDstExtent? values that indicate a range of possible positions and sizes mayb be used to describe the region within the display mode that the source pixels will be mapped to.Other vendors maya support only a 1-1 mapping between pixels in the presentable images and the display mode. This may& be indicated by returning (0,0) for minSrcPosition, maxSrcPosition, minDstPosition, and maxDstPosition5, and (display mode width, display mode height) for  minSrcExtent,  maxSrcExtent,  minDstExtent, and  maxDstExtent.These values indicate the limits of the implementation s individual fields. Not all combinations of values within the offset and extent ranges returned in VkDisplayPlaneCapabilitiesKHR* are guaranteed to be supported. Vendors mayI still fail presentation requests that specify unsupported combinations.See Also , , ,   supportedAlpha is a bitmask of  0 describing the supported alpha blending modes. minSrcPositionZ is the minimum source rectangle offset supported by this plane using the specified mode. maxSrcPosition_ is the maximum source rectangle offset supported by this plane using the specified mode. The x and y components of maxSrcPosition must& each be greater than or equal to the x and y components of minSrcPosition, respectively.  minSrcExtentX is the minimum source rectangle size supported by this plane using the specified mode.  maxSrcExtentX is the maximum source rectangle size supported by this plane using the specified mode. minDstPosition, maxDstPosition,  minDstExtent,  maxDstExtent4 all have similar semantics to their corresponding *Src* equivalents, but apply to the output region within the mode rather than the input region within the source image. Unlike the *Src* offsets, minDstPosition and maxDstPosition may contain negative values. dVkDisplayModeCreateInfoKHR - Structure specifying parameters of a newly created display mode object Valid UsageThe width and height members of the  visibleRegion member of  parameters must be greater than 0The  refreshRate member of  parameters must be greater than 0Valid Usage (Implicit)sType must be .VK_STRUCTURE_TYPE_DISPLAY_MODE_CREATE_INFO_KHRpNext must be NULLflags must be 0See Also ,  , ,   sType is the type of this structure. pNext is NULL1 or a pointer to an extension-specific structure. flags! is reserved for future use, and must be zero.  parameters is a VkDisplayModeParametersKHR structure describing the display parameters to use in creating the new mode. If the parameters are not compatible with the specified display, the implementation must return VK_ERROR_INITIALIZATION_FAILED. JVkDisplayModePropertiesKHR - Structure describing display mode propertiesSee Also ,  ,    displayMode is a handle to the display mode described in this structure. This handle will be valid for the lifetime of the Vulkan instance.  parameters is a VkDisplayModeParametersKHR> structure describing the display parameters associated with  displayMode. dVkDisplayModeParametersKHR - Structure describing display parameters associated with a display mode DescriptionNote0For example, a 60Hz display mode would report a  refreshRate of 60,000.See Also ,  ,   visibleRegion) is the 2D extents of the visible region.  refreshRate is a uint32_tV that is the number of times the display is refreshed each second multiplied by 1000. LVkDisplayPlanePropertiesKHR - Structure describing display plane propertiesSee Also ,   currentDisplay is the handle of the display the plane is currently associated with. If the plane is not currently attached to any displays, this will be VK_NULL_HANDLE. currentStackIndexY is the current z-order of the plane. This will be between 0 and the value returned by ,vkGetPhysicalDeviceDisplayPlanePropertiesKHR in pPropertyCount. JVkDisplayPropertiesKHR - Structure describing an available display device DescriptionNoteIFor devices which have no natural value to return here, implementations should) return the maximum resolution supported.supportedTransformsp tells which transforms are supported by this display. This will contain one or more of the bits from VkSurfaceTransformFlagsKHR.planeReorderPossible/ tells whether the planes on this display can( have their z order changed. If this is VK_TRUE, the application canP re-arrange the planes on this display in any order relative to each other.persistentContentp tells whether the display supports self-refresh/internal buffering. If this is true, the application canV submit persistent present operations on swapchains created against this display.NotePersistent presents may have higher latency, and may use less power when the screen content is updated infrequently, or when only a portion of the screen needs to be updated in most frames.See AlsoVkBool32,  , ,  a,  display is a handle that is used to refer to the display described here. This handle will be valid for the lifetime of the Vulkan instance.  displayName is a pointer to a NULL-terminated string containing the name of the display. Generally, this will be the name provided by the display s EDID. It can be NULL+ if no suitable name is available. If not NULL, the memory it points to must remain accessible as long as display is valid. physicalDimensions` describes the physical width and height of the visible portion of the display, in millimeters. physicalResolutionI describes the physical, native, or preferred resolution of the display. 9VkDisplayModeKHR - Opaque handle to a display mode objectSee Also ,  ,  ,  ,Dummy data to tag the  with 0VkDisplayKHR - Opaque handle to a display objectSee Also ,  , Z,  , C,  ,  , Z, 4, Y-Dummy data to tag the  with 4VkDisplayPlaneAlphaFlagBitsKHR - Alpha blending typeSee Also ,  +vkCreateDisplayPlaneSurfaceKHR - Create a  s1 structure representing a display plane and mode ParametersinstanceV is the instance corresponding to the physical device the targeted display is on. pCreateInfo) is a pointer to an instance of the  ^ structure specifying which mode, plane, and other parameters to use, as described below. pAllocator is the allocator used for host memory allocated for the surface object when there is no more specific allocator available (see  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation).pSurface points to a  VkSurfaceKHR6 handle in which the created surface is returned.Valid Usage (Implicit)instance must be a valid  VkInstance handle pCreateInfo must$ be a valid pointer to a valid VkDisplaySurfaceCreateInfoKHR structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structurepSurface must be a valid pointer to a  VkSurfaceKHR handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also,  , ,  s VvkGetDisplayPlaneCapabilitiesKHR - Query capabilities of a mode and plane combination ParametersphysicalDevice( is the physical device associated with displaymode is the display mode the application intends to program when using the specified plane. Note this parameter also implicitly specifies a display. planeIndex is the plane which the application intends to use with the display, and is less than the number of display planes supported by the device. pCapabilities is a pointer to a  7 structure in which the capabilities are returned.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handlemode must be a valid VkDisplayModeKHR handle pCapabilities must be a valid pointer to a VkDisplayPlaneCapabilitiesKHR structureHost SynchronizationHost access to mode must be externally synchronized Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also ,  ,  .vkCreateDisplayModeKHR - Create a display mode ParametersphysicalDevice( is the physical device associated with display.display1 is the display to create an additional mode for. pCreateInfo is a  2 structure describing the new mode to create. pAllocator is the allocator used for host memory allocated for the display mode object when there is no more specific allocator available (see  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation).pMode( returns the handle of the mode created.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handledisplay must be a valid  VkDisplayKHR handle pCreateInfo must$ be a valid pointer to a valid VkDisplayModeCreateInfoKHR structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structurepMode must be a valid pointer to a VkDisplayModeKHR handleHost SynchronizationHost access to display must be externally synchronized Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_INITIALIZATION_FAILEDSee Also,  ,  ,  ,  ZvkGetDisplayModePropertiesKHR - Query the set of mode properties supported by the display ParametersphysicalDevice( is the physical device associated with display.display is the display to query.pPropertyCountq is a pointer to an integer related to the number of display modes available or queried, as described below. pProperties is either NULL" or a pointer to an array of VkDisplayModePropertiesKHR structures. DescriptionIf  pProperties is NULL?, then the number of display modes available on the specified display for physicalDevice is returned in pPropertyCount . Otherwise, pPropertyCount mustG point to a variable set by the user to the number of elements in the  pPropertiesf array, and on return the variable is overwritten with the number of structures actually written to  pProperties. If the value of pPropertyCount/ is less than the number of display modes for physicalDevice , at most pPropertyCount structures will be written. If pPropertyCountJ is smaller than the number of display modes available on the specified display for physicalDevice,  VK_INCOMPLETE will be returned instead of  VK_SUCCESS> to indicate that not all the available values were returned.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handledisplay must be a valid  VkDisplayKHR handlepPropertyCount must be a valid pointer to a uint32_t valueIf the value referenced by pPropertyCount is not 0 , and  pProperties is not NULL,  pProperties must( be a valid pointer to an array of pPropertyCount VkDisplayModePropertiesKHR structures Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS  VK_INCOMPLETE ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also ,  ,  TvkGetDisplayPlaneSupportedDisplaysKHR - Query the list of displays a plane supports ParametersphysicalDevice is a physical device. planeIndex< is the plane which the application wishes to use, and must6 be in the range [0, physical device plane count - 1]. pDisplayCountl is a pointer to an integer related to the number of displays available or queried, as described below. pDisplays is either NULL" or a pointer to an array of  VkDisplayKHR handles. DescriptionIf  pDisplays is NULL9, then the number of displays usable with the specified  planeIndex for physicalDevice is returned in  pDisplayCount . Otherwise,  pDisplayCount mustG point to a variable set by the user to the number of elements in the  pDisplaysc array, and on return the variable is overwritten with the number of handles actually written to  pDisplays. If the value of  pDisplayCount0 is less than the number of display planes for physicalDevice , at most  pDisplayCount handles will be written. If  pDisplayCountC is smaller than the number of displays usable with the specified  planeIndex for physicalDevice,  VK_INCOMPLETE will be returned instead of  VK_SUCCESS> to indicate that not all the available values were returned. Valid Usage planeIndex mustf be less than the number of display planes supported by the device as determined by calling ,vkGetPhysicalDeviceDisplayPlanePropertiesKHRValid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handle pDisplayCount must be a valid pointer to a uint32_t valueIf the value referenced by  pDisplayCount is not 0 , and  pDisplays is not NULL,  pDisplays must( be a valid pointer to an array of  pDisplayCount  VkDisplayKHR handles Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS  VK_INCOMPLETE ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also ,  JvkGetPhysicalDeviceDisplayPlanePropertiesKHR - Query the plane properties ParametersphysicalDevice is a physical device.pPropertyCountr is a pointer to an integer related to the number of display planes available or queried, as described below. pProperties is either NULL" or a pointer to an array of VkDisplayPlanePropertiesKHR structures. DescriptionIf  pProperties is NULL3, then the number of display planes available for physicalDevice is returned in pPropertyCount. Otherwise, pPropertyCount mustG point to a variable set by the user to the number of elements in the  pPropertiesf array, and on return the variable is overwritten with the number of structures actually written to  pProperties. If the value of pPropertyCount0 is less than the number of display planes for physicalDevice , at most pPropertyCount structures will be written.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handlepPropertyCount must be a valid pointer to a uint32_t valueIf the value referenced by pPropertyCount is not 0 , and  pProperties is not NULL,  pProperties must( be a valid pointer to an array of pPropertyCount VkDisplayPlanePropertiesKHR structures Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS  VK_INCOMPLETE ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also ,  YvkGetPhysicalDeviceDisplayPropertiesKHR - Query information about the available displays ParametersphysicalDevice is a physical device.pPropertyCounts is a pointer to an integer related to the number of display devices available or queried, as described below. pProperties is either NULL" or a pointer to an array of VkDisplayPropertiesKHR structures. DescriptionIf  pProperties is NULL4, then the number of display devices available for physicalDevice is returned in pPropertyCount. Otherwise, pPropertyCount mustG point to a variable set by the user to the number of elements in the  pPropertiesf array, and on return the variable is overwritten with the number of structures actually written to  pProperties. If the value of pPropertyCount1 is less than the number of display devices for physicalDevice , at most pPropertyCount! structures will be written. If pPropertyCount> is smaller than the number of display devices available for physicalDevice,  VK_INCOMPLETE will be returned instead of  VK_SUCCESS> to indicate that not all the available values were returned.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handlepPropertyCount must be a valid pointer to a uint32_t valueIf the value referenced by pPropertyCount is not 0 , and  pProperties is not NULL,  pProperties must( be a valid pointer to an array of pPropertyCount VkDisplayPropertiesKHR structures Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS  VK_INCOMPLETE ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also ,  '6VK_DISPLAY_PLANE_ALPHA_PER_PIXEL_PREMULTIPLIED_BIT_KHR is equivalent to (VK_DISPLAY_PLANE_ALPHA_PER_PIXEL_BIT_KHRp, except the source alpha values are assumed to be premultiplied into the source image s other color channels. ((VK_DISPLAY_PLANE_ALPHA_PER_PIXEL_BIT_KHR specifies that the alpha value will be determined by the alpha channel of the source image s pixels. If the source format contains no alpha values, no blending will be applied. The source alpha values are not premultiplied into the source image s other color channels. )%VK_DISPLAY_PLANE_ALPHA_GLOBAL_BIT_KHR& specifies that a global alpha value mustF be specified that will be applied to all pixels in the source image. *%VK_DISPLAY_PLANE_ALPHA_OPAQUE_BIT_KHR< specifies that the source image will be treated as opaque.L                           ! " # $ % & ' ( ) *L   * ) ( '     & % $ # " !                     YNone-STejk%)v U@vkReleaseDisplayEXT - Release access to an acquired VkDisplayKHR ParametersphysicalDevice' The physical device the display is on.display# The display to release control of.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handledisplay must be a valid  VkDisplayKHR handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESSSee Also ,  U V W W V UZNone-STejk%P8 YYvkGetRandROutputDisplayEXT - Query the VkDisplayKHR corresponding to an X11 RandR Output ParametersphysicalDevice4 The physical device to query the display handle on.dpy+ A connection to the X11 server from which rrOutput was queried.rrOutput An X11 RandR output ID.pDisplay The corresponding  # handle will be returned here. DescriptionIf there is no   corresponding to rrOutput on physicalDevice,  must be returned in pDisplay.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handledpy must be a valid pointer to a Display valuepDisplay must be a valid pointer to a  VkDisplayKHR handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESSSee Also ,  ZEvkAcquireXlibDisplayEXT - Acquire access to a VkDisplayKHR using Xlib ParametersphysicalDevice' The physical device the display is on.dpy4 A connection to the X11 server that currently owns display.display4 The display the caller wishes to control in Vulkan. DescriptioneAll permissions necessary to control the display are granted to the Vulkan instance associated with physicalDeviceC until the display is released or the X11 connection specified by dpy2 is terminated. Permission to access the display mayu be temporarily revoked during periods when the X11 server from which control was acquired itself looses access to displayG. During such periods, operations which require access to the display mustH fail with an approriate error code. If the X11 server associated with dpy does not own displayX, or if permission to access it has already been acquired by another entity, the call must return the error code VK_ERROR_INITIALIZATION_FAILED.NotepOne example of when an X11 server loses access to a display is when it loses ownership of its virtual terminal.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handledpy must be a valid pointer to a Display valuedisplay must be a valid  VkDisplayKHR handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_INITIALIZATION_FAILEDSee Also ,  X Y Z [ \ X \ [ Z Y[None "-STbejk&3$ ]VkMultisamplePropertiesEXT - Structure returning information about sample count specific additional multisampling capabilitiesValid Usage (Implicit)sType must be ,VK_STRUCTURE_TYPE_MULTISAMPLE_PROPERTIES_EXTpNext must be NULLSee Also, ,  _sType is the type of this structure. `pNext is NULL1 or a pointer to an extension-specific structure. amaxSampleLocationGridSizeB is the maximum size of the pixel grid in which sample locations can vary. bVkPhysicalDeviceSampleLocationsPropertiesEXT - Structure describing sample location limits that can be supported by an implementationMembersThe members of the ,VkPhysicalDeviceSampleLocationsPropertiesEXTC structure describe the following implementation-dependent limits: DescriptionsampleLocationSampleCounts is a bitmask of F indicating the sample counts supporting custom sample locations.maxSampleLocationGridSizeF is the maximum size of the pixel grid in which sample locations can6 vary that is supported for all sample counts in sampleLocationSampleCounts.sampleLocationCoordinateRange?[2] is the range of supported sample location coordinates.sampleLocationSubPixelBitsG is the number of bits of subpixel precision for sample locations.variableSampleLocations specifies whether the sample locations used by all pipelines that will be bound to a command buffer during a subpass must match. If set to VK_TRUEZ, the implementation supports variable sample locations in a subpass. If set to VK_FALSE, then the sample locations must$ stay constant in each subpass.Valid Usage (Implicit)sType must be AVK_STRUCTURE_TYPE_PHYSICAL_DEVICE_SAMPLE_LOCATIONS_PROPERTIES_EXTIf the ,VkPhysicalDeviceSampleLocationsPropertiesEXT structure is included in the pNext chain of sf9, it is filled with the implementation-dependent limits.See AlsoVkBool32, , ,  kcVkPipelineSampleLocationsStateCreateInfoEXT - Structure specifying sample locations for a pipelineValid Usage (Implicit)sType must be AVK_STRUCTURE_TYPE_PIPELINE_SAMPLE_LOCATIONS_STATE_CREATE_INFO_EXTsampleLocationsInfo must be a valid VkSampleLocationsInfoEXT structureSee AlsoVkBool32,  ,  msType is the type of this structure. npNext is NULL1 or a pointer to an extension-specific structure. osampleLocationsEnable8 controls whether custom sample locations are used. If sampleLocationsEnable is VK_FALSEE, the default sample locations are used and the values specified in sampleLocationsInfo are ignored. psampleLocationsInfo9 is the sample locations to use during rasterization if sampleLocationsEnable is VK_TRUE/ and the graphics pipeline isn t created with %VK_DYNAMIC_STATE_SAMPLE_LOCATIONS_EXT. qVkRenderPassSampleLocationsBeginInfoEXT - Structure specifying sample locations to use for the layout transition of custom sample locations compatible depth/stencil attachmentsValid Usage (Implicit)sType must be =VK_STRUCTURE_TYPE_RENDER_PASS_SAMPLE_LOCATIONS_BEGIN_INFO_EXTIf %attachmentInitialSampleLocationsCount is not 0, !pAttachmentInitialSampleLocations must( be a valid pointer to an array of %attachmentInitialSampleLocationsCount valid VkAttachmentSampleLocationsEXT structuresIf postSubpassSampleLocationsCount is not 0, pPostSubpassSampleLocations must( be a valid pointer to an array of postSubpassSampleLocationsCount valid VkSubpassSampleLocationsEXT structuresSee Also }, ,  y ssType is the type of this structure. tpNext is NULL1 or a pointer to an extension-specific structure. u%attachmentInitialSampleLocationsCount# is the number of elements in the !pAttachmentInitialSampleLocations array. v!pAttachmentInitialSampleLocations is an array of %attachmentInitialSampleLocationsCount  }p structures specifying the attachment indices and their corresponding sample location state. Each element of !pAttachmentInitialSampleLocations can specify the sample location state to use in the automatic layout transition performed to transition a depth/stencil attachment from the initial layout of the attachment to the image layout specified for the attachment in the first subpass using it. wpostSubpassSampleLocationsCount# is the number of elements in the pPostSubpassSampleLocations array. xpPostSubpassSampleLocations is an array of postSubpassSampleLocationsCount  yl structures specifying the subpass indices and their corresponding sample location state. Each element of pPostSubpassSampleLocations can] specify the sample location state to use in the automatic layout transition performed to transition the depth/stencil attachment used by the specified subpass to the image layout specified in a dependent subpass or to the final layout of the attachment in case the specified subpass is the last subpass using that attachment. In addition, if  b::variableSampleLocations is VK_FALSE, each element of pPostSubpassSampleLocations must specify the sample location state that matches the sample locations used by all pipelines that will be bound to a command buffer during the specified subpass. If variableSampleLocations is VK_TRUEA, the sample locations used for rasterization do not depend on pPostSubpassSampleLocations. yVkSubpassSampleLocationsEXT - Structure specifying the sample locations state to use for layout transitions of attachments performed after a given subpass Description[If the image referenced by the depth/stencil attachment used in the subpass identified by  subpassIndex was not created with 9VK_IMAGE_CREATE_SAMPLE_LOCATIONS_COMPATIBLE_DEPTH_BIT_EXTB or if the subpass does not use a depth/stencil attachment, and  b::variableSampleLocations is VK_TRUE then the values specified in sampleLocationsInfo are ignored. Valid Usage subpassIndex must be less than the  subpassCount specified in ( the render pass specified by :: renderPass was created withValid Usage (Implicit)sampleLocationsInfo must be a valid VkSampleLocationsInfoEXT structureSee Also q,  { subpassIndexO is the index of the subpass for which the sample locations state is provided. |sampleLocationsInfo is the sample locations state to use for the layout transition of the depth/stencil attachment away from the image layout the attachment is used with in the subpass specified in  subpassIndex. }VkAttachmentSampleLocationsEXT - Structure specifying the sample locations state to use in the initial layout transition of attachments Description@If the image referenced by the framebuffer attachment at index attachmentIndex was not created with 9VK_IMAGE_CREATE_SAMPLE_LOCATIONS_COMPATIBLE_DEPTH_BIT_EXT then the values specified in sampleLocationsInfo are ignored. Valid UsageattachmentIndex must be less than the attachmentCount specified in ( the render pass specified by :: renderPass was created withValid Usage (Implicit)sampleLocationsInfo must be a valid VkSampleLocationsInfoEXT structureSee Also q,  attachmentIndexR is the index of the attachment for which the sample locations state is provided. sampleLocationsInfo is the sample locations state to use for the layout transition of the given attachment from the initial layout of the attachment to the image layout specified for the attachment in the first subpass using it. JVkSampleLocationsInfoEXT - Structure specifying a set of sample locations DescriptionThis structure can be used either to specify the sample locations to be used for rendering or to specify the set of sample locations an image subresource has been last rendered with for the purposes of layout transitions of depth/stencil images created with 9VK_IMAGE_CREATE_SAMPLE_LOCATIONS_COMPATIBLE_DEPTH_BIT_EXT.The sample locations in pSampleLocations specify sampleLocationsPerPixelQ number of sample locations for each pixel in the grid of the size specified in sampleLocationGridSizeT. The sample location for sample i at the pixel grid location (x,y) is taken from pSampleLocations [(x + y * sampleLocationGridSize.width) * sampleLocationsPerPixel + i]. Valid UsagesampleLocationsPerPixel must$ be a bit value that is set in  b::sampleLocationSampleCountssampleLocationsCount must equal sampleLocationsPerPixel sampleLocationGridSize.width sampleLocationGridSize.heightValid Usage (Implicit)sType must be +VK_STRUCTURE_TYPE_SAMPLE_LOCATIONS_INFO_EXTsampleLocationsPerPixel must be a valid  valuepSampleLocations must( be a valid pointer to an array of sampleLocationsCount VkSampleLocationEXT structuressampleLocationsCount must be greater than 0See Also }, ,  k, ,  , ,  y,  sType is the type of this structure. pNext is NULL1 or a pointer to an extension-specific structure. sampleLocationsPerPixel is a 6 specifying the number of sample locations per pixel. sampleLocationGridSizeP is the size of the sample location grid to select custom sample locations for. sampleLocationsCount' is the number of sample locations in pSampleLocations. pSampleLocations is an array of sampleLocationsCount   structures. PVkSampleLocationEXT - Structure specifying the coordinates of a sample location DescriptiontThe domain space of the sample location coordinates has an upper-left origin within the pixel in framebuffer space.The values specified in a VkSampleLocationEXTb structure are always clamped to the implementation-dependent sample location coordinate range [sampleLocationCoordinateRange[0],sampleLocationCoordinateRange [1]] that can be queried by chaining the  b structure to the pNext chain of sf.See Also x7 is the horizontal coordinate of the sample s location. y5 is the vertical coordinate of the sample s location. {vkGetPhysicalDeviceMultisamplePropertiesEXT - Report sample count specific multisampling capabilities of a physical device ParametersphysicalDevice[ is the physical device from which to query the additional multisampling capabilities.samples3 is the sample count to query the capabilities for.pMultisampleProperties* is a pointer to a structure of type  ]z, in which information about the additional multisampling capabilities specific to the sample count is returned.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handlesamples must be a valid  valuepMultisampleProperties must be a valid pointer to a VkMultisamplePropertiesEXT structureSee Also ], ,  CvkCmdSetSampleLocationsEXT - Set the dynamic sample locations state Parameters commandBufferD is the command buffer into which the command will be recorded.pSampleLocationsInfo& is the sample locations state to set. Valid UsageThe bound graphics pipeline must! have been created with the %VK_DYNAMIC_STATE_SAMPLE_LOCATIONS_EXT dynamic state enabledThe sampleLocationsPerPixel member of pSampleLocationsInfo must equal the rasterizationSamples member of the H~A structure the bound graphics pipeline has been created withIf  b::variableSampleLocations is VK_FALSE then the current render pass must& have been begun by specifying a  q structure whose pPostSubpassSampleLocations( member contains an element with a  subpassIndex1 matching the current subpass index and the sampleLocationsInfo member of that element must5 match the sample locations state pointed to by pSampleLocationsInfoValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handlepSampleLocationsInfo must$ be a valid pointer to a valid VkSampleLocationsInfoEXT structure commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must! support graphics operationsHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Both  Graphics  See Also,  %VK_DYNAMIC_STATE_SAMPLE_LOCATIONS_EXT specifies that the sampleLocationsInfo state in  k will be ignored and must be set dynamically with  a before any draw or clear commands. Enabling custom sample locations is still indicated by the sampleLocationsEnable member of +VkPipelineSampleLocationsStateCreateInfoEXT.; ] ^ _ ` a b c d e f g h i j k l m n p o q r s t u v w x y z | { } ~  ; } ~  y z | { q r s t u v w x k l m n p o b c d e f g h i j ] ^ _ ` a\None "-KSTbejk&_ AVkSurfaceCounterFlagsEXT - Bitmask of VkSurfaceCounterFlagBitsEXT DescriptionVkSurfaceCounterFlagsEXT7 is a bitmask type for setting a mask of zero or more  .See Also ,  ,  KVkSurfaceCapabilities2EXT - Structure describing capabilities of a surfaceMembersAll members of VkSurfaceCapabilities2EXT1 are identical to the corresponding members of K. where one exists. The remaining members are: DescriptionsType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.supportedSurfaceCounters is a bitmask of  5 indicating the supported surface counter types. Valid UsagesupportedSurfaceCounters must not include VK_SURFACE_COUNTER_VBLANK_EXT& unless the surface queried is a  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#wsi-display-surfacesdisplay surface.Valid Usage (Implicit)sType must be ,VK_STRUCTURE_TYPE_SURFACE_CAPABILITIES_2_EXTpNext must be NULLSee Also b, , , ,  ,  t,  a,  <VkSurfaceCounterFlagBitsEXT - Surface-relative counter typesSee Also , k GvkGetPhysicalDeviceSurfaceCapabilities2EXT - Query surface capabilities ParametersphysicalDevicem is the physical device that will be associated with the swapchain to be created, as described for  .surface; is the surface that will be associated with the swapchain.pSurfaceCapabilities) is a pointer to an instance of the  7 structure in which the capabilities are returned. Description*vkGetPhysicalDeviceSurfaceCapabilities2EXT behaves similarly to KZ, with the ability to return extended information by adding extension structures to the pNext chain of its pSurfaceCapabilities parameter.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handlesurface must be a valid  VkSurfaceKHR handlepSurfaceCapabilities must be a valid pointer to a VkSurfaceCapabilities2EXT structureBoth of physicalDevice, and surface must? have been created, allocated, or retrieved from the same  VkInstance Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_SURFACE_LOST_KHRSee Also,  ,  s VK_SURFACE_COUNTER_VBLANK_EXT specifies a counter incrementing once every time a vertical blanking period occurs on the display associated with the surface.  ]None "-KSTbejk& VVkPipelineDiscardRectangleStateCreateInfoEXT - Structure specifying discard rectangle Valid UsagediscardRectangleCount must be between 0 and -VkPhysicalDeviceDiscardRectanglePropertiesEXT::maxDiscardRectangles, inclusiveValid Usage (Implicit)sType must be BVK_STRUCTURE_TYPE_PIPELINE_DISCARD_RECTANGLE_STATE_CREATE_INFO_EXTflags must be 0discardRectangleMode must be a valid   valueSee Also ,  , ,  sType is the type of this structure. pNext is NULL1 or a pointer to an extension-specific structure. flags is reserved for future use. discardRectangleModem is the mode used to determine whether fragments that lie within the discard rectangle are discarded or not. discardRectangleCount; is the number of discard rectangles used by the pipeline. pDiscardRectangles is a pointer to an array of r structures, defining the discard rectangles. If the discard rectangle state is dynamic, this member is ignored. VkPhysicalDeviceDiscardRectanglePropertiesEXT - Structure describing discard rectangle limits that can be supported by an implementationMembersThe members of the -VkPhysicalDeviceDiscardRectanglePropertiesEXTC structure describe the following implementation-dependent limits: DescriptionmaxDiscardRectangles7 is the maximum number of discard rectangles that can be specified.Valid Usage (Implicit)sType must be BVK_STRUCTURE_TYPE_PHYSICAL_DEVICE_DISCARD_RECTANGLE_PROPERTIES_EXTIf the -VkPhysicalDeviceDiscardRectanglePropertiesEXT structure is included in the pNext chain of sf9, it is filled with the implementation-dependent limits.See Also GVkPipelineDiscardRectangleStateCreateFlagsEXT - Reserved for future use Description-VkPipelineDiscardRectangleStateCreateFlagsEXTQ is a bitmask type for setting a mask, but is currently reserved for future use.See Also >VkDiscardRectangleModeEXT - Specify the discard rectangle modeSee Also @vkCmdSetDiscardRectangleEXT - Set discard rectangles dynamically Parameters commandBufferD is the command buffer into which the command will be recorded.firstDiscardRectangleX is the index of the first discard rectangle whose state is updated by the command.discardRectangleCountQ is the number of discard rectangles whose state are updated by the command.pDiscardRectangles" is a pointer to an array of / structures specifying discard rectangles. Description.The discard rectangle taken from element i of pDiscardRectangles= replace the current state for the discard rectangle index firstDiscardRectangle + i, for i in [0, discardRectangleCount). Valid UsageThe bound graphics pipeline must! have been created with the &VK_DYNAMIC_STATE_DISCARD_RECTANGLE_EXT dynamic state enabled The sum of firstDiscardRectangle and discardRectangleCount must be less than or equal to  ::maxDiscardRectanglesThe x and y member of offset in each  element of pDiscardRectangles must be greater than or equal to 0Evaluation of (offset.x +  extent.width) in each  element of pDiscardRectangles must2 not cause a signed integer addition overflowEvaluation of (offset.y +  extent.height) in each  element of pDiscardRectangles must2 not cause a signed integer addition overflowValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handlepDiscardRectangles must( be a valid pointer to an array of discardRectangleCount VkRect2D structures commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must! support graphics operationsdiscardRectangleCount must be greater than 0Host SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Both  Graphics  See Also,  'VK_DISCARD_RECTANGLE_MODE_EXCLUSIVE_EXTX specifies that a fragment not within any of the discard rectangles satisfies the test. 'VK_DISCARD_RECTANGLE_MODE_INCLUSIVE_EXTL specifies that a fragment within any discard rectangle satisfies the test.  ^None"bejk'% YVkBindImageMemoryDeviceGroupInfo - Structure specifying device within a group to bind toMembersIf the pNext list of p includes a  VkBindImageMemoryDeviceGroupInfou structure, then that structure determines how memory is bound to images across multiple devices in a device group. DescriptionThe  VkBindImageMemoryDeviceGroupInfo structure is defined as:sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.deviceIndexCount is the number of elements in pDeviceIndices.pDeviceIndices, is a pointer to an array of device indices.splitInstanceBindRegionCount# is the number of elements in pSplitInstanceBindRegions.pSplitInstanceBindRegions is a pointer to an array of rectangles describing which regions of the image are attached to each instance of memory.If deviceIndexCount/ is greater than zero, then on device index i imageg is attached to the instance of the memory on the physical device with device index pDeviceIndices[i].CLet N be the number of physical devices in the logical device. If splitInstanceBindRegionCount is greater than zero, then pSplitInstanceBindRegions is an array of N2 rectangles, where the image region specified by the rectangle at element i*N+j in resource instance i is bound to the memory instance j. The blocks of the memory that are bound to each sparse image block region use an offset in memory, relative to  memoryOffset!, computed as if the whole image were being bound to a contiguous range of memory. In other words, horizontally adjacent image blocks use consecutive blocks of memory, vertically adjacent image blocks are separated by the number of bytes per block multiplied by the width in blocks of image<, and the block at (0,0) corresponds to memory starting at  memoryOffset.If splitInstanceBindRegionCount and deviceIndexCount= are zero and the memory comes from a memory heap with the !VK_MEMORY_HEAP_MULTI_INSTANCE_BIT bit set, then it is as if pDeviceIndices contains consecutive indices from zero to the number of physical devices in the logical device, minus one. In other words, by default each physical device attaches to its own instance of the memory.If splitInstanceBindRegionCount and deviceIndexCount@ are zero and the memory comes from a memory heap without the !VK_MEMORY_HEAP_MULTI_INSTANCE_BIT bit set, then it is as if pDeviceIndicesh contains an array of zeros. In other words, by default each physical device attaches to instance zero. Valid UsageAt least one of deviceIndexCount and splitInstanceBindRegionCount must be zero.deviceIndexCount mustU either be zero or equal to the number of physical devices in the logical deviceAll elements of pDeviceIndices must be valid device indices.splitInstanceBindRegionCount must] either be zero or equal to the number of physical devices in the logical device squared Elements of pSplitInstanceBindRegions7 that correspond to the same instance of an image must not overlap.The offset.x member of any element of pSplitInstanceBindRegions must5 be a multiple of the sparse image block width (VkSparseImageFormatProperties::imageGranularity.width/) of all non-metadata aspects of the imageThe offset.y member of any element of pSplitInstanceBindRegions must6 be a multiple of the sparse image block height (VkSparseImageFormatProperties::imageGranularity.height/) of all non-metadata aspects of the imageThe  extent.width member of any element of pSplitInstanceBindRegions mustr either be a multiple of the sparse image block width of all non-metadata aspects of the image, or else  extent.width + offset.x must. equal the width of the image subresourceThe  extent.height member of any element of pSplitInstanceBindRegions musts either be a multiple of the sparse image block height of all non-metadata aspects of the image, or else  extent.height offset.y must) equal the width of the image subresourceValid Usage (Implicit)sType must be 5VK_STRUCTURE_TYPE_BIND_IMAGE_MEMORY_DEVICE_GROUP_INFOIf deviceIndexCount is not 0, pDeviceIndices must( be a valid pointer to an array of deviceIndexCount uint32_t valuesIf splitInstanceBindRegionCount is not 0, pSplitInstanceBindRegions must( be a valid pointer to an array of splitInstanceBindRegionCount VkRect2D structuresSee Also,  ZVkBindBufferMemoryDeviceGroupInfo - Structure specifying device within a group to bind toMembersIf the pNext list of p includes a !VkBindBufferMemoryDeviceGroupInfov structure, then that structure determines how memory is bound to buffers across multiple devices in a device group. DescriptionThe !VkBindBufferMemoryDeviceGroupInfo structure is defined as:sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.deviceIndexCount is the number of elements in pDeviceIndices.pDeviceIndices, is a pointer to an array of device indices.If deviceIndexCountY is greater than zero, then on device index i the buffer is attached to the instance of memory= on the physical device with device index pDeviceIndices[i].If deviceIndexCount is zero and memory$ comes from a memory heap with the !VK_MEMORY_HEAP_MULTI_INSTANCE_BIT bit set, then it is as if pDeviceIndices contains consecutive indices from zero to the number of physical devices in the logical device, minus one. In other words, by default each physical device attaches to its own instance of memory.If deviceIndexCount is zero and memory' comes from a memory heap without the !VK_MEMORY_HEAP_MULTI_INSTANCE_BIT bit set, then it is as if pDeviceIndicesh contains an array of zeros. In other words, by default each physical device attaches to instance zero. Valid UsagedeviceIndexCount mustU either be zero or equal to the number of physical devices in the logical deviceAll elements of pDeviceIndices must be valid device indicesValid Usage (Implicit)sType must be 6VK_STRUCTURE_TYPE_BIND_BUFFER_MEMORY_DEVICE_GROUP_INFOIf deviceIndexCount is not 0, pDeviceIndices must( be a valid pointer to an array of deviceIndexCount uint32_t valuesSee Also                 _None "-KSTbejk( QVkSamplerCreateInfo - Structure specifying parameters of a newly created samplerMemberssType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.flags is reserved for future use. magFilter is a  -D value specifying the magnification filter to apply to lookups. minFilter is a  -C value specifying the minification filter to apply to lookups. mipmapMode is a  += value specifying the mipmap filter to apply to lookups. addressModeU is a  /U value specifying the addressing mode for outside [0..1] range for U coordinate. addressModeV is a  /U value specifying the addressing mode for outside [0..1] range for V coordinate. addressModeW is a  /U value specifying the addressing mode for outside [0..1] range for W coordinate. mipLodBias is the bias to be added to mipmap LOD (level-of-detail) calculation and bias provided by image sampling functions in SPIR-V, as described in the  phttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#textures-level-of-detail-operationLevel-of-Detail Operation section.anisotropyEnable is VK_TRUE; to enable anisotropic filtering, as described in the  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#textures-texel-anisotropic-filtering Texel Anisotropic Filtering section, or VK_FALSE otherwise. maxAnisotropy= is the anisotropy value clamp used by the sampler when anisotropyEnable is VK_TRUE. If anisotropyEnable is VK_FALSE,  maxAnisotropy is ignored. compareEnable is VK_TRUEH to enable comparison against a reference value during lookups, or VK_FALSE otherwise.ZNote: Some implementations will default to shader state if this member does not match. compareOp is a  r value specifying the comparison function to apply to fetched data before filtering as described in the  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#textures-depth-compare-operationDepth Compare Operation section.minLod and maxLodO are the values used to clamp the computed LOD value, as described in the  phttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#textures-level-of-detail-operationLevel-of-Detail Operation section. maxLod must be greater than or equal to minLod. borderColor is a  1: value specifying the predefined border color to use.unnormalizedCoordinates| controls whether to use unnormalized or normalized texel coordinates to address texels of the image. When set to VK_TRUE, the range of the image coordinates used to lookup the texel is in the range of zero to the image dimensions for x, y and z. When set to VK_FALSE: the range of image coordinates is zero to one. When unnormalizedCoordinates is VK_TRUE0, samplers have the following requirements: minFilter and  magFilter must be equal. mipmapMode must be VK_SAMPLER_MIPMAP_MODE_NEAREST.minLod and maxLod must be zero. addressModeU and  addressModeV must each be either %VK_SAMPLER_ADDRESS_MODE_CLAMP_TO_EDGE or 'VK_SAMPLER_ADDRESS_MODE_CLAMP_TO_BORDER.anisotropyEnable must be VK_FALSE. compareEnable must be VK_FALSE. The sampler must& not enable sampler Y CBCR conversion.When unnormalizedCoordinates is VK_TRUEU, images the sampler is used with in the shader have the following requirements:The viewType must be either VK_IMAGE_VIEW_TYPE_1D or VK_IMAGE_VIEW_TYPE_2D.The image view must0 have a single layer and a single mip level.When unnormalizedCoordinates is VK_TRUEh, image built-in functions in the shader that use the sampler have the following requirements:The functions must not use projection.The functions must not use offsets. DescriptionNote magFilter values of VK_FILTER_NEAREST and VK_FILTER_LINEAR directly correspond to  GL_NEAREST and  GL_LINEAR magnification filters.  minFilter and  mipmapModeN combine to correspond to the similarly named OpenGL minification filter of GL_minFilter_MIPMAP_mipmapMode (e.g.  minFilter of VK_FILTER_LINEAR and  mipmapMode of VK_SAMPLER_MIPMAP_MODE_NEAREST correspond to GL_LINEAR_MIPMAP_NEAREST).]There are no Vulkan filter modes that directly correspond to OpenGL minification filters of  GL_LINEAR or  GL_NEAREST , but they can be emulated using VK_SAMPLER_MIPMAP_MODE_NEAREST, minLod = 0, and maxLod = 0.25, and using  minFilter = VK_FILTER_LINEAR or  minFilter = VK_FILTER_NEAREST, respectively.Note that using a maxLod of zero would cause  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#textures-texel-filtering magnification" to always be performed, and the  magFilter to always be used. This is valid, just not an exact match for OpenGL behavior. Clamping the maximum LOD to 0.25 allows the  value to be non-zero and minification to be performed, while still always rounding down to the base level. If the  minFilter and  magFilter are equal, then using a maxLod of zero also works.,The maximum number of sampler objects which canZ be simultaneously created on a device is implementation-dependent and specified by the  whttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-limits-maxSamplerAllocationCountmaxSamplerAllocationCount member of the / structure. If maxSamplerAllocationCount is exceeded, vkCreateSampler will return VK_ERROR_TOO_MANY_OBJECTS.Since  (5 is a non-dispatchable handle type, implementations may return the same handle for sampler state vectors that are identical. In such cases, all such objects would only count once against the maxSamplerAllocationCount limit. Valid UsageThe absolute value of  mipLodBias must be less than or equal to VkPhysicalDeviceLimits::maxSamplerLodBiasIf the  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-samplerAnisotropyanisotropic sampling feature is not enabled, anisotropyEnable must be VK_FALSEIf anisotropyEnable is VK_TRUE,  maxAnisotropy must be between 1.0 and VkPhysicalDeviceLimits::maxSamplerAnisotropy, inclusiveIf  ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#samplers-YCbCr-conversionsampler Y CBCR conversion is enabled and SVK_FORMAT_FEATURE_SAMPLED_IMAGE_YCBCR_CONVERSION_SEPARATE_RECONSTRUCTION_FILTER_BIT! is not set for the format,  minFilter and  magFilter must2 be equal to the sampler Y CBCR conversion s  chromaFilterIf unnormalizedCoordinates is VK_TRUE,  minFilter and  magFilter must be equalIf unnormalizedCoordinates is VK_TRUE,  mipmapMode must be VK_SAMPLER_MIPMAP_MODE_NEARESTIf unnormalizedCoordinates is VK_TRUE, minLod and maxLod must be zeroIf unnormalizedCoordinates is VK_TRUE,  addressModeU and  addressModeV must each be either %VK_SAMPLER_ADDRESS_MODE_CLAMP_TO_EDGE or 'VK_SAMPLER_ADDRESS_MODE_CLAMP_TO_BORDERIf unnormalizedCoordinates is VK_TRUE, anisotropyEnable must be VK_FALSEIf unnormalizedCoordinates is VK_TRUE,  compareEnable must be VK_FALSE If any of  addressModeU,  addressModeV or  addressModeW are 'VK_SAMPLER_ADDRESS_MODE_CLAMP_TO_BORDER,  borderColor must be a valid  1 valueIf  ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#samplers-YCbCr-conversionsampler Y CBCR conversion is enabled,  addressModeU,  addressModeV, and  addressModeW must be %VK_SAMPLER_ADDRESS_MODE_CLAMP_TO_EDGE, anisotropyEnable must be VK_FALSE , and unnormalizedCoordinates must be VK_FALSEThe sampler reduction mode must be set to .VK_SAMPLER_REDUCTION_MODE_WEIGHTED_AVERAGE_EXT if  ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#samplers-YCbCr-conversionsampler Y CBCR conversion is enabledIf the 8{html_spec_relative}#VK_KHR_sampler_mirror_clamp_to_edge extension is not enabled,  addressModeU,  addressModeV and  addressModeW must not be ,VK_SAMPLER_ADDRESS_MODE_MIRROR_CLAMP_TO_EDGEIf  compareEnable is VK_TRUE,  compareOp must be a valid   value If either  magFilter or  minFilter is VK_FILTER_CUBIC_IMG, anisotropyEnable must be VK_FALSE If either  magFilter or  minFilter is VK_FILTER_CUBIC_IMG , the  reductionMode member of 2 must be .VK_SAMPLER_REDUCTION_MODE_WEIGHTED_AVERAGE_EXTIf  compareEnable is VK_TRUE, the  reductionMode member of 2 must be .VK_SAMPLER_REDUCTION_MODE_WEIGHTED_AVERAGE_EXTValid Usage (Implicit)sType must be %VK_STRUCTURE_TYPE_SAMPLER_CREATE_INFO Each pNext: member of any structure (including this one) in the pNext chain must be either NULL/ or a pointer to a valid instance of 2 or xEach sType member in the pNext chain must be uniqueflags must be 0 magFilter must be a valid  - value minFilter must be a valid  - value mipmapMode must be a valid  + value addressModeU must be a valid  / value addressModeV must be a valid  / value addressModeW must be a valid  / valueSee AlsoVkBool32,  1,  ,  -,  /,  ),  +, ,  4 (-VkSampler - Opaque handle to a sampler objectSee Also, ,  4,  3.Dummy data to tag the  with ).VkSamplerCreateFlags - Reserved for future use DescriptionVkSamplerCreateFlagsQ is a bitmask type for setting a mask, but is currently reserved for future use.See Also  +BVkSamplerMipmapMode - Specify mipmap mode used for texture lookups DescriptionVK_SAMPLER_MIPMAP_MODE_NEAREST specifies nearest filtering.VK_SAMPLER_MIPMAP_MODE_LINEAR specifies linear filtering.'These modes are described in detail in  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#textures-texel-filteringTexel Filtering.See Also  -3VkFilter - Specify filters used for texture lookups DescriptionVK_FILTER_NEAREST specifies nearest filtering.VK_FILTER_LINEAR specifies linear filtering.VK_FILTER_CUBIC_IMG specifies cubic filtering.)These filters are described in detail in  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#textures-texel-filteringTexel Filtering.See Also , x,  /^VkSamplerAddressMode - Specify behavior of sampling with texture coordinates outside an imageSee Also  1=VkBorderColor - Specify border color used for texture lookups Description'VK_BORDER_COLOR_FLOAT_TRANSPARENT_BLACKB specifies a transparent, floating-point format, black color.%VK_BORDER_COLOR_INT_TRANSPARENT_BLACK; specifies a transparent, integer format, black color."VK_BORDER_COLOR_FLOAT_OPAQUE_BLACK> specifies an opaque, floating-point format, black color. VK_BORDER_COLOR_INT_OPAQUE_BLACK7 specifies an opaque, integer format, black color."VK_BORDER_COLOR_FLOAT_OPAQUE_WHITE> specifies an opaque, floating-point format, white color. VK_BORDER_COLOR_INT_OPAQUE_WHITE7 specifies an opaque, integer format, white color.(These colors are described in detail in  hhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#textures-texel-replacementTexel Replacement.See Also  3+vkDestroySampler - Destroy a sampler object Parametersdevice1 is the logical device that destroys the sampler.sampler is the sampler to destroy. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. Valid Usage%All submitted commands that refer to sampler must have completed executionIf VkAllocationCallbacks were provided when sampler1 was created, a compatible set of callbacks must be provided hereIf no VkAllocationCallbacks were provided when sampler was created,  pAllocator must be NULLValid Usage (Implicit)device must be a valid VkDevice handleIf sampler is not , sampler must be a valid  VkSampler handleIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structureIf sampler is a valid handle, it must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to sampler must be externally synchronizedSee Also, ,  ( 4-vkCreateSampler - Create a new sampler object Parametersdevice0 is the logical device that creates the sampler. pCreateInfo) is a pointer to an instance of the  ; structure specifying the state of the sampler object. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter.pSampler points to a  (? handle in which the resulting sampler object is returned.Valid Usage (Implicit)device must be a valid VkDevice handle pCreateInfo must$ be a valid pointer to a valid VkSamplerCreateInfo structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structurepSampler must be a valid pointer to a  VkSampler handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_TOO_MANY_OBJECTSSee Also, ,  (,   9'VK_SAMPLER_ADDRESS_MODE_CLAMP_TO_BORDER< specifies that the clamp to border wrap mode will be used. :%VK_SAMPLER_ADDRESS_MODE_CLAMP_TO_EDGE: specifies that the clamp to edge wrap mode will be used. ;'VK_SAMPLER_ADDRESS_MODE_MIRRORED_REPEAT< specifies that the mirrored repeat wrap mode will be used. <VK_SAMPLER_ADDRESS_MODE_REPEAT3 specifies that the repeat wrap mode will be used./      #        ! " $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B/ 1 2 B A @ ? > = / 0 < ; : 9 - . 8 7 + , 6 5 ) * ( 4 3      #        ! " $ % & '`Noneejk( _ c,VK_SAMPLER_ADDRESS_MODE_MIRROR_CLAMP_TO_EDGE] specifies that the mirror clamp to edge wrap mode will be used. This is only valid if the 8{html_spec_relative}#VK_KHR_sampler_mirror_clamp_to_edge extension is enabled. a b c c b aaNoneejk(  d e f g g f e dbNone "-KSTbejk) h5VkShaderStageFlags - Bitmask of VkShaderStageFlagBits DescriptionVkShaderStageFlags7 is a bitmask type for setting a mask of zero or more .See Also, , dp,  r, , c ,  ikVkPipelineLayoutCreateInfo - Structure specifying the parameters of a newly created pipeline layout objectMemberssType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.flags is reserved for future use.setLayoutCountG is the number of descriptor sets included in the pipeline layout. pSetLayouts is a pointer to an array of VkDescriptorSetLayout objects.pushConstantRangeCountL is the number of push constant ranges included in the pipeline layout.pPushConstantRanges" is a pointer to an array of VkPushConstantRange structures defining a set of push constant ranges for use in a single pipeline layout. In addition to descriptor set layouts, a pipeline layout also describes how many push constants can+ be accessed by each stage of the pipeline.NotePush constants represent a high speed path to modify constant data in pipelines that is expected to outperform memory-backed resource updates. Valid UsagesetLayoutCount must be less than or equal to VkPhysicalDeviceLimits::maxBoundDescriptorSetsXThe total number of descriptors in descriptor set layouts created without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT bit set with a descriptorType of VK_DESCRIPTOR_TYPE_SAMPLER and )VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLERB accessible to any given shader stage across all elements of  pSetLayouts must$ be less than or equal to VkPhysicalDeviceLimits::maxPerStageDescriptorSamplersXThe total number of descriptors in descriptor set layouts created without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT bit set with a descriptorType of !VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER and )VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER_DYNAMICB accessible to any given shader stage across all elements of  pSetLayouts must$ be less than or equal to VkPhysicalDeviceLimits::#maxPerStageDescriptorUniformBuffersXThe total number of descriptors in descriptor set layouts created without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT bit set with a descriptorType of !VK_DESCRIPTOR_TYPE_STORAGE_BUFFER and )VK_DESCRIPTOR_TYPE_STORAGE_BUFFER_DYNAMICB accessible to any given shader stage across all elements of  pSetLayouts must$ be less than or equal to VkPhysicalDeviceLimits::#maxPerStageDescriptorStorageBuffersXThe total number of descriptors in descriptor set layouts created without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT bit set with a descriptorType of )VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLER,  VK_DESCRIPTOR_TYPE_SAMPLED_IMAGE , and 'VK_DESCRIPTOR_TYPE_UNIFORM_TEXEL_BUFFERB accessible to any given shader stage across all elements of  pSetLayouts must$ be less than or equal to VkPhysicalDeviceLimits::"maxPerStageDescriptorSampledImagesXThe total number of descriptors in descriptor set layouts created without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT bit set with a descriptorType of  VK_DESCRIPTOR_TYPE_STORAGE_IMAGE , and 'VK_DESCRIPTOR_TYPE_STORAGE_TEXEL_BUFFERB accessible to any given shader stage across all elements of  pSetLayouts must$ be less than or equal to VkPhysicalDeviceLimits::"maxPerStageDescriptorStorageImagesXThe total number of descriptors in descriptor set layouts created without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT bit set with a descriptorType of #VK_DESCRIPTOR_TYPE_INPUT_ATTACHMENTG accessible to any given shader stage across all elements of  pSetLayouts must be less than or equal to VkPhysicalDeviceLimits::%maxPerStageDescriptorInputAttachments'The total number of descriptors with a descriptorType of VK_DESCRIPTOR_TYPE_SAMPLER and )VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLERB accessible to any given shader stage across all elements of  pSetLayouts must$ be less than or equal to /VkPhysicalDeviceDescriptorIndexingPropertiesEXT::,maxPerStageDescriptorUpdateAfterBindSamplers'The total number of descriptors with a descriptorType of !VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER and )VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER_DYNAMICB accessible to any given shader stage across all elements of  pSetLayouts must$ be less than or equal to /VkPhysicalDeviceDescriptorIndexingPropertiesEXT::2maxPerStageDescriptorUpdateAfterBindUniformBuffers'The total number of descriptors with a descriptorType of !VK_DESCRIPTOR_TYPE_STORAGE_BUFFER and )VK_DESCRIPTOR_TYPE_STORAGE_BUFFER_DYNAMICB accessible to any given shader stage across all elements of  pSetLayouts must$ be less than or equal to /VkPhysicalDeviceDescriptorIndexingPropertiesEXT::2maxPerStageDescriptorUpdateAfterBindStorageBuffers'The total number of descriptors with a descriptorType of )VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLER,  VK_DESCRIPTOR_TYPE_SAMPLED_IMAGE , and 'VK_DESCRIPTOR_TYPE_UNIFORM_TEXEL_BUFFERB accessible to any given shader stage across all elements of  pSetLayouts must$ be less than or equal to /VkPhysicalDeviceDescriptorIndexingPropertiesEXT::1maxPerStageDescriptorUpdateAfterBindSampledImages'The total number of descriptors with a descriptorType of  VK_DESCRIPTOR_TYPE_STORAGE_IMAGE , and 'VK_DESCRIPTOR_TYPE_STORAGE_TEXEL_BUFFERB accessible to any given shader stage across all elements of  pSetLayouts must$ be less than or equal to /VkPhysicalDeviceDescriptorIndexingPropertiesEXT::1maxPerStageDescriptorUpdateAfterBindStorageImages'The total number of descriptors with a descriptorType of #VK_DESCRIPTOR_TYPE_INPUT_ATTACHMENTB accessible to any given shader stage across all elements of  pSetLayouts must$ be less than or equal to /VkPhysicalDeviceDescriptorIndexingPropertiesEXT::4maxPerStageDescriptorUpdateAfterBindInputAttachmentsXThe total number of descriptors in descriptor set layouts created without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT bit set with a descriptorType of VK_DESCRIPTOR_TYPE_SAMPLER and )VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLERE accessible across all shader stages and across all elements of  pSetLayouts must$ be less than or equal to VkPhysicalDeviceLimits::maxDescriptorSetSamplersXThe total number of descriptors in descriptor set layouts created without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT bit set with a descriptorType of !VK_DESCRIPTOR_TYPE_UNIFORM_BUFFERO accessible across all shader stagess and and across all elements of  pSetLayouts must be less than or equal to VkPhysicalDeviceLimits::maxDescriptorSetUniformBuffersXThe total number of descriptors in descriptor set layouts created without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT bit set with a descriptorType of )VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER_DYNAMICE accessible across all shader stages and across all elements of  pSetLayouts must$ be less than or equal to VkPhysicalDeviceLimits::%maxDescriptorSetUniformBuffersDynamicXThe total number of descriptors in descriptor set layouts created without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT bit set with a descriptorType of !VK_DESCRIPTOR_TYPE_STORAGE_BUFFERJ accessible across all shader stages and across all elements of  pSetLayouts must be less than or equal to VkPhysicalDeviceLimits::maxDescriptorSetStorageBuffersXThe total number of descriptors in descriptor set layouts created without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT bit set with a descriptorType of )VK_DESCRIPTOR_TYPE_STORAGE_BUFFER_DYNAMICE accessible across all shader stages and across all elements of  pSetLayouts must$ be less than or equal to VkPhysicalDeviceLimits::%maxDescriptorSetStorageBuffersDynamicXThe total number of descriptors in descriptor set layouts created without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT bit set with a descriptorType of )VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLER,  VK_DESCRIPTOR_TYPE_SAMPLED_IMAGE , and 'VK_DESCRIPTOR_TYPE_UNIFORM_TEXEL_BUFFERE accessible across all shader stages and across all elements of  pSetLayouts must$ be less than or equal to VkPhysicalDeviceLimits::maxDescriptorSetSampledImagesXThe total number of descriptors in descriptor set layouts created without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT bit set with a descriptorType of  VK_DESCRIPTOR_TYPE_STORAGE_IMAGE , and 'VK_DESCRIPTOR_TYPE_STORAGE_TEXEL_BUFFERE accessible across all shader stages and across all elements of  pSetLayouts must$ be less than or equal to VkPhysicalDeviceLimits::maxDescriptorSetStorageImagesXThe total number of descriptors in descriptor set layouts created without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT bit set with a descriptorType of #VK_DESCRIPTOR_TYPE_INPUT_ATTACHMENTJ accessible across all shader stages and across all elements of  pSetLayouts must be less than or equal to VkPhysicalDeviceLimits:: maxDescriptorSetInputAttachments1The total number of descriptors of the type VK_DESCRIPTOR_TYPE_SAMPLER and )VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLERE accessible across all shader stages and across all elements of  pSetLayouts must$ be less than or equal to /VkPhysicalDeviceDescriptorIndexingPropertiesEXT::'maxDescriptorSetUpdateAfterBindSamplers1The total number of descriptors of the type !VK_DESCRIPTOR_TYPE_UNIFORM_BUFFERJ accessible across all shader stagess and and across all elements of  pSetLayouts must$ be less than or equal to /VkPhysicalDeviceDescriptorIndexingPropertiesEXT::-maxDescriptorSetUpdateAfterBindUniformBuffers1The total number of descriptors of the type )VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER_DYNAMICE accessible across all shader stages and across all elements of  pSetLayouts must$ be less than or equal to /VkPhysicalDeviceDescriptorIndexingPropertiesEXT::4maxDescriptorSetUpdateAfterBindUniformBuffersDynamic1The total number of descriptors of the type !VK_DESCRIPTOR_TYPE_STORAGE_BUFFERE accessible across all shader stages and across all elements of  pSetLayouts must$ be less than or equal to /VkPhysicalDeviceDescriptorIndexingPropertiesEXT::-maxDescriptorSetUpdateAfterBindStorageBuffers1The total number of descriptors of the type )VK_DESCRIPTOR_TYPE_STORAGE_BUFFER_DYNAMICE accessible across all shader stages and across all elements of  pSetLayouts must$ be less than or equal to /VkPhysicalDeviceDescriptorIndexingPropertiesEXT::4maxDescriptorSetUpdateAfterBindStorageBuffersDynamic1The total number of descriptors of the type )VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLER,  VK_DESCRIPTOR_TYPE_SAMPLED_IMAGE , and 'VK_DESCRIPTOR_TYPE_UNIFORM_TEXEL_BUFFERE accessible across all shader stages and across all elements of  pSetLayouts must$ be less than or equal to /VkPhysicalDeviceDescriptorIndexingPropertiesEXT::,maxDescriptorSetUpdateAfterBindSampledImages1The total number of descriptors of the type  VK_DESCRIPTOR_TYPE_STORAGE_IMAGE , and 'VK_DESCRIPTOR_TYPE_STORAGE_TEXEL_BUFFERE accessible across all shader stages and across all elements of  pSetLayouts must$ be less than or equal to /VkPhysicalDeviceDescriptorIndexingPropertiesEXT::,maxDescriptorSetUpdateAfterBindStorageImages1The total number of descriptors of the type #VK_DESCRIPTOR_TYPE_INPUT_ATTACHMENTE accessible across all shader stages and across all elements of  pSetLayouts must$ be less than or equal to /VkPhysicalDeviceDescriptorIndexingPropertiesEXT::/maxDescriptorSetUpdateAfterBindInputAttachmentsAny two elements of pPushConstantRanges must$ not include the same stage in  stageFlags pSetLayouts mustQ not contain more than one descriptor set layout that was created with 7VK_DESCRIPTOR_SET_LAYOUT_CREATE_PUSH_DESCRIPTOR_BIT_KHR setValid Usage (Implicit)sType must be -VK_STRUCTURE_TYPE_PIPELINE_LAYOUT_CREATE_INFOpNext must be NULLflags must be 0If setLayoutCount is not 0,  pSetLayouts must( be a valid pointer to an array of setLayoutCount valid VkDescriptorSetLayout handlesIf pushConstantRangeCount is not 0, pPushConstantRanges must( be a valid pointer to an array of pushConstantRangeCount valid VkPushConstantRange structuresSee Also w,  x,  r, ,  { r@VkPushConstantRange - Structure specifying a push constant range Valid Usageoffset must be less than VkPhysicalDeviceLimits::maxPushConstantsSizeoffset must be a multiple of 4size must be greater than 0size must be a multiple of 4size must be less than or equal to VkPhysicalDeviceLimits::maxPushConstantsSize minus offsetValid Usage (Implicit) stageFlags must be a valid combination of  values stageFlags must not be 0See Also i,  h t stageFlags is a set of stage flags describing the shader stages that will access a range of push constants. If a particular stage is not included in the range, then accessing members of that range of push constants from the corresponding shader stage will result in undefined data being read. uoffset and sizeK are the start offset and size, respectively, consumed by the range. Both offset and size are in units of bytes and must[ be a multiple of 4. The layout of the push constant variables is specified in the shader. wGVkDescriptorSetLayout - Opaque handle to a descriptor set layout objectSee Also, ,  i, , /Dummy data to tag the  with x5VkPipelineLayoutCreateFlags - Reserved for future use DescriptionVkPipelineLayoutCreateFlagsQ is a bitmask type for setting a mask, but is currently reserved for future use.See Also i z:vkDestroyPipelineLayout - Destroy a pipeline layout object Parametersdevice9 is the logical device that destroys the pipeline layout.pipelineLayout# is the pipeline layout to destroy. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. Valid UsageIf VkAllocationCallbacks were provided when pipelineLayout1 was created, a compatible set of callbacks must be provided hereIf no VkAllocationCallbacks were provided when pipelineLayout was created,  pAllocator must be NULLValid Usage (Implicit)device must be a valid VkDevice handleIf pipelineLayout is not , pipelineLayout must be a valid VkPipelineLayout handleIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structureIf pipelineLayout is a valid handle, it must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to pipelineLayout must be externally synchronizedSee Also, ,  {=vkCreatePipelineLayout - Creates a new pipeline layout object Parametersdevice8 is the logical device that creates the pipeline layout. pCreateInfo) is a pointer to an instance of the  iC structure specifying the state of the pipeline layout object. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter.pPipelineLayout points to a VkPipelineLayoutG handle in which the resulting pipeline layout object is returned.Valid Usage (Implicit)device must be a valid VkDevice handle pCreateInfo must$ be a valid pointer to a valid VkPipelineLayoutCreateInfo structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structurepPipelineLayout must be a valid pointer to a VkPipelineLayout handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, , ,  i h i j k l m n o p q r s v u t w x y z { x y w { z r s v u t i j k l m n o p q hcNone "-KSTbejk)g `VkShaderStatisticsInfoAMD - Statistical information about a particular shader within a pipeline DescriptionkSome implementations may merge multiple logical shader stages together in a single shader. In such cases, shaderStageMask will contain a bitmask of all of the stages that are active within that shader. Consequently, if specifying those stages as input to  , the same output information may0 be returned for all such shader stage queries.)The number of available VGPRs and SGPRs (numAvailableVgprs and numAvailableSgprs respectively) are the shader-addressable subset of physical registers that is given as a limit to the compiler for register assignment. These values mayq further be limited by implementations due to performance optimizations where register pressure is a bottleneck.See Also ,  h shaderStageMaskL are the combination of logical shader stages contained within this shader.  resourceUsage is an instance of  D describing internal physical device resources used by this shader. numPhysicalVgprsq is the maximum number of vector instruction general-purpose registers (VGPRs) available to the physical device. numPhysicalSgprsq is the maximum number of scalar instruction general-purpose registers (SGPRs) available to the physical device. numAvailableVgprsF is the maximum limit of VGPRs made available to the shader compiler. numAvailableSgprsF is the maximum limit of SGPRs made available to the shader compiler. computeWorkGroupSizeG is the local workgroup size of this shader in { X, Y, Z } dimensions. bVkShaderResourceUsageAMD - Resource usage information about a particular shader within a pipelineSee Also  numUsedVgprsT is the number of vector instruction general-purpose registers used by this shader.  numUsedSgprsT is the number of scalar instruction general-purpose registers used by this shader. ldsSizePerLocalWorkGroup? is the maximum local data store size per work group in bytes. ldsUsageSizeInBytes? is the LDS usage size in bytes per work group by this shader. scratchMemUsageInBytes6 is the scratch memory usage in bytes by this shader. AvkGetShaderInfoAMD - Get information about a shader in a pipeline Parametersdevice is the device that created pipeline.pipeline is the target of the query. shaderStaged identifies the particular shader within the pipeline about which information is being queried.infoType5 describes what kind of information is being queried. pInfoSizeb is a pointer to a value related to the amount of data the query returns, as described below.pInfo) is either NULL or a pointer to a buffer. DescriptionIf pInfo is NULL1, then the maximum size of the information that can: be retrieved about the shader, in bytes, is returned in  pInfoSize . Otherwise,  pInfoSize mustY point to a variable set by the user to the size of the buffer, in bytes, pointed to by pInfoZ, and on return the variable is overwritten with the amount of data actually written to pInfo.If  pInfoSize$ is less than the maximum size that can3 be retrieved by the pipeline cache, then at most  pInfoSize bytes will be written to pInfo, and vkGetShaderInfoAMD will return  VK_INCOMPLETE.Not all information is available for every shader and implementations may not support all kinds of information for any shader. When a certain type of information is unavailable, the function returns VK_ERROR_FEATURE_NOT_PRESENT.LIf information is successfully and fully queried, the function will return  VK_SUCCESS.For "VK_SHADER_INFO_TYPE_STATISTICS_AMD, an instance of VkShaderStatisticsInfoAMD. will be written to the buffer pointed to by pInfo. This structure will be populated with statistics regarding the physical device resources used by that shader along with other miscellaneous information and is described in further detail below.For #VK_SHADER_INFO_TYPE_DISASSEMBLY_AMD, pInfo points to a UTF-8 null-terminated string containing human-readable disassembly. The exact formatting and contents of the disassembly string are vendor-specific.JThe formatting and contents of all other types of information, including VK_SHADER_INFO_TYPE_BINARY_AMDJ, are left to the vendor and are not further specified by this extension.Valid Usage (Implicit)device must be a valid VkDevice handlepipeline must be a valid  VkPipeline handle shaderStage must be a valid  valueinfoType must be a valid   value pInfoSize must be a valid pointer to a size_t valueIf the value referenced by  pInfoSize is not 0, and pInfo is not NULL, pInfo must( be a valid pointer to an array of  pInfoSize bytespipeline must6 have been created, allocated, or retrieved from device Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS  VK_INCOMPLETE ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_FEATURE_NOT_PRESENT VK_ERROR_OUT_OF_HOST_MEMORYSee Also, ,  ,   dNone"Kbejk) =VkSubgroupFeatureFlags - Bitmask of VkSubgroupFeatureFlagBits DescriptionVkSubgroupFeatureFlags7 is a bitmask type for setting a mask of zero or more  .See Also ,  aVkPhysicalDeviceSubgroupProperties - Structure describing subgroup support for an implementationMembersThe members of the "VkPhysicalDeviceSubgroupPropertiesC structure describe the following implementation-dependent limits: DescriptionsType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure. subgroupSizeN is the number of invocations in each subgroup. This will match any  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#interfaces-builtin-variables-sgs@SubgroupSize@P decorated variable used in any shader module created on this device.  subgroupSizeC is at least 1 if any of the physical device s queues support VK_QUEUE_GRAPHICS_BIT or VK_QUEUE_COMPUTE_BIT.supportedStages is a bitfield of H S describing the shader stages that subgroup operations are supported in. supportedStages will have the VK_SHADER_STAGE_COMPUTE_BITI bit set if any of any of the physical device s queues support VK_QUEUE_COMPUTE_BIT.supportedOperations is a bitmask of  P specifying the sets of subgroup operations supported on this device. supportedOperations will have the VK_SUBGROUP_FEATURE_BASIC_BITB bit set if any of the physical device s queues support VK_QUEUE_GRAPHICS_BIT or VK_QUEUE_COMPUTE_BIT.quadOperationsInAllStages* is a boolean that specifies whether  mhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-subgroup-quadquad subgroup operationsY are available in all stages, or are restricted to fragment and compute stages.Valid Usage (Implicit)sType must be 5VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_SUBGROUP_PROPERTIESIf the "VkPhysicalDeviceSubgroupProperties structure is included in the pNext chain of sf9, it is filled with the implementation-dependent limits.See AlsoVkBool32,  h, ,  SVkSubgroupFeatureFlagBits - Enum describing what subgroup operations are supportedSee Also VK_SUBGROUP_FEATURE_QUAD_BITJ specifies the device will accept SPIR-V shader modules that contain the GroupNonUniformQuad capability. !VK_SUBGROUP_FEATURE_CLUSTERED_BITJ specifies the device will accept SPIR-V shader modules that contain the GroupNonUniformClustered capability. (VK_SUBGROUP_FEATURE_SHUFFLE_RELATIVE_BITK specifies the device will accept SPIR-V shader modules that contain the GroupNonUniformShuffleRelative capability. VK_SUBGROUP_FEATURE_SHUFFLE_BITJ specifies the device will accept SPIR-V shader modules that contain the GroupNonUniformShuffle capability. VK_SUBGROUP_FEATURE_BALLOT_BITJ specifies the device will accept SPIR-V shader modules that contain the GroupNonUniformBallot capability. "VK_SUBGROUP_FEATURE_ARITHMETIC_BITJ specifies the device will accept SPIR-V shader modules that contain the GroupNonUniformArithmetic capability. VK_SUBGROUP_FEATURE_VOTE_BITJ specifies the device will accept SPIR-V shader modules that contain the GroupNonUniformVote capability. VK_SUBGROUP_FEATURE_BASIC_BITJ specifies the device will accept SPIR-V shader modules that contain the GroupNonUniform capability.  eNoneejk)S &VK_SUBGROUP_FEATURE_PARTITIONED_BIT_NVK specifies the device will accept SPIR-V shader modules that contain the GroupNonUniformPartitionedNV capability.  fNone "-KSTbejk+2R @VkMappedMemoryRange - Structure specifying a mapped memory range Valid Usagememory must be currently mappedIf size is not equal to  VK_WHOLE_SIZE, offset and size mustE specify a range contained within the currently mapped range of memoryIf size is equal to  VK_WHOLE_SIZE, offset must. be within the currently mapped range of memoryIf size is equal to  VK_WHOLE_SIZE), the end of the current mapping of memory must be a multiple of /::nonCoherentAtomSize4 bytes from the beginning of the memory object.offset must be a multiple of /::nonCoherentAtomSizeIf size is not equal to  VK_WHOLE_SIZE, size must# either be a multiple of /::nonCoherentAtomSize , or offset plus size must equal the size of memory.Valid Usage (Implicit)sType must be %VK_STRUCTURE_TYPE_MAPPED_MEMORY_RANGEpNext must be NULLmemory must be a valid VkDeviceMemory handleSee Also ,  VkDeviceSize, ,  ,  sType is the type of this structure. pNext is NULL1 or a pointer to an extension-specific structure. memory2 is the memory object to which this range belongs. offsetH is the zero-based byte offset from the beginning of the memory object. size! is either the size of range, or  VK_WHOLE_SIZE to affect the range from offset5 to the end of the current mapping of the allocation. NVkMemoryAllocateInfo - Structure containing parameters of a memory allocation DescriptionAn instance of the  5 structure defines a memory import operation if the pNextD chain contains an instance of one of the following structures: * 9 with non-zero  handleType value * 7 with a non-zero  handleType value * 8 with a non-zero  handleType value * 4 with a non-NULL buffer valueImporting memory must8 not modify the content of the memory. Implementations must ensure that importing memory does not enable the importing Vulkan instance to access any memory or resources in other Vulkan instances other than that corresponding to the memory object imported. Implementations must also ensure accessing imported memory which has not been initialized does not allow the importing Vulkan instance to obtain data from the exporting Vulkan instance or vice-versa.NoteHow exported and imported memory is isolated is left to the implementation, but applications should be aware that such isolation may prevent implementations from placing multiple exportable memory objects in the same physical or virtual page. Hence, applications shouldF avoid creating many small external memory objects whenever possible.When performing a memory import operation, it is the responsibility of the application to ensure the external handles meet all valid usage requirements. However, implementations mustn perform sufficient validation of external handles to ensure that the operation results in a valid memory object which will not cause program termination, device loss, queue stalls, or corruption of other resources when used as allowed according to its allocation parameters. If the external handle provided does not meet these requirements, the implementation must8 fail the memory import operation with the error code  VK_ERROR_INVALID_EXTERNAL_HANDLE. Valid UsageIf the pNext$ chain contains an instance of VkExportMemoryAllocateInfo0, and any of the handle types specified in VkExportMemoryAllocateInfo:: handleTypes: require a dedicated allocation, as reported by s in VkExternalImageFormatProperties::externalMemoryProperties::externalMemoryFeatures or VkExternalBufferProperties::externalMemoryProperties::externalMemoryFeatures , the pNext( chain must contain an instance of nD or k with either its image or buffer& field set to a value other than VK_NULL_HANDLE.If the pNext$ chain contains an instance of  , it must! not contain an instance of 1 or h.If the pNext$ chain contains an instance of 9 , it must! not contain an instance of h:.If the parameters define an import operation, the external handle specified was created by the Vulkan API, and the external handle type is 0VK_EXTERNAL_MEMORY_HANDLE_TYPE_OPAQUE_FD_BIT_KHR, then the values of allocationSize and memoryTypeIndex mustN match those specified when the memory object being imported was created.If the parameters define an import operation and the external handle specified was created by the Vulkan API, the device mask specified by A mustO match that specified when the memory object being imported was allocated.If the parameters define an import operation and the external handle specified was created by the Vulkan API, the list of physical devices that comprise the logical device passed to   must| match the list of physical devices that comprise the logical device on which the memory was originally allocated.If the parameters define an import operation and the external handle is an NT handle or a global share handle created outside of the Vulkan API, the value of memoryTypeIndex must' be one of those returned by d.If the parameters define an import operation, the external handle was created by the Vulkan API, and the external handle type is 3VK_EXTERNAL_MEMORY_HANDLE_TYPE_OPAQUE_WIN32_BIT_KHR or 7VK_EXTERNAL_MEMORY_HANDLE_TYPE_OPAQUE_WIN32_KMT_BIT_KHR, then the values of allocationSize and memoryTypeIndex mustN match those specified when the memory object being imported was created.RIf the parameters define an import operation and the external handle type is 0VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D11_TEXTURE_BIT, 4VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D11_TEXTURE_KMT_BIT , or 1VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D12_RESOURCE_BIT, allocationSize must@ match the size reported in the memory requirements of the image or buffer member of the instance of )VkDedicatedAllocationMemoryAllocateInfoNV included in the pNext chain.RIf the parameters define an import operation and the external handle type is -VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D12_HEAP_BIT, allocationSize musto match the size specified when creating the Direct3D 12 heap from which the external handle was extracted.If the parameters define an import operation and the external handle is a POSIX file descriptor created outside of the Vulkan API, the value of memoryTypeIndex must" be one of those returned by `.jIf the parameters define an import operation and the external handle is a host pointer, the value of memoryTypeIndex must' be one of those returned by a]If the parameters define an import operation and the external handle is a host pointer, allocationSize must be an integer multiple of /VkPhysicalDeviceExternalMemoryHostPropertiesEXT::minImportedHostPointerAlignmentWIf the parameters define an import operation and the external handle type is ;VK_EXTERNAL_MEMORY_HANDLE_TYPE_ANDROID_HARDWARE_BIT_ANDROID:allocationSize must be the size returned by G$ for the Android hardware bufferIf the pNext* chain doesn t contain an instance of nD or VkMemoryDedicatedAllocateInfo::image is ", the Android hardware buffer must have a format of AHARDWAREBUFFER_FORMAT_BLOB and a usage that includes %AHARDWAREBUFFER_USAGE_GPU_DATA_BUFFERmemoryTypeIndex must! be one of those returned by G$ for the Android hardware buffer=If the parameters do not define an import operation, and the pNext$ chain contains an instance of VkExportMemoryAllocateInfo with BVK_EXTERNAL_MEMORY_HANDLE_TYPE_ANDROID_HARDWARE_BUFFER_BIT_ANDROID included in its  handleTypes member, and the pNext# contains an instance of nD with image not equal to  , then allocationSize must be 0 , otherwise allocationSize must be greater than 0.nIf the parameters define an import operation, the external handle is an Android hardware buffer, and the pNext) chain includes an instance of nD with image that is not :$The Android hardware buffer s usage must include at least one of &AHARDWAREBUFFER_USAGE_GPU_COLOR_OUTPUT or 'AHARDWAREBUFFER_USAGE_GPU_SAMPLED_IMAGEThe image s format must be VK_FORMAT_UNDEFINED# or the format returned by G in ::format% for the Android hardware buffer.XThe image s and Android hardware buffer s width, height, and array layer dimensions must be the same4If the Android hardware buffer s usage includes )AHARDWAREBUFFER_USAGE_GPU_MIPMAP_COMPLETE$, the image must have # log2(max(width, height7))# + 1 mip levels, otherwise it must have exactly 1 mip level."Each bit set in the image s usage must be listed in  {https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-external-android-hardware-buffer-usage%AHardwareBuffer Usage Equivalence&, and if there is a corresponding AHARDWAREBUFFER_USAGE bit listed that bit must7 be included in the Android hardware buffer s usageValid Usage (Implicit)sType must be &VK_STRUCTURE_TYPE_MEMORY_ALLOCATE_INFOEach pNext: member of any structure (including this one) in the pNext chain must be either NULL/ or a pointer to a valid instance of k, , 1, , h, 4, 7, 8, 9, h:, A, or nDEach sType member in the pNext chain must be uniqueSee Also VkDeviceSize, ,  sType is the type of this structure. pNext is NULL1 or a pointer to an extension-specific structure. allocationSize' is the size of the allocation in bytes memoryTypeIndex1 is an index identifying a memory type from the  memoryTypes array of the /  structure 8VkDeviceMemory - Opaque handle to a device memory objectSee Alsop, p,  , G, H, I, r, r, i, g,  , j, j,  ,  , hc,  ,  0Dummy data to tag the  with *VkMemoryMapFlags - Reserved for future use DescriptionVkMemoryMapFlagsQ is a bitmask type for setting a mask, but is currently reserved for future use.See Also PvkGetDeviceMemoryCommitment - Query the current commitment for a VkDeviceMemory Parametersdevice, is the logical device that owns the memory.memory$ is the memory object being queried.pCommittedMemoryInBytes is a pointer to a  VkDeviceSizeZ value in which the number of bytes currently committed is returned, on success. DescriptionThe implementation mayJ update the commitment at any time, and the value returned by this query may be out of date.The implementation guarantees to allocate any committed memory from the heapIndex indicated by the memory type that the memory object was created with. Valid Usagememory must8 have been created with a memory type that reports 'VK_MEMORY_PROPERTY_LAZILY_ALLOCATED_BITValid Usage (Implicit)device must be a valid VkDevice handlememory must be a valid VkDeviceMemory handlepCommittedMemoryInBytes must be a valid pointer to a  VkDeviceSize valuememory must6 have been created, allocated, or retrieved from deviceSee Also,  ,  VkDeviceSize LvkInvalidateMappedMemoryRanges - Invalidate ranges of mapped memory objects Parametersdevice3 is the logical device that owns the memory ranges.memoryRangeCount is the length of the  pMemoryRanges array. pMemoryRanges is a pointer to an array of  < structures describing the memory ranges to invalidate. DescriptionvkInvalidateMappedMemoryRangesB guarantees that device writes to the memory ranges described by  pMemoryRanges', which have been made visible to the VK_ACCESS_HOST_WRITE_BIT and VK_ACCESS_HOST_READ_BIT  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-access-types access types, are made visible to the host. If a range of non-coherent memory is written by the host and then invalidated without first being flushed, its contents are undefined.Within each range described by  pMemoryRanges, each set of nonCoherentAtomSize bytes in that range is invalidated if any byte in that set has been written by the device since it was first mapped, or the last time it was invalidated.NoteMapping non-coherent memory does not implicitly invalidate the mapped memory, and device writes that have not been invalidated must; be made visible before the host reads or overwrites them.Valid Usage (Implicit)device must be a valid VkDevice handle pMemoryRanges must( be a valid pointer to an array of memoryRangeCount valid VkMappedMemoryRange structuresmemoryRangeCount must be greater than 0 Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also,  6vkFlushMappedMemoryRanges - Flush mapped memory ranges Parametersdevice3 is the logical device that owns the memory ranges.memoryRangeCount is the length of the  pMemoryRanges array. pMemoryRanges is a pointer to an array of  7 structures describing the memory ranges to flush. DescriptionvkFlushMappedMemoryRanges@ guarantees that host writes to the memory ranges described by  pMemoryRanges can* be made available to device access, via  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-dependencies-available-and-visibleavailability operations from the VK_ACCESS_HOST_WRITE_BIT  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-access-types access type.Within each range described by  pMemoryRanges, each set of nonCoherentAtomSize bytes in that range is flushed if any byte in that set has been written by the host since it was first mapped, or the last time it was flushed. If  pMemoryRanges includes sets of nonCoherentAtomSizeB bytes where no bytes have been written by the host, those bytes must not be flushed.wUnmapping non-coherent memory does not implicitly flush the mapped memory, and host writes that have not been flushed may> not ever be visible to the device. However, implementations must[ ensure that writes that have not been flushed do not become visible to any other memory.NoteThe above guarantee avoids a potential memory corruption in scenarios where host writes to a mapped memory object have not been flushed before the memory is unmapped (or freed), and the virtual address range is subsequently reused for a different mapping (or memory allocation).Valid Usage (Implicit)device must be a valid VkDevice handle pMemoryRanges must( be a valid pointer to an array of memoryRangeCount valid VkMappedMemoryRange structuresmemoryRangeCount must be greater than 0 Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also,  7vkUnmapMemory - Unmap a previously mapped memory object Parametersdevice, is the logical device that owns the memory.memory% is the memory object to be unmapped. Valid Usagememory must be currently mappedValid Usage (Implicit)device must be a valid VkDevice handlememory must be a valid VkDeviceMemory handlememory must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to memory must be externally synchronizedSee Also,  @vkMapMemory - Map a memory object into application address space Parametersdevice, is the logical device that owns the memory.memory is the VkDeviceMemory object to be mapped.offsetJ is a zero-based byte offset from the beginning of the memory object.size, is the size of the memory range to map, or  VK_WHOLE_SIZE to map from offset to the end of the allocation.flags is reserved for future use.ppData points to a pointer in which is returned a host-accessible pointer to the beginning of the mapped range. This pointer minus offset must be aligned to at least /::minMemoryMapAlignment. Description#It is an application error to call  vkMapMemory, on a memory object that is already mapped.Note vkMapMemory will fail if the implementation is unable to allocate an appropriately sized contiguous virtual address range, e.g. due to virtual address space fragmentation or platform limits. In such cases,  vkMapMemory must return VK_ERROR_MEMORY_MAP_FAILED. The application canv improve the likelihood of success by reducing the size of the mapped range and/or removing unneeded mappings using  VkUnmapMemory. vkMapMemory} does not check whether the device memory is currently in use before returning the host-accessible pointer. The application must guarantee that any previously submitted command that writes to this range has completed before the host reads from or writes to that range, and that any previously submitted command that reads from that range has completed before the host writes to that region (see  thttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-submission-host-writeshere_ for details on fulfilling such a guarantee). If the device memory was allocated without the $VK_MEMORY_PROPERTY_HOST_COHERENT_BIT set, these guarantees must0 be made for an extended range: the application must@ round down the start of the range to the nearest multiple of /::nonCoherentAtomSizeA, and round the end of the range up to the nearest multiple of /::nonCoherentAtomSize.While a range of device memory is mapped for host access, the application is responsible for synchronizing both device and host access to that memory range.NoteIt is important for the application developer to become meticulously familiar with all of the mechanisms described in the chapter on  ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization"Synchronization and Cache Control< as they are crucial to maintaining memory access ordering. Valid Usagememory must not be currently mappedoffset must be less than the size of memoryIf size is not equal to  VK_WHOLE_SIZE, size must be greater than 0If size is not equal to  VK_WHOLE_SIZE, size must/ be less than or equal to the size of the memory minus offsetmemory must8 have been created with a memory type that reports #VK_MEMORY_PROPERTY_HOST_VISIBLE_BITmemory must1 not have been allocated with multiple instances.Valid Usage (Implicit)device must be a valid VkDevice handlememory must be a valid VkDeviceMemory handleflags must be 0ppData must& be a valid pointer to a pointer valuememory must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to memory must be externally synchronized Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_MEMORY_MAP_FAILEDSee Also,  ,  VkDeviceSize,  !vkFreeMemory - Free device memory Parametersdevice, is the logical device that owns the memory.memory is the VkDeviceMemory object to be freed. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. Description/Before freeing a memory object, an application muste ensure the memory object is no longer in use by the device  for example by command buffers in the  pending state . The memory can remain bound to images or buffers at the time the memory object is freed, but any further use of them (on host or device) for anything other than destroying those objects will result in undefined behavior. If there are still any bound images or buffers, the memory may9 not be immediately released by the implementation, but must be released by the time all bound images and buffers have been destroyed. Once memory is released, it is returned to the heap from which it was allocated.RHow memory objects are bound to Images and Buffers is described in detail in the  chttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#resources-associationResource Memory Association section.QIf a memory object is mapped at the time it is freed, it is implicitly unmapped.NoteAs described  phttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-device-unmap-does-not-flushbelowf, host writes are not implicitly flushed when the memory object is unmapped, but the implementation mustR guarantee that writes that have not been flushed do not affect any other memory. Valid Usage%All submitted commands that refer to memory (via images or buffers) must have completed executionValid Usage (Implicit)device must be a valid VkDevice handleIf memory is not , memory must be a valid VkDeviceMemory handleIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structureIf memory is a valid handle, it must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to memory must be externally synchronizedSee Also, ,  )vkAllocateMemory - Allocate device memory Parametersdevice, is the logical device that owns the memory. pAllocateInfo) is a pointer to an instance of the  Z structure describing parameters of the allocation. A successful returned allocation must] use the requested parameters  no substitution is permitted by the implementation. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter.pMemory is a pointer to a VkDeviceMemoryI handle in which information about the allocated memory is returned. DescriptionAllocations returned by vkAllocateMemory% are guaranteed to meet any alignment requirement of the implementation. For example, if an implementation requires 128 byte alignment for images and 64 byte alignment for buffers, the device memory returned through this mechanism would be 128-byte aligned. This ensures that applications can correctly suballocate objects of different types (with potentially different alignment requirements) in the same memory object.5When memory is allocated, its contents are undefined.4The maximum number of valid memory allocations that can! exist simultaneously within a  mayO be restricted by implementation- or platform-dependent limits. If a call to  ` would cause the total number of allocations to exceed these limits, such a call will fail and must return VK_ERROR_TOO_MANY_OBJECTS. The  vhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-limits-maxMemoryAllocationCount@maxMemoryAllocationCount@3 feature describes the number of allocations that canA exist simultaneously before encountering these internal limits.Some platforms mayX have a limit on the maximum size of a single allocation. For example, certain systems may fail to create allocations with a size greater than or equal to 4GB. Such a limit is implementation-dependent, and if such a failure occurs then the error VK_ERROR_OUT_OF_DEVICE_MEMORY must, be returned. This limit is advertised in `::maxMemoryAllocationSize. Valid Usage pAllocateInfo->allocationSize must be less than or equal to / :: memoryHeaps[ pAllocateInfo->memoryTypeIndex].size as returned by /  for the / that device was created from. pAllocateInfo->memoryTypeIndex must be less than / ::memoryTypeCount as returned by /  for the / that device was created from.Valid Usage (Implicit)device must be a valid VkDevice handle pAllocateInfo must$ be a valid pointer to a valid VkMemoryAllocateInfo structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structurepMemory must be a valid pointer to a VkDeviceMemory handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_TOO_MANY_OBJECTS  VK_ERROR_INVALID_EXTERNAL_HANDLESee Also, ,  ,    gNone"bejk+S ^VkWin32KeyedMutexAcquireReleaseInfoNV - use Windows keyex mutex mechanism to synchronize workValid Usage (Implicit)sType must be ;VK_STRUCTURE_TYPE_WIN32_KEYED_MUTEX_ACQUIRE_RELEASE_INFO_NVIf  acquireCount is not 0,  pAcquireSyncs must( be a valid pointer to an array of  acquireCount valid VkDeviceMemory handlesIf  acquireCount is not 0,  pAcquireKeys must( be a valid pointer to an array of  acquireCount uint64_t valuesIf  acquireCount is not 0, pAcquireTimeoutMilliseconds must( be a valid pointer to an array of  acquireCount uint32_t valuesIf  releaseCount is not 0,  pReleaseSyncs must( be a valid pointer to an array of  releaseCount valid VkDeviceMemory handlesIf  releaseCount is not 0,  pReleaseKeys must( be a valid pointer to an array of  releaseCount uint64_t valuesBoth of the elements of  pAcquireSyncs, and the elements of  pReleaseSyncs that are valid handles must? have been created, allocated, or retrieved from the same VkDeviceSee Also ,   acquireCount! is the number of entries in the  pAcquireSyncs,  pAcquireKeys, and pAcquireTimeoutMilliseconds arrays.  pAcquireSyncs is a pointer to an array of  9 objects which were imported from Direct3D 11 resources.  pAcquireKeys is a pointer to an array of mutex key values to wait for prior to beginning the submitted work. Entries refer to the keyed mutex associated with the corresponding entries in  pAcquireSyncs. pAcquireTimeoutMillisecondsU is an array of timeout values, in millisecond units, for each acquire specified in  pAcquireKeys.  releaseCount! is the number of entries in the  pReleaseSyncs and  pReleaseKeys arrays.  pReleaseSyncs is a pointer to an array of  9 objects which were imported from Direct3D 11 resources.  pReleaseKeys is a pointer to an array of mutex key values to set when the submitted work has completed. Entries refer to the keyed mutex associated with the corresponding entries in  pReleaseSyncs.  hNone "-STbejk+ iVkExportMemoryWin32HandleInfoNV - specify security attributes and access rights for Win32 memory handles Description(If this structure is not present, or if  pAttributes is set to NULL*, default security descriptor values will be used, and child processes created by the application will not inherit the handle, as described in the MSDN documentation for Synchronization Object Security and Access Rights [1]. Further, if the structure is not present, the access rights will be 6DXGI_SHARED_RESOURCE_READ | DXGI_SHARED_RESOURCE_WRITE 1 Fhttps://msdn.microsoft.com/en-us/library/windows/desktop/ms686670.aspxValid Usage (Implicit)sType must be 4VK_STRUCTURE_TYPE_EXPORT_MEMORY_WIN32_HANDLE_INFO_NVIf  pAttributes is not NULL,  pAttributes must$ be a valid pointer to a valid SECURITY_ATTRIBUTES valueSee AlsosType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure. pAttributes is a pointer to a Windows SECURITY_ATTRIBUTES9 structure specifying security attributes of the handle.dwAccess is a DWORD( specifying access rights of the handle.ZVkImportMemoryWin32HandleInfoNV - import Win32 memory created on the same physical device DescriptionIf  handleType is 01, this structure is ignored by consumers of the fB structure it is chained from. Valid Usage handleType must not have more than one bit set.handle must< be a valid handle to memory, obtained as specified by  handleType.Valid Usage (Implicit)sType must be 4VK_STRUCTURE_TYPE_IMPORT_MEMORY_WIN32_HANDLE_INFO_NV handleType must be a valid combination of  valuesSee Also,  sType is the type of this structure. pNext is NULL1 or a pointer to an extension-specific structure.  handleType is 0 or a 0 value specifying the type of memory handle in handle. handle is a Windows HANDLE referring to the memory. Opaque dataKvkGetMemoryWin32HandleNV - retrieve Win32 handle to a device memory object Parametersdevice, is the logical device that owns the memory.memory is the VkDeviceMemory object. handleType is a bitmask of F containing a single bit specifying the type of handle requested.handle points to a Windows HANDLE& in which the handle is returned. Valid Usage handleType must be a flag specified in 1:: handleTypes when allocating memoryValid Usage (Implicit)device must be a valid VkDevice handlememory must be a valid VkDeviceMemory handle handleType must be a valid combination of  values handleType must not be 0pHandle must be a valid pointer to a HANDLE valuememory must6 have been created, allocated, or retrieved from device Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_TOO_MANY_OBJECTS VK_ERROR_OUT_OF_HOST_MEMORYSee Also,  ,           iNone"bejk+ncVkWin32KeyedMutexAcquireReleaseInfoKHR - Use the Windows keyed mutex mechanism to synchronize work Valid UsageEach member of  pAcquireSyncs and  pReleaseSyncs must9 be a device memory object imported by setting 9:: handleType to 0VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D11_TEXTURE_BIT or 4VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D11_TEXTURE_KMT_BIT.Valid Usage (Implicit)sType must be <VK_STRUCTURE_TYPE_WIN32_KEYED_MUTEX_ACQUIRE_RELEASE_INFO_KHRIf  acquireCount is not 0,  pAcquireSyncs must( be a valid pointer to an array of  acquireCount valid VkDeviceMemory handlesIf  acquireCount is not 0,  pAcquireKeys must( be a valid pointer to an array of  acquireCount uint64_t valuesIf  acquireCount is not 0, pAcquireTimeouts must( be a valid pointer to an array of  acquireCount uint32_t valuesIf  releaseCount is not 0,  pReleaseSyncs must( be a valid pointer to an array of  releaseCount valid VkDeviceMemory handlesIf  releaseCount is not 0,  pReleaseKeys must( be a valid pointer to an array of  releaseCount uint64_t valuesBoth of the elements of  pAcquireSyncs, and the elements of  pReleaseSyncs that are valid handles must? have been created, allocated, or retrieved from the same VkDeviceSee Also ,   acquireCount! is the number of entries in the  pAcquireSyncs,  pAcquireKeys, and pAcquireTimeoutMilliseconds arrays.! pAcquireSyncs is a pointer to an array of  9 objects which were imported from Direct3D 11 resources." pAcquireKeys is a pointer to an array of mutex key values to wait for prior to beginning the submitted work. Entries refer to the keyed mutex associated with the corresponding entries in  pAcquireSyncs.$ releaseCount! is the number of entries in the  pReleaseSyncs and  pReleaseKeys arrays.% pReleaseSyncs is a pointer to an array of  9 objects which were imported from Direct3D 11 resources.& pReleaseKeys is a pointer to an array of mutex key values to set when the submitted work has completed. Entries refer to the keyed mutex associated with the corresponding entries in  pReleaseSyncs. !"$%&#'())(' !"$%&#jNone"-STbjk,5p -?VkMemoryRequirements - Structure specifying memory requirementsSee Also VkDeviceSize, uK, 7, 5/size1 is the size, in bytes, of the memory allocation required for the resource.0 alignmentB is the alignment, in bytes, of the offset within the allocation required for the resource.1memoryTypeBits^ is a bitmask and contains one bit set for every supported memory type for the resource. Bit i( is set if and only if the memory type i in the  VkPhysicalDeviceMemoryPropertiesB structure for the physical device is supported for the resource.2)VkImage - Opaque handle to a image objectSee Alsop, k, -, u., u0, w2, nD, r , r, 4, , , , , , , , , !, 5, rZ, ], l1Dummy data to tag the  with3+VkBuffer - Opaque handle to a buffer objectSee Alsop, , u, , , k, , , nD, , , r, 6, , , , , , , , , l, , l, , , m, , , 72Dummy data to tag the  with49vkBindImageMemory - Bind device memory to an image object Parametersdevice6 is the logical device that owns the image and memory.image is the image.memory is the VkDeviceMemory4 object describing the device memory to attach. memoryOffset& is the start offset of the region of memoryR which is to be bound to the image. The number of bytes returned in the VkMemoryRequirements::size member in memory, starting from  memoryOffset- bytes, will be bound to the specified image. DescriptionvkBindImageMemory7 is equivalent to passing the same parameters through p to p>. Valid Usageimage must% not have been created with the VK_IMAGE_CREATE_DISJOINT_BIT set. image must) not already be backed by a memory objectimage must@ not have been created with any sparse memory binding flags memoryOffset must be less than the size of memorymemory mustG have been allocated using one of the memory types allowed in the memoryTypeBits member of the VkMemoryRequirements( structure returned from a call to vkGetImageMemoryRequirements with image memoryOffset must be an integer multiple of the  alignment member of the VkMemoryRequirements( structure returned from a call to vkGetImageMemoryRequirements with imageThe size member of the VkMemoryRequirements( structure returned from a call to vkGetImageMemoryRequirements with image must+ be less than or equal to the size of memory minus  memoryOffsetIf image6 requires a dedicated allocation (as reported by uX in nE'::requiresDedicatedAllocation for image), memory must have been created with nD::image equal to imageIf the VkMemoryAllocateInfo provided when memory1 was allocated included an instance of nD in its pNext chain, and nD::image was not VK_NULL_HANDLE, then image must equal nD::image and  memoryOffset must be zero.If image was created with k::dedicatedAllocation equal to VK_TRUE, memory must have been created with k::imageR equal to an image handle created with identical creation parameters to image and  memoryOffset must be zeroValid Usage (Implicit)device must be a valid VkDevice handleimage must be a valid VkImage handlememory must be a valid VkDeviceMemory handleimage must6 have been created, allocated, or retrieved from devicememory must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to image must be externally synchronized Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also,  ,  VkDeviceSize, 25[vkGetImageMemoryRequirements - Returns the memory requirements for specified Vulkan object Parametersdevice+ is the logical device that owns the image.image is the image to query.pMemoryRequirements# points to an instance of the -R structure in which the memory requirements of the image object are returned. Valid Usageimage must% not have been created with the VK_IMAGE_CREATE_DISJOINT_BIT flag setValid Usage (Implicit)device must be a valid VkDevice handleimage must be a valid VkImage handlepMemoryRequirements must be a valid pointer to a VkMemoryRequirements structureimage must6 have been created, allocated, or retrieved from deviceSee Also, 2, -6:vkBindBufferMemory - Bind device memory to a buffer object Parametersdevice7 is the logical device that owns the buffer and memory.buffer( is the buffer to be attached to memory.memory is a VkDeviceMemory4 object describing the device memory to attach. memoryOffset& is the start offset of the region of memoryS which is to be bound to the buffer. The number of bytes returned in the VkMemoryRequirements::size member in memory, starting from  memoryOffset. bytes, will be bound to the specified buffer. DescriptionvkBindBufferMemory8 is equivalent to passing the same parameters through p to p<. Valid Usagebuffer must) not already be backed by a memory object buffer must@ not have been created with any sparse memory binding flags memoryOffset must be less than the size of memoryIf buffer was created with the (VK_BUFFER_USAGE_UNIFORM_TEXEL_BUFFER_BIT or (VK_BUFFER_USAGE_STORAGE_TEXEL_BUFFER_BIT,  memoryOffset must be a multiple of VkPhysicalDeviceLimits::minTexelBufferOffsetAlignmentIf buffer was created with the "VK_BUFFER_USAGE_UNIFORM_BUFFER_BIT,  memoryOffset must be a multiple of VkPhysicalDeviceLimits::minUniformBufferOffsetAlignmentIf buffer was created with the "VK_BUFFER_USAGE_STORAGE_BUFFER_BIT,  memoryOffset must be a multiple of VkPhysicalDeviceLimits::minStorageBufferOffsetAlignmentmemory mustG have been allocated using one of the memory types allowed in the memoryTypeBits member of the VkMemoryRequirements( structure returned from a call to vkGetBufferMemoryRequirements with buffer memoryOffset must be an integer multiple of the  alignment member of the VkMemoryRequirements( structure returned from a call to vkGetBufferMemoryRequirements with bufferThe size member of the VkMemoryRequirements( structure returned from a call to vkGetBufferMemoryRequirements with buffer must+ be less than or equal to the size of memory minus  memoryOffsetIf buffer5 requires a dedicated allocation(as reported by uI in nE'::requiresDedicatedAllocation for buffer), memory must have been created with nD::buffer equal to bufferIf the VkMemoryAllocateInfo provided when memory1 was allocated included an instance of nD in its pNext chain, and nD::buffer was not VK_NULL_HANDLE, then buffer must equal nD::buffer , and  memoryOffset must be zero.If buffer was created with k::dedicatedAllocation equal to VK_TRUE, memory must have been created with k::bufferR equal to a buffer handle created with identical creation parameters to buffer and  memoryOffset must be zeroValid Usage (Implicit)device must be a valid VkDevice handlebuffer must be a valid VkBuffer handlememory must be a valid VkDeviceMemory handlebuffer must6 have been created, allocated, or retrieved from devicememory must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to buffer must be externally synchronized Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also3, ,  ,  VkDeviceSize7\vkGetBufferMemoryRequirements - Returns the memory requirements for specified Vulkan object Parametersdevice, is the logical device that owns the buffer.buffer is the buffer to query.pMemoryRequirements# points to an instance of the -S structure in which the memory requirements of the buffer object are returned.Valid Usage (Implicit)device must be a valid VkDevice handlebuffer must be a valid VkBuffer handlepMemoryRequirements must be a valid pointer to a VkMemoryRequirements structurebuffer must6 have been created, allocated, or retrieved from deviceSee Also3, , - -./01234567 327654-./01kNone"bejk,g ;[VkDedicatedAllocationMemoryAllocateInfoNV - Specify a dedicated memory allocation resource Valid UsageAt least one of image and buffer must be If image is not , the image must have been created with &VkDedicatedAllocationImageCreateInfoNV::dedicatedAllocation equal to VK_TRUEIf buffer is not  , the buffer must" have been created with 'VkDedicatedAllocationBufferCreateInfoNV::dedicatedAllocation equal to VK_TRUEIf image is not , VkMemoryAllocateInfo::allocationSize must equal the VkMemoryRequirements::size of the imageIf buffer is not , VkMemoryAllocateInfo::allocationSize must equal the VkMemoryRequirements::size of the bufferIf image is not  and fBC defines a memory import operation, the memory being imported must/ also be a dedicated image allocation and image mustD be identical to the image associated with the imported memory.If buffer is not  and fBC defines a memory import operation, the memory being imported must0 also be a dedicated buffer allocation and buffer mustE be identical to the buffer associated with the imported memory.Valid Usage (Implicit)sType must be >VK_STRUCTURE_TYPE_DEDICATED_ALLOCATION_MEMORY_ALLOCATE_INFO_NVIf image is not , image must be a valid VkImage handleIf buffer is not , buffer must be a valid VkBuffer handleBoth of buffer, and image that are valid handles must? have been created, allocated, or retrieved from the same VkDeviceSee Also3, 2, =sType is the type of this structure.>pNext is NULL1 or a pointer to an extension-specific structure.?image is = or a handle of an image which this memory will be bound to.@buffer is = or a handle of a buffer which this memory will be bound to.AhVkDedicatedAllocationBufferCreateInfoNV - Specify that a buffer is bound to a dedicated memory resourceValid Usage (Implicit)sType must be <VK_STRUCTURE_TYPE_DEDICATED_ALLOCATION_BUFFER_CREATE_INFO_NVSee AlsoVkBool32, CsType is the type of this structure.DpNext is NULL1 or a pointer to an extension-specific structure.EdedicatedAllocationL specifies whether the buffer will have a dedicated allocation bound to it.FgVkDedicatedAllocationImageCreateInfoNV - Specify that an image is bound to a dedicated memory resource DescriptionNote\Using a dedicated allocation for color and depth/stencil attachments or other large images may% improve performance on some devices. Valid UsageIf dedicatedAllocation is VK_TRUE, VkImageCreateInfo::flags must not include "VK_IMAGE_CREATE_SPARSE_BINDING_BIT, $VK_IMAGE_CREATE_SPARSE_RESIDENCY_BIT , or "VK_IMAGE_CREATE_SPARSE_ALIASED_BITValid Usage (Implicit)sType must be ;VK_STRUCTURE_TYPE_DEDICATED_ALLOCATION_IMAGE_CREATE_INFO_NVSee AlsoVkBool32, HsType is the type of this structure.IpNext is NULL1 or a pointer to an extension-specific structure.JdedicatedAllocationK specifies whether the image will have a dedicated allocation bound to it.;<=>?@ABCDEFGHIJKLMNOONMLKFGHIJABCDE;<=>?@lNone-STejk-MYnvkCmdDrawIndexedIndirectCountAMD - Perform an indexed indirect draw with the draw count sourced from a buffer Parameters commandBuffer? is the command buffer into which the command is recorded.buffer* is the buffer containing draw parameters.offset is the byte offset into buffer where parameters begin. countBuffer) is the buffer containing the draw count.countBufferOffset is the byte offset into  countBuffer" where the draw count begins. maxDrawCount specifies the maximum number of draws that will be executed. The actual number of executed draw calls is the minimum of the count specified in  countBuffer and  maxDrawCount.strideD is the byte stride between successive sets of draw parameters. Description vkCmdDrawIndexedIndirectCountAMD behaves similarly to  except that the draw count is read by the device from a buffer during execution. The command will read an unsigned 32-bit integer from  countBuffer located at countBufferOffset! and use this as the draw count. Valid UsageIf buffer is non-sparse then it must7 be bound completely and contiguously to a single VkDeviceMemory objectbuffer must! have been created with the #VK_BUFFER_USAGE_INDIRECT_BUFFER_BIT bit setIf  countBuffer is non-sparse then it must7 be bound completely and contiguously to a single VkDeviceMemory object countBuffer must! have been created with the #VK_BUFFER_USAGE_INDIRECT_BUFFER_BIT bit setoffset must be a multiple of 4countBufferOffset must be a multiple of 4stride must be a multiple of 4 and must" be greater than or equal to sizeof(VkDrawIndirectCommand)If  maxDrawCount is greater than or equal to 1, (stride ( maxDrawCount - 1) + offset + sizeof(VkDrawIndirectCommand)) must& be less than or equal to the size of buffer If the  yhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-drawIndirectFirstInstancedrawIndirectFirstInstance& feature is not enabled, all the  firstInstance members of the VkDrawIndexedIndirectCommand* structures accessed by this command must be 0The current render pass must be  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#renderpass-compatibility compatible with the  renderPass member of the VkGraphicsPipelineCreateInfo, structure specified when creating the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS.-The subpass index of the current render pass must be equal to the subpass member of the VkGraphicsPipelineCreateInfo, structure specified when creating the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS. For each set n that is statically used by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS, a descriptor set must have been bound to n at VK_PIPELINE_BIND_POINT_GRAPHICS, with a VkPipelineLayout that is compatible for set n, with the VkPipelineLayout used to create the current  VkPipeline, as described in jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-compatibility1{html_spec_relative}#descriptorsets-compatibility6For each push constant that is statically used by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS, a push constant value must have been set for VK_PIPELINE_BIND_POINT_GRAPHICS, with a VkPipelineLayout6 that is compatible for push constants, with the VkPipelineLayout used to create the current  VkPipeline, as described in jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-compatibility1{html_spec_relative}#descriptorsets-compatibility=Descriptors in each bound descriptor set, specified via vkCmdBindDescriptorSets, must8 be valid if they are statically used by the bound  VkPipeline object, specified via vkCmdBindPipelineyAll vertex input bindings accessed via vertex input variables declared in the vertex shader entry point s interface must have valid buffers boundA valid graphics pipeline must2 be bound to the current command buffer with VK_PIPELINE_BIND_POINT_GRAPHICSIf the  VkPipeline object bound to VK_PIPELINE_BIND_POINT_GRAPHICS- requires any dynamic state, that state must, have been set on the current command bufferIf count stored in  countBuffer is equal to 1, (offset + sizeof(VkDrawIndexedIndirectCommand)) must+ be less than or equal to the size of bufferIf count stored in  countBuffer is greater than 1, (stride ( drawCount - 1) + offset + sizeof(VkDrawIndexedIndirectCommand)) must+ be less than or equal to the size of buffer drawCount must be less than or equal to VkPhysicalDeviceLimits::maxDrawIndirectCount3Every input attachment used by the current subpass must3 be bound to the pipeline via a descriptor setIf any  VkSampler3 object that is accessed from a shader by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS( uses unnormalized coordinates, it must% not be used to sample from any VkImage with a  VkImageView of the type VK_IMAGE_VIEW_TYPE_3D, VK_IMAGE_VIEW_TYPE_CUBE, VK_IMAGE_VIEW_TYPE_1D_ARRAY, VK_IMAGE_VIEW_TYPE_2D_ARRAY or VK_IMAGE_VIEW_TYPE_CUBE_ARRAY, in any shader stageIf any  VkSampler3 object that is accessed from a shader by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS( uses unnormalized coordinates, it must) not be used with any of the SPIR-V OpImageSample* or OpImageSparseSample* instructions with  ImplicitLod, Dref or Proj# in their name, in any shader stageIf any  VkSampler3 object that is accessed from a shader by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS( uses unnormalized coordinates, it must) not be used with any of the SPIR-V OpImageSample* or OpImageSparseSample*U instructions that includes a LOD bias or any offset values, in any shader stageIf the  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-robustBufferAccessrobust buffer access: feature is not enabled, and any shader stage in the  VkPipeline object bound to VK_PIPELINE_BIND_POINT_GRAPHICS$ accesses a uniform buffer, it musta not access values outside of the range of that buffer specified in the bound descriptor setIf the  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-robustBufferAccessrobust buffer access: feature is not enabled, and any shader stage in the  VkPipeline object bound to VK_PIPELINE_BIND_POINT_GRAPHICS$ accesses a storage buffer, it musta not access values outside of the range of that buffer specified in the bound descriptor setAny  VkImageView being sampled with VK_FILTER_LINEAR" as a result of this command mustO be of a format which supports linear filtering, as specified by the 1VK_FORMAT_FEATURE_SAMPLED_IMAGE_FILTER_LINEAR_BIT flag in VkFormatProperties::linearTilingFeatures (for a linear image) or VkFormatProperties::optimalTilingFeatures0(for an optimally tiled image) returned by #vkGetPhysicalDeviceFormatPropertiesGImage subresources used as attachments in the current render pass mustM not be accessed in any way other than as an attachment by this command.jIf the draw is recorded in a render pass instance with multiview enabled, the maximum instance index must be less than or equal to d::maxMultiviewInstanceIndex.5If the bound graphics pipeline was created with [::sampleLocationsEnable set to VK_TRUES and the current subpass has a depth/stencil attachment, then that attachment must! have been created with the 9VK_IMAGE_CREATE_SAMPLE_LOCATIONS_COMPATIBLE_DEPTH_BIT_EXT bit setValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handlebuffer must be a valid VkBuffer handle countBuffer must be a valid VkBuffer handle commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must! support graphics operations This command must0 only be called inside of a render pass instanceEach of buffer,  commandBuffer, and  countBuffer must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Inside  Graphics  Graphics See Also3, ,  VkDeviceSizeZ_vkCmdDrawIndirectCountAMD - Perform an indirect draw with the draw count sourced from a buffer Parameters commandBuffer? is the command buffer into which the command is recorded.buffer* is the buffer containing draw parameters.offset is the byte offset into buffer where parameters begin. countBuffer) is the buffer containing the draw count.countBufferOffset is the byte offset into  countBuffer" where the draw count begins. maxDrawCount specifies the maximum number of draws that will be executed. The actual number of executed draw calls is the minimum of the count specified in  countBuffer and  maxDrawCount.strideD is the byte stride between successive sets of draw parameters. DescriptionvkCmdDrawIndirectCountAMD behaves similarly to  except that the draw count is read by the device from a buffer during execution. The command will read an unsigned 32-bit integer from  countBuffer located at countBufferOffset! and use this as the draw count. Valid UsageIf buffer is non-sparse then it must7 be bound completely and contiguously to a single VkDeviceMemory objectbuffer must! have been created with the #VK_BUFFER_USAGE_INDIRECT_BUFFER_BIT bit setIf  countBuffer is non-sparse then it must7 be bound completely and contiguously to a single VkDeviceMemory object countBuffer must! have been created with the #VK_BUFFER_USAGE_INDIRECT_BUFFER_BIT bit setoffset must be a multiple of 4countBufferOffset must be a multiple of 4stride must be a multiple of 4 and must" be greater than or equal to sizeof(VkDrawIndirectCommand)If  maxDrawCount is greater than or equal to 1, (stride ( maxDrawCount - 1) + offset + sizeof(VkDrawIndirectCommand)) must& be less than or equal to the size of buffer If the  yhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-drawIndirectFirstInstancedrawIndirectFirstInstance& feature is not enabled, all the  firstInstance members of the VkDrawIndirectCommand% structures accessed by this command must be 0The current render pass must be  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#renderpass-compatibility compatible with the  renderPass member of the VkGraphicsPipelineCreateInfo, structure specified when creating the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS.-The subpass index of the current render pass must be equal to the subpass member of the VkGraphicsPipelineCreateInfo, structure specified when creating the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS. For each set n that is statically used by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS, a descriptor set must have been bound to n at VK_PIPELINE_BIND_POINT_GRAPHICS, with a VkPipelineLayout that is compatible for set n, with the VkPipelineLayout used to create the current  VkPipeline, as described in jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-compatibility1{html_spec_relative}#descriptorsets-compatibility6For each push constant that is statically used by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS, a push constant value must have been set for VK_PIPELINE_BIND_POINT_GRAPHICS, with a VkPipelineLayout6 that is compatible for push constants, with the VkPipelineLayout used to create the current  VkPipeline, as described in jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-compatibility1{html_spec_relative}#descriptorsets-compatibility=Descriptors in each bound descriptor set, specified via vkCmdBindDescriptorSets, must8 be valid if they are statically used by the bound  VkPipeline object, specified via vkCmdBindPipelineyAll vertex input bindings accessed via vertex input variables declared in the vertex shader entry point s interface must have valid buffers boundA valid graphics pipeline must2 be bound to the current command buffer with VK_PIPELINE_BIND_POINT_GRAPHICSIf the  VkPipeline object bound to VK_PIPELINE_BIND_POINT_GRAPHICS- requires any dynamic state, that state must, have been set on the current command bufferIf the count stored in  countBuffer is equal to 1, (offset + sizeof(VkDrawIndirectCommand)) must+ be less than or equal to the size of bufferIf the count stored in  countBuffer is greater than 1, (stride ( drawCount - 1) + offset + sizeof(VkDrawIndirectCommand)) must& be less than or equal to the size of bufferThe count stored in  countBuffer must be less than or equal to VkPhysicalDeviceLimits::maxDrawIndirectCount3Every input attachment used by the current subpass must3 be bound to the pipeline via a descriptor setIf any  VkSampler3 object that is accessed from a shader by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS( uses unnormalized coordinates, it must% not be used to sample from any VkImage with a  VkImageView of the type VK_IMAGE_VIEW_TYPE_3D, VK_IMAGE_VIEW_TYPE_CUBE, VK_IMAGE_VIEW_TYPE_1D_ARRAY, VK_IMAGE_VIEW_TYPE_2D_ARRAY or VK_IMAGE_VIEW_TYPE_CUBE_ARRAY, in any shader stageIf any  VkSampler3 object that is accessed from a shader by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS( uses unnormalized coordinates, it must) not be used with any of the SPIR-V OpImageSample* or OpImageSparseSample* instructions with  ImplicitLod, Dref or Proj# in their name, in any shader stageIf any  VkSampler3 object that is accessed from a shader by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS( uses unnormalized coordinates, it must) not be used with any of the SPIR-V OpImageSample* or OpImageSparseSample*U instructions that includes a LOD bias or any offset values, in any shader stageIf the  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-robustBufferAccessrobust buffer access: feature is not enabled, and any shader stage in the  VkPipeline object bound to VK_PIPELINE_BIND_POINT_GRAPHICS$ accesses a uniform buffer, it musta not access values outside of the range of that buffer specified in the bound descriptor setIf the  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-robustBufferAccessrobust buffer access: feature is not enabled, and any shader stage in the  VkPipeline object bound to VK_PIPELINE_BIND_POINT_GRAPHICS$ accesses a storage buffer, it musta not access values outside of the range of that buffer specified in the bound descriptor setAny  VkImageView being sampled with VK_FILTER_LINEAR" as a result of this command mustO be of a format which supports linear filtering, as specified by the 1VK_FORMAT_FEATURE_SAMPLED_IMAGE_FILTER_LINEAR_BIT flag in VkFormatProperties::linearTilingFeatures (for a linear image) or VkFormatProperties::optimalTilingFeatures0(for an optimally tiled image) returned by #vkGetPhysicalDeviceFormatPropertiesGImage subresources used as attachments in the current render pass mustM not be accessed in any way other than as an attachment by this command.jIf the draw is recorded in a render pass instance with multiview enabled, the maximum instance index must be less than or equal to d::maxMultiviewInstanceIndex.5If the bound graphics pipeline was created with [::sampleLocationsEnable set to VK_TRUES and the current subpass has a depth/stencil attachment, then that attachment must! have been created with the 9VK_IMAGE_CREATE_SAMPLE_LOCATIONS_COMPATIBLE_DEPTH_BIT_EXT bit setValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handlebuffer must be a valid VkBuffer handle countBuffer must be a valid VkBuffer handle commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must! support graphics operations This command must0 only be called inside of a render pass instanceEach of buffer,  commandBuffer, and  countBuffer must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Inside  Graphics  Graphics See Also3, ,  VkDeviceSizeYZ[\\[ZYmNone-STejk. ]VvkCmdWriteBufferMarkerAMD - Execute a pipelined write of a marker value into a buffer Parameters commandBufferD is the command buffer into which the command will be recorded. pipelineStage is one of the \ values, specifying the pipeline stage whose completion triggers the marker write. dstBuffer3 is the buffer where the marker will be written to. dstOffsetM is the byte offset into the buffer where the marker will be written to.marker# is the 32-bit value of the marker. DescriptionThe command will write the 32-bit marker value into the buffer only after all preceding commands have finished executing up to at least the specified pipeline stage. This includes the completion of other preceding vkCmdWriteBufferMarkerAMD~ commands so long as their specified pipeline stages occur either at the same time or earlier than this command s specified  pipelineStage.5While consecutive buffer marker writes with the same  pipelineStage parameter are implicitly complete in submission order, memory and execution dependencies between buffer marker writes and other operations must still be explicitly ordered using synchronization commands. The access scope for buffer marker writes falls under the VK_ACCESS_TRANSFER_WRITE_BITE, and the pipeline stages for identifying the synchronization scope must include both  pipelineStage and VK_PIPELINE_STAGE_TRANSFER_BIT.Note Similar to vkCmdWriteTimestampW, if an implementation is unable to write a marker at any specific pipeline stage, it may- instead do so at any logically later stage.NoteImplementations may only support a limited number of pipelined marker write operations in flight at a given time, thus excessive number of marker write operations may' degrade command execution performance. Valid Usage dstOffset must& be less than or equal to the size of  dstBuffer minus 4. dstBuffer must have been created with  VK_BUFFER_USAGE_TRANSFER_DST_BIT usage flagIf  dstBuffer is non-sparse then it must7 be bound completely and contiguously to a single VkDeviceMemory object dstOffset must be a multiple of 4Valid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle pipelineStage must be a valid  value dstBuffer must be a valid VkBuffer handle commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must7 support transfer, graphics, or compute operationsBoth of  commandBuffer, and  dstBuffer must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type I Primary Secondary F Both 7 Transfer Graphics Compute v Transfer See Also3, ,  VkDeviceSize, ]^__^]nNone"bejk.{ `OVkMemoryDedicatedAllocateInfo - Specify a dedicated memory allocation resource Valid UsageAt least one of image and buffer must be  If image is not , VkMemoryAllocateInfo::allocationSize must equal the VkMemoryRequirements::size of the imageIf image is not , image must have been created without "VK_IMAGE_CREATE_SPARSE_BINDING_BIT set in VkImageCreateInfo::flagsIf buffer is not , VkMemoryAllocateInfo::allocationSize must equal the VkMemoryRequirements::size of the bufferIf buffer is not , buffer must have been created without #VK_BUFFER_CREATE_SPARSE_BINDING_BIT set in ::flagsIf image is not VK_NULL_HANDLE and fB> defines a memory import operation with handle type /VK_EXTERNAL_MEMORY_HANDLE_TYPE_OPAQUE_WIN32_BIT, 3VK_EXTERNAL_MEMORY_HANDLE_TYPE_OPAQUE_WIN32_KMT_BIT, 0VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D11_TEXTURE_BIT, 4VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D11_TEXTURE_KMT_BIT, -VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D12_HEAP_BIT , or 1VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D12_RESOURCE_BITb, and the external handle was created by the Vulkan API, then the memory being imported must* also be a dedicated image allocation and imageI must be identical to the image associated with the imported memory.If buffer is not  and fB> defines a memory import operation with handle type /VK_EXTERNAL_MEMORY_HANDLE_TYPE_OPAQUE_WIN32_BIT, 3VK_EXTERNAL_MEMORY_HANDLE_TYPE_OPAQUE_WIN32_KMT_BIT, 0VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D11_TEXTURE_BIT, 4VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D11_TEXTURE_KMT_BIT, -VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D12_HEAP_BIT , or 1VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D12_RESOURCE_BITb, and the external handle was created by the Vulkan API, then the memory being imported must+ also be a dedicated buffer allocation and bufferJ must be identical to the buffer associated with the imported memory.If image is not VK_NULL_HANDLE and fB> defines a memory import operation with handle type ,VK_EXTERNAL_MEMORY_HANDLE_TYPE_OPAQUE_FD_BIT!, the memory being imported must* also be a dedicated image allocation and imageI must be identical to the image associated with the imported memory.If buffer is not VK_NULL_HANDLE and fB> defines a memory import operation with handle type ,VK_EXTERNAL_MEMORY_HANDLE_TYPE_OPAQUE_FD_BIT!, the memory being imported must+ also be a dedicated buffer allocation and bufferJ must be identical to the buffer associated with the imported memory.If image is not , image must! not have been created with VK_IMAGE_CREATE_DISJOINT_BIT set in *::flagsValid Usage (Implicit)sType must be 0VK_STRUCTURE_TYPE_MEMORY_DEDICATED_ALLOCATE_INFOIf image is not , image must be a valid VkImage handleIf buffer is not , buffer must be a valid VkBuffer handleBoth of buffer, and image that are valid handles must? have been created, allocated, or retrieved from the same VkDeviceSee Also3, 2, bsType is the type of this structure.cpNext is NULL1 or a pointer to an extension-specific structure.dimage is = or a handle of an image which this memory will be bound to.ebuffer is = or a handle of a buffer which this memory will be bound to.fuVkMemoryDedicatedRequirements - Structure describing dedicated allocation requirements of buffer and image resources DescriptionIf the VkMemoryDedicatedRequirements structure is included in the pNext chain of the uK structure passed as the pMemoryRequirements parameter of a vkGetBufferMemoryRequirements2 call, requiresDedicatedAllocation may be VK_TRUE' under one of the following conditions:The pNext chain of VkBufferCreateInfo for the call to vkCreateBufferG used to create the buffer being queried contained an instance of  VkExternalMemoryBufferCreateInfo5, and any of the handle types specified in  VkExternalMemoryBufferCreateInfo:: handleTypes9 requires dedicated allocation, as reported by  in VkExternalBufferProperties::externalMemoryProperties::externalMemoryFeatures , the requiresDedicatedAllocation field will be set to VK_TRUE.In all other cases, requiresDedicatedAllocation must be set to VK_FALSE# by the implementation whenever a VkMemoryDedicatedRequirements structure is included in the pNext chain of the VkMemoryRequirements2 structure passed to a call to vkGetBufferMemoryRequirements2.If the VkMemoryDedicatedRequirements structure is included in the pNext chain of the VkMemoryRequirements2 structure passed as the pMemoryRequirements parameter of a vkGetBufferMemoryRequirements2 call and #VK_BUFFER_CREATE_SPARSE_BINDING_BIT was set in VkBufferCreateInfo::flags when buffer& was created then the implementation must set both prefersDedicatedAllocation and requiresDedicatedAllocation to VK_FALSE.If the VkMemoryDedicatedRequirements structure is included in the pNext chain of the VkMemoryRequirements2 structure passed as the pMemoryRequirements parameter of a vkGetImageMemoryRequirements2 call, requiresDedicatedAllocation may be VK_TRUE( under one of the following conditions:The pNext chain of VkImageCreateInfo for the call to  vkCreateImageF used to create the image being queried contained an instance of VkExternalMemoryImageCreateInfo0, and any of the handle types specified in VkExternalMemoryImageCreateInfo:: handleTypes9 requires dedicated allocation, as reported by s in VkExternalImageFormatProperties::externalMemoryProperties::externalMemoryFeatures , the requiresDedicatedAllocation field will be set to VK_TRUE.In all other cases, requiresDedicatedAllocation must be set to VK_FALSE# by the implementation whenever a VkMemoryDedicatedRequirements structure is included in the pNext chain of the VkMemoryRequirements2 structure passed to a call to vkGetImageMemoryRequirements2.If the VkMemoryDedicatedRequirements structure is included in the pNext chain of the VkMemoryRequirements2 structure passed as the pMemoryRequirements parameter of a vkGetImageMemoryRequirements2 call and "VK_IMAGE_CREATE_SPARSE_BINDING_BIT was set in VkImageCreateInfo::flags when image& was created then the implementation must set both prefersDedicatedAllocation and requiresDedicatedAllocation to VK_FALSE.Valid Usage (Implicit)sType must be /VK_STRUCTURE_TYPE_MEMORY_DEDICATED_REQUIREMENTSSee AlsoVkBool32, hsType is the type of this structure.ipNext is NULL1 or a pointer to an extension-specific structure.jprefersDedicatedAllocation specifies that the implementation would prefer a dedicated allocation for this resource. The application is still free to suballocate the resource but it may; get better performance if a dedicated allocation is used.krequiresDedicatedAllocationF specifies that a dedicated allocation is required for this resource.`abcdefghijklmmlfghijk`abcdeoNone-STejk.|ztuvwxyz{{zuytxwvpNone "-STbejk/! |LVkBindImageMemoryInfo - Structure specifying how to bind an image to memory Valid Usageimage must) not already be backed by a memory objectimage must@ not have been created with any sparse memory binding flags memoryOffset must be less than the size of memoryIf the pNext0 chain does not include an instance of the x structure, memory mustG have been allocated using one of the memory types allowed in the memoryTypeBits member of the j- structure returned from a call to uX with imageIf the pNext0 chain does not include an instance of the x structure,  memoryOffset must$ be an integer multiple of the  alignment member of the j- structure returned from a call to uX with imageIf the pNext0 chain does not include an instance of the x/ structure, the difference of the size of memory and  memoryOffset must! be greater than or equal to the size member of the j- structure returned from a call to uX with the same imageIf the pNext( chain includes an instance of the x structure, image must! have been created with the VK_IMAGE_CREATE_DISJOINT_BIT bit set.If the pNext( chain includes an instance of the x structure, memory mustG have been allocated using one of the memory types allowed in the memoryTypeBits member of the j- structure returned from a call to uX with image and the correct  planeAspect for this plane in the x/% structure attached to the u. s pNext chainIf the pNext( chain includes an instance of the x structure,  memoryOffset must$ be an integer multiple of the  alignment member of the j- structure returned from a call to uX with image and the correct  planeAspect for this plane in the x/% structure attached to the u. s pNext chainIf the pNext( chain includes an instance of the x/ structure, the difference of the size of memory and  memoryOffset must! be greater than or equal to the size member of the j- structure returned from a call to uX with the same image and the correct  planeAspect! for this plane in the x/% structure attached to the u. s pNext chainIf image6 requires a dedicated allocation (as reported by uX in nE'::requiresDedicatedAllocation for image), memory must have been created with nD::image equal to image and  memoryOffset must be zeroIf the VkMemoryAllocateInfo provided when memory1 was allocated included an instance of nD in its pNext chain, and nD::image was not VK_NULL_HANDLE, then image must equal nD::image and  memoryOffset must be zero.If image was created with k::dedicatedAllocation equal to VK_TRUE, memory must have been created with k::image equal to image and  memoryOffset must be zeroIf the pNext chain includes ^, all instances of memory specified by ^::pDeviceIndices must have been allocatedIf the pNext chain includes ^, and ^::splitInstanceBindRegionCount is not zero, then image must! have been created with the /VK_IMAGE_CREATE_SPLIT_INSTANCE_BIND_REGIONS_BIT bit setIf the pNext chain includes ^, all elements of ^::pSplitInstanceBindRegions must= be valid rectangles contained within the dimensions of imageIf the pNext chain includes ^6, the union of the areas of all elements of ^::pSplitInstanceBindRegions. that correspond to the same instance of image must cover the entire image.If image3 was created with a valid swapchain handle in 1:: swapchain, then the pNext chain must" include a valid instance of If the pNext$ chain includes an instance of , memory must be If the pNext, chain does not include an instance of , memory must be a valid VkDeviceMemory handleValid Usage (Implicit)sType must be (VK_STRUCTURE_TYPE_BIND_IMAGE_MEMORY_INFOEach pNext: member of any structure (including this one) in the pNext chain must be either NULL/ or a pointer to a valid instance of ^, , or xEach sType member in the pNext chain must be uniqueimage must be a valid VkImage handleBoth of image, and memory that are valid handles must? have been created, allocated, or retrieved from the same VkDeviceSee Also ,  VkDeviceSize, 2, , , q?~sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.image' is the image to be attached to memory.memory is a VkDeviceMemory0 object describing the device memory to attach. memoryOffset& is the start offset of the region of memoryJ which is to be bound to the image. The number of bytes returned in the VkMemoryRequirements::size member in memory, starting from  memoryOffset- bytes, will be bound to the specified image.MVkBindBufferMemoryInfo - Structure specifying how to bind a buffer to memory Valid Usagebuffer must) not already be backed by a memory object buffer must@ not have been created with any sparse memory binding flags memoryOffset must be less than the size of memoryIf buffer was created with the (VK_BUFFER_USAGE_UNIFORM_TEXEL_BUFFER_BIT or (VK_BUFFER_USAGE_STORAGE_TEXEL_BUFFER_BIT,  memoryOffset must be a multiple of VkPhysicalDeviceLimits::minTexelBufferOffsetAlignmentIf buffer was created with the "VK_BUFFER_USAGE_UNIFORM_BUFFER_BIT,  memoryOffset must be a multiple of VkPhysicalDeviceLimits::minUniformBufferOffsetAlignmentIf buffer was created with the "VK_BUFFER_USAGE_STORAGE_BUFFER_BIT,  memoryOffset must be a multiple of VkPhysicalDeviceLimits::minStorageBufferOffsetAlignmentmemory mustG have been allocated using one of the memory types allowed in the memoryTypeBits member of the VkMemoryRequirements( structure returned from a call to vkGetBufferMemoryRequirements with buffer memoryOffset must be an integer multiple of the  alignment member of the VkMemoryRequirements( structure returned from a call to vkGetBufferMemoryRequirements with bufferThe size member of the VkMemoryRequirements( structure returned from a call to vkGetBufferMemoryRequirements with buffer must+ be less than or equal to the size of memory minus  memoryOffsetIf buffer5 requires a dedicated allocation(as reported by uI in nE'::requiresDedicatedAllocation for buffer), memory must have been created with nD::buffer equal to buffer and  memoryOffset must be zeroIf the VkMemoryAllocateInfo provided when memory1 was allocated included an instance of nD in its pNext chain, and nD::buffer was not VK_NULL_HANDLE, then buffer must equal nD::buffer and  memoryOffset must be zero.If buffer was created with k::dedicatedAllocation equal to VK_TRUE, memory must have been created with k::buffer equal to buffer and  memoryOffset must be zeroIf the pNext chain includes ^, all instances of memory specified by ^::pDeviceIndices must have been allocatedValid Usage (Implicit)sType must be )VK_STRUCTURE_TYPE_BIND_BUFFER_MEMORY_INFOpNext must be NULL* or a pointer to a valid instance of ^buffer must be a valid VkBuffer handlememory must be a valid VkDeviceMemory handleBoth of buffer, and memory must? have been created, allocated, or retrieved from the same VkDeviceSee Also3,  ,  VkDeviceSize, , , q=sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.buffer( is the buffer to be attached to memory.memory is a VkDeviceMemory0 object describing the device memory to attach. memoryOffset& is the start offset of the region of memoryK which is to be bound to the buffer. The number of bytes returned in the VkMemoryRequirements::size member in memory, starting from  memoryOffset. bytes, will be bound to the specified buffer.8vkBindImageMemory2 - Bind device memory to image objects Parametersdevice7 is the logical device that owns the images and memory. bindInfoCount is the number of elements in  pBindInfos. pBindInfos5 is a pointer to an array of structures of type |', describing images and memory to bind. DescriptionOn some implementations, it mayC be more efficient to batch memory bindings into a single command.Valid Usage (Implicit)device must be a valid VkDevice handle pBindInfos must( be a valid pointer to an array of  bindInfoCount valid VkBindImageMemoryInfo structures bindInfoCount must be greater than 0 Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also|, :vkBindBufferMemory2 - Bind device memory to buffer objects Parametersdevice8 is the logical device that owns the buffers and memory. bindInfoCount is the number of elements in  pBindInfos. pBindInfos5 is a pointer to an array of structures of type (, describing buffers and memory to bind. DescriptionOn some implementations, it mayC be more efficient to batch memory bindings into a single command.Valid Usage (Implicit)device must be a valid VkDevice handle pBindInfos must( be a valid pointer to an array of  bindInfoCount valid VkBindBufferMemoryInfo structures bindInfoCount must be greater than 0 Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, |}~|}~qNone-STejk/".  rNone "-KSTbejk0DAVkSparseImageFormatFlags - Bitmask of VkSparseImageFormatFlagBits DescriptionVkSparseImageFormatFlags7 is a bitmask type for setting a mask of zero or more .See Also, ?VkSparseMemoryBindFlags - Bitmask of VkSparseMemoryBindFlagBits DescriptionVkSparseMemoryBindFlags7 is a bitmask type for setting a mask of zero or more .See Also, , 5VkImageAspectFlags - Bitmask of VkImageAspectFlagBits DescriptionVkImageAspectFlags7 is a bitmask type for setting a mask of zero or more .See Also, , , , w, , BVkBindSparseInfo - Structure specifying a sparse binding operationValid Usage (Implicit)sType must be "VK_STRUCTURE_TYPE_BIND_SPARSE_INFOpNext must be NULL* or a pointer to a valid instance of If waitSemaphoreCount is not 0, pWaitSemaphores must( be a valid pointer to an array of waitSemaphoreCount valid  VkSemaphore handlesIf bufferBindCount is not 0,  pBufferBinds must( be a valid pointer to an array of bufferBindCount valid VkSparseBufferMemoryBindInfo structuresIf imageOpaqueBindCount is not 0, pImageOpaqueBinds must( be a valid pointer to an array of imageOpaqueBindCount valid !VkSparseImageOpaqueMemoryBindInfo structuresIf imageBindCount is not 0,  pImageBinds must( be a valid pointer to an array of imageBindCount valid VkSparseImageMemoryBindInfo structuresIf signalSemaphoreCount is not 0, pSignalSemaphores must( be a valid pointer to an array of signalSemaphoreCount valid  VkSemaphore handlesBoth of the elements of pSignalSemaphores, and the elements of pWaitSemaphores that are valid handles must? have been created, allocated, or retrieved from the same VkDeviceSee Also, , , , , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.waitSemaphoreCountn is the number of semaphores upon which to wait before executing the sparse binding operations for the batch.pWaitSemaphores is a pointer to an array of semaphores upon which to wait on before the sparse binding operations for this batch begin execution. If semaphores to wait on are provided, they define a  phttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-semaphores-waitingsemaphore wait operation.bufferBindCountB is the number of sparse buffer bindings to perform in the batch. pBufferBinds is a pointer to an array of  structures.imageOpaqueBindCount; is the number of opaque sparse image bindings to perform.pImageOpaqueBinds is a pointer to an array of A structures, indicating opaque sparse image bindings to perform.imageBindCount3 is the number of sparse image bindings to perform. pImageBinds is a pointer to an array of : structures, indicating sparse image bindings to perform.signalSemaphoreCount is the number of semaphores to be signaled once the sparse binding operations specified by the structure have completed execution.pSignalSemaphores is a pointer to an array of semaphores which will be signaled when the sparse binding operations for this batch have completed execution. If semaphores to be signaled are provided, they define a  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-semaphores-signalingsemaphore signal operation.QVkSparseImageMemoryBindInfo - Structure specifying sparse image memory bind info Valid UsageThe subresource.mipLevel member of each element of pBinds must be less than the  mipLevels specified in * when image was createdThe subresource.arrayLayer member of each element of pBinds must be less than the  arrayLayers specified in * when image was createdValid Usage (Implicit)image must be a valid VkImage handlepBinds must# be a valid pointer to an array of  bindCount valid VkSparseImageMemoryBind structures bindCount must be greater than 0See Also, 2, image is the VkImage object to be bound bindCount is the number of VkSparseImageMemoryBind structures in pBinds arraypBinds is a pointer to array of VkSparseImageMemoryBind structures^VkSparseImageOpaqueMemoryBindInfo - Structure specifying sparse image opaque memory bind info Valid UsageIf the flags member of any element of pBinds contains "VK_SPARSE_MEMORY_BIND_METADATA_BIT!, the binding range defined must> be within the mip tail region of the metadata aspect of imageValid Usage (Implicit)image must be a valid VkImage handlepBinds must# be a valid pointer to an array of  bindCount valid VkSparseMemoryBind structures bindCount must be greater than 0See Also, 2, image is the VkImage object to be bound. bindCount is the number of VkSparseMemoryBind structures in the pBinds array.pBinds is a pointer to array of VkSparseMemoryBind structures.ZVkSparseBufferMemoryBindInfo - Structure specifying a sparse buffer memory bind operationValid Usage (Implicit)buffer must be a valid VkBuffer handlepBinds must# be a valid pointer to an array of  bindCount valid VkSparseMemoryBind structures bindCount must be greater than 0See Also, 3, buffer is the VkBuffer object to be bound. bindCount is the number of VkSparseMemoryBind structures in the pBinds array.pBinds is a pointer to array of VkSparseMemoryBind structures.GVkSparseImageMemoryBind - Structure specifying sparse image memory bind Valid UsageIf the  vhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-sparseResidencyAliasedsparse aliased residencyU feature is not enabled, and if any other resources are bound to ranges of memory, the range of memory being bound must) not overlap with those bound rangesmemory and  memoryOffset must= match the memory requirements of the calling command s image, as described in section chttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#resources-association*{html_spec_relative}#resources-association subresource must" be a valid image subresource for image (see  chttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#resources-image-views*{html_spec_relative}#resources-image-views)offset.x must5 be a multiple of the sparse image block width (VkSparseImageFormatProperties::imageGranularity.width) of the image extent.width mustR either be a multiple of the sparse image block width of the image, or else ( extent.width + offset.x) must. equal the width of the image subresourceoffset.y must6 be a multiple of the sparse image block height (VkSparseImageFormatProperties::imageGranularity.height) of the image extent.height mustS either be a multiple of the sparse image block height of the image, or else ( extent.height + offset.y) must* equal the height of the image subresourceoffset.z must5 be a multiple of the sparse image block depth (VkSparseImageFormatProperties::imageGranularity.depth) of the image extent.depth mustR either be a multiple of the sparse image block depth of the image, or else ( extent.depth + offset.z) must. equal the depth of the image subresourceValid Usage (Implicit) subresource must be a valid VkImageSubresource structureIf memory is not , memory must be a valid VkDeviceMemory handleflags must be a valid combination of  valuesSee Also ,  VkDeviceSize, , , , ,  subresource7 is the aspectMask and region of interest in the image.offsetN are the coordinates of the first texel within the image subresource to bind.extentW is the size in texels of the region within the image subresource to bind. The extent must be a multiple of the sparse image block dimensions, except when binding sparse image blocks along the edge of an image subresource it can) instead be such that any coordinate of offset + extent? equals the corresponding dimensions of the image subresource.memory is the VkDeviceMemoryD object that the sparse image blocks of the image are bound to. If memory is ', the sparse image blocks are unbound. memoryOffset is an offset into VkDeviceMemory object. If memory is , this value is ignored.flags! are sparse memory binding flags.HVkSparseMemoryBind - Structure specifying a sparse memory bind operation DescriptionThe  binding range [resourceOffset, resourceOffset + size&) has different constraints based on flags. If flags contains "VK_SPARSE_MEMORY_BIND_METADATA_BIT, the binding range must\ be within the mip tail region of the metadata aspect. This metadata region is defined by:metadataRegion = [base, base + imageMipTailSize)base = imageMipTailOffset + imageMipTailStride nand imageMipTailOffset, imageMipTailSize, and imageMipTailStride values are from the g corresponding to the metadata aspect of the image, and n is a valid array layer index for the image,imageMipTailStride- is considered to be zero for aspects where VkSparseImageMemoryRequirements::formatProperties.flags contains )VK_SPARSE_IMAGE_FORMAT_SINGLE_MIPTAIL_BIT.If flags does not contain "VK_SPARSE_MEMORY_BIND_METADATA_BIT, the binding range must be within the range [0,j::size). Valid UsageIf memory is not , memory and  memoryOffset mustR match the memory requirements of the resource, as described in section chttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#resources-association*{html_spec_relative}#resources-associationIf memory is not , memory mustA not have been created with a memory type that reports 'VK_MEMORY_PROPERTY_LAZILY_ALLOCATED_BIT bit setsize must be greater than 0resourceOffset must& be less than the size of the resourcesize must> be less than or equal to the size of the resource minus resourceOffset memoryOffset must be less than the size of memorysize must& be less than or equal to the size of memory minus  memoryOffsetValid Usage (Implicit)If memory is not , memory must be a valid VkDeviceMemory handleflags must be a valid combination of  valuesSee Also ,  VkDeviceSize, , , resourceOffset! is the offset into the resource.size. is the size of the memory region to be bound.memory is the VkDeviceMemory8 object that the range of the resource is bound to. If memory is , the range is unbound. memoryOffset is the offset into the VkDeviceMemory+ object to bind the resource range to. If memory is , this value is ignored.flags is a bitmask of , specifying usage of the binding operation.=VkImageSubresource - Structure specifying a image subresourceValid Usage (Implicit) aspectMask must be a valid combination of  values aspectMask must not be 0See Also, , ] aspectMask is a  selecting the image aspect.mipLevel selects the mipmap level. arrayLayer selects the array layer.XVkSparseImageMemoryRequirements - Structure specifying sparse image memory requirementsMembersformatProperties.aspectMask is the set of aspects of the image that this sparse memory requirement applies to. This will usually have a single aspect specified. However, depth/stencil images may` have depth and stencil data interleaved in the same sparse block, in which case both VK_IMAGE_ASPECT_DEPTH_BIT and VK_IMAGE_ASPECT_STENCIL_BIT would be present.!formatProperties.imageGranularityg describes the dimensions of a single bindable sparse image block in texel units. For aspect VK_IMAGE_ASPECT_METADATA_BITS, all dimensions will be zero. All metadata is located in the mip tail region.formatProperties.flags is a bitmask of :If )VK_SPARSE_IMAGE_FORMAT_SINGLE_MIPTAIL_BITI is set the image uses a single mip tail region for all array layers.If +VK_SPARSE_IMAGE_FORMAT_ALIGNED_MIP_SIZE_BIT) is set the dimensions of mip levels must be integer multiples of the corresponding dimensions of the sparse image block for levels not located in the mip tail.If 1VK_SPARSE_IMAGE_FORMAT_NONSTANDARD_BLOCK_SIZE_BITO is set the image uses non-standard sparse image block dimensions. The !formatProperties.imageGranularityk values do not match the standard sparse image block dimension corresponding to the image s format.imageMipTailFirstLod] is the first mip level at which image subresources are included in the mip tail region.imageMipTailSize? is the memory size (in bytes) of the mip tail region. If formatProperties.flags contains )VK_SPARSE_IMAGE_FORMAT_SINGLE_MIPTAIL_BIT, this is the size of the whole mip tail, otherwise this is the size of the mip tail of a single array layer. This value is guaranteed to be a multiple of the sparse block size in bytes.imageMipTailOffset, is the opaque memory offset used with  to bind the mip tail region(s).imageMipTailStrideC is the offset stride between each array-layer s mip tail, if formatProperties.flags does not contain )VK_SPARSE_IMAGE_FORMAT_SINGLE_MIPTAIL_BIT) (otherwise the value is undefined).See Also VkDeviceSize, , u, TVkSparseImageFormatProperties - Structure specifying sparse image format propertiesSee Also, , , s, ,  aspectMask is a bitmask @ specifying which aspects of the image the properties apply to.imageGranularitya is the width, height, and depth of the sparse image block in texels or compressed texel blocks.flags is a bitmask of > specifying additional information about the sparse resource.<VkOffset3D - Structure specifying a three-dimensional offsetSee Also, , 5, 6, x is the x offset.y is the y offset.z is the z offset.fVkSparseImageFormatFlagBits - Bitmask specifying additional information about a sparse image resourceSee Also[VkSparseMemoryBindFlagBits - Bitmask specifying usage of a sparse memory binding operationSee Also\VkImageAspectFlagBits - Bitmask specifying which aspects of an image are included in a viewSee Alsox, , x/BvkQueueBindSparse - Bind device memory to a sparse resource object ParametersqueueK is the queue that the sparse binding operations will be submitted to. bindInfoCount" is the number of elements in the  pBindInfo array. pBindInfo is an array of D structures, each specifying a sparse binding submission batch.fence is an optional+ handle to a fence to be signaled. If fence is not , it defines a  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-fences-signalingfence signal operation. DescriptionvkQueueBindSparse is a  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#devsandqueues-submissionqueue submission command,, with each batch defined by an element of  pBindInfo as an instance of the A structure. Batches begin execution in the order they appear in  pBindInfo, but may complete out of order.,Within a batch, a given range of a resource must not be bound more than once. Across batches, if a range is to be bound to one allocation and offset and then to another allocation and offset, then the application must guarantee (usually using semaphores) that the binding operations are executed in the correct order, as well as to order binding operations against the execution of command buffer submissions.As no operation to  causes any pipeline stage to access memory, synchronization primitives used in this command effectively only define execution dependencies.LAdditional information about fence and semaphore operation is described in  ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronizationthe synchronization chapter. Valid UsageIf fence is not , fence must be unsignaledIf fence is not , fence mustg not be associated with any other queue command that has not yet completed execution on that queueEach element of the pSignalSemaphores member of each element of  pBindInfo must\ be unsignaled when the semaphore signal operation it defines is executed on the deviceGWhen a semaphore unsignal operation defined by any element of the pWaitSemaphores member of any element of  pBindInfo executes on queue, no other queue must" be waiting on the same semaphore.All elements of the pWaitSemaphores member of all elements of  pBindInfo must/ be semaphores that are signaled, or have  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-semaphores-signaling semaphore signal operations) previously submitted for execution.Valid Usage (Implicit)queue must be a valid VkQueue handleIf  bindInfoCount is not 0,  pBindInfo must( be a valid pointer to an array of  bindInfoCount valid VkBindSparseInfo structuresIf fence is not , fence must be a valid VkFence handleThe queue must" support sparse binding operationsBoth of fence, and queue that are valid handles must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to queue must be externally synchronizedHost access to  pBindInfo[].pWaitSemaphores[] must be externally synchronizedHost access to  pBindInfo[].pSignalSemaphores[] must be externally synchronizedHost access to  pBindInfo[].pBufferBinds[].buffer must be externally synchronizedHost access to  pBindInfo[].pImageOpaqueBinds[].image must be externally synchronizedHost access to  pBindInfo[].pImageBinds[].image must be externally synchronizedHost access to fence must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type m - l - g SPARSE_BINDING | -  Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_DEVICE_LOSTSee Also, , qvkGetPhysicalDeviceSparseImageFormatProperties - Retrieve properties of an image format applied to sparse images ParametersphysicalDeviceO is the physical device from which to query the sparse image capabilities.format is the image format.type is the dimensionality of image.samples7 is the number of samples per texel as defined in .usage9 is a bitmask describing the intended usage of the image.tiling: is the tiling arrangement of the data elements in memory.pPropertyCount| is a pointer to an integer related to the number of sparse format properties available or queried, as described below. pProperties is either NULL" or a pointer to an array of  structures. DescriptionIf  pProperties is NULLH, then the number of sparse format properties available is returned in pPropertyCount . Otherwise, pPropertyCount mustG point to a variable set by the user to the number of elements in the  pPropertiese array, and on return the variable is overwritten with the number of structures actually written to  pProperties. If pPropertyCountI is less than the number of sparse format properties available, at most pPropertyCount structures will be written.If $VK_IMAGE_CREATE_SPARSE_RESIDENCY_BIT, is not supported for the given arguments, pPropertyCountB will be set to zero upon return, and no data will be written to  pProperties.Multiple aspects are returned for depth/stencil images that are implemented as separate planes by the implementation. The depth and stencil data planes each have unique VkSparseImageFormatProperties data.gDepth/stencil images with depth and stencil data interleaved into a single plane will return a single VkSparseImageFormatProperties structure with the  aspectMask set to VK_IMAGE_ASPECT_DEPTH_BIT | VK_IMAGE_ASPECT_STENCIL_BIT. Valid Usagesamples must$ be a bit value that is set in VkImageFormatProperties:: sampleCounts returned by (vkGetPhysicalDeviceImageFormatProperties with format, type, tiling, and usage$ equal to those in this command and flags( equal to the value that is set in VkImageCreateInfo::flags when the image is createdValid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handleformat must be a valid  valuetype must be a valid  valuesamples must be a valid  valueusage must be a valid combination of  valuesusage must not be 0tiling must be a valid  valuepPropertyCount must be a valid pointer to a uint32_t valueIf the value referenced by pPropertyCount is not 0 , and  pProperties is not NULL,  pProperties must( be a valid pointer to an array of pPropertyCount VkSparseImageFormatProperties structuresSee Also, , , , , , VvkGetImageSparseMemoryRequirements - Query the memory requirements for a sparse image Parametersdevice+ is the logical device that owns the image.image is the VkImage+ object to get the memory requirements for.pSparseMemoryRequirementCount is a pointer to an integer related to the number of sparse memory requirements available or queried, as described below.pSparseMemoryRequirements is either NULL" or a pointer to an array of VkSparseImageMemoryRequirements structures. DescriptionIf pSparseMemoryRequirements is NULLK, then the number of sparse memory requirements available is returned in pSparseMemoryRequirementCount. Otherwise, pSparseMemoryRequirementCount mustG point to a variable set by the user to the number of elements in the pSparseMemoryRequirementsf array, and on return the variable is overwritten with the number of structures actually written to pSparseMemoryRequirements. If pSparseMemoryRequirementCountK is less than the number of sparse memory requirements available, at most pSparseMemoryRequirementCount structures will be written."If the image was not created with $VK_IMAGE_CREATE_SPARSE_RESIDENCY_BIT then pSparseMemoryRequirementCount will be set to zero and pSparseMemoryRequirements will not be written to.Note?It is legal for an implementation to report a larger value in VkMemoryRequirements::sizeA than would be obtained by adding together memory sizes for all VkSparseImageMemoryRequirements returned by "vkGetImageSparseMemoryRequirements. This mayf occur when the implementation requires unused padding in the address range describing the resource.Valid Usage (Implicit)device must be a valid VkDevice handleimage must be a valid VkImage handlepSparseMemoryRequirementCount must be a valid pointer to a uint32_t valueIf the value referenced by pSparseMemoryRequirementCount is not 0, and pSparseMemoryRequirements is not NULL, pSparseMemoryRequirements must( be a valid pointer to an array of pSparseMemoryRequirementCount VkSparseImageMemoryRequirements structuresimage must6 have been created, allocated, or retrieved from deviceSee Also, 2, 1VK_SPARSE_IMAGE_FORMAT_NONSTANDARD_BLOCK_SIZE_BITU specifies that the image uses non-standard sparse image block dimensions, and the imageGranularityV values do not match the standard sparse image block dimensions for the given format.+VK_SPARSE_IMAGE_FORMAT_ALIGNED_MIP_SIZE_BIT specifies that the first mip level whose dimensions are not integer multiples of the corresponding dimensions of the sparse image block begins the mip tail region.)VK_SPARSE_IMAGE_FORMAT_SINGLE_MIPTAIL_BITN specifies that the image uses a single mip tail region for all array layers."VK_SPARSE_MEMORY_BIND_METADATA_BITH specifies that the memory being bound is only for the metadata aspect.VK_IMAGE_ASPECT_METADATA_BIT1 specifies the metadata aspect, used for sparse  Zhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#sparsememorysparse resource operations.VK_IMAGE_ASPECT_STENCIL_BIT specifies the stencil aspect.VK_IMAGE_ASPECT_DEPTH_BIT specifies the depth aspect.VK_IMAGE_ASPECT_COLOR_BIT specifies the color aspect.VVsNone "-STbejk140)YVkPhysicalDeviceSparseImageFormatInfo2 - Structure specifying sparse image format inputs Valid Usagesamples must$ be a bit value that is set in VkImageFormatProperties:: sampleCounts returned by (vkGetPhysicalDeviceImageFormatProperties with format, type, tiling, and usage$ equal to those in this command and flags( equal to the value that is set in VkImageCreateInfo::flags when the image is createdValid Usage (Implicit)sType must be <VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_SPARSE_IMAGE_FORMAT_INFO_2pNext must be NULLformat must be a valid  valuetype must be a valid  valuesamples must be a valid  valueusage must be a valid combination of / valuesusage must not be 0tiling must be a valid  valueSee Also, , , , , , ^, t+sType is the type of this structure.,pNext is NULL1 or a pointer to an extension-specific structure.-format is the image format..type is the dimensionality of image./samples3 is the number of samples per texel as defined in .0usage9 is a bitmask describing the intended usage of the image.1tiling: is the tiling arrangement of the data elements in memory.2UVkSparseImageFormatProperties2 - Structure specifying sparse image format propertiesValid Usage (Implicit)sType must be 2VK_STRUCTURE_TYPE_SPARSE_IMAGE_FORMAT_PROPERTIES_2pNext must be NULLSee Also, , ^, t4sType is the type of this structure.5pNext is NULL1 or a pointer to an extension-specific structure.6 properties is a structure of type 1 which is populated with the same values as in r.7[VkPhysicalDeviceMemoryProperties2 - Structure specifying physical device memory propertiesValid Usage (Implicit)sType must be 5VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_MEMORY_PROPERTIES_2pNext must be NULLSee Also, , _, t9sType is the type of this structure.:pNext is NULL1 or a pointer to an extension-specific structure.;memoryProperties is a structure of type 1 which is populated with the same values as in / .<PVkQueueFamilyProperties2 - Structure providing information about a queue familyValid Usage (Implicit)sType must be +VK_STRUCTURE_TYPE_QUEUE_FAMILY_PROPERTIES_2pNext must be NULLSee Also, , `, t>sType is the type of this structure.?pNext is NULL1 or a pointer to an extension-specific structure.@queueFamilyProperties is a structure of type 1 which is populated with the same values as in /.ARVkPhysicalDeviceImageFormatInfo2 - Structure specifying image creation parameters DescriptionThe members of  VkPhysicalDeviceImageFormatInfo2" correspond to the arguments to /, with sType and pNext added for extensibility.Valid Usage (Implicit)sType must be 5VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_IMAGE_FORMAT_INFO_2pNext must be NULL* or a pointer to a valid instance of Yformat must be a valid  valuetype must be a valid  valuetiling must be a valid  valueusage must be a valid combination of / valuesusage must not be 0flags must be a valid combination of / valuesSee Also, , , , , , a, tCsType is the type of this structure.DpNext is NULL7 or a pointer to an extension-specific structure. The pNext chain of  VkPhysicalDeviceImageFormatInfo25 is used to provide additional image parameters to )vkGetPhysicalDeviceImageFormatProperties2.Eformat is a 7 value indicating the image format, corresponding to *::format.Ftype is a 5 value indicating the image type, corresponding to *:: imageType.Gtiling is a 7 value indicating the image tiling, corresponding to *::tiling.Husage is a bitmask of /@ indicating the intended usage of the image, corresponding to *::usage.Iflags is a bitmask of /C indicating additional parameters of the image, corresponding to *::flags.JJVkImageFormatProperties2 - Structure specifying a image format properties Description%If the combination of parameters to )vkGetPhysicalDeviceImageFormatProperties24 is not supported by the implementation for use in , then all members of imageFormatProperties will be filled with zero.NoteFilling imageFormatProperties with zero for unsupported formats is an exception to the usual rule that output structures have undefined contents on error. This exception was unintentional, but is preserved for backwards compatibility. This exeption only applies to imageFormatProperties, not sType, pNext", or any structures chained from pNext.Valid Usage (Implicit)sType must be +VK_STRUCTURE_TYPE_IMAGE_FORMAT_PROPERTIES_2Each pNext: member of any structure (including this one) in the pNext chain must be either NULL/ or a pointer to a valid instance of , , x, or Each sType member in the pNext chain must be uniqueSee Also, , a, tLsType is the type of this structure.MpNext is NULL7 or a pointer to an extension-specific structure. The pNext chain of VkImageFormatProperties2U is used to allow the specification of additional capabilities to be returned from )vkGetPhysicalDeviceImageFormatProperties2.NimageFormatProperties is an instance of a / structure in which capabilities are returned.OBVkFormatProperties2 - Structure specifying image format propertiesValid Usage (Implicit)sType must be %VK_STRUCTURE_TYPE_FORMAT_PROPERTIES_2pNext must be NULLSee Also, , b, tQsType is the type of this structure.RpNext is NULL1 or a pointer to an extension-specific structure.SformatProperties is a structure of type 8 describing features supported by the requested format.TNVkPhysicalDeviceProperties2 - Structure specifying physical device properties DescriptionThe pNext` chain of this structure is used to extend the structure with properties defined by extensions.Valid Usage (Implicit)sType must be .VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_PROPERTIES_2Each pNext: member of any structure (including this one) in the pNext chain must be either NULL/ or a pointer to a valid instance of R, S, ]V, Z, ^, `, c, d, e, h, i, [j, 2k, m, dp, or sEach sType member in the pNext chain must be uniqueSee Also, , c, tVsType is the type of this structure.WpNext is NULL1 or a pointer to an extension-specific structure.X properties is a structure of type ~ describing the properties of the physical device. This structure is written with the same values as if it were written by /.YvVkPhysicalDeviceFeatures2 - Structure describing the fine-grained features that can be supported by an implementationMembersThe VkPhysicalDeviceFeatures2 structure is defined as: DescriptionsType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.features is a structure of type XA describing the fine-grained features of the Vulkan 1.0 API.The pNextn chain of this structure is used to extend the structure with features defined by extensions. This structure can be used in d or can be in the pNext chain of a ~\ structure, in which case it controls which features are enabled in the device in lieu of pEnabledFeatures.Valid Usage (Implicit)sType must be ,VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_FEATURES_2See AlsoX, , d, t^rvkGetPhysicalDeviceSparseImageFormatProperties2 - Retrieve properties of an image format applied to sparse images ParametersphysicalDeviceO is the physical device from which to query the sparse image capabilities. pFormatInfo* is a pointer to a structure of type )1 containing input parameters to the command.pPropertyCount| is a pointer to an integer related to the number of sparse format properties available or queried, as described below. pProperties is either NULL" or a pointer to an array of 2 structures. Description/vkGetPhysicalDeviceSparseImageFormatProperties2 behaves identically to rZ, with the ability to return extended information by adding extension structures to the pNext chain of its  pProperties parameter.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handle pFormatInfo must$ be a valid pointer to a valid &VkPhysicalDeviceSparseImageFormatInfo2 structurepPropertyCount must be a valid pointer to a uint32_t valueIf the value referenced by pPropertyCount is not 0 , and  pProperties is not NULL,  pProperties must( be a valid pointer to an array of pPropertyCount VkSparseImageFormatProperties2 structuresSee Also, ), 2_dvkGetPhysicalDeviceMemoryProperties2 - Reports memory information for the specified physical device ParametersphysicalDevice& is the handle to the device to query.pMemoryProperties points to an instance of !VkPhysicalDeviceMemoryProperties25 structure in which the properties are returned. Description$vkGetPhysicalDeviceMemoryProperties2 behaves similarly to / 8, with the ability to return extended information in a pNext chain of output structures.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handlepMemoryProperties must be a valid pointer to a !VkPhysicalDeviceMemoryProperties2 structureSee Also, 7`nvkGetPhysicalDeviceQueueFamilyProperties2 - Reports properties of the queues of the specified physical device ParametersphysicalDeviceL is the handle to the physical device whose properties will be queried.pQueueFamilyPropertyCountt is a pointer to an integer related to the number of queue families available or queried, as described in /.pQueueFamilyProperties is either NULL" or a pointer to an array of < structures. Description)vkGetPhysicalDeviceQueueFamilyProperties2 behaves similarly to /8, with the ability to return extended information in a pNext chain of output structures.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handlepQueueFamilyPropertyCount must be a valid pointer to a uint32_t valueIf the value referenced by pQueueFamilyPropertyCount is not 0 , and pQueueFamilyProperties is not NULL, pQueueFamilyProperties must# be a valid pointer to an array of pQueueFamilyPropertyCount VkQueueFamilyProperties2 structuresSee Also, <a^vkGetPhysicalDeviceImageFormatProperties2 - Lists physical device s image format capabilities ParametersphysicalDeviceH is the physical device from which to query the image capabilities.pImageFormatInfo# points to an instance of the AJ structure, describing the parameters that would be consumed by .pImageFormatProperties# points to an instance of the J3 structure in which capabilities are returned. Description)vkGetPhysicalDeviceImageFormatProperties2 behaves similarly to /8, with the ability to return extended information in a pNext chain of output structures. Valid UsageIf the pNext chain of pImageFormatProperties# contains an instance of  , the pNext chain of pImageFormatInfo must" contain an instance of Y with  handleType set to BVK_EXTERNAL_MEMORY_HANDLE_TYPE_ANDROID_HARDWARE_BUFFER_BIT_ANDROID.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handlepImageFormatInfo must$ be a valid pointer to a valid  VkPhysicalDeviceImageFormatInfo2 structurepImageFormatProperties must be a valid pointer to a VkImageFormatProperties2 structure Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_FORMAT_NOT_SUPPORTEDSee AlsoJ, , AbSvkGetPhysicalDeviceFormatProperties2 - Lists physical device s format capabilities ParametersphysicalDeviceG is the physical device from which to query the format properties.format, is the format whose properties are queried.pFormatProperties is a pointer to a O8 structure in which physical device properties for format are returned. Description$vkGetPhysicalDeviceFormatProperties2 behaves similarly to /8, with the ability to return extended information in a pNext chain of output structures.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handleformat must be a valid  valuepFormatProperties must be a valid pointer to a VkFormatProperties2 structureSee Also, O, cHvkGetPhysicalDeviceProperties2 - Returns properties of a physical device ParametersphysicalDeviceL is the handle to the physical device whose properties will be queried. pProperties# points to an instance of the T? structure, that will be filled with returned information. DescriptionEach structure in  pProperties and its pNextY chain contain members corresponding to properties or implementation-dependent limits. vkGetPhysicalDeviceProperties2O writes each member to a value indicating the value of that property or limit.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handle pProperties must be a valid pointer to a VkPhysicalDeviceProperties2 structureSee Also, TdHvkGetPhysicalDeviceFeatures2 - Reports capabilities of a physical device ParametersphysicalDeviceH is the physical device from which to query the supported features. pFeatures is a pointer to a YC structure in which the physical device features are returned. DescriptionEach structure in  pFeatures and its pNext@ chain contain members corresponding to fine-grained features. vkGetPhysicalDeviceFeatures2V writes each member to a boolean value indicating whether that feature is supported.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handle pFeatures must be a valid pointer to a VkPhysicalDeviceFeatures2 structureSee Also, YE)*+,-.10/23456789:;<=>?@ABCDIEFGHJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmEmlkjihgfedcba`_^YZ[\]TUVWXOPQRSJKLMNABCDIEFGH<=>?@789:;23456)*+,-.10/tNone-STejk1$$uNone "-STbejk1")VkSparseImageMemoryRequirements2 - (None)Valid Usage (Implicit)sType must be 4VK_STRUCTURE_TYPE_SPARSE_IMAGE_MEMORY_REQUIREMENTS_2pNext must be NULLSee Also, , , v\sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.memoryRequirements is a structure of type 9 describing the memory requirements of the sparse image.@VkMemoryRequirements2 - Structure specifying memory requirementsValid Usage (Implicit)sType must be 'VK_STRUCTURE_TYPE_MEMORY_REQUIREMENTS_2pNext must be NULL* or a pointer to a valid instance of nESee Also-, , , vJ, , vYsType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.memoryRequirements is a structure of type -5 describing the memory requirements of the resource.-VkImageSparseMemoryRequirementsInfo2 - (None)Valid Usage (Implicit)sType must be 9VK_STRUCTURE_TYPE_IMAGE_SPARSE_MEMORY_REQUIREMENTS_INFO_2pNext must be NULLimage must be a valid VkImage handleSee Also2, , , v\sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.image is the image to query.'VkImageMemoryRequirementsInfo2 - (None) Valid UsageIf image was created with a  multi-planar format and the VK_IMAGE_CREATE_DISJOINT_BIT flag, there must be a x/ in the pNext chain of the  structureIf image was not created with the VK_IMAGE_CREATE_DISJOINT_BIT flag, there must not be a x/ in the pNext chain of the  structureIf image/ was created with a single-plane format, there must not be a x/ in the pNext chain of the  structureIf image was created with the VK_EXTERNAL_MEMORY_HANDLE_TYPE_ANDROID_HARDWARE_BUFFER_BIT_ANDROID external memory handle type, then image must be bound to memory.Valid Usage (Implicit)sType must be 2VK_STRUCTURE_TYPE_IMAGE_MEMORY_REQUIREMENTS_INFO_2pNext must be NULL* or a pointer to a valid instance of x/image must be a valid VkImage handleSee Also2, , , vYsType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.image is the image to query.(VkBufferMemoryRequirementsInfo2 - (None)Valid Usage (Implicit)sType must be 3VK_STRUCTURE_TYPE_BUFFER_MEMORY_REQUIREMENTS_INFO_2pNext must be NULLbuffer must be a valid VkBuffer handleSee Also3, , , vJsType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.buffer is the buffer to query.WvkGetImageSparseMemoryRequirements2 - Query the memory requirements for a sparse image Parametersdevice+ is the logical device that owns the image.pInfo) is a pointer to an instance of the $VkImageSparseMemoryRequirementsInfo2Q structure containing parameters required for the memory requirements query.pSparseMemoryRequirementCount is a pointer to an integer related to the number of sparse memory requirements available or queried, as described below.pSparseMemoryRequirements is either NULL" or a pointer to an array of  VkSparseImageMemoryRequirements2 structures.Valid Usage (Implicit)device must be a valid VkDevice handlepInfo must$ be a valid pointer to a valid $VkImageSparseMemoryRequirementsInfo2 structurepSparseMemoryRequirementCount must be a valid pointer to a uint32_t valueIf the value referenced by pSparseMemoryRequirementCount is not 0, and pSparseMemoryRequirements is not NULL, pSparseMemoryRequirements must( be a valid pointer to an array of pSparseMemoryRequirementCount  VkSparseImageMemoryRequirements2 structuresSee Also, , \vkGetImageMemoryRequirements2 - Returns the memory requirements for specified Vulkan object Parametersdevice+ is the logical device that owns the image.pInfo) is a pointer to an instance of the VkImageMemoryRequirementsInfo2Q structure containing parameters required for the memory requirements query.pMemoryRequirements# points to an instance of the R structure in which the memory requirements of the image object are returned.Valid Usage (Implicit)device must be a valid VkDevice handlepInfo must$ be a valid pointer to a valid VkImageMemoryRequirementsInfo2 structurepMemoryRequirements must be a valid pointer to a VkMemoryRequirements2 structureSee Also, , ]vkGetBufferMemoryRequirements2 - Returns the memory requirements for specified Vulkan object Parametersdevice, is the logical device that owns the buffer.pInfo) is a pointer to an instance of the VkBufferMemoryRequirementsInfo2Q structure containing parameters required for the memory requirements query.pMemoryRequirements# points to an instance of the S structure in which the memory requirements of the buffer object are returned.Valid Usage (Implicit)device must be a valid VkDevice handlepInfo must$ be a valid pointer to a valid VkBufferMemoryRequirementsInfo2 structurepMemoryRequirements must be a valid pointer to a VkMemoryRequirements2 structureSee Also, , !!vNone-STejk1wNone "-KSTbejk4QVVkImageViewCreateInfo - Structure specifying parameters of a newly created image view DescriptionIf image was created with the "VK_IMAGE_CREATE_MUTABLE_FORMAT_BIT flag, and if the format of the image is not  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversion multi-planar, format can. be different from the image s format, but if image was created without the /VK_IMAGE_CREATE_BLOCK_TEXEL_VIEW_COMPATIBLE_BIT# flag and they are not equal they must be  compatible0. Image format compatibility is defined in the  thttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-compatibility-classesFormat Compatibility Classes section. Views of compatible formats will have the same mapping between texel coordinates and memory locations irrespective of the format<, with only the interpretation of the bit pattern changing.Note0Values intended to be used with one view format may not be exactly preserved when written or read through a different format. For example, an integer value that happens to have the bit pattern of a floating point denorm or NaN may be flushed or canonicalized when written or read through a view with a floating point format. Similarly, a value written through a signed normalized format that has a bit pattern exactly equal to -2b may( be changed to -2b + 1 as described in  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-fixedfpconv9Conversion from Normalized Fixed-Point to Floating-Point.If image was created with the /VK_IMAGE_CREATE_BLOCK_TEXEL_VIEW_COMPATIBLE_BIT flag, format must be  compatible0 with the image s format as described above, or must- be an uncompressed format in which case it must be size-compatible* with the image s format, as defined for  uhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#copies-images-format-size-compatibilitycopying data between images In this case the resulting image view s texel dimensions equal the dimensions of the selected mip level divided by the compressed texel block size and rounded up.>If the image view is to be used with a sampler which supports  ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#samplers-YCbCr-conversionsampler Y CBCR conversion, an identically defined object of type x% to that used to create the sampler must be passed to  in a x added to the pNext chain of .If the image has a  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversion multi-planar format and subresourceRange.aspectMask is VK_IMAGE_ASPECT_COLOR_BIT, format must be identical to the image format1, and the sampler to be used with the image view must enable  ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#samplers-YCbCr-conversionsampler Y CBCR conversion.If image was created with the "VK_IMAGE_CREATE_MUTABLE_FORMAT_BIT and the image has a  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversion multi-planar format , and if subresourceRange.aspectMask is VK_IMAGE_ASPECT_PLANE_0_BIT, VK_IMAGE_ASPECT_PLANE_1_BIT, or VK_IMAGE_ASPECT_PLANE_2_BIT, format must be  phttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-compatible-planes compatible] with the corresponding plane of the image, and the sampler to be used with the image view must not enable  ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#samplers-YCbCr-conversionsampler Y CBCR conversion. The width and height of the single-plane image view mustP be derived from the multi-planar image s dimensions in the manner listed for  phttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-compatible-planesplane compatibility for the plane.Any view of an image plane will have the same mapping between texel coordinates and memory locations as used by the channels of the color aspect, subject to the formulae relating texel coordinates to lower-resolution planes as described in  lhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#textures-chroma-reconstructionChroma Reconstruction. That is, if an R or B plane has a reduced resolution relative to the G plane of the multi-planar image, the image view operates using the (uplane, vplane}) unnormalized coordinates of the reduced-resolution plane, and these coordinates access the same memory locations as the (ucolor, vcolorp) unnormalized coordinates of the color aspect for which chroma reconstruction operations operate on the same (uplane, vplane) or (iplane, jplane) coordinates. Dim, Arrayed, MS  Image parameters k View parameters m   imageType = ci. imageType width = ci. extent.width height = ci. extent.height depth = ci. extent.depth  arrayLayers = ci. arrayLayers samples = ci.samples flags = ci.flagsR where ci is the * used to create image.  baseArrayLayer,  layerCount , and  levelCount are members of the subresourceRange member.  | 0__ | width, "e 1 | VK_IMAGE_VIEW_TYPE_1D | | | height+ = 1 | baseArrayLayer" "e 0 | | | depth, = 1 |  layerCount& = 1 | | |  arrayLayersX "e 1 | | | | samples = 1 | | +----------+--------------------------------------------------+-----------------------------------+ | __1D, 1, |  imageType = VK_IMAGE_TYPE_1D | viewType( = | | 0__ | width, "e 1 | VK_IMAGE_VIEW_TYPE_1D_ARRAY | | | height+ = 1 | baseArrayLayer" "e 0 | | | depth, = 1 |  layerCount& "e 1 | | |  arrayLayersX "e 1 | | | | samples = 1 | | +----------+--------------------------------------------------+-----------------------------------+ | __2D, 0, |  imageType = VK_IMAGE_TYPE_2D | viewType( = | | 0__ | width, "e 1 | VK_IMAGE_VIEW_TYPE_2D | | | height+ "e 1 | baseArrayLayer" "e 0 | | | depth, = 1 |  layerCount& = 1 | | |  arrayLayersX "e 1 | | | | samples = 1 | | +----------+--------------------------------------------------+-----------------------------------+ | __2D, 1, |  imageType = VK_IMAGE_TYPE_2D | viewType( = | | 0__ | width, "e 1 | VK_IMAGE_VIEW_TYPE_2D_ARRAY | | | height+ "e 1 | baseArrayLayer" "e 0 | | | depth, = 1 |  layerCount& "e 1 | | |  arrayLayersX "e 1 | | | | samples = 1 | | +----------+--------------------------------------------------+-----------------------------------+ | __2D, 0, |  imageType = VK_IMAGE_TYPE_2D | viewType( = | | 1__ | width, "e 1 | VK_IMAGE_VIEW_TYPE_2D | | | height+ "e 1 | baseArrayLayer" "e 0 | | | depth, = 1 |  layerCount& = 1 | | |  arrayLayersX "e 1 | | | | samples > 1 | | +----------+--------------------------------------------------+-----------------------------------+ | __2D, 1, |  imageType = VK_IMAGE_TYPE_2D | viewType( = | | 1__ | width, "e 1 | VK_IMAGE_VIEW_TYPE_2D_ARRAY | | | height+ "e 1 | baseArrayLayer" "e 0 | | | depth, = 1 |  layerCount& "e 1 | | |  arrayLayersX "e 1 | | | | samples > 1 | | +----------+--------------------------------------------------+-----------------------------------+ | __CUBE, |  imageType = VK_IMAGE_TYPE_2D | viewType( = | | 0, 0__ | width, "e 1 | VK_IMAGE_VIEW_TYPE_CUBE | | | height = width! | baseArrayLayer" "e 0 | | | depth, = 1 |  layerCount& = 6 | | |  arrayLayersX "e 6 | | | | samples\ = 1 | | | | flags^ includes | | | | #VK_IMAGE_CREATE_CUBE_COMPATIBLE_BIT | | +----------+--------------------------------------------------+-----------------------------------+ | __CUBE, |  imageType = VK_IMAGE_TYPE_2D | viewType( = | | 1, 0__ | width, "e 1 | VK_IMAGE_VIEW_TYPE_CUBE_ARRAY | | | height+ = width | baseArrayLayer" "e 0 | | | depth, = 1 |  layerCount = 6 N, N "e 1 | | | Nb "e 1 | | | |  arrayLayers "e 6 NN | | | | samples\ = 1 | | | | flags^ includes | | | | #VK_IMAGE_CREATE_CUBE_COMPATIBLE_BIT | | +----------+--------------------------------------------------+-----------------------------------+ | __3D, 0, |  imageType = VK_IMAGE_TYPE_3D | viewType( = | | 0__ | width, "e 1 | VK_IMAGE_VIEW_TYPE_3D | | | height+ "e 1 | baseArrayLayer" = 0 | | | depth, "e 1 |  layerCount& = 1 | | |  arrayLayersX = 1 | | | | samples = 1 | | +----------+--------------------------------------------------+-----------------------------------+ | __3D, 0, |  imageType = VK_IMAGE_TYPE_3D | viewType( = | | 0__ | width, "e 1 | VK_IMAGE_VIEW_TYPE_2D | | | height+ "e 1 |  levelCount& = 1 | | | depth, "e 1 | baseArrayLayer" "e 0 | | |  arrayLayers& = 1 |  layerCount& = 1 | | | samples\ = 1 | | | | flags^ includes | | | | 'VK_IMAGE_CREATE_2D_ARRAY_COMPATIBLE_BIT< | | | | flags^ does not include | | | | "VK_IMAGE_CREATE_SPARSE_BINDING_BITA, | | | | $VK_IMAGE_CREATE_SPARSE_RESIDENCY_BIT?, and | | | | "VK_IMAGE_CREATE_SPARSE_ALIASED_BIT | | +----------+--------------------------------------------------+-----------------------------------+ | __3D, 0, |  imageType = VK_IMAGE_TYPE_3D | viewType( = | | 0__ | width, "e 1 | VK_IMAGE_VIEW_TYPE_2D_ARRAY | | | height+ "e 1 |  levelCount& = 1 | | | depth, "e 1 | baseArrayLayer" "e 0 | | |  arrayLayers& = 1 |  layerCount& "e 1 | | | samples\ = 1 | | | | flags^ includes | | | | 'VK_IMAGE_CREATE_2D_ARRAY_COMPATIBLE_BIT< | | | | flags^ does not include | | | | "VK_IMAGE_CREATE_SPARSE_BINDING_BITA, | | | | $VK_IMAGE_CREATE_SPARSE_RESIDENCY_BIT?, and | | | | "VK_IMAGE_CREATE_SPARSE_ALIASED_BIT | | +----------+--------------------------------------------------+-----------------------------------+9Image and image view parameter compatibility requirements Valid UsageIf image was not created with #VK_IMAGE_CREATE_CUBE_COMPATIBLE_BIT then viewType must not be VK_IMAGE_VIEW_TYPE_CUBE or VK_IMAGE_VIEW_TYPE_CUBE_ARRAYIf the  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-imageCubeArrayimage cubemap arrays feature is not enabled, viewType must not be VK_IMAGE_VIEW_TYPE_CUBE_ARRAYIf image was created with VK_IMAGE_TYPE_3D but without 'VK_IMAGE_CREATE_2D_ARRAY_COMPATIBLE_BIT set then viewType must not be VK_IMAGE_VIEW_TYPE_2D or VK_IMAGE_VIEW_TYPE_2D_ARRAYIf image was created with VK_IMAGE_TILING_LINEAR, format mustT be format that has at least one supported feature bit present in the value of VkFormatProperties::linearTilingFeatures returned by #vkGetPhysicalDeviceFormatProperties with the same value of formatimage must have been created with a usage' value containing at least one of VK_IMAGE_USAGE_SAMPLED_BIT, VK_IMAGE_USAGE_STORAGE_BIT, #VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT, +VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT , or #VK_IMAGE_USAGE_INPUT_ATTACHMENT_BITIf image was created with VK_IMAGE_TILING_LINEAR and usage contains VK_IMAGE_USAGE_SAMPLED_BIT, format must@ be supported for sampled images, as specified by the #VK_FORMAT_FEATURE_SAMPLED_IMAGE_BIT flag in VkFormatProperties::linearTilingFeatures returned by #vkGetPhysicalDeviceFormatProperties with the same value of formatIf image was created with VK_IMAGE_TILING_LINEAR and usage contains VK_IMAGE_USAGE_STORAGE_BIT, format must@ be supported for storage images, as specified by the #VK_FORMAT_FEATURE_STORAGE_IMAGE_BIT flag in VkFormatProperties::linearTilingFeatures returned by #vkGetPhysicalDeviceFormatProperties with the same value of formatIf image was created with VK_IMAGE_TILING_LINEAR and usage contains #VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT, format mustC be supported for color attachments, as specified by the &VK_FORMAT_FEATURE_COLOR_ATTACHMENT_BIT flag in VkFormatProperties::linearTilingFeatures returned by #vkGetPhysicalDeviceFormatProperties with the same value of formatIf image was created with VK_IMAGE_TILING_LINEAR and usage contains +VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT, format mustF be supported for depth/stencil attachments, as specified by the .VK_FORMAT_FEATURE_DEPTH_STENCIL_ATTACHMENT_BIT flag in VkFormatProperties::linearTilingFeatures returned by #vkGetPhysicalDeviceFormatProperties with the same value of formatIf image was created with VK_IMAGE_TILING_OPTIMAL, format mustT be format that has at least one supported feature bit present in the value of VkFormatProperties::optimalTilingFeatures returned by #vkGetPhysicalDeviceFormatProperties with the same value of formatIf image was created with VK_IMAGE_TILING_OPTIMAL and usage contains VK_IMAGE_USAGE_SAMPLED_BIT, format must@ be supported for sampled images, as specified by the #VK_FORMAT_FEATURE_SAMPLED_IMAGE_BIT flag in VkFormatProperties::optimalTilingFeatures returned by #vkGetPhysicalDeviceFormatProperties with the same value of formatIf image was created with VK_IMAGE_TILING_OPTIMAL and usage contains VK_IMAGE_USAGE_STORAGE_BIT, format must@ be supported for storage images, as specified by the #VK_FORMAT_FEATURE_STORAGE_IMAGE_BIT flag in VkFormatProperties::optimalTilingFeatures returned by #vkGetPhysicalDeviceFormatProperties with the same value of formatIf image was created with VK_IMAGE_TILING_OPTIMAL and usage contains #VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT, format mustC be supported for color attachments, as specified by the &VK_FORMAT_FEATURE_COLOR_ATTACHMENT_BIT flag in VkFormatProperties::optimalTilingFeatures returned by #vkGetPhysicalDeviceFormatProperties with the same value of formatIf image was created with VK_IMAGE_TILING_OPTIMAL and usage contains +VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT, format mustF be supported for depth/stencil attachments, as specified by the .VK_FORMAT_FEATURE_DEPTH_STENCIL_ATTACHMENT_BIT flag in VkFormatProperties::optimalTilingFeatures returned by #vkGetPhysicalDeviceFormatProperties with the same value of formatsubresourceRange.baseMipLevel must be less than the  mipLevels specified in * when image was createdIf subresourceRange.levelCount is not VK_REMAINING_MIP_LEVELS, subresourceRange.baseMipLevel + subresourceRange.levelCount must be less than or equal to the  mipLevels specified in * when image was createdIf image% is not a 3D image created with 'VK_IMAGE_CREATE_2D_ARRAY_COMPATIBLE_BIT set, or viewType is not VK_IMAGE_VIEW_TYPE_2D or VK_IMAGE_VIEW_TYPE_2D_ARRAY, subresourceRange::baseArrayLayer must be less than the  arrayLayers specified in * when image was createdIf subresourceRange:: layerCount is not VK_REMAINING_ARRAY_LAYERS, image% is not a 3D image created with 'VK_IMAGE_CREATE_2D_ARRAY_COMPATIBLE_BIT set, or viewType is not VK_IMAGE_VIEW_TYPE_2D or VK_IMAGE_VIEW_TYPE_2D_ARRAY, subresourceRange:: layerCount must be non-zero and subresourceRange::baseArrayLayer + subresourceRange:: layerCount must# be less than or equal to the  arrayLayers specified in * when image was createdIf image! is a 3D image created with 'VK_IMAGE_CREATE_2D_ARRAY_COMPATIBLE_BIT set, and viewType is VK_IMAGE_VIEW_TYPE_2D or VK_IMAGE_VIEW_TYPE_2D_ARRAY, subresourceRange::baseArrayLayer must be less than the  extent.depth specified in * when image was createdIf subresourceRange:: layerCount is not VK_REMAINING_ARRAY_LAYERS, image! is a 3D image created with 'VK_IMAGE_CREATE_2D_ARRAY_COMPATIBLE_BIT set, and viewType is VK_IMAGE_VIEW_TYPE_2D or VK_IMAGE_VIEW_TYPE_2D_ARRAY, subresourceRange:: layerCount must be non-zero and subresourceRange::baseArrayLayer + subresourceRange:: layerCount must# be less than or equal to the  extent.depth specified in * when image was createdIf image was created with the "VK_IMAGE_CREATE_MUTABLE_FORMAT_BIT flag, format must be compatible with the format used to create image, as defined in thttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-compatibility-classes!Format Compatibility ClassesIf image was created with the "VK_IMAGE_CREATE_MUTABLE_FORMAT_BIT! flag, but without the /VK_IMAGE_CREATE_BLOCK_TEXEL_VIEW_COMPATIBLE_BIT flag, and if the format of the image is not a  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversion multi-planar format, format must be compatible with the format used to create image, as defined in thttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-compatibility-classes!Format Compatibility ClassesIf image was created with the /VK_IMAGE_CREATE_BLOCK_TEXEL_VIEW_COMPATIBLE_BIT flag, format must be compatible with, or mustB be an uncompressed format that is size-compatible with, the format used to create image.If image was created with the /VK_IMAGE_CREATE_BLOCK_TEXEL_VIEW_COMPATIBLE_BIT flag, the  levelCount and  layerCount members of subresourceRange must both be 1.If a VkImageFormatListCreateInfoKHR$ structure was included in the pNext chain of the VkImageCreateInfo struct used when creating image and the viewFormatCount field of VkImageFormatListCreateInfoKHR is not zero then format must$ be one of the formats in VkImageFormatListCreateInfoKHR:: pViewFormats.If image was created with the "VK_IMAGE_CREATE_MUTABLE_FORMAT_BIT flag, if the format of the image is a  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversion multi-planar format, and if subresourceRange.aspectMask is one of VK_IMAGE_ASPECT_PLANE_0_BIT, VK_IMAGE_ASPECT_PLANE_1_BIT , or VK_IMAGE_ASPECT_PLANE_2_BIT, then format must be compatible with the  for the plane of the image format indicated by subresourceRange.aspectMask, as defined in phttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-compatible-planes7{html_spec_relative}#features-formats-compatible-planesIf image was not created with the "VK_IMAGE_CREATE_MUTABLE_FORMAT_BIT flag, or if the format of the image is a  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversion multi-planar format and if subresourceRange.aspectMask is VK_IMAGE_ASPECT_COLOR_BIT, format must be identical to the format used to create imageIf image is non-sparse then it must7 be bound completely and contiguously to a single VkDeviceMemory objectsubresourceRange and viewType must8 be compatible with the image, as described in the qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#resources-image-views-compatibilitycompatibility tableIf image has an  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-external-android-hardware-buffer-external-formatsexternal format:format must be VK_FORMAT_UNDEFINEDThe pNext' chain must contain an instance of x with a  conversion5 object created with the same external format as imageAll members of  components must be VK_COMPONENT_SWIZZLE_IDENTITYValid Usage (Implicit)sType must be (VK_STRUCTURE_TYPE_IMAGE_VIEW_CREATE_INFOEach pNext: member of any structure (including this one) in the pNext chain must be either NULL/ or a pointer to a valid instance of 3 or xEach sType member in the pNext chain must be uniqueflags must be 0image must be a valid VkImage handleviewType must be a valid   valueformat must be a valid  value components must be a valid VkComponentMapping structuresubresourceRange must be a valid VkImageSubresourceRange structureSee Also, , 2, ,  ,  , , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.flags is reserved for future use.image is a VkImage# on which the view will be created.viewType is an  . value specifying the type of the image view.format is a N describing the format and type used to interpret data elements in the image. components is a  specifies a remapping of color components (or of depth or stencil components after they have been converted into color components).subresourceRange is a S selecting the set of mipmap levels and array layers to be accessible to the view.HVkImageSubresourceRange - Structure specifying a image subresource range Description-The number of mipmap levels and array layers must be a subset of the image subresources in the image. If an application wants to use all mip levels or layers in an image after the  baseMipLevel or baseArrayLayer, it can set  levelCount and  layerCount to the special values VK_REMAINING_MIP_LEVELS and VK_REMAINING_ARRAY_LAYERS; without knowing the exact number of mip levels or layers.OFor cube and cube array image views, the layers of the image view starting at baseArrayLayer correspond to faces in the order +X, -X, +Y, -Y, +Z, -Z. For cube arrays, each set of six sequential layers is a single cube, so the number of cube maps in a cube map array view is  layerCount / 6, and image array layer (baseArrayLayer' + i) is face index (i mod 6) of cube i / 6B. If the number of layers in the view, whether set explicitly in  layerCount or implied by VK_REMAINING_ARRAY_LAYERSM, is not a multiple of 6, behavior when indexing the last cube is undefined. aspectMask must be only VK_IMAGE_ASPECT_COLOR_BIT, VK_IMAGE_ASPECT_DEPTH_BIT or VK_IMAGE_ASPECT_STENCIL_BIT if formatJ is a color, depth-only or stencil-only format, respectively, except if format is a  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversionmulti-planar formatL. If using a depth/stencil format with both depth and stencil components,  aspectMask must include at least one of VK_IMAGE_ASPECT_DEPTH_BIT and VK_IMAGE_ASPECT_STENCIL_BIT, and can include both. When the VkImageSubresourceRange structure is used to select a subset of the slices of a 3D image s mip level in order to create a 2D or 2D array image view of a 3D image created with 'VK_IMAGE_CREATE_2D_ARRAY_COMPATIBLE_BIT, baseArrayLayer and  layerCountr specify the first slice index and the number of slices to include in the created image view. Such an image view canC be used as a framebuffer attachment that refers only to the specified range of slices of the selected mip level. However, any layout transitions performed on such an attachment view during a render pass instance still apply to the entire subresource referenced which includes all the slices of the selected mip level.When using an imageView of a depth/stencil image to populate a descriptor set (e.g. for sampling in the shader, or for use as an input attachment), the  aspectMask must\ only include one bit and selects whether the imageView is used for depth reads (i.e. using a floating-point sampler or input attachment in the shader) or stencil reads (i.e. using an unsigned integer sampler or input attachment in the shader). When an imageView of a depth/stencil image is used as a depth/stencil framebuffer attachment, the  aspectMaskD is ignored and both depth and stencil image subresources are used.The  components member is of type , and describes a remapping from components of the image to components of the vector returned by shader image instructions. This remapping mustm be identity for storage image descriptors, input attachment descriptors, framebuffer attachments, and any  VkImageView2 used with a combined image sampler that enables  ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#samplers-YCbCr-conversionsampler Y CBCR conversion.When creating a  VkImageView, if  ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#samplers-YCbCr-conversionsampler Y CBCR conversion! is enabled in the sampler, the  aspectMask of a subresourceRange used by the  VkImageView must be VK_IMAGE_ASPECT_COLOR_BIT.When creating a  VkImageViewL, if sampler Y CBCR conversion is not enabled in the sampler and the image format is  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversion multi-planar , the image must have been created with "VK_IMAGE_CREATE_MUTABLE_FORMAT_BIT , and the  aspectMask of the  VkImageView s subresourceRange must be VK_IMAGE_ASPECT_PLANE_0_BIT, VK_IMAGE_ASPECT_PLANE_1_BIT or VK_IMAGE_ASPECT_PLANE_2_BIT. Valid UsageIf  levelCount is not VK_REMAINING_MIP_LEVELS, it must be greater than 0If  layerCount is not VK_REMAINING_ARRAY_LAYERS, it must be greater than 0If  aspectMask includes VK_IMAGE_ASPECT_COLOR_BIT , then it must not include any of VK_IMAGE_ASPECT_PLANE_0_BIT, VK_IMAGE_ASPECT_PLANE_1_BIT, or VK_IMAGE_ASPECT_PLANE_2_BITValid Usage (Implicit) aspectMask must be a valid combination of r values aspectMask must not be 0See Also, -, , ,  aspectMask is a bitmask of rC specifying which aspect(s) of the image are included in the view. baseMipLevel2 is the first mipmap level accessible to the view. levelCount0 is the number of mipmap levels (starting from  baseMipLevel) accessible to the view.baseArrayLayer1 is the first array layer accessible to the view. layerCount/ is the number of array layers (starting from baseArrayLayer) accessible to the view.CVkComponentMapping - Structure specifying a color component mappingValid Usage (Implicit)r must be a valid   valueg must be a valid   valueb must be a valid   valuea must be a valid   valueSee Also,  , , xr is a  P specifying the component value placed in the R component of the output vector.g is a  P specifying the component value placed in the G component of the output vector.b is a  P specifying the component value placed in the B component of the output vector.a is a  P specifying the component value placed in the A component of the output vector.2VkImageView - Opaque handle to a image view objectSee Also, &, , 3Dummy data to tag the  with 0VkImageViewCreateFlags - Reserved for future use DescriptionVkImageViewCreateFlagsQ is a bitmask type for setting a mask, but is currently reserved for future use.See Also "VkImageViewType - Image view types DescriptionThe exact image view type is partially implicit, based on the image s type and sample count, as well as the view creation parameters as described in the  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#resources-image-views-compatibilityimage view compatibility table for &. This table also shows which SPIR-V  OpTypeImage Dim and Arrayed0 parameters correspond to each image view type.See Also 8VkComponentSwizzle - Specify how a component is swizzled DescriptionVK_COMPONENT_SWIZZLE_IDENTITYB specifies that the component is set to the identity swizzle.VK_COMPONENT_SWIZZLE_ZERO2 specifies that the component is set to zero.VK_COMPONENT_SWIZZLE_ONE specifies that the component is set to either 1 or 1.0, depending on whether the type of the image view format is integer or floating-point respectively, as determined by the  ihttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-definitionFormat Definition section for each .VK_COMPONENT_SWIZZLE_RW specifies that the component is set to the value of the R component of the image.VK_COMPONENT_SWIZZLE_GW specifies that the component is set to the value of the G component of the image.VK_COMPONENT_SWIZZLE_BW specifies that the component is set to the value of the B component of the image.VK_COMPONENT_SWIZZLE_AW specifies that the component is set to the value of the A component of the image.vSetting the identity swizzle on a component is equivalent to setting the identity mapping on that component. That is:# Component # Identity Mapping   components.r  VK_COMPONENT_SWIZZLE_R   components.g  VK_COMPONENT_SWIZZLE_G   components.b  VK_COMPONENT_SWIZZLE_B   components.a  VK_COMPONENT_SWIZZLE_A !Component Mappings Equivalent To VK_COMPONENT_SWIZZLE_IDENTITYSee Also1vkDestroyImageView - Destroy an image view object Parametersdevice4 is the logical device that destroys the image view. imageView is the image view to destroy. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. Valid Usage%All submitted commands that refer to  imageView must have completed executionIf VkAllocationCallbacks were provided when  imageView1 was created, a compatible set of callbacks must be provided hereIf no VkAllocationCallbacks were provided when  imageView was created,  pAllocator must be NULLValid Usage (Implicit)device must be a valid VkDevice handleIf  imageView is not ,  imageView must be a valid  VkImageView handleIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structureIf  imageView is a valid handle, it must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to  imageView must be externally synchronizedSee Also, , ?vkCreateImageView - Create an image view from an existing image Parametersdevice3 is the logical device that creates the image view. pCreateInfo) is a pointer to an instance of the VkImageViewCreateInfoJ structure containing parameters to be used to create the image view. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter.pView points to a  VkImageViewB handle in which the resulting image view object is returned. DescriptionSome of the image creation parameters are inherited by the view. In particular, image view creation inherits the implicit parameter usagej specifying the allowed usages of the image view that, by default, takes the value of the corresponding usage parameter specified in VkImageCreateInfo2 at image creation time. This implicit parameter can be overriden by chaining a 3 structure through the pNext member to VkImageViewCreateInfo% as described later in this section..The remaining parameters are contained in the  pCreateInfo.Valid Usage (Implicit)device must be a valid VkDevice handle pCreateInfo must$ be a valid pointer to a valid VkImageViewCreateInfo structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structurepView must be a valid pointer to a  VkImageView handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, , , .     .     xNone "-KSTbejk6uG9VkSamplerYcbcrConversionImageFormatProperties - Structure specifying combined image sampler descriptor count for multi-planar imagesValid Usage (Implicit)sType must be BVK_STRUCTURE_TYPE_SAMPLER_YCBCR_CONVERSION_IMAGE_FORMAT_PROPERTIESSee Also;sType is the type of this structure.<pNext is NULL1 or a pointer to an extension-specific structure.=#combinedImageSamplerDescriptorCounth is the number of combined image sampler descriptors that the implementation uses to access the format.>VkPhysicalDeviceSamplerYcbcrConversionFeatures - Structure describing Y CbCr conversion features that can be supported by an implementationMembersThe members of the .VkPhysicalDeviceSamplerYcbcrConversionFeatures+ structure describe the following feature: DescriptionsamplerYcbcrConversion4 specifies whether the implementation supports  ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#samplers-YCbCr-conversionsampler Y CBCR conversion . If samplerYcbcrConversion is VK_FALSEe, sampler Y CBCR conversion is not supported, and samplers using sampler Y CBCR conversion must not be used.Valid Usage (Implicit)sType must be CVK_STRUCTURE_TYPE_PHYSICAL_DEVICE_SAMPLER_YCBCR_CONVERSION_FEATURESSee AlsoVkBool32, C^VkImagePlaneMemoryRequirementsInfo - Structure specifying image plane for memory requirements Valid Usage planeAspect mustM be an aspect that exists in the format; that is, for a two-plane image  planeAspect must be VK_IMAGE_ASPECT_PLANE_0_BIT or VK_IMAGE_ASPECT_PLANE_1_BIT#, and for a three-plane image  planeAspect must be VK_IMAGE_ASPECT_PLANE_0_BIT, VK_IMAGE_ASPECT_PLANE_1_BIT or VK_IMAGE_ASPECT_PLANE_2_BITValid Usage (Implicit)sType must be 6VK_STRUCTURE_TYPE_IMAGE_PLANE_MEMORY_REQUIREMENTS_INFO planeAspect must be a valid  valueSee Also, EsType is the type of this structure.FpNext is NULL1 or a pointer to an extension-specific structure.G planeAspect9 is the aspect corresponding to the image plane to query.HWVkBindImagePlaneMemoryInfo - Structure specifying how to bind an image plane to memory Valid Usage planeAspect mustD be a single valid plane aspect for the image format (that is,  planeAspect must be VK_IMAGE_ASPECT_PLANE_0_BIT or VK_IMAGE_ASPECT_PLANE_1_BIT for _2PLANE  formats and  planeAspect must be VK_IMAGE_ASPECT_PLANE_0_BIT, VK_IMAGE_ASPECT_PLANE_1_BIT , or VK_IMAGE_ASPECT_PLANE_2_BIT for _3PLANE  formats)A single call to p> mustZ bind all or none of the planes of an image (i.e. bindings to all planes of an image must be made in a single p>! call), as separate bindingsValid Usage (Implicit)sType must be .VK_STRUCTURE_TYPE_BIND_IMAGE_PLANE_MEMORY_INFO planeAspect must be a valid  valueSee Also, JsType is the type of this structure.KpNext is NULL1 or a pointer to an extension-specific structure.L planeAspect3 is the aspect of the disjoint image plane to bind.MiVkSamplerYcbcrConversionCreateInfo - Structure specifying the parameters of the newly created conversion DescriptionNoteSetting forceExplicitReconstruction to VK_TRUE mayt have a performance penalty on implementations where explicit reconstruction is not the default mode of operation.If the pNext chain has an instance of  with non-zero externalFormat= member, the sampler Y CBCR conversion object represents an external format conversion, and format must be VK_FORMAT_UNDEFINED. Such conversions must5 only be used to sample image views with a matching  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-external-android-hardware-buffer-external-formatsexternal format=. When creating an external format conversion, the value of  components is ignored. Valid Usage3If an external format conversion is being created, format must be VK_FORMAT_UNDEFINED, otherwise it must not be VK_FORMAT_UNDEFINED.format must support -VK_FORMAT_FEATURE_MIDPOINT_CHROMA_SAMPLES_BIT or ,VK_FORMAT_FEATURE_COSITED_CHROMA_SAMPLES_BIT$If the format does not support ,VK_FORMAT_FEATURE_COSITED_CHROMA_SAMPLES_BIT,  xChromaOffset and  yChromaOffset must not be VK_CHROMA_LOCATION_COSITED_EVEN$If the format does not support -VK_FORMAT_FEATURE_MIDPOINT_CHROMA_SAMPLES_BIT,  xChromaOffset and  yChromaOffset must not be VK_CHROMA_LOCATION_MIDPOINTformat mustF represent unsigned normalized values (i.e. the format must be a UNORM format)If the format has a _422 or _420 suffix: components.g must be VK_COMPONENT_SWIZZLE_IDENTITY components.a must be VK_COMPONENT_SWIZZLE_IDENTITY, VK_COMPONENT_SWIZZLE_ONE, or VK_COMPONENT_SWIZZLE_ZERO components.r must be VK_COMPONENT_SWIZZLE_IDENTITY or VK_COMPONENT_SWIZZLE_B components.b must be VK_COMPONENT_SWIZZLE_IDENTITY or VK_COMPONENT_SWIZZLE_R If either  components.r or  components.b is VK_COMPONENT_SWIZZLE_IDENTITY, both values must be VK_COMPONENT_SWIZZLE_IDENTITYIf  ycbcrModel is not .VK_SAMPLER_YCBCR_MODEL_CONVERSION_RGB_IDENTITY , then  components.r,  components.g, and  components.b must$ correspond to channels of the format ; that is,  components.r,  components.g, and  components.b must not be VK_COMPONENT_SWIZZLE_ZERO or VK_COMPONENT_SWIZZLE_ONE , and mustQ not correspond to a channel which contains zero or one as a consequence of ihttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#textures-conversion-to-rgbaconversion to RGBA$If the format does not support ]VK_FORMAT_FEATURE_SAMPLED_IMAGE_YCBCR_CONVERSION_CHROMA_RECONSTRUCTION_EXPLICIT_FORCEABLE_BIT, forceExplicitReconstruction must be FALSE$If the format does not support BVK_FORMAT_FEATURE_SAMPLED_IMAGE_YCBCR_CONVERSION_LINEAR_FILTER_BIT,  chromaFilter must be VK_FILTER_NEARESTValid Usage (Implicit)sType must be 6VK_STRUCTURE_TYPE_SAMPLER_YCBCR_CONVERSION_CREATE_INFOpNext must be NULL* or a pointer to a valid instance of format must be a valid  value ycbcrModel must be a valid c value ycbcrRange must be a valid a value components must be a valid VkComponentMapping structure xChromaOffset must be a valid _ value yChromaOffset must be a valid _ value chromaFilter must be a valid  - valueIf  chromaFilter is VK_FILTER_NEAREST, chroma samples are reconstructed to luma channel resolution using nearest-neighbour sampling. Otherwise, chroma samples are reconstructed using interpolation. More details can be found in  ohttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#textures-sampler-YCbCr-conversion.the description of sampler Y CBCR conversion in the  Vhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#texturesImage Operations chapter.See AlsoVkBool32, _, ,  -, , c, a, , f, y OsType is the type of this structure.PpNext is NULL1 or a pointer to an extension-specific structure.QformatL is the format of the image from which color information will be retrieved.R ycbcrModelA describes the color matrix for conversion between color models.S ycbcrRangez describes whether the encoded values have headroom and foot room, or whether the encoding uses the full numerical range.T components applies a swizzle based on w< enums prior to range expansion and color model conversion.U xChromaOffset describes the  lhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#textures-chroma-reconstructionsample locationC associated with downsampled chroma channels in the x dimension.  xChromaOffseta has no effect for formats in which chroma channels are the same resolution as the luma channel.V yChromaOffset describes the  lhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#textures-chroma-reconstructionsample locationC associated with downsampled chroma channels in the y dimension.  yChromaOffsetX has no effect for formats in which the chroma channels are not downsampled vertically.W chromaFilter) is the filter for chroma reconstruction.XforceExplicitReconstruction canI be used to ensure that reconstruction is done explicitly, if supported.YaVkSamplerYcbcrConversionInfo - Structure specifying Y CbCr conversion to a sampler or image viewValid Usage (Implicit)sType must be /VK_STRUCTURE_TYPE_SAMPLER_YCBCR_CONVERSION_INFO conversion must be a valid VkSamplerYcbcrConversion handleSee Also^, [sType is the type of this structure.\pNext is NULL1 or a pointer to an extension-specific structure.] conversion is a ^ handle created with f.^8VkSamplerYcbcrConversion - NO SHORT DESCRIPTION PROVIDEDSee AlsoY, f, y , e, y,4Dummy data to tag the  with_9VkChromaLocation - Position of downsampled chroma samplesSee Also, Ma>VkSamplerYcbcrRange - Range of encoded values in a color space DescriptionVK_SAMPLER_YCBCR_RANGE_ITU_FULL specifies that the full range of the encoded values are valid and interpreted according to the ITU full range  quantization rules.!VK_SAMPLER_YCBCR_RANGE_ITU_NARROW specifies that headroom and foot room are reserved in the numerical range of encoded values, and the remaining values are expanded according to the ITU narrow range  quantization rules.7The formulae for these conversions is described in the  {https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#textures-sampler-YCbCr-conversion-rangeexpand Sampler Y CBCR Range Expansion section of the  Vhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#texturesImage Operations chapter.%No range modification takes place if  ycbcrModel is .VK_SAMPLER_YCBCR_MODEL_CONVERSION_RGB_IDENTITY; the  ycbcrRange field of "VkSamplerYcbcrConversionCreateInfo is ignored in this case.See Also, McFVkSamplerYcbcrModelConversion - Color model component of a color space Description.VK_SAMPLER_YCBCR_MODEL_CONVERSION_RGB_IDENTITYG specifies that the input values to the conversion are unmodified.0VK_SAMPLER_YCBCR_MODEL_CONVERSION_YCBCR_IDENTITYT specifies no model conversion but the inputs are range expanded as for Y CBCR.+VK_SAMPLER_YCBCR_MODEL_CONVERSION_YCBCR_709 specifies the color model conversion from Y CBCR to R G B' defined in BT.709 and described in the BT.709 Y CBCR conversion  section of the  Yhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#data-format+Khronos Data Format Specification.+VK_SAMPLER_YCBCR_MODEL_CONVERSION_YCBCR_601 specifies the color model conversion from Y CBCR to R G B' defined in BT.601 and described in the BT.601 Y CBCR conversion  section of the  Yhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#data-format+Khronos Data Format Specification.,VK_SAMPLER_YCBCR_MODEL_CONVERSION_YCBCR_2020 specifies the color model conversion from Y CBCR to R G B' defined in BT.2020 and described in the BT.2020 Y CBCR conversion  section of the  Yhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#data-format+Khronos Data Format Specification.In the )VK_SAMPLER_YCBCR_MODEL_CONVERSION_YCBCR_*Y color models, for the input to the sampler Y CBCR range expansion and model conversion:Jthe Y (Y' luma) channel corresponds to the G channel of an RGB image.cthe CB (CB or U  blue color difference) channel corresponds to the B channel of an RGB image.bthe CR (CR or V  red color difference) channel corresponds to the R channel of an RGB image.Nthe alpha channel, if present, is not modified by color model conversion.aThese rules reflect the mapping of channels after the channel swizzle operation (controlled by M:: components).Note[For example, an YUVA  32-bit format comprising four 8-bit channels can be implemented as VK_FORMAT_R8G8B8A8_UNORM with a component mapping: components.a = VK_COMPONENT_SWIZZLE_IDENTITY components.r = VK_COMPONENT_SWIZZLE_B components.g = VK_COMPONENT_SWIZZLE_R components.b = VK_COMPONENT_SWIZZLE_GSee Also, MeEvkDestroySamplerYcbcrConversion - Destroy a created Y CbCr conversion Parametersdevice; is the logical device that destroys the Y CBCR conversion.ycbcrConversion is the conversion to destroy. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter.Valid Usage (Implicit)device must be a valid VkDevice handleIf ycbcrConversion is not , ycbcrConversion must be a valid VkSamplerYcbcrConversion handleIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structureIf ycbcrConversion is a valid handle, it must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to ycbcrConversion must be externally synchronizedSee Also, , ^f>vkCreateSamplerYcbcrConversion - Create a new Ycbcr conversion ParametersdeviceG is the logical device that creates the sampler Y CBCR conversion. pCreateInfo) is a pointer to an instance of the M9 specifying the requested sampler Y CBCR conversion. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter.pYcbcrConversion points to a ^J handle in which the resulting sampler Y CBCR conversion is returned. Description_The interpretation of the configured sampler Y CBCR conversion is described in more detail in  ohttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#textures-sampler-YCbCr-conversion-the description of sampler Y CBCR conversion in the  Vhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#texturesImage Operations chapter. Valid UsageThe  xhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-sampler-YCbCr-conversion&sampler Y CBCR conversion feature must be enabledValid Usage (Implicit)device must be a valid VkDevice handle pCreateInfo must$ be a valid pointer to a valid "VkSamplerYcbcrConversionCreateInfo structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structurepYcbcrConversion must be a valid pointer to a VkSamplerYcbcrConversion handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, , ^, My&VK_FORMAT_G16_B16_R16_3PLANE_444_UNORM" specifies a unsigned normalized multi-planar formath that has a 16-bit G component in each 16-bit word of plane 0, a 16-bit B component in each 16-bit word of plane 1, and a 16-bit R component in each 16-bit word of plane 2. Each plane has the same dimensions and each R, G and B component contributes to a single texel. The location of each plane when this image is in linear layout can be determined via ] , using VK_IMAGE_ASPECT_PLANE_0_BIT for the G plane, VK_IMAGE_ASPECT_PLANE_1_BIT for the B plane, and VK_IMAGE_ASPECT_PLANE_2_BIT for the R plane.z%VK_FORMAT_G16_B16R16_2PLANE_422_UNORM" specifies a unsigned normalized multi-planar formatu that has a 16-bit G component in each 16-bit word of plane 0, and a two-component, 32-bit BR plane 1 consisting of a 16-bit B component in the word in bytes 0..1, and a 16-bit R component in the word in bytes 2..3. The horizontal dimensions of the BR plane is halved relative to the image dimensions, and each R and B value is shared with the G components for which *\lfloor i_G \times 0.5 \rfloor = i_B = i_RY. The location of each plane when this image is in linear layout can be determined via ] , using VK_IMAGE_ASPECT_PLANE_0_BIT for the G plane, and VK_IMAGE_ASPECT_PLANE_1_BIT* for the BR plane. Images in this format must3 be defined with a width that is a multiple of two.{&VK_FORMAT_G16_B16_R16_3PLANE_422_UNORM" specifies a unsigned normalized multi-planar formatM that has a 16-bit G component in each 16-bit word of plane 0, a 16-bit B component in each 16-bit word of plane 1, and a 16-bit R component in each 16-bit word of plane 2. The horizontal dimension of the R and B plane is halved relative to the image dimensions, and each R and B value is shared with the G components for which *\lfloor i_G \times 0.5 \rfloor = i_B = i_RY. The location of each plane when this image is in linear layout can be determined via ] , using VK_IMAGE_ASPECT_PLANE_0_BIT for the G plane, VK_IMAGE_ASPECT_PLANE_1_BIT for the B plane, and VK_IMAGE_ASPECT_PLANE_2_BIT) for the R plane. Images in this format must3 be defined with a width that is a multiple of two.|%VK_FORMAT_G16_B16R16_2PLANE_420_UNORM" specifies a unsigned normalized multi-planar format that has a 16-bit G component in each 16-bit word of plane 0, and a two-component, 32-bit BR plane 1 consisting of a 16-bit B component in the word in bytes 0..1, and a 16-bit R component in the word in bytes 2..3. The horizontal and vertical dimensions of the BR plane is halved relative to the image dimensions, and each R and B value is shared with the G components for which (lfloor i_G times 0.5 rfloor = i_B = i_R) and *\lfloor j_G \times 0.5 \rfloor = j_B = j_RZ. The location of each plane when this image is in linear layout can be determined via ] , using VK_IMAGE_ASPECT_PLANE_0_BIT for the G plane, and VK_IMAGE_ASPECT_PLANE_1_BIT* for the BR plane. Images in this format must> be defined with a width and height that is a multiple of two.}&VK_FORMAT_G16_B16_R16_3PLANE_420_UNORM" specifies a unsigned normalized multi-planar format that has a 16-bit G component in each 16-bit word of plane 0, a 16-bit B component in each 16-bit word of plane 1, and a 16-bit R component in each 16-bit word of plane 2. The horizontal and vertical dimensions of the R and B planes are halved relative to the image dimensions, and each R and B component is shared with the G components for which (lfloor i_G times 0.5 rfloor = i_B = i_R) and (lfloor j_G times 0.5 rfloor = j_B = j_R). The location of each plane when this image is in linear layout can be determined via ] , using VK_IMAGE_ASPECT_PLANE_0_BIT for the G plane, VK_IMAGE_ASPECT_PLANE_1_BIT for the B plane, and VK_IMAGE_ASPECT_PLANE_2_BIT) for the R plane. Images in this format must> be defined with a width and height that is a multiple of two.~ VK_FORMAT_B16G16R16G16_422_UNORM specifies a four-component, 64-bit format containing a pair of G components, an R component, and a B component, collectively encoding a 21 rectangle of unsigned normalized RGB texel data. One G value is present at each i coordinate, with the B and R values shared across both G values and thus recorded at half the horizontal resolution of the image. This format has a 16-bit B component in the word in bytes 0..1, a 16-bit G component for the even i~ coordinate in the word in bytes 2..3, a 16-bit R component in the word in bytes 4..5, and a 16-bit G component for the odd i> coordinate in the word in bytes 6..7. Images in this format must be defined with a width that is a multiple of two. For the purposes of the constraints on copy extents, this format is treated as a compressed format with a 21 compressed texel block. VK_FORMAT_G16B16G16R16_422_UNORM specifies a four-component, 64-bit format containing a pair of G components, an R component, and a B component, collectively encoding a 21 rectangle of unsigned normalized RGB texel data. One G value is present at each i coordinate, with the B and R values shared across both G values and thus recorded at half the horizontal resolution of the image. This format has a 16-bit G component for the even iz coordinate in the word in bytes 0..1, a 16-bit B component in the word in bytes 2..3, a 16-bit G component for the odd ir coordinate in the word in bytes 4..5, and a 16-bit R component in the word in bytes 6..7. Images in this format must be defined with a width that is a multiple of two. For the purposes of the constraints on copy extents, this format is treated as a compressed format with a 21 compressed texel block.4VK_FORMAT_G12X4_B12X4_R12X4_3PLANE_444_UNORM_3PACK16" specifies a unsigned normalized multi-planar format that has a 12-bit G component in the top 12 bits of each 16-bit word of plane 0, a 12-bit B component in the top 12 bits of each 16-bit word of plane 1, and a 12-bit R component in the top 12 bits of each 16-bit word of plane 2, with the bottom 4 bits of each word set to 0. Each plane has the same dimensions and each R, G and B component contributes to a single texel. The location of each plane when this image is in linear layout can be determined via ] , using VK_IMAGE_ASPECT_PLANE_0_BIT for the G plane, VK_IMAGE_ASPECT_PLANE_1_BIT for the B plane, and VK_IMAGE_ASPECT_PLANE_2_BIT for the R plane.3VK_FORMAT_G12X4_B12X4R12X4_2PLANE_422_UNORM_3PACK16" specifies a unsigned normalized multi-planar format that has a 12-bit G component in the top 12 bits of each 16-bit word of plane 0, and a two-component, 32-bit BR plane 1 consisting of a 12-bit B component in the top 12 bits of the word in bytes 0..1, and a 12-bit R component in the top 12 bits of the word in bytes 2..3, the bottom 4 bits of each word set to 0. The horizontal dimensions of the BR plane is halved relative to the image dimensions, and each R and B value is shared with the G components for which *\lfloor i_G \times 0.5 \rfloor = i_B = i_RY. The location of each plane when this image is in linear layout can be determined via ] , using VK_IMAGE_ASPECT_PLANE_0_BIT for the G plane, and VK_IMAGE_ASPECT_PLANE_1_BIT* for the BR plane. Images in this format must3 be defined with a width that is a multiple of two.4VK_FORMAT_G12X4_B12X4_R12X4_3PLANE_422_UNORM_3PACK16" specifies a unsigned normalized multi-planar format that has a 12-bit G component in the top 12 bits of each 16-bit word of plane 0, a 12-bit B component in the top 12 bits of each 16-bit word of plane 1, and a 12-bit R component in the top 12 bits of each 16-bit word of plane 2, with the bottom 4 bits of each word set to 0. The horizontal dimension of the R and B plane is halved relative to the image dimensions, and each R and B value is shared with the G components for which *\lfloor i_G \times 0.5 \rfloor = i_B = i_RY. The location of each plane when this image is in linear layout can be determined via ] , using VK_IMAGE_ASPECT_PLANE_0_BIT for the G plane, VK_IMAGE_ASPECT_PLANE_1_BIT for the B plane, and VK_IMAGE_ASPECT_PLANE_2_BIT) for the R plane. Images in this format must3 be defined with a width that is a multiple of two.3VK_FORMAT_G12X4_B12X4R12X4_2PLANE_420_UNORM_3PACK16" specifies a unsigned normalized multi-planar format that has a 12-bit G component in the top 12 bits of each 16-bit word of plane 0, and a two-component, 32-bit BR plane 1 consisting of a 12-bit B component in the top 12 bits of the word in bytes 0..1, and a 12-bit R component in the top 12 bits of the word in bytes 2..3, the bottom 4 bits of each word set to 0. The horizontal and vertical dimensions of the BR plane is halved relative to the image dimensions, and each R and B value is shared with the G components for which (lfloor i_G times 0.5 rfloor = i_B = i_R) and *\lfloor j_G \times 0.5 \rfloor = j_B = j_RZ. The location of each plane when this image is in linear layout can be determined via ] , using VK_IMAGE_ASPECT_PLANE_0_BIT for the G plane, and VK_IMAGE_ASPECT_PLANE_1_BIT* for the BR plane. Images in this format must> be defined with a width and height that is a multiple of two.4VK_FORMAT_G12X4_B12X4_R12X4_3PLANE_420_UNORM_3PACK16" specifies a unsigned normalized multi-planar format| that has a 12-bit G component in the top 12 bits of each 16-bit word of plane 0, a 12-bit B component in the top 12 bits of each 16-bit word of plane 1, and a 12-bit R component in the top 12 bits of each 16-bit word of plane 2, with the bottom 4 bits of each word set to 0. The horizontal and vertical dimensions of the R and B planes are halved relative to the image dimensions, and each R and B component is shared with the G components for which (lfloor i_G times 0.5 rfloor = i_B = i_R) and (lfloor j_G times 0.5 rfloor = j_B = j_R). The location of each plane when this image is in linear layout can be determined via ] , using VK_IMAGE_ASPECT_PLANE_0_BIT for the G plane, VK_IMAGE_ASPECT_PLANE_1_BIT for the B plane, and VK_IMAGE_ASPECT_PLANE_2_BIT) for the R plane. Images in this format must> be defined with a width and height that is a multiple of two.0VK_FORMAT_B12X4G12X4R12X4G12X4_422_UNORM_4PACK16 specifies a four-component, 64-bit format containing a pair of G components, an R component, and a B component, collectively encoding a 21 rectangle of unsigned normalized RGB texel data. One G value is present at each i coordinate, with the B and R values shared across both G values and thus recorded at half the horizontal resolution of the image. This format has a 12-bit B component in the top 12 bits of the word in bytes 0..1, a 12-bit G component for the even i coordinate in the top 12 bits of the word in bytes 2..3, a 12-bit R component in the top 12 bits of the word in bytes 4..5, and a 12-bit G component for the odd i coordinate in the top 12 bits of the word in bytes 6..7, with the bottom 4 bits of each word set to 0. Images in this format must be defined with a width that is a multiple of two. For the purposes of the constraints on copy extents, this format is treated as a compressed format with a 21 compressed texel block.0VK_FORMAT_G12X4B12X4G12X4R12X4_422_UNORM_4PACK16 specifies a four-component, 64-bit format containing a pair of G components, an R component, and a B component, collectively encoding a 21 rectangle of unsigned normalized RGB texel data. One G value is present at each i coordinate, with the B and R values shared across both G values and thus recorded at half the horizontal resolution of the image. This format has a 12-bit G component for the even i coordinate in the top 12 bits of the word in bytes 0..1, a 12-bit B component in the top 12 bits of the word in bytes 2..3, a 12-bit G component for the odd i coordinate in the top 12 bits of the word in bytes 4..5, and a 12-bit R component in the top 12 bits of the word in bytes 6..7, with the bottom 4 bits of each word set to 0. Images in this format must be defined with a width that is a multiple of two. For the purposes of the constraints on copy extents, this format is treated as a compressed format with a 21 compressed texel block.,VK_FORMAT_R12X4G12X4B12X4A12X4_UNORM_4PACK16 specifies a four-component, 64-bit unsigned normalized format that has a 12-bit R component in the top 12 bits of the word in bytes 0..1, a 12-bit G component in the top 12 bits of the word in bytes 2..3, a 12-bit B component in the top 12 bits of the word in bytes 4..5, and a 12-bit A component in the top 12 bits of the word in bytes 6..7, with the bottom 4 bits of each word set to 0."VK_FORMAT_R12X4G12X4_UNORM_2PACK16 specifies a two-component, 32-bit unsigned normalized format that has a 12-bit R component in the top 12 bits of the word in bytes 0..1, and a 12-bit G component in the top 12 bits of the word in bytes 2..3, with the bottom 4 bits of each word set to 0.VK_FORMAT_R12X4_UNORM_PACK16 specifies a one-component, 16-bit unsigned normalized format that has a single 12-bit R component in the top 12 bits of a 16-bit word, with the bottom 4 bits set to 0.4VK_FORMAT_G10X6_B10X6_R10X6_3PLANE_444_UNORM_3PACK16" specifies a unsigned normalized multi-planar format that has a 10-bit G component in the top 10 bits of each 16-bit word of plane 0, a 10-bit B component in the top 10 bits of each 16-bit word of plane 1, and a 10-bit R component in the top 10 bits of each 16-bit word of plane 2, with the bottom 6 bits of each word set to 0. Each plane has the same dimensions and each R, G and B component contributes to a single texel. The location of each plane when this image is in linear layout can be determined via ] , using VK_IMAGE_ASPECT_PLANE_0_BIT for the G plane, VK_IMAGE_ASPECT_PLANE_1_BIT for the B plane, and VK_IMAGE_ASPECT_PLANE_2_BIT for the R plane.3VK_FORMAT_G10X6_B10X6R10X6_2PLANE_422_UNORM_3PACK16" specifies a unsigned normalized multi-planar format that has a 10-bit G component in the top 10 bits of each 16-bit word of plane 0, and a two-component, 32-bit BR plane 1 consisting of a 10-bit B component in the top 10 bits of the word in bytes 0..1, and a 10-bit R component in the top 10 bits of the word in bytes 2..3, the bottom 6 bits of each word set to 0. The horizontal dimensions of the BR plane is halved relative to the image dimensions, and each R and B value is shared with the G components for which *\lfloor i_G \times 0.5 \rfloor = i_B = i_RY. The location of each plane when this image is in linear layout can be determined via ] , using VK_IMAGE_ASPECT_PLANE_0_BIT for the G plane, and VK_IMAGE_ASPECT_PLANE_1_BIT* for the BR plane. Images in this format must3 be defined with a width that is a multiple of two.4VK_FORMAT_G10X6_B10X6_R10X6_3PLANE_422_UNORM_3PACK16" specifies a unsigned normalized multi-planar format that has a 10-bit G component in the top 10 bits of each 16-bit word of plane 0, a 10-bit B component in the top 10 bits of each 16-bit word of plane 1, and a 10-bit R component in the top 10 bits of each 16-bit word of plane 2, with the bottom 6 bits of each word set to 0. The horizontal dimension of the R and B plane is halved relative to the image dimensions, and each R and B value is shared with the G components for which *\lfloor i_G \times 0.5 \rfloor = i_B = i_RY. The location of each plane when this image is in linear layout can be determined via ] , using VK_IMAGE_ASPECT_PLANE_0_BIT for the G plane, VK_IMAGE_ASPECT_PLANE_1_BIT for the B plane, and VK_IMAGE_ASPECT_PLANE_2_BIT) for the R plane. Images in this format must3 be defined with a width that is a multiple of two.3VK_FORMAT_G10X6_B10X6R10X6_2PLANE_420_UNORM_3PACK16" specifies a unsigned normalized multi-planar format that has a 10-bit G component in the top 10 bits of each 16-bit word of plane 0, and a two-component, 32-bit BR plane 1 consisting of a 10-bit B component in the top 10 bits of the word in bytes 0..1, and a 10-bit R component in the top 10 bits of the word in bytes 2..3, the bottom 6 bits of each word set to 0. The horizontal and vertical dimensions of the BR plane is halved relative to the image dimensions, and each R and B value is shared with the G components for which (lfloor i_G times 0.5 rfloor = i_B = i_R) and *\lfloor j_G \times 0.5 \rfloor = j_B = j_RZ. The location of each plane when this image is in linear layout can be determined via ] , using VK_IMAGE_ASPECT_PLANE_0_BIT for the G plane, and VK_IMAGE_ASPECT_PLANE_1_BIT* for the BR plane. Images in this format must> be defined with a width and height that is a multiple of two.4VK_FORMAT_G10X6_B10X6_R10X6_3PLANE_420_UNORM_3PACK16" specifies a unsigned normalized multi-planar format| that has a 10-bit G component in the top 10 bits of each 16-bit word of plane 0, a 10-bit B component in the top 10 bits of each 16-bit word of plane 1, and a 10-bit R component in the top 10 bits of each 16-bit word of plane 2, with the bottom 6 bits of each word set to 0. The horizontal and vertical dimensions of the R and B planes are halved relative to the image dimensions, and each R and B component is shared with the G components for which (lfloor i_G times 0.5 rfloor = i_B = i_R) and (lfloor j_G times 0.5 rfloor = j_B = j_R). The location of each plane when this image is in linear layout can be determined via ] , using VK_IMAGE_ASPECT_PLANE_0_BIT for the G plane, VK_IMAGE_ASPECT_PLANE_1_BIT for the B plane, and VK_IMAGE_ASPECT_PLANE_2_BIT) for the R plane. Images in this format must> be defined with a width and height that is a multiple of two.0VK_FORMAT_B10X6G10X6R10X6G10X6_422_UNORM_4PACK16 specifies a four-component, 64-bit format containing a pair of G components, an R component, and a B component, collectively encoding a 21 rectangle of unsigned normalized RGB texel data. One G value is present at each i coordinate, with the B and R values shared across both G values and thus recorded at half the horizontal resolution of the image. This format has a 10-bit B component in the top 10 bits of the word in bytes 0..1, a 10-bit G component for the even i coordinate in the top 10 bits of the word in bytes 2..3, a 10-bit R component in the top 10 bits of the word in bytes 4..5, and a 10-bit G component for the odd i coordinate in the top 10 bits of the word in bytes 6..7, with the bottom 6 bits of each word set to 0. Images in this format must be defined with a width that is a multiple of two. For the purposes of the constraints on copy extents, this format is treated as a compressed format with a 21 compressed texel block.0VK_FORMAT_G10X6B10X6G10X6R10X6_422_UNORM_4PACK16 specifies a four-component, 64-bit format containing a pair of G components, an R component, and a B component, collectively encoding a 21 rectangle of unsigned normalized RGB texel data. One G value is present at each i coordinate, with the B and R values shared across both G values and thus recorded at half the horizontal resolution of the image. This format has a 10-bit G component for the even i coordinate in the top 10 bits of the word in bytes 0..1, a 10-bit B component in the top 10 bits of the word in bytes 2..3, a 10-bit G component for the odd i coordinate in the top 10 bits of the word in bytes 4..5, and a 10-bit R component in the top 10 bits of the word in bytes 6..7, with the bottom 6 bits of each word set to 0. Images in this format must be defined with a width that is a multiple of two. For the purposes of the constraints on copy extents, this format is treated as a compressed format with a 21 compressed texel block.,VK_FORMAT_R10X6G10X6B10X6A10X6_UNORM_4PACK16 specifies a four-component, 64-bit unsigned normalized format that has a 10-bit R component in the top 10 bits of the word in bytes 0..1, a 10-bit G component in the top 10 bits of the word in bytes 2..3, a 10-bit B component in the top 10 bits of the word in bytes 4..5, and a 10-bit A component in the top 10 bits of the word in bytes 6..7, with the bottom 6 bits of each word set to 0."VK_FORMAT_R10X6G10X6_UNORM_2PACK16 specifies a two-component, 32-bit unsigned normalized format that has a 10-bit R component in the top 10 bits of the word in bytes 0..1, and a 10-bit G component in the top 10 bits of the word in bytes 2..3, with the bottom 6 bits of each word set to 0.VK_FORMAT_R10X6_UNORM_PACK16 specifies a one-component, 16-bit unsigned normalized format that has a single 10-bit R component in the top 10 bits of a 16-bit word, with the bottom 6 bits set to 0.#VK_FORMAT_G8_B8_R8_3PLANE_444_UNORM" specifies a unsigned normalized multi-planar format+ that has an 8-bit G component in plane 0, an 8-bit B component in plane 1, and an 8-bit R component in plane 2. Each plane has the same dimensions and each R, G and B component contributes to a single texel. The location of each plane when this image is in linear layout can be determined via ] , using VK_IMAGE_ASPECT_PLANE_0_BIT for the G plane, VK_IMAGE_ASPECT_PLANE_1_BIT for the B plane, and VK_IMAGE_ASPECT_PLANE_2_BIT for the R plane."VK_FORMAT_G8_B8R8_2PLANE_422_UNORM" specifies a unsigned normalized multi-planar format? that has an 8-bit G component in plane 0, and a two-component, 16-bit BR plane 1 consisting of an 8-bit B component in byte 0 and an 8-bit R component in byte 1. The horizontal dimensions of the BR plane is halved relative to the image dimensions, and each R and B value is shared with the G components for which *\lfloor i_G \times 0.5 \rfloor = i_B = i_RY. The location of each plane when this image is in linear layout can be determined via ] , using VK_IMAGE_ASPECT_PLANE_0_BIT for the G plane, and VK_IMAGE_ASPECT_PLANE_1_BIT* for the BR plane. Images in this format must3 be defined with a width that is a multiple of two.#VK_FORMAT_G8_B8_R8_3PLANE_422_UNORM" specifies a unsigned normalized multi-planar format that has an 8-bit G component in plane 0, an 8-bit B component in plane 1, and an 8-bit R component in plane 2. The horizontal dimension of the R and B plane is halved relative to the image dimensions, and each R and B value is shared with the G components for which *\lfloor i_G \times 0.5 \rfloor = i_B = i_RY. The location of each plane when this image is in linear layout can be determined via ] , using VK_IMAGE_ASPECT_PLANE_0_BIT for the G plane, VK_IMAGE_ASPECT_PLANE_1_BIT for the B plane, and VK_IMAGE_ASPECT_PLANE_2_BIT) for the R plane. Images in this format must3 be defined with a width that is a multiple of two."VK_FORMAT_G8_B8R8_2PLANE_420_UNORM" specifies a unsigned normalized multi-planar format{ that has an 8-bit G component in plane 0, and a two-component, 16-bit BR plane 1 consisting of an 8-bit B component in byte 0 and an 8-bit R component in byte 1. The horizontal and vertical dimensions of the BR plane is halved relative to the image dimensions, and each R and B value is shared with the G components for which (lfloor i_G times 0.5 rfloor = i_B = i_R) and *\lfloor j_G \times 0.5 \rfloor = j_B = j_RZ. The location of each plane when this image is in linear layout can be determined via ] , using VK_IMAGE_ASPECT_PLANE_0_BIT for the G plane, and VK_IMAGE_ASPECT_PLANE_1_BIT* for the BR plane. Images in this format must> be defined with a width and height that is a multiple of two.#VK_FORMAT_G8_B8_R8_3PLANE_420_UNORM" specifies a unsigned normalized multi-planar format that has an 8-bit G component in plane 0, an 8-bit B component in plane 1, and an 8-bit R component in plane 2. The horizontal and vertical dimensions of the R and B planes are halved relative to the image dimensions, and each R and B component is shared with the G components for which (lfloor i_G times 0.5 rfloor = i_B = i_R) and (lfloor j_G times 0.5 rfloor = j_B = j_R). The location of each plane when this image is in linear layout can be determined via ] , using VK_IMAGE_ASPECT_PLANE_0_BIT for the G plane, VK_IMAGE_ASPECT_PLANE_1_BIT for the B plane, and VK_IMAGE_ASPECT_PLANE_2_BIT) for the R plane. Images in this format must> be defined with a width and height that is a multiple of two.VK_FORMAT_B8G8R8G8_422_UNORM specifies a four-component, 32-bit format containing a pair of G components, an R component, and a B component, collectively encoding a 21 rectangle of unsigned normalized RGB texel data. One G value is present at each i coordinate, with the B and R values shared across both G values and thus recorded at half the horizontal resolution of the image. This format has an 8-bit B component in byte 0, an 8-bit G component for the even i] coordinate in byte 1, an 8-bit R component in byte 2, and an 8-bit G component for the odd i. coordinate in byte 3. Images in this format must be defined with a width that is a multiple of two. For the purposes of the constraints on copy extents, this format is treated as a compressed format with a 21 compressed texel block.VK_FORMAT_G8B8G8R8_422_UNORM specifies a four-component, 32-bit format containing a pair of G components, an R component, and a B component, collectively encoding a 21 rectangle of unsigned normalized RGB texel data. One G value is present at each i coordinate, with the B and R values shared across both G values and thus recorded at half the horizontal resolution of the image. This format has an 8-bit G component for the even iY coordinate in byte 0, an 8-bit B component in byte 1, an 8-bit G component for the odd iR coordinate in byte 2, and an 8-bit R component in byte 3. Images in this format must be defined with a width that is a multiple of two. For the purposes of the constraints on copy extents, this format is treated as a compressed format with a 21 compressed texel block.VK_CHROMA_LOCATION_MIDPOINT specifies that downsampled chroma samples are located half way between each even luma sample and the nearest higher odd luma sample.VK_CHROMA_LOCATION_COSITED_EVEN` specifies that downsampled chroma samples are aligned with luma samples with even coordinates.k9:;<=>?@ABCDEFGHIJKLMNOPQTRSUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~kcdab_`~}|{zyxwvutsrqponmlkjihg^feYZ[\]MNOPQTRSUVWXHIJKLCDEFG>?@AB9:;<=yNone-STejk6CR     R     zNone "-KSTbejk7D 5VkFenceCreateFlags - Bitmask of VkFenceCreateFlagBits DescriptionVkFenceCreateFlags7 is a bitmask type for setting a mask of zero or more .See Also, MVkFenceCreateInfo - Structure specifying parameters of a newly created fenceValid Usage (Implicit)sType must be #VK_STRUCTURE_TYPE_FENCE_CREATE_INFOEach pNext: member of any structure (including this one) in the pNext chain must be either NULL/ or a pointer to a valid instance of ; or Each sType member in the pNext chain must be uniqueflags must be a valid combination of  valuesSee Also, , #sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.flags is a bitmask of 9 specifying the initial state and behavior of the fence.QVkFenceCreateFlagBits - Bitmask specifying initial state and behavior of a fenceSee Also@vkWaitForFences - Wait for one or more fences to become signaled Parametersdevice, is the logical device that owns the fences. fenceCount$ is the number of fences to wait on.pFences is a pointer to an array of  fenceCount fence handles.waitAll is the condition that must8 be satisfied to successfully unblock the wait. If waitAll is VK_TRUE0, then the condition is that all fences in pFencesK are signaled. Otherwise, the condition is that at least one fence in pFences is signaled.timeout0 is the timeout period in units of nanoseconds. timeoutl is adjusted to the closest value allowed by the implementation-dependent timeout accuracy, which may7 be substantially longer than one nanosecond, and may* be longer than the requested period. Description#If the condition is satisfied when vkWaitForFences is called, then vkWaitForFencesE returns immediately. If the condition is not satisfied at the time vkWaitForFences is called, then vkWaitForFences will block and wait up to timeout4 nanoseconds for the condition to become satisfied.If timeout is zero, then vkWaitForFencesE does not wait, but simply returns the current state of the fences.  VK_TIMEOUTm will be returned in this case if the condition is not satisfied, even though no actual wait was performed.LIf the specified timeout period expires before the condition is satisfied, vkWaitForFences returns  VK_TIMEOUT(. If the condition is satisfied before timeout nanoseconds has expired, vkWaitForFences returns  VK_SUCCESS.If device loss occurs (see  ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#devsandqueues-lost-device Lost Device#) before the timeout has expired, vkWaitForFences must$ return in finite time with either  VK_SUCCESS or VK_ERROR_DEVICE_LOST.NoteWhile we guarantee that vkWaitForFences must return in finite time, no guarantees are made that it returns immediately upon device loss. However, the client can reasonably expect that the delay will be on the order of seconds and that calling vkWaitForFencesK will not result in a permanently (or seemingly permanently) dead process.Valid Usage (Implicit)device must be a valid VkDevice handlepFences must# be a valid pointer to an array of  fenceCount valid VkFence handles fenceCount must be greater than 0Each element of pFences must6 have been created, allocated, or retrieved from device Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS  VK_TIMEOUT ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_DEVICE_LOSTSee AlsoVkBool32, ,  /vkGetFenceStatus - Return the status of a fence Parametersdevice+ is the logical device that owns the fence.fence% is the handle of the fence to query. DescriptionUpon success, vkGetFenceStatusJ returns the status of the fence object, with the following return codes:# Status s Meaning   VK_SUCCESS  The fence specified by fenceT is signaled.   VK_NOT_READY  The fence specified by fenceT is unsignaled.  VK_ERROR_DEVICE_LOST0  The device has been lost. See  ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#devsandqueues-lost-device[Lost Device. Fence Object Status CodesIf a  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#devsandqueues-submissionqueue submissionI command is pending execution, then the value returned by this command may immediately be out of date.!If the device has been lost (see  ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#devsandqueues-lost-device Lost Device), vkGetFenceStatus mayH return any of the above status codes. If the device has been lost and vkGetFenceStatus9 is called repeatedly, it will eventually return either  VK_SUCCESS or VK_ERROR_DEVICE_LOST.Valid Usage (Implicit)device must be a valid VkDevice handlefence must be a valid VkFence handlefence must6 have been created, allocated, or retrieved from device Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS  VK_NOT_READY ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_DEVICE_LOSTSee Also, !0vkResetFences - Resets one or more fence objects Parametersdevice, is the logical device that owns the fences. fenceCount" is the number of fences to reset.pFences4 is a pointer to an array of fence handles to reset. DescriptionIf any member of pFences currently has its  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-fences-importingpayload imported with temporary permanence, that fence s prior permanent payload is first restored. The remaining operations described therefore operate on the restored payload.When ! is executed on the host, it defines a /fence unsignal operation/ for each fence, which resets the fence to the unsignaled state.If any member of pFences* is already in the unsignaled state when ! is executed, then ! has no effect on that fence. Valid UsageEach element of pFences mustk not be currently associated with any queue command that has not yet completed execution on that queueValid Usage (Implicit)device must be a valid VkDevice handlepFences must# be a valid pointer to an array of  fenceCount valid VkFence handles fenceCount must be greater than 0Each element of pFences must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to each member of pFences must be externally synchronized Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, "'vkDestroyFence - Destroy a fence object Parametersdevice/ is the logical device that destroys the fence.fence' is the handle of the fence to destroy. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. Valid UsageAll  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#devsandqueues-submissionqueue submission commands that refer to fence must have completed executionIf VkAllocationCallbacks were provided when fence1 was created, a compatible set of callbacks must be provided hereIf no VkAllocationCallbacks were provided when fence was created,  pAllocator must be NULLValid Usage (Implicit)device must be a valid VkDevice handleIf fence is not , fence must be a valid VkFence handleIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structureIf fence is a valid handle, it must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to fence must be externally synchronizedSee Also, , #)vkCreateFence - Create a new fence object Parametersdevice. is the logical device that creates the fence. pCreateInfo$ is a pointer to an instance of the VkFenceCreateInfoU structure which contains information about how the fence is to be created. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter.pFenceI points to a handle in which the resulting fence object is returned.Valid Usage (Implicit)device must be a valid VkDevice handle pCreateInfo must$ be a valid pointer to a valid VkFenceCreateInfo structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structurepFence must be a valid pointer to a VkFence handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, , , $VK_FENCE_CREATE_SIGNALED_BITv specifies that the fence object is created in the signaled state. Otherwise, it is created in the unsignaled state. !"#$$#"! {None "-STbejk7Α/CVkExtensionProperties - Structure specifying a extension propertiesSee Also4, 51 extensionNameC is a null-terminated string specifying the name of the extension.2 specVersionc is the version of this extension. It is an integer, incremented with backward compatible changes.4bvkEnumerateDeviceExtensionProperties - Returns properties of available physical device extensions ParametersphysicalDevice- is the physical device that will be queried. pLayerName is either NULLb or a pointer to a null-terminated UTF-8 string naming the layer to retrieve extensions from.pPropertyCount is a pointer to an integer related to the number of extension properties available or queried, and is treated in the same fashion as the 5::pPropertyCount parameter. pProperties is either NULL" or a pointer to an array of / structures. DescriptionWhen  pLayerName parameter is NULLm, only extensions provided by the Vulkan implementation or by implicitly enabled layers are returned. When  pLayerNameT is the name of a layer, the device extensions provided by that layer are returned.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handleIf  pLayerName is not NULL,  pLayerName must' be a null-terminated UTF-8 stringpPropertyCount must be a valid pointer to a uint32_t valueIf the value referenced by pPropertyCount is not 0 , and  pProperties is not NULL,  pProperties must( be a valid pointer to an array of pPropertyCount VkExtensionProperties structures Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS  VK_INCOMPLETE ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_LAYER_NOT_PRESENTSee Also/, 5gvkEnumerateInstanceExtensionProperties - Returns up to requested number of global extension properties Parameters pLayerName is either NULLb or a pointer to a null-terminated UTF-8 string naming the layer to retrieve extensions from.pPropertyCountx is a pointer to an integer related to the number of extension properties available or queried, as described below. pProperties is either NULL" or a pointer to an array of / structures. DescriptionWhen  pLayerName parameter is NULLm, only extensions provided by the Vulkan implementation or by implicitly enabled layers are returned. When  pLayerNameV is the name of a layer, the instance extensions provided by that layer are returned.If  pProperties is NULLE, then the number of extensions properties available is returned in pPropertyCount . Otherwise, pPropertyCount mustG point to a variable set by the user to the number of elements in the  pPropertiese array, and on return the variable is overwritten with the number of structures actually written to  pProperties. If pPropertyCountE is less than the number of extension properties available, at most pPropertyCount! structures will be written. If pPropertyCount6 is smaller than the number of extensions available,  VK_INCOMPLETE will be returned instead of  VK_SUCCESSC, to indicate that not all the available properties were returned.MBecause the list of available layers may change externally between calls to &vkEnumerateInstanceExtensionProperties1, two calls may retrieve different results if a  pLayerName is available in one call but not in another. The extensions supported by a layer may also change between two calls, e.g. if the layer implementation is replaced by a different version between those calls.Valid Usage (Implicit)If  pLayerName is not NULL,  pLayerName must' be a null-terminated UTF-8 stringpPropertyCount must be a valid pointer to a uint32_t valueIf the value referenced by pPropertyCount is not 0 , and  pProperties is not NULL,  pProperties must( be a valid pointer to an array of pPropertyCount VkExtensionProperties structures Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS  VK_INCOMPLETE ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_LAYER_NOT_PRESENTSee Also//01234563654/012|None "-STbejk8::9VkLayerProperties - Structure specifying layer propertiesSee AlsoA, B< layerName[ is a null-terminated UTF-8 string specifying the name of the layer. Use this name in the ppEnabledLayerNames array passed in the />1 structure to enable this layer for an instance.= specVersionN is the Vulkan version the layer was written to, encoded as described in the  ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-versionnum"API Version Numbers and Semantics section.>implementationVersion^ is the version of this layer. It is an integer, increasing with backward compatible changes.? descriptionF is a null-terminated UTF-8 string providing additional details that can2 be used by the application to identify the layer.AZvkEnumerateDeviceLayerProperties - Returns properties of available physical device layers ParameterspPropertyCount` is a pointer to an integer related to the number of layer properties available or queried. pProperties is either NULL" or a pointer to an array of : structures. DescriptionIf  pProperties is NULL@, then the number of layer properties available is returned in pPropertyCount . Otherwise, pPropertyCount mustG point to a variable set by the user to the number of elements in the  pPropertiese array, and on return the variable is overwritten with the number of structures actually written to  pProperties. If pPropertyCountA is less than the number of layer properties available, at most pPropertyCount structures will be written. If pPropertyCount2 is smaller than the number of layers available,  VK_INCOMPLETE will be returned instead of  VK_SUCCESSI, to indicate that not all the available layer properties were returned.!The list of layers enumerated by  vkEnumerateDeviceLayerProperties mustM be exactly the sequence of layers enabled for the instance. The members of VkLayerProperties for each enumerated layer mustB be the same as the properties when the layer was enumerated by "vkEnumerateInstanceLayerProperties.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handlepPropertyCount must be a valid pointer to a uint32_t valueIf the value referenced by pPropertyCount is not 0 , and  pProperties is not NULL,  pProperties must( be a valid pointer to an array of pPropertyCount VkLayerProperties structures Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS  VK_INCOMPLETE ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also:, B_vkEnumerateInstanceLayerProperties - Returns up to requested number of global layer properties ParameterspPropertyCountt is a pointer to an integer related to the number of layer properties available or queried, as described below. pProperties is either NULL" or a pointer to an array of : structures. DescriptionIf  pProperties is NULL@, then the number of layer properties available is returned in pPropertyCount . Otherwise, pPropertyCount mustG point to a variable set by the user to the number of elements in the  pPropertiese array, and on return the variable is overwritten with the number of structures actually written to  pProperties. If pPropertyCountA is less than the number of layer properties available, at most pPropertyCount structures will be written. If pPropertyCount2 is smaller than the number of layers available,  VK_INCOMPLETE will be returned instead of  VK_SUCCESSI, to indicate that not all the available layer properties were returned.{The list of available layers may change at any time due to actions outside of the Vulkan implementation, so two calls to "vkEnumerateInstanceLayerProperties with the same parameters may2 return different results, or retrieve different pPropertyCount values or  pProperties contents. Once an instance has been created, the layers enabled for that instance will continue to be enabled and valid for the lifetime of that instance, even if some of them become unavailable for future instances.Valid Usage (Implicit)pPropertyCount must be a valid pointer to a uint32_t valueIf the value referenced by pPropertyCount is not 0 , and  pProperties is not NULL,  pProperties must( be a valid pointer to an array of pPropertyCount VkLayerProperties structures Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS  VK_INCOMPLETE ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also: :;=<>?@ABC @CBA:;=<>?}None "-KSTbejk8 GMVkEventCreateInfo - Structure specifying parameters of a newly created eventValid Usage (Implicit)sType must be #VK_STRUCTURE_TYPE_EVENT_CREATE_INFOpNext must be NULLflags must be 0See AlsoM, , SIsType is the type of this structure.JpNext is NULL1 or a pointer to an extension-specific structure.Kflags is reserved for future use.L)VkEvent - Opaque handle to a event objectSee Also, , , S, R, Q, O, P5Dummy data to tag the  withM,VkEventCreateFlags - Reserved for future use DescriptionVkEventCreateFlagsQ is a bitmask type for setting a mask, but is currently reserved for future use.See AlsoGO3vkResetEvent - Reset an event to non-signaled state Parametersdevice+ is the logical device that owns the event.event is the event to reset. DescriptionWhen Os is executed on the host, it defines an /event unsignal operation/ which resets the event to the unsignaled state.If event) is already in the unsignaled state when O is executed, then O8 has no effect, and no event unsignal operation occurs. Valid Usageevent must not be waited on by a vkCmdWaitEvents) command that is currently executingValid Usage (Implicit)device must be a valid VkDevice handleevent must be a valid VkEvent handleevent must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to event must be externally synchronized Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, LP+vkSetEvent - Set an event to signaled state Parametersdevice+ is the logical device that owns the event.event is the event to set. DescriptionWhen Pm is executed on the host, it defines an /event signal operation/ which sets the event to the signaled state.If event' is already in the signaled state when P is executed, then P6 has no effect, and no event signal operation occurs.Valid Usage (Implicit)device must be a valid VkDevice handleevent must be a valid VkEvent handleevent must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to event must be externally synchronized Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, LQ9vkGetEventStatus - Retrieve the status of an event object Parametersdevice+ is the logical device that owns the event.event% is the handle of the event to query. DescriptionUpon success, vkGetEventStatusH returns the state of the event object with the following return codes:# Status # Meaning   VK_EVENT_SET8  The event specified by event( is signaled.  VK_EVENT_RESET6  The event specified by event( is unsignaled. Event Object Status CodesIf a  vkCmdSetEvent or vkCmdResetEvent0 command is in a command buffer that is in the  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclepending state+, then the value returned by this command may immediately be out of date.The state of an event cana be updated by the host. The state of the event is immediately changed, and subsequent calls to vkGetEventStatus~ will return the new state. If an event is already in the requested state, then updating it to the same state has no effect.Valid Usage (Implicit)device must be a valid VkDevice handleevent must be a valid VkEvent handleevent must6 have been created, allocated, or retrieved from device Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_EVENT_SET VK_EVENT_RESET ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_DEVICE_LOSTSee Also, LR(vkDestroyEvent - Destroy an event object Parametersdevice/ is the logical device that destroys the event.event' is the handle of the event to destroy. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. Valid Usage%All submitted commands that refer to event must have completed executionIf VkAllocationCallbacks were provided when event1 was created, a compatible set of callbacks must be provided hereIf no VkAllocationCallbacks were provided when event was created,  pAllocator must be NULLValid Usage (Implicit)device must be a valid VkDevice handleIf event is not , event must be a valid VkEvent handleIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structureIf event is a valid handle, it must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to event must be externally synchronizedSee Also, , LS)vkCreateEvent - Create a new event object Parametersdevice. is the logical device that creates the event. pCreateInfo$ is a pointer to an instance of the VkEventCreateInfoU structure which contains information about how the event is to be created. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter.pEventI points to a handle in which the resulting event object is returned. Description:When created, the event object is in the unsignaled state.Valid Usage (Implicit)device must be a valid VkDevice handle pCreateInfo must$ be a valid pointer to a valid VkEventCreateInfo structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structurepEvent must be a valid pointer to a VkEvent handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, , L, G GHIJKLMNOPQRS MNLSRQPOGHIJK~None "-KSTbejk9'^AVkDeviceQueueCreateFlags - Bitmask of VkDeviceQueueCreateFlagBits DescriptionVkDeviceQueueCreateFlags7 is a bitmask type for setting a mask of zero or more s.See Alsos, k,  _OVkDeviceCreateInfo - Structure specifying parameters of a newly created device Valid UsageThe queueFamilyIndex member of each element of pQueueCreateInfos must be unique within pQueueCreateInfosIf the pNext chain includes a s\ structure, then pEnabledFeatures must be NULLppEnabledExtensionNames must not contain both ({html_spec_relative}#VK_KHR_maintenance1 and 4{html_spec_relative}#VK_AMD_negative_viewport_heightValid Usage (Implicit)sType must be $VK_STRUCTURE_TYPE_DEVICE_CREATE_INFOEach pNext: member of any structure (including this one) in the pNext chain must be either NULL/ or a pointer to a valid instance of =, P, T, s\, b, g, xl, or rEach sType member in the pNext chain must be uniqueflags must be 0pQueueCreateInfos must( be a valid pointer to an array of queueCreateInfoCount valid VkDeviceQueueCreateInfo structuresIf enabledLayerCount is not 0, ppEnabledLayerNames must( be a valid pointer to an array of enabledLayerCount# null-terminated UTF-8 stringsIf enabledExtensionCount is not 0, ppEnabledExtensionNames must# be a valid pointer to an array of enabledExtensionCount# null-terminated UTF-8 stringsIf pEnabledFeatures is not NULL, pEnabledFeatures must$ be a valid pointer to a valid VkPhysicalDeviceFeatures structurequeueCreateInfoCount must be greater than 0See Alsou, k, X, , xasType is the type of this structure.bpNext is NULL1 or a pointer to an extension-specific structure.cflags is reserved for future use.dqueueCreateInfoCount& is the unsigned integer size of the pQueueCreateInfos array. Refer to the  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#devsandqueues-queue-creationQueue Creation$ section below for further details.epQueueCreateInfos is a pointer to an array of kq structures describing the queues that are requested to be created along with the logical device. Refer to the  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#devsandqueues-queue-creationQueue Creation$ section below for further details.fenabledLayerCount is deprecated and ignored.gppEnabledLayerNames is deprecated and ignored. See  }https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#extended-functionality-device-layer-deprecationDevice Layer Deprecation.henabledExtensionCount. is the number of device extensions to enable.ippEnabledExtensionNames is a pointer to an array of enabledExtensionCountn null-terminated UTF-8 strings containing the names of extensions to enable for the created device. See the  ohttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#extended-functionality-extensions Extensions section for further details.jpEnabledFeatures is NULL or a pointer to a X_ structure that contains boolean indicators of all the features to be enabled. Refer to the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-featuresFeatures section for further details.kZVkDeviceQueueCreateInfo - Structure specifying parameters of a newly created device queue Valid UsagequeueFamilyIndex must be less than pQueueFamilyPropertyCount returned by (vkGetPhysicalDeviceQueueFamilyProperties queueCount must be less than or equal to the  queueCount member of the VkQueueFamilyProperties structure, as returned by (vkGetPhysicalDeviceQueueFamilyProperties in the pQueueFamilyProperties[queueFamilyIndex]Each element of pQueuePriorities must be between 0.0 and 1.0 inclusiveValid Usage (Implicit)sType must be *VK_STRUCTURE_TYPE_DEVICE_QUEUE_CREATE_INFOpNext must be NULL* or a pointer to a valid instance of  flags must be a valid combination of s valuespQueuePriorities must( be a valid pointer to an array of  queueCount float values queueCount must be greater than 0See Also_, ^, msType is the type of this structure.npNext is NULL1 or a pointer to an extension-specific structure.oflags is reserved for future use.pqueueFamilyIndex is an unsigned integer indicating the index of the queue family to create on this device. This index corresponds to the index of an element of the pQueueFamilyProperties array that was returned by (vkGetPhysicalDeviceQueueFamilyProperties.q queueCountd is an unsigned integer specifying the number of queues to create in the queue family indicated by queueFamilyIndex.rpQueuePriorities is an array of  queueCountu normalized floating point values, specifying priorities of work that will be submitted to each created queue. See  dhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#devsandqueues-priorityQueue Priority for more information.sFVkDeviceQueueCreateFlagBits - Bitmask specifying behavior of the queueSee Also^u-VkDeviceCreateFlags - Reserved for future use DescriptionVkDeviceCreateFlagsQ is a bitmask type for setting a mask, but is currently reserved for future use.See Also_w*vkDestroyDevice - Destroy a logical device Parametersdevice" is the logical device to destroy. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. Description1To ensure that no work is active on the device, @B can be used to gate the destruction of the device. Prior to destroying a device, an application is responsible for destroying/freeing any Vulkan objects that were created using that device as the first parameter of the corresponding  vkCreate* or  vkAllocate* command.NoteGThe lifetime of each of these objects is bound by the lifetime of the VkDevice object. Therefore, to avoid resource leaks, it is critical that an application explicitly free all of these resources prior to calling vkDestroyDevice. Valid UsageAll child objects created on device must. have been destroyed prior to destroying deviceIf VkAllocationCallbacks were provided when device1 was created, a compatible set of callbacks must be provided hereIf no VkAllocationCallbacks were provided when device was created,  pAllocator must be NULLValid Usage (Implicit)If device is not NULL, device must be a valid VkDevice handleIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structureHost SynchronizationHost access to device must be externally synchronizedSee Also, x-vkCreateDevice - Create a new device instance ParametersphysicalDevice must; be one of the device handles returned from a call to vkEnumeratePhysicalDevices (see  whttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#devsandqueues-physical-device-enumeration Physical Device Enumeration). pCreateInfo is a pointer to a _F structure containing information about how to create the device. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter.pDevice) points to a handle in which the created VkDevice is returned. DescriptionvkCreateDevice9 verifies that extensions and features requested in the ppEnabledExtensionNames and pEnabledFeatures members of  pCreateInfoc, respectively, are supported by the implementation. If any requested extension is not supported, vkCreateDevice must return VK_ERROR_EXTENSION_NOT_PRESENT.. If any requested feature is not supported, vkCreateDevice must return VK_ERROR_FEATURE_NOT_PRESENT. Support for extensions can3 be checked before creating a device by querying {. Support for features can# similarly be checked by querying /.0After verifying and enabling the extensions the VkDevice object is created and returned to the application. If a requested extension is only supported by a layer, both the layer and the extension need to be specified at vkCreateInstance" time for the creation to succeed.Multiple logical devices canD be created from the same physical device. Logical device creation mayd fail due to lack of device-specific resources (in addition to the other errors). If that occurs, vkCreateDevice will return VK_ERROR_TOO_MANY_OBJECTS. Valid UsageAll  |https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#extended-functionality-extensions-dependenciesrequired extensions% for each extension in the _::ppEnabledExtensionNames list must# also be present in that list.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handle pCreateInfo must$ be a valid pointer to a valid VkDeviceCreateInfo structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structurepDevice must be a valid pointer to a VkDevice handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_INITIALIZATION_FAILED VK_ERROR_EXTENSION_NOT_PRESENT VK_ERROR_FEATURE_NOT_PRESENT VK_ERROR_TOO_MANY_OBJECTS VK_ERROR_DEVICE_LOSTSee Also, , _, ^_`abcfghidejklmnoqprstuvwxuvstxwklmnoqpr_`abcfghidej^None "-KSTbejk9?VkCommandPoolResetFlags - Bitmask of VkCommandPoolResetFlagBits DescriptionVkCommandPoolResetFlags7 is a bitmask type for setting a mask of zero or more .See Also, AVkCommandPoolCreateFlags - Bitmask of VkCommandPoolCreateFlagBits DescriptionVkCommandPoolCreateFlags7 is a bitmask type for setting a mask of zero or more .See Also, ZVkCommandPoolCreateInfo - Structure specifying parameters of a newly created command pool Valid UsagequeueFamilyIndex mustH be the index of a queue family available in the calling command s device parameterValid Usage (Implicit)sType must be *VK_STRUCTURE_TYPE_COMMAND_POOL_CREATE_INFOpNext must be NULLflags must be a valid combination of  valuesSee Also, , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.flags is a bitmask of O indicating usage behavior for the pool and command buffers allocated from it.queueFamilyIndex4 designates a queue family as described in section  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#devsandqueues-queuepropsQueue Family Properties8. All command buffers allocated from this command pool must4 be submitted on queues from the same queue family.6VkCommandPool - Opaque handle to a command pool objectSee Also, , , E, , , 6Dummy data to tag the  withRVkCommandPoolResetFlagBits - Bitmask controlling behavior of a command pool resetSee AlsoSVkCommandPoolCreateFlagBits - Bitmask specifying usage behavior for a command poolSee Also)vkResetCommandPool - Reset a command pool Parametersdevice2 is the logical device that owns the command pool. commandPool is the command pool to reset.flags is a bitmask of & controlling the reset operation. DescriptionResetting a command pool recycles all of the resources from all of the command buffers allocated from the command pool back to the command pool. All command buffers that have been allocated from the command pool are put in the  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecycleinitial state.2Any primary command buffer allocated from another  that is in the  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording or executable state4 and has a secondary command buffer allocated from  commandPool recorded into it, becomes  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecycleinvalid. Valid UsageAll VkCommandBuffer objects allocated from  commandPool must not be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclepending stateValid Usage (Implicit)device must be a valid VkDevice handle commandPool must be a valid  VkCommandPool handleflags must be a valid combination of  values commandPool must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to  commandPool must be externally synchronized Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, , 4vkDestroyCommandPool - Destroy a command pool object Parametersdevice6 is the logical device that destroys the command pool. commandPool. is the handle of the command pool to destroy. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. DescriptionLWhen a pool is destroyed, all command buffers allocated from the pool are  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkFreeCommandBuffersfreed.2Any primary command buffer allocated from another  that is in the  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording or executable state4 and has a secondary command buffer allocated from  commandPool recorded into it, becomes  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecycleinvalid. Valid UsageAll VkCommandBuffer objects allocated from  commandPool must not be in the  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclepending state.If VkAllocationCallbacks were provided when  commandPool1 was created, a compatible set of callbacks must be provided hereIf no VkAllocationCallbacks were provided when  commandPool was created,  pAllocator must be NULLValid Usage (Implicit)device must be a valid VkDevice handleIf  commandPool is not ,  commandPool must be a valid  VkCommandPool handleIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structureIf  commandPool is a valid handle, it must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to  commandPool must be externally synchronizedSee Also, , 6vkCreateCommandPool - Create a new command pool object Parametersdevice5 is the logical device that creates the command pool. pCreateInfo6 contains information used to create the command pool. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. pCommandPool points to a  VkCommandPool3 handle in which the created pool is returned.Valid Usage (Implicit)device must be a valid VkDevice handle pCreateInfo must$ be a valid pointer to a valid VkCommandPoolCreateInfo structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structure pCommandPool must be a valid pointer to a  VkCommandPool handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, , , +VK_COMMAND_POOL_RESET_RELEASE_RESOURCES_BITr specifies that resetting a command pool recycles all of the resources from the command pool back to the system./VK_COMMAND_POOL_CREATE_RESET_COMMAND_BUFFER_BITR allows any command buffer allocated from a pool to be individually reset to the  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecycleinitial state; either by calling +, or via the implicit reset when calling +. If this flag is not set on a pool, then vkResetCommandBuffer must@ not be called for any command buffer allocated from that pool.$VK_COMMAND_POOL_CREATE_TRANSIENT_BIT specifies that command buffers allocated from the pool will be short-lived, meaning that they will be reset or freed in a relatively short timeframe. This flag mayW be used by the implementation to control memory allocation behavior within the pool.None-KSTejk9|0VkCommandPoolTrimFlags - Reserved for future use DescriptionVkCommandPoolTrimFlagsQ is a bitmask type for setting a mask, but is currently reserved for future use.See Also, 'vkTrimCommandPool - Trim a command pool Parametersdevice2 is the logical device that owns the command pool. commandPool is the command pool to trim.flags is reserved for future use. DescriptionTrimming a command pool recycles unused memory from the command pool back to the system. Command buffers allocated from the pool are not affected by the command.NoteqThis command provides applications with some control over the internal memory allocations used by command pools.(Unused memory normally arises from command buffers that have been recorded and later reset, such that they are no longer using the memory. On reset, a command buffer can return memory to its command pool, but the only way to release memory from a command pool to the system requires calling w, which cannot be executed while any command buffers from that pool are still in use. Subsequent recording operations into command buffers will re-use this memory but since total memory requirements fluctuate over time, unused memory can accumulate.+In this situation, trimming a command pool may be useful to return unused memory back to the system, returning the total outstanding memory allocated by the pool back to a more average  value.Implementations utilize many internal allocation strategies that make it impossible to guarantee that all unused memory is released back to the system. For instance, an implementation of a command pool may+ involve allocating memory in bulk from the system and sub-allocating from that memory. In such an implementation any live command buffer that holds a reference to a bulk allocation would prevent that allocation from being freed, even if only a small proportion of the bulk allocation is in use.In most cases trimming will result in a reduction in allocated but unused memory, but it does not guarantee the ideal  behaviour. Trimming may be an expensive operation, and should% not be called frequently. Trimming should be treated as a way to relieve memory pressure after application-known points when there exists enough unused memory that the cost of trimming is worth  it.Valid Usage (Implicit)device must be a valid VkDevice handle commandPool must be a valid  VkCommandPool handleflags must be 0 commandPool must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to  commandPool must be externally synchronizedSee Also, , None-STejk9*None "-KSTbejk:! XVkBufferViewCreateInfo - Structure specifying parameters of a newly created buffer view Valid Usageoffset must be less than the size of buffer offset must be a multiple of VkPhysicalDeviceLimits::minTexelBufferOffsetAlignmentIf range is not equal to  VK_WHOLE_SIZE, range must be greater than 0If range is not equal to  VK_WHOLE_SIZE, range must+ be a multiple of the element size of formatIf range is not equal to  VK_WHOLE_SIZE, range% divided by the element size of format must be less than or equal to VkPhysicalDeviceLimits::maxTexelBufferElementsIf range is not equal to  VK_WHOLE_SIZE , the sum of offset and range must& be less than or equal to the size of bufferbuffer must have been created with a usage' value containing at least one of (VK_BUFFER_USAGE_UNIFORM_TEXEL_BUFFER_BIT or (VK_BUFFER_USAGE_STORAGE_TEXEL_BUFFER_BITIf buffer was created with usage containing (VK_BUFFER_USAGE_UNIFORM_TEXEL_BUFFER_BIT, format mustG be supported for uniform texel buffers, as specified by the *VK_FORMAT_FEATURE_UNIFORM_TEXEL_BUFFER_BIT flag in VkFormatProperties::bufferFeatures returned by #vkGetPhysicalDeviceFormatPropertiesIf buffer was created with usage containing (VK_BUFFER_USAGE_STORAGE_TEXEL_BUFFER_BIT, format mustG be supported for storage texel buffers, as specified by the *VK_FORMAT_FEATURE_STORAGE_TEXEL_BUFFER_BIT flag in VkFormatProperties::bufferFeatures returned by #vkGetPhysicalDeviceFormatPropertiesIf buffer is non-sparse then it must7 be bound completely and contiguously to a single VkDeviceMemory objectValid Usage (Implicit)sType must be )VK_STRUCTURE_TYPE_BUFFER_VIEW_CREATE_INFOpNext must be NULLflags must be 0buffer must be a valid VkBuffer handleformat must be a valid  valueSee Also3, ,  VkDeviceSize, , , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.flags is reserved for future use.buffer is a VkBuffer# on which the view will be created.format is a ; describing the format of the data elements in the buffer.offset is an offset in bytes from the base address of the buffer. Accesses to the buffer view from shaders use addressing that is relative to this starting offset.range+ is a size in bytes of the buffer view. If range is equal to  VK_WHOLE_SIZE, the range from offset' to the end of the buffer is used. If  VK_WHOLE_SIZEX is used and the remaining size of the buffer is not a multiple of the element size of format-, then the nearest smaller multiple is used.4VkBufferView - Opaque handle to a buffer view objectSee Also, , 7Dummy data to tag the  with1VkBufferViewCreateFlags - Reserved for future use DescriptionVkBufferViewCreateFlagsQ is a bitmask type for setting a mask, but is currently reserved for future use.See Also2vkDestroyBufferView - Destroy a buffer view object Parametersdevice5 is the logical device that destroys the buffer view. bufferView is the buffer view to destroy. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. Valid Usage%All submitted commands that refer to  bufferView must have completed executionIf VkAllocationCallbacks were provided when  bufferView1 was created, a compatible set of callbacks must be provided hereIf no VkAllocationCallbacks were provided when  bufferView was created,  pAllocator must be NULLValid Usage (Implicit)device must be a valid VkDevice handleIf  bufferView is not ,  bufferView must be a valid  VkBufferView handleIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structureIf  bufferView is a valid handle, it must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to  bufferView must be externally synchronizedSee Also, , 4vkCreateBufferView - Create a new buffer view object Parametersdevice4 is the logical device that creates the buffer view. pCreateInfo) is a pointer to an instance of the VkBufferViewCreateInfoF structure containing parameters to be used to create the buffer. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter.pView points to a  VkBufferViewC handle in which the resulting buffer view object is returned.Valid Usage (Implicit)device must be a valid VkDevice handle pCreateInfo must$ be a valid pointer to a valid VkBufferViewCreateInfo structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structurepView must be a valid pointer to a  VkBufferView handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, , , None "-KSTbejk:7VkBufferCreateFlags - Bitmask of VkBufferCreateFlagBits DescriptionVkBufferCreateFlags7 is a bitmask type for setting a mask of zero or more .See Also, , W5VkBufferUsageFlags - Bitmask of VkBufferUsageFlagBits DescriptionVkBufferUsageFlags7 is a bitmask type for setting a mask of zero or more .See Also, , WZVkBufferCreateInfo - Structure specifying the parameters of a newly created buffer object Valid Usagesize must be greater than 0 If  sharingMode is VK_SHARING_MODE_CONCURRENT, pQueueFamilyIndices must( be a valid pointer to an array of queueFamilyIndexCount uint32_t valuesIf  sharingMode is VK_SHARING_MODE_CONCURRENT, queueFamilyIndexCount must be greater than 1If  sharingMode is VK_SHARING_MODE_CONCURRENT, each element of pQueueFamilyIndices must be unique and must be less than pQueueFamilyPropertyCount returned by either / or s for the physicalDevice that was used to create deviceIf the  mhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-sparseBindingsparse bindings feature is not enabled, flags must not contain #VK_BUFFER_CREATE_SPARSE_BINDING_BITIf the  uhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-sparseResidencyBuffersparse buffer residency feature is not enabled, flags must not contain %VK_BUFFER_CREATE_SPARSE_RESIDENCY_BITIf the  vhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-sparseResidencyAliasedsparse aliased residency feature is not enabled, flags must not contain #VK_BUFFER_CREATE_SPARSE_ALIASED_BITIf flags contains %VK_BUFFER_CREATE_SPARSE_RESIDENCY_BIT or #VK_BUFFER_CREATE_SPARSE_ALIASED_BIT, it must also contain #VK_BUFFER_CREATE_SPARSE_BINDING_BITIf the pNext$ chain contains an instance of  , its  handleTypes member must) only contain bits that are also in ::externalMemoryProperties.pname1:compatibleHandleTypes, as returned by  with pExternalBufferInfo-> handleType= equal to any one of the handle types specified in :: handleTypesIf the pNext$ chain contains an instance of k, and the dedicatedAllocation) member of the chained structure is VK_TRUE, then flags must not include #VK_BUFFER_CREATE_SPARSE_BINDING_BIT, %VK_BUFFER_CREATE_SPARSE_RESIDENCY_BIT , or #VK_BUFFER_CREATE_SPARSE_ALIASED_BITValid Usage (Implicit)sType must be $VK_STRUCTURE_TYPE_BUFFER_CREATE_INFOEach pNext: member of any structure (including this one) in the pNext chain must be either NULL/ or a pointer to a valid instance of k or Each sType member in the pNext chain must be uniqueflags must be a valid combination of  valuesusage must be a valid combination of  valuesusage must not be 0 sharingMode must be a valid  valueSee Also, ,  VkDeviceSize, , , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.flags is a bitmask of 1 specifying additional parameters of the buffer.size2 is the size in bytes of the buffer to be created.usage is a bitmask of * specifying allowed usages of the buffer. sharingMode is a f value specifying the sharing mode of the buffer when it will be accessed by multiple queue families.queueFamilyIndexCount" is the number of entries in the pQueueFamilyIndices array.pQueueFamilyIndicesG is a list of queue families that will access this buffer (ignored if  sharingMode is not VK_SHARING_MODE_CONCURRENT).NVkBufferCreateFlagBits - Bitmask specifying additional parameters of a buffer Description#VK_BUFFER_CREATE_SPARSE_BINDING_BITK specifies that the buffer will be backed using sparse memory binding.%VK_BUFFER_CREATE_SPARSE_RESIDENCY_BIT specifies that the buffer canV be partially backed using sparse memory binding. Buffers created with this flag must also be created with the #VK_BUFFER_CREATE_SPARSE_BINDING_BIT flag.#VK_BUFFER_CREATE_SPARSE_ALIASED_BIT specifies that the buffer will be backed using sparse memory binding with memory ranges that might also simultaneously be backing another buffer (or another portion of the same buffer). Buffers created with this flag must also be created with the #VK_BUFFER_CREATE_SPARSE_BINDING_BIT flag.See  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#sparsememory-sparseresourcefeaturesSparse Resource Features and  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-featuresPhysical Device FeaturesB for details of the sparse memory features supported on a device.See AlsoDVkBufferUsageFlagBits - Bitmask specifying allowed usage of a bufferSee Also.VkSharingMode - Buffer and image sharing modes DescriptionVK_SHARING_MODE_EXCLUSIVE specifies that access to any range or image subresource of the object will be exclusive to a single queue family at a time.VK_SHARING_MODE_CONCURRENT specifies that concurrent access to any range or image subresource of the object from multiple queue families is supported.NoteVK_SHARING_MODE_CONCURRENT mayA result in lower performance access to the buffer or image than VK_SHARING_MODE_EXCLUSIVE.IRanges of buffers and image subresources of image objects created using VK_SHARING_MODE_EXCLUSIVE must: only be accessed by queues in the queue family that has  ownership of the resource. Upon creation, such resources are not owned by any queue family; ownership is implicitly acquired upon first use within a queue. Once a resource using VK_SHARING_MODE_EXCLUSIVE1 is owned by some queue family, the application must perform a  mhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-queue-transfers queue family ownership transferf to make the memory contents of a range or image subresource accessible to a different queue family.NoteImages still require a  ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#resources-image-layoutslayout transition from VK_IMAGE_LAYOUT_UNDEFINED or VK_IMAGE_LAYOUT_PREINITIALIZED' before being used on the first queue.A queue family canT take ownership of an image subresource or buffer range of a resource created with VK_SHARING_MODE_EXCLUSIVE, without an ownership transfer, in the same way as for a resource that was just created; however, taking ownership in this way has the effect that the contents of the image subresource or buffer range are undefined.IRanges of buffers and image subresources of image objects created using VK_SHARING_MODE_CONCURRENT mustK only be accessed by queues from the queue families specified through the queueFamilyIndexCount and pQueueFamilyIndices6 members of the corresponding create info structures.See Also, *, )vkDestroyBuffer - Destroy a buffer object Parametersdevice0 is the logical device that destroys the buffer.buffer is the buffer to destroy. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. Valid Usage%All submitted commands that refer to buffer , either directly or via a  VkBufferView, must have completed executionIf VkAllocationCallbacks were provided when buffer1 was created, a compatible set of callbacks must be provided hereIf no VkAllocationCallbacks were provided when buffer was created,  pAllocator must be NULLValid Usage (Implicit)device must be a valid VkDevice handleIf buffer is not , buffer must be a valid VkBuffer handleIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structureIf buffer is a valid handle, it must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to buffer must be externally synchronizedSee Also, 3, +vkCreateBuffer - Create a new buffer object Parametersdevice6 is the logical device that creates the buffer object. pCreateInfo) is a pointer to an instance of the VkBufferCreateInfoG structure containing parameters affecting creation of the buffer. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter.pBuffer points to a VkBuffer> handle in which the resulting buffer object is returned. Valid UsageIf the flags member of  pCreateInfo includes #VK_BUFFER_CREATE_SPARSE_BINDING_BIT, creating this VkBuffer mustw not cause the total required sparse memory for all currently valid sparse resources on the device to exceed VkPhysicalDeviceLimits::sparseAddressSpaceSizeValid Usage (Implicit)device must be a valid VkDevice handle pCreateInfo must$ be a valid pointer to a valid VkBufferCreateInfo structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structurepBuffer must be a valid pointer to a VkBuffer handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, 3, , #VK_BUFFER_USAGE_INDIRECT_BUFFER_BIT; specifies that the buffer is suitable for passing as the buffer parameter to vkCmdDrawIndirect, vkCmdDrawIndexedIndirect, or vkCmdDispatchIndirect*. It is also suitable for passing as the buffer member of VkIndirectCommandsTokenNVX, or sequencesCountBuffer or sequencesIndexBuffer member of VkCmdProcessCommandsInfoNVX!VK_BUFFER_USAGE_VERTEX_BUFFER_BITI specifies that the buffer is suitable for passing as an element of the pBuffers array to vkCmdBindVertexBuffers. VK_BUFFER_USAGE_INDEX_BUFFER_BIT; specifies that the buffer is suitable for passing as the buffer parameter to vkCmdBindIndexBuffer."VK_BUFFER_USAGE_STORAGE_BUFFER_BIT specifies that the buffer can be used in a VkDescriptorBufferInfo suitable for occupying a VkDescriptorSet slot either of type !VK_DESCRIPTOR_TYPE_STORAGE_BUFFER or )VK_DESCRIPTOR_TYPE_STORAGE_BUFFER_DYNAMIC."VK_BUFFER_USAGE_UNIFORM_BUFFER_BIT specifies that the buffer can be used in a VkDescriptorBufferInfo suitable for occupying a VkDescriptorSet slot either of type !VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER or )VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER_DYNAMIC.(VK_BUFFER_USAGE_STORAGE_TEXEL_BUFFER_BIT specifies that the buffer can be used to create a  VkBufferView suitable for occupying a VkDescriptorSet slot of type 'VK_DESCRIPTOR_TYPE_STORAGE_TEXEL_BUFFER.(VK_BUFFER_USAGE_UNIFORM_TEXEL_BUFFER_BIT specifies that the buffer can be used to create a  VkBufferView suitable for occupying a VkDescriptorSet slot of type 'VK_DESCRIPTOR_TYPE_UNIFORM_TEXEL_BUFFER. VK_BUFFER_USAGE_TRANSFER_DST_BIT specifies that the buffer can3 be used as the destination of a transfer command. VK_BUFFER_USAGE_TRANSFER_SRC_BIT specifies that the buffer can be used as the source of a transfer command (see the definition of  vhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-transfer @VK_PIPELINE_STAGE_TRANSFER_BIT@).""None "-KSTbejk;<#JVkExternalMemoryFeatureFlags - Bitmask of VkExternalMemoryFeatureFlagBits DescriptionVkExternalMemoryFeatureFlags7 is a bitmask type for setting a mask of zero or more >.See Also>, 8PVkExternalMemoryHandleTypeFlags - Bitmask of VkExternalMemoryHandleTypeFlagBits DescriptionVkExternalMemoryHandleTypeFlags7 is a bitmask type for setting a mask of zero or more @.See Also, , @, , 8WVkPhysicalDeviceIDProperties - Structure specifying IDs related to the physical device Description deviceUUID mustp be immutable for a given device across instances, processes, driver APIs, driver versions, and system reboots. Applications can compare the  driverUUID4 value across instance and process boundaries, and can make similar queries in external APIs to determine whether they are capable of sharing memory objects and resources using them with the device. deviceUUID and/or  driverUUID must be used to determine whether a particular external object can be shared between driver components, where such a restriction exists as defined in the compatibility table for the particular object type: xhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#external-memory-handle-types-compatibility/External memory handle types compatibility {https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#external-semaphore-handle-types-compatibility2External semaphore handle types compatibility whttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#external-fence-handle-types-compatibility.External fence handle types compatibilityIf deviceLUIDValid is VK_FALSE, the contents of  deviceLUID and deviceNodeMask are undefined. If deviceLUIDValid is VK_TRUEJ and Vulkan is running on the Windows operating system, the contents of  deviceLUID can be cast to an LUID object and must1 be equal to the locally unique identifier of a  IDXGIAdapter1 object that corresponds to physicalDevice. If deviceLUIDValid is VK_TRUE, deviceNodeMask mustn contain exactly one bit. If Vulkan is running on an operating system that supports the Direct3D 12 API and physicalDeviceB corresponds to an individual device in a linked device adapter, deviceNodeMask3 identifies the Direct3D 12 node corresponding to physicalDevice . Otherwise, deviceNodeMask must be 1.Note,Although they have identical descriptions, :: deviceUUID may differ from sf::pipelineCacheUUID. The former is intended to identify and correlate devices across API and driver boundaries, while the latter is used to identify a compatible device and driver combination to use when serializing and de-serializing pipeline state.NoteWhile :: deviceUUID is specified to remain consistent across driver versions and system reboots, it is not intended to be usable as a serializable persistent identifier for a device. It may change when a device is physically added to, removed from, or moved to a different connector in a system while that system is powered down. Further, there is no reasonable way to verify with conformance testing that a given device retains the same UUID in a given system across all driver versions supported in that system. While implementations should make every effort to report consistent device UUIDs across driver versions, applications should avoid relying on the persistence of this value for uses other than identifying compatible devices for external object sharing purposes.Valid Usage (Implicit)sType must be /VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_ID_PROPERTIESSee AlsoVkBool32, sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure. deviceUUID is an array of size  VK_UUID_SIZEY, containing 8-bit values that represent a universally unique identifier for the device. driverUUID is an array of size  VK_UUID_SIZEu, containing 8-bit values that represent a universally unique identifier for the driver build in use by the device. deviceLUID is an array of size  VK_LUID_SIZEU, containing 8-bit values that represent a locally unique identifier for the device. deviceNodeMask` is a bitfield identifying the node within a linked device adapter corresponding to the device.!deviceLUIDValid! is a boolean value that will be VK_TRUE if  deviceLUID contains a valid LUID and deviceNodeMask" contains a valid node mask, and VK_FALSE if they do not."YVkExternalBufferProperties - Structure specifying supported external handle capabilitiesValid Usage (Implicit)sType must be ,VK_STRUCTURE_TYPE_EXTERNAL_BUFFER_PROPERTIESpNext must be NULLSee Also8, , B, $sType is the type of this structure%pNext9 is NULL or a pointer to an extension-specific structure.&externalMemoryProperties is an instance of the 8 structure specifying various capabilities of the external handle type when used with the specified buffer creation parameters.'UVkPhysicalDeviceExternalBufferInfo - Structure specifying buffer creation parametersValid Usage (Implicit)sType must be 6VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_EXTERNAL_BUFFER_INFOpNext must be NULLflags must be a valid combination of  valuesusage must be a valid combination of  valuesusage must not be 0 handleType must be a valid @ valueSee Also, , @, , B, )sType is the type of this structure*pNext9 is NULL or a pointer to an extension-specific structure.+flags is a bitmask of D describing additional parameters of the buffer, corresponding to ::flags.,usage is a bitmask of A describing the intended usage of the buffer, corresponding to ::usage.- handleType is a @h value specifying the memory handle type that will be used with the memory associated with the buffer..\VkExternalImageFormatProperties - Structure specifying supported external handle propertiesValid Usage (Implicit)sType must be 2VK_STRUCTURE_TYPE_EXTERNAL_IMAGE_FORMAT_PROPERTIESSee Also8, 0sType is the type of this structure.1pNext is NULL1 or a pointer to an extension-specific structure.2externalMemoryProperties is an instance of the 8 structure specifying various capabilities of the external handle type when used with the specified image creation parameters.3bVkPhysicalDeviceExternalImageFormatInfo - Structure specifying external image creation parameters DescriptionIf  handleType is 0, s will behave as if 3 was not present, and . will be ignored.If  handleType is not compatible with the format, type, tiling, usage, and flags specified in s_ , then s returns VK_ERROR_FORMAT_NOT_SUPPORTED.Valid Usage (Implicit)sType must be <VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_EXTERNAL_IMAGE_FORMAT_INFOIf  handleType is not 0,  handleType must be a valid @ valueSee Also@, 5sType is the type of this structure.6pNext is NULL1 or a pointer to an extension-specific structure.7 handleType is a @g value specifying the memory handle type that will be used with the memory associated with the image.8[VkExternalMemoryProperties - Structure specifying external memory handle type capabilities DescriptioncompatibleHandleTypes must include at least  handleType!. Inclusion of a handle type in compatibleHandleTypes) does not imply the values returned in s, will be the same when 3:: handleType is set to that type. The application is responsible for querying the capabilities of all handle types intended for concurrent use in a single image and intersecting them to obtain the compatible set of capabilities.See Also", ., , :externalMemoryFeatures is a bitmask of > specifying the features of  handleType.;exportFromImportedHandleTypes is a bitmask of @, specifying which types of imported handle  handleType can be exported from.<compatibleHandleTypes is a bitmask of @ specifying handle types which can# be specified at the same time as  handleType9 when creating an image compatible with external memory.>`VkExternalMemoryFeatureFlagBits - Bitmask specifying features of an external memory handle type Description-VK_EXTERNAL_MEMORY_FEATURE_DEDICATED_ONLY_BITb specifies that images or buffers created with the specified parameters and handle type must( use the mechanisms defined in the /{html_spec_relative}#VK_NV_dedicated_allocationU extension to create (or import) a dedicated allocation for the image or buffer.)VK_EXTERNAL_MEMORY_FEATURE_EXPORTABLE_BIT* specifies that handles of this type can( be exported from Vulkan memory objects.)VK_INTERNAL_MEMORY_FEATURE_IMPORTABLE_BIT* specifies that handles of this type can& be imported as Vulkan memory objects.Because their semantics in external APIs roughly align with that of an image or buffer with a dedicated allocation in Vulkan, implementations are required to report -VK_EXTERNAL_MEMORY_FEATURE_DEDICATED_ONLY_BIT* for the following external handle types: 0VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D11_TEXTURE_BIT 4VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D11_TEXTURE_KMT_BIT 1VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D12_RESOURCE_BITBVK_EXTERNAL_MEMORY_HANDLE_TYPE_ANDROID_HARDWARE_BUFFER_BIT_ANDROID for images onlyImplementations must not report -VK_EXTERNAL_MEMORY_FEATURE_DEDICATED_ONLY_BIT) for buffers with external handle type BVK_EXTERNAL_MEMORY_HANDLE_TYPE_ANDROID_HARDWARE_BUFFER_BIT_ANDROID.See Also@QVkExternalMemoryHandleTypeFlagBits - Bit specifying external memory handle types Description,VK_EXTERNAL_MEMORY_HANDLE_TYPE_OPAQUE_FD_BIT specifies a POSIX file descriptor handle that has only limited valid usage outside of Vulkan and other compatible APIs. It must0 be compatible with the POSIX system calls dup, dup2, close(, and the non-standard system call dup3. Additionally, it must. be transportable over a socket using an  SCM_RIGHTSz control message. It owns a reference to the underlying memory resource represented by its Vulkan memory object. /VK_EXTERNAL_MEMORY_HANDLE_TYPE_OPAQUE_WIN32_BITt specifies an NT handle that has only limited valid usage outside of Vulkan and other compatible APIs. It must' be compatible with the functions DuplicateHandle,  CloseHandle, CompareObjectHandles, GetHandleInformation, and SetHandleInformationj. It owns a reference to the underlying memory resource represented by its Vulkan memory object.3VK_EXTERNAL_MEMORY_HANDLE_TYPE_OPAQUE_WIN32_KMT_BIT specifies a global share handle that has only limited valid usage outside of Vulkan and other compatible APIs. It is not compatible with any native APIs. It does not own a reference to the underlying memory resource represented its Vulkan memory object, and will therefore become invalid when all Vulkan memory objects associated with it are destroyed.0VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D11_TEXTURE_BIT) specifies an NT handle returned by IDXGIResource1::CreateSharedHandle~ referring to a Direct3D 10 or 11 texture resource. It owns a reference to the memory used by the Direct3D resource.4VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D11_TEXTURE_KMT_BIT2 specifies a global share handle returned by  IDXGIResource::GetSharedHandle referring to a Direct3D 10 or 11 texture resource. It does not own a reference to the underlying Direct3D resource, and will therefore become invalid when all Vulkan memory objects and Direct3D resources associated with it are destroyed.-VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D12_HEAP_BIT) specifies an NT handle returned by  ID3D12Device::CreateSharedHandlet referring to a Direct3D 12 heap resource. It owns a reference to the resources used by the Direct3D heap.1VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D12_RESOURCE_BIT) specifies an NT handle returned by  ID3D12Device::CreateSharedHandlez referring to a Direct3D 12 committed resource. It owns a reference to the memory used by the Direct3D resource.6VK_EXTERNAL_MEMORY_HANDLE_TYPE_HOST_ALLOCATION_BIT_EXT specifies a host pointer returned by a host memory allocation command. It does not own a reference to the underlying memory resource, and will therefore become invalid if the host memory is freed.AVK_EXTERNAL_MEMORY_HANDLE_TYPE_HOST_MAPPED_FOREIGN_MEMORY_BIT_EXT" specifies a host pointer to host mapped foreign memory. It does not own a reference to the underlying memory resource, and will therefore become invalid if the foreign memory is unmapped or otherwise becomes no longer available..VK_EXTERNAL_MEMORY_HANDLE_TYPE_DMA_BUF_BIT_EXT is a file descriptor for a Linux dma_buf. It owns a reference to the underlying memory resource represented by its Vulkan memory object.BVK_EXTERNAL_MEMORY_HANDLE_TYPE_ANDROID_HARDWARE_BUFFER_BIT_ANDROID specifies an AHardwareBuffer- object defined by the Android NDK. See  uhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-external-android-hardware-bufferAndroid Hardware Buffers+ for more details of this handle type.Some external memory handle types can only be shared within the same underlying physical device and/or the same driver version, as defined in the following table: F Handle type  VkPhysicalDeviceIDProperties:: driverUUID  VkPhysicalDeviceIDProperties:: deviceUUID  ,VK_EXTERNAL_MEMORY_HANDLE_TYPE_OPAQUE_FD_BIT . Must match . Must match  /VK_EXTERNAL_MEMORY_HANDLE_TYPE_OPAQUE_WIN32_BIT . Must match . Must match  3VK_EXTERNAL_MEMORY_HANDLE_TYPE_OPAQUE_WIN32_KMT_BIT . Must match . Must match  0VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D11_TEXTURE_BIT . Must match . Must match  4VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D11_TEXTURE_KMT_BIT . Must match . Must match  -VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D12_HEAP_BIT . Must match . Must match  1VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D12_RESOURCE_BIT . Must match . Must match  6VK_EXTERNAL_MEMORY_HANDLE_TYPE_HOST_ALLOCATION_BIT_EXT . No restriction . No restriction  AVK_EXTERNAL_MEMORY_HANDLE_TYPE_HOST_MAPPED_FOREIGN_MEMORY_BIT_EXT . No restriction . No restriction  .VK_EXTERNAL_MEMORY_HANDLE_TYPE_DMA_BUF_BIT_EXT . No restriction . No restriction  BVK_EXTERNAL_MEMORY_HANDLE_TYPE_ANDROID_HARDWARE_BUFFER_BIT_ANDROID . No restriction . No restriction *External memory handle types compatibilityNoteFThe above table does not restrict the drivers and devices with which 6VK_EXTERNAL_MEMORY_HANDLE_TYPE_HOST_ALLOCATION_BIT_EXT and AVK_EXTERNAL_MEMORY_HANDLE_TYPE_HOST_MAPPED_FOREIGN_MEMORY_BIT_EXT may be shared, as these handle types inherently mean memory that does not come from the same device, as they import memory from the host or a foreign device, respectively.NoteREven though the above table does not restrict the drivers and devices with which .VK_EXTERNAL_MEMORY_HANDLE_TYPE_DMA_BUF_BIT_EXT mayr be shared, query mechanisms exist in the Vulkan API that prevent the import of incompatible dma-bufs (such as `=) and that prevent incompatible usage of dma-bufs (such as  and ).See Also, 7, 8, 9, H, I, ', 3, `, a, dB_vkGetPhysicalDeviceExternalBufferProperties - Query external handle types supported by buffers ParametersphysicalDeviceI is the physical device from which to query the buffer capabilities.pExternalBufferInfo# points to an instance of the 'J structure, describing the parameters that would be consumed by .pExternalBufferProperties# points to an instance of the "3 structure in which capabilities are returned.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handlepExternalBufferInfo must$ be a valid pointer to a valid "VkPhysicalDeviceExternalBufferInfo structurepExternalBufferProperties must be a valid pointer to a VkExternalBufferProperties structureSee Also", , '< !"#$%&'()*+-,./0123456789:;<=>?@ABCDEFGHIJKLMNOPQR<@ARQPONML>?KJIHGFED=CB89:;<34567./012'()*+-,"#$%& !None "-STbejkThe properties of the handle returned depend on the value of  handleType. See @S for a description of the properties of the defined external memory handle types. Valid Usage handleType must have been included in :: handleTypes when memory was created.If  handleType" is defined as an NT handle,  mustG be called no more than once for each valid unique combination of memory and  handleType. handleType must: be defined as an NT handle or a global share handle.Valid Usage (Implicit)sType must be 2VK_STRUCTURE_TYPE_MEMORY_GET_WIN32_HANDLE_INFO_KHRpNext must be NULLmemory must be a valid VkDeviceMemory handle handleType must be a valid @ valueSee Also , @, , usType is the type of this structure.vpNext is NULL1 or a pointer to an extension-specific structure.wmemory= is the memory object from which the handle will be exported.x handleType! is the type of handle requested.yQVkMemoryWin32HandlePropertiesKHR - Properties of External Memory Windows HandlesSee Also, {sType is the type of this structure.|pNext is NULL1 or a pointer to an extension-specific structure.}memoryTypeBits_ is a bitmask containing one bit set for every memory type which the specified windows handle can be imported as.~xVkExportMemoryWin32HandleInfoKHR - Structure specifying additional attributes of Windows handles exported from a memory Description(If this structure is not present, or if  pAttributes is set to NULL(, default security descriptor values will be used, and child processes created by the application will not inherit the handle, as described in the MSDN documentation for Synchronization Object Security and Access Rights 1. Further, if the structure is not present, the access rights will beDXGI_SHARED_RESOURCE_READ | DXGI_SHARED_RESOURCE_WRITE#for handles of the following types:/VK_EXTERNAL_MEMORY_HANDLE_TYPE_OPAQUE_WIN32_BIT 0VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D11_TEXTURE_BITAnd  GENERIC_ALL#for handles of the following types:-VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D12_HEAP_BIT 1VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D12_RESOURCE_BIT 1 Fhttps://msdn.microsoft.com/en-us/library/windows/desktop/ms686670.aspx Valid UsageIf :: handleTypes does not include /VK_EXTERNAL_MEMORY_HANDLE_TYPE_OPAQUE_WIN32_BIT, 0VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D11_TEXTURE_BIT, -VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D12_HEAP_BIT , or 1VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D12_RESOURCE_BIT(, VkExportMemoryWin32HandleInfoKHR must not be in the pNext chain of fB.Valid Usage (Implicit)sType must be 5VK_STRUCTURE_TYPE_EXPORT_MEMORY_WIN32_HANDLE_INFO_KHRIf  pAttributes is not NULL,  pAttributes must$ be a valid pointer to a valid SECURITY_ATTRIBUTES valueSee AlsosType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure. pAttributes is a pointer to a Windows SECURITY_ATTRIBUTES9 structure specifying security attributes of the handle.dwAccess is a DWORD( specifying access rights of the handle.name is a NULL-terminated UTF-16 string to associate with the underlying resource referenced by NT handles exported from the created memory.[VkImportMemoryWin32HandleInfoKHR - import Win32 memory created on the same physical device DescriptionImporting memory objects from Windows handles does not transfer ownership of the handle to the Vulkan implementation. For handle types defined as NT handles, the application must release ownership using the  CloseHandle1 system call when the handle is no longer needed. Applications can import the same underlying memory into multiple instances of Vulkan, into the same instance from which it was exported, and multiple times into a given Vulkan instance. In all cases, each import operation must create a distinct VkDeviceMemory object. Valid UsageIf  handleType is not 0, it must3 be supported for import, as reported by  or .The memory from which handle+ was exported, or the memory named by name mustB have been created on the same underlying physical device as device.If  handleType is not 0, it must: be defined as an NT handle or a global share handle.If  handleType is not /VK_EXTERNAL_MEMORY_HANDLE_TYPE_OPAQUE_WIN32_BIT, 0VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D11_TEXTURE_BIT, -VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D12_HEAP_BIT , or 1VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D12_RESOURCE_BIT, name must be NULL.If  handleType is not 0 and handle is NULL, name must< name a valid memory resource of the type specified by  handleType.If  handleType is not 0 and name is NULL, handle must1 be a valid handle of the type specified by  handleType.if handle is not NULL, name must be NULL.If handle is not NULL, it must' obey any requirements listed for  handleType in  xhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#external-memory-handle-types-compatibility/external memory handle types compatibility.If name is not NULL, it must' obey any requirements listed for  handleType in  xhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#external-memory-handle-types-compatibility/external memory handle types compatibility.Valid Usage (Implicit)sType must be 5VK_STRUCTURE_TYPE_IMPORT_MEMORY_WIN32_HANDLE_INFO_KHRIf  handleType is not 0,  handleType must be a valid @ valueSee Also@, sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure. handleType specifies the type of handle or name.handle& is the external handle to import, or NULL.nameY is a NULL-terminated UTF-16 string naming the underlying memory resource to import, or NULL.VvkGetMemoryWin32HandlePropertiesKHR - Get Properties of External Memory Win32 Handles Parametersdevice. is the logical device that will be importing handle. handleType is the type of the handle handle.handle& is the handle which will be imported.pMemoryWin32HandleProperties will return properties of handle. Valid Usagehandle mustE be an external memory handle created outside of the Vulkan API. handleType must7 not be one of the handle types defined as opaque.Valid Usage (Implicit)device must be a valid VkDevice handle handleType must be a valid @ valuepMemoryWin32HandleProperties must be a valid pointer to a  VkMemoryWin32HandlePropertiesKHR structure Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] -  VK_ERROR_INVALID_EXTERNAL_HANDLESee Also, @, yDvkGetMemoryWin32HandleKHR - Get a Windows HANDLE for a memory object ParametersdeviceJ is the logical device that created the device memory being exported.pGetWin32HandleInfo) is a pointer to an instance of the s> structure containing parameters of the export operation.pHandleg will return the Windows handle representing the underlying resources of the device memory object. DescriptionAFor handle types defined as NT handles, the handles returned by vkGetMemoryWin32HandleKHRL are owned by the application. To avoid leaking resources, the application must& release ownership of them using the  CloseHandle, system call when they are no longer needed.Valid Usage (Implicit)device must be a valid VkDevice handlepGetWin32HandleInfo must$ be a valid pointer to a valid VkMemoryGetWin32HandleInfoKHR structurepHandle must be a valid pointer to a HANDLE value Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_TOO_MANY_OBJECTS VK_ERROR_OUT_OF_HOST_MEMORYSee Also, s"stuvxwyz{|}~"~yz{|}stuvxwNone "-STbejk=)bVkSemaphoreGetWin32HandleInfoKHR - Structure describing a Win32 handle semaphore export operation Description>The properties of the handle returned depend on the value of  handleType. See V for a description of the properties of the defined external semaphore handle types. Valid Usage handleType must have been included in 7:: handleTypes when the  semaphore s current payload was created.If  handleType" is defined as an NT handle,  mustG be called no more than once for each valid unique combination of  semaphore and  handleType. semaphore must[ not currently have its payload replaced by an imported payload as described below in  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-semaphores-importing!Importing Semaphore PayloadsF unless that imported payload s handle type was included in 5!::exportFromImportedHandleTypes for  handleType.If  handleType\ refers to a handle type with copy payload transference semantics, as defined below in  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-semaphores-importing!Importing Semaphore Payloads , there must be no queue waiting on  semaphore.If  handleTypeH refers to a handle type with copy payload transference semantics,  semaphore must) be signaled, or have an associated  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-semaphores-signalingsemaphore signal operation pending execution. handleType must: be defined as an NT handle or a global share handle.Valid Usage (Implicit)sType must be 5VK_STRUCTURE_TYPE_SEMAPHORE_GET_WIN32_HANDLE_INFO_KHRpNext must be NULL semaphore must be a valid  VkSemaphore handle handleType must be a valid  valueSee Also, , , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure. semaphore4 is the semaphore from which state will be exported. handleType! is the type of handle requested.`VkD3D12FenceSubmitInfoKHR - Structure specifying values for Direct3D 12 fence-backed semaphores DescriptionIf the semaphore in @::pWaitSemaphores or @::pSignalSemaphores corresponding to an entry in pWaitSemaphoreValues or pSignalSemaphoreValues) respectively does not currently have a  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-semaphores-payloadspayload7 referring to a Direct3D 12 fence, the implementation must ignore the value in the pWaitSemaphoreValues or pSignalSemaphoreValues entry. Valid UsagewaitSemaphoreValuesCount must be the same value as  VkSubmitInfo::waitSemaphoreCount, where  VkSubmitInfo is in the pNext chain of this VkD3D12FenceSubmitInfoKHR structure.signalSemaphoreValuesCount must be the same value as  VkSubmitInfo::signalSemaphoreCount, where  VkSubmitInfo is in the pNext chain of this VkD3D12FenceSubmitInfoKHR structure.Valid Usage (Implicit)sType must be -VK_STRUCTURE_TYPE_D3D12_FENCE_SUBMIT_INFO_KHRIf waitSemaphoreValuesCount is not 0, and pWaitSemaphoreValues is not NULL, pWaitSemaphoreValues must( be a valid pointer to an array of waitSemaphoreValuesCount uint64_t valuesIf signalSemaphoreValuesCount is not 0 , and pSignalSemaphoreValues is not NULL, pSignalSemaphoreValues must( be a valid pointer to an array of signalSemaphoreValuesCount uint64_t valuesSee AlsosType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.waitSemaphoreValuesCount6 is the number of semaphore wait values specified in pWaitSemaphoreValues.pWaitSemaphoreValues is an array of length waitSemaphoreValuesCount9 containing values for the corresponding semaphores in @::pWaitSemaphores to wait for.signalSemaphoreValuesCount8 is the number of semaphore signal values specified in pSignalSemaphoreValues.pSignalSemaphoreValues is an array of length signalSemaphoreValuesCount9 containing values for the corresponding semaphores in @::pSignalSemaphores to set when signaled.~VkExportSemaphoreWin32HandleInfoKHR - Structure specifying additional attributes of Windows handles exported from a semaphore Description(If this structure is not present, or if  pAttributes is set to NULL(, default security descriptor values will be used, and child processes created by the application will not inherit the handle, as described in the MSDN documentation for Synchronization Object Security and Access Rights 1. Further, if the structure is not present, the access rights will beDXGI_SHARED_RESOURCE_READ | DXGI_SHARED_RESOURCE_WRITE#for handles of the following types: 2VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_OPAQUE_WIN32_BITAnd  GENERIC_ALL#for handles of the following types: 1VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_D3D12_FENCE_BIT 1 Fhttps://msdn.microsoft.com/en-us/library/windows/desktop/ms686670.aspx Valid UsageIf 7:: handleTypes does not include 2VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_OPAQUE_WIN32_BIT or 1VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_D3D12_FENCE_BIT, #VkExportSemaphoreWin32HandleInfoKHR must not be in the pNext chain of E.Valid Usage (Implicit)sType must be 8VK_STRUCTURE_TYPE_EXPORT_SEMAPHORE_WIN32_HANDLE_INFO_KHRIf  pAttributes is not NULL,  pAttributes must$ be a valid pointer to a valid SECURITY_ATTRIBUTES valueSee AlsosType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure. pAttributes is a pointer to a Windows SECURITY_ATTRIBUTES9 structure specifying security attributes of the handle.dwAccess is a DWORD( specifying access rights of the handle.name is a NULL-terminated UTF-16 string to associate with the underlying synchronization primitive referenced by NT handles exported from the created semaphore.cVkImportSemaphoreWin32HandleInfoKHR - Structure specifying Windows handle to import to a semaphore DescriptionThe handle types supported by  handleType are:: Handle Type  Transference  Permanence Supported  2VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_OPAQUE_WIN32_BIT  Reference  Temporary,Permanent  6VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_OPAQUE_WIN32_KMT_BIT  Reference  Temporary,Permanent  1VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_D3D12_FENCE_BIT  Reference  Temporary,Permanent =Handle Types Supported by VkImportSemaphoreWin32HandleInfoKHR Valid Usage handleType must be a value included in the  yhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-semaphore-handletypes-win32GHandle Types Supported by VkImportSemaphoreWin32HandleInfoKHR table.If  handleType is not 2VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_OPAQUE_WIN32_BIT or 1VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_D3D12_FENCE_BIT, name must be NULL.If  handleType is not 0 and handle is NULL, name mustK name a valid synchronization primitive of the type specified by  handleType.If  handleType is not 0 and name is NULL, handle must1 be a valid handle of the type specified by  handleType.If handle is not NULL, name must be NULL.If handle is not NULL, it must' obey any requirements listed for  handleType in  {https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#external-semaphore-handle-types-compatibility2external semaphore handle types compatibility.If name is not NULL, it must' obey any requirements listed for  handleType in  {https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#external-semaphore-handle-types-compatibility2external semaphore handle types compatibility.Valid Usage (Implicit)sType must be 8VK_STRUCTURE_TYPE_IMPORT_SEMAPHORE_WIN32_HANDLE_INFO_KHRpNext must be NULL semaphore must be a valid  VkSemaphore handleflags must be a valid combination of 7 valuesIf  handleType is not 0,  handleType must be a valid  valueHost SynchronizationHost access to  semaphore must be externally synchronizedSee Also, , , , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure. semaphore: is the semaphore into which the payload will be imported.flags is a bitmask of 7O specifying additional parameters for the semaphore payload import operation. handleType specifies the type of handle.handle& is the external handle to import, or NULL.namec is a NULL-terminated UTF-16 string naming the underlying synchronization primitive to import, or NULL.KvkImportSemaphoreWin32HandleKHR - Import a semaphore from a Windows HANDLE Parametersdevice2 is the logical device that created the semaphore.pImportSemaphoreWin32HandleInfo points to a ? structure specifying the semaphore and import parameters. DescriptionImporting a semaphore payload from Windows handles does not transfer ownership of the handle to the Vulkan implementation. For handle types defined as NT handles, the application must release ownership using the  CloseHandle1 system call when the handle is no longer needed. Applications can import the same semaphore payload into multiple instances of Vulkan, into the same instance from which it was exported, and multiple times into a given Vulkan instance.Valid Usage (Implicit)device must be a valid VkDevice handlepImportSemaphoreWin32HandleInfo must$ be a valid pointer to a valid #VkImportSemaphoreWin32HandleInfoKHR structure Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY  VK_ERROR_INVALID_EXTERNAL_HANDLESee Also, CvkGetSemaphoreWin32HandleKHR - Get a Windows HANDLE for a semaphore ParametersdeviceF is the logical device that created the semaphore being exported.pGetWin32HandleInfo) is a pointer to an instance of the > structure containing parameters of the export operation.pHandleF will return the Windows handle representing the semaphore state. DescriptionAFor handle types defined as NT handles, the handles returned by vkGetSemaphoreWin32HandleKHRL are owned by the application. To avoid leaking resources, the application must& release ownership of them using the  CloseHandle, system call when they are no longer needed.,Exporting a Windows handle from a semaphore maya have side effects depending on the transference of the specified handle type, as described in  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-semaphores-importingImporting Semaphore Payloads.Valid Usage (Implicit)device must be a valid VkDevice handlepGetWin32HandleInfo must$ be a valid pointer to a valid  VkSemaphoreGetWin32HandleInfoKHR structurepHandle must be a valid pointer to a HANDLE value Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_TOO_MANY_OBJECTS VK_ERROR_OUT_OF_HOST_MEMORYSee Also, &&None "-STbejk=`ZVkFenceGetWin32HandleInfoKHR - Structure describing a Win32 handle fence export operation Description>The properties of the handle returned depend on the value of  handleType. See R for a description of the properties of the defined external fence handle types. Valid Usage handleType must have been included in ;:: handleTypes when the fence s current payload was created.If  handleType" is defined as an NT handle,  mustG be called no more than once for each valid unique combination of fence and  handleType.fence must[ not currently have its payload replaced by an imported payload as described below in  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-fences-importingImporting Fence PayloadsF unless that imported payload s handle type was included in 9::exportFromImportedHandleTypes for  handleType.If  handleTypeH refers to a handle type with copy payload transference semantics, fence must) be signaled, or have an associated  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-fences-signalingfence signal operation pending execution. handleType must: be defined as an NT handle or a global share handle.Valid Usage (Implicit)sType must be 1VK_STRUCTURE_TYPE_FENCE_GET_WIN32_HANDLE_INFO_KHRpNext must be NULLfence must be a valid VkFence handle handleType must be a valid  valueSee Also, , , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.fence0 is the fence from which state will be exported. handleType! is the type of handle requested.vVkExportFenceWin32HandleInfoKHR - Structure specifying additional attributes of Windows handles exported from a fence Description(If this structure is not present, or if  pAttributes is set to NULL(, default security descriptor values will be used, and child processes created by the application will not inherit the handle, as described in the MSDN documentation for Synchronization Object Security and Access Rights 1. Further, if the structure is not present, the access rights will beDXGI_SHARED_RESOURCE_READ | DXGI_SHARED_RESOURCE_WRITE#for handles of the following types: .VK_EXTERNAL_FENCE_HANDLE_TYPE_OPAQUE_WIN32_BIT 1 Fhttps://msdn.microsoft.com/en-us/library/windows/desktop/ms686670.aspx Valid UsageIf ;:: handleTypes does not include .VK_EXTERNAL_FENCE_HANDLE_TYPE_OPAQUE_WIN32_BIT', VkExportFenceWin32HandleInfoKHR must not be in the pNext chain of z".Valid Usage (Implicit)sType must be 4VK_STRUCTURE_TYPE_EXPORT_FENCE_WIN32_HANDLE_INFO_KHRIf  pAttributes is not NULL,  pAttributes must$ be a valid pointer to a valid SECURITY_ATTRIBUTES valueSee AlsosType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure. pAttributes is a pointer to a Windows SECURITY_ATTRIBUTES9 structure specifying security attributes of the handle.dwAccess is a DWORD( specifying access rights of the handle.name is a NULL-terminated UTF-16 string to associate with the underlying synchronization primitive referenced by NT handles exported from the created fence.(VkImportFenceWin32HandleInfoKHR - (None) DescriptionThe handle types supported by  handleType are:6 Handle Type  Transference  Permanence Supported  .VK_EXTERNAL_FENCE_HANDLE_TYPE_OPAQUE_WIN32_BIT  Reference  Temporary,Permanent  2VK_EXTERNAL_FENCE_HANDLE_TYPE_OPAQUE_WIN32_KMT_BIT  Reference  Temporary,Permanent 9Handle Types Supported by VkImportFenceWin32HandleInfoKHR Valid Usage handleType must be a value included in the  uhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-fence-handletypes-win32CHandle Types Supported by VkImportFenceWin32HandleInfoKHR table.If  handleType is not .VK_EXTERNAL_FENCE_HANDLE_TYPE_OPAQUE_WIN32_BIT, name must be NULL.If  handleType is not 0 and handle is NULL, name mustK name a valid synchronization primitive of the type specified by  handleType.If  handleType is not 0 and name is NULL, handle must1 be a valid handle of the type specified by  handleType.If handle is not NULL, name must be NULL.If handle is not NULL, it must' obey any requirements listed for  handleType in  whttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#external-fence-handle-types-compatibility.external fence handle types compatibility.If name is not NULL, it must' obey any requirements listed for  handleType in  whttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#external-fence-handle-types-compatibility.external fence handle types compatibility.Valid Usage (Implicit)sType must be 4VK_STRUCTURE_TYPE_IMPORT_FENCE_WIN32_HANDLE_INFO_KHRpNext must be NULLfence must be a valid VkFence handleflags must be a valid combination of ; valuesIf  handleType is not 0,  handleType must be a valid  valueHost SynchronizationHost access to fence must be externally synchronizedSee Also, , C, , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.fence4 is the fence into which the state will be imported.flags is a bitmask of ;J specifying additional parameters for the fence payload import operation. handleType specifies the type of handle.handle& is the external handle to import, or NULL.namee is the NULL-terminated UTF-16 string naming the underlying synchronization primitive to import, or NULL.BvkImportFenceWin32HandleKHR - Import a fence from a Windows HANDLE Parametersdevice. is the logical device that created the fence.pImportFenceWin32HandleInfo points to a ; structure specifying the fence and import parameters. DescriptionImporting a fence payload from Windows handles does not transfer ownership of the handle to the Vulkan implementation. For handle types defined as NT handles, the application must release ownership using the  CloseHandle1 system call when the handle is no longer needed. Applications can import the same fence payload into multiple instances of Vulkan, into the same instance from which it was exported, and multiple times into a given Vulkan instance.Valid Usage (Implicit)device must be a valid VkDevice handlepImportFenceWin32HandleInfo must$ be a valid pointer to a valid VkImportFenceWin32HandleInfoKHR structure Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY  VK_ERROR_INVALID_EXTERNAL_HANDLESee Also, ;vkGetFenceWin32HandleKHR - Get a Windows HANDLE for a fence ParametersdeviceB is the logical device that created the fence being exported.pGetWin32HandleInfo) is a pointer to an instance of the > structure containing parameters of the export operation.pHandleB will return the Windows handle representing the fence state. DescriptionAFor handle types defined as NT handles, the handles returned by vkGetFenceWin32HandleKHRL are owned by the application. To avoid leaking resources, the application must& release ownership of them using the  CloseHandle, system call when they are no longer needed.(Exporting a Windows handle from a fence maya have side effects depending on the transference of the specified handle type, as described in  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-fences-importingImporting Fence Payloads.Valid Usage (Implicit)device must be a valid VkDevice handlepGetWin32HandleInfo must$ be a valid pointer to a valid VkFenceGetWin32HandleInfoKHR structurepHandle must be a valid pointer to a HANDLE value Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_TOO_MANY_OBJECTS VK_ERROR_OUT_OF_HOST_MEMORYSee Also, None "-STbejk>RVkMemoryGetFdInfoKHR - Structure describing a POSIX FD semaphore export operation DescriptionGThe properties of the file descriptor exported depend on the value of  handleType. See @S for a description of the properties of the defined external memory handle types.NoteThe size of the exported file may' be larger than the size requested by fB::allocationSize. If  handleType is .VK_EXTERNAL_MEMORY_HANDLE_TYPE_DMA_BUF_BIT_EXT, then the application can$ query the file s actual size with  man:lseek(2lseek(2)). Valid Usage handleType must have been included in :: handleTypes when memory was created. handleType must. be defined as a POSIX file descriptor handle.Valid Usage (Implicit)sType must be (VK_STRUCTURE_TYPE_MEMORY_GET_FD_INFO_KHRpNext must be NULLmemory must be a valid VkDeviceMemory handle handleType must be a valid @ valueSee Also , @, ,  sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.memory= is the memory object from which the handle will be exported. handleType! is the type of handle requested.HVkMemoryFdPropertiesKHR - Properties of External Memory File DescriptorsSee Also,  sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.memoryTypeBits` is a bitmask containing one bit set for every memory type which the specified file descriptor can be imported as.cVkImportMemoryFdInfoKHR - import memory created on the same physical device from a file descriptor DescriptionImporting memory from a file descriptor transfers ownership of the file descriptor from the application to the Vulkan implementation. The application mustN not perform any operations on the file descriptor after a successful import. Applications can import the same underlying memory into multiple instances of Vulkan, into the same instance from which it was exported, and multiple times into a given Vulkan instance. In all cases, each import operation must create a distinct VkDeviceMemory object. Valid UsageIf  handleType is not 0, it must3 be supported for import, as reported by  or .The memory from which fd was exported mustB have been created on the same underlying physical device as device.If  handleType is not 0, it must3 be defined as a POSIX file descriptor handle.If  handleType is not 0, fd must1 be a valid handle of the type specified by  handleType.The memory represented by fd mustR have been created from a physical device and driver that is compatible with device and  handleType, as described in  xhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#external-memory-handle-types-compatibility?{html_spec_relative}#external-memory-handle-types-compatibility.fd must" obey any requirements listed for  handleType in  xhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#external-memory-handle-types-compatibility/external memory handle types compatibility.Valid Usage (Implicit)sType must be +VK_STRUCTURE_TYPE_IMPORT_MEMORY_FD_INFO_KHRIf  handleType is not 0,  handleType must be a valid @ valueSee Also@, sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure. handleType specifies the handle type of fd. fd" is the external handle to import. PvkGetMemoryFdPropertiesKHR - Get Properties of External Memory File Descriptors Parametersdevice. is the logical device that will be importing fd. handleType is the type of the handle fd.fd& is the handle which will be imported.pMemoryFdProperties& will return properties of the handle fd. Valid Usagefd mustE be an external memory handle created outside of the Vulkan API. handleType must not be 0VK_EXTERNAL_MEMORY_HANDLE_TYPE_OPAQUE_FD_BIT_KHR.Valid Usage (Implicit)device must be a valid VkDevice handle handleType must be a valid @ valuepMemoryFdProperties must be a valid pointer to a VkMemoryFdPropertiesKHR structure Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] -  VK_ERROR_INVALID_EXTERNAL_HANDLESee Also, @,  BvkGetMemoryFdKHR - Get a POSIX file descriptor for a memory object ParametersdeviceJ is the logical device that created the device memory being exported. pGetFdInfo) is a pointer to an instance of the > structure containing parameters of the export operation.pFdf will return a file descriptor representing the underlying resources of the device memory object. Description Each call to vkGetMemoryFdKHR must} create a new file descriptor and transfer ownership of it to the application. To avoid leaking resources, the application must5 release ownership of the file descriptor using the close system call when it is no longer needed, or by importing a Vulkan memory object from it. Where supported by the operating system, the implementation must= set the file descriptor to be closed automatically when an execve system call is made.Valid Usage (Implicit)device must be a valid VkDevice handle pGetFdInfo must$ be a valid pointer to a valid VkMemoryGetFdInfoKHR structurepFd must be a valid pointer to a int value Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_TOO_MANY_OBJECTS VK_ERROR_OUT_OF_HOST_MEMORYSee Also,           None-STejk>U$ !"#$%&'()*+,-./0123456789:;<=$<;=$#"! :9876543210/.-,+*)('&%None "-STbejk>bj>VkPhysicalDeviceExternalMemoryHostPropertiesEXT - Structure describing external memory host pointer limits that can be supported by an implementationMembersThe members of the /VkPhysicalDeviceExternalMemoryHostPropertiesEXTC structure describe the following implementation-dependent limits: DescriptionminImportedHostPointerAlignment is the minimum requiredT alignment, in bytes, for the base address and size of host pointers that can' be imported to a Vulkan memory object.Valid Usage (Implicit)sType must be EVK_STRUCTURE_TYPE_PHYSICAL_DEVICE_EXTERNAL_MEMORY_HOST_PROPERTIES_EXTIf the /VkPhysicalDeviceExternalMemoryHostPropertiesEXT structure is included in the pNext chain of t9, it is filled with the implementation-dependent limits.See Also VkDeviceSize, HDVkImportMemoryHostPointerInfoEXT - import memory from a host pointer DescriptionImporting memory from a host pointer shares ownership of the memory between the host and the Vulkan implementation. The application can continue to access the memory through the host pointer but it is the application s responsibility to synchronize device and non-device access to the underlying memory as defined in  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-device-hostaccess%Host Access to Device Memory Objects. Applications can import the same underlying memory into multiple instances of Vulkan and multiple times into a given Vulkan instance. However, implementations mayt fail to import the same underlying memory multiple times into a given physical device due to platform constraints.0Importing memory from a particular host pointer may not be possible due to additional platform-specific restrictions beyond the scope of this specification in which case the implementation must8 fail the memory import operation with the error code $VK_ERROR_INVALID_EXTERNAL_HANDLE_KHR.The application mustt ensure that the imported memory range remains valid and accessible for the lifetime of the imported memory object. Valid UsageIf  handleType is not 0, it must3 be supported for import, as reported in  If  handleType is not 0, it must be 6VK_EXTERNAL_MEMORY_HANDLE_TYPE_HOST_ALLOCATION_BIT_EXT or AVK_EXTERNAL_MEMORY_HANDLE_TYPE_HOST_MAPPED_FOREIGN_MEMORY_BIT_EXT pHostPointer must5 be a pointer aligned to an integer multiple of /VkPhysicalDeviceExternalMemoryHostPropertiesEXT::minImportedHostPointerAlignmentIf  handleType is 6VK_EXTERNAL_MEMORY_HANDLE_TYPE_HOST_ALLOCATION_BIT_EXT,  pHostPointer must be a pointer to allocationSize, number of bytes of host memory, where allocationSize is the member of the VkMemoryAllocateInfo' structure this structure is chained toIf  handleType is AVK_EXTERNAL_MEMORY_HANDLE_TYPE_HOST_MAPPED_FOREIGN_MEMORY_BIT_EXT,  pHostPointer must be a pointer to allocationSize; number of bytes of host mapped foreign memory, where allocationSize is the member of the VkMemoryAllocateInfo, structure this structure is chained toValid Usage (Implicit)sType must be 5VK_STRUCTURE_TYPE_IMPORT_MEMORY_HOST_POINTER_INFO_EXT handleType must be a valid @ valueSee Also@, JsType is the type of this structure.KpNext is NULL1 or a pointer to an extension-specific structure.L handleType specifies the handle type.M pHostPointer$ is the host pointer to import from.NUvkGetMemoryHostPointerPropertiesEXT - Get properties of external memory host pointer Parametersdevice3 is the logical device that will be importing  pHostPointer. handleType is the type of the handle  pHostPointer. pHostPointer$ is the host pointer to import from. Valid Usage handleType must be 6VK_EXTERNAL_MEMORY_HANDLE_TYPE_HOST_ALLOCATION_BIT_EXT or AVK_EXTERNAL_MEMORY_HANDLE_TYPE_HOST_MAPPED_FOREIGN_MEMORY_BIT_EXT pHostPointer must5 be a pointer aligned to an integer multiple of /VkPhysicalDeviceExternalMemoryHostPropertiesEXT::minImportedHostPointerAlignmentIf  handleType is 6VK_EXTERNAL_MEMORY_HANDLE_TYPE_HOST_ALLOCATION_BIT_EXT,  pHostPointer must be a pointer to host memoryIf  handleType is AVK_EXTERNAL_MEMORY_HANDLE_TYPE_HOST_MAPPED_FOREIGN_MEMORY_BIT_EXT,  pHostPointer must+ be a pointer to host mapped foreign memoryValid Usage (Implicit)device must be a valid VkDevice handle handleType must be a valid @ valuepMemoryHostPointerProperties must be a valid pointer to a  VkMemoryHostPointerPropertiesEXT structure Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] -  VK_ERROR_INVALID_EXTERNAL_HANDLESee Also, @, C>?@ABCDEFGHIJKLMNOPQRSTUUTSRQPONHIJKLMCDEFG>?@ABNoneejk>c_`aa`_None "-STbejk?#bZVkExternalFormatANDROID - Structure containing an Android hardware buffer external format DescriptionIf externalFormat# is zero, the effect is as if the VkExternalFormatANDROID` structure was not present. Otherwise, the image will have the specified external format, and VkImageCreateInfo::format must be VK_FORMAT_UNDEFINED. Valid UsageexternalFormat must be 0! or a value returned in the externalFormat member of g by an earlier call to Valid Usage (Implicit)sType must be )VK_STRUCTURE_TYPE_EXTERNAL_FORMAT_ANDROIDSee AlsodsType is the type of this structure.epNext is NULL1 or a pointer to an extension-specific structure.fexternalFormatA is an implementation-defined identifier for the external formatgVkAndroidHardwareBufferFormatPropertiesANDROID - Structure describing the image format properties of an Android hardware buffer DescriptionEIf the Android hardware buffer has one of the formats listed in the  }https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-external-android-hardware-buffer-formatsFormat Equivalence table, then format mustD have the equivalent Vulkan format listed in the table. Otherwise, format may be VK_FORMAT_UNDEFINEDS, indicating the Android hardware buffer can only be used with an external format.The formatFeatures member must include #VK_FORMAT_FEATURE_SAMPLED_IMAGE_BIT and at least one of -VK_FORMAT_FEATURE_MIDPOINT_CHROMA_SAMPLES_BIT or ,VK_FORMAT_FEATURE_COSITED_CHROMA_SAMPLES_BIT, and should include 1VK_FORMAT_FEATURE_SAMPLED_IMAGE_FILTER_LINEAR_BIT and BVK_FORMAT_FEATURE_SAMPLED_IMAGE_YCBCR_CONVERSION_LINEAR_FILTER_BIT.7Android hardware buffers with the same external format must have the same support for 1VK_FORMAT_FEATURE_SAMPLED_IMAGE_FILTER_LINEAR_BIT, -VK_FORMAT_FEATURE_MIDPOINT_CHROMA_SAMPLES_BIT, ,VK_FORMAT_FEATURE_COSITED_CHROMA_SAMPLES_BIT, BVK_FORMAT_FEATURE_SAMPLED_IMAGE_YCBCR_CONVERSION_LINEAR_FILTER_BIT, SVK_FORMAT_FEATURE_SAMPLED_IMAGE_YCBCR_CONVERSION_SEPARATE_RECONSTRUCTION_FILTER_BIT, and ]VK_FORMAT_FEATURE_SAMPLED_IMAGE_YCBCR_CONVERSION_CHROMA_RECONSTRUCTION_EXPLICIT_FORCEABLE_BIT. Other format features mayx differ between Android hardware buffers that have the same external format. This allows applications to use the same x} object (and samplers and pipelines created from them) for any Android hardware buffers that have the same external format.If format is not VK_FORMAT_UNDEFINED, then the value of  samplerYcbcrConversionComponents must be valid when used as the  components member of x with that format. If format is VK_FORMAT_UNDEFINED, all members of  samplerYcbcrConversionComponents must be VK_COMPONENT_SWIZZLE_IDENTITY.Implementations may not always be able to determine the color model, numerical range, or chroma offsets of the image contents, so the values in .VkAndroidHardwareBufferFormatPropertiesANDROID% are only suggestions. Applications should treat these values as sensible defaults to use in the absence of more reliable information obtained through some other means. If the underlying physical device is also usable via OpenGL ES with the GL_OES_EGL_image_external extension, the implementation shouldx suggest values that will produce similar sampled values as would be obtained by sampling the same external image via samplerExternalOES2 in OpenGL ES using equivalent sampler parameters.NoteSince GL_OES_EGL_image_external does not require the same sampling and conversion calculations as Vulkan does, achieving identical results between APIs may) not be possible on some implementations.Valid Usage (Implicit)sType must be CVK_STRUCTURE_TYPE_ANDROID_HARDWARE_BUFFER_FORMAT_PROPERTIES_ANDROIDSee Also_, , , , c, a, isType is the type of this structure.jpNext is NULL1 or a pointer to an extension-specific structure.kformatQ is the Vulkan format corresponding to the Android hardware buffer s format, or VK_FORMAT_UNDEFINED- if there isn t an equivalent Vulkan format.lexternalFormatG is an implementation-defined external format identifier for use with b. It must not be zero.mformatFeaturesk describes the capabilities of this external format when used with an image bound to memory imported from buffer.n samplerYcbcrConversionComponents is the component swizzle that should be used in x.osuggestedYcbcrModel+ is a suggested color model to use in the x.psuggestedYcbcrRange1 is a suggested numerical value range to use in x.qsuggestedXChromaOffset+ is a suggested X chroma offset to use in x.rsuggestedYChromaOffset+ is a suggested Y chroma offset to use in x.svVkMemoryGetAndroidHardwareBufferInfoANDROID - Structure describing an Android hardware buffer memory export operation Valid UsageBVK_EXTERNAL_MEMORY_HANDLE_TYPE_ANDROID_HARDWARE_BUFFER_BIT_ANDROID must have been included in !:: handleTypes when memory was created.If the pNext chain of the VkMemoryAllocateInfo used to allocate memory included a VkMemoryDedicatedAllocateInfo with non-NULL image member, then that image must already be bound to memory.See Also , , usType is the type of this structure.vpNext is NULL1 or a pointer to an extension-specific structure.wmemoryO is the memory object from which the Android hardware buffer will be exported.xbVkAndroidHardwareBufferPropertiesANDROID - Properties of External Memory Android Hardware BuffersSee Also VkDeviceSize, , zsType is the type of this structure.{pNext is NULL1 or a pointer to an extension-specific structure.|allocationSize# is the size of the external memory}memoryTypeBitsh is a bitmask containing one bit set for every memory type which the specified Android hardware buffer can be imported as.~\VkAndroidHardwareBufferUsageANDROID - Struct containing Android hardware buffer usage flags DescriptionThe androidHardwareBufferUsage field must< include Android hardware buffer usage flags listed in the  {https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-external-android-hardware-buffer-usage"AHardwareBuffer Usage Equivalence_ table when the corresponding Vulkan image usage or image creation flags are included in the usage or flags fields of s_. It must' include at least one GPU usage flag (AHARDWAREBUFFER_USAGE_GPU_L*), even if none of the corresponding Vulkan usages or flags are requested.Note%Requiring at least one GPU usage flag ensures that Android hardware buffer memory will be allocated in a memory pool accessible to the Vulkan implementation, and that specializing the memory layout based on usage flags doesn t prevent it from being compatible with Vulkan. Implementations may avoid unnecessary restrictions caused by this requirement by using vendor usage flags to indicate that only the Vulkan uses indicated in s, are required.Valid Usage (Implicit)sType must be 7VK_STRUCTURE_TYPE_ANDROID_HARDWARE_BUFFER_USAGE_ANDROIDSee AlsosType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.androidHardwareBufferUsage6 returns the the Android hardware buffer usage flags.YVkImportAndroidHardwareBufferInfoANDROID - Import memory from an Android hardware buffer DescriptionIf the vkAllocateMemory& command succeeds, the implementation must@ acquire a reference to the imported hardware buffer, which it must\ release when the device memory object is freed. If the command fails, the implementation must not retain a reference. Valid UsageIf buffer is not NULL, Android hardware buffers must3 be supported for import, as reported by  or .If buffer is not NULL, it mustw be a valid Android hardware buffer object with format and usage compatible with Vulkan as described by @.Valid Usage (Implicit)sType must be =VK_STRUCTURE_TYPE_IMPORT_ANDROID_HARDWARE_BUFFER_INFO_ANDROIDbuffer must be a valid pointer to a AHardwareBuffer valueSee AlsosType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.buffer* is the Android hardware buffer to import. Opaque data]vkGetMemoryAndroidHardwareBufferANDROID - Get an Android hardware buffer for a memory object ParametersdeviceJ is the logical device that created the device memory being exported.pInfo) is a pointer to an instance of the s> structure containing parameters of the export operation.pBuffero will return an Android hardware buffer representing the underlying resources of the device memory object. Description Each call to 'vkGetMemoryAndroidHardwareBufferANDROID mustl return an Android hardware buffer with a new reference acquired in addition to the reference held by the VkDeviceMemory/. To avoid leaking resources, the application must~ release the reference by calling AHardwareBuffer_release when it is no longer needed. When called with the same handle in +VkMemoryGetAndroidHardwareBufferInfoANDROID::memory, 'vkGetMemoryAndroidHardwareBufferANDROID must} return the same Android hardware buffer object. If the device memory was created by importing an Android hardware buffer, 'vkGetMemoryAndroidHardwareBufferANDROID must1 return that same Android hardware buffer object.Valid Usage (Implicit)device must be a valid VkDevice handlepInfo must$ be a valid pointer to a valid +VkMemoryGetAndroidHardwareBufferInfoANDROID structurepBuffer must1 be a valid pointer to a valid pointer to a AHardwareBuffer value Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_TOO_MANY_OBJECTS VK_ERROR_OUT_OF_HOST_MEMORYSee Also, sivkGetAndroidHardwareBufferPropertiesANDROID - Get Properties of External Memory Android Hardware Buffers Parametersdevice. is the logical device that will be importing buffer.buffer7 is the Android hardware buffer which will be imported. pProperties will return properties of buffer. Valid Usagebuffer mustI be a valid Android hardware buffer object with at least one of the AHARDWAREBUFFER_USAGE_GPU_* usage flags.Valid Usage (Implicit)device must be a valid VkDevice handlebuffer must be a valid pointer to a valid AHardwareBuffer value pProperties must be a valid pointer to a (VkAndroidHardwareBufferPropertiesANDROID structure Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - $VK_ERROR_INVALID_EXTERNAL_HANDLE_KHRSee Alsox, 2bcdefghijklmnopqrstuvwxyz{|}~2~xyz{|}stuvwghijklmnopqrbcdefNone"bejk?- XVkExportMemoryAllocateInfo - Specify exportable handle types for a device memory object Valid Usage The bits in  handleTypes must7 be supported and compatible, as reported by  or .Valid Usage (Implicit)sType must be -VK_STRUCTURE_TYPE_EXPORT_MEMORY_ALLOCATE_INFO handleTypes must be a valid combination of " valuesSee Also, sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure. handleTypes is a bitmask of "= specifying one or more memory handle types the application can8 export from the resulting allocation. The application can8 request multiple handle types for the same allocation.ZVkExternalMemoryBufferCreateInfo - Specify that a buffer may be backed by external memoryValid Usage (Implicit)sType must be 4VK_STRUCTURE_TYPE_EXTERNAL_MEMORY_BUFFER_CREATE_INFO handleTypes must be a valid combination of " valuesSee Also, sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure. handleTypes is a bitmask of "6 specifying one or more external memory handle types.YVkExternalMemoryImageCreateInfo - Specify that an image may be backed by external memoryValid Usage (Implicit)sType must be 3VK_STRUCTURE_TYPE_EXTERNAL_MEMORY_IMAGE_CREATE_INFO handleTypes must be a valid combination of " values handleTypes must not be 0See Also, sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure. handleTypes is a bitmask of "6 specifying one or more external memory handle types.None-STejk?.  None "-STbejk?zXVkDeviceQueueInfo2 - Structure specifying the parameters used for device queue creation DescriptionThe queue returned by vkGetDeviceQueue2 must have the same flagsG value from this structure as that used at device creation time in a VkDeviceQueueCreateInfo instance. If no matching flags. were specified at device creation time then pQueue will return VK_NULL_HANDLE. Valid UsagequeueFamilyIndex must8 be one of the queue family indices specified when device was created, via the VkDeviceQueueCreateInfo structure queueIndex mustY be less than the number of queues created for the specified queue family index and VkDeviceQueueCreateFlags member flags equal to this flags value when device was created, via the  queueCount member of the VkDeviceQueueCreateInfo structureValid Usage (Implicit)sType must be %VK_STRUCTURE_TYPE_DEVICE_QUEUE_INFO_2pNext must be NULLflags must be a valid combination of s valuesflags must not be 0See Also^, , sType is the type of this structure.pNext is NULL7 or a pointer to an extension-specific structure. The pNext chain of VkDeviceQueueInfo24 is used to provide additional image parameters to vkGetDeviceQueue2.flags is a ^= value indicating the flags used to create the device queue.queueFamilyIndex> is the index of the queue family to which the queue belongs. queueIndexA is the index within this queue family of the queue to retrieve.VkPhysicalDeviceProtectedMemoryProperties - Structure describing protected memory properties that can be supported by an implementation DescriptionIf the )VkPhysicalDeviceProtectedMemoryProperties structure is included in the pNext chain of sfO, it is filled with a value indicating the implementation-dependent behavior.Valid Usage (Implicit)sType must be =VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_PROTECTED_MEMORY_PROPERTIESSee AlsoVkBool32, sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.protectedNoFaultc specifies whether the undefined behavior will not include process termination or device loss. If protectedNoFault is VK_FALSE, undefined behavior may1 include process termination or device loss. If protectedNoFault is VK_TRUEJ, undefined behavior will not include process termination or device loss.VkPhysicalDeviceProtectedMemoryFeatures - Structure describing protected memory features that can be supported by an implementation DescriptionIf the 'VkPhysicalDeviceProtectedMemoryFeatures structure is included in the pNext chain of s\I, it is filled with a value indicating whether the feature is supported.Valid Usage (Implicit)sType must be ;VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_PROTECTED_MEMORY_FEATURESSee AlsoVkBool32, protectedMemory1 specifies whether protected memory is supported.QVkProtectedSubmitInfo - Structure indicating whether the submission is protected Valid Usage0If the protected memory feature is not enabled, protectedSubmit must not be VK_TRUE.If protectedSubmit is VK_TRUE , then each element of the pCommandBuffers array must be a protected command buffer.If protectedSubmit is VK_FALSE , then each element of the pCommandBuffers array must" be an unprotected command buffer.If the  VkSubmitInfo::pNext chain does not include a VkProtectedSubmitInfo@ structure, then each element of the command buffer of the pCommandBuffers array must' be an unprotected command buffer.Valid Usage (Implicit)sType must be 'VK_STRUCTURE_TYPE_PROTECTED_SUBMIT_INFOSee AlsoVkBool32, protectedSubmit/ specifies whether the batch is protected. If protectedSubmit is VK_TRUE, the batch is protected. If protectedSubmit is VK_FALSE$, the batch is unprotected. If the  VkSubmitInfo::pNextB chain does not contain this structure, the batch is unprotected.4vkGetDeviceQueue2 - Get a queue handle from a device Parametersdevice+ is the logical device that owns the queue. pQueueInfo points to an instance of the P structure, describing the parameters used to create the device queue.pQueue is a pointer to a VkQueueI object that will be filled with the handle for the requested queue.Valid Usage (Implicit)device must be a valid VkDevice handle pQueueInfo must$ be a valid pointer to a valid VkDeviceQueueInfo2 structurepQueue must be a valid pointer to a VkQueue handleSee Also, , $VK_DEVICE_QUEUE_CREATE_PROTECTED_BITu specifies that the device queue is a protected-capable queue. If the protected memory feature is not enabled, the $VK_DEVICE_QUEUE_CREATE_PROTECTED_BIT bit of flags must not be set.!!None "-KSTbejkA)=VkSubresourceLayout - Structure specifying subresource layout Description'For images created with linear tiling, rowPitch,  arrayPitch and  depthPitch[ describe the layout of the image subresource in linear memory. For uncompressed formats, rowPitcht is the number of bytes between texels with the same x coordinate in adjacent rows (y coordinates differ by one).  arrayPitch is the number of bytes between texels with the same x and y coordinate in adjacent array layers of the image (array layer values differ by one).  depthPitch is the number of bytes between texels with the same x and y coordinate in adjacent slices of a 3D image (z coordinates differ by one). Expressed as an addressing formula, the starting byte of a texel in the image subresource has address: // (x,y,z,layer) are in texel coordinates address(x,y,z,layer) = layer*arrayPitch + z*depthPitch + y*rowPitch + x*elementSize + offsetFor compressed formats, the rowPitchK is the number of bytes between compressed texel blocks in adjacent rows.  arrayPitchT is the number of bytes between compressed texel blocks in adjacent array layers.  depthPitchZ is the number of bytes between compressed texel blocks in adjacent slices of a 3D image. // (x,y,z,layer) are in compressed texel block coordinates address(x,y,z,layer) = layer*arrayPitch + z*depthPitch + y*rowPitch + x*compressedTexelBlockByteSize + offset; arrayPitch; is undefined for images that were not created as arrays.  depthPitch is defined only for 3D images.For  single-plane color formats, the  aspectMask member of VkImageSubresource must be VK_IMAGE_ASPECT_COLOR_BIT. For depth/stencil formats,  aspectMask must be either VK_IMAGE_ASPECT_DEPTH_BIT or VK_IMAGE_ASPECT_STENCIL_BIT. On implementations that store depth and stencil aspects separately, querying each of these image subresource layouts will return a different offset and size representing the region of memory used for that aspect. On implementations that store depth and stencil aspects interleaved, the same offset and size? are returned and represent the interleaved memory allocation.For  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversionmulti-planar formats, the  aspectMask member of VkImageSubresource must be VK_IMAGE_ASPECT_PLANE_0_BIT, VK_IMAGE_ASPECT_PLANE_1_BIT!, or (for 3-plane formats only) VK_IMAGE_ASPECT_PLANE_2_BITL. Querying each of these image subresource layouts will return a different offset and size7 representing the region of memory used for that plane.See Also VkDeviceSize, offsetT is the byte offset from the start of the image where the image subresource begins.size0 is the size in bytes of the image subresource. size6 includes any extra memory that is required based on rowPitch.rowPitchG describes the number of bytes between each row of texels in an image. arrayPitchE describes the number of bytes between each array layer of an image. depthPitch? describes the number of bytes between each slice of 3D image.XVkImageCreateInfo - Structure specifying the parameters of a newly created image object DescriptionImages created with tiling equal to VK_IMAGE_TILING_LINEAR^ have further restrictions on their limits and capabilities compared to images created with tiling equal to VK_IMAGE_TILING_OPTIMAL". Creation of images with tiling VK_IMAGE_TILING_LINEAR mayG not be supported unless other parameters meet all of the constraints: imageType is VK_IMAGE_TYPE_2Dformat is not a depth/stencil format mipLevels is 1 arrayLayers is 1samples is VK_SAMPLE_COUNT_1_BITusage only includes VK_IMAGE_USAGE_TRANSFER_SRC_BIT and/or VK_IMAGE_USAGE_TRANSFER_DST_BITImplementations mayG support additional limits and capabilities beyond those listed above.OTo query an implementation s specific capabilities for a given combination of format,  imageType, tiling, usage, :: handleTypes and flags, call sh. The return value specifies whether that combination of image settings is supported. On success, the VkImageFormatProperties. output parameter specifies the set of valid samples bits and the limits for extent,  mipLevels,  arrayLayers, and maxResourceSize . Even if s\. returns success and the parameters to vkCreateImage are all within the returned limits,  vkCreateImage must fail and return VK_ERROR_OUT_OF_DEVICE_MEMORY: if the resulting size of the image would be larger than maxResourceSize.To determine the set of valid usage bits for a given format, call /.NoteFor images created without "VK_IMAGE_CREATE_EXTENDED_USAGE_BIT a usageK bit is valid if it is supported for the format the image is created with.For images created with "VK_IMAGE_CREATE_EXTENDED_USAGE_BIT a usageE bit is valid if it is supported for at least one of the formats a  VkImageView created from the image can have (see  chttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#resources-image-views Image Views for more detail). Valid UsageIf the pNext+ chain doesn t contain an instance of  , or if format5 is not VK_FORMAT_UNDEFINED, the combination of format,  imageType, tiling, usage, and flags must& be supported, as indicated by a  VK_SUCCESS return value from (vkGetPhysicalDeviceImageFormatPropertiesJ invoked with the same values passed to the corresponding parameters.BIf  sharingMode is VK_SHARING_MODE_CONCURRENT, pQueueFamilyIndices must( be a valid pointer to an array of queueFamilyIndexCount uint32_t valuesIf  sharingMode is VK_SHARING_MODE_CONCURRENT, queueFamilyIndexCount must be greater than 1If  sharingMode is VK_SHARING_MODE_CONCURRENT, each element of pQueueFamilyIndices must be unique and must be less than pQueueFamilyPropertyCount returned by either / or s for the physicalDevice that was used to create deviceformat must not be VK_FORMAT_UNDEFINEDextent::width must be greater than 0.extent::height must be greater than 0.extent::depth must be greater than 0. mipLevels must be greater than 0 arrayLayers must be greater than 0If flags contains #VK_IMAGE_CREATE_CUBE_COMPATIBLE_BIT,  imageType must be VK_IMAGE_TYPE_2DIf flags contains 'VK_IMAGE_CREATE_2D_ARRAY_COMPATIBLE_BIT,  imageType must be VK_IMAGE_TYPE_3DIf  imageType is VK_IMAGE_TYPE_1D,  extent.width must be less than or equal to VkPhysicalDeviceLimits::maxImageDimension1D , or VkImageFormatProperties::maxExtent.width (as returned by (vkGetPhysicalDeviceImageFormatProperties with format,  imageType, tiling, usage, and flags= equal to those in this structure) - whichever is higherIf  imageType is VK_IMAGE_TYPE_2D and flags does not contain #VK_IMAGE_CREATE_CUBE_COMPATIBLE_BIT,  extent.width and  extent.height must be less than or equal to VkPhysicalDeviceLimits::maxImageDimension2D , or VkImageFormatProperties::maxExtent.width/height (as returned by (vkGetPhysicalDeviceImageFormatProperties with format,  imageType, tiling, usage, and flags= equal to those in this structure) - whichever is higherIf  imageType is VK_IMAGE_TYPE_2D and flags contains #VK_IMAGE_CREATE_CUBE_COMPATIBLE_BIT,  extent.width and  extent.height must be less than or equal to VkPhysicalDeviceLimits::maxImageDimensionCube , or VkImageFormatProperties::maxExtent.width/height (as returned by (vkGetPhysicalDeviceImageFormatProperties with format,  imageType, tiling, usage, and flags= equal to those in this structure) - whichever is higherIf  imageType is VK_IMAGE_TYPE_2D and flags contains #VK_IMAGE_CREATE_CUBE_COMPATIBLE_BIT,  extent.width and  extent.height must be equal and  arrayLayers must# be greater than or equal to 6If  imageType is VK_IMAGE_TYPE_3D,  extent.width,  extent.height and  extent.depth must be less than or equal to VkPhysicalDeviceLimits::maxImageDimension3D , or VkImageFormatProperties::maxExtent.width/height/depth (as returned by (vkGetPhysicalDeviceImageFormatProperties with format,  imageType, tiling, usage, and flags= equal to those in this structure) - whichever is higherIf  imageType is VK_IMAGE_TYPE_1D, both  extent.height and  extent.depth must be 1If  imageType is VK_IMAGE_TYPE_2D,  extent.depth must be 1 mipLevels must) be less than or equal to # log2(max( extent.width,  extent.height,  extent.depth))# + 1. mipLevels must be less than or equal to VkImageFormatProperties:: maxMipLevels (as returned by (vkGetPhysicalDeviceImageFormatProperties with format,  imageType, tiling, usage, and flags' equal to those in this structure) arrayLayers must be less than or equal to VkImageFormatProperties::maxArrayLayers (as returned by (vkGetPhysicalDeviceImageFormatProperties with format,  imageType, tiling, usage, and flags' equal to those in this structure)If  imageType is VK_IMAGE_TYPE_3D,  arrayLayers must be 1.If samples is not VK_SAMPLE_COUNT_1_BIT,  imageType must be VK_IMAGE_TYPE_2D, flags must not contain #VK_IMAGE_CREATE_CUBE_COMPATIBLE_BIT, tiling must be VK_IMAGE_TILING_OPTIMAL, and  mipLevels must be equal to 1If usage includes 'VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT, then bits other than #VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT, +VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT , and #VK_IMAGE_USAGE_INPUT_ATTACHMENT_BIT must not be setIf usage includes #VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT, +VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT, 'VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT , or #VK_IMAGE_USAGE_INPUT_ATTACHMENT_BIT,  extent.width must be less than or equal to VkPhysicalDeviceLimits::maxFramebufferWidthIf usage includes #VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT, +VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT, 'VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT , or #VK_IMAGE_USAGE_INPUT_ATTACHMENT_BIT,  extent.height must$ be less than or equal to VkPhysicalDeviceLimits::maxFramebufferHeightIf usage includes 'VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT, usage must# also contain at least one of #VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT, +VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT , or #VK_IMAGE_USAGE_INPUT_ATTACHMENT_BIT.samples must$ be a bit value that is set in VkImageFormatProperties:: sampleCounts returned by (vkGetPhysicalDeviceImageFormatProperties with format,  imageType, tiling, usage, and flags& equal to those in this structureIf the  }https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-shaderStorageImageMultisample multisampled storage images" feature is not enabled, and usage contains VK_IMAGE_USAGE_STORAGE_BIT, samples must be VK_SAMPLE_COUNT_1_BITIf the  mhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-sparseBindingsparse bindings feature is not enabled, flags must not contain "VK_IMAGE_CREATE_SPARSE_BINDING_BITIf the  vhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-sparseResidencyAliasedsparse aliased residency feature is not enabled, flags must not contain "VK_IMAGE_CREATE_SPARSE_ALIASED_BITIf  imageType is VK_IMAGE_TYPE_1D, flags must not contain $VK_IMAGE_CREATE_SPARSE_RESIDENCY_BITIf the  vhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-sparseResidencyImage2D#sparse residency for 2D images" feature is not enabled, and  imageType is VK_IMAGE_TYPE_2D, flags must not contain $VK_IMAGE_CREATE_SPARSE_RESIDENCY_BITIf the  vhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-sparseResidencyImage3D#sparse residency for 3D images" feature is not enabled, and  imageType is VK_IMAGE_TYPE_3D, flags must not contain $VK_IMAGE_CREATE_SPARSE_RESIDENCY_BITIf the  whttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-sparseResidency2Samples/sparse residency for images with 2 samples feature is not enabled,  imageType is VK_IMAGE_TYPE_2D , and samples is VK_SAMPLE_COUNT_2_BIT, flags must not contain $VK_IMAGE_CREATE_SPARSE_RESIDENCY_BITIf the  whttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-sparseResidency4Samples/sparse residency for images with 4 samples feature is not enabled,  imageType is VK_IMAGE_TYPE_2D , and samples is VK_SAMPLE_COUNT_4_BIT, flags must not contain $VK_IMAGE_CREATE_SPARSE_RESIDENCY_BITIf the  whttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-sparseResidency8Samples/sparse residency for images with 8 samples feature is not enabled,  imageType is VK_IMAGE_TYPE_2D , and samples is VK_SAMPLE_COUNT_8_BIT, flags must not contain $VK_IMAGE_CREATE_SPARSE_RESIDENCY_BITIf the  xhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-sparseResidency16Samples0sparse residency for images with 16 samples feature is not enabled,  imageType is VK_IMAGE_TYPE_2D , and samples is VK_SAMPLE_COUNT_16_BIT, flags must not contain $VK_IMAGE_CREATE_SPARSE_RESIDENCY_BITIf tiling is VK_IMAGE_TILING_LINEAR, format must[ be a format that has at least one supported feature bit present in the value of VkFormatProperties::linearTilingFeatures returned by #vkGetPhysicalDeviceFormatProperties with the same value of formatIf tiling is VK_IMAGE_TILING_LINEAR , and VkFormatProperties::linearTilingFeatures (as returned by #vkGetPhysicalDeviceFormatProperties with the same value of format) does not include #VK_FORMAT_FEATURE_SAMPLED_IMAGE_BIT, usage must not contain VK_IMAGE_USAGE_SAMPLED_BITIf tiling is VK_IMAGE_TILING_LINEAR , and VkFormatProperties::linearTilingFeatures (as returned by #vkGetPhysicalDeviceFormatProperties with the same value of format) does not include #VK_FORMAT_FEATURE_STORAGE_IMAGE_BIT, usage must not contain VK_IMAGE_USAGE_STORAGE_BITIf tiling is VK_IMAGE_TILING_LINEAR , and VkFormatProperties::linearTilingFeatures (as returned by #vkGetPhysicalDeviceFormatProperties with the same value of format) does not include &VK_FORMAT_FEATURE_COLOR_ATTACHMENT_BIT, usage must not contain #VK_IMAGE_USAGE_COLOR_ATTACHMENT_BITIf tiling is VK_IMAGE_TILING_LINEAR , and VkFormatProperties::linearTilingFeatures (as returned by #vkGetPhysicalDeviceFormatProperties with the same value of format) does not include .VK_FORMAT_FEATURE_DEPTH_STENCIL_ATTACHMENT_BIT, usage must not contain +VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BITIf tiling is VK_IMAGE_TILING_OPTIMAL, format must[ be a format that has at least one supported feature bit present in the value of VkFormatProperties::optimalTilingFeatures returned by #vkGetPhysicalDeviceFormatProperties with the same value of formatIf tiling is VK_IMAGE_TILING_OPTIMAL , and VkFormatProperties::optimalTilingFeatures (as returned by #vkGetPhysicalDeviceFormatProperties with the same value of format) does not include #VK_FORMAT_FEATURE_SAMPLED_IMAGE_BIT, usage must not contain VK_IMAGE_USAGE_SAMPLED_BITIf tiling is VK_IMAGE_TILING_OPTIMAL , and VkFormatProperties::optimalTilingFeatures (as returned by #vkGetPhysicalDeviceFormatProperties with the same value of format) does not include #VK_FORMAT_FEATURE_STORAGE_IMAGE_BIT, usage must not contain VK_IMAGE_USAGE_STORAGE_BITIf tiling is VK_IMAGE_TILING_OPTIMAL , and VkFormatProperties::optimalTilingFeatures (as returned by #vkGetPhysicalDeviceFormatProperties with the same value of format) does not include &VK_FORMAT_FEATURE_COLOR_ATTACHMENT_BIT, usage must not contain #VK_IMAGE_USAGE_COLOR_ATTACHMENT_BITIf tiling is VK_IMAGE_TILING_OPTIMAL , and VkFormatProperties::optimalTilingFeatures (as returned by #vkGetPhysicalDeviceFormatProperties with the same value of format) does not include .VK_FORMAT_FEATURE_DEPTH_STENCIL_ATTACHMENT_BIT, usage must not contain +VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BITIf flags contains $VK_IMAGE_CREATE_SPARSE_RESIDENCY_BIT or "VK_IMAGE_CREATE_SPARSE_ALIASED_BIT, it must also contain "VK_IMAGE_CREATE_SPARSE_BINDING_BITIf any of the bits "VK_IMAGE_CREATE_SPARSE_BINDING_BIT, $VK_IMAGE_CREATE_SPARSE_RESIDENCY_BIT , or "VK_IMAGE_CREATE_SPARSE_ALIASED_BIT are set, 'VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT must not also be setIf the pNext$ chain contains an instance of 1  , it must! not contain an instance of .If the pNext$ chain contains an instance of  , its  handleTypes member must) only contain bits that are also in ::externalMemoryProperties::compatibleHandleTypes, as returned by s with format,  imageType, tiling, usage, and flagsE equal to those in this structure, and with an instance of Y in the pNext chain, with a  handleType= equal to any one of the handle types specified in :: handleTypesIf the pNext$ chain contains an instance of 1  , its  handleTypes member must) only contain bits that are also in 0::externalMemoryProperties::compatibleHandleTypes, as returned by 0 with format,  imageType, tiling, usage, and flags1 equal to those in this structure, and with externalHandleType= equal to any one of the handle types specified in 1 :: handleTypes,If the logical device was created with =::physicalDeviceCount equal to 1, flags must not contain /VK_IMAGE_CREATE_SPLIT_INSTANCE_BIND_REGIONS_BITIf flags contains /VK_IMAGE_CREATE_SPLIT_INSTANCE_BIND_REGIONS_BIT, then  mipLevels must be one,  arrayLayers must be one,  imageType must be VK_IMAGE_TYPE_2D, and tiling must be VK_IMAGE_TILING_OPTIMALIf flags contains /VK_IMAGE_CREATE_BLOCK_TEXEL_VIEW_COMPATIBLE_BIT, then format must be a  ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#appendix-compressedtex-bc"block-compressed image format , an  ihttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#appendix-compressedtex-etc2 ETC compressed image format , or an  ihttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#appendix-compressedtex-astc!ASTC compressed image format.If flags contains /VK_IMAGE_CREATE_BLOCK_TEXEL_VIEW_COMPATIBLE_BIT, then flags must also contain "VK_IMAGE_CREATE_MUTABLE_FORMAT_BIT. initialLayout must be VK_IMAGE_LAYOUT_UNDEFINED or VK_IMAGE_LAYOUT_PREINITIALIZED.If the pNext chain includes a  or 1  structure whose  handleTypes member is not 0,  initialLayout must be VK_IMAGE_LAYOUT_UNDEFINED If the image format is one of those listed in  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversionH{html_spec_relative}#features-formats-requiring-sampler-ycbcr-conversion: mipLevels must be 1samples must be VK_SAMPLE_COUNT_1_BIT imageType must be VK_IMAGE_TYPE_2D arrayLayers must be 1If tiling is VK_IMAGE_TILING_OPTIMAL, format is a  multi-planar format, and VkFormatProperties::optimalTilingFeatures (as returned by #vkGetPhysicalDeviceFormatProperties with the same value of format) does not include VK_FORMAT_FEATURE_DISJOINT_BIT, flags must not contain VK_IMAGE_CREATE_DISJOINT_BITIf tiling is VK_IMAGE_TILING_LINEAR, format is a  multi-planar format, and VkFormatProperties::linearTilingFeatures (as returned by #vkGetPhysicalDeviceFormatProperties with the same value of format) does not include VK_FORMAT_FEATURE_DISJOINT_BIT, flags must not contain VK_IMAGE_CREATE_DISJOINT_BITIf format is not a  multi-planar format, and flags does not include VK_IMAGE_CREATE_ALIAS_BIT, flags must not contain VK_IMAGE_CREATE_DISJOINT_BITIf flags contains 9VK_IMAGE_CREATE_SAMPLE_LOCATIONS_COMPATIBLE_DEPTH_BIT_EXT format must# be a depth or depth/stencil formatIf the pNext chain includes a  structure whose  handleTypes member includes BVK_EXTERNAL_MEMORY_HANDLE_TYPE_ANDROID_HARDWARE_BUFFER_BIT_ANDROID: imageType must be VK_IMAGE_TYPE_2D mipLevels must either be 1 or equal to # log2(max( extent.width,  extent.height,  extent.depth ))# + 1.If format is not VK_FORMAT_UNDEFINED, then format,  imageType, tiling, usage, flags,  mipLevels , and samples must be supported with BVK_EXTERNAL_MEMORY_HANDLE_TYPE_ANDROID_HARDWARE_BUFFER_BIT_ANDROID3 external memory handle types according to sIf format is VK_FORMAT_UNDEFINED , then the pNext chain must include a  structure whose externalFormat member is not 0If the pNext chain includes a  structure whose externalFormat member is not 0:format must be VK_FORMAT_UNDEFINEDflags must/ not include VK_IMAGE_CREATE_MUTABLE_FORMAT_BITusage must# not include any usages except VK_IMAGE_USAGE_SAMPLED_BITtiling must be VK_IMAGE_TILING_OPTIMALValid Usage (Implicit)sType must be #VK_STRUCTURE_TYPE_IMAGE_CREATE_INFO Each pNext: member of any structure (including this one) in the pNext chain must be either NULL/ or a pointer to a valid instance of k, , , 1 ,  +, or 1Each sType member in the pNext chain must be uniqueflags must be a valid combination of / values imageType must be a valid  valueformat must be a valid  valuesamples must be a valid  valuetiling must be a valid  valueusage must be a valid combination of / valuesusage must not be 0 sharingMode must be a valid  value initialLayout must be a valid  valueSee Also, , , , , , , , , , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.flags is a bitmask of /0 describing additional parameters of the image.  imageType is a  value specifying the basic dimensionality of the image. Layers in array textures do not count as a dimension for the purposes of the image type. format is a [ describing the format and type of the data elements that will be contained in the image. extent is a N describing the number of data elements in each dimension of the base level.  mipLevelsX describes the number of levels of detail available for minified sampling of the image.  arrayLayers& is the number of layers in the image.samplesH is the number of sub-data element samples in the image as defined in . See  ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#primsrast-multisampling Multisampling.tiling is a I value specifying the tiling arrangement of the data elements in memory.usage is a bitmask of /- describing the intended usage of the image. sharingMode is a f value specifying the sharing mode of the image when it will be accessed by multiple queue families.queueFamilyIndexCount" is the number of entries in the pQueueFamilyIndices array.pQueueFamilyIndicesF is a list of queue families that will access this image (ignored if  sharingMode is not VK_SHARING_MODE_CONCURRENT). initialLayout is a  value specifying the initial - of all image subresources of the image. See  ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#resources-image-layoutsImage Layouts.6VkImageLayout - Layout of image and image subresources Description:The type(s) of device access supported by each layout are: VK_IMAGE_LAYOUT_UNDEFINED2 does not support device access. This layout must only be used as the  initialLayout member of VkImageCreateInfo or VkAttachmentDescription, or as the  oldLayout in an image transition. When transitioning out of this layout, the contents of the memory are not guaranteed to be preserved.VK_IMAGE_LAYOUT_PREINITIALIZED2 does not support device access. This layout must only be used as the  initialLayout member of VkImageCreateInfo or VkAttachmentDescription, or as the  oldLayout in an image transition. When transitioning out of this layout, the contents of the memory are preserved. This layout is intended to be used as the initial layout for an image whose contents are written by the host, and hence the data cane be written to memory immediately, without first executing a layout transition. Currently, VK_IMAGE_LAYOUT_PREINITIALIZED is only useful with VK_IMAGE_TILING_LINEAR@ images because there is not a standard layout defined for VK_IMAGE_TILING_OPTIMAL images.VK_IMAGE_LAYOUT_GENERAL% supports all types of device access.(VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL must9 only be used as a color or resolve attachment in a  VkFramebufferX. This layout is valid only for image subresources of images created with the #VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT usage bit enabled.0VK_IMAGE_LAYOUT_DEPTH_STENCIL_ATTACHMENT_OPTIMAL must6 only be used as a depth/stencil attachment in a  VkFramebufferX. This layout is valid only for image subresources of images created with the +VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT usage bit enabled./VK_IMAGE_LAYOUT_DEPTH_STENCIL_READ_ONLY_OPTIMAL must@ only be used as a read-only depth/stencil attachment in a  VkFramebuffer5 and/or as a read-only image in a shader (which can be read as a sampled image, combined image/sampler and/or input attachment). This layout is valid only for image subresources of images created with the +VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BITM usage bit enabled. Only image subresources of images created with VK_IMAGE_USAGE_SAMPLED_BIT can be used as a sampled image or combined image/sampler in a shader. Similarly, only image subresources of images created with #VK_IMAGE_USAGE_INPUT_ATTACHMENT_BIT can# be used as input attachments.:VK_IMAGE_LAYOUT_DEPTH_READ_ONLY_STENCIL_ATTACHMENT_OPTIMAL: must6 only be used as a depth/stencil attachment in a  VkFramebuffer`, where the depth aspect is read-only, and/or as a read-only image in a shader (which can be read as a sampled image, combined image/sampler and/or input attachment) where only the depth aspect is accessed. This layout is valid only for image subresources of images created with the +VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BITM usage bit enabled. Only image subresources of images created with VK_IMAGE_USAGE_SAMPLED_BIT can be used as a sampled image or combined image/sampler in a shader. Similarly, only image subresources of images created with #VK_IMAGE_USAGE_INPUT_ATTACHMENT_BIT can# be used as input attachments.:VK_IMAGE_LAYOUT_DEPTH_ATTACHMENT_STENCIL_READ_ONLY_OPTIMAL: must6 only be used as a depth/stencil attachment in a  VkFramebufferb, where the stencil aspect is read-only, and/or as a read-only image in a shader (which can be read as a sampled image, combined image/sampler and/or input attachment) where only the stencil aspect is accessed. This layout is valid only for image subresources of images created with the +VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BITM usage bit enabled. Only image subresources of images created with VK_IMAGE_USAGE_SAMPLED_BIT can be used as a sampled image or combined image/sampler in a shader. Similarly, only image subresources of images created with #VK_IMAGE_USAGE_INPUT_ATTACHMENT_BIT can# be used as input attachments.(VK_IMAGE_LAYOUT_SHADER_READ_ONLY_OPTIMAL must; only be used as a read-only image in a shader (which can be read as a sampled image, combined image/sampler and/or input attachment). This layout is valid only for image subresources of images created with the VK_IMAGE_USAGE_SAMPLED_BIT or #VK_IMAGE_USAGE_INPUT_ATTACHMENT_BIT usage bit enabled.$VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL mustW only be used as a source image of a transfer command (see the definition of  vhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-transfer @VK_PIPELINE_STAGE_TRANSFER_BIT@Y). This layout is valid only for image subresources of images created with the VK_IMAGE_USAGE_TRANSFER_SRC_BIT usage bit enabled.$VK_IMAGE_LAYOUT_TRANSFER_DST_OPTIMAL must only be used as a destination image of a transfer command. This layout is valid only for image subresources of images created with the VK_IMAGE_USAGE_TRANSFER_DST_BIT usage bit enabled.VK_IMAGE_LAYOUT_PRESENT_SRC_KHR mustW only be used for presenting a presentable image for display. A swapchain s image must9 be transitioned to this layout before calling  , and must: be transitioned away from this layout after calling 9."VK_IMAGE_LAYOUT_SHARED_PRESENT_KHR7 is valid only for shared presentable images, and must/ be used for any usage the image supports.The layout of each image subresource is not a state of the image subresource itself, but is rather a property of how the data in memory is organized, and thus for each mechanism of accessing an image in the API the application must specify a parameter or structure member that indicates which image layout the image subresource(s) are considered to be in when the image will be accessed. For transfer commands, this is a parameter to the command (see  Thttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#clears{html_spec_relative}#clears and  Thttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#copies{html_spec_relative}#copiesW). For use as a framebuffer attachment, this is a member in the substructures of the VkRenderPassCreateInfo (see  Xhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#renderpass Render Pass:). For use in a descriptor set, this is a member in the VkDescriptorImageInfo structure (see  dhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-updates+{html_spec_relative}#descriptorsets-updates). At the time that any command buffer command accessing an image executes on any queue, the layouts of the image subresources that are accessed mustH all match the layout specified via the API controlling those accesses.SWhen performing a layout transition on an image subresource, the old layout value mustn either equal the current layout of the image subresource (at the time the transition executes), or else be VK_IMAGE_LAYOUT_UNDEFINEDt (implying that the contents of the image subresource need not be preserved). The new layout used in a transition must not be VK_IMAGE_LAYOUT_UNDEFINED or VK_IMAGE_LAYOUT_PREINITIALIZED.RThe image layout of each image subresource of a depth/stencil image created with 9VK_IMAGE_CREATE_SAMPLE_LOCATIONS_COMPATIBLE_DEPTH_BIT_EXT is dependent on the last sample locations used to render to the image subresource as a depth/stencil attachment, thus applications must provide the same sample locations that were last used to render to the given image subresource whenever a layout transition of the image subresource happens, otherwise the contents of the depth aspect of the image subresource become undefined.In addition, depth reads from a depth/stencil attachment referring to an image subresource range of a depth/stencil image created with 9VK_IMAGE_CREATE_SAMPLE_LOCATIONS_COMPATIBLE_DEPTH_BIT_EXT using different sample locations than what have been last used to perform depth writes to the image subresources of the same image subresource range produce undefined results.Similarly, depth writes to a depth/stencil attachment referring to an image subresource range of a depth/stencil image created with 9VK_IMAGE_CREATE_SAMPLE_LOCATIONS_COMPATIBLE_DEPTH_BIT_EXT using different sample locations than what have been last used to perform depth writes to the image subresources of the same image subresource range make the contents of the depth aspect of those image subresources undefined.See Also, #, , , -, , , , , , , NvkGetImageSubresourceLayout - Retrieve information about an image subresource Parametersdevice+ is the logical device that owns the image.image, is the image whose layout is being queried. pSubresource is a pointer to a E structure selecting a specific image for the image subresource.pLayout points to a 0 structure in which the layout is returned. DescriptionIf the  of image is a  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversionmulti-planar format, vkGetImageSubresourceLayout" describes one plane of the image. is invariant for the lifetime of a single image. However, the subresource layout of images in Android hardware buffer external memory isn t known until the image has been bound to memory, so calling vkGetImageSubresourceLayoutO for such an image before it has been bound will result in undefined behavior. Valid Usageimage must have been created with tiling equal to VK_IMAGE_TILING_LINEARThe  aspectMask member of  pSubresource must only have a single bit setThe mipLevel member of  pSubresource must be less than the  mipLevels specified in  when image was createdThe  arrayLayer member of  pSubresource must be less than the  arrayLayers specified in  when image was createdIf the format of image is a  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversionmulti-planar format with two planes, the  aspectMask member of  pSubresource must be VK_IMAGE_ASPECT_PLANE_0_BIT or VK_IMAGE_ASPECT_PLANE_1_BITIf the format of image is a  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversionmulti-planar format with three planes, the  aspectMask member of  pSubresource must be VK_IMAGE_ASPECT_PLANE_0_BIT, VK_IMAGE_ASPECT_PLANE_1_BIT or VK_IMAGE_ASPECT_PLANE_2_BITIf image was created with the VK_EXTERNAL_MEMORY_HANDLE_TYPE_ANDROID_HARDWARE_BUFFER_BIT_ANDROID external memory handle type, then image must be bound to memory.Valid Usage (Implicit)device must be a valid VkDevice handleimage must be a valid VkImage handle pSubresource must$ be a valid pointer to a valid VkImageSubresource structurepLayout must be a valid pointer to a VkSubresourceLayout structureimage must6 have been created, allocated, or retrieved from deviceSee Also, 2, , (vkDestroyImage - Destroy an image object Parametersdevice/ is the logical device that destroys the image.image is the image to destroy. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. Valid Usage%All submitted commands that refer to image , either directly or via a  VkImageView, must have completed executionIf VkAllocationCallbacks were provided when image1 was created, a compatible set of callbacks must be provided hereIf no VkAllocationCallbacks were provided when image was created,  pAllocator must be NULLValid Usage (Implicit)device must be a valid VkDevice handleIf image is not , image must be a valid VkImage handleIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structureIf image is a valid handle, it must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to image must be externally synchronizedSee Also, , 2)vkCreateImage - Create a new image object Parametersdevice. is the logical device that creates the image. pCreateInfo$ is a pointer to an instance of the VkImageCreateInfoE structure containing parameters to be used to create the image. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter.pImage points to a VkImage= handle in which the resulting image object is returned. Valid UsageIf the flags member of  pCreateInfo includes "VK_IMAGE_CREATE_SPARSE_BINDING_BIT, creating this VkImage must| not cause the total required sparse memory for all currently valid sparse resources on the device to exceed VkPhysicalDeviceLimits::sparseAddressSpaceSizeValid Usage (Implicit)device must be a valid VkDevice handle pCreateInfo must$ be a valid pointer to a valid VkImageCreateInfo structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structurepImage must be a valid pointer to a VkImage handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, , 2, &      !"&"!      None "-KSTbejkDF.RVkDeviceGroupPresentModeFlagsKHR - Bitmask of VkDeviceGroupPresentModeFlagBitsKHR Description VkDeviceGroupPresentModeFlagsKHR7 is a bitmask type for setting a mask of zero or more u.See AlsoP, u, 0, {/CVkSwapchainCreateFlagsKHR - Bitmask of VkSwapchainCreateFlagBitsKHR DescriptionVkSwapchainCreateFlagsKHR7 is a bitmask type for setting a mask of zero or more w.See Alsow, `0jVkDeviceGroupSwapchainCreateInfoKHR - Structure specifying parameters of a newly created swapchain object Description"If this structure is not present, modes is considered to be *VK_DEVICE_GROUP_PRESENT_MODE_LOCAL_BIT_KHR.Valid Usage (Implicit)sType must be 8VK_STRUCTURE_TYPE_DEVICE_GROUP_SWAPCHAIN_CREATE_INFO_KHRmodes must be a valid combination of u valuesmodes must not be 0See Also., 2sType is the type of this structure.3pNext is NULL1 or a pointer to an extension-specific structure.4modes+ is a bitfield of modes that the swapchain can be used with.5eVkDeviceGroupPresentInfoKHR - Mode and mask controlling which physical devices' images are presented DescriptionIf mode is *VK_DEVICE_GROUP_PRESENT_MODE_LOCAL_BIT_KHR, then each element of  pDeviceMasksN selects which instance of the swapchain image is presented. Each element of  pDeviceMasks mustB have exactly one bit set, and the corresponding physical device must, have a presentation engine as reported by P.If mode is +VK_DEVICE_GROUP_PRESENT_MODE_REMOTE_BIT_KHR, then each element of  pDeviceMasksN selects which instance of the swapchain image is presented. Each element of  pDeviceMasks mustK have exactly one bit set, and some physical device in the logical device must include that bit in its P:: presentMask.If mode is (VK_DEVICE_GROUP_PRESENT_MODE_SUM_BIT_KHR, then each element of  pDeviceMasks selects which instances of the swapchain image are component-wise summed and the sum of those images is presented. If the sum in any component is outside the representable range, the value of that component is undefined. Each element of  pDeviceMasks mustI have a value for which all set bits are set in one of the elements of P:: presentMask.If mode is 7VK_DEVICE_GROUP_PRESENT_MODE_LOCAL_MULTI_DEVICE_BIT_KHR, then each element of  pDeviceMasksh selects which instance(s) of the swapchain images are presented. For each bit set in each element of  pDeviceMasks$, the corresponding physical device must- have a presentation engine as reported by P.If VkDeviceGroupPresentInfoKHR is not provided or swapchainCount. is zero then the masks are considered to be 1. If VkDeviceGroupPresentInfoKHR is not provided, mode is considered to be *VK_DEVICE_GROUP_PRESENT_MODE_LOCAL_BIT_KHR. Valid UsageswapchainCount must equal 0 or V::swapchainCountIf mode is *VK_DEVICE_GROUP_PRESENT_MODE_LOCAL_BIT_KHR, then each element of  pDeviceMasks mustF have exactly one bit set, and the corresponding element of P:: presentMask must be non-zeroIf mode is +VK_DEVICE_GROUP_PRESENT_MODE_REMOTE_BIT_KHR, then each element of  pDeviceMasks mustO have exactly one bit set, and some physical device in the logical device must include that bit in its P:: presentMask.If mode is (VK_DEVICE_GROUP_PRESENT_MODE_SUM_BIT_KHR, then each element of  pDeviceMasks mustQ have a value for which all set bits are set in one of the elements of P:: presentMaskIf mode is 7VK_DEVICE_GROUP_PRESENT_MODE_LOCAL_MULTI_DEVICE_BIT_KHR0, then for each bit set in each element of  pDeviceMasks$, the corresponding element of P:: presentMask must be non-zeroThe value of each element of  pDeviceMasks must, be equal to the device mask passed in <:: deviceMask, when the image index was last acquiredmode must( have exactly one bit set, and that bit must have been included in 0::modesValid Usage (Implicit)sType must be /VK_STRUCTURE_TYPE_DEVICE_GROUP_PRESENT_INFO_KHRIf swapchainCount is not 0,  pDeviceMasks must( be a valid pointer to an array of swapchainCount uint32_t valuesmode must be a valid u valueSee Alsou, 7sType is the type of this structure.8pNext is NULL1 or a pointer to an extension-specific structure.9swapchainCount& is zero or the number of elements in  pDeviceMasks.: pDeviceMasks7 is an array of device masks, one for each element of V::pSwapchains.;modeF is the device group present mode that will be used for this present.<KVkAcquireNextImageInfoKHR - Structure specifying parameters of the acquire DescriptionIf ~_ is used, the device mask is considered to include all physical devices in the logical device.Notez} signals at most one semaphore, even if the application requests waiting for multiple physical devices to be ready via the  deviceMask). However, only a single physical device cand wait on that semaphore, since the semaphore becomes unsignaled when the wait succeeds. For other physical devices to wait for the image to be ready, it is necessary for the application to submit semaphore signal operation(s) to that first physical device to signal additional semaphore(s) after the wait succeeds, which the other physical device(s) can wait upon. Valid Usage swapchain must not be in the retired stateIf  semaphore is not  it must be unsignaledIf  semaphore is not  it must@ not have any uncompleted signal or wait operations pendingIf fence is not  it must be unsignaled and mustg not be associated with any other queue command that has not yet completed execution on that queue semaphore and fence must not both be equal to  deviceMask must be a valid device mask deviceMask must not be zero semaphore and fence must not both be equal to .Valid Usage (Implicit)sType must be -VK_STRUCTURE_TYPE_ACQUIRE_NEXT_IMAGE_INFO_KHRpNext must be NULL swapchain must be a valid VkSwapchainKHR handleIf  semaphore is not ,  semaphore must be a valid  VkSemaphore handleIf fence is not , fence must be a valid VkFence handleEach of fence,  semaphore, and  swapchain that are valid handles must? have been created, allocated, or retrieved from the same  VkInstanceHost SynchronizationHost access to  swapchain must be externally synchronizedHost access to  semaphore must be externally synchronizedHost access to fence must be externally synchronizedSee Also, , , t, z>sType is the type of this structure.?pNext is NULL1 or a pointer to an extension-specific structure.@ swapchain< is a non-retired swapchain from which an image is acquired.AtimeoutR specifies how long the function waits, in nanoseconds, if no image is available.B semaphore is VK_NULL_HANDLE or a semaphore to signal.Cfence is VK_NULL_HANDLE or a fence to signal.D deviceMask{ is a mask of physical devices for which the swapchain image will be ready to use when the semaphore or fence is signaled.E[VkBindImageMemorySwapchainInfoKHR - Structure specifying swapchain image memory to bind to DescriptionIf  swapchain is not NULL, the  swapchain and  imageIndexJ are used to determine the memory that the image is bound to, instead of memory and  memoryOffset.Memory can% be bound to a swapchain and use the pDeviceIndices or pSplitInstanceBindRegions members of ^. Valid Usage imageIndex must& be less than the number of images in  swapchainValid Usage (Implicit)sType must be 6VK_STRUCTURE_TYPE_BIND_IMAGE_MEMORY_SWAPCHAIN_INFO_KHR swapchain must be a valid VkSwapchainKHR handleHost SynchronizationHost access to  swapchain must be externally synchronizedSee Also, tGsType is the type of this structure.HpNext is NULL1 or a pointer to an extension-specific structure.I swapchain is  or a swapchain handle.J imageIndex is an image index within  swapchain.KXVkImageSwapchainCreateInfoKHR - Specify that an image will be bound to swapchain memory Valid UsageIf  swapchain is not , the fields of * must match the  mhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#swapchain-wsi-image-create-info&implied image creation parameters of the swapchainValid Usage (Implicit)sType must be 1VK_STRUCTURE_TYPE_IMAGE_SWAPCHAIN_CREATE_INFO_KHRIf  swapchain is not ,  swapchain must be a valid VkSwapchainKHR handleSee Also, tMsType is the type of this structure.NpNext is NULL1 or a pointer to an extension-specific structure.O swapchain is = or a handle of a swapchain that the image will be bound to.PWVkDeviceGroupPresentCapabilitiesKHR - Present capabilities from other physical devices Descriptionmodes always has *VK_DEVICE_GROUP_PRESENT_MODE_LOCAL_BIT_KHR set.CThe present mode flags are also used when presenting an image, in 5::mode.?If a device group only includes a single physical device, then modes must equal *VK_DEVICE_GROUP_PRESENT_MODE_LOCAL_BIT_KHR.Valid Usage (Implicit)sType must be 7VK_STRUCTURE_TYPE_DEVICE_GROUP_PRESENT_CAPABILITIES_KHRpNext must be NULLSee Also., , |RsType is the type of this structure.SpNext is NULL1 or a pointer to an extension-specific structure.T presentMask is an array of masks, where the mask at element i is non-zero if physical device i has a presentation engine, and where bit j is set in element i if physical device i canX present swapchain images from physical device j. If element i is non-zero, then bit i must be set.Umodes is a bitmask of uA indicating which device group presentation modes are supported.VKVkPresentInfoKHR - Structure describing parameters of a queue presentation DescriptionBefore an application can& present an image, the image s layout must be transitioned to the VK_IMAGE_LAYOUT_PRESENT_SRC_KHR0 layout, or for a shared presentable image the "VK_IMAGE_LAYOUT_SHARED_PRESENT_KHR layout.Note When transitioning the image to "VK_IMAGE_LAYOUT_SHARED_PRESENT_KHR or VK_IMAGE_LAYOUT_PRESENT_SRC_KHR], there is no need to delay subsequent processing, or perform any visibility operations (as }C performs automatic visibility operations). To achieve this, the  dstAccessMask member of the - should be set to 0 , and the  dstStageMask parameter should be set to $VK_PIPELINE_STAGE_BOTTOM_OF_PIPE_BIT. Valid UsageEach element of  pImageIndices musty be the index of a presentable image acquired from the swapchain specified by the corresponding element of the  pSwapchains1 array, and the presented image subresource must be in the VK_IMAGE_LAYOUT_PRESENT_SRC_KHR or "VK_IMAGE_LAYOUT_SHARED_PRESENT_KHR8 layout at the time the operation is executed on a VkDeviceValid Usage (Implicit)sType must be "VK_STRUCTURE_TYPE_PRESENT_INFO_KHREach pNext: member of any structure (including this one) in the pNext chain must be either NULL* or a pointer to a valid instance of 5, , W, or Each sType member in the pNext chain must be uniqueIf waitSemaphoreCount is not 0, pWaitSemaphores must( be a valid pointer to an array of waitSemaphoreCount valid  VkSemaphore handles pSwapchains must( be a valid pointer to an array of swapchainCount valid VkSwapchainKHR handles pImageIndices must( be a valid pointer to an array of swapchainCount uint32_t valuesIf pResults is not NULL, pResults must( be a valid pointer to an array of swapchainCount  valuesswapchainCount must be greater than 0Both of the elements of  pSwapchains, and the elements of pWaitSemaphores that are valid handles must? have been created, allocated, or retrieved from the same  VkInstanceSee Also, , , t, }XsType is the type of this structure.YpNext is NULL1 or a pointer to an extension-specific structure.ZwaitSemaphoreCountY is the number of semaphores to wait for before issuing the present request. The number may be zero.[pWaitSemaphores , if not NULL, is an array of  VkSemaphore objects with waitSemaphoreCountW entries, and specifies the semaphores to wait for before issuing the present request.\swapchainCountA is the number of swapchains being presented to by this command.] pSwapchains is an array of VkSwapchainKHR objects with swapchainCount entries. A given swapchain must) not appear in this list more than once.^ pImageIndicesU is an array of indices into the array of each swapchain s presentable images, with swapchainCountg entries. Each entry in this array identifies the image to present on the corresponding entry in the  pSwapchains array._pResults is an array of  typed elements with swapchainCount? entries. Applications that do not need per-swapchain results can use NULL for pResults . If non-NULL, each entry in pResults will be set to the B for presenting the swapchain corresponding to the same index in  pSwapchains.`_VkSwapchainCreateInfoKHR - Structure specifying parameters of a newly created swapchain object DescriptionNote%On some platforms, it is normal that maxImageExtent may become (0, 0), for example when the window is minimized. In such a case, it is not possible to create a swapchain due to the Valid Usage requirements. imageArrayLayersr is the number of views in a multiview/stereo surface. For non-stereoscopic-3D applications, this value is 1. imageUsage is a bitmask of /G describing the intended usage of the (acquired) swapchain images.imageSharingModeA is the sharing mode used for the image(s) of the swapchain.queueFamilyIndexCountZ is the number of queue families having access to the image(s) of the swapchain when imageSharingMode is VK_SHARING_MODE_CONCURRENT.pQueueFamilyIndices_ is an array of queue family indices having access to the images(s) of the swapchain when imageSharingMode is VK_SHARING_MODE_CONCURRENT. preTransform is a  t value describing the transform, relative to the presentation engine s natural orientation, applied to the image content prior to presentation. If it does not match the currentTransform value returned by )vkGetPhysicalDeviceSurfaceCapabilitiesKHRk, the presentation engine will transform the image content as part of the presentation operation.compositeAlpha is a  v value indicating the alpha compositing mode to use when this surface is composited together with other surfaces on certain window systems. presentMode is the presentation mode the swapchain will use. A swapchain s present mode determines how incoming present requests will be processed and queued internally.clipped specifies whether the Vulkan implementation is allowed to discard rendering operations that affect regions of the surface that are not visible. If set to VK_TRUE;, the presentable images associated with the swapchain may not own all of their pixels. Pixels in the presentable images that correspond to regions of the target surface obscured by another window on the desktop, or subject to some other clipping mechanism will have undefined content when read back. Pixel shaders maye not execute for these pixels, and thus any side effects they would have had will not occur. VK_TRUE value does not guarantee any clipping will occur, but allows more optimal presentation methods to be used on some platforms. If set to VK_FALSE_, presentable images associated with the swapchain will own all of the pixels they contain.Note Applications should set this value to VK_TRUE if they do not expect to read back the content of presentable images before presenting them or after reacquiring them, and if their pixel shaders do not have any side effects that require them to run for all pixels in the presentable image. oldSwapchain is L, or the existing non-retired swapchain currently associated with surface. Providing a valid  oldSwapchain may aid in the resource reuse, and also allows the application to still present any images that are already acquired from it. Upon calling vkCreateSwapchainKHR with an  oldSwapchain that is not ,  oldSwapchain is retired  even if creation of the new swapchain fails. The new swapchain is created in the non-retired state whether or not  oldSwapchain is . Upon calling vkCreateSwapchainKHR with an  oldSwapchain that is not , any images from  oldSwapchain* that are not acquired by the application may( be freed by the implementation, which mayE occur even if creation of the new swapchain fails. The application can destroy  oldSwapchain% to free all memory associated with  oldSwapchain.NoteMultiple retired swapchains can be associated with the same  VkSurfaceKHR through multiple uses of  oldSwapchain that outnumber calls to .After  oldSwapchain is retired, the application can pass to }* any images it had already acquired from  oldSwapchain. E.g., an application may present an image from the old swapchain before an image from the new swapchain is ready to be presented. As usual, } may fail if  oldSwapchain" has entered a state that causes VK_ERROR_OUT_OF_DATE_KHR to be returned.The application can; continue to use a shared presentable image obtained from  oldSwapchain until a presentable image is acquired from the new swapchain, as long as it has not entered a state that causes it to return VK_ERROR_OUT_OF_DATE_KHR. Valid Usagesurface mustG be a surface that is supported by the device as determined using $vkGetPhysicalDeviceSurfaceSupportKHR minImageCount must< be greater than or equal to the value returned in the  minImageCount member of the VkSurfaceCapabilitiesKHR structure returned by )vkGetPhysicalDeviceSurfaceCapabilitiesKHR for the surface minImageCount must9 be less than or equal to the value returned in the  maxImageCount member of the VkSurfaceCapabilitiesKHR structure returned by )vkGetPhysicalDeviceSurfaceCapabilitiesKHR& for the surface if the returned  maxImageCount is not zero minImageCount must be 1 if  presentMode is either )VK_PRESENT_MODE_SHARED_DEMAND_REFRESH_KHR or -VK_PRESENT_MODE_SHARED_CONTINUOUS_REFRESH_KHR imageFormat and imageColorSpace must match the format and  colorSpace+ members, respectively, of one of the VkSurfaceFormatKHR structures returned by $vkGetPhysicalDeviceSurfaceFormatsKHR for the surface imageExtent must be between minImageExtent and maxImageExtent, inclusive, where minImageExtent and maxImageExtent are members of the VkSurfaceCapabilitiesKHR structure returned by )vkGetPhysicalDeviceSurfaceCapabilitiesKHR for the surface imageExtent members width and height must both be non-zeroimageArrayLayers must be greater than 0$ and less than or equal to the maxImageArrayLayers member of the VkSurfaceCapabilitiesKHR structure returned by )vkGetPhysicalDeviceSurfaceCapabilitiesKHR for the surfaceIf  presentMode is VK_PRESENT_MODE_IMMEDIATE_KHR, VK_PRESENT_MODE_MAILBOX_KHR, VK_PRESENT_MODE_FIFO_KHR or  VK_PRESENT_MODE_FIFO_RELAXED_KHR,  imageUsage must> be a subset of the supported usage flags present in the supportedUsageFlags member of the K! structure returned by K for surfaceIf  presentMode is )VK_PRESENT_MODE_SHARED_DEMAND_REFRESH_KHR or -VK_PRESENT_MODE_SHARED_CONTINUOUS_REFRESH_KHR,  imageUsage mustC be a subset of the supported usage flags present in the  sharedPresentSupportedUsageFlags member of the ! structure returned by T for surfaceIf imageSharingMode is VK_SHARING_MODE_CONCURRENT, pQueueFamilyIndices must( be a valid pointer to an array of queueFamilyIndexCount uint32_t valuesIf imageSharingMode is VK_SHARING_MODE_CONCURRENT, queueFamilyIndexCount must be greater than 1If imageSharingMode is VK_SHARING_MODE_CONCURRENT, each element of pQueueFamilyIndices must be unique and must be less than pQueueFamilyPropertyCount returned by either / or s for the physicalDevice that was used to create device preTransform must( be one of the bits present in the supportedTransforms member of the VkSurfaceCapabilitiesKHR structure returned by )vkGetPhysicalDeviceSurfaceCapabilitiesKHR for the surfacecompositeAlpha must( be one of the bits present in the supportedCompositeAlpha member of the VkSurfaceCapabilitiesKHR structure returned by )vkGetPhysicalDeviceSurfaceCapabilitiesKHR for the surface presentMode must be one of the  x values returned by )vkGetPhysicalDeviceSurfacePresentModesKHR for the surface,If the logical device was created with =::physicalDeviceCount equal to 1, flags must not contain 7VK_SWAPCHAIN_CREATE_SPLIT_INSTANCE_BIND_REGIONS_BIT_KHR oldSwapchain must not be in the retired state imageFormat,  imageUsage,  imageExtent, and imageArrayLayers must be supported for VK_IMAGE_TYPE_2D VK_IMAGE_TILING_OPTIMAL! images as reported by /.Valid Usage (Implicit)sType must be +VK_STRUCTURE_TYPE_SWAPCHAIN_CREATE_INFO_KHREach pNext: member of any structure (including this one) in the pNext chain must be either NULL* or a pointer to a valid instance of 0 or Each sType member in the pNext chain must be uniqueflags must be a valid combination of w valuessurface must be a valid  VkSurfaceKHR handle imageFormat must be a valid  valueimageColorSpace must be a valid  z value imageUsage must be a valid combination of / values imageUsage must not be 0imageSharingMode must be a valid  value preTransform must be a valid  t valuecompositeAlpha must be a valid  v value presentMode must be a valid  x valueIf  oldSwapchain is not ,  oldSwapchain must be a valid VkSwapchainKHR handleIf  oldSwapchain is a valid handle, it must6 have been created, allocated, or retrieved from surfaceBoth of  oldSwapchain, and surface that are valid handles mustD have been created, allocated, or retrieved from the same  VkInstanceSee AlsoVkBool32,  z,  v, , , ,  x, , ,  s,  t, /, t,  , bsType is the type of this structure.cpNext is NULL1 or a pointer to an extension-specific structure.dflags is a bitmask of w2 indicating parameters of the swapchain creation.esurface is the surface onto which the swapchain will present images. If the creation succeeds, the swapchain becomes associated with surface.f minImageCount is the minimum number of presentable images that the application needs. The implementation will either create the swapchain with at least that many images, or it will fail to create the swapchain.g imageFormat is a J value specifying the format the swapchain image(s) will be created with.himageColorSpace is a  z? value specifying the way the swapchain interprets image data.i imageExtent is the size (in pixels) of the swapchain image(s). The behavior is platform-dependent if the image extent does not match the surface s  currentExtent as returned by )vkGetPhysicalDeviceSurfaceCapabilitiesKHR.t4VkSwapchainKHR - Opaque handle to a swapchain object DescriptionA swapchain is an abstraction for an array of presentable images that are associated with a surface. The presentable images are represented by VkImage3 objects created by the platform. One image (which cani be an array image for multiview/stereoscopic-3D surfaces) is displayed at a time, but multiple images can~ be queued for presentation. An application renders to the image, and then queues the image for presentation to the surface.A native window cannotL be associated with more than one swapchain at a time. Further, swapchains cannota be created for native windows that have a non-Vulkan graphics API surface associated with them.Note[The presentation engine is an abstraction for the platform s compositor or display engine.The presentation engine mayW be synchronous or asynchronous with respect to the application and/or logical device.Some implementations may] use the device s graphics queue or dedicated presentation hardware to perform presentation.\The presentable images of a swapchain are owned by the presentation engine. An application can^ acquire use of a presentable image from the presentation engine. Use of a presentable image must, occur only after the image is returned by vkAcquireNextImageKHR!, and before it is presented by vkQueuePresentKHRG. This includes transitioning the image layout and rendering commands.An application can* acquire use of a presentable image with vkAcquireNextImageKHRP. After acquiring a presentable image and before modifying it, the application must use a synchronization primitive to ensure that the presentation engine has finished reading from the image. The application can} then transition the image s layout, queue rendering commands to it, etc. Finally, the application presents the image with vkQueuePresentKHR/, which releases the acquisition of the image.pThe presentation engine controls the order in which presentable images are acquired for use by the application.NoteThis allows the platform to handle situations which require out-of-order return of images after presentation. At the same time, it allows the application to generate command buffers referencing all of the images in the swapchain at initialization time, rather than in its main loop.See Also<, E, K, V, `, ~,  , , , e, f, k, , m, ~8Dummy data to tag the  withu^VkDeviceGroupPresentModeFlagBitsKHR - Bitmask specifying supported device group present modesSee Also5, .wEVkSwapchainCreateFlagBitsKHR - Bitmask controlling swapchain creationSee Also/yfvkGetPhysicalDevicePresentRectanglesKHR - Query present rectangles for a surface on a physical device ParametersphysicalDevice is the physical device.surface is the surface. pRectCountn is a pointer to an integer related to the number of rectangles available or queried, as described below.pRects is either NULL or a pointer to an array of VkRect2D structures. DescriptionIf pRects is NULL@, then the number of rectangles used when presenting the given surface is returned in  pRectCount. Otherwise,  pRectCount mustG point to a variable set by the user to the number of elements in the pRectse array, and on return the variable is overwritten with the number of structures actually written to pRects. If the value of  pRectCount1 is less than the number of rectangles, at most  pRectCount structures will be written. If  pRectCount> is smaller than the number of rectangles used for the given surface,  VK_INCOMPLETE will be returned instead of  VK_SUCCESS> to indicate that not all the available values were returned.;The values returned by this command are not invariant, and mayF change in response to the surface being moved, resized, or occluded.(The rectangles returned by this command must not overlap.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handlesurface must be a valid  VkSurfaceKHR handle pRectCount must be a valid pointer to a uint32_t valueIf the value referenced by  pRectCount is not 0, and pRects is not NULL, pRects must( be a valid pointer to an array of  pRectCount VkRect2D structuresBoth of physicalDevice, and surface must? have been created, allocated, or retrieved from the same  VkInstanceHost SynchronizationHost access to surface must be externally synchronized Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS  VK_INCOMPLETE ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, ,  szTvkAcquireNextImage2KHR - Retrieve the index of the next available presentable image Parametersdevice is the device associated with  swapchain. pAcquireInfo* is a pointer to a structure of type <& containing parameters of the acquire. pImageIndex is a pointer to a uint32_t8 that is set to the index of the next image to use. Valid UsagesIf the number of currently acquired images is greater than the difference between the number of images in the  swapchain member of  pAcquireInfo and the value of K:: minImageCount$ as returned by a call to T with the surface used to create  swapchain, the timeout member of  pAcquireInfo must not be  UINT64_MAXValid Usage (Implicit)device must be a valid VkDevice handle pAcquireInfo must$ be a valid pointer to a valid VkAcquireNextImageInfoKHR structure pImageIndex must be a valid pointer to a uint32_t value Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS  VK_TIMEOUT  VK_NOT_READY VK_SUBOPTIMAL_KHR ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_DEVICE_LOST VK_ERROR_OUT_OF_DATE_KHR VK_ERROR_SURFACE_LOST_KHRSee Also<, {RvkGetDeviceGroupSurfacePresentModesKHR - Query present capabilities for a surface Parametersdevice is the logical device.surface is the surface.pModes& is a pointer to a value of type  VkDeviceGroupPresentModeFlagsKHRS that is filled with the supported device group present modes for the surface. Description:The modes returned by this command are not invariant, and mayT change in response to the surface being moved, resized, or occluded. These modes must' be a subset of the modes returned by |.Valid Usage (Implicit)device must be a valid VkDevice handlesurface must be a valid  VkSurfaceKHR handlepModes must be a valid pointer to a . valueBoth of device, and surface must? have been created, allocated, or retrieved from the same  VkInstanceHost SynchronizationHost access to surface must be externally synchronized Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_SURFACE_LOST_KHRSee Also, .,  s|`vkGetDeviceGroupPresentCapabilitiesKHR - Query present capabilities from other physical devices Parametersdevice is the logical device.pDeviceGroupPresentCapabilities* is a pointer to a structure of type P< that is filled with the logical device s capabilities.Valid Usage (Implicit)device must be a valid VkDevice handlepDeviceGroupPresentCapabilities must be a valid pointer to a #VkDeviceGroupPresentCapabilitiesKHR structure Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, P}3vkQueuePresentKHR - Queue an image for presentation Parametersqueue~ is a queue that is capable of presentation to the target surface s platform on the same device as the image s swapchain. pPresentInfo$ is a pointer to an instance of the V> structure specifying the parameters of the presentation. DescriptionNoteThere is no requirement for an application to present images in the same order that they were acquired - applications can arbitrarily present any image that is currently acquired. Valid UsageEach element of  pSwapchains member of  pPresentInfo musta be a swapchain that is created for a surface for which presentation is supported from queue$ as determined using a call to $vkGetPhysicalDeviceSurfaceSupportKHRIf more than one member of  pSwapchainsn was created from a display surface, all display surfaces referenced that refer to the same display must use the same display modeHWhen a semaphore unsignal operation defined by the elements of the pWaitSemaphores member of  pPresentInfo executes on queue, no other queue must" be waiting on the same semaphore.All elements of the pWaitSemaphores member of  pPresentInfo must* be semaphores that are signaled, or have  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-semaphores-signaling semaphore signal operations) previously submitted for execution.;Any writes to memory backing the images referenced by the  pImageIndices and  pSwapchains members of  pPresentInfo, that are available before } is executed, are automatically made visible to the read access performed by the presentation engine. This automatic visibility operation for an image happens-after the semaphore signal operation, and happens-before the presentation engine accesses the image.4Queueing an image for presentation defines a set of queue operations, including waiting on the semaphores and submitting a presentation request to the presentation engine. However, the scope of this set of queue operations does not include the actual processing of the image by the presentation engine.If vkQueuePresentKHRA fails to enqueue the corresponding set of queue operations, it may return VK_ERROR_OUT_OF_HOST_MEMORY or VK_ERROR_OUT_OF_DEVICE_MEMORY!. If it does, the implementation must ensure that the state and contents of any resources or synchronization primitives referenced is unaffected by the call or its failure.If vkQueuePresentKHRc fails in such a way that the implementation is unable to make that guarantee, the implementation must return VK_ERROR_DEVICE_LOST.[However, if the presentation request is rejected by the presentation engine with an error VK_ERROR_OUT_OF_DATE_KHR or VK_ERROR_SURFACE_LOST_KHR, the set of queue operations are still considered to be enqueued and thus any semaphore to be waited on gets unsignaled when the corresponding queue operation is complete.Valid Usage (Implicit)queue must be a valid VkQueue handle pPresentInfo must$ be a valid pointer to a valid VkPresentInfoKHR structureHost SynchronizationHost access to queue must be externally synchronizedHost access to pPresentInfo.pWaitSemaphores[] must be externally synchronizedHost access to pPresentInfo.pSwapchains[] must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type m - l - g Any | -  Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS VK_SUBOPTIMAL_KHR ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_DEVICE_LOST VK_ERROR_OUT_OF_DATE_KHR VK_ERROR_SURFACE_LOST_KHRSee AlsoV, ~SvkAcquireNextImageKHR - Retrieve the index of the next available presentable image Parametersdevice is the device associated with  swapchain. swapchainI is the non-retired swapchain from which an image is being acquired.timeoutV specifies how long the function waits, in nanoseconds, if no image is available. semaphore is  or a semaphore to signal.fence is  or a fence to signal. pImageIndex is a pointer to a uint32_tq that is set to the index of the next image to use (i.e. an index into the array of images returned by vkGetSwapchainImagesKHR). Valid Usage swapchain must not be in the retired stateIf  semaphore is not  it must be unsignaledIf  semaphore is not  it must@ not have any uncompleted signal or wait operations pendingIf fence is not  it must be unsignaled and mustg not be associated with any other queue command that has not yet completed execution on that queue semaphore and fence must not both be equal to oIf the number of currently acquired images is greater than the difference between the number of images in  swapchain and the value of K:: minImageCount$ as returned by a call to T with the surface used to create  swapchain, timeout must not be  UINT64_MAXValid Usage (Implicit)device must be a valid VkDevice handle swapchain must be a valid VkSwapchainKHR handleIf  semaphore is not ,  semaphore must be a valid  VkSemaphore handleIf fence is not , fence must be a valid VkFence handle pImageIndex must be a valid pointer to a uint32_t valueIf  semaphore is a valid handle, it must6 have been created, allocated, or retrieved from deviceIf fence is a valid handle, it must6 have been created, allocated, or retrieved from deviceBoth of device, and  swapchain that are valid handles must? have been created, allocated, or retrieved from the same  VkInstanceHost SynchronizationHost access to  swapchain must be externally synchronizedHost access to  semaphore must be externally synchronizedHost access to fence must be externally synchronized Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS  VK_TIMEOUT  VK_NOT_READY VK_SUBOPTIMAL_KHR ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_DEVICE_LOST VK_ERROR_OUT_OF_DATE_KHR VK_ERROR_SURFACE_LOST_KHRSee Also, , , t]vkGetSwapchainImagesKHR - Obtain the array of presentable images associated with a swapchain Parametersdevice is the device associated with  swapchain. swapchain is the swapchain to query.pSwapchainImageCount{ is a pointer to an integer related to the number of presentable images available or queried, as described below.pSwapchainImages is either NULL" or a pointer to an array of VkImage handles. DescriptionIf pSwapchainImages is NULL-, then the number of presentable images for  swapchain is returned in pSwapchainImageCount. Otherwise, pSwapchainImageCount mustG point to a variable set by the user to the number of elements in the pSwapchainImagesf array, and on return the variable is overwritten with the number of structures actually written to pSwapchainImages. If the value of pSwapchainImageCount4 is less than the number of presentable images for  swapchain , at most pSwapchainImageCount! structures will be written. If pSwapchainImageCount7 is smaller than the number of presentable images for  swapchain,  VK_INCOMPLETE will be returned instead of  VK_SUCCESS> to indicate that not all the available values were returned.Valid Usage (Implicit)device must be a valid VkDevice handle swapchain must be a valid VkSwapchainKHR handlepSwapchainImageCount must be a valid pointer to a uint32_t valueIf the value referenced by pSwapchainImageCount is not 0 , and pSwapchainImages is not NULL, pSwapchainImages must( be a valid pointer to an array of pSwapchainImageCount VkImage handlesBoth of device, and  swapchain must? have been created, allocated, or retrieved from the same  VkInstance Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS  VK_INCOMPLETE ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, 2, t2vkDestroySwapchainKHR - Destroy a swapchain object Parametersdevice is the VkDevice associated with  swapchain. swapchain is the swapchain to destroy. pAllocator is the allocator used for host memory allocated for the swapchain object when there is no more specific allocator available (see  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation). DescriptionThe application must not destroy a swapchain until after completion of all outstanding operations on images that were acquired from the swapchain.  swapchain and all associated VkImage handles are destroyed, and mustJ not be acquired or used any more by the application. The memory of each VkImage will only be freed after that image is no longer used by the presentation engine. For example, if one image of the swapchain is being displayed in a window, the memory for that image may not be freed until the window is destroyed, or another swapchain is created for the window. Destroying the swapchain does not invalidate the parent  VkSurfaceKHR, and a new swapchain can be created with it.When a swapchain associated with a display surface is destroyed, if the image most recently presented to the display surface is from the swapchain being destroyed, then either any display resources modified by presenting images from any swapchain associated with the display surface must be reverted by the implementation to their state prior to the first present performed on one of these swapchains, or such resources must be left in their current state. Valid Usage-All uses of presentable images acquired from  swapchain must have completed executionIf VkAllocationCallbacks were provided when  swapchain1 was created, a compatible set of callbacks must be provided hereIf no VkAllocationCallbacks were provided when  swapchain was created,  pAllocator must be NULLValid Usage (Implicit)device must be a valid VkDevice handleIf  swapchain is not ,  swapchain must be a valid VkSwapchainKHR handleIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structureBoth of device, and  swapchain that are valid handles must? have been created, allocated, or retrieved from the same  VkInstanceHost SynchronizationHost access to  swapchain must be externally synchronizedSee Also, , t)vkCreateSwapchainKHR - Create a swapchain Parametersdevice+ is the device to create the swapchain for. pCreateInfo) is a pointer to an instance of the `C structure specifying the parameters of the created swapchain. pAllocator is the allocator used for host memory allocated for the swapchain object when there is no more specific allocator available (see  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation). pSwapchain is a pointer to a VkSwapchainKHRD handle in which the created swapchain object will be returned.Valid Usage (Implicit)device must be a valid VkDevice handle pCreateInfo must$ be a valid pointer to a valid VkSwapchainCreateInfoKHR structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structure pSwapchain must be a valid pointer to a VkSwapchainKHR handleHost SynchronizationHost access to pCreateInfo.surface must be externally synchronizedHost access to pCreateInfo.oldSwapchain must be externally synchronized Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_DEVICE_LOST VK_ERROR_SURFACE_LOST_KHR !VK_ERROR_NATIVE_WINDOW_IN_USE_KHRSee Also, , `, t7VK_SWAPCHAIN_CREATE_SPLIT_INSTANCE_BIND_REGIONS_BIT_KHRB specifies that images created from the swapchain (i.e. with the  swapchain member of K! set to this swapchain s handle) must use /VK_IMAGE_CREATE_SPLIT_INSTANCE_BIND_REGIONS_BIT.7VK_DEVICE_GROUP_PRESENT_MODE_LOCAL_MULTI_DEVICE_BIT_KHRF specifies that multiple physical devices with a presentation engine can* each present their own swapchain images.(VK_DEVICE_GROUP_PRESENT_MODE_SUM_BIT_KHR@ specifies that any physical device with a presentation engine canG present the sum of swapchain images from any physical devices in its  presentMask.+VK_DEVICE_GROUP_PRESENT_MODE_REMOTE_BIT_KHR@ specifies that any physical device with a presentation engine can; present swapchain images from any physical device in its  presentMask.*VK_DEVICE_GROUP_PRESENT_MODE_LOCAL_BIT_KHR@ specifies that any physical device with a presentation engine can# present its own swapchain images.h./0123456789:;<=>?BC@ADEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdfeimnghjklopqrstuvwxyz{|}~hwxuvt~}|{zy`abcdfeimnghjklopqrsVWXYZ[\]^_PQRSTUKLMNOEFGHIJ<=>?BC@AD56789:;01234/.None "-STbejkEmaVkDisplayPresentInfoKHR - Structure describing parameters of a queue presentation to a swapchain DescriptionIf the extent of the srcRect and dstRectA are not equal, the presented pixels will be scaled accordingly. Valid UsagesrcRect mustP specify a rectangular region that is a subset of the image being presenteddstRect must; specify a rectangular region that is a subset of the  visibleRegionF parameter of the display mode the swapchain being presented usesIf the persistentContent member of the VkDisplayPropertiesKHR structure returned by 'vkGetPhysicalDeviceDisplayPropertiesKHR9 for the display the present operation targets then  persistent must be VK_FALSEValid Usage (Implicit)sType must be *VK_STRUCTURE_TYPE_DISPLAY_PRESENT_INFO_KHRSee AlsoVkBool32, , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.srcRect2 is a rectangular region of pixels to present. It must/ be a subset of the image being presented. If VkDisplayPresentInfoKHRT is not specified, this region will be assumed to be the entire presentable image.dstRectX is a rectangular region within the visible region of the swapchain s display mode. If VkDisplayPresentInfoKHR5 is not specified, this region will be assumed to be the entire visible region of the visible region of the swapchain s mode. If the specified rectangle is a subset of the display mode s visible region, content from display planes below the swapchain s plane will be visible outside the rectangle. If there are no planes below the swapchain s, the area outside the specified rectangle will be black. If portions of the specified rectangle are outside of the display s visible region, pixels mapping only to those portions of the rectangle will be discarded. persistent : If this is VK_TRUE#, the display engine will enable buffered mode on displays that support it. This allows the display engine to stop sending content to the display until a new image is presented. The display will instead maintain a copy of the last presented image. This allows less power to be used, but may$ increase presentation latency. If VkDisplayPresentInfoKHR5 is not specified, persistent mode will not be used.WvkCreateSharedSwapchainsKHR - Create multiple swapchains that share presentable images Parametersdevice, is the device to create the swapchains for.swapchainCount' is the number of swapchains to create. pCreateInfos" is a pointer to an array of `E structures specifying the parameters of the created swapchains. pAllocator is the allocator used for host memory allocated for the swapchain objects when there is no more specific allocator available (see  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation). pSwapchains is a pointer to an array of VkSwapchainKHRF handles in which the created swapchain objects will be returned. DescriptionvkCreateSharedSwapchains is similar to  $, except that it takes an array of VkSwapchainCreateInfoKHR8 structures, and returns an array of swapchain objects._The swapchain creation parameters that affect the properties and number of presentable images must match between all the swapchains. If the displays used by any of the swapchains do not use the same presentable image layout or are incompatible in a way that prevents sharing images, swapchain creation will fail with the result code !VK_ERROR_INCOMPATIBLE_DISPLAY_KHR_. If any error occurs, no swapchains will be created. Images presented to multiple swapchains mustB be re-acquired from all of them before transitioning away from VK_IMAGE_LAYOUT_PRESENT_SRC_KHRg. After destroying one or more of the swapchains, the remaining swapchains and the presentable images can continue to be used.Valid Usage (Implicit)device must be a valid VkDevice handle pCreateInfos must( be a valid pointer to an array of swapchainCount valid VkSwapchainCreateInfoKHR structuresIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structure pSwapchains must( be a valid pointer to an array of swapchainCount VkSwapchainKHR handlesswapchainCount must be greater than 0Host SynchronizationHost access to  pCreateInfos [].surface must be externally synchronizedHost access to  pCreateInfos[].oldSwapchain must be externally synchronized Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY !VK_ERROR_INCOMPATIBLE_DISPLAY_KHR VK_ERROR_DEVICE_LOST VK_ERROR_SURFACE_LOST_KHRSee Also, , `, t  None "-STbejkEvAVkPresentTimeGOOGLE - The earliest time image should be presentedSee Also presentID7 is an application-provided identification value, that can be used with the results of ], in order to uniquely identify this present. In order to be useful to the application, it shouldM be unique within some period of time that is meaningful to the application.desiredPresentTime specifies that the image given should; not be displayed to the user any earlier than this time. desiredPresentTimeP is a time in nanoseconds, relative to a monotonically-increasing clock (e.g. CLOCK_MONOTONICg (see clock_gettime(2)) on Android and Linux). A value of zero specifies that the presentation engine mayY display the image at any time. This is useful when the application desires to provide  presentID, but doesn t need a specific desiredPresentTime.LVkPresentTimesInfoGOOGLE - The earliest time each image should be presented Valid UsageswapchainCount must be the same value as VkPresentInfoKHR::swapchainCount, where VkPresentInfoKHR is in the pNext chain of this VkPresentTimesInfoGOOGLE structure.Valid Usage (Implicit)sType must be +VK_STRUCTURE_TYPE_PRESENT_TIMES_INFO_GOOGLEIf pTimes is not NULL, pTimes must( be a valid pointer to an array of swapchainCount VkPresentTimeGOOGLE structuresswapchainCount must be greater than 0See Also, sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.swapchainCountA is the number of swapchains being presented to by this command.pTimes is NULL or a pointer to an array of VkPresentTimeGOOGLE elements with swapchainCount entries. If not NULL, each element of pTimesT contains the earliest time to present the image corresponding to the entry in the VkPresentInfoKHR:: pImageIndices array.lVkPastPresentationTimingGOOGLE - Structure containing timing information about a previously-presented image DescriptionThe results for a given  swapchain and  presentID are only returned once from !vkGetPastPresentationTimingGOOGLE.The application can use the VkPastPresentationTimingGOOGLE< values to occasionally adjust its timing. For example, if actualPresentTime# is later than expected (e.g. one refreshDurationM late), the application may increase its target IPD to a higher multiple of refreshDuration7 (e.g. decrease its frame rate from 60Hz to 30Hz). If actualPresentTime and earliestPresentTime% are consistently different, and if  presentMargine is consistently large enough, the application may decrease its target IPD to a smaller multiple of refreshDuration7 (e.g. increase its frame rate from 30Hz to 60Hz). If actualPresentTime and earliestPresentTime are same, and if  presentMarginX is consistently high, the application may delay the start of its input-render-present loop in order to decrease the latency between user input and the corresponding present (always leaving some margin in case a new image takes longer to render than the previous image). An application that desires its target IPD to always be the same as refreshDuration", can also adjust features until actualPresentTime is never late and  presentMargin is satisfactory.See Also presentID@ is an application-provided value that was given to a previous vkQueuePresentKHR command via :: presentID (see below). It can< be used to uniquely identify a previous present with the  command.desiredPresentTimeA is an application-provided value that was given to a previous  command via ::desiredPresentTimek. If non-zero, it was used by the application to indicate that an image not be presented any sooner than desiredPresentTime.actualPresentTime# is the time when the image of the  swapchain was actually displayed.earliestPresentTime# is the time when the image of the  swapchain" could have been displayed. This may differ from actualPresentTimeK if the application requested that the image be presented no sooner than ::desiredPresentTime. presentMargin# is an indication of how early the vkQueuePresentKHRc command was processed compared to how soon it needed to be processed, and still be presented at earliestPresentTime.QVkRefreshCycleDurationGOOGLE - Structure containing the RC duration of a displaySee AlsorefreshDurationO is the number of nanoseconds from the start of one refresh cycle to the next.RvkGetPastPresentationTimingGOOGLE - Obtain timing of a previously-presented image Parametersdevice is the device associated with  swapchain. swapchainN is the swapchain to obtain presentation timing information duration for.pPresentationTimingCount: is a pointer to an integer related to the number of VkPastPresentationTimingGOOGLE. structures to query, as described below.pPresentationTimings is either NULL% or a pointer to an an array of VkPastPresentationTimingGOOGLE structures. DescriptionIf pPresentationTimings is NULLC, then the number of newly-available timing records for the given  swapchain is returned in pPresentationTimingCount . Otherwise, pPresentationTimingCount mustH point to a variable set by the user to the number of elements in the pPresentationTimingsf array, and on return the variable is overwritten with the number of structures actually written to pPresentationTimings. If the value of pPresentationTimingCountF is less than the number of newly-available timing records, at most pPresentationTimingCount! structures will be written. If pPresentationTimingCountM is smaller than the number of newly-available timing records for the given  swapchain,  VK_INCOMPLETE will be returned instead of  VK_SUCCESS> to indicate that not all the available values were returned.Valid Usage (Implicit)device must be a valid VkDevice handle swapchain must be a valid VkSwapchainKHR handlepPresentationTimingCount must be a valid pointer to a uint32_t valueIf the value referenced by pPresentationTimingCount is not 0 , and pPresentationTimings is not NULL, pPresentationTimings must# be a valid pointer to an array of pPresentationTimingCount VkPastPresentationTimingGOOGLE structuresBoth of device, and  swapchain must? have been created, allocated, or retrieved from the same  VkInstanceHost SynchronizationHost access to  swapchain must be externally synchronized Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS  VK_INCOMPLETE ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_DEVICE_LOST VK_ERROR_OUT_OF_DATE_KHR VK_ERROR_SURFACE_LOST_KHRSee Also, , tMvkGetRefreshCycleDurationGOOGLE - Obtain the RC duration of the PE s display Parametersdevice is the device associated with  swapchain. swapchain5 is the swapchain to obtain the refresh duration for.pDisplayTimingProperties) is a pointer to an instance of the VkRefreshCycleDurationGOOGLE structure.Valid Usage (Implicit)device must be a valid VkDevice handle swapchain must be a valid VkSwapchainKHR handlepDisplayTimingProperties must be a valid pointer to a VkRefreshCycleDurationGOOGLE structureBoth of device, and  swapchain must? have been created, allocated, or retrieved from the same  VkInstanceHost SynchronizationHost access to  swapchain must be externally synchronized Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_DEVICE_LOST VK_ERROR_SURFACE_LOST_KHRSee Also, , tNone "-STbejkEG 4VkHdrMetadataEXT - structure to specify Hdr metadata DescriptionNotecThe validity and use of this data is outside the scope of Vulkan and thus no Valid Usage is given.See Also, , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.displayPrimaryRedD is the mastering display s red primary in chromaticity coordinatesdisplayPrimaryGreenF is the mastering display s green primary in chromaticity coordinatesdisplayPrimaryBlueE is the mastering display s blue primary in chromaticity coordinates whitePointD is the mastering display s white-point in chromaticity coordinates maxLuminance: is the maximum luminance of the mastering display in nits minLuminance: is the minimum luminance of the mastering display in nitsmaxContentLightLevel' is content s maximum luminance in nitsmaxFrameAverageLightLevel2 is the maximum frame average light level in nits@VkXYColorEXT - structure to specify X,Y chromaticity coordinatesSee Also2vkSetHdrMetadataEXT - function to set Hdr metadata Parametersdevice; is the logical device where the swapchain(s) were created.swapchainCount. is the number of swapchains included in  pSwapchains. pSwapchains is a pointer to the array of swapchainCount VkSwapchainKHR handles. pMetadata is a pointer to the array of swapchainCount VkHdrMetadataEXT structures.Valid Usage (Implicit)device must be a valid VkDevice handle pSwapchains must( be a valid pointer to an array of swapchainCount valid VkSwapchainKHR handles pMetadata must( be a valid pointer to an array of swapchainCount valid VkHdrMetadataEXT structuresswapchainCount must be greater than 0Both of device, and the elements of  pSwapchains must? have been created, allocated, or retrieved from the same  VkInstanceSee Also, , tNone "-KSTbejkFx FVkSwapchainCounterCreateInfoEXT - Specify the surface counters desired Valid Usage The bits in surfaceCounters must be supported by ::surface, as reported by \.Valid Usage (Implicit)sType must be 3VK_STRUCTURE_TYPE_SWAPCHAIN_COUNTER_CREATE_INFO_EXTsurfaceCounters must be a valid combination of   valuesSee Also,   sType is the type of this structure. pNext is NULL1 or a pointer to an extension-specific structure.surfaceCounters is a bitmask of  : specifying surface counters to enable for the swapchain.:VkDisplayEventInfoEXT - Describe a display event to createValid Usage (Implicit)sType must be (VK_STRUCTURE_TYPE_DISPLAY_EVENT_INFO_EXTpNext must be NULL displayEvent must be a valid  valueSee Also, , %sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure. displayEvent is a - specifying when the fence will be signaled.8VkDeviceEventInfoEXT - Describe a device event to createValid Usage (Implicit)sType must be 'VK_STRUCTURE_TYPE_DEVICE_EVENT_INFO_EXTpNext must be NULL deviceEvent must be a valid   valueSee Also , , &sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.=VkDisplayPowerInfoEXT - Describe the power state of a displayValid Usage (Implicit)sType must be (VK_STRUCTURE_TYPE_DISPLAY_POWER_INFO_EXTpNext must be NULL powerState must be a valid " valueSee Also", , 'sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure. powerState is a "6 value specifying the new power state of the display.AVkDisplayEventTypeEXT - Events that can occur on a display objectSee Also ?VkDeviceEventTypeEXT - Events that can occur on a device objectSee Also"<VkDisplayPowerStateEXT - Possible power states for a displaySee Also$GvkGetSwapchainCounterEXT - Query the current value of a surface counter Parametersdevice is the VkDevice associated with  swapchain. swapchain8 is the swapchain from which to query the counter value.counter is the counter to query. pCounterValue. will return the current value of the counter. DescriptionXIf a counter is not available because the swapchain is out of date, the implementation may return VK_ERROR_OUT_OF_DATE_KHR. Valid Usage One or more present commands on  swapchain must5 have been processed by the presentation engine.Valid Usage (Implicit)device must be a valid VkDevice handle swapchain must be a valid VkSwapchainKHR handlecounter must be a valid   value pCounterValue must be a valid pointer to a uint64_t valueBoth of device, and  swapchain must? have been created, allocated, or retrieved from the same  VkInstance Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_DEVICE_LOST VK_ERROR_OUT_OF_DATE_KHRSee Also,  , t%FvkRegisterDisplayEventEXT - Signal a fence when a display event occurs Parametersdevice% is a logical device associated with displaydisplay# is the display on which the event may occur.pDisplayEventInfo) is a pointer to an instance of the D structure describing the event of interest to the application. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter.pFenceI points to a handle in which the resulting fence object is returned.Valid Usage (Implicit)device must be a valid VkDevice handledisplay must be a valid  VkDisplayKHR handlepDisplayEventInfo must$ be a valid pointer to a valid VkDisplayEventInfoEXT structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structurepFence must be a valid pointer to a VkFence handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESSSee Also, , ,  , &DvkRegisterDeviceEventEXT - Signal a fence when a device event occurs Parametersdevice( is a logical device on which the event may occur.pDeviceEventInfo) is a pointer to an instance of the D structure describing the event of interest to the application. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter.pFenceI points to a handle in which the resulting fence object is returned.Valid Usage (Implicit)device must be a valid VkDevice handlepDeviceEventInfo must$ be a valid pointer to a valid VkDeviceEventInfoEXT structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structurepFence must be a valid pointer to a VkFence handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESSSee Also, , , ';vkDisplayPowerControlEXT - Set the power state of a display Parametersdevice% is a logical device associated with display.display. is the display whose power state is modified.pDisplayPowerInfo is an instance of ( specifying the new power state of display.Valid Usage (Implicit)device must be a valid VkDevice handledisplay must be a valid  VkDisplayKHR handlepDisplayPowerInfo must$ be a valid pointer to a valid VkDisplayPowerInfoEXT structure Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESSSee Also,  , .)VK_DISPLAY_EVENT_TYPE_FIRST_PIXEL_OUT_EXT specifies that the fence is signaled when the first pixel of the next display refresh cycle leaves the display engine for the display./(VK_DEVICE_EVENT_TYPE_DISPLAY_HOTPLUG_EXT| specifies that the fence is signaled when a display is plugged into or unplugged from the specified device. Applications cang use this notification to determine when they need to re-enumerate the available displays on a device.0VK_DISPLAY_POWER_STATE_ON_EXT+ specifies that the display is powered on.1"VK_DISPLAY_POWER_STATE_SUSPEND_EXTI specifies that the display is put into a low power mode, from which it may be able to transition back to VK_DISPLAY_POWER_STATE_ON_EXT" more quickly than if it were in VK_DISPLAY_POWER_STATE_OFF_EXT . This state may be the same as VK_DISPLAY_POWER_STATE_OFF_EXT.2VK_DISPLAY_POWER_STATE_OFF_EXT- specifies that the display is powered down.)     !"#$%&'()*+,-./012)"#210 !/.-,+*)('&%$    None "-STbejkF7NoVkSharedPresentSurfaceCapabilitiesKHR - structure describing capabilities of a surface for shared presentationValid Usage (Implicit)sType must be 9VK_STRUCTURE_TYPE_SHARED_PRESENT_SURFACE_CAPABILITIES_KHRSee Also, PsType is the type of this structure.QpNext is NULL1 or a pointer to an extension-specific structure.R sharedPresentSupportedUsageFlags is a bitmask of /( representing the ways the application canB use the shared presentable image from a swapchain created with  x set to )VK_PRESENT_MODE_SHARED_DEMAND_REFRESH_KHR or -VK_PRESENT_MODE_SHARED_CONTINUOUS_REFRESH_KHR+ for the surface on the specified device. #VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT must- be included in the set but implementations may support additional usages.S2vkGetSwapchainStatusKHR - Get a swapchain s status Parametersdevice is the device associated with  swapchain. swapchain is the swapchain to query.Valid Usage (Implicit)device must be a valid VkDevice handle swapchain must be a valid VkSwapchainKHR handleBoth of device, and  swapchain must? have been created, allocated, or retrieved from the same  VkInstanceHost SynchronizationHost access to  swapchain must be externally synchronized Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS VK_SUBOPTIMAL_KHR ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_DEVICE_LOST VK_ERROR_OUT_OF_DATE_KHR VK_ERROR_SURFACE_LOST_KHRSee Also, t NOPQRSTUVWXY YXWVUTSNOPQRNone"KbejkF]tVkPipelineTessellationDomainOriginStateCreateInfo - Structure specifying the orientation of the tessellation domain DescriptionIf the 1VkPipelineTessellationDomainOriginStateCreateInfo structure is included in the pNext chain of He, it controls the origin of the tessellation domain. If this structure is not present, it is as if  domainOrigin were (VK_TESSELLATION_DOMAIN_ORIGIN_UPPER_LEFT.Valid Usage (Implicit)sType must be GVK_STRUCTURE_TYPE_PIPELINE_TESSELLATION_DOMAIN_ORIGIN_STATE_CREATE_INFO domainOrigin must be a valid w valueSee Also, w_sType is the type of this structure.`pNext is NULL1 or a pointer to an extension-specific structure.a domainOriginG controls the origin of the tessellation domain space, and is of type w.bHVkImageViewUsageCreateInfo - Specify the intended usage of an image view Description"When this structure is chained to VkImageViewCreateInfo the usage field overrides the implicit usage parameter inherited from image creation time and its value is used instead for the purposes of determining the valid usage conditions of w2. Valid Usageusage must8 not include any set bits that were not set in the usage member of the *I structure used to create the image this image view is created from.Valid Usage (Implicit)sType must be .VK_STRUCTURE_TYPE_IMAGE_VIEW_USAGE_CREATE_INFOusage must be a valid combination of / valuesusage must not be 0See Also, dsType is the type of this structure.epNext is NULL1 or a pointer to an extension-specific structure.fusageD is a bitmask describing the allowed usages of the image view. See /* for a description of the supported bits.gzVkPhysicalDevicePointClippingProperties - Structure describing the point clipping behavior supported by an implementationMembersThe members of the 'VkPhysicalDevicePointClippingPropertiesB structure describe the following implementation-dependent limit: DescriptionsType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.pointClippingBehaviorU is the point clipping behavior supported by the implementation, and is of type y.If the 'VkPhysicalDevicePointClippingProperties structure is included in the pNext chain of sf9, it is filled with the implementation-dependent limits.Valid Usage (Implicit)sType must be ;VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_POINT_CLIPPING_PROPERTIESSee Alsoy, l}VkRenderPassInputAttachmentAspectCreateInfo - Structure specifying, for a given subpass/input attachment pair, which aspect can be read.Valid Usage (Implicit)sType must be AVK_STRUCTURE_TYPE_RENDER_PASS_INPUT_ATTACHMENT_ASPECT_CREATE_INFOpAspectReferences must( be a valid pointer to an array of aspectReferenceCount valid  VkInputAttachmentAspectReference structuresaspectReferenceCount must be greater than 0See Alsor, nsType is the type of this structure.opNext is NULL1 or a pointer to an extension-specific structure.paspectReferenceCount; is the number of elements in the pAspectReferences array.qpAspectReferences points to an array of aspectReferenceCount number of r( structures describing which aspect(s) canB be accessed for a given input attachment within a given subpass.rqVkInputAttachmentAspectReference - Structure specifying a subpass/input attachment pair and an aspect mask that can be read. Valid UsageThere must be an input attachment at  pCreateInfo:: pSubpasses[subpass].pInputAttachments[inputAttachmentIndex].The specified input attachment must% have more than one aspect mask. aspectMask mustH be a subset of the aspect masks in the specified input attachment.Valid Usage (Implicit) aspectMask must be a valid combination of r values aspectMask must not be 0See Also, ltsubpass is an index into the  pSubpasses array of the parent VkRenderPassCreateInfo structure.uinputAttachmentIndex is an index into the pInputAttachments of the specified subpass.v aspectMask is a mask of which aspect(s) can+ be accessed within the specified subpass.wGVkTessellationDomainOrigin - Enum describing tessellation domain origin Description(VK_TESSELLATION_DOMAIN_ORIGIN_UPPER_LEFTi specifies that the origin of the domain space is in the upper left corner, as shown in figure  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#img-tessellation-topology-ul1{html_spec_relative}#img-tessellation-topology-ul.(VK_TESSELLATION_DOMAIN_ORIGIN_LOWER_LEFTi specifies that the origin of the domain space is in the lower left corner, as shown in figure  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#img-tessellation-topology-ll1{html_spec_relative}#img-tessellation-topology-ll.This enum affects how the  VertexOrderCw and VertexOrderCcwx tessellation execution modes are interpreted, since the winding is defined relative to the orientation of the domain.See Also]yFVkPointClippingBehavior - Enum specifying the point clipping behaviourSee Alsog0VK_POINT_CLIPPING_BEHAVIOR_USER_CLIP_PLANES_ONLYa specifies that the primitive is discarded only if the vertex lies outside any user clip plane.*VK_POINT_CLIPPING_BEHAVIOR_ALL_CLIP_PLANES specifies that the primitive is discarded if the vertex lies outside any clip plane, including the planes bounding the view volume.*]^_`abcdefghijklmnopqrstvuwxyz{|}~*yzwx~}|{rstvulmnopqghijkbcdef]^_`aNone-STejkFbNone "-KSTbejkJ'O3VkDependencyFlags - Bitmask of VkDependencyFlagBits DescriptionVkDependencyFlags7 is a bitmask type for setting a mask of zero or more .See Also, , JVkAttachmentDescriptionFlags - Bitmask of VkAttachmentDescriptionFlagBits DescriptionVkAttachmentDescriptionFlags7 is a bitmask type for setting a mask of zero or more .See Also, CVkSubpassDescriptionFlags - Bitmask of VkSubpassDescriptionFlagBits DescriptionVkSubpassDescriptionFlags7 is a bitmask type for setting a mask of zero or more .See Also, +VkAccessFlags - Bitmask of VkAccessFlagBits Description VkAccessFlags7 is a bitmask type for setting a mask of zero or more .See Also, , -, C, YVkFramebufferCreateInfo - Structure specifying parameters of a newly created framebuffer Description Applications must ensure that all accesses to memory that backs image subresources used as attachments in a given renderpass instance either happen-before the  ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#renderpass-load-store-opsload operations- for those attachments, or happen-after the  ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#renderpass-load-store-opsstore operations for those attachments.+For depth/stencil attachments, each aspect can be used separately as attachments and non-attachments as long as the non-attachment accesses are also via an image subresource in either the :VK_IMAGE_LAYOUT_DEPTH_READ_ONLY_STENCIL_ATTACHMENT_OPTIMAL layout or the :VK_IMAGE_LAYOUT_DEPTH_ATTACHMENT_STENCIL_READ_ONLY_OPTIMALo layout, and the attachment resource uses whichever of those two layouts the image accesses do not. Use of non-attachment aspects in this case is only well defined if the attachment is used in the subpass where the non-attachment access is being made, or the layout of the image subresource is constant throughout the entire render pass instance, including the  initialLayout and  finalLayout.NoteThese restrictions mean that the render pass has full knowledge of all uses of all of the attachments, so that the implementation is able to make correct decisions about when and how to perform layout transitions, when to overlap execution of subpasses, etc.It is legal for a subpass to use no color or depth/stencil attachments, and rather use shader side effects such as image stores and atomics to produce an output. In this case, the subpass continues to use the width, height, and layersM of the framebuffer to define the dimensions of the rendering area, and the rasterizationSamples from each pipeline s H~F to define the number of samples used in rasterization; however, if /::variableMultisampleRate is VK_FALSEG, then all pipelines to be bound with a given zero-attachment subpass must have the same value for H~::rasterizationSamples. Valid UsageattachmentCount must4 be equal to the attachment count specified in  renderPassEach element of  pAttachmentsB that is used as a color attachment or resolve attachment by  renderPass must have been created with a usage value including #VK_IMAGE_USAGE_COLOR_ATTACHMENT_BITEach element of  pAttachments4 that is used as a depth/stencil attachment by  renderPass must have been created with a usage value including +VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BITEach element of  pAttachments- that is used as an input attachment by  renderPass must have been created with a usage value including #VK_IMAGE_USAGE_INPUT_ATTACHMENT_BITEach element of  pAttachments must have been created with an  value that matches the % specified by the corresponding VkAttachmentDescription in  renderPassEach element of  pAttachments must have been created with a samples value that matches the samples+ value specified by the corresponding VkAttachmentDescription in  renderPassEach element of  pAttachments mustR have dimensions at least as large as the corresponding framebuffer dimensionEach element of  pAttachments must% only specify a single mip levelEach element of  pAttachments must1 have been created with the identity swizzlewidth must be greater than 0.width must be less than or equal to VkPhysicalDeviceLimits::maxFramebufferWidthheight must be greater than 0.height must be less than or equal to VkPhysicalDeviceLimits::maxFramebufferHeightlayers must be greater than 0.layers must be less than or equal to VkPhysicalDeviceLimits::maxFramebufferLayersEach element of  pAttachments@ that is a 2D or 2D array image view taken from a 3D image must not be a depth/stencil formatValid Usage (Implicit)sType must be )VK_STRUCTURE_TYPE_FRAMEBUFFER_CREATE_INFOpNext must be NULLflags must be 0 renderPass must be a valid  VkRenderPass handleIf attachmentCount is not 0,  pAttachments must( be a valid pointer to an array of attachmentCount valid  VkImageView handlesBoth of  renderPass, and the elements of  pAttachments that are valid handles must? have been created, allocated, or retrieved from the same VkDeviceSee Also, , , , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.flags is reserved for future use. renderPass` is a render pass that defines what render passes the framebuffer will be compatible with. See  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#renderpass-compatibilityRender Pass Compatibility for details.attachmentCount is the number of attachments. pAttachments is an array of  VkImageView` handles, each of which will be used as the corresponding attachment in a render pass instance.width, height and layersT define the dimensions of the framebuffer. If the render pass uses multiview, then layers must be one and each attachment requires a number of layers that is greater than the maximum bit index set in the view mask in the subpasses in which it is used.XVkRenderPassCreateInfo - Structure specifying parameters of a newly created render pass Valid UsageUIf any two subpasses operate on attachments with overlapping ranges of the same VkDeviceMemory> object, and at least one subpass writes to that area of VkDeviceMemory, a subpass dependency mustX be included (either directly or via some intermediate subpasses) between themIf the  attachment member of any element of pInputAttachments, pColorAttachments, pResolveAttachments or pDepthStencilAttachment3, or the attachment indexed by any element of pPreserveAttachments in any element of  pSubpasses is bound to a range of a VkDeviceMemoryk object that overlaps with any other attachment in any subpass (including the same subpass), the VkAttachmentDescription structures describing them must include 'VK_ATTACHMENT_DESCRIPTION_MAY_ALIAS_BIT in flagsIf the  attachment member of any element of pInputAttachments, pColorAttachments, pResolveAttachments or pDepthStencilAttachment, or any element of pPreserveAttachments in any element of  pSubpasses is not VK_ATTACHMENT_UNUSED , it must be less than attachmentCount!The value of each element of the pPreserveAttachments member in each element of  pSubpasses must not be VK_ATTACHMENT_UNUSEDFor any member of  pAttachments with a loadOp equal to VK_ATTACHMENT_LOAD_OP_CLEAR(, the first use of that attachment must not specify a layout equal to (VK_IMAGE_LAYOUT_SHADER_READ_ONLY_OPTIMAL or /VK_IMAGE_LAYOUT_DEPTH_STENCIL_READ_ONLY_OPTIMAL.For any member of  pAttachments with a loadOp equal to VK_ATTACHMENT_LOAD_OP_CLEAR(, the first use of that attachment must not specify a layout equal to :VK_IMAGE_LAYOUT_DEPTH_READ_ONLY_STENCIL_ATTACHMENT_OPTIMAL.For any member of  pAttachments with a  stencilLoadOp equal to VK_ATTACHMENT_LOAD_OP_CLEAR(, the first use of that attachment must not specify a layout equal to :VK_IMAGE_LAYOUT_DEPTH_ATTACHMENT_STENCIL_READ_ONLY_OPTIMAL.For any element of  pDependencies , if the  srcSubpass is not VK_SUBPASS_EXTERNAL', all stage flags included in the  srcStageMask member of that dependency must0 be a pipeline stage supported by the  shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typespipeline identified by the pipelineBindPoint member of the source subpass.For any element of  pDependencies , if the  dstSubpass is not VK_SUBPASS_EXTERNAL', all stage flags included in the  dstStageMask member of that dependency must0 be a pipeline stage supported by the  shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typespipeline identified by the pipelineBindPoint member of the source subpass.Valid Usage (Implicit)sType must be )VK_STRUCTURE_TYPE_RENDER_PASS_CREATE_INFOEach pNext: member of any structure (including this one) in the pNext chain must be either NULL/ or a pointer to a valid instance of  or Each sType member in the pNext chain must be uniqueflags must be 0If attachmentCount is not 0,  pAttachments must( be a valid pointer to an array of attachmentCount valid VkAttachmentDescription structures pSubpasses must# be a valid pointer to an array of  subpassCount valid VkSubpassDescription structuresIf dependencyCount is not 0,  pDependencies must( be a valid pointer to an array of dependencyCount valid VkSubpassDependency structures subpassCount must be greater than 0See Also, , , , ,  sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.flags is reserved for future use.attachmentCount is the number of attachments used by this render pass, or zero indicating no attachments. Attachments are referred to by zero-based indices in the range [0,attachmentCount). pAttachments points to an array of attachmentCount number of : structures describing properties of the attachments, or NULL if attachmentCount is zero. subpassCount~ is the number of subpasses to create for this render pass. Subpasses are referred to by zero-based indices in the range [0, subpassCount). A render pass must have at least one subpass. pSubpasses points to an array of  subpassCount number of 4 structures describing properties of the subpasses.dependencyCount_ is the number of dependencies between pairs of subpasses, or zero indicating no dependencies. pDependencies points to an array of dependencyCount number of D structures describing dependencies between pairs of subpasses, or NULL if dependencyCount is zero.?VkSubpassDependency - Structure specifying a subpass dependency DescriptionIf  srcSubpass is equal to  dstSubpass then the  describes a  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-barriers-subpass-self-dependenciessubpass self-dependency, and only constrains the pipeline barriers allowed within a subpass instance. Otherwise, when a render pass instance which includes a subpass dependency is submitted to a queue, it defines a memory dependency between the subpasses identified by  srcSubpass and  dstSubpass.If  srcSubpass is equal to VK_SUBPASS_EXTERNAL , the first  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-dependencies-scopessynchronization scope* includes commands that occur earlier in  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-submission-ordersubmission order than the  used to begin the render pass instance. Otherwise, the first set of commands includes all commands submitted as part of the subpass instance identified by  srcSubpassO and any load, store or multisample resolve operations on attachments used in  srcSubpassv. In either case, the first synchronization scope is limited to operations on the pipeline stages determined by the  shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-maskssource stage mask specified by  srcStageMask.If  dstSubpass is equal to VK_SUBPASS_EXTERNAL, the second  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-dependencies-scopessynchronization scope( includes commands that occur later in  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-submission-ordersubmission order than the  used to end the render pass instance. Otherwise, the second set of commands includes all commands submitted as part of the subpass instance identified by  dstSubpassO and any load, store or multisample resolve operations on attachments used in  dstSubpassw. In either case, the second synchronization scope is limited to operations on the pipeline stages determined by the  shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-masksdestination stage mask specified by  dstStageMask. The first  xhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-dependencies-access-scopes access scope@ is limited to access in the pipeline stages determined by the  shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-maskssource stage mask specified by  srcStageMask-. It is also limited to access types in the  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-access-maskssource access mask specified by  srcAccessMask. The second  xhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-dependencies-access-scopes access scopeA is limited to access in the pipeline stages determined by the  shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-masksdestination stage mask specified by  dstStageMask-. It is also limited to access types in the  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-access-masksdestination access mask specified by  dstAccessMask.The  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-dependencies-available-and-visible'availability and visibility operations: defined by a subpass dependency affect the execution of  khttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#renderpass-layout-transitionsimage layout transitions within the render pass.NotewFor non-attachment resources, the memory dependency expressed by subpass dependency is nearly identical to that of a C (with matching  srcAccessMask/ dstAccessMask( parameters) submitted as a part of a  (with matching  srcStageMask/ dstStageMask parameters). The only difference being that its scopes are limited to the identified subpasses rather than potentially affecting everything before and after.AFor attachments however, subpass dependencies work more like an - defined similarly to the C) above, the queue family indices set to VK_QUEUE_FAMILY_IGNORED, and layouts as follows:The equivalent to  oldLayoutJ is the attachment s layout according to the subpass description for  srcSubpass.The equivalent to  newLayoutJ is the attachment s layout according to the subpass description for  dstSubpass. Valid UsageIf  srcSubpass is not VK_SUBPASS_EXTERNAL,  srcStageMask must not include VK_PIPELINE_STAGE_HOST_BITIf  dstSubpass is not VK_SUBPASS_EXTERNAL,  dstStageMask must not include VK_PIPELINE_STAGE_HOST_BITIf the  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-geometryShadergeometry shaders feature is not enabled,  srcStageMask must not contain %VK_PIPELINE_STAGE_GEOMETRY_SHADER_BITIf the  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-geometryShadergeometry shaders feature is not enabled,  dstStageMask must not contain %VK_PIPELINE_STAGE_GEOMETRY_SHADER_BITIf the  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-tessellationShadertessellation shaders feature is not enabled,  srcStageMask must not contain 1VK_PIPELINE_STAGE_TESSELLATION_CONTROL_SHADER_BIT or 4VK_PIPELINE_STAGE_TESSELLATION_EVALUATION_SHADER_BITIf the  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-tessellationShadertessellation shaders feature is not enabled,  dstStageMask must not contain 1VK_PIPELINE_STAGE_TESSELLATION_CONTROL_SHADER_BIT or 4VK_PIPELINE_STAGE_TESSELLATION_EVALUATION_SHADER_BIT srcSubpass must be less than or equal to  dstSubpass, unless one of them is VK_SUBPASS_EXTERNALF, to avoid cyclic dependencies and ensure a valid execution order srcSubpass and  dstSubpass must not both be equal to VK_SUBPASS_EXTERNALIf  srcSubpass is equal to  dstSubpass,  srcStageMask and  dstStageMask must only contain one of !VK_PIPELINE_STAGE_TOP_OF_PIPE_BIT, #VK_PIPELINE_STAGE_DRAW_INDIRECT_BIT, "VK_PIPELINE_STAGE_VERTEX_INPUT_BIT, #VK_PIPELINE_STAGE_VERTEX_SHADER_BIT, 1VK_PIPELINE_STAGE_TESSELLATION_CONTROL_SHADER_BIT, 4VK_PIPELINE_STAGE_TESSELLATION_EVALUATION_SHADER_BIT, %VK_PIPELINE_STAGE_GEOMETRY_SHADER_BIT, %VK_PIPELINE_STAGE_FRAGMENT_SHADER_BIT, *VK_PIPELINE_STAGE_EARLY_FRAGMENT_TESTS_BIT, )VK_PIPELINE_STAGE_LATE_FRAGMENT_TESTS_BIT, -VK_PIPELINE_STAGE_COLOR_ATTACHMENT_OUTPUT_BIT, $VK_PIPELINE_STAGE_BOTTOM_OF_PIPE_BIT , or "VK_PIPELINE_STAGE_ALL_GRAPHICS_BITIf  srcSubpass is equal to  dstSubpass# and not all of the stages in  srcStageMask and  dstStageMask are  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-framebuffer-regionsframebuffer-space stages , the  shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-orderlogically latest pipeline stage in  srcStageMask must be  shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-orderlogically earlier than or equal to the  shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-orderlogically earliest pipeline stage in  dstStageMaskAny access flag included in  srcAccessMask must4 be supported by one of the pipeline stages in  srcStageMask, as specified in the  thttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-access-types-supported$table of supported access types.Any access flag included in  dstAccessMask must4 be supported by one of the pipeline stages in  dstStageMask, as specified in the  thttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-access-types-supported$table of supported access types.If dependencyFlags includes VK_DEPENDENCY_VIEW_LOCAL_BIT, then both  srcSubpass and  dstSubpass must not equal VK_SUBPASS_EXTERNALIf dependencyFlags includes VK_DEPENDENCY_VIEW_LOCAL_BIT, then the render pass must have multiview enabledIf  srcSubpass equals  dstSubpassH and that subpass has more than one bit set in the view mask, then dependencyFlags must include VK_DEPENDENCY_VIEW_LOCAL_BITValid Usage (Implicit) srcStageMask must be a valid combination of @$ values srcStageMask must not be 0 dstStageMask must be a valid combination of @$ values dstStageMask must not be 0 srcAccessMask must be a valid combination of  values dstAccessMask must be a valid combination of  valuesdependencyFlags must be a valid combination of  valuesSee Also, , ,  srcSubpassB is the subpass index of the first subpass in the dependency, or VK_SUBPASS_EXTERNAL. dstSubpassC is the subpass index of the second subpass in the dependency, or VK_SUBPASS_EXTERNAL. srcStageMask is a bitmask of @$ specifying the  shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-maskssource stage mask. dstStageMask is a bitmask of @$ specifying the shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-masksdestination stage mask srcAccessMask is a bitmask of  specifying a  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-access-maskssource access mask. dstAccessMask is a bitmask of  specifying a  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-access-masksdestination access mask.dependencyFlags is a bitmask of .AVkSubpassDescription - Structure specifying a subpass description DescriptionaThe contents of an attachment within the render area become undefined at the start of a subpass S. if all of the following conditions are true:oThe attachment is used as a color, depth/stencil, or resolve attachment in any subpass in the render pass.There is a subpass S1K that uses or preserves the attachment, and a subpass dependency from S1 to S.3The attachment is not used or preserved in subpass S.?Once the contents of an attachment become undefined in subpass S[, they remain undefined for subpasses in subpass dependency chains starting with subpass S until they are written again. However, they remain valid for subpasses in other subpass dependency chains starting with subpass S13 if those subpasses use or preserve the attachment. Valid UsagepipelineBindPoint must be VK_PIPELINE_BIND_POINT_GRAPHICS colorAttachmentCount must be less than or equal to VkPhysicalDeviceLimits::maxColorAttachmentsIf the first use of an attachment in this render pass is as an input attachment, and the attachment is not also used as a color or depth/stencil attachment in the same subpass, then loadOp must not be VK_ATTACHMENT_LOAD_OP_CLEARIf pResolveAttachments is not NULL@, for each resolve attachment that does not have the value VK_ATTACHMENT_UNUSED*, the corresponding color attachment must not have the value VK_ATTACHMENT_UNUSEDIf pResolveAttachments is not NULL+, the sample count of each element of pColorAttachments must be anything other than VK_SAMPLE_COUNT_1_BITEach element of pResolveAttachments must have a sample count of VK_SAMPLE_COUNT_1_BITEach element of pResolveAttachments must have the same + as its corresponding color attachmentAll attachments in pColorAttachments that are not VK_ATTACHMENT_UNUSED must have the same sample countAll attachments in pColorAttachments that are not VK_ATTACHMENT_UNUSED mustO have a sample count that is smaller than or equal to the sample count of pDepthStencilAttachment if it is not VK_ATTACHMENT_UNUSEDIf any input attachments are VK_ATTACHMENT_UNUSED3, then any pipelines bound during the subpass mustA not access those input attachments from the fragment shaderThe  attachment member of each element of pPreserveAttachments must not be VK_ATTACHMENT_UNUSEDEach element of pPreserveAttachments mustK not also be an element of any other member of the subpass descriptionrIf any attachment is used as both an input attachment and a color or depth/stencil attachment, then each use must use the same layoutIf flags includes 7VK_SUBPASS_DESCRIPTION_PER_VIEW_POSITION_X_ONLY_BIT_NVX, it must also include 2VK_SUBPASS_DESCRIPTION_PER_VIEW_ATTRIBUTES_BIT_NVX.Valid Usage (Implicit)flags must be a valid combination of  valuespipelineBindPoint must be a valid  valueIf inputAttachmentCount is not 0, pInputAttachments must( be a valid pointer to an array of inputAttachmentCount valid VkAttachmentReference structuresIf colorAttachmentCount is not 0, pColorAttachments must( be a valid pointer to an array of colorAttachmentCount valid VkAttachmentReference structuresIf colorAttachmentCount is not 0, and pResolveAttachments is not NULL, pResolveAttachments must( be a valid pointer to an array of colorAttachmentCount valid VkAttachmentReference structuresIf pDepthStencilAttachment is not NULL, pDepthStencilAttachment must$ be a valid pointer to a valid VkAttachmentReference structureIf preserveAttachmentCount is not 0, pPreserveAttachments must# be a valid pointer to an array of preserveAttachmentCount uint32_t valuesSee Also, , , flags is a bitmask of " specifying usage of the subpass.pipelineBindPoint is a t value specifying whether this is a compute or graphics subpass. Currently, only graphics subpasses are supported.inputAttachmentCount$ is the number of input attachments.pInputAttachments is an array of O structures (defined below) that lists which of the render pass s attachments can be read in the fragment shader stage during the subpass, and what layout each attachment will be in during the subpass. Each element of the array corresponds to an input attachment unit number in the shader, i.e. if the shader declares an input variable 2layout(input_attachment_index=X, set=Y, binding=Z)* then it uses the attachment provided in pInputAttachments[X]. Input attachments must also be bound to the pipeline with a descriptor set, with the input attachment descriptor written in the location (set=Y, binding=Z). Fragment shaders can use subpass input variables to access the contents of an input attachment at the fragment s (x, y, layer) framebuffer coordinates.colorAttachmentCount$ is the number of color attachments.pColorAttachments is an array of colorAttachmentCount . structures that lists which of the render pass s attachments will be used as color attachments in the subpass, and what layout each attachment will be in during the subpass. Each element of the array corresponds to a fragment shader output location, i.e. if the shader declared an output variable layout(location=X)* then it uses the attachment provided in pColorAttachments[X].pResolveAttachments is NULL or an array of colorAttachmentCount  structures that lists which of the render pass s attachments are resolved to at the end of the subpass, and what layout each attachment will be in during the multisample resolve operation. If pResolveAttachments is not NULLJ, each of its elements corresponds to a color attachment (the element in pColorAttachmentsS at the same index), and a multisample resolve operation is defined for each attachment. At the end of each subpass, multisample resolve operations read the subpass s color attachments, and resolve the samples for each pixel to the same pixel location in the corresponding resolve attachments, unless the resolve attachment index is VK_ATTACHMENT_UNUSED[. If the first use of an attachment in a render pass is as a resolve attachment, then the loadOpb is effectively ignored as the resolve is guaranteed to overwrite all pixels in the render area.pDepthStencilAttachment is a pointer to a  specifying which attachment will be used for depth/stencil data and the layout it will be in during the subpass. Setting the attachment index to VK_ATTACHMENT_UNUSED or leaving this pointer as NULLI indicates that no depth/stencil attachment will be used in the subpass.preserveAttachmentCount( is the number of preserved attachments.pPreserveAttachments is an array of preserveAttachmentCountp render pass attachment indices describing the attachments that are not used by a subpass, but whose contents must& be preserved throughout the subpass.DVkAttachmentReference - Structure specifying an attachment reference Valid Usagelayout must not be VK_IMAGE_LAYOUT_UNDEFINED or VK_IMAGE_LAYOUT_PREINITIALIZEDValid Usage (Implicit)layout must be a valid  valueSee Also,  attachmentw is the index of the attachment of the render pass, and corresponds to the index of the corresponding element in the  pAttachments array of the VkRenderPassCreateInfo; structure. If any color or depth/stencil attachments are VK_ATTACHMENT_UNUSED., then no writes occur for those attachments.layout is a E value specifying the layout the attachment uses during the subpass.HVkAttachmentDescription - Structure specifying an attachment description Description,If the attachment uses a color format, then loadOp and storeOp are used, and  stencilLoadOp and stencilStoreOpB are ignored. If the format has depth and/or stencil components, loadOp and storeOp& apply only to the depth data, while  stencilLoadOp and stencilStoreOp* define how the stencil data is handled. loadOp and  stencilLoadOp define the load operationsF that execute as part of the first subpass that uses the attachment. storeOp and stencilStoreOp define the store operationsD that execute as part of the last subpass that uses the attachment.The load operation for each sample in an attachment happens-before any recorded command which accesses the sample in the first subpass where the attachment is used. Load operations for attachments with a depth/stencil format execute in the *VK_PIPELINE_STAGE_EARLY_FRAGMENT_TESTS_BITV pipeline stage. Load operations for attachments with a color format execute in the -VK_PIPELINE_STAGE_COLOR_ATTACHMENT_OUTPUT_BIT pipeline stage.The store operation for each sample in an attachment happens-after any recorded command which accesses the sample in the last subpass where the attachment is used. Store operations for attachments with a depth/stencil format execute in the )VK_PIPELINE_STAGE_LATE_FRAGMENT_TESTS_BITW pipeline stage. Store operations for attachments with a color format execute in the -VK_PIPELINE_STAGE_COLOR_ATTACHMENT_OUTPUT_BIT pipeline stage.2If an attachment is not used by any subpass, then loadOp, storeOp, stencilStoreOp, and  stencilLoadOpq are ignored, and the attachment s memory contents will not be modified by execution of a render pass instance.aThe load and store operations apply on the first and last use of each view in the render pass, respectively. If a view index of an attachment is not included in the view mask in any subpass that uses it, then the load and store operations are ignored, and the attachment s memory contents will not be modified by execution of a render pass instance.{During a render pass instance, input/color attachments with color formats that have a component size of 8, 16, or 32 bits must be represented in the attachment s format throughout the instance. Attachments with other floating- or fixed-point color formats, or with depth components mayU be represented in a format with a precision higher than the attachment format, but mustN be represented with the same range. When such a component is loaded via the loadOpj, it will be converted into an implementation-dependent format used by the render pass. Such components must be converted from the render pass format, to the format of the attachment, before they are resolved or stored at the end of a render pass instance via storeOp%. Conversions occur as described in  chttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-numerics'Numeric Representation and Computation and  dhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-fixedconvFixed-Point Data Conversions.If flags includes 'VK_ATTACHMENT_DESCRIPTION_MAY_ALIAS_BIT, then the attachment is treated as if it shares physical memory with another attachment in the same render pass. This information limits the ability of the implementation to reorder certain operations (like layout transitions and the loadOp) such that it is not improperly reordered against other uses of the same physical memory via a different attachment. This is described in more detail below. Valid Usage finalLayout must not be VK_IMAGE_LAYOUT_UNDEFINED or VK_IMAGE_LAYOUT_PREINITIALIZEDValid Usage (Implicit)flags must be a valid combination of  valuesformat must be a valid  valuesamples must be a valid  valueloadOp must be a valid   valuestoreOp must be a valid  value stencilLoadOp must be a valid   valuestencilStoreOp must be a valid  value initialLayout must be a valid  value finalLayout must be a valid  valueSee Also,  , , , , , flags is a bitmask of 5 specifying additional properties of the attachment.format is a P value specifying the format of the image that will be used for the attachment.samples6 is the number of samples of the image as defined in .loadOp is a   value specifying how the contents of color and depth components of the attachment are treated at the beginning of the subpass where it is first used.storeOp is a  value specifying how the contents of color and depth components of the attachment are treated at the end of the subpass where it is last used. stencilLoadOp is a   value specifying how the contents of stencil components of the attachment are treated at the beginning of the subpass where it is first used.stencilStoreOp is a  value specifying how the contents of stencil components of the attachment are treated at the end of the last subpass where it is used. initialLayout_ is the layout the attachment image subresource will be in when a render pass instance begins. finalLayout is the layout the attachment image subresource will be transitioned to when a render pass instance ends. During a render pass instance, an attachment can5 use a different layout in each subpass, if desired.5VkFramebuffer - Opaque handle to a framebuffer objectSee Also, , , 9Dummy data to tag the  with[VkDependencyFlagBits - Bitmask specifying how execution and memory dependencies are formedSee Also\VkAttachmentDescriptionFlagBits - Bitmask specifying additional properties of an attachmentSee AlsoDVkSubpassDescriptionFlagBits - Bitmask specifying usage of a subpassSee AlsogVkAccessFlagBits - Bitmask specifying memory access types that will participate in a memory dependency Description#VK_ACCESS_INDIRECT_COMMAND_READ_BITz specifies read access to an indirect command structure read as part of an indirect drawing or dispatch command.VK_ACCESS_INDEX_READ_BITd specifies read access to an index buffer as part of an indexed drawing command, bound by .#VK_ACCESS_VERTEX_ATTRIBUTE_READ_BIT[ specifies read access to a vertex buffer as part of a drawing command, bound by .VK_ACCESS_UNIFORM_READ_BIT specifies read access to a  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-uniformbufferuniform buffer.#VK_ACCESS_INPUT_ATTACHMENT_READ_BIT" specifies read access to an  Xhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#renderpassinput attachment3 within a render pass during fragment shading.VK_ACCESS_SHADER_READ_BIT specifies read access to a  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-storagebufferstorage buffer,  ohttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-uniformtexelbufferuniform texel buffer,  ohttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-storagetexelbufferstorage texel buffer,  ihttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-sampledimagesampled image , or  ihttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-storageimagestorage image.VK_ACCESS_SHADER_WRITE_BIT specifies write access to a  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-storagebufferstorage buffer,  ohttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-storagetexelbufferstorage texel buffer , or  ihttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-storageimagestorage image.#VK_ACCESS_COLOR_ATTACHMENT_READ_BIT! specifies read access to a  Xhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#renderpasscolor attachment, such as via  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#framebuffer-blendingblending,  ahttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#framebuffer-logicoplogic operations, or via certain  ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#renderpass-load-store-opssubpass load operations. It does not include  hhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#framebuffer-blend-advancedadvanced blend operations.3VK_ACCESS_COLOR_ATTACHMENT_READ_NONCOHERENT_BIT_EXT is similar to #VK_ACCESS_COLOR_ATTACHMENT_READ_BIT, but also includes  hhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#framebuffer-blend-advanced#advanced blend operations.$VK_ACCESS_COLOR_ATTACHMENT_WRITE_BIT" specifies write access to a  Xhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#renderpass color or resolve attachment during a  Xhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#renderpassrender pass or via certain  ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#renderpass-load-store-ops&subpass load and store operations.+VK_ACCESS_DEPTH_STENCIL_ATTACHMENT_READ_BIT! specifies read access to a  Xhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#renderpassdepth/stencil attachment , via  ^https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fragops-ds-state depth or stencil operations or via certain  ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#renderpass-load-store-opssubpass load operations.,VK_ACCESS_DEPTH_STENCIL_ATTACHMENT_WRITE_BIT" specifies write access to a  Xhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#renderpassdepth/stencil attachment , via  ^https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fragops-ds-state depth or stencil operations or via certain  ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#renderpass-load-store-ops&subpass load and store operations.VK_ACCESS_TRANSFER_READ_BIT< specifies read access to an image or buffer in a  Thttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#copiescopy operation.VK_ACCESS_TRANSFER_WRITE_BIT= specifies write access to an image or buffer in a  Thttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#clearsclear or  Thttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#copiescopy operation.VK_ACCESS_HOST_READ_BIT specifies read access by a host operation. Accesses of this type are not performed through a resource, but directly on memory.VK_ACCESS_HOST_WRITE_BIT specifies write access by a host operation. Accesses of this type are not performed through a resource, but directly on memory.VK_ACCESS_MEMORY_READ_BITs specifies read access via non-specific entities. These entities include the Vulkan device and host, but may also include entities external to the Vulkan device or otherwise not part of the core Vulkan pipeline. When included in a destination access mask, makes all available writes visible to all future read accesses on entities known to the Vulkan device.VK_ACCESS_MEMORY_WRITE_BITt specifies write access via non-specific entities. These entities include the Vulkan device and host, but may also include entities external to the Vulkan device or otherwise not part of the core Vulkan pipeline. When included in a source access mask, all writes that are performed by entities known to the Vulkan device are made available. When included in a destination access mask, makes all available writes visible to all future write accesses on entities known to the Vulkan device.&VK_ACCESS_COMMAND_PROCESS_READ_BIT_NVX specifies reads from VkBuffer inputs to .'VK_ACCESS_COMMAND_PROCESS_WRITE_BIT_NVX< specifies writes to the target command buffer in .Certain access types are only performed by a subset of pipeline stages. Any synchronization command that takes both stage masks and access masks uses both to define the  xhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-dependencies-access-scopesaccess scopesx - only the specified access types performed by the specified stages are included in the access scope. An application must not specify an access flag in a synchronization command if it does not include a pipeline stage in the corresponding stage mask that is able to perform accesses of that type. The following table lists, for each access flag, which pipeline stages can perform that type of access.7 Access flag 9 Supported pipeline stages  #VK_ACCESS_INDIRECT_COMMAND_READ_BIT  #VK_PIPELINE_STAGE_DRAW_INDIRECT_BIT  VK_ACCESS_INDEX_READ_BIT  "VK_PIPELINE_STAGE_VERTEX_INPUT_BIT  #VK_ACCESS_VERTEX_ATTRIBUTE_READ_BIT  "VK_PIPELINE_STAGE_VERTEX_INPUT_BIT  VK_ACCESS_UNIFORM_READ_BIT2  #VK_PIPELINE_STAGE_VERTEX_SHADER_BIT, 1VK_PIPELINE_STAGE_TESSELLATION_CONTROL_SHADER_BIT, 4VK_PIPELINE_STAGE_TESSELLATION_EVALUATION_SHADER_BIT, %VK_PIPELINE_STAGE_GEOMETRY_SHADER_BIT, %VK_PIPELINE_STAGE_FRAGMENT_SHADER_BIT, or $VK_PIPELINE_STAGE_COMPUTE_SHADER_BIT  #VK_ACCESS_INPUT_ATTACHMENT_READ_BIT  %VK_PIPELINE_STAGE_FRAGMENT_SHADER_BIT  VK_ACCESS_SHADER_READ_BIT3  #VK_PIPELINE_STAGE_VERTEX_SHADER_BIT, 1VK_PIPELINE_STAGE_TESSELLATION_CONTROL_SHADER_BIT, 4VK_PIPELINE_STAGE_TESSELLATION_EVALUATION_SHADER_BIT, %VK_PIPELINE_STAGE_GEOMETRY_SHADER_BIT, %VK_PIPELINE_STAGE_FRAGMENT_SHADER_BIT, or $VK_PIPELINE_STAGE_COMPUTE_SHADER_BIT  VK_ACCESS_SHADER_WRITE_BIT2  #VK_PIPELINE_STAGE_VERTEX_SHADER_BIT, 1VK_PIPELINE_STAGE_TESSELLATION_CONTROL_SHADER_BIT, 4VK_PIPELINE_STAGE_TESSELLATION_EVALUATION_SHADER_BIT, %VK_PIPELINE_STAGE_GEOMETRY_SHADER_BIT, %VK_PIPELINE_STAGE_FRAGMENT_SHADER_BIT, or $VK_PIPELINE_STAGE_COMPUTE_SHADER_BIT  #VK_ACCESS_COLOR_ATTACHMENT_READ_BIT  -VK_PIPELINE_STAGE_COLOR_ATTACHMENT_OUTPUT_BIT  3VK_ACCESS_COLOR_ATTACHMENT_READ_NONCOHERENT_BIT_EXT  -VK_PIPELINE_STAGE_COLOR_ATTACHMENT_OUTPUT_BIT  $VK_ACCESS_COLOR_ATTACHMENT_WRITE_BIT  -VK_PIPELINE_STAGE_COLOR_ATTACHMENT_OUTPUT_BIT  +VK_ACCESS_DEPTH_STENCIL_ATTACHMENT_READ_BITA  *VK_PIPELINE_STAGE_EARLY_FRAGMENT_TESTS_BIT, or )VK_PIPELINE_STAGE_LATE_FRAGMENT_TESTS_BIT  ,VK_ACCESS_DEPTH_STENCIL_ATTACHMENT_WRITE_BIT@  *VK_PIPELINE_STAGE_EARLY_FRAGMENT_TESTS_BIT, or )VK_PIPELINE_STAGE_LATE_FRAGMENT_TESTS_BIT  VK_ACCESS_TRANSFER_READ_BIT  VK_PIPELINE_STAGE_TRANSFER_BIT  VK_ACCESS_TRANSFER_WRITE_BIT  VK_PIPELINE_STAGE_TRANSFER_BIT  VK_ACCESS_HOST_READ_BIT  VK_PIPELINE_STAGE_HOST_BIT  VK_ACCESS_HOST_WRITE_BIT  VK_PIPELINE_STAGE_HOST_BIT  VK_ACCESS_MEMORY_READ_BIT 8 N/A  VK_ACCESS_MEMORY_WRITE_BIT 8 N/A  &VK_ACCESS_COMMAND_PROCESS_READ_BIT_NVX  )VK_PIPELINE_STAGE_COMMAND_PROCESS_BIT_NVX  'VK_ACCESS_COMMAND_PROCESS_WRITE_BIT_NVX  )VK_PIPELINE_STAGE_COMMAND_PROCESS_BIT_NVX Supported access types&If a memory object does not have the $VK_MEMORY_PROPERTY_HOST_COHERENT_BIT property, then fD mustj be called in order to guarantee that writes to the memory object from the host are made visible to the VK_ACCESS_HOST_WRITE_BIT  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-access-types access type , where it can- be further made available to the device by  ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronizationsynchronization commands. Similarly, fs must? be called to guarantee that writes which are visible to the VK_ACCESS_HOST_READ_BIT  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-access-types access type& are made visible to host operations.$If the memory object does have the $VK_MEMORY_PROPERTY_HOST_COHERENT_BITb property flag, writes to the memory object from the host are automatically made visible to the VK_ACCESS_HOST_WRITE_BIT  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-access-types access type). Similarly, writes made visible to the VK_ACCESS_HOST_READ_BIT  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-access-types access type- are automatically made visible to the host.NoteThe @% command  thttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-submission-host-writeseautomatically guarantees that host writes flushed to @VK_ACCESS_HOST_WRITE_BIT@ are made available if they were flushed before the command executed, so in most cases an explicit memory barrier is not needed for this case. In the few circumstances where a submit does not occur between the host write and the device read access, writes can8 be made available by using an explicit memory barrier.See Also1VkRenderPassCreateFlags - Reserved for future use DescriptionVkRenderPassCreateFlagsQ is a bitmask type for setting a mask, but is currently reserved for future use.See Also2VkFramebufferCreateFlags - Reserved for future use DescriptionVkFramebufferCreateFlagsQ is a bitmask type for setting a mask, but is currently reserved for future use.See AlsoVVkPipelineBindPoint - Specify the bind point of a pipeline object to a command bufferSee Also, =, , , , `VkAttachmentStoreOp - Specify how contents of an attachment are treated at the end of a subpassSee Also eVkAttachmentLoadOp - Specify how contents of an attachment are treated at the beginning of a subpassSee Also MvkGetRenderAreaGranularity - Returns the granularity for optimal render area Parametersdevice1 is the logical device that owns the render pass. renderPass is a handle to a render pass. pGranularity points to a 5 structure in which the granularity is returned. Description%The conditions leading to an optimal  renderArea are:the offset.x member in  renderArea is a multiple of the width member of the returned # (the horizontal granularity).the offset.y member in  renderArea is a multiple of the height of the returned ! (the vertical granularity). either the  offset.width member in  renderArea5 is a multiple of the horizontal granularity or offset.x+ offset.width is equal to the width of the  framebuffer in the . either the  offset.height member in  renderArea3 is a multiple of the vertical granularity or offset.y+ offset.height is equal to the height of the  framebuffer in the .Subpass dependencies are not affected by the render area, and apply to the entire image subresources attached to the framebuffer as specified in the description of  khttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#renderpass-layout-transitionsautomatic layout transitions`. Similarly, pipeline barriers are valid even if their effect extends outside the render area.Valid Usage (Implicit)device must be a valid VkDevice handle renderPass must be a valid  VkRenderPass handle pGranularity must be a valid pointer to a  VkExtent2D structure renderPass must6 have been created, allocated, or retrieved from deviceSee Also, ,  2vkDestroyRenderPass - Destroy a render pass object Parametersdevice5 is the logical device that destroys the render pass. renderPass- is the handle of the render pass to destroy. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. Valid Usage%All submitted commands that refer to  renderPass must have completed executionIf VkAllocationCallbacks were provided when  renderPass1 was created, a compatible set of callbacks must be provided hereIf no VkAllocationCallbacks were provided when  renderPass was created,  pAllocator must be NULLValid Usage (Implicit)device must be a valid VkDevice handleIf  renderPass is not ,  renderPass must be a valid  VkRenderPass handleIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structureIf  renderPass is a valid handle, it must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to  renderPass must be externally synchronizedSee Also, ,  4vkCreateRenderPass - Create a new render pass object Parametersdevice4 is the logical device that creates the render pass. pCreateInfo) is a pointer to an instance of the A structure that describes the parameters of the render pass. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. pRenderPass points to a  VkRenderPassC handle in which the resulting render pass object is returned.Valid Usage (Implicit)device must be a valid VkDevice handle pCreateInfo must$ be a valid pointer to a valid VkRenderPassCreateInfo structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structure pRenderPass must be a valid pointer to a  VkRenderPass handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, , , 3vkDestroyFramebuffer - Destroy a framebuffer object Parametersdevice5 is the logical device that destroys the framebuffer. framebuffer- is the handle of the framebuffer to destroy. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. Valid Usage%All submitted commands that refer to  framebuffer must have completed executionIf VkAllocationCallbacks were provided when  framebuffer1 was created, a compatible set of callbacks must be provided hereIf no VkAllocationCallbacks were provided when  framebuffer was created,  pAllocator must be NULLValid Usage (Implicit)device must be a valid VkDevice handleIf  framebuffer is not ,  framebuffer must be a valid  VkFramebuffer handleIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structureIf  framebuffer is a valid handle, it must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to  framebuffer must be externally synchronizedSee Also, , 5vkCreateFramebuffer - Create a new framebuffer object Parametersdevice4 is the logical device that creates the framebuffer. pCreateInfo points to a R structure which describes additional information about framebuffer creation. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. pFramebuffer points to a  VkFramebufferC handle in which the resulting framebuffer object is returned.Valid Usage (Implicit)device must be a valid VkDevice handle pCreateInfo must$ be a valid pointer to a valid VkFramebufferCreateInfo structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structure pFramebuffer must be a valid pointer to a  VkFramebuffer handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, , , VK_DEPENDENCY_BY_REGION_BIT& specifies that dependencies will be  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-framebuffer-regionsframebuffer-local.'VK_ATTACHMENT_DESCRIPTION_MAY_ALIAS_BITT specifies that the attachment aliases the same device memory as other attachments.#VK_PIPELINE_BIND_POINT_COMPUTE* specifies binding as a compute pipeline.$VK_PIPELINE_BIND_POINT_GRAPHICS+ specifies binding as a graphics pipeline.% VK_ATTACHMENT_STORE_OP_DONT_CARET specifies the contents within the render area are not needed after rendering, and may be discarded; the contents of the attachment will be undefined inside the render area. For attachments with a depth/stencil format, this uses the access type ,VK_ACCESS_DEPTH_STENCIL_ATTACHMENT_WRITE_BITC. For attachments with a color format, this uses the access type $VK_ACCESS_COLOR_ATTACHMENT_WRITE_BIT.&VK_ATTACHMENT_STORE_OP_STORE specifies the contents generated during the render pass and within the render area are written to memory. For attachments with a depth/stencil format, this uses the access type ,VK_ACCESS_DEPTH_STENCIL_ATTACHMENT_WRITE_BITC. For attachments with a color format, this uses the access type $VK_ACCESS_COLOR_ATTACHMENT_WRITE_BIT.'VK_ATTACHMENT_LOAD_OP_DONT_CARE specifies that the previous contents within the area need not be preserved; the contents of the attachment will be undefined inside the render area. For attachments with a depth/stencil format, this uses the access type ,VK_ACCESS_DEPTH_STENCIL_ATTACHMENT_WRITE_BITC. For attachments with a color format, this uses the access type $VK_ACCESS_COLOR_ATTACHMENT_WRITE_BIT.(VK_ATTACHMENT_LOAD_OP_CLEAR specifies that the contents within the render area will be cleared to a uniform value, which is specified when a render pass instance is begun. For attachments with a depth/stencil format, this uses the access type ,VK_ACCESS_DEPTH_STENCIL_ATTACHMENT_WRITE_BITC. For attachments with a color format, this uses the access type $VK_ACCESS_COLOR_ATTACHMENT_WRITE_BIT.)VK_ATTACHMENT_LOAD_OP_LOAD specifies that the previous contents of the image within the render area will be preserved. For attachments with a depth/stencil format, this uses the access type +VK_ACCESS_DEPTH_STENCIL_ATTACHMENT_READ_BITC. For attachments with a color format, this uses the access type #VK_ACCESS_COLOR_ATTACHMENT_READ_BIT.p      !"#$%&'()p  )('&%$#"!    None"bejkJAuVkPhysicalDeviceMultiviewPerViewAttributesPropertiesNVX - Structure describing multiview limits that can be supported by an implementationMembersThe members of the 7VkPhysicalDeviceMultiviewPerViewAttributesPropertiesNVXC structure describe the following implementation-dependent limits: DescriptionperViewPositionAllComponents is VK_TRUEx if the implementation supports per-view position values that differ in components other than the X component.Valid Usage (Implicit)sType must be NVK_STRUCTURE_TYPE_PHYSICAL_DEVICE_MULTIVIEW_PER_VIEW_ATTRIBUTES_PROPERTIES_NVXIf the 7VkPhysicalDeviceMultiviewPerViewAttributesPropertiesNVX structure is included in the pNext chain of sf9, it is filled with the implementation-dependent limits.See AlsoVkBool32, |7VK_SUBPASS_DESCRIPTION_PER_VIEW_POSITION_X_ONLY_BIT_NVX specifies that shaders compiled for this subpass use per-view positions which only differ in value in the x component. Per-view viewport mask can also be used.}2VK_SUBPASS_DESCRIPTION_PER_VIEW_ATTRIBUTES_BIT_NVX specifies that shaders compiled for this subpass write the attributes for all views in a single invocation of each vertex processing stage. All pipelines compiled against a subpass that includes this bit mustl write per-view attributes to the code:*PerViewNV[] shader outputs, in addition to the non-per-view (e.g. Position ) outputs. uvwxyz{|}~ ~}|{zuvwxyNone"KbejkJj wVkPipelineColorBlendAdvancedStateCreateInfoEXT - Structure specifying parameters that affect advanced blend operations Description"If this structure is not present, srcPremultiplied and dstPremultiplied are both considered to be VK_TRUE, and  blendOverlap is considered to be !VK_BLEND_OVERLAP_UNCORRELATED_EXT. Valid UsageIf the  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-limits-advancedBlendNonPremultipliedSrcColor#non-premultiplied source color! property is not supported, srcPremultiplied must be VK_TRUEIf the  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-limits-advancedBlendNonPremultipliedDstColor(non-premultiplied destination color! property is not supported, dstPremultiplied must be VK_TRUEIf the  |https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-limits-advancedBlendCorrelatedOverlapcorrelated overlap! property is not supported,  blendOverlap must be !VK_BLEND_OVERLAP_UNCORRELATED_EXTValid Usage (Implicit)sType must be EVK_STRUCTURE_TYPE_PIPELINE_COLOR_BLEND_ADVANCED_STATE_CREATE_INFO_EXT blendOverlap must be a valid  valueSee Also, VkBool32, sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.srcPremultipliedX specifies whether the source color of the blend operation is treated as premultiplied.dstPremultiplied] specifies whether the destination color of the blend operation is treated as premultiplied. blendOverlap is a R value specifying how the source and destination sample s coverage is correlated.VkPhysicalDeviceBlendOperationAdvancedPropertiesEXT - Structure describing advanced blending limits that can be supported by an implementationMembersThe members of the 3VkPhysicalDeviceBlendOperationAdvancedPropertiesEXTC structure describe the following implementation-dependent limits: Description advancedBlendMaxColorAttachmentsB is one greater than the highest color attachment index that can8 be used in a subpass, for a pipeline that uses an  hhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#framebuffer-blend-advancedadvanced blend operation.advancedBlendIndependentBlend2 specifies whether advanced blend operations can vary per-attachment.%advancedBlendNonPremultipliedSrcColor) specifies whether the source color can- be treated as non-premultiplied. If this is VK_FALSE, then ::srcPremultiplied must be VK_TRUE.%advancedBlendNonPremultipliedDstColor. specifies whether the destination color can2 be treated as non-premultiplied. If this is VK_FALSE , then ::dstPremultiplied must be VK_TRUE.advancedBlendCorrelatedOverlap) specifies whether the overlap mode can& be treated as correlated. If this is VK_FALSE , then :: blendOverlap must be !VK_BLEND_OVERLAP_UNCORRELATED_EXT.advancedBlendAllOperationsf specifies whether all advanced blend operation enums are supported. See the valid usage of H.Valid Usage (Implicit)sType must be IVK_STRUCTURE_TYPE_PHYSICAL_DEVICE_BLEND_OPERATION_ADVANCED_PROPERTIES_EXTIf the 3VkPhysicalDeviceBlendOperationAdvancedPropertiesEXT structure is included in the pNext chain of sf9, it is filled with the implementation-dependent limits.See AlsoVkBool32, VkPhysicalDeviceBlendOperationAdvancedFeaturesEXT - Structure describing advanced blending features that can be supported by an implementationMembersThe members of the 1VkPhysicalDeviceBlendOperationAdvancedFeaturesEXT, structure describe the following features: DescriptionadvancedBlendCoherentOperations' specifies whether blending using  hhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#framebuffer-blend-advancedadvanced blend operations1 is guaranteed to execute atomically and in  ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#drawing-primitive-orderprimitive order. If this is VK_TRUE, 3VK_ACCESS_COLOR_ATTACHMENT_READ_NONCOHERENT_BIT_EXT is treated the same as #VK_ACCESS_COLOR_ATTACHMENT_READ_BITf, and advanced blending needs no additional synchronization over basic blending. If this is VK_FALSE, then memory dependencies are required to guarantee order between two advanced blending operations that occur on the same sample.If the 1VkPhysicalDeviceBlendOperationAdvancedFeaturesEXT structure is included in the pNext chain of s\K, it is filled with values indicating whether each feature is supported. 1VkPhysicalDeviceBlendOperationAdvancedFeaturesEXT can also be used in pNext chain of ~ to enable the features.Valid Usage (Implicit)sType must be GVK_STRUCTURE_TYPE_PHYSICAL_DEVICE_BLEND_OPERATION_ADVANCED_FEATURES_EXTSee AlsoVkBool32, DVkBlendOverlapEXT - Enumerant specifying the blend overlap parameter Description!VK_BLEND_OVERLAP_UNCORRELATED_EXTY specifies that there is no correlation between the source and destination coverage.VK_BLEND_OVERLAP_CONJOINT_EXT` specifies that the source and destination coverage are considered to have maximal overlap.VK_BLEND_OVERLAP_DISJOINT_EXT` specifies that the source and destination coverage are considered to have minimal overlap.% Overlap Mode V Weighting Equations  !VK_BLEND_OVERLAP_UNCORRELATED_EXT   \begin{aligned} p_0(A_s,A_d) & = A_sA_d \\ p_1(A_s,A_d) & = A_s(1-A_d) \\ p_2(A_s,A_d) & = A_d(1-A_s) \\ \end{aligned}  VK_BLEND_OVERLAP_CONJOINT_EXT   \begin{aligned} p_0(A_s,A_d) & = min(A_s,A_d) \\ p_1(A_s,A_d) & = max(A_s-A_d,0) \\ p_2(A_s,A_d) & = max(A_d-A_s,0) \\ \end{aligned}  VK_BLEND_OVERLAP_DISJOINT_EXT   \begin{aligned} p_0(A_s,A_d) & = max(A_s+A_d-1,0) \\ p_1(A_s,A_d) & = min(A_s,1-A_d) \\ p_2(A_s,A_d) & = min(A_d,1-A_s) \\ \end{aligned} Advanced Blend Overlap ModesSee AlsoOONone"bejkKW XVkRenderPassMultiviewCreateInfo - Structure containing multiview info for all subpasses Description*When a subpass uses a non-zero view mask,  multiview| functionality is considered to be enabled. Multiview is all-or-nothing for a render pass - that is, either all subpasses must3 have a non-zero view mask (though some subpasses may have only one view) or all must be zero. Multiview causes all drawing and clear commands in the subpass to behave as if they were broadcast to each view, where a view is represented by one layer of the framebuffer attachments. All draws and clears are broadcast to each  view indexG whose bit is set in the view mask. The view index is provided in the  ViewIndex shader input variable, and color, depth/stencil, and input attachments all read/write the layer of the framebuffer corresponding to the view index.If the view mask is zero for all subpasses, multiview is considered to be disabled and all drawing commands execute normally, without this additional broadcasting.Some implementations may, not support multiview in conjunction with  lhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-multiview-gsgeometry shaders or  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-multiview-tesstessellation shaders.When multiview is enabled, the VK_DEPENDENCY_VIEW_LOCAL_BIT bit in a dependency can be used to express a view-local dependency, meaning that each view in the destination subpass depends on a single view in the source subpass. Unlike pipeline barriers, a subpass dependency canZ potentially have a different view mask in the source subpass and the destination subpass. If the dependency is view-local, then each view (dstView) in the destination subpass depends on the view dstView + pViewOffsets[dependency] in the source subpass. If there is not such a view in the source subpass, then this dependency does not affect that view in the destination subpass. If the dependency is not view-local, then all views in the destination subpass depend on all views in the source subpass, and the view offset is ignored. A non-zero view offset is not allowed in a self-dependency.The elements of pCorrelationMasksE are a set of masks of views indicating that views in the same mask mayx exhibit spatial coherency between the views, making it more efficient to render them concurrently. Correlation masks mustI not have a functional effect on the results of the multiview rendering.When multiview is enabled, at the beginning of each subpass all non-render pass state is undefined. In particular, each time  or " is called the graphics pipeline mustA be bound, any relevant descriptor sets or vertex/index buffers must= be bound, and any relevant dynamic state or push constants must be set before they are used.A multiview subpass canp declare that its shaders will write per-view attributes for all views in a single invocation, by setting the 2VK_SUBPASS_DESCRIPTION_PER_VIEW_ATTRIBUTES_BIT_NVX bit in the subpass description. The only supported per-view attributes are position and viewport mask, and per-view position and viewport masks are written to output array variables decorated with PositionPerViewNV and ViewportMaskPerViewNV, respectively. If *{html_spec_relative}#VK_NV_viewport_array2 is not supported and enabled, ViewportMaskPerViewNV must- not be used. Values written to elements of PositionPerViewNV and ViewportMaskPerViewNV must not depend on the  ViewIndex . The shader must2 also write to an output variable decorated with Position, and the value written to Position must equal the value written to PositionPerViewNV[ ViewIndex]. Similarly, if ViewportMaskPerViewNV is written to then the shader must1 also write to an output variable decorated with ViewportMaskNV, and the value written to ViewportMaskNV must equal the value written to ViewportMaskPerViewNV[ ViewIndex6]. Implementations will either use values taken from Position and ViewportMaskNVJ and invoke the shader once for each view, or will use values taken from PositionPerViewNV and ViewportMaskPerViewNV; and invoke the shader fewer times. The values written to Position and ViewportMaskNV must& not depend on the values written to PositionPerViewNV and ViewportMaskPerViewNV, or vice versa (to allow compilers to eliminate the unused outputs). All attributes that do not have *PerViewNV counterparts must not depend on  ViewIndex.|Per-view attributes are all-or-nothing for a subpass. That is, all pipelines compiled against a subpass that includes the 2VK_SUBPASS_DESCRIPTION_PER_VIEW_ATTRIBUTES_BIT_NVX bit mustg write per-view attributes to the *PerViewNV[] shader outputs, in addition to the non-per-view (e.g. PositionP) outputs. Pipelines compiled against a subpass that does not include this bit must; not include the *PerViewNV[] outputs in their interfaces. Valid UsageIf  subpassCount is not zero,  subpassCount must be equal to the  subpassCount in the VkRenderPassCreateInfo) structure at the start of the chainIf dependencyCount is not zero, dependencyCount must be equal to the dependencyCount in the VkRenderPassCreateInfo) structure at the start of the chainEach view index must- not be set in more than one element of pCorrelationMasksIf an element of  pViewOffsets% is non-zero, the corresponding  structure must have different values of  srcSubpass and  dstSubpass.Valid Usage (Implicit)sType must be 3VK_STRUCTURE_TYPE_RENDER_PASS_MULTIVIEW_CREATE_INFOIf  subpassCount is not 0,  pViewMasks must( be a valid pointer to an array of  subpassCount uint32_t valuesIf dependencyCount is not 0,  pViewOffsets must( be a valid pointer to an array of dependencyCount int32_t valuesIf correlationMaskCount is not 0, pCorrelationMasks must( be a valid pointer to an array of correlationMaskCount uint32_t valuesSee AlsosType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure. subpassCount: is zero or is the number of subpasses in the render pass. pViewMasks points to an array of  subpassCount number of view masks, where each mask is a bitfield of view indices describing which views rendering is broadcast to in each subpass, when multiview is enabled. If  subpassCount, is zero, each view mask is treated as zero.dependencyCount; is zero or the number of dependencies in the render pass. pViewOffsets points to an array of dependencyCount, view offsets, one for each dependency. If dependencyCount is zero, each dependency s view offset is treated as zero. Each view offset controls which views in the source subpass the views in the destination subpass depend on.correlationMaskCount* is zero or a number of correlation masks.pCorrelationMasks: is an array of view masks indicating sets of views that may* be more efficient to render concurrently.wVkPhysicalDeviceMultiviewProperties - Structure describing multiview limits that can be supported by an implementationMembersThe members of the #VkPhysicalDeviceMultiviewPropertiesC structure describe the following implementation-dependent limits: DescriptionmaxMultiviewViewCount6 is one greater than the maximum view index that can be used in a subpass.maxMultiviewInstanceIndex is the maximum valid value of instance index allowed to be generated by a drawing command recorded within a subpass of a multiview render pass instance.Valid Usage (Implicit)sType must be 6VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_MULTIVIEW_PROPERTIESIf the #VkPhysicalDeviceMultiviewProperties structure is included in the pNext chain of sf9, it is filled with the implementation-dependent limits.See AlsowVkPhysicalDeviceMultiviewFeatures - Structure describing multiview features that can be supported by an implementationMembersThe members of the !VkPhysicalDeviceMultiviewFeatures, structure describe the following features: Description multiview specifies whether the implementation supports multiview rendering within a render pass. If this feature is not enabled, the view mask of each subpass must always be zero.multiviewGeometryShaderc specifies whether the implementation supports multiview rendering within a render pass, with  Vhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#geometrygeometry shadersq. If this feature is not enabled, then a pipeline compiled against a subpass with a non-zero view mask must$ not include a geometry shader.multiviewTessellationShaderh specifies whether the implementation supports multiview rendering within a render pass, with  Zhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#tessellationtessellation shadersq. If this feature is not enabled, then a pipeline compiled against a subpass with a non-zero view mask must+ not include any tessellation shaders.If the !VkPhysicalDeviceMultiviewFeatures structure is included in the pNext chain of s\K, it is filled with values indicating whether each feature is supported. !VkPhysicalDeviceMultiviewFeatures can also be used in the pNext chain of ~ to enable the features. Valid UsageIf multiviewGeometryShader is enabled then  multiview must also be enabled.If multiviewTessellationShader is enabled then  multiview must also be enabled.Valid Usage (Implicit)sType must be 4VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_MULTIVIEW_FEATURESSee AlsoVkBool32, VK_DEPENDENCY_VIEW_LOCAL_BIT specifies that a  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-barriers-subpass-self-dependencies subpass has more than one view.None-STejkKY            None "-KSTbejkL&;VkMemoryAllocateFlags - Bitmask of VkMemoryAllocateFlagBits DescriptionVkMemoryAllocateFlags7 is a bitmask type for setting a mask of zero or more 3.See Also3, -AVkPeerMemoryFeatureFlags - Bitmask of VkPeerMemoryFeatureFlagBits DescriptionVkPeerMemoryFeatureFlags7 is a bitmask type for setting a mask of zero or more 5.See Also5, 9, NMVkDeviceGroupBindSparseInfo - Structure indicating which instances are bound DescriptionThese device indices apply to all buffer and image memory binds included in the batch that points to this structure. The semaphore waits and signals for the batch are executed only by the physical device specified by the resourceDeviceIndex."If this structure is not present, resourceDeviceIndex and memoryDeviceIndex are assumed to be zero. Valid UsageresourceDeviceIndex and memoryDeviceIndex must# both be valid device indices.+Each memory allocation bound in this batch must% have allocated an instance for memoryDeviceIndex.Valid Usage (Implicit)sType must be /VK_STRUCTURE_TYPE_DEVICE_GROUP_BIND_SPARSE_INFOSee AlsosType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.resourceDeviceIndexG is a device index indicating which instance of the resource is bound.memoryDeviceIndex^ is a device index indicating which instance of the memory the resource instance is bound to.wVkDeviceGroupSubmitInfo - Structure indicating which physical devices execute semaphore operations and command buffers DescriptioniIf this structure is not present, semaphore operations and command buffers execute on device index zero. Valid UsagewaitSemaphoreCount must equal @::waitSemaphoreCountcommandBufferCount must equal @::commandBufferCountsignalSemaphoreCount must equal @::signalSemaphoreCountAll elements of pWaitSemaphoreDeviceIndices and pSignalSemaphoreDeviceIndices must be valid device indicesAll elements of pCommandBufferDeviceMasks must be valid device masksValid Usage (Implicit)sType must be *VK_STRUCTURE_TYPE_DEVICE_GROUP_SUBMIT_INFOIf waitSemaphoreCount is not 0, pWaitSemaphoreDeviceIndices must# be a valid pointer to an array of waitSemaphoreCount uint32_t valuesIf commandBufferCount is not 0, pCommandBufferDeviceMasks must# be a valid pointer to an array of commandBufferCount uint32_t valuesIf signalSemaphoreCount is not 0, pSignalSemaphoreDeviceIndices must( be a valid pointer to an array of signalSemaphoreCount uint32_t valuesSee AlsosType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.waitSemaphoreCount# is the number of elements in the pWaitSemaphoreDeviceIndices array.pWaitSemaphoreDeviceIndices is an array of device indices indicating which physical device executes the semaphore wait operation in the corresponding element of @::pWaitSemaphores.commandBufferCount# is the number of elements in the pCommandBufferDeviceMasks array.pCommandBufferDeviceMasks| is an array of device masks indicating which physical devices execute the command buffer in the corresponding element of @::pCommandBuffers^. A physical device executes the command buffer if the corresponding bit is set in the mask.signalSemaphoreCount# is the number of elements in the pSignalSemaphoreDeviceIndices array. pSignalSemaphoreDeviceIndices is an array of device indices indicating which physical device executes the semaphore signal operation in the corresponding element of @::pSignalSemaphores.!WVkDeviceGroupCommandBufferBeginInfo - Set the initial device mask for a command buffer DescriptionPThe initial device mask also acts as an upper bound on the set of devices that can2 ever be in the device mask in the command buffer.If this structure is not present, the initial value of a command buffer s device mask is set to include all physical devices in the logical device when the command buffer begins recording. Valid Usage deviceMask must be a valid device mask value deviceMask must not be zeroValid Usage (Implicit)sType must be 8VK_STRUCTURE_TYPE_DEVICE_GROUP_COMMAND_BUFFER_BEGIN_INFOSee Also#sType is the type of this structure.$pNext is NULL1 or a pointer to an extension-specific structure.% deviceMask: is the initial value of the command buffer s device mask.&kVkDeviceGroupRenderPassBeginInfo - Set the initial device mask and render areas for a render pass instance DescriptionThe  deviceMaskT serves several purposes. It is an upper bound on the set of physical devices that can2 be used during the render pass instance, and the initial device mask when the render pass instance begins. Render pass attachment load, store, and resolve operations only apply to physical devices included in the device mask. Subpass dependencies only apply to the physical devices in the device mask.If deviceRenderAreaCount$ is not zero, then the elements of pDeviceRenderAreas override the value of :: renderArean, and provide a render area specific to each physical device. These render areas serve the same purpose as :: renderAreaH, including controlling the region of attachments that are cleared by VK_ATTACHMENT_LOAD_OP_CLEAR1 and that are resolved into resolve attachments.ZIf this structure is not present, the render pass instance s device mask is the value of !:: deviceMask*. If this structure is not present or if deviceRenderAreaCount is zero, :: renderArea# is used for all physical devices. Valid Usage deviceMask must be a valid device mask value deviceMask must not be zero deviceMask must= be a subset of the command buffer s initial device maskdeviceRenderAreaCount mustV either be zero or equal to the number of physical devices in the logical device.Valid Usage (Implicit)sType must be 5VK_STRUCTURE_TYPE_DEVICE_GROUP_RENDER_PASS_BEGIN_INFOIf deviceRenderAreaCount is not 0, pDeviceRenderAreas must( be a valid pointer to an array of deviceRenderAreaCount VkRect2D structuresSee Also, (sType is the type of this structure.)pNext is NULL1 or a pointer to an extension-specific structure.* deviceMask1 is the device mask for the render pass instance.+deviceRenderAreaCount# is the number of elements in the pDeviceRenderAreas array.,pDeviceRenderAreas$ is an array of structures of type 4 defining the render area for each physical device.-aVkMemoryAllocateFlagsInfo - Structure controlling how many instances of memory will be allocated DescriptionIf "VK_MEMORY_ALLOCATE_DEVICE_MASK_BITD is not set, the number of instances allocated depends on whether !VK_MEMORY_HEAP_MULTI_INSTANCE_BIT is set in the memory heap. If !VK_MEMORY_HEAP_MULTI_INSTANCE_BITZ is set, then memory is allocated for every physical device in the logical device (as if  deviceMask+ has bits set for all device indices). If !VK_MEMORY_HEAP_MULTI_INSTANCE_BITD is not set, then a single instance of memory is allocated (as if  deviceMask is set to one).@On some implementations, allocations from a multi-instance heap may5 consume memory on all physical devices even if the  deviceMask excludes some devices. If =]::subsetAllocation is VK_TRUEC, then memory is only consumed for the devices in the device mask.NoteIn practice, most allocations on a multi-instance heap will be allocated across all physical devices. Unicast allocation support is an optional optimization for a minority of allocations. Valid UsageIf "VK_MEMORY_ALLOCATE_DEVICE_MASK_BIT is set,  deviceMask must be a valid device mask.If "VK_MEMORY_ALLOCATE_DEVICE_MASK_BIT is set,  deviceMask must not be zeroValid Usage (Implicit)sType must be ,VK_STRUCTURE_TYPE_MEMORY_ALLOCATE_FLAGS_INFOflags must be a valid combination of 3 valuesSee Also, /sType is the type of this structure.0pNext is NULL1 or a pointer to an extension-specific structure.1flags is a bitmask of 3 controlling the allocation.2 deviceMaskN is a mask of physical devices in the logical device, indicating that memory must. be allocated on each device in the mask, if "VK_MEMORY_ALLOCATE_DEVICE_MASK_BIT is set in flags.3SVkMemoryAllocateFlagBits - Bitmask specifying flags for a device memory allocationSee Also5PVkPeerMemoryFeatureFlagBits - Bitmask specifying supported peer memory features Description#VK_PEER_MEMORY_FEATURE_COPY_SRC_BIT specifies that the memory can be accessed as the source of a vkCmdCopyBuffer, vkCmdCopyImage, vkCmdCopyBufferToImage , or vkCmdCopyImageToBuffer command.#VK_PEER_MEMORY_FEATURE_COPY_DST_BIT specifies that the memory can% be accessed as the destination of a vkCmdCopyBuffer, vkCmdCopyImage, vkCmdCopyBufferToImage , or vkCmdCopyImageToBuffer command.&VK_PEER_MEMORY_FEATURE_GENERIC_SRC_BIT specifies that the memory can# be read as any memory access type.&VK_PEER_MEMORY_FEATURE_GENERIC_DST_BIT specifies that the memory canW be written as any memory access type. Shader atomics are considered to be writes.NoteKThe peer memory features of a memory heap also apply to any accesses that may be performed during  vhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-image-layout-transitionsimage layout transitions.#VK_PEER_MEMORY_FEATURE_COPY_DST_BIT mustO be supported for all host local heaps and for at least one device local heap.If a device does not support a peer memory feature, it is still valid to use a resource that includes both local and peer memory bindings with the corresponding access type as long as only the local bindings are actually accessed. For example, an application doing split-frame rendering would use framebuffer attachments that include both local and peer memory bindings, but would scissor the rendering to only update local memory.See Also7/vkCmdDispatchBase - Dispatch compute work items Parameters commandBufferD is the command buffer into which the command will be recorded. baseGroupX0 is the start value for the X component of  WorkgroupId. baseGroupY0 is the start value for the Y component of  WorkgroupId. baseGroupZ0 is the start value for the Z component of  WorkgroupId. groupCountXG is the number of local workgroups to dispatch in the X dimension. groupCountYG is the number of local workgroups to dispatch in the Y dimension. groupCountZG is the number of local workgroups to dispatch in the Z dimension. DescriptionWhen the command is executed, a global workgroup consisting of groupCountX groupCountY groupCountZ local workgroups is assembled, with  WorkgroupIdN values ranging from [baseGroup, baseGroup + groupCount) in each component. Q is equivalent to vkCmdDispatchBase(0,0,0,groupCountX,groupCountY,groupCountZ). Valid Usage All valid usage rules from  apply baseGroupX must be less than VkPhysicalDeviceLimits::maxComputeWorkGroupCount[0] baseGroupX must be less than VkPhysicalDeviceLimits::maxComputeWorkGroupCount[1] baseGroupZ must be less than VkPhysicalDeviceLimits::maxComputeWorkGroupCount[2] groupCountX must be less than or equal to VkPhysicalDeviceLimits::maxComputeWorkGroupCount[0] minus  baseGroupX groupCountY must be less than or equal to VkPhysicalDeviceLimits::maxComputeWorkGroupCount[1] minus  baseGroupY groupCountZ must be less than or equal to VkPhysicalDeviceLimits::maxComputeWorkGroupCount[2] minus  baseGroupZ If any of  baseGroupX,  baseGroupY, or  baseGroupZ4 are not zero, then the bound compute pipeline must! have been created with the  VK_PIPELINE_CREATE_DISPATCH_BASE flag.Valid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must support compute operations This command must1 only be called outside of a render pass instanceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Outside  Compute  See Also8;vkCmdSetDeviceMask - Modify device mask of a command buffer Parameters commandBuffer> is command buffer whose current device mask is modified. deviceMask- is the new value of the current device mask. Description deviceMask} is used to filter out subsequent commands from executing on all physical devices whose bit indices are not set in the mask. Valid Usage deviceMask must be a valid device mask value deviceMask must not be zero deviceMask must4 not include any set bits that were not in the !:: deviceMask4 value when the command buffer began recording.If vkCmdSetDeviceMask/ is called inside a render pass instance,  deviceMask must4 not include any set bits that were not in the &:: deviceMask: value when the render pass instance began recording.Valid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must7 support graphics, compute, or transfer operationsHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type I Primary Secondary F Both 7 Graphics Compute Transfer v See Also9VvkGetDeviceGroupPeerMemoryFeatures - Query supported peer memory features of a device Parametersdevice, is the logical device that owns the memory. heapIndexI is the index of the memory heap from which the memory is allocated.localDeviceIndexQ is the device index of the physical device that performs the memory access.remoteDeviceIndexR is the device index of the physical device that the memory is allocated for.pPeerMemoryFeatures# is a pointer to a bitmask of 5z indicating which types of memory accesses are supported for the combination of heap, local, and remote devices. Valid Usage heapIndex must be less than memoryHeapCountlocalDeviceIndex must be a valid device indexremoteDeviceIndex must be a valid device indexlocalDeviceIndex must not equal remoteDeviceIndexValid Usage (Implicit)device must be a valid VkDevice handlepPeerMemoryFeatures must be a valid pointer to a  valuepPeerMemoryFeatures must not be 0See Also, :VK_DEPENDENCY_DEVICE_GROUP_BIT" specifies that dependencies are  whttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-device-local-dependenciesnon-device-local dependency.B"VK_MEMORY_ALLOCATE_DEVICE_MASK_BIT= specifies that memory will be allocated for the devices in -:: deviceMask.8 !"#$%&'()*+,-./0123456789:;<=>?@ABCDEF856FEDC34BA@?>=<;:987-./012&'()*+,!"#$% None-STejkL'defghijklmnopqrstuvwxyz{|}~'nmlkjihgfed~}|{zyxwvutsrqpoNone "-KSTbejkMCVkCommandBufferUsageFlags - Bitmask of VkCommandBufferUsageFlagBits DescriptionVkCommandBufferUsageFlags7 is a bitmask type for setting a mask of zero or more .See Also, CVkCommandBufferResetFlags - Bitmask of VkCommandBufferResetFlagBits DescriptionVkCommandBufferResetFlags7 is a bitmask type for setting a mask of zero or more .See Also, 7VkQueryControlFlags - Bitmask of VkQueryControlFlagBits DescriptionVkQueryControlFlags7 is a bitmask type for setting a mask of zero or more .See Also, , QVkCommandBufferBeginInfo - Structure specifying a command buffer begin operation Valid UsageIf flags contains 0VK_COMMAND_BUFFER_USAGE_RENDER_PASS_CONTINUE_BIT, the  renderPass member of pInheritanceInfo must be a valid  VkRenderPassIf flags contains 0VK_COMMAND_BUFFER_USAGE_RENDER_PASS_CONTINUE_BIT, the subpass member of pInheritanceInfo must* be a valid subpass index within the  renderPass member of pInheritanceInfoIf flags contains 0VK_COMMAND_BUFFER_USAGE_RENDER_PASS_CONTINUE_BIT , the  framebuffer member of pInheritanceInfo must be either , or a valid  VkFramebuffer that is compatible with the  renderPass member of pInheritanceInfoValid Usage (Implicit)sType must be +VK_STRUCTURE_TYPE_COMMAND_BUFFER_BEGIN_INFOpNext must be NULL* or a pointer to a valid instance of flags must be a valid combination of  valuesSee Also, , , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.flags is a bitmask of 3 specifying usage behavior for the command buffer.pInheritanceInfo is a pointer to a VkCommandBufferInheritanceInfo structure, which is used if  commandBuffera is a secondary command buffer. If this is a primary command buffer, then this value is ignored.VVkCommandBufferInheritanceInfo - Structure specifying command buffer inheritance infoMemberssType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure. renderPass is a  VkRenderPass. object defining which render passes the VkCommandBuffer will be  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#renderpass-compatibility compatible with and can be executed within. If the VkCommandBuffer: will not be executed within a render pass instance,  renderPass is ignored.subpassK is the index of the subpass within the render pass instance that the VkCommandBuffer& will be executed within. If the VkCommandBuffer: will not be executed within a render pass instance, subpass is ignored. framebuffer optionally refers to the  VkFramebuffer object that the VkCommandBufferO will be rendering to if it is executed within a render pass instance. It can be 1 if the framebuffer is not known, or if the VkCommandBuffer9 will not be executed within a render pass instance.NoteYSpecifying the exact framebuffer that the secondary command buffer will be executed with may? result in better performance at command buffer execution time.occlusionQueryEnable& specifies whether the command buffer cand be executed while an occlusion query is active in the primary command buffer. If this is VK_TRUE, then this command buffer cank be executed whether the primary command buffer has an occlusion query active or not. If this is VK_FALSE', then the primary command buffer must$ not have an occlusion query active. queryFlags specifies the query flags that can be used by an active occlusion query in the primary command buffer when this secondary command buffer is executed. If this value includes the VK_QUERY_CONTROL_PRECISE_BIT bit, then the active query cani return boolean results or actual sample counts. If this bit is not set, then the active query must not use the VK_QUERY_CONTROL_PRECISE_BIT bit.pipelineStatistics is a bitmask of F5 specifying the set of pipeline statistics that can be counted by an active query in the primary command buffer when this secondary command buffer is executed. If this value includes a given bit, then this command buffer can be executed whether the primary command buffer has a pipeline statistics query active that includes this bit or not. If this value excludes a given bit, then the active pipeline statistics query must: not be from a query pool that counts that statistic. Valid UsageIf the  phttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-inheritedQueriesinherited queries feature is not enabled, occlusionQueryEnable must be VK_FALSEIf the  phttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-inheritedQueriesinherited queries feature is enabled,  queryFlags must be a valid combination of  valuesIf the  whttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-pipelineStatisticsQuery pipeline statistics queries feature is not enabled, pipelineStatistics must be 0Valid Usage (Implicit)sType must be 1VK_STRUCTURE_TYPE_COMMAND_BUFFER_INHERITANCE_INFOpNext must be NULLBoth of  framebuffer, and  renderPass that are valid handles must? have been created, allocated, or retrieved from the same VkDeviceSee AlsoVkBool32, , , , , , gVkCommandBufferAllocateInfo - Structure specifying the allocation parameters for command buffer object Valid UsagecommandBufferCount must be greater than 0Valid Usage (Implicit)sType must be .VK_STRUCTURE_TYPE_COMMAND_BUFFER_ALLOCATE_INFOpNext must be NULL commandPool must be a valid  VkCommandPool handlelevel must be a valid  valueSee Also, , , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure. commandPoolC is the command pool from which the command buffers are allocated.level is an , value specifying the command buffer level.commandBufferCount= is the number of command buffers to allocate from the pool.TVkCommandBufferUsageFlagBits - Bitmask specifying usage behavior for command bufferSee AlsoVVkCommandBufferResetFlagBits - Bitmask controlling behavior of a command buffer resetSee AlsoBVkQueryControlFlagBits - Bitmask specifying constraints on a querySee AlsoBVkCommandBufferLevel - Enumerant specifying a command buffer levelSee AlsoBvkResetCommandBuffer - Reset a command buffer to the initial state Parameters commandBuffer9 is the command buffer to reset. The command buffer can! be in any state other than  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclepending, and is moved into the  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecycleinitial state.flags is a bitmask of & controlling the reset operation. Description*Any primary command buffer that is in the  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording or executable state and has  commandBuffer recorded into it, becomes  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecycleinvalid. Valid Usage commandBuffer must not be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclepending state commandBuffer must@ have been allocated from a pool that was created with the /VK_COMMAND_POOL_CREATE_RESET_COMMAND_BUFFER_BITValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handleflags must be a valid combination of  valuesHost SynchronizationHost access to  commandBuffer must be externally synchronized Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, 6vkEndCommandBuffer - Finish recording a command buffer Parameters commandBuffer- is the command buffer to complete recording. DescriptionuIf there was an error during recording, the application will be notified by an unsuccessful return code returned by vkEndCommandBufferT. If the application wishes to further use the command buffer, the command buffer must be reset. The command buffer must have been in the  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording state, and is moved to the  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecycleexecutable state. Valid Usage commandBuffer must be in the  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording state.If  commandBuffer$ is a primary command buffer, there must+ not be an active render pass instanceAll queries made  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#queries-operation-activeactive during the recording of  commandBuffer must have been made inactiveIf  commandBuffer& is a secondary command buffer, there must! not be an outstanding C command recorded to  commandBuffer; that has not previously been ended by a call to C.If  commandBuffer& is a secondary command buffer, there must! not be an outstanding D command recorded to  commandBuffer; that has not previously been ended by a call to D.Valid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handleHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronized Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also7vkBeginCommandBuffer - Start recording a command buffer Parameters commandBufferT is the handle of the command buffer which is to be put in the recording state. pBeginInfo is an instance of the VkCommandBufferBeginInfoi structure, which defines additional information about how the command buffer begins recording. Valid Usage commandBuffer must not be in the  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording or pending state.If  commandBuffer was allocated from a  which did not have the /VK_COMMAND_POOL_CREATE_RESET_COMMAND_BUFFER_BIT flag set,  commandBuffer must be in the  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecycleinitial state.If  commandBuffer) is a secondary command buffer, the pInheritanceInfo member of  pBeginInfo must be a valid VkCommandBufferInheritanceInfo structureIf  commandBuffer3 is a secondary command buffer and either the occlusionQueryEnable member of the pInheritanceInfo member of  pBeginInfo is VK_FALSED, or the precise occlusion queries feature is not enabled, the  queryFlags member of the pInheritanceInfo member  pBeginInfo must not contain VK_QUERY_CONTROL_PRECISE_BITValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle pBeginInfo must$ be a valid pointer to a valid VkCommandBufferBeginInfo structureHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronized Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, +vkFreeCommandBuffers - Free command buffers Parametersdevice2 is the logical device that owns the command pool. commandPoolH is the command pool from which the command buffers were allocated.commandBufferCount is the length of the pCommandBuffers array.pCommandBuffers3 is an array of handles of command buffers to free. Description*Any primary command buffer that is in the  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording or executable state and has any element of pCommandBuffers recorded into it, becomes  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecycleinvalid. Valid UsageAll elements of pCommandBuffers must not be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclepending statepCommandBuffers must( be a valid pointer to an array of commandBufferCount VkCommandBuffer% handles, each element of which must either be a valid handle or NULLValid Usage (Implicit)device must be a valid VkDevice handle commandPool must be a valid  VkCommandPool handlecommandBufferCount must be greater than 0 commandPool must6 have been created, allocated, or retrieved from deviceEach element of pCommandBuffers that is a valid handle must6 have been created, allocated, or retrieved from  commandPoolHost SynchronizationHost access to  commandPool must be externally synchronizedHost access to each member of pCommandBuffers must be externally synchronizedSee Also, , RvkAllocateCommandBuffers - Allocate command buffers from an existing command pool Parametersdevice2 is the logical device that owns the command pool. pAllocateInfo) is a pointer to an instance of the VkCommandBufferAllocateInfo8 structure describing parameters of the allocation.pCommandBuffers is a pointer to an array of VkCommandBufferY handles in which the resulting command buffer objects are returned. The array must. be at least the length specified by the commandBufferCount member of  pAllocateInfoA. Each allocated command buffer begins in the initial state. DescriptionvkAllocateCommandBuffers cany be used to create multiple command buffers. If the creation of any of those command buffers fails, the implementation mustd destroy all successfully created command buffer objects from this command, set all entries of the pCommandBuffers array to NULL and return the error.:When command buffers are first allocated, they are in the  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecycleinitial state.Valid Usage (Implicit)device must be a valid VkDevice handle pAllocateInfo must$ be a valid pointer to a valid VkCommandBufferAllocateInfo structurepCommandBuffers must( be a valid pointer to an array of  pAllocateInfo::commandBufferCount VkCommandBuffer handlesHost SynchronizationHost access to  pAllocateInfo::commandPool must be externally synchronized Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, , ,VK_COMMAND_BUFFER_USAGE_SIMULTANEOUS_USE_BIT" specifies that a command buffer cans be resubmitted to a queue while it is in the /pending state/, and recorded into multiple primary command buffers.0VK_COMMAND_BUFFER_USAGE_RENDER_PASS_CONTINUE_BIT specifies that a secondary command buffer is considered to be entirely inside a render pass. If this is a primary command buffer, then this bit is ignored.+VK_COMMAND_BUFFER_USAGE_ONE_TIME_SUBMIT_BIT specifies that each recording of the command buffer will only be submitted once, and the command buffer will be reset and recorded again between each submission.-VK_COMMAND_BUFFER_RESET_RELEASE_RESOURCES_BITT specifies that most or all memory resources currently owned by the command buffer should\ be returned to the parent command pool. If this flag is not set, then the command buffer mayE hold onto memory resources and reuse them when recording commands.  commandBuffer is moved to the  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecycleinitial state.VK_QUERY_CONTROL_PRECISE_BIT specifies the precision of  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#queries-occlusionocclusion queries.!VK_COMMAND_BUFFER_LEVEL_SECONDARY' specifies a secondary command buffer.VK_COMMAND_BUFFER_LEVEL_PRIMARY$ specifies a primary command buffer...None "-KSTbejkP}CGVkDescriptorPoolCreateFlags - Bitmask of VkDescriptorPoolCreateFlagBits DescriptionVkDescriptorPoolCreateFlags7 is a bitmask type for setting a mask of zero or more $.See Also$, RVkDescriptorSetLayoutCreateFlags - Bitmask of VkDescriptorSetLayoutCreateFlagBits Description VkDescriptorSetLayoutCreateFlags7 is a bitmask type for setting a mask of zero or more &.See Also&, aVkDescriptorSetAllocateInfo - Structure specifying the allocation parameters for descriptor sets Valid UsageEach element of  pSetLayouts must! not have been created with 7VK_DESCRIPTOR_SET_LAYOUT_CREATE_PUSH_DESCRIPTOR_BIT_KHR setIf any element of  pSetLayouts was created with the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT bit set, descriptorPool must! have been created with the 3VK_DESCRIPTOR_POOL_CREATE_UPDATE_AFTER_BIND_BIT_EXT flag setValid Usage (Implicit)sType must be .VK_STRUCTURE_TYPE_DESCRIPTOR_SET_ALLOCATE_INFOpNext must be NULL* or a pointer to a valid instance of descriptorPool must be a valid VkDescriptorPool handle pSetLayouts must( be a valid pointer to an array of descriptorSetCount valid VkDescriptorSetLayout handlesdescriptorSetCount must be greater than 0Both of descriptorPool, and the elements of  pSetLayouts must? have been created, allocated, or retrieved from the same VkDeviceSee Also ,  w, , ,sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.descriptorPool3 is the pool which the sets will be allocated from.descriptorSetCountI determines the number of descriptor sets to be allocated from the pool. pSetLayoutsw is an array of descriptor set layouts, with each member specifying how the corresponding descriptor set is allocated.`VkDescriptorPoolCreateInfo - Structure specifying parameters of a newly created descriptor pool Description If multiple VkDescriptorPoolSize structures appear in the  pPoolSizesl array then the pool will be created with enough storage for the total number of descriptors of each type.3Fragmentation of a descriptor pool is possible and may lead to descriptor set allocation failures. A failure due to fragmentation is defined as failing a descriptor set allocation despite the sum of all outstanding descriptor set allocations from the pool plus the requested allocation requiring no more than the total number of descriptors requested at pool creation. Implementations provide certain guarantees of when fragmentation must3 not cause allocation failure, as described below.{If a descriptor pool has not had any descriptor sets freed since it was created or most recently reset then fragmentation muste not cause an allocation failure (note that this is always the case for a pool created without the 1VK_DESCRIPTOR_POOL_CREATE_FREE_DESCRIPTOR_SET_BIT bit set). Additionally, if all sets allocated from the pool since it was created or most recently reset use the same number of descriptors (of each type) and the requested allocation also uses that same number of descriptors (of each type), then fragmentation must" not cause an allocation failure.FIf an allocation failure occurs due to fragmentation, an application canU create an additional descriptor pool to perform further descriptor set allocations.If flags has the 3VK_DESCRIPTOR_POOL_CREATE_UPDATE_AFTER_BIND_BIT_EXT$ bit set, descriptor pool creation may fail with the error VK_ERROR_FRAGMENTATION_EXTn if the total number of descriptors across all pools (including this one) created with this bit set exceeds 'maxUpdateAfterBindDescriptorsInAllPoolsC, or if fragmentation of the underlying hardware resources occurs. Valid UsagemaxSets must be greater than 0Valid Usage (Implicit)sType must be -VK_STRUCTURE_TYPE_DESCRIPTOR_POOL_CREATE_INFOpNext must be NULLflags must be a valid combination of $ values pPoolSizes must( be a valid pointer to an array of  poolSizeCount valid VkDescriptorPoolSize structures poolSizeCount must be greater than 0See Also, , , /sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.flags is a bitmask of $6 specifying certain supported operations on the pool.maxSets/ is the maximum number of descriptor sets that can be allocated from the pool. poolSizeCount is the number of elements in  pPoolSizes. pPoolSizes is a pointer to an array of VkDescriptorPoolSizet structures, each containing a descriptor type and number of descriptors of that type to be allocated in the pool.@VkDescriptorPoolSize - Structure specifying descriptor pool size Valid UsagedescriptorCount must be greater than 0Valid Usage (Implicit)type must be a valid ( valueSee Also, (type is the type of descriptor.descriptorCount7 is the number of descriptors of that type to allocate.kVkDescriptorSetLayoutCreateInfo - Structure specifying parameters of a newly created descriptor set layout Valid UsageThe ::binding% members of the elements of the  pBindings array must each have different values.If flags contains 7VK_DESCRIPTOR_SET_LAYOUT_CREATE_PUSH_DESCRIPTOR_BIT_KHR, then all elements of  pBindings must not have a descriptorType of )VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER_DYNAMIC or )VK_DESCRIPTOR_TYPE_STORAGE_BUFFER_DYNAMICIf flags contains 7VK_DESCRIPTOR_SET_LAYOUT_CREATE_PUSH_DESCRIPTOR_BIT_KHR9, then the total number of elements of all bindings must$ be less than or equal to i::maxPushDescriptorsIf any binding has the /VK_DESCRIPTOR_BINDING_UPDATE_AFTER_BIND_BIT_EXT bit set, flags must include >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXTIf any binding has the /VK_DESCRIPTOR_BINDING_UPDATE_AFTER_BIND_BIT_EXT! bit set, then all bindings must not have descriptorType of )VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER_DYNAMIC or )VK_DESCRIPTOR_TYPE_STORAGE_BUFFER_DYNAMICValid Usage (Implicit)sType must be 3VK_STRUCTURE_TYPE_DESCRIPTOR_SET_LAYOUT_CREATE_INFOpNext must be NULL* or a pointer to a valid instance of flags must be a valid combination of & valuesIf  bindingCount is not 0,  pBindings must( be a valid pointer to an array of  bindingCount valid VkDescriptorSetLayoutBinding structuresSee Also, , , 1, K, LsType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.flags is a bitmask of &8 specifying options for descriptor set layout creation. bindingCount is the number of elements in  pBindings. pBindings is a pointer to an array of  structures.TVkDescriptorSetLayoutBinding - Structure specifying a descriptor set layout bindingMembersbindingx is the binding number of this entry and corresponds to a resource of the same binding number in the shader stages.descriptorType is a (N specifying which type of resource descriptors are used for this binding.descriptorCountb is the number of descriptors contained in the binding, accessed in a shader as an array. If descriptorCount> is zero this binding entry is reserved and the resource mustd not be accessed from any stage via this binding within any pipeline using the set layout. stageFlags member is a bitmask of H . specifying which pipeline shader stages can* access a resource for this binding. VK_SHADER_STAGE_ALL| is a shorthand specifying that all defined shader stages, including any additional stages defined by extensions, can access the resource.%If a shader stage is not included in  stageFlags, then a resource must not be accessed from that stage via this binding within any pipeline using the set layout. Other than input attachments which are limited to the fragment shader, there are no limitations on what combinations of stages can7 use a descriptor binding, and in particular a binding can7 be used by both graphics stages and the compute stage. DescriptionpImmutableSamplers- affects initialization of samplers. If descriptorType specifies a VK_DESCRIPTOR_TYPE_SAMPLER or )VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLER type descriptor, then pImmutableSamplers can be used to initialize a set of /immutable samplers/. Immutable samplers are permanently bound into the set layout; later binding a sampler into an immutable sampler slot in a descriptor set is not allowed. If pImmutableSamplers is not NULL, then it is considered to be a pointer to an array of sampler handles that will be consumed by the set layout and used for the corresponding binding. If pImmutableSamplers is NULL>, then the sampler slots are dynamic and sampler handles must: be bound into descriptor sets using this layout. If descriptorType1 is not one of these descriptor types, then pImmutableSamplers is ignored.The above layout definition allows the descriptor bindings to be specified sparsely such that not all binding numbers between 0 and the maximum binding number need to be specified in the  pBindings0 array. Bindings that are not specified have a descriptorCount and  stageFlags of zero, and the descriptorTypei is treated as undefined. However, all binding numbers between 0 and the maximum binding number in the :: pBindings array mayg consume memory in the descriptor set layout even if not all descriptor bindings are used, though it should9 not consume additional memory from the descriptor pool.Note%The maximum binding number specified should3 be as compact as possible to avoid wasted memory. Valid UsageIf descriptorType is VK_DESCRIPTOR_TYPE_SAMPLER or )VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLER, and descriptorCount is not 0 and pImmutableSamplers is not NULL, pImmutableSamplers must( be a valid pointer to an array of descriptorCount valid  VkSampler handlesIf descriptorCount is not 0,  stageFlags must% be a valid combination of H  valuesIf descriptorType is #VK_DESCRIPTOR_TYPE_INPUT_ATTACHMENT and descriptorCount is not 0, then  stageFlags must be 0 or VK_SHADER_STAGE_FRAGMENT_BITValid Usage (Implicit)descriptorType must be a valid ( valueSee Also, (,  (,  hKVkCopyDescriptorSet - Structure specifying a copy descriptor set operation Valid Usage srcBinding must be a valid binding within srcSet The sum of srcArrayElement and descriptorCount mustl be less than or equal to the number of array elements in the descriptor set binding specified by  srcBindingE, and all applicable consecutive bindings, as described by phttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-updates-consecutive7{html_spec_relative}#descriptorsets-updates-consecutive dstBinding must be a valid binding within dstSet The sum of dstArrayElement and descriptorCount mustl be less than or equal to the number of array elements in the descriptor set binding specified by  dstBindingE, and all applicable consecutive bindings, as described by phttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-updates-consecutive7{html_spec_relative}#descriptorsets-updates-consecutiveIf srcSet is equal to dstSet=, then the source and destination ranges of descriptors must not overlap, where the ranges mayL include array elements from consecutive bindings as described by phttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-updates-consecutive7{html_spec_relative}#descriptorsets-updates-consecutiveIf srcSet$ s layout was created with the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT flag set, then dstSet s layout must& also have been created with the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT flag setIf srcSet' s layout was created without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT flag set, then dstSet s layout must. also have been created without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT flag set"If the descriptor pool from which srcSet) was allocated was created with the 3VK_DESCRIPTOR_POOL_CREATE_UPDATE_AFTER_BIND_BIT_EXT4 flag set, then the descriptor pool from which dstSet was allocated must& also have been created with the 3VK_DESCRIPTOR_POOL_CREATE_UPDATE_AFTER_BIND_BIT_EXT flag set"If the descriptor pool from which srcSet, was allocated was created without the 3VK_DESCRIPTOR_POOL_CREATE_UPDATE_AFTER_BIND_BIT_EXT4 flag set, then the descriptor pool from which dstSet was allocated must) also have been created without the 3VK_DESCRIPTOR_POOL_CREATE_UPDATE_AFTER_BIND_BIT_EXT flag setValid Usage (Implicit)sType must be %VK_STRUCTURE_TYPE_COPY_DESCRIPTOR_SETpNext must be NULLsrcSet must be a valid VkDescriptorSet handledstSet must be a valid VkDescriptorSet handleBoth of dstSet, and srcSet must? have been created, allocated, or retrieved from the same VkDeviceSee Also!, , *sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.srcSet,  srcBinding, and srcArrayElement? are the source set, binding, and array element, respectively.dstSet,  dstBinding, and dstArrayElementD are the destination set, binding, and array element, respectively. descriptorCountJ is the number of descriptors to copy from the source to destination. If descriptorCount is greater than the number of remaining array elements in the source or destination binding, those affect consecutive bindings in a manner similar to   above. _VkWriteDescriptorSet - Structure specifying the parameters of a descriptor set write operation Description Only one of  pImageInfo,  pBufferInfo, or pTexelBufferViewE members is used according to the descriptor type specified in the descriptorType member of the containing VkWriteDescriptorSet structure, as specified below.If the  dstBinding has fewer than descriptorCount) array elements remaining starting from dstArrayElementF, then the remainder will be used to update the subsequent binding -  dstBinding7+1 starting at array element zero. If a binding has a descriptorCount of zero, it is skipped. This behavior applies recursively, with the update affecting consecutive bindings as needed to update all descriptorCount descriptors. Valid Usage dstBinding must4 be less than or equal to the maximum value of binding of all  structures specified when dstSet$ s descriptor set layout was created dstBinding must be a binding with a non-zero descriptorCount.All consecutive bindings updated via a single VkWriteDescriptorSet% structure, except those with a descriptorCount of zero, must have identical descriptorType and  stageFlags..All consecutive bindings updated via a single VkWriteDescriptorSet% structure, except those with a descriptorCount of zero, must+ all either use immutable samplers or must% all not use immutable samplers.descriptorType must match the type of  dstBinding within dstSetdstSet must be a valid ! handle The sum of dstArrayElement and descriptorCount mustl be less than or equal to the number of array elements in the descriptor set binding specified by  dstBindingE, and all applicable consecutive bindings, as described by phttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-updates-consecutive7{html_spec_relative}#descriptorsets-updates-consecutiveIf descriptorType is VK_DESCRIPTOR_TYPE_SAMPLER, )VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLER,  VK_DESCRIPTOR_TYPE_SAMPLED_IMAGE,  VK_DESCRIPTOR_TYPE_STORAGE_IMAGE , or #VK_DESCRIPTOR_TYPE_INPUT_ATTACHMENT,  pImageInfo must( be a valid pointer to an array of descriptorCount valid VkDescriptorImageInfo structuresIf descriptorType is 'VK_DESCRIPTOR_TYPE_UNIFORM_TEXEL_BUFFER or 'VK_DESCRIPTOR_TYPE_STORAGE_TEXEL_BUFFER, pTexelBufferView must( be a valid pointer to an array of descriptorCount valid  VkBufferView handlesIf descriptorType is !VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER, !VK_DESCRIPTOR_TYPE_STORAGE_BUFFER, )VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER_DYNAMIC , or )VK_DESCRIPTOR_TYPE_STORAGE_BUFFER_DYNAMIC,  pBufferInfo must( be a valid pointer to an array of descriptorCount valid VkDescriptorBufferInfo structuresIf descriptorType is VK_DESCRIPTOR_TYPE_SAMPLER or )VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLER, and dstSetP was not allocated with a layout that included immutable samplers for  dstBinding with descriptorType, the sampler member of each element of  pImageInfo must be a valid  VkSampler objectIf descriptorType is )VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLER,  VK_DESCRIPTOR_TYPE_SAMPLED_IMAGE,  VK_DESCRIPTOR_TYPE_STORAGE_IMAGE , or #VK_DESCRIPTOR_TYPE_INPUT_ATTACHMENT, the  imageView and  imageLayout members of each element of  pImageInfo must be a valid  VkImageView and , respectivelyIf descriptorType is  VK_DESCRIPTOR_TYPE_STORAGE_IMAGEW, for each descriptor that will be accessed via load or store operations the  imageLayout& member for corresponding elements of  pImageInfo must be VK_IMAGE_LAYOUT_GENERALIf descriptorType is !VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER or )VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER_DYNAMIC, the offset member of each element of  pBufferInfo must be a multiple of VkPhysicalDeviceLimits::minUniformBufferOffsetAlignmentIf descriptorType is !VK_DESCRIPTOR_TYPE_STORAGE_BUFFER or )VK_DESCRIPTOR_TYPE_STORAGE_BUFFER_DYNAMIC, the offset member of each element of  pBufferInfo must be a multiple of VkPhysicalDeviceLimits::minStorageBufferOffsetAlignmentIf descriptorType is !VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER, )VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER_DYNAMIC, !VK_DESCRIPTOR_TYPE_STORAGE_BUFFER , or )VK_DESCRIPTOR_TYPE_STORAGE_BUFFER_DYNAMIC , and the buffer member of any element of  pBufferInfo= is the handle of a non-sparse buffer, then that buffer must7 be bound completely and contiguously to a single VkDeviceMemory objectIf descriptorType is !VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER or )VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER_DYNAMIC, the buffer member of each element of  pBufferInfo must have been created with "VK_BUFFER_USAGE_UNIFORM_BUFFER_BIT setIf descriptorType is !VK_DESCRIPTOR_TYPE_STORAGE_BUFFER or )VK_DESCRIPTOR_TYPE_STORAGE_BUFFER_DYNAMIC, the buffer member of each element of  pBufferInfo must have been created with "VK_BUFFER_USAGE_STORAGE_BUFFER_BIT setIf descriptorType is !VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER or )VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER_DYNAMIC, the range member of each element of  pBufferInfo, or the effective range if range is  VK_WHOLE_SIZE, must be less than or equal to VkPhysicalDeviceLimits::maxUniformBufferRangeIf descriptorType is !VK_DESCRIPTOR_TYPE_STORAGE_BUFFER or )VK_DESCRIPTOR_TYPE_STORAGE_BUFFER_DYNAMIC, the range member of each element of  pBufferInfo, or the effective range if range is  VK_WHOLE_SIZE, must be less than or equal to VkPhysicalDeviceLimits::maxStorageBufferRangeIf descriptorType is 'VK_DESCRIPTOR_TYPE_UNIFORM_TEXEL_BUFFER , the VkBuffer that each element of pTexelBufferView was created from must have been created with (VK_BUFFER_USAGE_UNIFORM_TEXEL_BUFFER_BIT setIf descriptorType is 'VK_DESCRIPTOR_TYPE_STORAGE_TEXEL_BUFFER , the VkBuffer that each element of pTexelBufferView was created from must have been created with (VK_BUFFER_USAGE_STORAGE_TEXEL_BUFFER_BIT setIf descriptorType is  VK_DESCRIPTOR_TYPE_STORAGE_IMAGE or #VK_DESCRIPTOR_TYPE_INPUT_ATTACHMENT, the  imageView member of each element of  pImageInfo must1 have been created with the identity swizzleIf descriptorType is  VK_DESCRIPTOR_TYPE_SAMPLED_IMAGE or )VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLER, the  imageView member of each element of  pImageInfo must have been created with VK_IMAGE_USAGE_SAMPLED_BIT setIf descriptorType is  VK_DESCRIPTOR_TYPE_SAMPLED_IMAGE or )VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLER, the  imageLayout member of each element of  pImageInfo must be (VK_IMAGE_LAYOUT_SHADER_READ_ONLY_OPTIMAL, /VK_IMAGE_LAYOUT_DEPTH_STENCIL_READ_ONLY_OPTIMAL or VK_IMAGE_LAYOUT_GENERALIf descriptorType is #VK_DESCRIPTOR_TYPE_INPUT_ATTACHMENT , the  imageView member of each element of  pImageInfo must have been created with #VK_IMAGE_USAGE_INPUT_ATTACHMENT_BIT setIf descriptorType is  VK_DESCRIPTOR_TYPE_STORAGE_IMAGE , the  imageView member of each element of  pImageInfo must have been created with VK_IMAGE_USAGE_STORAGE_BIT set.All consecutive bindings updated via a single VkWriteDescriptorSet% structure, except those with a descriptorCount of zero, must have identical &.Valid Usage (Implicit)sType must be &VK_STRUCTURE_TYPE_WRITE_DESCRIPTOR_SETpNext must be NULLdescriptorType must be a valid ( valuedescriptorCount must be greater than 0Both of dstSet, and the elements of pTexelBufferView that are valid handles must? have been created, allocated, or retrieved from the same VkDeviceSee Also, , , !, (, , , * sType is the type of this structure. pNext is NULL1 or a pointer to an extension-specific structure.dstSet- is the destination descriptor set to update. dstBinding+ is the descriptor binding within that set.dstArrayElement' is the starting element in that array.descriptorCountD is the number of descriptors to update (the number of elements in  pImageInfo,  pBufferInfo, or pTexelBufferView).descriptorType is a (, specifying the type of each descriptor in  pImageInfo,  pBufferInfo, or pTexelBufferView, as described below. It must( be the same type as that specified in VkDescriptorSetLayoutBinding for dstSet at  dstBindingW. The type of the descriptor also controls which array the descriptors are taken from. pImageInfo points to an array of / structures or is ignored, as described below. pBufferInfo points to an array of / structures or is ignored, as described below.pTexelBufferView points to an array of  handles as described in the  dhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#resources-buffer-views Buffer Views, section or is ignored, as described below.BVkDescriptorImageInfo - Structure specifying descriptor image info Description Members of VkDescriptorImageInfoB that are not used in an update (as described above) are ignored. Valid Usage imageView must> not be 2D or 2D array image view created from a 3D image imageLayout must match the actual * of each subresource accessible from  imageView( at the time this descriptor is accessedIf sampler is used and enables  ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#samplers-YCbCr-conversionsampler Y CBCR conversion:The format of the  imageView must be the same as the  of the imageThe  aspectMask of the  imageView must be VK_IMAGE_ASPECT_COLOR_BITThe  components.a of the  imageView must be VK_COMPONENT_SWIZZLE_IDENTITYThe  components.r of the  imageView must be VK_COMPONENT_SWIZZLE_IDENTITYThe  components.g of the  imageView must be VK_COMPONENT_SWIZZLE_IDENTITYThe  components.b of the  imageView must be VK_COMPONENT_SWIZZLE_IDENTITYThe pNext chain of the  imageView must contain a VkSamplerYcbcrConversionInfo which has a  conversion which is an identically defined object to the  conversion of the VkSamplerYcbcrConversionInfo which is in the pNext chain of the samplerIf sampler is used and does not enable  ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#samplers-YCbCr-conversionsampler Y CBCR conversion and the  of the image is a  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversionmulti-planar format, the image must have been created with "VK_IMAGE_CREATE_MUTABLE_FORMAT_BIT , and the  aspectMask of the  imageView must be VK_IMAGE_ASPECT_PLANE_0_BIT, VK_IMAGE_ASPECT_PLANE_1_BIT( or (for three-plane formats only) VK_IMAGE_ASPECT_PLANE_2_BITValid Usage (Implicit)Both of  imageView, and sampler that are valid handles must? have been created, allocated, or retrieved from the same VkDeviceSee Also, ,  (,  samplerC is a sampler handle, and is used in descriptor updates for types VK_DESCRIPTOR_TYPE_SAMPLER and )VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLER? if the binding being updated does not use immutable samplers. imageViewG is an image view handle, and is used in descriptor updates for types  VK_DESCRIPTOR_TYPE_SAMPLED_IMAGE,  VK_DESCRIPTOR_TYPE_STORAGE_IMAGE, )VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLER, and #VK_DESCRIPTOR_TYPE_INPUT_ATTACHMENT. imageLayout< is the layout that the image subresources accessible from  imageView6 will be in at the time this descriptor is accessed.  imageLayout* is used in descriptor updates for types  VK_DESCRIPTOR_TYPE_SAMPLED_IMAGE,  VK_DESCRIPTOR_TYPE_STORAGE_IMAGE, )VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLER, and #VK_DESCRIPTOR_TYPE_INPUT_ATTACHMENT.DVkDescriptorBufferInfo - Structure specifying descriptor buffer info DescriptionNote When setting range to  VK_WHOLE_SIZE, the effective range must` not be larger than the maximum range for the descriptor type ([maxUniformBufferRange](https:/www.khronos.orgregistryvulkanspecs1.0-extensions=html/vkspec.html#features-limits-maxUniformBufferRange) or  shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-limits-maxStorageBufferRangemaxStorageBufferRange). This means that  VK_WHOLE_SIZE is not typically useful in the common case where uniform buffer descriptors are suballocated from a buffer that is much larger than maxUniformBufferRange.For )VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER_DYNAMIC and )VK_DESCRIPTOR_TYPE_STORAGE_BUFFER_DYNAMIC descriptor types, offsetB is the base offset from which the dynamic offset is applied and range2 is the static size used for all dynamic offsets. Valid Usageoffset must be less than the size of bufferIf range is not equal to  VK_WHOLE_SIZE, range must be greater than 0If range is not equal to  VK_WHOLE_SIZE, range must+ be less than or equal to the size of buffer minus offsetValid Usage (Implicit)buffer must be a valid VkBuffer handleSee Also3,  VkDeviceSize,  buffer is the buffer resource.offset* is the offset in bytes from the start of bufferi. Access to buffer memory via this descriptor uses addressing that is relative to this starting offset.rangeC is the size in bytes that is used for this descriptor update, or  VK_WHOLE_SIZE to use the range from offset to the end of the buffer. <VkDescriptorPool - Opaque handle to a descriptor pool objectSee Also, /, ., +, -:Dummy data to tag the  with!:VkDescriptorSet - Opaque handle to a descriptor set objectSee Also, ,  , ,, , +, , ;Dummy data to tag the  with"4VkDescriptorPoolResetFlags - Reserved for future use DescriptionVkDescriptorPoolResetFlagsQ is a bitmask type for setting a mask, but is currently reserved for future use.See Also-$fVkDescriptorPoolCreateFlagBits - Bitmask specifying certain supported operations on a descriptor poolSee Also&ZVkDescriptorSetLayoutCreateFlagBits - Bitmask specifying descriptor set layout propertiesSee Also(JVkDescriptorType - Specifies the type of a descriptor in a descriptor set DescriptionVK_DESCRIPTOR_TYPE_SAMPLER specifies a  dhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-samplersampler descriptor. )VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLER specifies a  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-combinedimagesampler+combined image sampler descriptor. VK_DESCRIPTOR_TYPE_SAMPLED_IMAGE specifies a  ihttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-sampledimagesampled image descriptor. VK_DESCRIPTOR_TYPE_STORAGE_IMAGE specifies a  ihttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-storageimagestorage image descriptor.'VK_DESCRIPTOR_TYPE_UNIFORM_TEXEL_BUFFER specifies a  ohttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-uniformtexelbuffer)uniform texel buffer descriptor.'VK_DESCRIPTOR_TYPE_STORAGE_TEXEL_BUFFER specifies a  ohttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-storagetexelbuffer)storage texel buffer descriptor.!VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER specifies a  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-uniformbufferuniform buffer descriptor.!VK_DESCRIPTOR_TYPE_STORAGE_BUFFER specifies a  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-storagebufferstorage buffer descriptor.)VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER_DYNAMIC specifies a  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-uniformbufferdynamic+dynamic uniform buffer descriptor.)VK_DESCRIPTOR_TYPE_STORAGE_BUFFER_DYNAMIC specifies a  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-storagebufferdynamic+dynamic storage buffer descriptor.#VK_DESCRIPTOR_TYPE_INPUT_ATTACHMENT specifies a  lhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-inputattachment input attachment descriptor.1When a descriptor set is updated via elements of  , members of  pImageInfo,  pBufferInfo and pTexelBufferView are only accessed by the implementation when they correspond to descriptor type being defined - otherwise they are ignored. The members accessed are as follows for each descriptor type:For VK_DESCRIPTOR_TYPE_SAMPLER , only the sample member of each element of  :: pImageInfo is accessed.For  VK_DESCRIPTOR_TYPE_SAMPLED_IMAGE,  VK_DESCRIPTOR_TYPE_STORAGE_IMAGE , or #VK_DESCRIPTOR_TYPE_INPUT_ATTACHMENT , only the  imageView and  imageLayout! members of each element of  :: pImageInfo are accessed.For )VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLER&, all members of each element of  :: pImageInfo are accessed.For !VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER, !VK_DESCRIPTOR_TYPE_STORAGE_BUFFER, )VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER_DYNAMIC , or )VK_DESCRIPTOR_TYPE_STORAGE_BUFFER_DYNAMIC&, all members of each element of  :: pBufferInfo are accessed.For 'VK_DESCRIPTOR_TYPE_UNIFORM_TEXEL_BUFFER or 'VK_DESCRIPTOR_TYPE_STORAGE_TEXEL_BUFFER, each element of  ::pTexelBufferView is accessed.See Also, , ',  *GvkUpdateDescriptorSets - Update the contents of a descriptor set object Parametersdevice8 is the logical device that updates the descriptor sets.descriptorWriteCount' is the number of elements in the pDescriptorWrites array.pDescriptorWrites" is a pointer to an array of  < structures describing the descriptor sets to write to.descriptorCopyCount' is the number of elements in the pDescriptorCopies array.pDescriptorCopies" is a pointer to an array of @ structures describing the descriptor sets to copy between. DescriptionThe operations described by pDescriptorWrites? are performed first, followed by the operations described by pDescriptorCopiesZ. Within each array, the operations are performed in the order they appear in the array.Each element in the pDescriptorWritesw array describes an operation updating the descriptor set using descriptors for resources specified in the structure.Each element in the pDescriptorCopies array is a E structure describing an operation copying descriptors between sets.If the dstSet member of any element of pDescriptorWrites or pDescriptorCopiesq is bound, accessed, or modified by any command that was recorded to a command buffer which is currently in the  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording or executable stateR, and any of the descriptor bindings that are updated were not created with the /VK_DESCRIPTOR_BINDING_UPDATE_AFTER_BIND_BIT_EXT or 9VK_DESCRIPTOR_BINDING_UPDATE_UNUSED_WHILE_PENDING_BIT_EXT) bits set, that command buffer becomes  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecycleinvalid. Valid UsagePDescriptor bindings updated by this command which were created without the /VK_DESCRIPTOR_BINDING_UPDATE_AFTER_BIND_BIT_EXT or 9VK_DESCRIPTOR_BINDING_UPDATE_UNUSED_WHILE_PENDING_BIT_EXT bits set mustW not be used by any command that was recorded to a command buffer which is in the  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclepending state.Valid Usage (Implicit)device must be a valid VkDevice handleIf descriptorWriteCount is not 0, pDescriptorWrites must( be a valid pointer to an array of descriptorWriteCount valid VkWriteDescriptorSet structuresIf descriptorCopyCount is not 0, pDescriptorCopies must( be a valid pointer to an array of descriptorCopyCount valid VkCopyDescriptorSet structuresHost SynchronizationHost access to pDescriptorWrites [].dstSet must be externally synchronizedHost access to pDescriptorCopies [].dstSet must be externally synchronizedSee Also, ,  +7vkFreeDescriptorSets - Free one or more descriptor sets Parametersdevice5 is the logical device that owns the descriptor pool.descriptorPoolK is the descriptor pool from which the descriptor sets were allocated.descriptorSetCount' is the number of elements in the pDescriptorSets array.pDescriptorSets is an array of handles to VkDescriptorSet objects. DescriptionAfter a successful call to vkFreeDescriptorSets, all descriptor sets in pDescriptorSets are invalid. Valid Usage9All submitted commands that refer to any element of pDescriptorSets must have completed executionpDescriptorSets must( be a valid pointer to an array of descriptorSetCount VkDescriptorSet% handles, each element of which must" either be a valid handle or Each valid handle in pDescriptorSets must have been allocated from descriptorPooldescriptorPool must! have been created with the 1VK_DESCRIPTOR_POOL_CREATE_FREE_DESCRIPTOR_SET_BIT flagValid Usage (Implicit)device must be a valid VkDevice handledescriptorPool must be a valid VkDescriptorPool handledescriptorSetCount must be greater than 0descriptorPool must6 have been created, allocated, or retrieved from deviceEach element of pDescriptorSets that is a valid handle must6 have been created, allocated, or retrieved from descriptorPoolHost SynchronizationHost access to descriptorPool must be externally synchronizedHost access to each member of pDescriptorSets must be externally synchronized Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also , !, ,?vkAllocateDescriptorSets - Allocate one or more descriptor sets Parametersdevice5 is the logical device that owns the descriptor pool. pAllocateInfo) is a pointer to an instance of the 8 structure describing parameters of the allocation.pDescriptorSets is a pointer to an array of VkDescriptorSetI handles in which the resulting descriptor set objects are returned. Description.The allocated descriptor sets are returned in pDescriptorSets.When a descriptor set is allocated, the initial state is largely uninitialized and all descriptors are undefined. However, the descriptor set cans be bound in a command buffer without causing errors or exceptions. For descriptor set bindings created with the -VK_DESCRIPTOR_BINDING_PARTIALLY_BOUND_BIT_EXTE bit set, all descriptors in that binding that are dynamically used must4 have been populated before the descriptor set is  dhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-bindingconsumed4. For descriptor set bindings created without the -VK_DESCRIPTOR_BINDING_PARTIALLY_BOUND_BIT_EXTD bit set, all descriptors in that binding that are statically used must4 have been populated before the descriptor set is  dhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-bindingconsumed+. Entries that are not used by a pipeline can have uninitialized descriptors or descriptors of resources that have been destroyed, and executing a draw or dispatch with such a descriptor set bound does not cause undefined behavior. This means applications need not populate unused entries with dummy descriptors. If a call to vkAllocateDescriptorSetsb would cause the total number of descriptor sets allocated from the pool to exceed the value of ::maxSets used to create  pAllocateInfo!descriptorPool, then the allocation mayN fail due to lack of space in the descriptor pool. Similarly, the allocation may+ fail due to lack of space if the call to vkAllocateDescriptorSetsT would cause the number of any given descriptor type to exceed the sum of all the descriptorCount members of each element of :: pPoolSizes with a member equal to that type. If the allocation fails due to no more space in the descriptor pool, and not because of system or device memory exhaustion, then VK_ERROR_OUT_OF_POOL_MEMORY must be returned.vkAllocateDescriptorSets can~ be used to create multiple descriptor sets. If the creation of any of those descriptor sets fails, then the implementation mustd destroy all successfully created descriptor set objects from this command, set all entries of the pDescriptorSets array to  and return the error.Valid Usage (Implicit)device must be a valid VkDevice handle pAllocateInfo must$ be a valid pointer to a valid VkDescriptorSetAllocateInfo structurepDescriptorSets must( be a valid pointer to an array of  pAllocateInfo::descriptorSetCount VkDescriptorSet handlesHost SynchronizationHost access to  pAllocateInfo::descriptorPool must be externally synchronized Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_FRAGMENTED_POOL VK_ERROR_OUT_OF_POOL_MEMORYSee Also!, , -7vkResetDescriptorPool - Resets a descriptor pool object Parametersdevice5 is the logical device that owns the descriptor pool.descriptorPool$ is the descriptor pool to be reset.flags is reserved for future use. DescriptionResetting a descriptor pool recycles all of the resources from all of the descriptor sets allocated from the descriptor pool back to the descriptor pool, and the descriptor sets are implicitly freed. Valid Usage All uses of descriptorPool* (via any allocated descriptor sets) must have completed executionValid Usage (Implicit)device must be a valid VkDevice handledescriptorPool must be a valid VkDescriptorPool handleflags must be 0descriptorPool must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to descriptorPool must be externally synchronizedHost access to any VkDescriptorSet objects allocated from descriptorPool must be externally synchronized Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also , ", .:vkDestroyDescriptorPool - Destroy a descriptor pool object Parametersdevice9 is the logical device that destroys the descriptor pool.descriptorPool# is the descriptor pool to destroy. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. DescriptionWhen a pool is destroyed, all descriptor sets allocated from the pool are implicitly freed and become invalid. Descriptor sets allocated from a given pool do not need to be freed before destroying that descriptor pool. Valid Usage%All submitted commands that refer to descriptorPool* (via any allocated descriptor sets) must have completed executionIf VkAllocationCallbacks were provided when descriptorPool1 was created, a compatible set of callbacks must be provided hereIf no VkAllocationCallbacks were provided when descriptorPool was created,  pAllocator must be NULLValid Usage (Implicit)device must be a valid VkDevice handleIf descriptorPool is not , descriptorPool must be a valid VkDescriptorPool handleIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structureIf descriptorPool is a valid handle, it must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to descriptorPool must be externally synchronizedSee Also,  , /9vkCreateDescriptorPool - Creates a descriptor pool object Parametersdevice8 is the logical device that creates the descriptor pool. pCreateInfo) is a pointer to an instance of the C structure specifying the state of the descriptor pool object. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter.pDescriptorPool points to a VkDescriptorPoolG handle in which the resulting descriptor pool object is returned. Description pAllocator5 controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter.+The created descriptor pool is returned in pDescriptorPool.Valid Usage (Implicit)device must be a valid VkDevice handle pCreateInfo must$ be a valid pointer to a valid VkDescriptorPoolCreateInfo structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structurepDescriptorPool must be a valid pointer to a VkDescriptorPool handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORY VK_ERROR_FRAGMENTATION_EXTSee Also,  , , 0EvkDestroyDescriptorSetLayout - Destroy a descriptor set layout object ParametersdeviceD is the logical device that destroys the descriptor set layout.descriptorSetLayout) is the descriptor set layout to destroy. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. Valid UsageIf VkAllocationCallbacks were provided when descriptorSetLayout1 was created, a compatible set of callbacks must be provided hereIf no VkAllocationCallbacks were provided when descriptorSetLayout was created,  pAllocator must be NULLValid Usage (Implicit)device must be a valid VkDevice handleIf descriptorSetLayout is not , descriptorSetLayout must be a valid VkDescriptorSetLayout handleIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structureIf descriptorSetLayout is a valid handle, it must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to descriptorSetLayout must be externally synchronizedSee Also,  w, 1@vkCreateDescriptorSetLayout - Create a new descriptor set layout ParametersdeviceC is the logical device that creates the descriptor set layout. pCreateInfo) is a pointer to an instance of the I structure specifying the state of the descriptor set layout object. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. pSetLayout points to a VkDescriptorSetLayoutM handle in which the resulting descriptor set layout object is returned.Valid Usage (Implicit)device must be a valid VkDevice handle pCreateInfo must$ be a valid pointer to a valid VkDescriptorSetLayoutCreateInfo structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structure pSetLayout must be a valid pointer to a VkDescriptorSetLayout handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also,  w, , 21VK_DESCRIPTOR_POOL_CREATE_FREE_DESCRIPTOR_SET_BIT! specifies that descriptor sets can? return their individual allocations to the pool, i.e. all of ,, +, and -B are allowed. Otherwise, descriptor sets allocated from the pool must8 not be individually freed back to the pool, i.e. only , and - are allowed.b      !"#$%&'()*+,-./0123456789:;<=b()=<;:9876543&'$%2"#! 10/.-,+*     None"KbejkRFtVkDescriptorSetVariableDescriptorCountLayoutSupportEXT - Structure returning information about whether a descriptor set layout can be supported Description?If the create info includes a variable-sized descriptor, then  supportedR is determined assuming the requested size of the variable-sized descriptor, and maxVariableDescriptorCount5 is set to the maximum size of that descriptor that can be successfully created (which is greater than or equal to the requested size passed in). If the create info does not include a variable-sized descriptor or if the ::(descriptorBindingVariableDescriptorCount feature is not enabled, then maxVariableDescriptorCount` is set to zero. For the purposes of this command, a variable-sized descriptor binding with a descriptorCount of zero is treated as if the descriptorCount is one, and thus the binding is not ignored and the maximum descriptor count will be returned. If the layout is not supported, then the value written to maxVariableDescriptorCount is undefined.Valid Usage (Implicit)sType must be MVK_STRUCTURE_TYPE_DESCRIPTOR_SET_VARIABLE_DESCRIPTOR_COUNT_LAYOUT_SUPPORT_EXTSee AlsovsType is the type of this structure.wpNext is NULL1 or a pointer to an extension-specific structure.xmaxVariableDescriptorCount indicates the maximum number of descriptors supported in the highest numbered binding of the layout, if that binding is variable-sized.yVkDescriptorSetVariableDescriptorCountAllocateInfoEXT - Structure specifying additional allocation parameters for descriptor sets DescriptionIf descriptorSetCount3 is zero or this structure is not included in the pNextI chain, then the variable lengths are considered to be zero. Otherwise, pDescriptorCounts|[i] is the number of descriptors in the variable count descriptor binding in the corresponding descriptor set layout. If :: pSetLayoutsA[i] does not include a variable count descriptor binding, then pDescriptorCounts[i] is ignored. Valid UsageIf descriptorSetCount is not zero, descriptorSetCount must equal ::descriptorSetCountIf :: pSetLayouts7[i] has a variable descriptor count binding, then pDescriptorCounts [i] mustz be less than or equal to the descriptor count specified for that binding when the descriptor set layout was created.Valid Usage (Implicit)sType must be LVK_STRUCTURE_TYPE_DESCRIPTOR_SET_VARIABLE_DESCRIPTOR_COUNT_ALLOCATE_INFO_EXTIf descriptorSetCount is not 0, pDescriptorCounts must( be a valid pointer to an array of descriptorSetCount uint32_t valuesSee Also{sType is the type of this structure.|pNext is NULL1 or a pointer to an extension-specific structure.}descriptorSetCount' is zero or the number of elements in pDescriptorCounts.~pDescriptorCounts is an array of descriptor counts, with each member specifying the number of descriptors in a variable descriptor count binding in the corresponding descriptor set being allocated.xVkDescriptorSetLayoutBindingFlagsCreateInfoEXT - Structure specifying creation flags for descriptor set layout bindings DescriptionIf  bindingCount, is zero or if this structure is not in the pNext chain, the su for each descriptor set layout binding is considered to be zero. Otherwise, the descriptor set layout binding at :: pBindings[i] uses the flags in  pBindingFlags[i]. Valid UsageIf  bindingCount is not zero,  bindingCount must equal :: bindingCount If ::flags includes 7VK_DESCRIPTOR_SET_LAYOUT_CREATE_PUSH_DESCRIPTOR_BIT_KHR, then all elements of  pBindingFlags must not include /VK_DESCRIPTOR_BINDING_UPDATE_AFTER_BIND_BIT_EXT, 9VK_DESCRIPTOR_BINDING_UPDATE_UNUSED_WHILE_PENDING_BIT_EXT , or 7VK_DESCRIPTOR_BINDING_VARIABLE_DESCRIPTOR_COUNT_BIT_EXTIf an element of  pBindingFlags includes 7VK_DESCRIPTOR_BINDING_VARIABLE_DESCRIPTOR_COUNT_BIT_EXT', then all other elements of :: pBindings must have a smaller value of bindingIf ::-descriptorBindingUniformBufferUpdateAfterBind= is not enabled, all bindings with descriptor type !VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER must not use /VK_DESCRIPTOR_BINDING_UPDATE_AFTER_BIND_BIT_EXTIf ::,descriptorBindingSampledImageUpdateAfterBind= is not enabled, all bindings with descriptor type VK_DESCRIPTOR_TYPE_SAMPLER, )VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLER , or  VK_DESCRIPTOR_TYPE_SAMPLED_IMAGE must not use /VK_DESCRIPTOR_BINDING_UPDATE_AFTER_BIND_BIT_EXTIf ::,descriptorBindingStorageImageUpdateAfterBind= is not enabled, all bindings with descriptor type  VK_DESCRIPTOR_TYPE_STORAGE_IMAGE must not use /VK_DESCRIPTOR_BINDING_UPDATE_AFTER_BIND_BIT_EXTIf ::-descriptorBindingStorageBufferUpdateAfterBind= is not enabled, all bindings with descriptor type !VK_DESCRIPTOR_TYPE_STORAGE_BUFFER must not use /VK_DESCRIPTOR_BINDING_UPDATE_AFTER_BIND_BIT_EXTIf ::2descriptorBindingUniformTexelBufferUpdateAfterBind= is not enabled, all bindings with descriptor type 'VK_DESCRIPTOR_TYPE_UNIFORM_TEXEL_BUFFER must not use /VK_DESCRIPTOR_BINDING_UPDATE_AFTER_BIND_BIT_EXTIf ::2descriptorBindingStorageTexelBufferUpdateAfterBind= is not enabled, all bindings with descriptor type 'VK_DESCRIPTOR_TYPE_STORAGE_TEXEL_BUFFER must not use /VK_DESCRIPTOR_BINDING_UPDATE_AFTER_BIND_BIT_EXT'All bindings with descriptor type #VK_DESCRIPTOR_TYPE_INPUT_ATTACHMENT, )VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER_DYNAMIC , or )VK_DESCRIPTOR_TYPE_STORAGE_BUFFER_DYNAMIC must not use /VK_DESCRIPTOR_BINDING_UPDATE_AFTER_BIND_BIT_EXTIf ::)descriptorBindingUpdateUnusedWhilePending& is not enabled, all elements of  pBindingFlags must not include 9VK_DESCRIPTOR_BINDING_UPDATE_UNUSED_WHILE_PENDING_BIT_EXTIf ::descriptorBindingPartiallyBound& is not enabled, all elements of  pBindingFlags must not include -VK_DESCRIPTOR_BINDING_PARTIALLY_BOUND_BIT_EXTIf ::(descriptorBindingVariableDescriptorCount& is not enabled, all elements of  pBindingFlags must not include 7VK_DESCRIPTOR_BINDING_VARIABLE_DESCRIPTOR_COUNT_BIT_EXTIf an element of  pBindingFlags includes 7VK_DESCRIPTOR_BINDING_VARIABLE_DESCRIPTOR_COUNT_BIT_EXT, that element s descriptorType must not be )VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER_DYNAMIC or )VK_DESCRIPTOR_TYPE_STORAGE_BUFFER_DYNAMICValid Usage (Implicit)sType must be EVK_STRUCTURE_TYPE_DESCRIPTOR_SET_LAYOUT_BINDING_FLAGS_CREATE_INFO_EXTIf  bindingCount is not 0,  pBindingFlags must( be a valid pointer to an array of  bindingCount valid combinations of  valuesEach element of  pBindingFlags must not be 0See Alsos, sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure. bindingCount& is zero or the number of elements in  pBindingFlags. pBindingFlags is a pointer to an array of s8 bitfields, one for each descriptor set layout binding.VkPhysicalDeviceDescriptorIndexingPropertiesEXT - Structure describing descriptor indexing properties that can be supported by an implementationMembersThe members of the /VkPhysicalDeviceDescriptorIndexingPropertiesEXTC structure describe the following implementation-dependent limits: Description'maxUpdateAfterBindDescriptorsInAllPoolsS is the maximum number of descriptors (summed over all descriptor types) that canA be created across all pools that are created with the 3VK_DESCRIPTOR_POOL_CREATE_UPDATE_AFTER_BIND_BIT_EXT bit set. Pool creation may fail when this limit is exceeded, or when the space this limit represents can t satisfy a pool creation due to fragmentation.0shaderUniformBufferArrayNonUniformIndexingNative} is a boolean value indicating whether uniform buffer descriptors natively support nonuniform indexing. If this is VK_FALSEs, then a single dynamic instance of an instruction that nonuniformly indexes an array of uniform buffers mayD execute multiple times in order to access all the descriptors./shaderSampledImageArrayNonUniformIndexingNative is a boolean value indicating whether sampler and image descriptors natively support nonuniform indexing. If this is VK_FALSEv, then a single dynamic instance of an instruction that nonuniformly indexes an array of samplers or images mayD execute multiple times in order to access all the descriptors.0shaderStorageBufferArrayNonUniformIndexingNative} is a boolean value indicating whether storage buffer descriptors natively support nonuniform indexing. If this is VK_FALSEs, then a single dynamic instance of an instruction that nonuniformly indexes an array of storage buffers mayD execute multiple times in order to access all the descriptors./shaderStorageImageArrayNonUniformIndexingNative| is a boolean value indicating whether storage image descriptors natively support nonuniform indexing. If this is VK_FALSEr, then a single dynamic instance of an instruction that nonuniformly indexes an array of storage images mayD execute multiple times in order to access all the descriptors.2shaderInputAttachmentArrayNonUniformIndexingNative is a boolean value indicating whether input attachment descriptors natively support nonuniform indexing. If this is VK_FALSEu, then a single dynamic instance of an instruction that nonuniformly indexes an array of input attachments mayD execute multiple times in order to access all the descriptors.!robustBufferAccessUpdateAfterBind1 is a boolean value indicating whether  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-robustBufferAccess@robustBufferAccess@ can1 be enabled in a device simultaneously with -descriptorBindingUniformBufferUpdateAfterBind, -descriptorBindingStorageBufferUpdateAfterBind, 2descriptorBindingUniformTexelBufferUpdateAfterBind, and/or 2descriptorBindingStorageTexelBufferUpdateAfterBind. If this is VK_FALSE, then either robustBufferAccess must= be disabled or all of these update-after-bind features must be disabled.quadDivergentImplicitLod is a boolean value indicating whether implicit level of detail calculations for image operations have well-defined results when the image and/or sampler objects used for the instruction are not uniform within a quad. See  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#textures-derivative-image-operations Derivative Image Operations.,maxPerStageDescriptorUpdateAfterBindSamplers is similar to maxPerStageDescriptorSamplersS but counts descriptors from descriptor sets created with or without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT bit set.2maxPerStageDescriptorUpdateAfterBindUniformBuffers is similar to #maxPerStageDescriptorUniformBuffersS but counts descriptors from descriptor sets created with or without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT bit set.2maxPerStageDescriptorUpdateAfterBindStorageBuffers is similar to #maxPerStageDescriptorStorageBuffersS but counts descriptors from descriptor sets created with or without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT bit set.1maxPerStageDescriptorUpdateAfterBindSampledImages is similar to "maxPerStageDescriptorSampledImagesS but counts descriptors from descriptor sets created with or without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT bit set.1maxPerStageDescriptorUpdateAfterBindStorageImages is similar to "maxPerStageDescriptorStorageImagesS but counts descriptors from descriptor sets created with or without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT bit set.4maxPerStageDescriptorUpdateAfterBindInputAttachments is similar to %maxPerStageDescriptorInputAttachmentsS but counts descriptors from descriptor sets created with or without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT bit set.#maxPerStageUpdateAfterBindResources is similar to maxPerStageResourcesS but counts descriptors from descriptor sets created with or without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT bit set.'maxDescriptorSetUpdateAfterBindSamplers is similar to maxDescriptorSetSamplersS but counts descriptors from descriptor sets created with or without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT bit set.-maxDescriptorSetUpdateAfterBindUniformBuffers is similar to maxDescriptorSetUniformBuffersS but counts descriptors from descriptor sets created with or without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT bit set.4maxDescriptorSetUpdateAfterBindUniformBuffersDynamic is similar to %maxDescriptorSetUniformBuffersDynamicS but counts descriptors from descriptor sets created with or without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT bit set.-maxDescriptorSetUpdateAfterBindStorageBuffers is similar to maxDescriptorSetStorageBuffersS but counts descriptors from descriptor sets created with or without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT bit set.4maxDescriptorSetUpdateAfterBindStorageBuffersDynamic is similar to %maxDescriptorSetStorageBuffersDynamicS but counts descriptors from descriptor sets created with or without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT bit set.,maxDescriptorSetUpdateAfterBindSampledImages is similar to maxDescriptorSetSampledImagesS but counts descriptors from descriptor sets created with or without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT bit set.,maxDescriptorSetUpdateAfterBindStorageImages is similar to maxDescriptorSetStorageImagesS but counts descriptors from descriptor sets created with or without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT bit set./maxDescriptorSetUpdateAfterBindInputAttachments is similar to  maxDescriptorSetInputAttachmentsS but counts descriptors from descriptor sets created with or without the >VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT bit set.If the /VkPhysicalDeviceDescriptorIndexingPropertiesEXT structure is included in the pNext chain of t9, it is filled with the implementation-dependent limits.Valid Usage (Implicit)sType must be DVK_STRUCTURE_TYPE_PHYSICAL_DEVICE_DESCRIPTOR_INDEXING_PROPERTIES_EXTSee AlsoVkBool32, VkPhysicalDeviceDescriptorIndexingFeaturesEXT - Structure describing descriptor indexing features that can be supported by an implementationMembersThe members of the -VkPhysicalDeviceDescriptorIndexingFeaturesEXT, structure describe the following features: Description)shaderInputAttachmentArrayDynamicIndexing4 indicates whether arrays of input attachments can be indexed by dynamically uniform integer expressions in shader code. If this feature is not enabled, resources with a descriptor type of #VK_DESCRIPTOR_TYPE_INPUT_ATTACHMENT must be indexed only by constant integral expressions when aggregated into arrays in shader code. This also indicates whether shader modules can declare the &InputAttachmentArrayDynamicIndexingEXT capability.,shaderUniformTexelBufferArrayDynamicIndexing8 indicates whether arrays of uniform texel buffers can be indexed by dynamically uniform integer expressions in shader code. If this feature is not enabled, resources with a descriptor type of 'VK_DESCRIPTOR_TYPE_UNIFORM_TEXEL_BUFFER must be indexed only by constant integral expressions when aggregated into arrays in shader code. This also indicates whether shader modules can declare the )UniformTexelBufferArrayDynamicIndexingEXT capability.,shaderStorageTexelBufferArrayDynamicIndexing8 indicates whether arrays of storage texel buffers can be indexed by dynamically uniform integer expressions in shader code. If this feature is not enabled, resources with a descriptor type of 'VK_DESCRIPTOR_TYPE_STORAGE_TEXEL_BUFFER must be indexed only by constant integral expressions when aggregated into arrays in shader code. This also indicates whether shader modules can declare the )StorageTexelBufferArrayDynamicIndexingEXT capability.*shaderUniformBufferArrayNonUniformIndexing2 indicates whether arrays of uniform buffers can be indexed by non-uniform integer expressions in shader code. If this feature is not enabled, resources with a descriptor type of !VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER or )VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER_DYNAMIC must not be indexed by non-uniform integer expressions when aggregated into arrays in shader code. This also indicates whether shader modules can declare the 'UniformBufferArrayNonUniformIndexingEXT capability.)shaderSampledImageArrayNonUniformIndexing= indicates whether arrays of samplers or sampled images can be indexed by non-uniform integer expressions in shader code. If this feature is not enabled, resources with a descriptor type of VK_DESCRIPTOR_TYPE_SAMPLER, )VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLER , or  VK_DESCRIPTOR_TYPE_SAMPLED_IMAGE must not be indexed by non-uniform integer expressions when aggregated into arrays in shader code. This also indicates whether shader modules can declare the &SampledImageArrayNonUniformIndexingEXT capability.*shaderStorageBufferArrayNonUniformIndexing2 indicates whether arrays of storage buffers can be indexed by non-uniform integer expressions in shader code. If this feature is not enabled, resources with a descriptor type of !VK_DESCRIPTOR_TYPE_STORAGE_BUFFER or )VK_DESCRIPTOR_TYPE_STORAGE_BUFFER_DYNAMIC must not be indexed by non-uniform integer expressions when aggregated into arrays in shader code. This also indicates whether shader modules can declare the 'StorageBufferArrayNonUniformIndexingEXT capability.)shaderStorageImageArrayNonUniformIndexing1 indicates whether arrays of storage images can be indexed by non-uniform integer expressions in shader code. If this feature is not enabled, resources with a descriptor type of  VK_DESCRIPTOR_TYPE_STORAGE_IMAGE must not be indexed by non-uniform integer expressions when aggregated into arrays in shader code. This also indicates whether shader modules can declare the &StorageImageArrayNonUniformIndexingEXT capability.,shaderInputAttachmentArrayNonUniformIndexing4 indicates whether arrays of input attachments can be indexed by non-uniform integer expressions in shader code. If this feature is not enabled, resources with a descriptor type of #VK_DESCRIPTOR_TYPE_INPUT_ATTACHMENT must not be indexed by non-uniform integer expressions when aggregated into arrays in shader code. This also indicates whether shader modules can declare the )InputAttachmentArrayNonUniformIndexingEXT capability./shaderUniformTexelBufferArrayNonUniformIndexing8 indicates whether arrays of uniform texel buffers can be indexed by non-uniform integer expressions in shader code. If this feature is not enabled, resources with a descriptor type of 'VK_DESCRIPTOR_TYPE_UNIFORM_TEXEL_BUFFER must not be indexed by non-uniform integer expressions when aggregated into arrays in shader code. This also indicates whether shader modules can declare the ,UniformTexelBufferArrayNonUniformIndexingEXT capability./shaderStorageTexelBufferArrayNonUniformIndexing8 indicates whether arrays of storage texel buffers can be indexed by non-uniform integer expressions in shader code. If this feature is not enabled, resources with a descriptor type of 'VK_DESCRIPTOR_TYPE_STORAGE_TEXEL_BUFFER must not be indexed by non-uniform integer expressions when aggregated into arrays in shader code. This also indicates whether shader modules can declare the ,StorageTexelBufferArrayNonUniformIndexingEXT capability.-descriptorBindingUniformBufferUpdateAfterBind indicates whether the implementation supports updating uniform buffer descriptors after a set is bound. If this feature is not enabled, /VK_DESCRIPTOR_BINDING_UPDATE_AFTER_BIND_BIT_EXT must not be used with !VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER.,descriptorBindingSampledImageUpdateAfterBind indicates whether the implementation supports updating sampled image descriptors after a set is bound. If this feature is not enabled, /VK_DESCRIPTOR_BINDING_UPDATE_AFTER_BIND_BIT_EXT must not be used with VK_DESCRIPTOR_TYPE_SAMPLER, )VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLER , or  VK_DESCRIPTOR_TYPE_SAMPLED_IMAGE.,descriptorBindingStorageImageUpdateAfterBind indicates whether the implementation supports updating storage image descriptors after a set is bound. If this feature is not enabled, /VK_DESCRIPTOR_BINDING_UPDATE_AFTER_BIND_BIT_EXT must not be used with  VK_DESCRIPTOR_TYPE_STORAGE_IMAGE.-descriptorBindingStorageBufferUpdateAfterBind indicates whether the implementation supports updating storage buffer descriptors after a set is bound. If this feature is not enabled, /VK_DESCRIPTOR_BINDING_UPDATE_AFTER_BIND_BIT_EXT must not be used with !VK_DESCRIPTOR_TYPE_STORAGE_BUFFER.2descriptorBindingUniformTexelBufferUpdateAfterBind indicates whether the implementation supports updating uniform texel buffer descriptors after a set is bound. If this feature is not enabled, /VK_DESCRIPTOR_BINDING_UPDATE_AFTER_BIND_BIT_EXT must not be used with 'VK_DESCRIPTOR_TYPE_UNIFORM_TEXEL_BUFFER.2descriptorBindingStorageTexelBufferUpdateAfterBind indicates whether the implementation supports updating storage texel buffer descriptors after a set is bound. If this feature is not enabled, /VK_DESCRIPTOR_BINDING_UPDATE_AFTER_BIND_BIT_EXT must not be used with 'VK_DESCRIPTOR_TYPE_STORAGE_TEXEL_BUFFER.)descriptorBindingUpdateUnusedWhilePending indicates whether the implementation supports updating descriptors while the set is in use. If this feature is not enabled, 9VK_DESCRIPTOR_BINDING_UPDATE_UNUSED_WHILE_PENDING_BIT_EXT must not be used.descriptorBindingPartiallyBound indicates whether the implementation supports statically using a descriptor set binding in which some descriptors are not valid. If this feature is not enabled, -VK_DESCRIPTOR_BINDING_PARTIALLY_BOUND_BIT_EXT must not be used.(descriptorBindingVariableDescriptorCount indicates whether the implementation supports descriptor sets with a variable-sized last binding. If this feature is not enabled, 7VK_DESCRIPTOR_BINDING_VARIABLE_DESCRIPTOR_COUNT_BIT_EXT must not be used.runtimeDescriptorArray indicates whether the implementation supports the SPIR-V RuntimeDescriptorArrayEXT capability. If this feature is not enabled, descriptors must( not be declared in runtime arrays.If the -VkPhysicalDeviceDescriptorIndexingFeaturesEXT structure is included in the pNext chain of t(K, it is filled with values indicating whether each feature is supported. -VkPhysicalDeviceDescriptorIndexingFeaturesEXT can also be used in the pNext chain of ~ to enable features.Valid Usage (Implicit)sType must be BVK_STRUCTURE_TYPE_PHYSICAL_DEVICE_DESCRIPTOR_INDEXING_FEATURES_EXTSee AlsoVkBool32, ]VkDescriptorBindingFlagBitsEXT - Bitmask specifying descriptor set layout binding properties Description/VK_DESCRIPTOR_BINDING_UPDATE_AFTER_BIND_BIT_EXT indicates that if descriptors in this binding are updated between when the descriptor set is bound in a command buffer and when that command buffer is submitted to a queue, then the submission will use the most recently set descriptors for this binding and the updates do not invalidate the command buffer. Descriptor bindings created with this flag are also partially exempt from the external synchronization requirement in  and  . They can be updated concurrently with the set being bound to a command buffer in another thread, but not concurrently with the set being reset or freed.-VK_DESCRIPTOR_BINDING_PARTIALLY_BOUND_BIT_EXT> indicates that descriptors in this binding that are not dynamically used need not contain valid descriptors at the time the descriptors are consumed. A descriptor is dynamically used if any shader invocation executes an instruction that performs any memory access using the descriptor.9VK_DESCRIPTOR_BINDING_UPDATE_UNUSED_WHILE_PENDING_BIT_EXT1 indicates that descriptors in this binding can be updated after a command buffer has bound this descriptor set, or while a command buffer that uses this descriptor set is pending execution, as long as the descriptors that are updated are not used by those command buffers. If -VK_DESCRIPTOR_BINDING_PARTIALLY_BOUND_BIT_EXT$ is also set, then descriptors can] be updated as long as they are not dynamically used by any shader invocations. If -VK_DESCRIPTOR_BINDING_PARTIALLY_BOUND_BIT_EXT# is not set, then descriptors canS be updated as long as they are not statically used by any shader invocations.7VK_DESCRIPTOR_BINDING_VARIABLE_DESCRIPTOR_COUNT_BIT_EXT indicates that this descriptor binding has a variable size that will be specified when a descriptor set is allocated using this layout. The value of descriptorCountD is treated as an upper bound on the size of the binding. This mustv only be used for the last binding in the descriptor set layout (i.e. the binding with the largest value of binding<). For the purposes of counting against limits such as maxDescriptorSet* and maxPerStageDescriptor*, the full value of descriptorCount is counted.NoteNote that while /VK_DESCRIPTOR_BINDING_UPDATE_AFTER_BIND_BIT_EXT and 9VK_DESCRIPTOR_BINDING_UPDATE_UNUSED_WHILE_PENDING_BIT_EXTA both involve updates to descriptor sets after they are bound, 9VK_DESCRIPTOR_BINDING_UPDATE_UNUSED_WHILE_PENDING_BIT_EXTY is a weaker requirement since it is only about descriptors that are not used, whereas /VK_DESCRIPTOR_BINDING_UPDATE_AFTER_BIND_BIT_EXTN requires the implementation to observe updates to descriptors that are used.See Alsos3VK_DESCRIPTOR_POOL_CREATE_UPDATE_AFTER_BIND_BIT_EXT: specifies that descriptor sets allocated from this pool can include bindings with the /VK_DESCRIPTOR_BINDING_UPDATE_AFTER_BIND_BIT_EXTZ bit set. It is valid to allocate descriptor sets that have bindings that don t set the /VK_DESCRIPTOR_BINDING_UPDATE_AFTER_BIND_BIT_EXT bit from a pool that has 3VK_DESCRIPTOR_POOL_CREATE_UPDATE_AFTER_BIND_BIT_EXT set.>VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXT3 specifies that descriptor sets using this layout must8 be allocated from a descriptor pool created with the 3VK_DESCRIPTOR_POOL_CREATE_UPDATE_AFTER_BIND_BIT_EXT9 bit set. Descriptor set layouts created with this bit set have alternate limits for the maximum number of descriptors per-stage and per-pipeline layout. The non-UpdateAfterBind limits only count descriptors in sets created without this flag. The UpdateAfterBind limits count all descriptors, but the limits may/ be higher than the non-UpdateAfterBind limits.Ustuvwxyz{|}~Uyz{|}~tuvwxsNone "-STbejkRvVkDescriptorSetLayoutSupport - Structure returning information about whether a descriptor set layout can be supported Description supported is set to VK_TRUE if the descriptor set can be created, or else is set to VK_FALSE.Valid Usage (Implicit)sType must be /VK_STRUCTURE_TYPE_DESCRIPTOR_SET_LAYOUT_SUPPORTpNext must be NULL* or a pointer to a valid instance of See AlsoVkBool32, , , LsType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure. supported- specifies whether the descriptor set layout can be created.XVkPhysicalDeviceMaintenance3Properties - Structure describing descriptor set propertiesMembersThe members of the &VkPhysicalDeviceMaintenance3PropertiesC structure describe the following implementation-dependent limits: DescriptionmaxPerSetDescriptors is a maximum number of descriptors (summed over all descriptor types) in a single descriptor set that is guaranteed to satisfy any implementation-dependent constraints on the size of a descriptor set itself. Applications canY query whether a descriptor set that goes beyond this limit is supported using .maxMemoryAllocationSize6 is the maximum size of a memory allocation that canD be created, even if there is more space available in the heap.If the &VkPhysicalDeviceMaintenance3Properties structure is included in the pNext chain of sf9, it is filled with the implementation-dependent limits.Valid Usage (Implicit)sType must be :VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_MAINTENANCE_3_PROPERTIESSee Also VkDeviceSize, WvkGetDescriptorSetLayoutSupport - Query whether a descriptor set layout can be created ParametersdeviceH is the logical device that would create the descriptor set layout. pCreateInfo) is a pointer to an instance of the I structure specifying the state of the descriptor set layout object.pSupport points to a i structure in which information about support for the descriptor set layout object is returned. DescriptionSome implementations have limitations on what fits in a descriptor set which are not easily expressible in terms of existing limits like maxDescriptorSet*, for example if all descriptor types share a limited space in memory but each descriptor is a different size or alignment. This command returns information about whether a descriptor set satisfies this limit. If the descriptor set layout satisfies the ::maxPerSetDescriptors. limit, this command is guaranteed to return VK_TRUE in :: supported-. If the descriptor set layout exceeds the ::maxPerSetDescriptorsY limit, whether the descriptor set layout is supported is implementation-dependent and maye depend on whether the descriptor sizes and alignments cause the layout to exceed an internal limit.5This command does not consider other limits such as maxPerStageDescriptorO*, and so a descriptor set layout that is supported according to this command must3 still satisfy the pipeline layout limits such as maxPerStageDescriptor,* in order to be used in a pipeline layout.Note This is a VkDevice query rather than VkPhysicalDevice because the answer may depend on enabled features.Valid Usage (Implicit)device must be a valid VkDevice handle pCreateInfo must$ be a valid pointer to a valid VkDescriptorSetLayoutCreateInfo structurepSupport must be a valid pointer to a VkDescriptorSetLayoutSupport structureSee Also, , None-STejkR  None "-KSTbejkSW5uVkDescriptorUpdateTemplateCreateInfo - Structure specifying parameters of a newly created descriptor update template Valid UsageIf  templateType is 1VK_DESCRIPTOR_UPDATE_TEMPLATE_TYPE_DESCRIPTOR_SET, descriptorSetLayout must be a valid VkDescriptorSetLayout handleIf  templateType is 7VK_DESCRIPTOR_UPDATE_TEMPLATE_TYPE_PUSH_DESCRIPTORS_KHR, pipelineBindPoint must be a valid  valueIf  templateType is 7VK_DESCRIPTOR_UPDATE_TEMPLATE_TYPE_PUSH_DESCRIPTORS_KHR, pipelineLayout must be a valid VkPipelineLayout handleIf  templateType is 7VK_DESCRIPTOR_UPDATE_TEMPLATE_TYPE_PUSH_DESCRIPTORS_KHR, set musts be the unique set number in the pipeline layout that uses a descriptor set layout that was created with 7VK_DESCRIPTOR_SET_LAYOUT_CREATE_PUSH_DESCRIPTOR_BIT_KHRValid Usage (Implicit)sType must be 8VK_STRUCTURE_TYPE_DESCRIPTOR_UPDATE_TEMPLATE_CREATE_INFOpNext must be NULLflags must be 0pDescriptorUpdateEntries must( be a valid pointer to an array of descriptorUpdateEntryCount valid VkDescriptorUpdateTemplateEntry structures templateType must be a valid  valueIf descriptorSetLayout is not , descriptorSetLayout must be a valid VkDescriptorSetLayout handledescriptorUpdateEntryCount must be greater than 0Both of descriptorSetLayout, and pipelineLayout that are valid handles must? have been created, allocated, or retrieved from the same VkDeviceSee Also w, , , , , , , , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.flags is reserved for future use.descriptorUpdateEntryCount# is the number of elements in the pDescriptorUpdateEntries array.pDescriptorUpdateEntries is a pointer to an array of X structures describing the descriptors to be updated by the descriptor update template. templateTypeB Specifies the type of the descriptor update template. If set to 1VK_DESCRIPTOR_UPDATE_TEMPLATE_TYPE_DESCRIPTOR_SET it can6 only be used to update descriptor sets with a fixed descriptorSetLayout . If set to 7VK_DESCRIPTOR_UPDATE_TEMPLATE_TYPE_PUSH_DESCRIPTORS_KHR it can: only be used to push descriptor sets using the provided pipelineBindPoint, pipelineLayout, and set number.descriptorSetLayout is the descriptor set layout the parameter update template will be used with. All descriptor sets which are going to be updated through the newly created descriptor update template must be created with this layout. descriptorSetLayout is the descriptor set layout used to build the descriptor update template. All descriptor sets which are going to be updated through the newly created descriptor update template must be created with a layout that matches (is the same as, or defined identically to) this layout. This parameter is ignored if  templateType is not 1VK_DESCRIPTOR_UPDATE_TEMPLATE_TYPE_DESCRIPTOR_SET.pipelineBindPoint is a | indicating whether the descriptors will be used by graphics pipelines or compute pipelines. This parameter is ignored if  templateType is not 7VK_DESCRIPTOR_UPDATE_TEMPLATE_TYPE_PUSH_DESCRIPTORS_KHRpipelineLayout is a VkPipelineLayoutD object used to program the bindings. This parameter is ignored if  templateType is not 7VK_DESCRIPTOR_UPDATE_TEMPLATE_TYPE_PUSH_DESCRIPTORS_KHRsett is the set number of the descriptor set in the pipeline layout that will be updated. This parameter is ignored if  templateType is not 7VK_DESCRIPTOR_UPDATE_TEMPLATE_TYPE_PUSH_DESCRIPTORS_KHRiVkDescriptorUpdateTemplateEntry - Describes a single descriptor update of the descriptor update templateMembers dstBindingU is the descriptor binding to update when using this descriptor update template.dstArrayElement8 is the starting element in the array belonging to  dstBinding.descriptorCount1 is the number of descriptors to update. If descriptorCount is greater than the number of remaining array elements in the destination binding, those affect consecutive bindings in a manner similar to  above.descriptorType is a (, specifying the type of the descriptor.offsetL is the offset in bytes of the first binding in the raw data structure.stride is the stride in bytes between two consecutive array elements of the descriptor update informations in the raw data structure. The actual pointer ptr for each array element j of update entry i is computed using the following formula: w const char *ptr = (const char *)pData + pDescriptorUpdateEntries[i].offset + j * pDescriptorUpdateEntries[i].strideVThe stride is useful in case the bindings are stored in structs along with other data. Valid Usage dstBinding must be a valid binding in the descriptor set layout implicitly specified when using a descriptor update template to update descriptors.dstArrayElement and descriptorCount must be less than or equal to the number of array elements in the descriptor set binding implicitly specified when using a descriptor update template to update descriptors, and all applicable consecutive bindings, as described by phttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-updates-consecutive7{html_spec_relative}#descriptorsets-updates-consecutiveValid Usage (Implicit)descriptorType must be a valid ( valueSee Also(, KVkDescriptorUpdateTemplate - Opaque handle to a descriptor update templateSee Also, , , , , , <Dummy data to tag the  with?VkDescriptorUpdateTemplateCreateFlags - Reserved for future use Description%VkDescriptorUpdateTemplateCreateFlagsQ is a bitmask type for setting a mask, but is currently reserved for future use.See Also]VkDescriptorUpdateTemplateType - Indicates the valid usage of the descriptor update templateSee AlsolvkUpdateDescriptorSetWithTemplate - Update the contents of a descriptor set object using an update template Parametersdevice8 is the logical device that updates the descriptor sets. descriptorSet is the descriptor set to updatedescriptorUpdateTemplate is the VkDescriptorUpdateTemplate1 which specifies the update mapping between pData' and the descriptor set to update.pDataF is a pointer to memory which contains one or more structures of ,  , or $ used to write the descriptors. Valid UsagepData mustW be a valid pointer to a memory that contains one or more valid instances of ,  , or  in a layout defined by descriptorUpdateTemplate when it was created with Valid Usage (Implicit)device must be a valid VkDevice handle descriptorSet must be a valid VkDescriptorSet handledescriptorUpdateTemplate must be a valid VkDescriptorUpdateTemplate handledescriptorUpdateTemplate must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to  descriptorSet must be externally synchronized API example.  fstruct AppBufferView { VkBufferView bufferView; uint32_t applicationRelatedInformation; }; struct AppDataStructure { VkDescriptorImageInfo imageInfo; // a single image info VkDescriptorBufferInfo bufferInfoArray[3]; // 3 buffer infos in an array AppBufferView bufferView[2]; // An application defined structure containing a bufferView // ... some more application related data }; const VkDescriptorUpdateTemplateEntry descriptorUpdateTemplateEntries[] = { // binding to a single image descriptor { 0, // binding 0, // dstArrayElement 1, // descriptorCount VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLER, // descriptorType offsetof(AppDataStructure, imageInfo), // offset 0 // stride is not required if descriptorCount is 1. }, // binding to an array of buffer descriptors { 0, // binding 0, // dstArrayElement 3, // descriptorCount VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER, // descriptorType offsetof(AppDataStructure, bufferInfoArray), // offset sizeof(VkDescriptorBufferInfo) // stride, descriptor buffer infos are compact }, // binding to an array of buffer views { 0, // binding 3, // dstArrayElement 1, // descriptorCount VK_DESCRIPTOR_TYPE_STORAGE_TEXEL_BUFFER, // descriptorType offsetof(AppDataStructure, bufferView), // offset sizeof(AppBufferView) // stride, bufferViews do not have to be compact }, }; // create an descriptor update template for descriptor set updates const VkDescriptorUpdateTemplateCreateInfo createInfo = { VK_STRUCTURE_TYPE_DESCRIPTOR_UPDATE_TEMPLATE_CREATE_INFO, // sType NULL, // pNext 0, // flags 3, // descriptorUpdateEntryCount descriptorUpdateTemplateEntries, // pDescriptorUpdateEntries VK_DESCRIPTOR_UPDATE_TEMPLATE_TYPE_DESCRIPTOR_SET, // templateType myLayout, // descriptorSetLayout 0, // pipelineBindPoint, ignored by given templateType 0, // pipelineLayout, ignored by given templateType 0, // set, ignored by given templateType }; VkDescriptorUpdateTemplate myDescriptorUpdateTemplate; myResult = vkCreateDescriptorUpdateTemplate( myDevice, &createInfo, NULL, &myDescriptorUpdateTemplate); } AppDataStructure appData; // fill appData here or cache it in your engine vkUpdateDescriptorSetWithTemplate(myDevice, myDescriptorSet, myDescriptorUpdateTemplate, &appData);See Also!, , PvkDestroyDescriptorUpdateTemplate - Destroy a descriptor update template object ParametersdeviceW is the logical device that has been used to create the descriptor update templatedescriptorUpdateTemplate3 is the descriptor update template to destroy. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. Valid UsageIf VkAllocationCallbacks were provided when descriptorSetLayout1 was created, a compatible set of callbacks must be provided hereIf no VkAllocationCallbacks were provided when descriptorSetLayout was created,  pAllocator must be NULLValid Usage (Implicit)device must be a valid VkDevice handleIf descriptorUpdateTemplate is not , descriptorUpdateTemplate must be a valid VkDescriptorUpdateTemplate handleIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structureIf descriptorUpdateTemplate is a valid handle, it must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to descriptorUpdateTemplate must be externally synchronizedSee Also, , KvkCreateDescriptorUpdateTemplate - Create a new descriptor update template ParametersdeviceH is the logical device that creates the descriptor update template. pCreateInfo) is a pointer to an instance of the W structure specifying the set of descriptors to update with a single call to  or . pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter.pDescriptorUpdateTemplate points to a VkDescriptorUpdateTemplateW handle in which the resulting descriptor update template object is returned.Valid Usage (Implicit)device must be a valid VkDevice handle pCreateInfo must$ be a valid pointer to a valid $VkDescriptorUpdateTemplateCreateInfo structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structurepDescriptorUpdateTemplate must be a valid pointer to a VkDescriptorUpdateTemplate handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, , , 1VK_DESCRIPTOR_UPDATE_TEMPLATE_TYPE_DESCRIPTOR_SET] specifies that the descriptor update template will be used for descriptor set updates only.          None "-STbejkT)2,VkPhysicalDevicePushDescriptorPropertiesKHR - Structure describing push descriptor limits that can be supported by an implementationMembersThe members of the +VkPhysicalDevicePushDescriptorPropertiesKHRC structure describe the following implementation-dependent limits: DescriptionmaxPushDescriptors+ is the maximum number of descriptors that can4 be used in a descriptor set created with 7VK_DESCRIPTOR_SET_LAYOUT_CREATE_PUSH_DESCRIPTOR_BIT_KHR set.Valid Usage (Implicit)sType must be @VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_PUSH_DESCRIPTOR_PROPERTIES_KHRSee Also1{vkCmdPushDescriptorSetWithTemplateKHR - Pushes descriptor updates into a command buffer using a descriptor update template Parameters commandBufferE is the command buffer that the descriptors will be recorded in.descriptorUpdateTemplatef A descriptor update template which defines how to interpret the descriptor information in pData.layout is a VkPipelineLayout. object used to program the bindings. It must7 be compatible with the layout used to create the descriptorUpdateTemplate handle.set` is the set number of the descriptor set in the pipeline layout that will be updated. This must, be the same number used to create the descriptorUpdateTemplate handle.pDataO Points to memory which contains the descriptors for the templated update. Valid Usage[The pipelineBindPoint specified during the creation of the descriptor update template must be supported by the  commandBuffer s parent  VkCommandPool s queue familypData mustW be a valid pointer to a memory that contains one or more valid instances of ,  , or  in a layout defined by descriptorUpdateTemplate when it was created with Valid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handledescriptorUpdateTemplate must be a valid VkDescriptorUpdateTemplate handlelayout must be a valid VkPipelineLayout handle commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must- support graphics, or compute operationsEach of  commandBuffer, descriptorUpdateTemplate, and layout must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Both  Graphics Compute   API example. struct AppBufferView { VkBufferView bufferView; uint32_t applicationRelatedInformation; }; struct AppDataStructure { VkDescriptorImageInfo imageInfo; // a single image info // ... some more application related data }; const VkDescriptorUpdateTemplateEntry descriptorUpdateTemplateEntries[] = { // binding to a single image descriptor { 0, // binding 0, // dstArrayElement 1, // descriptorCount VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLER, // descriptorType offsetof(AppDataStructure, imageInfo), // offset 0 // stride is not required if descriptorCount is 1. } }; // create an descriptor update template for descriptor set updates const VkDescriptorUpdateTemplateCreateInfo createInfo = { VK_STRUCTURE_TYPE_DESCRIPTOR_UPDATE_TEMPLATE_CREATE_INFO, // sType NULL, // pNext 0, // flags 1, // descriptorUpdateEntryCount descriptorUpdateTemplateEntries, // pDescriptorUpdateEntries VK_DESCRIPTOR_UPDATE_TEMPLATE_TYPE_PUSH_DESCRIPTORS_KHR, // templateType 0, // descriptorSetLayout, ignored by given templateType VK_PIPELINE_BIND_POINT_GRAPHICS, // pipelineBindPoint myPipelineLayout, // pipelineLayout 0, // set }; VkDescriptorUpdateTemplate myDescriptorUpdateTemplate; myResult = vkCreateDescriptorUpdateTemplate( myDevice, &createInfo, NULL, &myDescriptorUpdateTemplate); } AppDataStructure appData; // fill appData here or cache it in your engine vkCmdPushDescriptorSetWithTemplateKHR(myCmdBuffer, myDescriptorUpdateTemplate, myPipelineLayout, 0,&appData);See Also, , 2LvkCmdPushDescriptorSetKHR - Pushes descriptor updates into a command buffer Parameters commandBufferE is the command buffer that the descriptors will be recorded in.pipelineBindPoint is a  indicating whether the descriptors will be used by graphics pipelines or compute pipelines. There is a separate set of push descriptor bindings for each of graphics and compute, so binding one does not disturb the other.layout is a VkPipelineLayout* object used to program the bindings.setZ is the set number of the descriptor set in the pipeline layout that will be updated.descriptorWriteCount' is the number of elements in the pDescriptorWrites array.pDescriptorWrites" is a pointer to an array of  : structures describing the descriptors to be updated. DescriptionPush descriptors# are a small bank of descriptors whose storage is internally managed by the command buffer rather than being written into a descriptor set and later bound to a command buffer. Push descriptors allow for incremental updates of descriptors without managing the lifetime of descriptor sets.hWhen a command buffer begins recording, all push descriptors have undefined contents. Push descriptors can be updated incrementally and cause shaders to use the updated descriptors for subsequent rendering commands (either compute or graphics, according to the pipelineBindPoint[) until the descriptor is overwritten, or else until the set is disturbed as described in  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-compatibilityPipeline Layout Compatibility. When the set is disturbed or push descriptors with a different descriptor set layout are set, all push descriptors become invalid.Valid descriptors must be pushed for all bindings that any shaders in a pipeline access, at the time that a draw or dispatch command is recorded to execute using that pipeline. This includes immutable sampler descriptors, which must be pushed before they are accessed by a pipeline. However, if none of the shaders in a pipeline statically use certain bindings in the push descriptor set, then those descriptors need not be valid.fPush descriptors do not use dynamic offsets. Instead, the corresponding non-dynamic descriptor types can be used and the offset member of  can1 be changed each time the descriptor is written.Each element of pDescriptorWrites is interpreted as in  , except the dstSet member is ignored.%To push an immutable sampler, use a   with  dstBinding and dstArrayElementG selecting the immutable sampler s binding. If the descriptor type is VK_DESCRIPTOR_TYPE_SAMPLER, the  pImageInfo parameter is ignored and the immutable sampler is taken from the push descriptor set layout in the pipeline layout. If the descriptor type is )VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLER, the sampler member of the  pImageInfov parameter is ignored and the immutable sampler is taken from the push descriptor set layout in the pipeline layout. Valid UsagepipelineBindPoint must be supported by the  commandBuffer s parent  VkCommandPool s queue familyset must be less than VkPipelineLayoutCreateInfo::setLayoutCount provided when layout was createdset musts be the unique set number in the pipeline layout that uses a descriptor set layout that was created with 7VK_DESCRIPTOR_SET_LAYOUT_CREATE_PUSH_DESCRIPTOR_BIT_KHRValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handlepipelineBindPoint must be a valid  valuelayout must be a valid VkPipelineLayout handlepDescriptorWrites must( be a valid pointer to an array of descriptorWriteCount valid VkWriteDescriptorSet structures commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must- support graphics, or compute operationsdescriptorWriteCount must be greater than 0Both of  commandBuffer, and layout must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Both  Graphics Compute  See Also, , ,  57VK_DESCRIPTOR_SET_LAYOUT_CREATE_PUSH_DESCRIPTOR_BIT_KHR! specifies that descriptor sets mustL not be allocated using this layout, and descriptors are instead pushed by 2.67VK_DESCRIPTOR_UPDATE_TEMPLATE_TYPE_PUSH_DESCRIPTORS_KHR_ specifies that the descriptor update template will be used for push descriptor updates only. ,-./01234567 7654321,-./0None-STejkT*;<=>?@ABCDEFGHIJGFHIJ?>=<E;DCBA@)NonejkT*STUVWXYZ[_`abcdhijklmn     CDEFGHIJKL_`abcdefghijklmnopq         `abcdefghijklm|}~)*+,-.10/23456789:;<=>?@ABCDIEFGHJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklm9:;<=>?@ABCDEFGHIJKLMNOPQTRSUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ !"#$%&'()*+-,./0123456789:;<=>?@ABCDEFGHIJKLMNOPQR]^_`abcdefghijklmnopqrstvuwxyz{|}~ !"#$%&'()*+,-./0123456789:;<=>?@ABCDEF     None "-KST]bejkhK5VkStencilFaceFlags - Bitmask of VkStencilFaceFlagBits DescriptionVkStencilFaceFlags7 is a bitmask type for setting a mask of zero or more .See Also, , , L1VkClearValue - Structure specifying a clear value DescriptionThis union is used where part of the API requires either color or depth/stencil clear values, depending on the attachment, and defines the initial clear values in the n structure. Valid Usage depthStencil must be a valid VkClearDepthStencilValue structureSee Alsoe, O, j, nO<VkClearColorValue - Structure specifying a clear color value DescriptionhThe four array elements of the clear color map to R, G, B, and A components of image formats, in order.nIf the image has more than one sample, the same value is written to all samples for any pixels being cleared.See AlsoL, SMVkDispatchIndirectCommand - Structure specifying a dispatch indirect command DescriptionThe members of VkDispatchIndirectCommand; have the same meaning as the corresponding parameters of . Valid Usagex must be less than or equal to VkPhysicalDeviceLimits::maxComputeWorkGroupCount[0]y must be less than or equal to VkPhysicalDeviceLimits::maxComputeWorkGroupCount[1]z must be less than or equal to VkPhysicalDeviceLimits::maxComputeWorkGroupCount[2]See AlsoUxB is the number of local workgroups to dispatch in the X dimension.VyB is the number of local workgroups to dispatch in the Y dimension.WzB is the number of local workgroups to dispatch in the Z dimension.XTVkDrawIndexedIndirectCommand - Structure specifying a draw indexed indirect command DescriptionThe members of VkDrawIndexedIndirectCommand= have the same meaning as the similarly named parameters of . Valid Usage>For a given vertex buffer binding, any attribute data fetched mustf be entirely contained within the corresponding vertex buffer binding, as described in \https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fxvertex-input#{html_spec_relative}#fxvertex-input( indexSize * ( firstIndex +  indexCount) + offset) mustM be less than or equal to the size of the bound index buffer, with  indexSize& being based on the type specified by  indexType, where the index buffer,  indexType, and offset are specified via vkCmdBindIndexBuffer If the  yhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-drawIndirectFirstInstancedrawIndirectFirstInstance feature is not enabled,  firstInstance must be 0See AlsoZ indexCount# is the number of vertices to draw.[ instanceCount$ is the number of instances to draw.\ firstIndex+ is the base index within the index buffer.] vertexOffsetP is the value added to the vertex index before indexing into the vertex buffer.^ firstInstance2 is the instance ID of the first instance to draw._DVkDrawIndirectCommand - Structure specifying a draw indirect command DescriptionThe members of VkDrawIndirectCommand= have the same meaning as the similarly named parameters of . Valid Usage>For a given vertex buffer binding, any attribute data fetched mustf be entirely contained within the corresponding vertex buffer binding, as described in \https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fxvertex-input#{html_spec_relative}#fxvertex-input If the  yhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-drawIndirectFirstInstancedrawIndirectFirstInstance feature is not enabled,  firstInstance must be 0See Alsoa vertexCount# is the number of vertices to draw.b instanceCount$ is the number of instances to draw.c firstVertex* is the index of the first vertex to draw.d firstInstance2 is the instance ID of the first instance to draw.e;VkClearAttachment - Structure specifying a clear attachment Description&No memory barriers are needed between vkCmdClearAttachmentsU and preceding or subsequent draw or attachment clear commands in the same subpass.The vkCmdClearAttachments6 command is not affected by the bound pipeline state. Attachments canH also be cleared at the beginning of a render pass instance by setting loadOp (or  stencilLoadOp) of  to VK_ATTACHMENT_LOAD_OP_CLEAR, as described for . Valid UsageIf  aspectMask includes VK_IMAGE_ASPECT_COLOR_BIT, it must not include VK_IMAGE_ASPECT_DEPTH_BIT or VK_IMAGE_ASPECT_STENCIL_BIT aspectMask must not include VK_IMAGE_ASPECT_METADATA_BIT clearValue must be a valid  VkClearValue unionValid Usage (Implicit) aspectMask must be a valid combination of r values aspectMask must not be 0See AlsoL, , g aspectMask_ is a mask selecting the color, depth and/or stencil aspects of the attachment to be cleared.  aspectMask can include VK_IMAGE_ASPECT_COLOR_BIT for color attachments, VK_IMAGE_ASPECT_DEPTH_BIT< for depth/stencil attachments with a depth component, and VK_IMAGE_ASPECT_STENCIL_BITh for depth/stencil attachments with a stencil component. If the subpass s depth/stencil attachment is VK_ATTACHMENT_UNUSED, then the clear has no effect.hcolorAttachment is only meaningful if VK_IMAGE_ASPECT_COLOR_BIT is set in  aspectMask', in which case it is an index to the pColorAttachments array in the T structure of the current subpass which selects the color attachment to clear. If colorAttachment is VK_ATTACHMENT_UNUSED then the clear has no effect.i clearValueR is the color or depth/stencil value to clear the attachment to, as described in  [https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#clears-values Clear Values below.jLVkClearDepthStencilValue - Structure specifying a clear depth stencil value Valid Usage Unless the 4{html_spec_relative}#VK_EXT_depth_range_unrestricted extension is enabled depth must be between 0.0 and 1.0, inclusiveSee AlsoL, ldepth is the clear value for the depth aspect of the depth/stencil attachment. It is a floating-point value which is automatically converted to the attachment s format.mstencil is the clear value for the stencil aspect of the depth/stencil attachment. It is a 32-bit integer value which is converted to the attachment s format by taking the appropriate number of LSBs.nCVkRenderPassBeginInfo - Structure specifying render pass begin info Description renderArea is the render area that is affected by the render pass instance. The effects of attachment load, store and multisample resolve operations are restricted to the pixels whose x and y coordinates fall within the render area on all attachments. The render area extends to all layers of  framebuffer. The application must ensure (using scissor if necessary) that all rendering is contained within the render area, otherwise the pixels outside of the render area become undefined and shader side effects may? occur for fragments outside the render area. The render area must1 be contained within the framebuffer dimensions.pWhen multiview is enabled, the resolve operation at the end of a subpass applies to all views in the view mask.NoteThere may be a performance cost for using a render area smaller than the framebuffer, unless it matches the render area granularity for the render pass. Valid UsageclearValueCount must6 be greater than the largest attachment index in  renderPass that specifies a loadOp (or  stencilLoadOp=, if the attachment has a depth/stencil format) of VK_ATTACHMENT_LOAD_OP_CLEARIf clearValueCount is not 0,  pClearValues must( be a valid pointer to an array of clearValueCount valid  VkClearValue unions renderPass must be  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#renderpass-compatibility compatible with the  renderPass member of the VkFramebufferCreateInfo( structure specified when creating  framebuffer.Valid Usage (Implicit)sType must be (VK_STRUCTURE_TYPE_RENDER_PASS_BEGIN_INFOEach pNext: member of any structure (including this one) in the pNext chain must be either NULL/ or a pointer to a valid instance of  or [Each sType member in the pNext chain must be unique renderPass must be a valid  VkRenderPass handle framebuffer must be a valid  VkFramebuffer handleBoth of  framebuffer, and  renderPass must? have been created, allocated, or retrieved from the same VkDeviceSee AlsoL, , , , , psType is the type of this structure.qpNext is NULL1 or a pointer to an extension-specific structure.r renderPass, is the render pass to begin an instance of.s framebufferS is the framebuffer containing the attachments that are used with the render pass.t renderAreai is the render area that is affected by the render pass instance, and is described in more detail below.uclearValueCount is the number of elements in  pClearValues.v pClearValues is an array of LV structures that contains clear values for each attachment, if the attachment uses a loadOp value of VK_ATTACHMENT_LOAD_OP_CLEAR= or if the attachment has a depth/stencil format and uses a  stencilLoadOp value of VK_ATTACHMENT_LOAD_OP_CLEAR~. The array is indexed by attachment number. Only elements corresponding to cleared attachments are used. Other elements of  pClearValues are ignored.w@VkImageResolve - Structure specifying an image resolve operation Valid UsageThe  aspectMask member of srcSubresource and dstSubresource must only contain VK_IMAGE_ASPECT_COLOR_BIT The  layerCount member of srcSubresource and dstSubresource must match#If either of the calling command s srcImage or dstImage parameters are of /* VK_IMAGE_TYPE_3D, the baseArrayLayer and  layerCount members of both srcSubresource and dstSubresource must be 0 and 1, respectively srcOffset.x and ( extent.width +  srcOffset.x) must' both be greater than or equal to 0B and less than or equal to the source image subresource width srcOffset.y and ( extent.height +  srcOffset.y) must' both be greater than or equal to 0C and less than or equal to the source image subresource heightIf the calling command s srcImage is of type VK_IMAGE_TYPE_1D , then  srcOffset.y must be 0 and  extent.height must be 1. srcOffset.z and ( extent.depth +  srcOffset.z) must' both be greater than or equal to 0B and less than or equal to the source image subresource depthIf the calling command s srcImage is of type VK_IMAGE_TYPE_1D or VK_IMAGE_TYPE_2D, then  srcOffset.z must be 0 and  extent.depth must be 1. dstOffset.x and ( extent.width +  dstOffset.x) must' both be greater than or equal to 0G and less than or equal to the destination image subresource width dstOffset.y and ( extent.height +  dstOffset.y) must' both be greater than or equal to 0H and less than or equal to the destination image subresource heightIf the calling command s dstImage is of type VK_IMAGE_TYPE_1D , then  dstOffset.y must be 0 and  extent.height must be 1. dstOffset.z and ( extent.depth +  dstOffset.z) must' both be greater than or equal to 0G and less than or equal to the destination image subresource depthIf the calling command s dstImage is of type VK_IMAGE_TYPE_1D or VK_IMAGE_TYPE_2D, then  dstOffset.z must be 0 and  extent.depth must be 1.Valid Usage (Implicit)srcSubresource must be a valid VkImageSubresourceLayers structuredstSubresource must be a valid VkImageSubresourceLayers structureSee Also, , , ysrcSubresource and dstSubresource are  structures specifying the image subresources of the images used for the source and destination image data, respectively. Resolve of depth/stencil images is not supported.z srcOffset and  dstOffset select the initial x, y, and zP offsets in texels of the sub-regions of the source and destination image data.}extent: is the size in texels of the source image to resolve in width, height and depth.~FVkBufferImageCopy - Structure specifying a buffer image copy operation DescriptionWhen copying to or from a depth or stencil aspect, the data in buffer memory uses a layout that is a (mostly) tightly packed representation of the depth or stencil data. Specifically:fdata copied to or from the stencil aspect of any depth/stencil format is tightly packed with one VK_FORMAT_S8_UINT value per texel.-data copied to or from the depth aspect of a VK_FORMAT_D16_UNORM or VK_FORMAT_D16_UNORM_S8_UINT( format is tightly packed with one VK_FORMAT_D16_UNORM value per texel.-data copied to or from the depth aspect of a VK_FORMAT_D32_SFLOAT or VK_FORMAT_D32_SFLOAT_S8_UINT( format is tightly packed with one VK_FORMAT_D32_SFLOAT value per texel.2data copied to or from the depth aspect of a VK_FORMAT_X8_D24_UNORM_PACK32 or VK_FORMAT_D24_UNORM_S8_UINT format is packed with one 32-bit word per texel with the D24 value in the LSBs of the word, and undefined values in the eight MSBs.NoteVTo copy both the depth and stencil aspects of a depth/stencil format, two entries in pRegions can3 be used, where one specifies the depth aspect in imageSubresource., and the other specifies the stencil aspect.7Because depth or stencil aspect buffer to image copies may require format conversions on some implementations, they are not supported on queues that do not support graphics. When copying to a depth aspect, the data in buffer memory must7 be in the the range [0,1] or undefined results occur.:Copies are done layer by layer starting with image layer baseArrayLayer member of imageSubresource.  layerCountF layers are copied from the source image or to the destination image. Valid UsageIf the calling command s VkImage< parameter s format is not a depth/stencil format or a  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversionmulti-planar format , then  bufferOffset must0 be a multiple of the format s element sizeIf the calling command s VkImage parameter s format is a  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversionmulti-planar format , then  bufferOffset mustX be a multiple of the element size of the compatible format for the format and the  aspectMask of the imageSubresource as defined in phttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-compatible-planes7{html_spec_relative}#features-formats-compatible-planes bufferOffset must be a multiple of 4bufferRowLength must be 0', or greater than or equal to the width member of  imageExtentbufferImageHeight must be 0', or greater than or equal to the height member of  imageExtent imageOffset.x and (imageExtent.width +  imageOffset.x) must' both be greater than or equal to 0g and less than or equal to the image subresource width where this refers to the width of the plane9 of the image involved in the copy in the case of a https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversionmulti-planar format imageOffset.y and (imageExtent.height +  imageOffset.y) must' both be greater than or equal to 0i and less than or equal to the image subresource height where this refers to the height of the plane9 of the image involved in the copy in the case of a https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversionmulti-planar formatIf the calling command s srcImage ( ) or dstImage ( ) is of type VK_IMAGE_TYPE_1D , then  imageOffset.y must be 0 and imageExtent.height must be 1. imageOffset.z and (imageExtent.depth +  imageOffset.z) must' both be greater than or equal to 0; and less than or equal to the image subresource depthIf the calling command s srcImage ( ) or dstImage ( ) is of type VK_IMAGE_TYPE_1D or VK_IMAGE_TYPE_2D, then  imageOffset.z must be 0 and imageExtent.depth must be 1If the calling command s VkImage, parameter is a compressed image, or a  single-plane, _422  image format, bufferRowLength must7 be a multiple of the compressed texel block widthIf the calling command s VkImage, parameter is a compressed image, or a  single-plane, _422  image format, bufferImageHeight must3 be a multiple of the compressed texel block heightIf the calling command s VkImage, parameter is a compressed image, or a  single-plane, _422$  image format, all members of  imageOffset mustQ be a multiple of the corresponding dimensions of the compressed texel blockIf the calling command s VkImage, parameter is a compressed image, or a  single-plane, _422  image format,  bufferOffset must? be a multiple of the compressed texel block size in bytesIf the calling command s VkImage, parameter is a compressed image, or a  single-plane, _422  image format, imageExtent.width must< be a multiple of the compressed texel block width or (imageExtent.width +  imageOffset.x) must' equal the image subresource widthIf the calling command s VkImage, parameter is a compressed image, or a  single-plane, _422  image format, imageExtent.height must= be a multiple of the compressed texel block height or (imageExtent.height +  imageOffset.y) must( equal the image subresource heightIf the calling command s VkImage, parameter is a compressed image, or a  single-plane, _422  image format, imageExtent.depth must< be a multiple of the compressed texel block depth or (imageExtent.depth +  imageOffset.z) must' equal the image subresource depthThe  aspectMask member of imageSubresource must7 specify aspects present in the calling command s VkImage parameterIf the calling command s VkImage parameter s format is a  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversionmulti-planar format, then the  aspectMask member of imageSubresource must be VK_IMAGE_ASPECT_PLANE_0_BIT, VK_IMAGE_ASPECT_PLANE_1_BIT , or VK_IMAGE_ASPECT_PLANE_2_BIT (with VK_IMAGE_ASPECT_PLANE_2_BIT5 valid only for image formats with three planes)The  aspectMask member of imageSubresource must only have a single bit setIf the calling command s VkImage parameter is of /* VK_IMAGE_TYPE_3D, the baseArrayLayer and  layerCount members of imageSubresource must be 0 and 1, respectively]When copying to the depth aspect of an image subresource, the data in the source buffer must be in the range [0,1]Valid Usage (Implicit)imageSubresource must be a valid VkImageSubresourceLayers structureSee Also VkDeviceSize, , , , ,  bufferOffsetg is the offset in bytes from the start of the buffer object where the image data is copied from or to.bufferRowLength and bufferImageHeight specify the data in buffer memory as a subregion of a larger two- or three-dimensional image, and control the addressing calculations of data in buffer memory. If either of these values is zero, that aspect of the buffer memory is considered to be tightly packed according to the  imageExtent.imageSubresource is a n used to specify the specific image subresources of the image used for the source or destination image data. imageOffset selects the initial x, y, zN offsets in texels of the sub-region of the source or destination image data. imageExtent/ is the size in texels of the image to copy in width, height and depth.:VkImageBlit - Structure specifying an image blit operation DescriptionFor each element of the pRegionsT array, a blit operation is performed the specified source and destination regions. Valid UsageThe  aspectMask member of srcSubresource and dstSubresource must matchThe  layerCount member of srcSubresource and dstSubresource must match#If either of the calling command s srcImage or dstImage parameters are of /* VK_IMAGE_TYPE_3D, the baseArrayLayer and  layerCount members of both srcSubresource and dstSubresource must be 0 and 1, respectivelyThe  aspectMask member of srcSubresource must7 specify aspects present in the calling command s srcImageThe  aspectMask member of dstSubresource must7 specify aspects present in the calling command s dstImage srcOffset[0].x and  srcOffset[1].x must' both be greater than or equal to 0B and less than or equal to the source image subresource width srcOffset[0].y and  srcOffset[1].y must' both be greater than or equal to 0C and less than or equal to the source image subresource heightIf the calling command s srcImage is of type VK_IMAGE_TYPE_1D , then  srcOffset[0].y must be 0 and  srcOffset[1].y must be 1. srcOffset[0].z and  srcOffset[1].z must' both be greater than or equal to 0B and less than or equal to the source image subresource depthIf the calling command s srcImage is of type VK_IMAGE_TYPE_1D or VK_IMAGE_TYPE_2D, then  srcOffset[0].z must be 0 and  srcOffset[1].z must be 1. dstOffset[0].x and  dstOffset[1].x must' both be greater than or equal to 0G and less than or equal to the destination image subresource width dstOffset[0].y and  dstOffset[1].y must' both be greater than or equal to 0H and less than or equal to the destination image subresource heightIf the calling command s dstImage is of type VK_IMAGE_TYPE_1D , then  dstOffset[0].y must be 0 and  dstOffset[1].y must be 1. dstOffset[0].z and  dstOffset[1].z must' both be greater than or equal to 0G and less than or equal to the destination image subresource depthIf the calling command s dstImage is of type VK_IMAGE_TYPE_1D or VK_IMAGE_TYPE_2D, then  dstOffset[0].z must be 0 and  dstOffset[1].z must be 1.Valid Usage (Implicit)srcSubresource must be a valid VkImageSubresourceLayers structuredstSubresource must be a valid VkImageSubresourceLayers structureSee Also, , srcSubresource! is the subresource to blit from. srcOffsets is an array of two @ structures specifying the bounds of the source region within srcSubresource.dstSubresource! is the subresource to blit into. dstOffsets is an array of two E structures specifying the bounds of the destination region within dstSubresource.:VkImageCopy - Structure specifying an image copy operation DescriptionFor VK_IMAGE_TYPE_3D@ images, copies are performed slice by slice starting with the z member of the  srcOffset or  dstOffset, and copying deptha slices. For images with multiple layers, copies are performed layer by layer starting with the baseArrayLayer member of the srcSubresource or dstSubresource and copying  layerCount layers. Image data canG be copied between images with different image types. If one image is VK_IMAGE_TYPE_3D and the other image is VK_IMAGE_TYPE_2DO with multiple layers, then each slice is copied to or from a different layer.Copies involving a  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversionmulti-planar image format2 specify the region to be copied in terms of the planet to be copied, not the coordinates of the multi-planar image. This means that copies accessing the R/B planes of _422  format images must( fit the copied region within half the widthD of the parent image, and that copies accessing the R/B planes of _420  format images must( fit the copied region within half the width and height of the parent image. Valid Usage!If neither the calling command s srcImage nor the calling command s dstImage has a  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversionmulti-planar image format then the  aspectMask member of srcSubresource and dstSubresource must match!If the calling command s srcImage has a  with  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversiontwo planes then the srcSubresource  aspectMask must be VK_IMAGE_ASPECT_PLANE_0_BIT or VK_IMAGE_ASPECT_PLANE_1_BITIf the calling command s srcImage has a  with  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversionthree planes then the srcSubresource  aspectMask must be VK_IMAGE_ASPECT_PLANE_0_BIT, VK_IMAGE_ASPECT_PLANE_1_BIT , or VK_IMAGE_ASPECT_PLANE_2_BITIf the calling command s dstImage has a  with  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversiontwo planes then the dstSubresource  aspectMask must be VK_IMAGE_ASPECT_PLANE_0_BIT or VK_IMAGE_ASPECT_PLANE_1_BITIf the calling command s dstImage has a  with  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversionthree planes then the dstSubresource  aspectMask must be VK_IMAGE_ASPECT_PLANE_0_BIT, VK_IMAGE_ASPECT_PLANE_1_BIT , or VK_IMAGE_ASPECT_PLANE_2_BITIf the calling command s srcImage has a  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversionmulti-planar image format and the dstImage5 does not have a multi-planar image format, the dstSubresource  aspectMask must be VK_IMAGE_ASPECT_COLOR_BITIf the calling command s dstImage has a  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversionmulti-planar image format and the srcImage5 does not have a multi-planar image format, the srcSubresource  aspectMask must be VK_IMAGE_ASPECT_COLOR_BITThe number of slices of the extent (for 3D) or layers of the srcSubresource (for non-3D) must( match the number of slices of the extent (for 3D) or layers of the dstSubresource (for non-3D)#If either of the calling command s srcImage or dstImage parameters are of /* VK_IMAGE_TYPE_3D, the baseArrayLayer and  layerCount/ members of the corresponding subresource must be 0 and 1, respectivelyThe  aspectMask member of srcSubresource must7 specify aspects present in the calling command s srcImageThe  aspectMask member of dstSubresource must7 specify aspects present in the calling command s dstImage srcOffset.x and ( extent.width +  srcOffset.x) must' both be greater than or equal to 0B and less than or equal to the source image subresource width srcOffset.y and ( extent.height +  srcOffset.y) must' both be greater than or equal to 0C and less than or equal to the source image subresource heightIf the calling command s srcImage is of type VK_IMAGE_TYPE_1D , then  srcOffset.y must be 0 and  extent.height must be 1. srcOffset.z and ( extent.depth +  srcOffset.z) must' both be greater than or equal to 0B and less than or equal to the source image subresource depthIf the calling command s srcImage is of type VK_IMAGE_TYPE_1D , then  srcOffset.z must be 0 and  extent.depth must be 1.If the calling command s dstImage is of type VK_IMAGE_TYPE_1D , then  dstOffset.z must be 0 and  extent.depth must be 1.If the calling command s srcImage is of type VK_IMAGE_TYPE_2D , then  srcOffset.z must be 0.If the calling command s dstImage is of type VK_IMAGE_TYPE_2D , then  dstOffset.z must be 0.If both srcImage and dstImage are of type VK_IMAGE_TYPE_2D then then  extent.depth must be 1.If the calling command s srcImage is of type VK_IMAGE_TYPE_2D, and the dstImage is of type VK_IMAGE_TYPE_3D , then  extent.depth must equal to the  layerCount member of srcSubresource.If the calling command s dstImage is of type VK_IMAGE_TYPE_2D, and the srcImage is of type VK_IMAGE_TYPE_3D , then  extent.depth must equal to the  layerCount member of dstSubresource. dstOffset.x and ( extent.width +  dstOffset.x) must' both be greater than or equal to 0G and less than or equal to the destination image subresource width dstOffset.y and ( extent.height +  dstOffset.y) must' both be greater than or equal to 0H and less than or equal to the destination image subresource heightIf the calling command s dstImage is of type VK_IMAGE_TYPE_1D , then  dstOffset.y must be 0 and  extent.height must be 1. dstOffset.z and ( extent.depth +  dstOffset.z) must' both be greater than or equal to 0G and less than or equal to the destination image subresource depthIf the calling command s srcImage" is a compressed image, or a  single-plane, _422  image format, all members of  srcOffset mustQ be a multiple of the corresponding dimensions of the compressed texel blockIf the calling command s srcImage" is a compressed image, or a  single-plane, _422  image format,  extent.width must< be a multiple of the compressed texel block width or ( extent.width +  srcOffset.x) must) equal the source image subresource widthIf the calling command s srcImage" is a compressed image, or a  single-plane, _422  image format,  extent.height must= be a multiple of the compressed texel block height or ( extent.height +  srcOffset.y) must* equal the source image subresource heightIf the calling command s srcImage" is a compressed image, or a  single-plane, _422  image format,  extent.depth must< be a multiple of the compressed texel block depth or ( extent.depth +  srcOffset.z) must) equal the source image subresource depthIf the calling command s dstImage) is a compressed format image, or a  single-plane, _422  image format, all members of  dstOffset mustQ be a multiple of the corresponding dimensions of the compressed texel blockIf the calling command s dstImage) is a compressed format image, or a  single-plane, _422  image format,  extent.width must< be a multiple of the compressed texel block width or ( extent.width +  dstOffset.x) must. equal the destination image subresource widthIf the calling command s dstImage) is a compressed format image, or a  single-plane, _422  image format,  extent.height must= be a multiple of the compressed texel block height or ( extent.height +  dstOffset.y) must/ equal the destination image subresource heightIf the calling command s dstImage) is a compressed format image, or a  single-plane, _422  image format,  extent.depth must< be a multiple of the compressed texel block depth or ( extent.depth +  dstOffset.z) must. equal the destination image subresource depthValid Usage (Implicit)srcSubresource must be a valid VkImageSubresourceLayers structuredstSubresource must be a valid VkImageSubresourceLayers structureSee Also, , , srcSubresource and dstSubresource are { structures specifying the image subresources of the images used for the source and destination image data, respectively. srcOffset and  dstOffset select the initial x, y, and zP offsets in texels of the sub-regions of the source and destination image data.extent/ is the size in texels of the image to copy in width, height and depth.;VkBufferCopy - Structure specifying a buffer copy operationSee Also VkDeviceSize,  srcOffset4 is the starting offset in bytes from the start of  srcBuffer. dstOffset4 is the starting offset in bytes from the start of  dstBuffer.size is the number of bytes to copy.VVkImageMemoryBarrier - Structure specifying the parameters of an image memory barrier Description The first  xhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-dependencies-access-scopes access scopei is limited to access to memory through the specified image subresource range, via access types in the  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-access-maskssource access mask specified by  srcAccessMask. If  srcAccessMask includes VK_ACCESS_HOST_WRITE_BIT, memory writes performed by that access type are also made visible, as that access type is not performed through a resource. The second  xhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-dependencies-access-scopes access scopei is limited to access to memory through the specified image subresource range, via access types in the  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-access-masksdestination access mask specified by  dstAccessMask. If  dstAccessMask includes VK_ACCESS_HOST_WRITE_BIT or VK_ACCESS_HOST_READ_BIT, available memory writes are also made visible to accesses of those types, as those access types are not performed through a resource.If srcQueueFamilyIndex is not equal to dstQueueFamilyIndex, and srcQueueFamilyIndexJ is equal to the current queue family, then the memory barrier defines a  uhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-queue-transfers-releasequeue family release operationd for the specified image subresource range, and the second access scope includes no access, as if  dstAccessMask was 0.If dstQueueFamilyIndex is not equal to srcQueueFamilyIndex, and dstQueueFamilyIndexJ is equal to the current queue family, then the memory barrier defines a  uhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-queue-transfers-acquirequeue family acquire operationc for the specified image subresource range, and the first access scope includes no access, as if  srcAccessMask was 0.If  oldLayout is not equal to  newLayout&, then the memory barrier defines an  vhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-image-layout-transitionsimage layout transition, for the specified image subresource range.^Layout transitions that are performed via image memory barriers execute in their entirety in  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-submission-ordersubmission orderi, relative to other image layout transitions submitted to the same queue, including those performed by  Xhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#renderpassrender passes. In effect there is an implicit execution dependency from each such layout transition to all layout transitions previously submitted to the same queue.RThe image layout of each image subresource of a depth/stencil image created with 9VK_IMAGE_CREATE_SAMPLE_LOCATIONS_COMPATIBLE_DEPTH_BIT_EXT is dependent on the last sample locations used to render to the image subresource as a depth/stencil attachment, thus when the image member of an VkImageMemoryBarrier5 is an image created with this flag the application can chain a [ structure to the pNext chain of VkImageMemoryBarrierL to specify the sample locations to use during the image layout transition.If the VkSampleLocationsInfoEXT structure in the pNext chain of VkImageMemoryBarrierl does not match the sample location state last used to render to the image subresource range specified by subresourceRange or if no VkSampleLocationsInfoEXT structure is in the pNext chain of VkImageMemoryBarrierQ then the contents of the given image subresource range becomes undefined as if  oldLayout would equal VK_IMAGE_LAYOUT_UNDEFINED.If image, has a multi-planar format and the image is disjoint, then including VK_IMAGE_ASPECT_COLOR_BIT in the  aspectMask member of subresourceRange is equivalent to including VK_IMAGE_ASPECT_PLANE_0_BIT, VK_IMAGE_ASPECT_PLANE_1_BIT&, and (for three-plane formats only) VK_IMAGE_ASPECT_PLANE_2_BIT. Valid Usage oldLayout must be VK_IMAGE_LAYOUT_UNDEFINEDM or the current layout of the image subresources affected by the barrier newLayout must not be VK_IMAGE_LAYOUT_UNDEFINED or VK_IMAGE_LAYOUT_PREINITIALIZEDIf image) was created with a sharing mode of VK_SHARING_MODE_CONCURRENT, at least one of srcQueueFamilyIndex and dstQueueFamilyIndex must be VK_QUEUE_FAMILY_IGNOREDIf image) was created with a sharing mode of VK_SHARING_MODE_CONCURRENT , and one of srcQueueFamilyIndex and dstQueueFamilyIndex is VK_QUEUE_FAMILY_IGNORED , the other must be VK_QUEUE_FAMILY_IGNORED] or a special queue family reserved for external memory transfers, as described in  mhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-queue-transfers4{html_spec_relative}#synchronization-queue-transfers.If image) was created with a sharing mode of VK_SHARING_MODE_EXCLUSIVE and srcQueueFamilyIndex is VK_QUEUE_FAMILY_IGNORED, dstQueueFamilyIndex must also be VK_QUEUE_FAMILY_IGNORED.If image) was created with a sharing mode of VK_SHARING_MODE_EXCLUSIVE and srcQueueFamilyIndex is not VK_QUEUE_FAMILY_IGNORED, it mustz be a valid queue family or a special queue family reserved for external memory transfers, as described in  mhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-queue-transfers4{html_spec_relative}#synchronization-queue-transfers.If image) was created with a sharing mode of VK_SHARING_MODE_EXCLUSIVE and dstQueueFamilyIndex is not VK_QUEUE_FAMILY_IGNORED, it mustz be a valid queue family or a special queue family reserved for external memory transfers, as described in  mhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-queue-transfers4{html_spec_relative}#synchronization-queue-transfers.If image) was created with a sharing mode of VK_SHARING_MODE_EXCLUSIVE, and srcQueueFamilyIndex and dstQueueFamilyIndex are not VK_QUEUE_FAMILY_IGNORED, at least one of them mustK be the same as the family of the queue that will execute this barriersubresourceRange.baseMipLevel must be less than the  mipLevels specified in * when image was createdIf subresourceRange.levelCount is not VK_REMAINING_MIP_LEVELS, subresourceRange.baseMipLevel + subresourceRange.levelCount must be less than or equal to the  mipLevels specified in * when image was createdsubresourceRange.baseArrayLayer must be less than the  arrayLayers specified in * when image was createdIf subresourceRange.layerCount is not VK_REMAINING_ARRAY_LAYERS, subresourceRange.baseArrayLayer + subresourceRange.layerCount must be less than or equal to the  arrayLayers specified in * when image was createdIf imageR has a depth/stencil format with both depth and stencil components, then the  aspectMask member of subresourceRange must include both VK_IMAGE_ASPECT_DEPTH_BIT and VK_IMAGE_ASPECT_STENCIL_BITIf image+ has a single-plane color format or is not disjoint, then the  aspectMask member of subresourceRange must be VK_IMAGE_ASPECT_COLOR_BITIf image, has a multi-planar format and the image is disjoint, then the  aspectMask member of subresourceRange must% include either at least one of VK_IMAGE_ASPECT_PLANE_0_BIT, VK_IMAGE_ASPECT_PLANE_1_BIT, and VK_IMAGE_ASPECT_PLANE_2_BIT ; or must include VK_IMAGE_ASPECT_COLOR_BITIf image? has a multi-planar format with only two planes, then the  aspectMask member of subresourceRange must not include VK_IMAGE_ASPECT_PLANE_2_BIT If either  oldLayout or  newLayout is (VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL then image must have been created with #VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT set If either  oldLayout or  newLayout is 0VK_IMAGE_LAYOUT_DEPTH_STENCIL_ATTACHMENT_OPTIMAL then image must have been created with +VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT set If either  oldLayout or  newLayout is /VK_IMAGE_LAYOUT_DEPTH_STENCIL_READ_ONLY_OPTIMAL then image must have been created with +VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT set If either  oldLayout or  newLayout is :VK_IMAGE_LAYOUT_DEPTH_READ_ONLY_STENCIL_ATTACHMENT_OPTIMAL then image must have been created with +VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT set If either  oldLayout or  newLayout is :VK_IMAGE_LAYOUT_DEPTH_ATTACHMENT_STENCIL_READ_ONLY_OPTIMAL then image must have been created with +VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT set If either  oldLayout or  newLayout is (VK_IMAGE_LAYOUT_SHADER_READ_ONLY_OPTIMAL then image must have been created with VK_IMAGE_USAGE_SAMPLED_BIT or #VK_IMAGE_USAGE_INPUT_ATTACHMENT_BIT set If either  oldLayout or  newLayout is $VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL then image must have been created with VK_IMAGE_USAGE_TRANSFER_SRC_BIT set If either  oldLayout or  newLayout is $VK_IMAGE_LAYOUT_TRANSFER_DST_OPTIMAL then image must have been created with VK_IMAGE_USAGE_TRANSFER_DST_BIT setValid Usage (Implicit)sType must be &VK_STRUCTURE_TYPE_IMAGE_MEMORY_BARRIERpNext must be NULL* or a pointer to a valid instance of [ srcAccessMask must be a valid combination of + values dstAccessMask must be a valid combination of + values oldLayout must be a valid  value newLayout must be a valid  valueimage must be a valid VkImage handlesubresourceRange must be a valid VkImageSubresourceRange structureSee Also, 2, , , , , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure. srcAccessMask is a bitmask of + specifying a  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-access-maskssource access mask. dstAccessMask is a bitmask of + specifying a  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-access-masksdestination access mask. oldLayout is the old layout in an  vhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-image-layout-transitionsimage layout transition. newLayout is the new layout in an  vhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-image-layout-transitionsimage layout transition.srcQueueFamilyIndex" is the source queue family for a  mhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-queue-transfers!queue family ownership transfer.dstQueueFamilyIndex' is the destination queue family for a  mhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-queue-transfers!queue family ownership transfer.image3 is a handle to the image affected by this barrier.subresourceRange describes the  chttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#resources-image-viewsimage subresource range within image" that is affected by this barrier.DVkBufferMemoryBarrier - Structure specifying a buffer memory barrier Description The first  xhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-dependencies-access-scopes access scope^ is limited to access to memory through the specified buffer range, via access types in the  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-access-maskssource access mask specified by  srcAccessMask. If  srcAccessMask includes VK_ACCESS_HOST_WRITE_BIT, memory writes performed by that access type are also made visible, as that access type is not performed through a resource. The second  xhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-dependencies-access-scopes access scope^ is limited to access to memory through the specified buffer range, via access types in the  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-access-masksdestination access mask. specified by  dstAccessMask. If  dstAccessMask includes VK_ACCESS_HOST_WRITE_BIT or VK_ACCESS_HOST_READ_BIT, available memory writes are also made visible to accesses of those types, as those access types are not performed through a resource.If srcQueueFamilyIndex is not equal to dstQueueFamilyIndex, and srcQueueFamilyIndexJ is equal to the current queue family, then the memory barrier defines a  uhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-queue-transfers-releasequeue family release operationY for the specified buffer range, and the second access scope includes no access, as if  dstAccessMask was 0.If dstQueueFamilyIndex is not equal to srcQueueFamilyIndex, and dstQueueFamilyIndexJ is equal to the current queue family, then the memory barrier defines a  uhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-queue-transfers-acquirequeue family acquire operationX for the specified buffer range, and the first access scope includes no access, as if  srcAccessMask was 0. Valid Usageoffset must be less than the size of bufferIf size is not equal to  VK_WHOLE_SIZE, size must be greater than 0If size is not equal to  VK_WHOLE_SIZE, size must0 be less than or equal to than the size of buffer minus offsetIf buffer) was created with a sharing mode of VK_SHARING_MODE_CONCURRENT, at least one of srcQueueFamilyIndex and dstQueueFamilyIndex must be VK_QUEUE_FAMILY_IGNOREDIf buffer) was created with a sharing mode of VK_SHARING_MODE_CONCURRENT , and one of srcQueueFamilyIndex and dstQueueFamilyIndex is VK_QUEUE_FAMILY_IGNORED , the other must be VK_QUEUE_FAMILY_IGNOREDg or a special queue family reserved for external memory ownership transfers, as described in  mhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-queue-transfers4{html_spec_relative}#synchronization-queue-transfers.If buffer) was created with a sharing mode of VK_SHARING_MODE_EXCLUSIVE and srcQueueFamilyIndex is VK_QUEUE_FAMILY_IGNORED, dstQueueFamilyIndex must also be VK_QUEUE_FAMILY_IGNOREDIf buffer) was created with a sharing mode of VK_SHARING_MODE_EXCLUSIVE and srcQueueFamilyIndex is not VK_QUEUE_FAMILY_IGNORED, it mustz be a valid queue family or a special queue family reserved for external memory transfers, as described in  mhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-queue-transfers4{html_spec_relative}#synchronization-queue-transfers.If buffer) was created with a sharing mode of VK_SHARING_MODE_EXCLUSIVE and dstQueueFamilyIndex is not VK_QUEUE_FAMILY_IGNORED, it mustz be a valid queue family or a special queue family reserved for external memory transfers, as described in  mhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-queue-transfers4{html_spec_relative}#synchronization-queue-transfers.If buffer) was created with a sharing mode of VK_SHARING_MODE_EXCLUSIVE, and srcQueueFamilyIndex and dstQueueFamilyIndex are not VK_QUEUE_FAMILY_IGNORED, at least one of them mustK be the same as the family of the queue that will execute this barrierValid Usage (Implicit)sType must be 'VK_STRUCTURE_TYPE_BUFFER_MEMORY_BARRIERpNext must be NULL srcAccessMask must be a valid combination of + values dstAccessMask must be a valid combination of + valuesbuffer must be a valid VkBuffer handleSee Also, 3,  VkDeviceSize, , , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure. srcAccessMask is a bitmask of + specifying a  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-access-maskssource access mask. dstAccessMask is a bitmask of + specifying a  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-access-masksdestination access mask.srcQueueFamilyIndex" is the source queue family for a  mhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-queue-transfers!queue family ownership transfer.dstQueueFamilyIndex' is the destination queue family for a  mhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-queue-transfers!queue family ownership transfer.bufferL is a handle to the buffer whose backing memory is affected by the barrier.offset3 is an offset in bytes into the backing memory for bufferD; this is relative to the base offset as bound to the buffer (see j).size@ is a size in bytes of the affected area of backing memory for buffer, or  VK_WHOLE_SIZE to use the range from offset to the end of the buffer.>VkMemoryBarrier - Structure specifying a global memory barrier Description The first  xhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-dependencies-access-scopes access scope$ is limited to access types in the  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-access-maskssource access mask specified by  srcAccessMask. The second  xhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-dependencies-access-scopes access scope$ is limited to access types in the  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-access-masksdestination access mask specified by  dstAccessMask.Valid Usage (Implicit)sType must be  VK_STRUCTURE_TYPE_MEMORY_BARRIERpNext must be NULL srcAccessMask must be a valid combination of + values dstAccessMask must be a valid combination of + valuesSee Also, , , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure. srcAccessMask is a bitmask of + specifying a  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-access-maskssource access mask. dstAccessMask is a bitmask of + specifying a  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-access-masksdestination access mask.KVkImageSubresourceLayers - Structure specifying a image subresource layers Valid UsageIf  aspectMask contains VK_IMAGE_ASPECT_COLOR_BIT, it must not contain either of VK_IMAGE_ASPECT_DEPTH_BIT or VK_IMAGE_ASPECT_STENCIL_BIT aspectMask must not contain VK_IMAGE_ASPECT_METADATA_BIT layerCount must be greater than 0Valid Usage (Implicit) aspectMask must be a valid combination of r values aspectMask must not be 0See Also~, , , , w aspectMask is a combination of rB, selecting the color, depth and/or stencil aspects to be copied.mipLevel" is the mipmap level to copy from.baseArrayLayer and  layerCount6 are the starting layer and number of layers to copy.4VkClearRect - Structure specifying a clear rectangle Description The layers [baseArrayLayer, baseArrayLayer +  layerCountI) counting from the base layer of the attachment image view are cleared.See Also, rect- is the two-dimensional region to be cleared.baseArrayLayer" is the first layer to be cleared. layerCount" is the number of layers to clear.fVkStencilFaceFlagBits - Bitmask specifying sets of stencil state for which to update the compare maskSee AlsoK\VkSubpassContents - Specify how commands in the first subpass of a render pass are providedSee Also, *VkIndexType - Type of index buffer indicesSee Also, XvkCmdExecuteCommands - Execute a secondary command buffer from a primary command buffer Parameters commandBuffera is a handle to a primary command buffer that the secondary command buffers are executed in.commandBufferCount is the length of the pCommandBuffers array.pCommandBuffers is an array of secondary command buffer handles, which are recorded to execute in the primary command buffer in the order they are listed in the array. DescriptionIf any element of pCommandBuffers was not recorded with the ,VK_COMMAND_BUFFER_USAGE_SIMULTANEOUS_USE_BIT] flag, and it was recorded into any other primary command buffer which is currently in the  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecycleexecutable or recording state(, that primary command buffer becomes  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecycleinvalid. Valid Usage commandBuffer must have been allocated with a level of VK_COMMAND_BUFFER_LEVEL_PRIMARYEach element of pCommandBuffers must! have been allocated with a level of !VK_COMMAND_BUFFER_LEVEL_SECONDARYEach element of pCommandBuffers must be in the  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecycle%pending or executable state.If any element of pCommandBuffers was not recorded with the ,VK_COMMAND_BUFFER_USAGE_SIMULTANEOUS_USE_BITh flag, and it was recorded into any other primary command buffer, that primary command buffer must not be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclepending stateIf any element of pCommandBuffers was not recorded with the ,VK_COMMAND_BUFFER_USAGE_SIMULTANEOUS_USE_BIT flag, it must not be in the  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclepending state.If any element of pCommandBuffers was not recorded with the ,VK_COMMAND_BUFFER_USAGE_SIMULTANEOUS_USE_BIT flag, it must( not have already been recorded to  commandBuffer.If any element of pCommandBuffers was not recorded with the ,VK_COMMAND_BUFFER_USAGE_SIMULTANEOUS_USE_BIT flag, it must# not appear more than once in pCommandBuffers.Each element of pCommandBuffers must! have been allocated from a  VkCommandPool8 that was created for the same queue family as the  VkCommandPool from which  commandBuffer was allocatedIf vkCmdExecuteCommandsO is being called within a render pass instance, that render pass instance must have been begun with the contents parameter of vkCmdBeginRenderPass set to -VK_SUBPASS_CONTENTS_SECONDARY_COMMAND_BUFFERSIf vkCmdExecuteCommandsE is being called within a render pass instance, each element of pCommandBuffers must" have been recorded with the 0VK_COMMAND_BUFFER_USAGE_RENDER_PASS_CONTINUE_BITIf vkCmdExecuteCommandsE is being called within a render pass instance, each element of pCommandBuffers must have been recorded with VkCommandBufferInheritanceInfo::subpass] set to the index of the subpass which the given command buffer will be executed inIf vkCmdExecuteCommandsp is being called within a render pass instance, the render passes specified in the pname::pBeginInfo::pInheritanceInfo:: renderPass members of the 7 commands used to begin recording each element of pCommandBuffers must be  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#renderpass-compatibility compatible# with the current render pass.If vkCmdExecuteCommandsH is being called within a render pass instance, and any element of pCommandBuffers was recorded with VkCommandBufferInheritanceInfo:: framebuffer not equal to  , that  VkFramebuffer must match the  VkFramebuffer. used in the current render pass instanceIf vkCmdExecuteCommandsI is not being called within a render pass instance, each element of pCommandBuffers must& not have been recorded with the 0VK_COMMAND_BUFFER_USAGE_RENDER_PASS_CONTINUE_BITIf the  phttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-inheritedQueriesinherited queries feature is not enabled,  commandBuffer must not have any queries fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#queries-operation-activeactiveIf  commandBuffer has a VK_QUERY_TYPE_OCCLUSION query  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#queries-operation-activeactive, then each element of pCommandBuffers must have been recorded with VkCommandBufferInheritanceInfo::occlusionQueryEnable set to VK_TRUEIf  commandBuffer has a VK_QUERY_TYPE_OCCLUSION query  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#queries-operation-activeactive, then each element of pCommandBuffers must have been recorded with VkCommandBufferInheritanceInfo:: queryFlags4 having all bits set that are set for the queryIf  commandBuffer has a !VK_QUERY_TYPE_PIPELINE_STATISTICS query  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#queries-operation-activeactive, then each element of pCommandBuffers must have been recorded with VkCommandBufferInheritanceInfo::pipelineStatistics. having all bits set that are set in the  VkQueryPool the query usesEach element of pCommandBuffers must. not begin any query types that are  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#queries-operation-activeactive in  commandBufferValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handlepCommandBuffers must( be a valid pointer to an array of commandBufferCount valid VkCommandBuffer handles commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must7 support transfer, graphics, or compute operations commandBuffer must be a primary VkCommandBuffercommandBufferCount must be greater than 0Both of  commandBuffer, and the elements of pCommandBuffers must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type I Primary F Both 7 Transfer Graphics Compute v See Also0vkCmdEndRenderPass - End the current render pass Parameters commandBufferM is the command buffer in which to end the current render pass instance. Description`Ending a render pass instance performs any multisample resolve operations on the final subpass. Valid UsageThe current subpass index mustF be equal to the number of subpasses in the render pass minus oneValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must! support graphics operations This command must0 only be called inside of a render pass instance commandBuffer must be a primary VkCommandBufferHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type m Primary l Inside g Graphics | Graphics See AlsoBvkCmdNextSubpass - Transition to the next subpass of a render pass Parameters commandBuffer; is the command buffer in which to record the command.contents specifies how the commands in the next subpass will be provided, in the same fashion as the corresponding parameter of . Description9The subpass index for a render pass begins at zero when vkCmdBeginRenderPass( is recorded, and increments each time vkCmdNextSubpass is recorded.Moving to the next subpass automatically performs any multisample resolve operations in the subpass being ended. End-of-subpass multisample resolves are treated as color attachment writes for the purposes of synchronization. That is, they are considered to execute in the -VK_PIPELINE_STAGE_COLOR_ATTACHMENT_OUTPUT_BIT9 pipeline stage and their writes are synchronized with $VK_ACCESS_COLOR_ATTACHMENT_WRITE_BIT*. Synchronization between rendering within a subpass and any resolve operations at the end of the subpass occurs automatically, without need for explicit dependencies or pipeline barriers. However, if the resolve attachment is also used in a different subpass, an explicit dependency is needed.9After transitioning to the next subpass, the application can' record the commands for that subpass. Valid UsageThe current subpass index mustG be less than the number of subpasses in the render pass minus oneValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handlecontents must be a valid  value commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must! support graphics operations This command must0 only be called inside of a render pass instance commandBuffer must be a primary VkCommandBufferHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type m Primary l Inside g Graphics | Graphics See Also, .vkCmdBeginRenderPass - Begin a new render pass Parameters commandBuffer; is the command buffer in which to record the command.pRenderPassBegin is a pointer to a n structure (defined below) which specifies the render pass to begin an instance of, and the framebuffer the instance uses.contents is a N value specifying how the commands in the first subpass will be provided. DescriptionAfter beginning a render pass instance, the command buffer is ready to record the commands for the first subpass of that render pass. Valid UsageIf any of the  initialLayout or  finalLayout member of the VkAttachmentDescription structures or the layout member of the VkAttachmentReferenceJ structures specified when creating the render pass specified in the  renderPass member of pRenderPassBegin is (VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMALc then the corresponding attachment image subresource of the framebuffer specified in the  framebuffer member of pRenderPassBegin must have been created with #VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT setIf any of the  initialLayout or  finalLayout member of the VkAttachmentDescription structures or the layout member of the VkAttachmentReferenceJ structures specified when creating the render pass specified in the  renderPass member of pRenderPassBegin is :VK_IMAGE_LAYOUT_DEPTH_READ_ONLY_STENCIL_ATTACHMENT_OPTIMAL, :VK_IMAGE_LAYOUT_DEPTH_ATTACHMENT_STENCIL_READ_ONLY_OPTIMAL, 0VK_IMAGE_LAYOUT_DEPTH_STENCIL_ATTACHMENT_OPTIMAL , or /VK_IMAGE_LAYOUT_DEPTH_STENCIL_READ_ONLY_OPTIMALc then the corresponding attachment image subresource of the framebuffer specified in the  framebuffer member of pRenderPassBegin must have been created with +VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT setIf any of the  initialLayout or  finalLayout member of the VkAttachmentDescription structures or the layout member of the VkAttachmentReferenceJ structures specified when creating the render pass specified in the  renderPass member of pRenderPassBegin is (VK_IMAGE_LAYOUT_SHADER_READ_ONLY_OPTIMALc then the corresponding attachment image subresource of the framebuffer specified in the  framebuffer member of pRenderPassBegin must have been created with VK_IMAGE_USAGE_SAMPLED_BIT or #VK_IMAGE_USAGE_INPUT_ATTACHMENT_BIT setIf any of the  initialLayout or  finalLayout member of the VkAttachmentDescription structures or the layout member of the VkAttachmentReferenceJ structures specified when creating the render pass specified in the  renderPass member of pRenderPassBegin is $VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMALc then the corresponding attachment image subresource of the framebuffer specified in the  framebuffer member of pRenderPassBegin must have been created with VK_IMAGE_USAGE_TRANSFER_SRC_BIT setIf any of the  initialLayout or  finalLayout member of the VkAttachmentDescription structures or the layout member of the VkAttachmentReferenceJ structures specified when creating the render pass specified in the  renderPass member of pRenderPassBegin is $VK_IMAGE_LAYOUT_TRANSFER_DST_OPTIMALc then the corresponding attachment image subresource of the framebuffer specified in the  framebuffer member of pRenderPassBegin must have been created with VK_IMAGE_USAGE_TRANSFER_DST_BIT setIf any of the  initialLayout members of the VkAttachmentDescriptionJ structures specified when creating the render pass specified in the  renderPass member of pRenderPassBegin is not VK_IMAGE_LAYOUT_UNDEFINED, then each such  initialLayout must be equal to the current layout of the corresponding attachment image subresource of the framebuffer specified in the  framebuffer member of pRenderPassBeginThe  srcStageMask and  dstStageMask$ members of any element of the  pDependencies member of  used to create  renderPass mustM be supported by the capabilities of the queue family identified by the queueFamilyIndex member of the , used to create the command pool which  commandBuffer was allocated from.Valid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handlepRenderPassBegin must$ be a valid pointer to a valid VkRenderPassBeginInfo structurecontents must be a valid  value commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must! support graphics operations This command must1 only be called outside of a render pass instance commandBuffer must be a primary VkCommandBufferHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type m Primary l Outside g Graphics | Graphics See Also, n, 8vkCmdPushConstants - Update the values of push constants Parameters commandBufferO is the command buffer in which the push constant update will be recorded.layoutG is the pipeline layout used to program the push constant updates. stageFlags is a bitmask of ^ specifying the shader stages that will use the push constants in the updated range.offsetR is the start offset of the push constant range to update, in units of bytes.sizeJ is the size of the push constant range to update, in units of bytes.pValues is an array of size4 bytes containing the new push constant values. Valid Usage(For each byte in the range specified by offset and size# and for each shader stage in  stageFlags, there must" be a push constant range in layout' that includes that byte and that stage(For each byte in the range specified by offset and size@ and for each push constant range that overlaps that byte,  stageFlags must7 include all stages in that push constant range s b,:: stageFlagsoffset must be a multiple of 4size must be a multiple of 4offset must be less than VkPhysicalDeviceLimits::maxPushConstantsSizesize must be less than or equal to VkPhysicalDeviceLimits::maxPushConstantsSize minus offsetValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handlelayout must be a valid VkPipelineLayout handle stageFlags must be a valid combination of  values stageFlags must not be 0pValues must# be a valid pointer to an array of size bytes commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must- support graphics, or compute operationssize must be greater than 0Both of  commandBuffer, and layout must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Both  Graphics Compute  See Also, ,  h[vkCmdCopyQueryPoolResults - Copy the results of queries in a query pool to a buffer object Parameters commandBufferE is the command buffer into which this command will be recorded. queryPoolL is the query pool managing the queries containing the desired results. firstQuery is the initial query index. queryCount is the number of queries.  firstQuery and  queryCount) together define a range of queries. dstBuffer is a VkBuffer? object that will receive the results of the copy command. dstOffset is an offset into  dstBuffer.strideK is the stride in bytes between results for individual queries within  dstBuffer3. The required size of the backing memory for  dstBuffer+ is determined as described above for F.flags is a bitmask of 3 specifying how and when results are returned. DescriptionvkCmdCopyQueryPoolResults6 is guaranteed to see the effect of previous uses of vkCmdResetQueryPool in the same queue, without any additional synchronization. Thus, the results will always reflect the most recent use of the query.flags6 has the same possible values described above for the flags parameter of F\, but the different style of execution causes some subtle behavioral differences. Because vkCmdCopyQueryPoolResults executes in order with respect to other query commands, there is less ambiguity about which use of a query is being requested.If no bits are set in flags, results for all requested queries in the available state are written as 32-bit unsigned integer values, and nothing is written for queries in the unavailable state.If VK_QUERY_RESULT_64_BITb is set, the results are written as an array of 64-bit unsigned integer values as described for F.If VK_QUERY_RESULT_WAIT_BIT is set, the implementation will wait for each query s status to be in the available state before retrieving the numerical results for that query. This is guaranteed to reflect the most recent use of the query on the same queue, assuming that the query is not being simultaneously used by other queues. If the query does not become available in a finite amount of time (e.g. due to not issuing a query since the last reset), a VK_ERROR_DEVICE_LOST error may occur.Similarly, if %VK_QUERY_RESULT_WITH_AVAILABILITY_BIT is set and VK_QUERY_RESULT_WAIT_BIT is not set, the availability is guaranteed to reflect the most recent use of the query on the same queue, assuming that the query is not being simultaneously used by other queues. As with vkGetQueryPoolResults, implementations muste guarantee that if they return a non-zero availability value, then the numerical results are valid.If VK_QUERY_RESULT_PARTIAL_BIT is set, VK_QUERY_RESULT_WAIT_BIT is not set, and the query s status is unavailable, an intermediate result value between zero and the final result value is written for that query.VK_QUERY_RESULT_PARTIAL_BIT must not be used if the pool s  queryType is VK_QUERY_TYPE_TIMESTAMP.vkCmdCopyQueryPoolResultsL is considered to be a transfer operation, and its writes to buffer memory must be synchronized using VK_PIPELINE_STAGE_TRANSFER_BIT and VK_ACCESS_TRANSFER_WRITE_BIT before using the results. Valid Usage dstOffset must be less than the size of  dstBuffer firstQuery must, be less than the number of queries in  queryPool The sum of  firstQuery and  queryCount must8 be less than or equal to the number of queries in  queryPoolIf VK_QUERY_RESULT_64_BIT is not set in flags then  dstOffset and stride must be multiples of 4If VK_QUERY_RESULT_64_BIT is set in flags then  dstOffset and stride must be multiples of 8 dstBuffer must have enough storage, from  dstOffset>, to contain the result of each query, as described lhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#queries-operation-memorylayouthere dstBuffer must have been created with  VK_BUFFER_USAGE_TRANSFER_DST_BIT usage flagIf  dstBuffer is non-sparse then it must7 be bound completely and contiguously to a single VkDeviceMemory objectIf the  queryType used to create  queryPool was VK_QUERY_TYPE_TIMESTAMP, flags must not contain VK_QUERY_RESULT_PARTIAL_BITValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle queryPool must be a valid  VkQueryPool handle dstBuffer must be a valid VkBuffer handleflags must be a valid combination of  values commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must- support graphics, or compute operations This command must1 only be called outside of a render pass instanceEach of  commandBuffer,  dstBuffer, and  queryPool must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Outside  Graphics Compute  Transfer See Also3, ,  VkDeviceSize, , BvkCmdWriteTimestamp - Write a device timestamp into a query object Parameters commandBufferD is the command buffer into which the command will be recorded. pipelineStage is one of the *, specifying a stage of the pipeline. queryPool2 is the query pool that will manage the timestamp.queryI is the query within the query pool that will contain the timestamp. DescriptionvkCmdWriteTimestamp latches the value of the timer when all previous commands have completed executing as far as the specified pipeline stage, and writes the timestamp value to memory. When the timestamp value is written, the availability status of the query is set to available.NotesIf an implementation is unable to detect completion and latch the timer at any specific stage of the pipeline, it may- instead do so at any logically later stage. can then be called to copy the timestamp value from the query pool into buffer memory, with ordering and synchronization behavior equivalent to how other queries operate. Timestamp values can. also be retrieved from the query pool using F$. As with other queries, the query must be reset using 9 before requesting the timestamp value be written to it.While vkCmdWriteTimestamp can9 be called inside or outside of a render pass instance,  must3 only be called outside of a render pass instance. Timestamps may\ only be meaningfully compared if they are written by commands submitted to the same queue.Note]An example of such a comparison is determining the execution time of a sequence of commands.If vkCmdWriteTimestamp is called while executing a render pass instance that has multiview enabled, the timestamp uses N consecutive query indices in the query pool (starting at query) where N is the number of bits set in the view mask of the subpass the command is executed in. The resulting query values are determined by an implementation-dependent choice of one of the following behaviors:MThe first query is a timestamp value and (if more than one bit is set in the view mask) zero is written to the remaining queries. If two timestamps are written in the same subpass, the sum of the execution time of all views between those commands is the difference between the first query written by each command..All N queries are timestamp values. If two timestamps are written in the same subpass, the sum of the execution time of all views between those commands is the sum of the difference between corresponding queries written by each command. The difference between corresponding queries may( be the execution time of a single view. In either case, the application canR sum the differences between all N queries to determine the total execution time. Valid Usage queryPool must have been created with a  queryType of VK_QUERY_TYPE_TIMESTAMPThe query identified by  queryPool and query must be  unavailable The command pool s queue family must support a non-zero timestampValidBits All queries used by the command must be unavailableIf vkCmdWriteTimestamp: is called within a render pass instance, the sum of queryD and the number of bits set in the current subpass s view mask must8 be less than or equal to the number of queries in  queryPoolValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle pipelineStage must be a valid  value queryPool must be a valid  VkQueryPool handle commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must7 support transfer, graphics, or compute operationsBoth of  commandBuffer, and  queryPool must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type I Primary Secondary F Both 7 Transfer Graphics Compute v Transfer See Also, , 3vkCmdResetQueryPool - Reset queries in a query pool Parameters commandBufferE is the command buffer into which this command will be recorded. queryPoolG is the handle of the query pool managing the queries being reset. firstQuery% is the initial query index to reset. queryCount# is the number of queries to reset. DescriptionJWhen executed on a queue, this command sets the status of query indices [ firstQuery,  firstQuery +  queryCount - 1] to unavailable. Valid Usage firstQuery must, be less than the number of queries in  queryPool The sum of  firstQuery and  queryCount must8 be less than or equal to the number of queries in  queryPoolValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle queryPool must be a valid  VkQueryPool handle commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must- support graphics, or compute operations This command must1 only be called outside of a render pass instanceBoth of  commandBuffer, and  queryPool must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Outside  Graphics Compute  See Also, vkCmdEndQuery - Ends a query Parameters commandBufferE is the command buffer into which this command will be recorded. queryPoolB is the query pool that is managing the results of the query.queryJ is the query index within the query pool where the result is stored. DescriptionAs queries operate asynchronously, ending a query does not immediately set the query s status to available. A query is considered finishedD when the final results of the query are ready to be retrieved by F and ;, and this is when the query s status is set to available. Once a query is ended the query must~ finish in finite time, unless the state of the query is changed using other commands, e.g. by issuing a reset of the query. Valid Usage All queries used by the command must be fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#queries-operation-activeactivequery must' be less than the number of queries in  queryPoolIf  vkCmdEndQuery: is called within a render pass instance, the sum of queryD and the number of bits set in the current subpass s view mask must8 be less than or equal to the number of queries in  queryPoolValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle queryPool must be a valid  VkQueryPool handle commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must- support graphics, or compute operationsBoth of  commandBuffer, and  queryPool must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Both  Graphics Compute  See Also, vkCmdBeginQuery - Begin a query Parameters commandBufferE is the command buffer into which this command will be recorded. queryPoolB is the query pool that will manage the results of the query.queryM is the query index within the query pool that will contain the results.flags is a bitmask of : specifying constraints on the types of queries that can be performed. DescriptionIf the  queryType of the pool is VK_QUERY_TYPE_OCCLUSION and flags contains VK_QUERY_CONTROL_PRECISE_BIT, an implementation musti return a result that matches the actual number of samples passed. This is described in more detail in  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#queries-occlusionOcclusion Queries.2After beginning a query, that query is considered active within the command buffer it was called in until that same query is ended. Queries active in a primary command buffer when secondary command buffers are executed are considered active for those secondary command buffers. Valid Usage queryPool must have been created with a  queryType: that differs from that of any queries that are  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#queries-operation-activeactive within  commandBuffer All queries used by the command must be unavailableIf the  uhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-occlusionQueryPreciseprecise occlusion queries% feature is not enabled, or the  queryType used to create  queryPool was not VK_QUERY_TYPE_OCCLUSION, flags must not contain VK_QUERY_CONTROL_PRECISE_BITquery must' be less than the number of queries in  queryPoolIf the  queryType used to create  queryPool was VK_QUERY_TYPE_OCCLUSION, the  VkCommandPool that  commandBuffer was allocated from must support graphics operationsIf the  queryType used to create  queryPool was !VK_QUERY_TYPE_PIPELINE_STATISTICS and any of the pipelineStatistics( indicate graphics operations, the  VkCommandPool that  commandBuffer was allocated from must! support graphics operationsIf the  queryType used to create  queryPool was !VK_QUERY_TYPE_PIPELINE_STATISTICS and any of the pipelineStatistics' indicate compute operations, the  VkCommandPool that  commandBuffer was allocated from must support compute operationsIf vkCmdBeginQuery: is called within a render pass instance, the sum of queryD and the number of bits set in the current subpass s view mask must8 be less than or equal to the number of queries in  queryPoolValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle queryPool must be a valid  VkQueryPool handleflags must be a valid combination of  values commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must- support graphics, or compute operationsBoth of  commandBuffer, and  queryPool must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Both  Graphics Compute  See Also, , 1vkCmdPipelineBarrier - Insert a memory dependency Parameters commandBuffer? is the command buffer into which the command is recorded.  srcStageMask is a bitmask of  specifying the  shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-maskssource stage mask. dstStageMask is a bitmask of  specifying the  shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-masksdestination stage mask.dependencyFlags is a bitmask of B specifying how execution and memory dependencies are formed.memoryBarrierCount is the length of the pMemoryBarriers array.pMemoryBarriers is a pointer to an array of  structures.bufferMemoryBarrierCount is the length of the pBufferMemoryBarriers array.pBufferMemoryBarriers" is a pointer to an array of  structures.imageMemoryBarrierCount is the length of the pImageMemoryBarriers array.pImageMemoryBarriers" is a pointer to an array of  structures. DescriptionWhen  is submitted to a queue, it defines a memory dependency between commands that were submitted before it, and those submitted after it.If 9 was recorded outside a render pass instance, the first  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-dependencies-scopessynchronization scope. includes all commands that occur earlier in  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-submission-ordersubmission order. If | was recorded inside a render pass instance, the first synchronization scope includes only commands that occur earlier in  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-submission-ordersubmission order within the same subpass. In either case, the first synchronization scope is limited to operations on the pipeline stages determined by the  shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-maskssource stage mask specified by  srcStageMask.If : was recorded outside a render pass instance, the second  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-dependencies-scopessynchronization scope, includes all commands that occur later in  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-submission-ordersubmission order. If { was recorded inside a render pass instance, the second synchronization scope includes only commands that occur later in  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-submission-ordersubmission order within the same subpass. In either case, the second synchronization scope is limited to operations on the pipeline stages determined by the  shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-masksdestination stage mask specified by  dstStageMask. The first  xhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-dependencies-access-scopes access scope@ is limited to access in the pipeline stages determined by the  shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-maskssource stage mask specified by  srcStageMaski. Within that, the first access scope only includes the first access scopes defined by elements of the pMemoryBarriers, pBufferMemoryBarriers and pImageMemoryBarriers% arrays, which each define a set of  mhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-memory-barriersmemory barriersZ. If no memory barriers are specified, then the first access scope includes no accesses. The second  xhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-dependencies-access-scopes access scopeA is limited to access in the pipeline stages determined by the  shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-masksdestination stage mask specified by  dstStageMaskk. Within that, the second access scope only includes the second access scopes defined by elements of the pMemoryBarriers, pBufferMemoryBarriers and pImageMemoryBarriers% arrays, which each define a set of  mhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-memory-barriersmemory barriers[. If no memory barriers are specified, then the second access scope includes no accesses.If dependencyFlags includes VK_DEPENDENCY_BY_REGION_BIT , then any dependency between  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-framebuffer-regionsframebuffer-space pipeline stages is  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-framebuffer-regionsframebuffer-local - otherwise it is  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-framebuffer-regionsframebuffer-global. Valid UsageIf the  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-geometryShadergeometry shaders feature is not enabled,  srcStageMask must not contain %VK_PIPELINE_STAGE_GEOMETRY_SHADER_BITIf the  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-geometryShadergeometry shaders feature is not enabled,  dstStageMask must not contain %VK_PIPELINE_STAGE_GEOMETRY_SHADER_BITIf the  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-tessellationShadertessellation shaders feature is not enabled,  srcStageMask must not contain 1VK_PIPELINE_STAGE_TESSELLATION_CONTROL_SHADER_BIT or 4VK_PIPELINE_STAGE_TESSELLATION_EVALUATION_SHADER_BITIf the  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-tessellationShadertessellation shaders feature is not enabled,  dstStageMask must not contain 1VK_PIPELINE_STAGE_TESSELLATION_CONTROL_SHADER_BIT or 4VK_PIPELINE_STAGE_TESSELLATION_EVALUATION_SHADER_BITIf vkCmdPipelineBarrier? is called within a render pass instance, the render pass must have been created with a VkSubpassDependency instance in  pDependenciesE that expresses a dependency from the current subpass to itself.If vkCmdPipelineBarrier/ is called within a render pass instance,  srcStageMask must0 contain a subset of the bit values in the  srcStageMask member of that instance of VkSubpassDependencyIf vkCmdPipelineBarrier/ is called within a render pass instance,  dstStageMask must0 contain a subset of the bit values in the  dstStageMask member of that instance of VkSubpassDependencyIf vkCmdPipelineBarrier3 is called within a render pass instance, the  srcAccessMask of any element of pMemoryBarriers or pImageMemoryBarriers must- contain a subset of the bit values the  srcAccessMask member of that instance of VkSubpassDependencyIf vkCmdPipelineBarrier3 is called within a render pass instance, the  dstAccessMask of any element of pMemoryBarriers or pImageMemoryBarriers must- contain a subset of the bit values the  dstAccessMask member of that instance of VkSubpassDependencyIf vkCmdPipelineBarrier/ is called within a render pass instance, dependencyFlags must be equal to the dependencyFlags! member of that instance of VkSubpassDependencyIf vkCmdPipelineBarrier/ is called within a render pass instance, bufferMemoryBarrierCount must be 0If vkCmdPipelineBarrier3 is called within a render pass instance, the image member of any element of pImageMemoryBarriers must) be equal to one of the elements of  pAttachments that the current  framebufferO was created with, that is also referred to by one of the elements of the pColorAttachments, pResolveAttachments or pDepthStencilAttachment members of the VkSubpassDescription8 instance that the current subpass was created withIf vkCmdPipelineBarrier3 is called within a render pass instance, the  oldLayout and  newLayout members of any element of pImageMemoryBarriers must be equal to the layout" member of an element of the pColorAttachments, pResolveAttachments or pDepthStencilAttachment members of the VkSubpassDescriptionW instance that the current subpass was created with, that refers to the same imageIf vkCmdPipelineBarrier3 is called within a render pass instance, the  oldLayout and  newLayout members of an element of pImageMemoryBarriers must be equalIf vkCmdPipelineBarrier3 is called within a render pass instance, the srcQueueFamilyIndex and dstQueueFamilyIndex members of any element of pImageMemoryBarriers must be VK_QUEUE_FAMILY_IGNOREDAny pipeline stage included in  srcStageMask or  dstStageMask mustL be supported by the capabilities of the queue family specified by the queueFamilyIndex member of the , structure that was used to create the  VkCommandPool that  commandBuffer) was allocated from, as specified in the  whttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-supported,table of supported pipeline stages.Each element of pMemoryBarriers, pBufferMemoryBarriers and pImageMemoryBarriers must/ not have any access flag included in its  srcAccessMaskK member if that bit is not supported by any of the pipeline stages in  srcStageMask, as specified in the  thttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-access-types-supported)table of supported access types.Each element of pMemoryBarriers, pBufferMemoryBarriers and pImageMemoryBarriers must/ not have any access flag included in its  dstAccessMaskK member if that bit is not supported by any of the pipeline stages in  dstStageMask, as specified in the  thttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-access-types-supported)table of supported access types.If vkCmdPipelineBarrier3 is called outside of a render pass instance, dependencyFlags must not include VK_DEPENDENCY_VIEW_LOCAL_BITValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle  srcStageMask must be a valid combination of  values srcStageMask must not be 0 dstStageMask must be a valid combination of  values dstStageMask must not be 0dependencyFlags must be a valid combination of  valuesIf memoryBarrierCount is not 0, pMemoryBarriers must( be a valid pointer to an array of memoryBarrierCount valid VkMemoryBarrier structuresIf bufferMemoryBarrierCount is not 0, pBufferMemoryBarriers must# be a valid pointer to an array of bufferMemoryBarrierCount valid VkBufferMemoryBarrier structuresIf imageMemoryBarrierCount is not 0, pImageMemoryBarriers must# be a valid pointer to an array of imageMemoryBarrierCount valid VkImageMemoryBarrier structures commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must7 support transfer, graphics, or compute operationsHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type I Primary Secondary F Both 7 Transfer Graphics Compute v See Also, , , , , HvkCmdWaitEvents - Wait for one or more events and insert a set of memory Parameters commandBuffer? is the command buffer into which the command is recorded.  eventCount is the length of the pEvents array.pEvents0 is an array of event object handles to wait on. srcStageMask is a bitmask of  specifying the  mhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stagessource stage mask. dstStageMask is a bitmask of  specifying the  mhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stagesdestination stage mask.memoryBarrierCount is the length of the pMemoryBarriers array.pMemoryBarriers is a pointer to an array of  structures.bufferMemoryBarrierCount is the length of the pBufferMemoryBarriers array.pBufferMemoryBarriers" is a pointer to an array of  structures.imageMemoryBarrierCount is the length of the pImageMemoryBarriers array.pImageMemoryBarriers" is a pointer to an array of  structures. DescriptionWhen vkCmdWaitEvents is submitted to a queue, it defines a memory dependency between prior event signal operations on the same queue or the host, and subsequent commands. vkCmdWaitEvents mustJ not be used to wait on event signal operations occuring on other queues.bThe first synchronization scope only includes event signal operations that operate on members of pEventsn, and the operations that happened-before the event signal operations. Event signal operations performed by  that occur earlier in  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-submission-ordersubmission order: are included in the first synchronization scope, if the  shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-orderlogically latest pipeline stage in their  stageMask parameter is  shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-orderlogically earlier than or equal to the  shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-orderlogically latest pipeline stage in  srcStageMask(. Event signal operations performed by }}: are only included in the first synchronization scope if VK_PIPELINE_STAGE_HOST_BIT is included in  srcStageMask. The second  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-dependencies-scopessynchronization scope, includes all commands that occur later in  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-submission-ordersubmission orderg. The second synchronization scope is limited to operations on the pipeline stages determined by the  shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-masksdestination stage mask specified by  dstStageMask. The first  xhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-dependencies-access-scopes access scope@ is limited to access in the pipeline stages determined by the  shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-maskssource stage mask specified by  srcStageMaski. Within that, the first access scope only includes the first access scopes defined by elements of the pMemoryBarriers, pBufferMemoryBarriers and pImageMemoryBarriers% arrays, which each define a set of  mhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-memory-barriersmemory barriersZ. If no memory barriers are specified, then the first access scope includes no accesses. The second  xhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-dependencies-access-scopes access scopeA is limited to access in the pipeline stages determined by the  shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-masksdestination stage mask specified by  dstStageMaskk. Within that, the second access scope only includes the second access scopes defined by elements of the pMemoryBarriers, pBufferMemoryBarriers and pImageMemoryBarriers% arrays, which each define a set of  mhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-memory-barriersmemory barriers[. If no memory barriers are specified, then the second access scope includes no accesses.Note is used with  to define a memory dependency between two sets of action commands, roughly in the same way as pipeline barriers, but split into two commands such that work between the two may execute unhindered.Note Applications shouldj be careful to avoid race conditions when using events. There is no direct ordering guarantee between a  command and a A command submitted after it, so some other execution dependency must8 be included between these commands (e.g. a semaphore). Valid Usage srcStageMask must be the bitwise OR of the  stageMask* parameter used in previous calls to  vkCmdSetEvent! with any of the members of pEvents and VK_PIPELINE_STAGE_HOST_BIT if any of the members of pEvents was set using  vkSetEvent If the  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-geometryShadergeometry shaders feature is not enabled,  srcStageMask must not contain %VK_PIPELINE_STAGE_GEOMETRY_SHADER_BITIf the  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-geometryShadergeometry shaders feature is not enabled,  dstStageMask must not contain %VK_PIPELINE_STAGE_GEOMETRY_SHADER_BITIf the  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-tessellationShadertessellation shaders feature is not enabled,  srcStageMask must not contain 1VK_PIPELINE_STAGE_TESSELLATION_CONTROL_SHADER_BIT or 4VK_PIPELINE_STAGE_TESSELLATION_EVALUATION_SHADER_BITIf the  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-tessellationShadertessellation shaders feature is not enabled,  dstStageMask must not contain 1VK_PIPELINE_STAGE_TESSELLATION_CONTROL_SHADER_BIT or 4VK_PIPELINE_STAGE_TESSELLATION_EVALUATION_SHADER_BITIf pEvents; includes one or more events that will be signaled by  vkSetEvent after  commandBuffer* has been submitted to a queue, then vkCmdWaitEvents must1 not be called inside a render pass instanceAny pipeline stage included in  srcStageMask or  dstStageMask mustL be supported by the capabilities of the queue family specified by the queueFamilyIndex member of the , structure that was used to create the  VkCommandPool that  commandBuffer) was allocated from, as specified in the  whttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-supported,table of supported pipeline stages.Each element of pMemoryBarriers, pBufferMemoryBarriers or pImageMemoryBarriers must/ not have any access flag included in its  srcAccessMaskK member if that bit is not supported by any of the pipeline stages in  srcStageMask, as specified in the  thttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-access-types-supported)table of supported access types.Each element of pMemoryBarriers, pBufferMemoryBarriers or pImageMemoryBarriers must/ not have any access flag included in its  dstAccessMaskK member if that bit is not supported by any of the pipeline stages in  dstStageMask, as specified in the  thttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-access-types-supported)table of supported access types. commandBuffer s current device mask must* include exactly one physical device.Valid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle pEvents must# be a valid pointer to an array of  eventCount valid VkEvent handles srcStageMask must be a valid combination of  values srcStageMask must not be 0 dstStageMask must be a valid combination of  values dstStageMask must not be 0If memoryBarrierCount is not 0, pMemoryBarriers must( be a valid pointer to an array of memoryBarrierCount valid VkMemoryBarrier structuresIf bufferMemoryBarrierCount is not 0, pBufferMemoryBarriers must# be a valid pointer to an array of bufferMemoryBarrierCount valid VkBufferMemoryBarrier structuresIf imageMemoryBarrierCount is not 0, pImageMemoryBarriers must# be a valid pointer to an array of imageMemoryBarrierCount valid VkImageMemoryBarrier structures commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must- support graphics, or compute operations eventCount must be greater than 0Both of  commandBuffer, and the elements of pEvents must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Both  Graphics Compute  See Also, , L, , , =vkCmdResetEvent - Reset an event object to non-signaled state Parameters commandBuffer? is the command buffer into which the command is recorded.event& is the event that will be unsignaled. stageMask is a bitmask of  specifying the  mhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stagessource stage mask! used to determine when the event is unsignaled. DescriptionWhen  is submitted to a queue, it defines an execution dependency on commands that were submitted before it, and defines an event unsignal operation which resets the event to the unsignaled state. The first  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-dependencies-scopessynchronization scope. includes all commands that occur earlier in  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-submission-ordersubmission order`. The synchronization scope is limited to operations on the pipeline stages determined by the  shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-maskssource stage mask specified by  stageMask. The second  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-dependencies-scopessynchronization scope- includes only the event unsignal operation.If event) is already in the unsignaled state when " is executed on the device, then ^ has no effect, no event unsignal operation occurs, and no execution dependency is generated. Valid Usage stageMask must not include VK_PIPELINE_STAGE_HOST_BITIf the  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-geometryShadergeometry shaders feature is not enabled,  stageMask must not contain %VK_PIPELINE_STAGE_GEOMETRY_SHADER_BITIf the  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-tessellationShadertessellation shaders feature is not enabled,  stageMask must not contain 1VK_PIPELINE_STAGE_TESSELLATION_CONTROL_SHADER_BIT or 4VK_PIPELINE_STAGE_TESSELLATION_EVALUATION_SHADER_BITWhen this command executes, event must not be waited on by a vkCmdWaitEvents$ command that is currently executing commandBuffer s current device mask must* include exactly one physical device.Valid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handleevent must be a valid VkEvent handle stageMask must be a valid combination of  values stageMask must not be 0 commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must- support graphics, or compute operations This command must1 only be called outside of a render pass instanceBoth of  commandBuffer, and event must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Outside  Graphics Compute  See Also, L, 5vkCmdSetEvent - Set an event object to signaled state Parameters commandBuffer? is the command buffer into which the command is recorded.event$ is the event that will be signaled. stageMask specifies the  mhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stagessource stage mask! used to determine when the event is signaled. DescriptionWhen  is submitted to a queue, it defines an execution dependency on commands that were submitted before it, and defines an event signal operation which sets the event to the signaled state. The first  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-dependencies-scopessynchronization scope. includes all commands that occur earlier in  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-submission-ordersubmission order`. The synchronization scope is limited to operations on the pipeline stages determined by the  shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-maskssource stage mask specified by  stageMask. The second  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-dependencies-scopessynchronization scope+ includes only the event signal operation.If event' is already in the signaled state when " is executed on the device, then \ has no effect, no event signal operation occurs, and no execution dependency is generated. Valid Usage stageMask must not include VK_PIPELINE_STAGE_HOST_BITIf the  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-geometryShadergeometry shaders feature is not enabled,  stageMask must not contain %VK_PIPELINE_STAGE_GEOMETRY_SHADER_BITIf the  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-tessellationShadertessellation shaders feature is not enabled,  stageMask must not contain 1VK_PIPELINE_STAGE_TESSELLATION_CONTROL_SHADER_BIT or 4VK_PIPELINE_STAGE_TESSELLATION_EVALUATION_SHADER_BIT commandBuffer s current device mask must* include exactly one physical device.Valid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handleevent must be a valid VkEvent handle stageMask must be a valid combination of  values stageMask must not be 0 commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must- support graphics, or compute operations This command must1 only be called outside of a render pass instanceBoth of  commandBuffer, and event must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Outside  Graphics Compute  See Also, L, /vkCmdResolveImage - Resolve regions of an image Parameters commandBufferD is the command buffer into which the command will be recorded.srcImage is the source image.srcImageLayoutE is the layout of the source image subresources for the resolve.dstImage is the destination image.dstImageLayoutJ is the layout of the destination image subresources for the resolve. regionCount% is the number of regions to resolve.pRegions is a pointer to an array of w3 structures specifying the regions to resolve. DescriptionDuring the resolve the samples corresponding to each pixel location in the source are converted to a single sample before being written to the destination. If the source formats are floating-point or normalized types, the sample values for each pixel are resolved in an implementation-dependent manner. If the source formats are integer types, a single sample s value is selected for each pixel. srcOffset and  dstOffset select the initial x, y, and zR offsets in texels of the sub-regions of the source and destination image data. extent: is the size in texels of the source image to resolve in width, height and depth./Resolves are done layer by layer starting with baseArrayLayer member of srcSubresource for the source and dstSubresource for the destination.  layerCount. layers are resolved to the destination image. Valid Usage/The source region specified by each element of pRegions must+ be a region that is contained within srcImage4The destination region specified by each element of pRegions must& be a region that is contained within dstImagemThe union of all source regions, and the union of all destination regions, specified by the elements of pRegions, must not overlap in memoryIf srcImage is non-sparse then it must7 be bound completely and contiguously to a single VkDeviceMemory objectsrcImage mustK have a sample count equal to any valid sample count value other than VK_SAMPLE_COUNT_1_BITIf dstImage is non-sparse then it must7 be bound completely and contiguously to a single VkDeviceMemory objectdstImage must# have a sample count equal to VK_SAMPLE_COUNT_1_BITsrcImageLayout must6 specify the layout of the image subresources of srcImage specified in pRegions0 at the time this command is executed on a VkDevicesrcImageLayout must be "VK_IMAGE_LAYOUT_SHARED_PRESENT_KHR, $VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL or VK_IMAGE_LAYOUT_GENERALdstImageLayout must6 specify the layout of the image subresources of dstImage specified in pRegions0 at the time this command is executed on a VkDevicedstImageLayout must be "VK_IMAGE_LAYOUT_SHARED_PRESENT_KHR, $VK_IMAGE_LAYOUT_TRANSFER_DST_OPTIMAL or VK_IMAGE_LAYOUT_GENERALIf dstImage was created with tiling equal to VK_IMAGE_TILING_LINEAR, dstImage must have been created with a formatB that supports being a color attachment, as specified by the &VK_FORMAT_FEATURE_COLOR_ATTACHMENT_BIT flag in VkFormatProperties::linearTilingFeatures returned by #vkGetPhysicalDeviceFormatPropertiesIf dstImage was created with tiling equal to VK_IMAGE_TILING_OPTIMAL, dstImage must have been created with a formatB that supports being a color attachment, as specified by the &VK_FORMAT_FEATURE_COLOR_ATTACHMENT_BIT flag in VkFormatProperties::optimalTilingFeatures returned by #vkGetPhysicalDeviceFormatPropertiessrcImage and dstImage must2 have been created with the same image formatThe srcSubresource.mipLevel member of each element of pRegions must be less than the  mipLevels specified in * when srcImage was createdThe dstSubresource.mipLevel member of each element of pRegions must be less than the  mipLevels specified in * when dstImage was createdThe srcSubresource.baseArrayLayer + srcSubresource.layerCount of each element of pRegions must# be less than or equal to the  arrayLayers specified in * when srcImage was createdThe dstSubresource.baseArrayLayer + dstSubresource.layerCount of each element of pRegions must# be less than or equal to the  arrayLayers specified in * when dstImage was createdValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle srcImage must be a valid VkImage handlesrcImageLayout must be a valid  valuedstImage must be a valid VkImage handledstImageLayout must be a valid  valuepRegions must# be a valid pointer to an array of  regionCount valid VkImageResolve structures commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must! support graphics operations This command must1 only be called outside of a render pass instance regionCount must be greater than 0Each of  commandBuffer, dstImage, and srcImage must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Outside  Graphics  Transfer See Also, 2, , wKvkCmdClearAttachments - Clear regions within bound framebuffer attachments Parameters commandBufferD is the command buffer into which the command will be recorded.attachmentCount! is the number of entries in the  pAttachments array. pAttachments is a pointer to an array of eT structures defining the attachments to clear and the clear values to use. rectCount! is the number of entries in the pRects array.pRects points to an array of K structures defining regions within each selected attachment to clear. DescriptionvkCmdClearAttachments canq clear multiple regions of each attachment used in the current subpass of a render pass instance. This command must be called only inside a render pass instance, and implicitly selects the images to clear based on the current framebuffer attachments and the command parameters. Valid UsageIf the  aspectMask member of any element of  pAttachments contains VK_IMAGE_ASPECT_COLOR_BIT, the colorAttachment member of that element must> refer to a valid color attachment in the current subpass4The rectangular region specified by each element of pRects mustR be contained within the render area of the current render pass instance(The layers specified by each element of pRects must0 be contained within every attachment that  pAttachments refers toJIf the render pass instance this is recorded in uses multiview, then baseArrayLayer must be zero and  layerCount must be one.Valid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle pAttachments must( be a valid pointer to an array of attachmentCount valid VkClearAttachment structurespRects must# be a valid pointer to an array of  rectCount  VkClearRect structures commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must! support graphics operations This command must0 only be called inside of a render pass instanceattachmentCount must be greater than 0 rectCount must be greater than 0Host SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Inside  Graphics  Graphics See Alsoe, , MvkCmdClearDepthStencilImage - Fill regions of a combined depth/stencil image Parameters commandBufferD is the command buffer into which the command will be recorded.image is the image to be cleared. imageLayoutV specifies the current layout of the image subresource ranges to be cleared, and must be VK_IMAGE_LAYOUT_GENERAL or $VK_IMAGE_LAYOUT_TRANSFER_DST_OPTIMAL. pDepthStencil is a pointer to a jz structure that contains the values the depth and stencil image subresource ranges will be cleared to (see  [https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#clears-values"{html_spec_relative}#clears-values below). rangeCount= is the number of image subresource range structures in pRanges.pRanges points to an array of w structures that describe a range of mipmap levels, array layers, and aspects to be cleared, as described in  chttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#resources-image-viewsImage Views . The  aspectMask$ of each image subresource range in pRanges can include VK_IMAGE_ASPECT_DEPTH_BIT5 if the image format has a depth component, and VK_IMAGE_ASPECT_STENCIL_BIT3 if the image format has a stencil component.  pDepthStencil is a pointer to a VkClearDepthStencilValuec structure that contains the values the image subresource ranges will be cleared to (see  [https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#clears-values"{html_spec_relative}#clears-values below). Valid Usageimage must! use a format that supports "VK_FORMAT_FEATURE_TRANSFER_DST_BIT, which is indicated by VkFormatProperties::linearTilingFeatures% (for linearly tiled images) or VkFormatProperties::optimalTilingFeatures9 (for optimally tiled images) - as returned by #vkGetPhysicalDeviceFormatProperties image must have been created with VK_IMAGE_USAGE_TRANSFER_DST_BIT usage flagIf image is non-sparse then it must7 be bound completely and contiguously to a single VkDeviceMemory object imageLayout must< specify the layout of the image subresource ranges of image specified in pRanges0 at the time this command is executed on a VkDevice imageLayout must be either of $VK_IMAGE_LAYOUT_TRANSFER_DST_OPTIMAL or VK_IMAGE_LAYOUT_GENERAL The :: baseMipLevel% members of the elements of the pRanges array must each be less than the  mipLevels specified in * when image was created For each  element of pRanges , if the  levelCount member is not VK_REMAINING_MIP_LEVELS, then  baseMipLevel +  levelCount must be less than the  mipLevels specified in * when image was created The ::baseArrayLayer% members of the elements of the pRanges array must each be less than the  arrayLayers specified in * when image was created For each  element of pRanges , if the  layerCount member is not VK_REMAINING_ARRAY_LAYERS, then baseArrayLayer +  layerCount must be less than the  arrayLayers specified in * when image was createdimage must have a depth/stencil formatValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle image must be a valid VkImage handle imageLayout must be a valid  value pDepthStencil must$ be a valid pointer to a valid VkClearDepthStencilValue structurepRanges must# be a valid pointer to an array of  rangeCount valid VkImageSubresourceRange structures commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must! support graphics operations This command must1 only be called outside of a render pass instance rangeCount must be greater than 0Both of  commandBuffer, and image must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Outside  Graphics  Transfer See Alsoj, , 2, , 5vkCmdClearColorImage - Clear regions of a color image Parameters commandBufferD is the command buffer into which the command will be recorded.image is the image to be cleared. imageLayoutV specifies the current layout of the image subresource ranges to be cleared, and must be "VK_IMAGE_LAYOUT_SHARED_PRESENT_KHR, VK_IMAGE_LAYOUT_GENERAL or $VK_IMAGE_LAYOUT_TRANSFER_DST_OPTIMAL.pColor is a pointer to a Oh structure that contains the values the image subresource ranges will be cleared to (see  [https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#clears-values"{html_spec_relative}#clears-values below). rangeCount= is the number of image subresource range structures in pRanges.pRanges points to an array of w structures that describe a range of mipmap levels, array layers, and aspects to be cleared, as described in  chttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#resources-image-viewsImage Views . The  aspectMask! of all image subresource ranges must only include VK_IMAGE_ASPECT_COLOR_BIT. DescriptionEach specified range in pRanges' is cleared to the value specified by pColor. Valid Usageimage must! use a format that supports "VK_FORMAT_FEATURE_TRANSFER_DST_BIT, which is indicated by VkFormatProperties::linearTilingFeatures% (for linearly tiled images) or VkFormatProperties::optimalTilingFeatures9 (for optimally tiled images) - as returned by #vkGetPhysicalDeviceFormatProperties image must have been created with VK_IMAGE_USAGE_TRANSFER_DST_BIT usage flagimage must! not use a format listed in https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversionH{html_spec_relative}#features-formats-requiring-sampler-ycbcr-conversionIf image is non-sparse then it must7 be bound completely and contiguously to a single VkDeviceMemory object imageLayout must< specify the layout of the image subresource ranges of image specified in pRanges0 at the time this command is executed on a VkDevice imageLayout must be $VK_IMAGE_LAYOUT_TRANSFER_DST_OPTIMAL, VK_IMAGE_LAYOUT_GENERAL, or "VK_IMAGE_LAYOUT_SHARED_PRESENT_KHR The :: baseMipLevel% members of the elements of the pRanges array must each be less than the  mipLevels specified in * when image was created For each  element of pRanges , if the  levelCount member is not VK_REMAINING_MIP_LEVELS, then  baseMipLevel +  levelCount must be less than the  mipLevels specified in * when image was created The ::baseArrayLayer% members of the elements of the pRanges array must each be less than the  arrayLayers specified in * when image was created For each  element of pRanges , if the  layerCount member is not VK_REMAINING_ARRAY_LAYERS, then baseArrayLayer +  layerCount must be less than the  arrayLayers specified in * when image was createdimage must. not have a compressed or depth/stencil formatValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle image must be a valid VkImage handle imageLayout must be a valid  valuepColor must be a valid pointer to a valid VkClearColorValue unionpRanges must# be a valid pointer to an array of  rangeCount valid VkImageSubresourceRange structures commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must- support graphics, or compute operations This command must1 only be called outside of a render pass instance rangeCount must be greater than 0Both of  commandBuffer, and image must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Outside  Graphics Compute  Transfer See AlsoO, , 2, , >vkCmdFillBuffer - Fill a region of a buffer with a fixed value Parameters commandBufferD is the command buffer into which the command will be recorded. dstBuffer is the buffer to be filled. dstOffsetH is the byte offset into the buffer at which to start filling, and must be a multiple of 4.size% is the number of bytes to fill, and must$ be either a multiple of 4, or  VK_WHOLE_SIZE to fill the range from offset# to the end of the buffer. If  VK_WHOLE_SIZEz is used and the remaining size of the buffer is not a multiple of 4, then the nearest smaller multiple is used.dataB is the 4-byte word written repeatedly to the buffer to fill sizeY bytes of data. The data word is written to memory according to the host endianness. DescriptionvkCmdFillBufferW is treated as transfer  operation for the purposes of synchronization barriers. The  VK_BUFFER_USAGE_TRANSFER_DST_BIT must be specified in usage of VkBufferCreateInfo0 in order for the buffer to be compatible with vkCmdFillBuffer. Valid Usage dstOffset must be less than the size of  dstBuffer dstOffset must be a multiple of 4If size is not equal to  VK_WHOLE_SIZE, size must be greater than 0If size is not equal to  VK_WHOLE_SIZE, size must+ be less than or equal to the size of  dstBuffer minus  dstOffsetIf size is not equal to  VK_WHOLE_SIZE, size must be a multiple of 4 dstBuffer must have been created with  VK_BUFFER_USAGE_TRANSFER_DST_BIT usage flagIf  dstBuffer is non-sparse then it must7 be bound completely and contiguously to a single VkDeviceMemory objectValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle dstBuffer must be a valid VkBuffer handle commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must6 support transfer, graphics or compute operations This command must1 only be called outside of a render pass instanceBoth of  commandBuffer, and  dstBuffer must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type I Primary Secondary F Outside 7 Transfer Graphics Compute v Transfer See Also3, ,  VkDeviceSize?vkCmdUpdateBuffer - Update a buffer s contents from host memory Parameters commandBufferD is the command buffer into which the command will be recorded. dstBuffer) is a handle to the buffer to be updated. dstOffset@ is the byte offset into the buffer to start updating, and must be a multiple of 4.dataSize' is the number of bytes to update, and must be a multiple of 4.pDataA is a pointer to the source data for the buffer update, and must be at least dataSize bytes in size. DescriptiondataSize mustI be less than or equal to 65536 bytes. For larger updates, applications can use buffer to buffer  \https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#copies-bufferscopies.NoteBuffer updates performed with vkCmdUpdateBuffer first copy the data into command buffer memory when the command is recorded (which requires additional storage and may incur an additional allocation), and then copy the data from the command buffer into  dstBuffer+ when the command is executed on a device.6The additional cost of this functionality compared to  \https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#copies-buffersbuffer to buffer copiesm means it is only recommended for very small amounts of data, and is why it is limited to only 65536 bytes. Applications can' work around this by issuing multiple vkCmdUpdateBuffer\ commands to different ranges of the same buffer, but it is strongly recommended that they should not.bThe source data is copied from the user pointer to the command buffer when the command is called.vkCmdUpdateBuffer is only allowed outside of a render pass. This command is treated as transfer  operation, for the purposes of synchronization barriers. The  VK_BUFFER_USAGE_TRANSFER_DST_BIT must be specified in usage of 0 in order for the buffer to be compatible with vkCmdUpdateBuffer. Valid Usage dstOffset must be less than the size of  dstBufferdataSize must& be less than or equal to the size of  dstBuffer minus  dstOffset dstBuffer must have been created with  VK_BUFFER_USAGE_TRANSFER_DST_BIT usage flagIf  dstBuffer is non-sparse then it must7 be bound completely and contiguously to a single VkDeviceMemory object dstOffset must be a multiple of 4dataSize must be less than or equal to 65536dataSize must be a multiple of 4Valid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle dstBuffer must be a valid VkBuffer handlepData must# be a valid pointer to an array of dataSize bytes commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must7 support transfer, graphics, or compute operations This command must1 only be called outside of a render pass instancedataSize must be greater than 0Both of  commandBuffer, and  dstBuffer must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type I Primary Secondary F Outside 7 Transfer Graphics Compute v Transfer See Also3, ,  VkDeviceSize6vkCmdCopyImageToBuffer - Copy image data into a buffer Parameters commandBufferD is the command buffer into which the command will be recorded.srcImage is the source image.srcImageLayoutB is the layout of the source image subresources for the copy. dstBuffer is the destination buffer. regionCount" is the number of regions to copy.pRegions is a pointer to an array of ~0 structures specifying the regions to copy. DescriptionEach region in pRegionsl is copied from the specified region of the source image to the specified region of the destination buffer.If the  of srcImage is a  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversionmulti-planar image format2, regions of each plane to be a source of a copy must$ be specified separately using the pRegions member of the ~ structure. In this case, the  aspectMask of imageSubresource must be VK_IMAGE_ASPECT_PLANE_0_BIT, VK_IMAGE_ASPECT_PLANE_1_BIT, or VK_IMAGE_ASPECT_PLANE_2_BIT. For the purposes of vkCmdCopyBufferToImageQ, each plane of a multi-planar image is treated as having the format listed in  phttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-compatible-planes7{html_spec_relative}#features-formats-compatible-planes" for the plane identified by the  aspectMask9 of the corresponding subresource. This applies both to J and to coordinates used in the copy, which correspond to texels in the planeJ rather than how these texels map to coordinates in the image as a whole. Valid Usage.The image region specified by each element of pRegions must+ be a region that is contained within srcImage if the srcImage s  is not a  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversionmulti-planar format , and mustI be a region that is contained within the plane being copied if the srcImage s  is a multi-planar format /The buffer region specified by each element of pRegions must+ be a region that is contained within  dstBuffermThe union of all source regions, and the union of all destination regions, specified by the elements of pRegions, must not overlap in memorysrcImage must! use a format that supports "VK_FORMAT_FEATURE_TRANSFER_SRC_BIT, which is indicated by VkFormatProperties::linearTilingFeatures% (for linearly tiled images) or VkFormatProperties::optimalTilingFeatures9 (for optimally tiled images) - as returned by /srcImage must have been created with VK_IMAGE_USAGE_TRANSFER_SRC_BIT usage flagIf srcImage is non-sparse then it must7 be bound completely and contiguously to a single VkDeviceMemory objectsrcImage must# have a sample count equal to VK_SAMPLE_COUNT_1_BITsrcImageLayout must6 specify the layout of the image subresources of srcImage specified in pRegions0 at the time this command is executed on a VkDevicesrcImageLayout must be "VK_IMAGE_LAYOUT_SHARED_PRESENT_KHR, $VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL or VK_IMAGE_LAYOUT_GENERAL dstBuffer must have been created with  VK_BUFFER_USAGE_TRANSFER_DST_BIT usage flagIf  dstBuffer is non-sparse then it must7 be bound completely and contiguously to a single VkDeviceMemory objectThe imageSubresource.mipLevel member of each element of pRegions must be less than the  mipLevels specified in * when srcImage was createdThe imageSubresource.baseArrayLayer + imageSubresource.layerCount of each element of pRegions must# be less than or equal to the  arrayLayers specified in * when srcImage was createdThe  imageOffset and and  imageExtent! members of each element of pRegions must= respect the image transfer granularity requirements of  commandBuffer: s command pool s queue family, as described in /-Valid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle srcImage must be a valid VkImage handlesrcImageLayout must be a valid  value dstBuffer must be a valid VkBuffer handlepRegions must# be a valid pointer to an array of  regionCount valid VkBufferImageCopy structures commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must7 support transfer, graphics, or compute operations This command must1 only be called outside of a render pass instance regionCount must be greater than 0Each of  commandBuffer,  dstBuffer, and srcImage must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type I Primary Secondary F Outside 7 Transfer Graphics Compute v Transfer See Also3, ~, , 2, >vkCmdCopyBufferToImage - Copy data from a buffer into an image Parameters commandBufferD is the command buffer into which the command will be recorded. srcBuffer is the source buffer.dstImage is the destination image.dstImageLayoutG is the layout of the destination image subresources for the copy. regionCount" is the number of regions to copy.pRegions is a pointer to an array of ~0 structures specifying the regions to copy. DescriptionEach region in pRegionsl is copied from the specified region of the source buffer to the specified region of the destination image.If the format of dstImage is a  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversionmulti-planar image format3), regions of each plane to be a target of a copy must$ be specified separately using the pRegions member of the ~ structure. In this case, the  aspectMask of imageSubresource must be VK_IMAGE_ASPECT_PLANE_0_BIT, VK_IMAGE_ASPECT_PLANE_1_BIT, or VK_IMAGE_ASPECT_PLANE_2_BIT. For the purposes of vkCmdCopyBufferToImageQ, each plane of a multi-planar image is treated as having the format listed in  phttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-compatible-planes7{html_spec_relative}#features-formats-compatible-planes" for the plane identified by the  aspectMask9 of the corresponding subresource. This applies both to J and to coordinates used in the copy, which correspond to texels in the planeJ rather than how these texels map to coordinates in the image as a whole. Valid Usage/The buffer region specified by each element of pRegions must+ be a region that is contained within  srcBuffer .The image region specified by each element of pRegions must+ be a region that is contained within dstImage if the dstImage s  is not a  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversionmulti-planar format , and mustL be a region that is contained within the plane being copied to if the dstImage s  is a multi-planar formatmThe union of all source regions, and the union of all destination regions, specified by the elements of pRegions, must not overlap in memory srcBuffer must have been created with  VK_BUFFER_USAGE_TRANSFER_SRC_BIT usage flagdstImage must! use a format that supports "VK_FORMAT_FEATURE_TRANSFER_DST_BIT, which is indicated by VkFormatProperties::linearTilingFeatures% (for linearly tiled images) or VkFormatProperties::optimalTilingFeatures9 (for optimally tiled images) - as returned by /If  srcBuffer is non-sparse then it must7 be bound completely and contiguously to a single VkDeviceMemory objectdstImage must have been created with VK_IMAGE_USAGE_TRANSFER_DST_BIT usage flagIf dstImage is non-sparse then it must7 be bound completely and contiguously to a single VkDeviceMemory objectdstImage must# have a sample count equal to VK_SAMPLE_COUNT_1_BITdstImageLayout must6 specify the layout of the image subresources of dstImage specified in pRegions0 at the time this command is executed on a VkDevicedstImageLayout must be $VK_IMAGE_LAYOUT_TRANSFER_DST_OPTIMAL, VK_IMAGE_LAYOUT_GENERAL, or "VK_IMAGE_LAYOUT_SHARED_PRESENT_KHRThe imageSubresource.mipLevel member of each element of pRegions must be less than the  mipLevels specified in * when dstImage was createdThe imageSubresource.baseArrayLayer + imageSubresource.layerCount of each element of pRegions must# be less than or equal to the  arrayLayers specified in * when dstImage was createdThe  imageOffset and and  imageExtent! members of each element of pRegions must= respect the image transfer granularity requirements of  commandBuffer: s command pool s queue family, as described in /-Valid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle  srcBuffer must be a valid VkBuffer handledstImage must be a valid VkImage handledstImageLayout must be a valid  valuepRegions must# be a valid pointer to an array of  regionCount valid VkBufferImageCopy structures commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must7 support transfer, graphics, or compute operations This command must1 only be called outside of a render pass instance regionCount must be greater than 0Each of  commandBuffer, dstImage, and  srcBuffer must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type I Primary Secondary F Outside 7 Transfer Graphics Compute v Transfer See Also3, ~, , 2, UvkCmdBlitImage - Copy regions of an image, potentially performing format conversion, Parameters commandBufferD is the command buffer into which the command will be recorded.srcImage is the source image.srcImageLayoutB is the layout of the source image subresources for the blit.dstImage is the destination image.dstImageLayoutG is the layout of the destination image subresources for the blit. regionCount" is the number of regions to blit.pRegions is a pointer to an array of 0 structures specifying the regions to blit.filter is a  -B specifying the filter to apply if the blits require scaling. DescriptionvkCmdBlitImage mustA not be used for multisampled source or destination images. Use  for this purpose.3As the sizes of the source and destination extents can differ in any dimension, texels in the source extent are scaled and filtered to the destination extent. Scaling occurs via the following operations:For each destination texel, the integer coordinate of that texel is converted to an unnormalized texture coordinate, using the effective inverse of the equations described in  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#textures-unnormalized-to-integer'unnormalized to integer conversion: ubase = i +  vbase = j +  wbase = k + LThese base coordinates are then offset by the first destination offset:uoffset = ubase - xdst0voffset = vbase - ydst0woffset = wbase - zdst0aoffset = a - baseArrayCountdstlThe scale is determined from the source and destination regions, and applied to the offset coordinates:+scale_u = (xsrc1 - xsrc0) / (xdst1 - xdst0)+scale_v = (ysrc1 - ysrc0) / (ydst1 - ydst0)+scale_w = (zsrc1 - zsrc0) / (zdst1 - zdst0)uscaled = uoffset * scaleuvscaled = voffset * scalevwscaled = woffset * scalewFinally the source offset is added to the scaled coordinates, to determine the final unnormalized coordinates used to sample from srcImage:u = uscaled + xsrc0v = vscaled + ysrc0w = wscaled + zsrc0q = mipLevela = aoffset + baseArrayCountsrcMThese coordinates are used to sample from the source image, as described in  Vhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#texturesImage Operations chapter), with the filter mode equal to that of filter, a mipmap mode of VK_SAMPLER_MIPMAP_MODE_NEAREST and an address mode of %VK_SAMPLER_ADDRESS_MODE_CLAMP_TO_EDGE. Implementations must- clamp at the edge of the source image, and may6 additionally clamp to the edge of the source region.Note<Due to allowable rounding errors in the generation of the source texture coordinates, it is not always possible to guarantee exactly which source texels will be sampled for a given blit. As rounding errors are implementation dependent, the exact results of a blitting operation are also implementation dependent.0Blits are done layer by layer starting with the baseArrayLayer member of srcSubresource for the source and dstSubresource for the destination.  layerCount- layers are blitted to the destination image.P3D textures are blitted slice by slice. Slices in the source region bounded by  srcOffsets[0].z and  srcOffsets[1].z< are copied to slices in the destination region bounded by  dstOffsets[0].z and  dstOffsets[1].z'. For each destination slice, a source z. coordinate is linearly interpolated between  srcOffsets[0].z and  srcOffsets[1].z . If the filter parameter is VK_FILTER_LINEARj then the value sampled from the source image is taken by doing linear filtering using the interpolated z coordinate. If filter parameter is VK_FILTER_NEARESTq then value sampled from the source image is taken from the single nearest slice (with undefined rounding mode).3The following filtering and conversion rules apply:Integer formats canJ only be converted to other integer formats with the same signedness.QNo format conversion is supported between depth/stencil images. The formats must match.Format conversions on unorm, snorm, unscaled and packed float formats of the copied aspect of the image are performed by first converting the pixels to float values.mFor sRGB source formats, nonlinear RGB values are converted to linear representation prior to filtering.After filtering, the float values are first clamped and then cast to the destination image format. In case of sRGB destination format, linear RGB values are converted to nonlinear representation before writing the pixel to the image.Signed and unsigned integers are converted by first clamping to the representable range of the destination format, then casting the value. Valid Usage/The source region specified by each element of pRegions must+ be a region that is contained within srcImage4The destination region specified by each element of pRegions must& be a region that is contained within dstImageHThe union of all destination regions, specified by the elements of pRegions, must+ not overlap in memory with any texel that may* be sampled during the blit operationsrcImage must! use a format that supports VK_FORMAT_FEATURE_BLIT_SRC_BIT, which is indicated by VkFormatProperties::linearTilingFeatures% (for linearly tiled images) or VkFormatProperties::optimalTilingFeatures9 (for optimally tiled images) - as returned by #vkGetPhysicalDeviceFormatPropertiessrcImage must! not use a format listed in https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversionH{html_spec_relative}#features-formats-requiring-sampler-ycbcr-conversionsrcImage must have been created with VK_IMAGE_USAGE_TRANSFER_SRC_BIT usage flagIf srcImage is non-sparse then it must7 be bound completely and contiguously to a single VkDeviceMemory objectsrcImageLayout must6 specify the layout of the image subresources of srcImage specified in pRegions0 at the time this command is executed on a VkDevicesrcImageLayout must be "VK_IMAGE_LAYOUT_SHARED_PRESENT_KHR, $VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL or VK_IMAGE_LAYOUT_GENERALdstImage must! use a format that supports VK_FORMAT_FEATURE_BLIT_DST_BIT, which is indicated by VkFormatProperties::linearTilingFeatures% (for linearly tiled images) or VkFormatProperties::optimalTilingFeatures9 (for optimally tiled images) - as returned by #vkGetPhysicalDeviceFormatPropertiesdstImage must! not use a format listed in https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversionH{html_spec_relative}#features-formats-requiring-sampler-ycbcr-conversiondstImage must have been created with VK_IMAGE_USAGE_TRANSFER_DST_BIT usage flagIf dstImage is non-sparse then it must7 be bound completely and contiguously to a single VkDeviceMemory objectdstImageLayout must6 specify the layout of the image subresources of dstImage specified in pRegions0 at the time this command is executed on a VkDevicedstImageLayout must be "VK_IMAGE_LAYOUT_SHARED_PRESENT_KHR, $VK_IMAGE_LAYOUT_TRANSFER_DST_OPTIMAL or VK_IMAGE_LAYOUT_GENERALThe sample count of srcImage and dstImage must both be equal to VK_SAMPLE_COUNT_1_BIT If either of srcImage or dstImage( was created with a signed integer  , the other must8 also have been created with a signed integer  If either of srcImage or dstImage+ was created with an unsigned integer  , the other must; also have been created with an unsigned integer  If either of srcImage or dstImage9 was created with a depth/stencil format, the other must have exactly the same formatIf srcImage* was created with a depth/stencil format, filter must be VK_FILTER_NEARESTsrcImage must have been created with a samples value of VK_SAMPLE_COUNT_1_BITdstImage must have been created with a samples value of VK_SAMPLE_COUNT_1_BITIf filter is VK_FILTER_LINEAR, srcImage mustO be of a format which supports linear filtering, as specified by the 1VK_FORMAT_FEATURE_SAMPLED_IMAGE_FILTER_LINEAR_BIT flag in VkFormatProperties::linearTilingFeatures (for a linear image) or VkFormatProperties::optimalTilingFeatures0(for an optimally tiled image) returned by #vkGetPhysicalDeviceFormatPropertiesIf filter is VK_FILTER_CUBIC_IMG, srcImage mustN be of a format which supports cubic filtering, as specified by the 4VK_FORMAT_FEATURE_SAMPLED_IMAGE_FILTER_CUBIC_BIT_IMG flag in VkFormatProperties::linearTilingFeatures (for a linear image) or VkFormatProperties::optimalTilingFeatures0(for an optimally tiled image) returned by #vkGetPhysicalDeviceFormatPropertiesIf filter is VK_FILTER_CUBIC_IMG, srcImage must have a /* of VK_IMAGE_TYPE_3DThe srcSubresource.mipLevel member of each element of pRegions must be less than the  mipLevels specified in * when srcImage was createdThe dstSubresource.mipLevel member of each element of pRegions must be less than the  mipLevels specified in * when dstImage was createdThe srcSubresource.baseArrayLayer + srcSubresource.layerCount of each element of pRegions must# be less than or equal to the  arrayLayers specified in * when srcImage was createdThe dstSubresource.baseArrayLayer + dstSubresource.layerCount of each element of pRegions must# be less than or equal to the  arrayLayers specified in * when dstImage was createdValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle srcImage must be a valid VkImage handlesrcImageLayout must be a valid  valuedstImage must be a valid VkImage handledstImageLayout must be a valid  valuepRegions must# be a valid pointer to an array of  regionCount valid  VkImageBlit structuresfilter must be a valid  - value commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must! support graphics operations This command must1 only be called outside of a render pass instance regionCount must be greater than 0Each of  commandBuffer, dstImage, and srcImage must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Outside  Graphics  Transfer See Also,  -, 2, , )vkCmdCopyImage - Copy data between images Parameters commandBufferD is the command buffer into which the command will be recorded.srcImage is the source image.srcImageLayout< is the current layout of the source image subresource.dstImage is the destination image.dstImageLayoutA is the current layout of the destination image subresource. regionCount" is the number of regions to copy.pRegions is a pointer to an array of 0 structures specifying the regions to copy. DescriptionEach region in pRegionsO is copied from the source image to the same region of the destination image. srcImage and dstImage can- be the same image or alias the same memory.The formats of srcImage and dstImage musty be compatible. Formats are considered compatible if their element size is the same between both formats. For example, VK_FORMAT_R8G8B8A8_UNORM is compatible with VK_FORMAT_R32_UINTA because both texels are 4 bytes in size. Depth/stencil formats must match exactly.If the format of srcImage or dstImage is a  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversion/multi-planar/ image format&, regions of each plane to be copied must$ be specified separately using the srcSubresource and dstSubresource members of the  structure. In this case, the  aspectMask of the srcSubresource or dstSubresource' that refers to the multi-planar image must be VK_IMAGE_ASPECT_PLANE_0_BIT, VK_IMAGE_ASPECT_PLANE_1_BIT, or VK_IMAGE_ASPECT_PLANE_2_BIT. For the purposes of vkCmdCopyImageR, each plane of a multi-planar image is treated as having the format listed in  phttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-compatible-planes7{html_spec_relative}#features-formats-compatible-planes" for the plane identified by the  aspectMask9 of the corresponding subresource. This applies both to J and to coordinates used in the copy, which correspond to texels in the planeJ rather than how these texels map to coordinates in the image as a whole.NoteFor example, the VK_IMAGE_ASPECT_PLANE_1_BIT plane of a "VK_FORMAT_G8_B8R8_2PLANE_420_UNORM. image is compatible with an image of format VK_FORMAT_R8G8_UNORM and (less usefully) with the VK_IMAGE_ASPECT_PLANE_0_BIT plane of an image of format 4VK_FORMAT_G10X6_B10X6_R10X6_3PLANE_420_UNORM_3PACK16$, as each texel is 2 bytes in size.vkCmdCopyImage allows copying between size-compatible6 compressed and uncompressed internal formats. Formats are size-compatible if the element size of the uncompressed format is equal to the element size (compressed texel block size) of the compressed format. Such a copy does not perform on-the-fly compression or decompression. When copying from an uncompressed format to a compressed format, each texel of uncompressed data of the source image is copied as a raw value to the corresponding compressed texel block of the destination image. When copying from a compressed format to an uncompressed format, each compressed texel block of the source image is copied as a raw value to the corresponding texel of uncompressed data in the destination image. Thus, for example, it is legal to copy between a 128-bit uncompressed format and a compressed format which has a 128-bit sized compressed texel block representing 44 texels (using 8 bits per texel), or between a 64-bit uncompressed format and a compressed format which has a 64-bit sized compressed texel block representing 44 texels (using 4 bits per texel).=When copying between compressed and uncompressed formats the extentA members represent the texel dimensions of the source image and not the destination. When copying from a compressed image to an uncompressed image the image texel dimensions written to the uncompressed image will be source extent divided by the compressed texel block dimensions. When copying from an uncompressed image to a compressed image the image texel dimensions written to the compressed image will be the source extent multiplied by the compressed texel block dimensions. In both cases the number of bytes read and the number of bytes written will be identical.Copying to or from block-compressed images is typically done in multiples of the compressed texel block size. For this reason the extent mustf be a multiple of the compressed texel block dimension. There is one exception to this rule which is required to handle compressed images created with dimensions that are not a multiple of the compressed texel block dimensions: if the srcImage is compressed, then:If  extent.widthC is not a multiple of the compressed texel block width, then ( extent.width +  srcOffset.x) must( equal the image subresource width.If  extent.heightD is not a multiple of the compressed texel block height, then ( extent.height +  srcOffset.y) must) equal the image subresource height.If  extent.depthC is not a multiple of the compressed texel block depth, then ( extent.depth +  srcOffset.z) must( equal the image subresource depth.Similarly, if the dstImage is compressed, then:If  extent.widthC is not a multiple of the compressed texel block width, then ( extent.width +  dstOffset.x) must( equal the image subresource width.If  extent.heightD is not a multiple of the compressed texel block height, then ( extent.height +  dstOffset.y) must) equal the image subresource height.If  extent.depthC is not a multiple of the compressed texel block depth, then ( extent.depth +  dstOffset.z) must( equal the image subresource depth.This allows the last compressed texel block of the image in each non-multiple dimension to be included as a source or destination of the copy. _422  image formats that are not  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversion/multi-planar/V are treated as having a 21 compressed texel block for the purposes of these rules.vkCmdCopyImage canI be used to copy image data between multisample images, but both images must! have the same number of samples. Valid Usage/The source region specified by each element of pRegions must+ be a region that is contained within srcImage if the srcImage s  is not a  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversionmulti-planar format , and mustI be a region that is contained within the plane being copied if the srcImage s  is a multi-planar format4The destination region specified by each element of pRegions must& be a region that is contained within dstImage if the dstImage s  is not a  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversionmulti-planar format , and mustL be a region that is contained within the plane being copied to if the dstImage s  is a multi-planar formatmThe union of all source regions, and the union of all destination regions, specified by the elements of pRegions, must not overlap in memorysrcImage must! use a format that supports "VK_FORMAT_FEATURE_TRANSFER_SRC_BIT, which is indicated by VkFormatProperties::linearTilingFeatures% (for linearly tiled images) or VkFormatProperties::optimalTilingFeatures9 (for optimally tiled images) - as returned by /srcImage must have been created with VK_IMAGE_USAGE_TRANSFER_SRC_BIT usage flagIf srcImage! is non-sparse then the image or disjoint plane to be copied must7 be bound completely and contiguously to a single VkDeviceMemory objectsrcImageLayout must6 specify the layout of the image subresources of srcImage specified in pRegions0 at the time this command is executed on a VkDevicesrcImageLayout must be $VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL, VK_IMAGE_LAYOUT_GENERAL, or "VK_IMAGE_LAYOUT_SHARED_PRESENT_KHRdstImage must! use a format that supports "VK_FORMAT_FEATURE_TRANSFER_DST_BIT, which is indicated by VkFormatProperties::linearTilingFeatures% (for linearly tiled images) or VkFormatProperties::optimalTilingFeatures9 (for optimally tiled images) - as returned by /dstImage must have been created with VK_IMAGE_USAGE_TRANSFER_DST_BIT usage flagIf dstImage! is non-sparse then the image or disjoint0 plane that is the destination of the copy must7 be bound completely and contiguously to a single VkDeviceMemory objectdstImageLayout must6 specify the layout of the image subresources of dstImage specified in pRegions0 at the time this command is executed on a VkDevicedstImageLayout must be $VK_IMAGE_LAYOUT_TRANSFER_DST_OPTIMAL, VK_IMAGE_LAYOUT_GENERAL, or "VK_IMAGE_LAYOUT_SHARED_PRESENT_KHRIf the  of each of srcImage and dstImage is not a  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversion/multi-planar format/ , the  of each of srcImage and dstImage must be compatible, as defined phttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#copies-images-format-compatibilitybelow"In a copy to or from a plane of a  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversionmulti-planar image , the  of the image and plane must be compatible according to  phttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-compatible-planes)the description of compatible planes for the plane being copied4When a copy is performed to or from an image with a  https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-formats-requiring-sampler-ycbcr-conversionmulti-planar format , the  aspectMask of the srcSubresource and/or dstSubresource, that refers to the multi-planar image must be VK_IMAGE_ASPECT_PLANE_0_BIT, VK_IMAGE_ASPECT_PLANE_1_BIT , or VK_IMAGE_ASPECT_PLANE_2_BIT (with VK_IMAGE_ASPECT_PLANE_2_BIT valid only for a  with three planes)The sample count of srcImage and dstImage must matchThe srcSubresource.mipLevel member of each element of pRegions must be less than the  mipLevels specified in * when srcImage was createdThe dstSubresource.mipLevel member of each element of pRegions must be less than the  mipLevels specified in * when dstImage was createdThe srcSubresource.baseArrayLayer + srcSubresource.layerCount of each element of pRegions must# be less than or equal to the  arrayLayers specified in * when srcImage was createdThe dstSubresource.baseArrayLayer + dstSubresource.layerCount of each element of pRegions must# be less than or equal to the  arrayLayers specified in * when dstImage was createdThe  srcOffset and and extent! members of each element of pRegions must= respect the image transfer granularity requirements of  commandBuffer: s command pool s queue family, as described in /-The  dstOffset and and extent! members of each element of pRegions must= respect the image transfer granularity requirements of  commandBuffer: s command pool s queue family, as described in /-Valid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle srcImage must be a valid VkImage handlesrcImageLayout must be a valid  valuedstImage must be a valid VkImage handledstImageLayout must be a valid  valuepRegions must# be a valid pointer to an array of  regionCount valid  VkImageCopy structures commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must7 support transfer, graphics, or compute operations This command must1 only be called outside of a render pass instance regionCount must be greater than 0Each of  commandBuffer, dstImage, and srcImage must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type I Primary Secondary F Outside 7 Transfer Graphics Compute v Transfer See Also, 2, , 2vkCmdCopyBuffer - Copy data between buffer regions Parameters commandBufferD is the command buffer into which the command will be recorded. srcBuffer is the source buffer. dstBuffer is the destination buffer. regionCount" is the number of regions to copy.pRegions is a pointer to an array of 0 structures specifying the regions to copy. DescriptionEach region in pRegionsQ is copied from the source buffer to the same region of the destination buffer.  srcBuffer and  dstBuffer canr be the same buffer or alias the same memory, but the result is undefined if the copy regions overlap in memory. Valid UsageThe size member of each element of pRegions must be greater than 0 The  srcOffset member of each element of pRegions must be less than the size of  srcBufferThe  dstOffset member of each element of pRegions must be less than the size of  dstBufferThe size member of each element of pRegions must+ be less than or equal to the size of  srcBuffer minus  srcOffsetThe size member of each element of pRegions must+ be less than or equal to the size of  dstBuffer minus  dstOffsetmThe union of the source regions, and the union of the destination regions, specified by the elements of pRegions, must not overlap in memory srcBuffer must have been created with  VK_BUFFER_USAGE_TRANSFER_SRC_BIT usage flagIf  srcBuffer is non-sparse then it must7 be bound completely and contiguously to a single VkDeviceMemory object dstBuffer must have been created with  VK_BUFFER_USAGE_TRANSFER_DST_BIT usage flagIf  dstBuffer is non-sparse then it must7 be bound completely and contiguously to a single VkDeviceMemory objectValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle srcBuffer must be a valid VkBuffer handle dstBuffer must be a valid VkBuffer handlepRegions must# be a valid pointer to an array of  regionCount  VkBufferCopy structures commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must7 support transfer, graphics, or compute operations This command must1 only be called outside of a render pass instance regionCount must be greater than 0Each of  commandBuffer,  dstBuffer, and  srcBuffer must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type I Primary Secondary F Outside 7 Transfer Graphics Compute v Transfer See Also3, , NvkCmdDispatchIndirect - Dispatch compute work items using indirect parameters Parameters commandBufferD is the command buffer into which the command will be recorded.buffer. is the buffer containing dispatch parameters.offset is the byte offset into buffer where parameters begin. DescriptionvkCmdDispatchIndirect behaves similarly to  except that the parameters are read by the device from a buffer during execution. The parameters of the dispatch are encoded in a S structure taken from buffer starting at offset. Valid UsageIf buffer is non-sparse then it must7 be bound completely and contiguously to a single VkDeviceMemory object For each set n that is statically used by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_COMPUTE, a descriptor set must have been bound to n at VK_PIPELINE_BIND_POINT_COMPUTE, with a VkPipelineLayout that is compatible for set n, with the VkPipelineLayout used to create the current  VkPipeline, as described in jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-compatibility1{html_spec_relative}#descriptorsets-compatibility=Descriptors in each bound descriptor set, specified via vkCmdBindDescriptorSets, must8 be valid if they are statically used by the bound  VkPipeline object, specified via vkCmdBindPipelineA valid compute pipeline must2 be bound to the current command buffer with VK_PIPELINE_BIND_POINT_COMPUTEbuffer must! have been created with the #VK_BUFFER_USAGE_INDIRECT_BUFFER_BIT bit setoffset must be a multiple of 4 The sum of offset and the size of VkDispatchIndirectCommand must& be less than or equal to the size of buffer6For each push constant that is statically used by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_COMPUTE, a push constant value must have been set for VK_PIPELINE_BIND_POINT_COMPUTE, with a VkPipelineLayoutT that is compatible for push constants with the one used to create the current  VkPipeline, as described in jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-compatibility1{html_spec_relative}#descriptorsets-compatibilityIf any  VkSampler3 object that is accessed from a shader by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_COMPUTE( uses unnormalized coordinates, it must% not be used to sample from any VkImage with a  VkImageView of the type VK_IMAGE_VIEW_TYPE_3D, VK_IMAGE_VIEW_TYPE_CUBE, VK_IMAGE_VIEW_TYPE_1D_ARRAY, VK_IMAGE_VIEW_TYPE_2D_ARRAY or VK_IMAGE_VIEW_TYPE_CUBE_ARRAY, in any shader stageIf any  VkSampler3 object that is accessed from a shader by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_COMPUTE( uses unnormalized coordinates, it must) not be used with any of the SPIR-V OpImageSample* or OpImageSparseSample* instructions with  ImplicitLod, Dref or Proj# in their name, in any shader stageIf any  VkSampler3 object that is accessed from a shader by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_COMPUTE( uses unnormalized coordinates, it must) not be used with any of the SPIR-V OpImageSample* or OpImageSparseSample*U instructions that includes a LOD bias or any offset values, in any shader stageIf the  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-robustBufferAccessrobust buffer access: feature is not enabled, and any shader stage in the  VkPipeline object bound to VK_PIPELINE_BIND_POINT_COMPUTE$ accesses a uniform buffer, it musta not access values outside of the range of that buffer specified in the bound descriptor setIf the  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-robustBufferAccessrobust buffer access: feature is not enabled, and any shader stage in the  VkPipeline object bound to VK_PIPELINE_BIND_POINT_COMPUTE$ accesses a storage buffer, it musta not access values outside of the range of that buffer specified in the bound descriptor setAny  VkImageView being sampled with VK_FILTER_LINEAR" as a result of this command mustO be of a format which supports linear filtering, as specified by the 1VK_FORMAT_FEATURE_SAMPLED_IMAGE_FILTER_LINEAR_BIT flag in VkFormatProperties::linearTilingFeatures (for a linear image) or VkFormatProperties::optimalTilingFeatures0(for an optimally tiled image) returned by #vkGetPhysicalDeviceFormatPropertiesAny w being sampled with VK_FILTER_CUBIC_IMG as a result of this command mustN be of a format which supports cubic filtering, as specified by the 4VK_FORMAT_FEATURE_SAMPLED_IMAGE_FILTER_CUBIC_BIT_IMG flag in VkFormatProperties::linearTilingFeatures (for a linear image) or VkFormatProperties::optimalTilingFeatures0(for an optimally tiled image) returned by #vkGetPhysicalDeviceFormatPropertiesAny w being sampled with VK_FILTER_CUBIC_IMG as a result of this command must not have a w of VK_IMAGE_VIEW_TYPE_3D, VK_IMAGE_VIEW_TYPE_CUBE , or VK_IMAGE_VIEW_TYPE_CUBE_ARRAYValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handlebuffer must be a valid VkBuffer handle commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must support compute operations This command must1 only be called outside of a render pass instanceBoth of buffer, and  commandBuffer must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Outside  Compute  Compute See Also3, ,  VkDeviceSize+vkCmdDispatch - Dispatch compute work items Parameters commandBufferD is the command buffer into which the command will be recorded. groupCountXG is the number of local workgroups to dispatch in the X dimension. groupCountYG is the number of local workgroups to dispatch in the Y dimension. groupCountZG is the number of local workgroups to dispatch in the Z dimension. DescriptionWhen the command is executed, a global workgroup consisting of groupCountX groupCountY groupCountZ local workgroups is assembled. Valid Usage groupCountX must be less than or equal to VkPhysicalDeviceLimits::maxComputeWorkGroupCount[0] groupCountY must be less than or equal to VkPhysicalDeviceLimits::maxComputeWorkGroupCount[1] groupCountZ must be less than or equal to VkPhysicalDeviceLimits::maxComputeWorkGroupCount[2] For each set n that is statically used by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_COMPUTE, a descriptor set must have been bound to n at VK_PIPELINE_BIND_POINT_COMPUTE, with a VkPipelineLayout that is compatible for set n, with the VkPipelineLayout used to create the current  VkPipeline, as described in jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-compatibility1{html_spec_relative}#descriptorsets-compatibility=Descriptors in each bound descriptor set, specified via vkCmdBindDescriptorSets, must8 be valid if they are statically used by the bound  VkPipeline object, specified via vkCmdBindPipelineA valid compute pipeline must2 be bound to the current command buffer with VK_PIPELINE_BIND_POINT_COMPUTE6For each push constant that is statically used by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_COMPUTE, a push constant value must have been set for VK_PIPELINE_BIND_POINT_COMPUTE, with a VkPipelineLayoutT that is compatible for push constants with the one used to create the current  VkPipeline, as described in jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-compatibility1{html_spec_relative}#descriptorsets-compatibilityIf any  VkSampler3 object that is accessed from a shader by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_COMPUTE( uses unnormalized coordinates, it must% not be used to sample from any VkImage with a  VkImageView of the type VK_IMAGE_VIEW_TYPE_3D, VK_IMAGE_VIEW_TYPE_CUBE, VK_IMAGE_VIEW_TYPE_1D_ARRAY, VK_IMAGE_VIEW_TYPE_2D_ARRAY or VK_IMAGE_VIEW_TYPE_CUBE_ARRAY, in any shader stageIf any  VkSampler3 object that is accessed from a shader by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_COMPUTE( uses unnormalized coordinates, it must) not be used with any of the SPIR-V OpImageSample* or OpImageSparseSample* instructions with  ImplicitLod, Dref or Proj# in their name, in any shader stageIf any  VkSampler3 object that is accessed from a shader by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_COMPUTE( uses unnormalized coordinates, it must) not be used with any of the SPIR-V OpImageSample* or OpImageSparseSample*U instructions that includes a LOD bias or any offset values, in any shader stageIf the  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-robustBufferAccessrobust buffer access: feature is not enabled, and any shader stage in the  VkPipeline object bound to VK_PIPELINE_BIND_POINT_COMPUTE$ accesses a uniform buffer, it musta not access values outside of the range of that buffer specified in the bound descriptor setIf the  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-robustBufferAccessrobust buffer access: feature is not enabled, and any shader stage in the  VkPipeline object bound to VK_PIPELINE_BIND_POINT_COMPUTE$ accesses a storage buffer, it musta not access values outside of the range of that buffer specified in the bound descriptor setAny  VkImageView being sampled with VK_FILTER_LINEAR" as a result of this command mustO be of a format which supports linear filtering, as specified by the 1VK_FORMAT_FEATURE_SAMPLED_IMAGE_FILTER_LINEAR_BIT flag in VkFormatProperties::linearTilingFeatures (for a linear image) or VkFormatProperties::optimalTilingFeatures0(for an optimally tiled image) returned by #vkGetPhysicalDeviceFormatPropertiesAny w being sampled with VK_FILTER_CUBIC_IMG as a result of this command mustN be of a format which supports cubic filtering, as specified by the 4VK_FORMAT_FEATURE_SAMPLED_IMAGE_FILTER_CUBIC_BIT_IMG flag in VkFormatProperties::linearTilingFeatures (for a linear image) or VkFormatProperties::optimalTilingFeatures0(for an optimally tiled image) returned by #vkGetPhysicalDeviceFormatPropertiesAny w being sampled with VK_FILTER_CUBIC_IMG as a result of this command must not have a w of VK_IMAGE_VIEW_TYPE_3D, VK_IMAGE_VIEW_TYPE_CUBE , or VK_IMAGE_VIEW_TYPE_CUBE_ARRAYValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must support compute operations This command must1 only be called outside of a render pass instanceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Outside  Compute  Compute See Also;vkCmdDrawIndexedIndirect - Perform an indexed indirect draw Parameters commandBuffer? is the command buffer into which the command is recorded.buffer* is the buffer containing draw parameters.offset is the byte offset into buffer where parameters begin. drawCount( is the number of draws to execute, and can be zero.strideD is the byte stride between successive sets of draw parameters. DescriptionvkCmdDrawIndexedIndirect behaves similarly to U except that the parameters are read by the device from a buffer during execution.  drawCount@ draws are executed by the command, with parameters taken from buffer starting at offset and increasing by strideY bytes for each successive draw. The parameters of each draw are encoded in an array of X structures. If  drawCount is less than or equal to one, stride is ignored. Valid UsageIf buffer is non-sparse then it must7 be bound completely and contiguously to a single VkDeviceMemory objectbuffer must! have been created with the #VK_BUFFER_USAGE_INDIRECT_BUFFER_BIT bit setoffset must be a multiple of 4If  drawCount is greater than 1, stride must be a multiple of 4 and must" be greater than or equal to sizeof(VkDrawIndexedIndirectCommand)If the  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-multiDrawIndirectmulti-draw indirect feature is not enabled,  drawCount must be 0 or 1 If the  yhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-drawIndirectFirstInstancedrawIndirectFirstInstance& feature is not enabled, all the  firstInstance members of the VkDrawIndexedIndirectCommand* structures accessed by this command must be 0The current render pass must be  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#renderpass-compatibility compatible with the  renderPass member of the VkGraphicsPipelineCreateInfo, structure specified when creating the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS.-The subpass index of the current render pass must be equal to the subpass member of the VkGraphicsPipelineCreateInfo, structure specified when creating the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS. For each set n that is statically used by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS, a descriptor set must have been bound to n at VK_PIPELINE_BIND_POINT_GRAPHICS, with a VkPipelineLayout that is compatible for set n, with the VkPipelineLayout used to create the current  VkPipeline, as described in jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-compatibility1{html_spec_relative}#descriptorsets-compatibility6For each push constant that is statically used by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS, a push constant value must have been set for VK_PIPELINE_BIND_POINT_GRAPHICS, with a VkPipelineLayout6 that is compatible for push constants, with the VkPipelineLayout used to create the current  VkPipeline, as described in jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-compatibility1{html_spec_relative}#descriptorsets-compatibility=Descriptors in each bound descriptor set, specified via vkCmdBindDescriptorSets, must8 be valid if they are statically used by the bound  VkPipeline object, specified via vkCmdBindPipelineyAll vertex input bindings accessed via vertex input variables declared in the vertex shader entry point s interface must have valid buffers boundA valid graphics pipeline must2 be bound to the current command buffer with VK_PIPELINE_BIND_POINT_GRAPHICSIf the  VkPipeline object bound to VK_PIPELINE_BIND_POINT_GRAPHICS- requires any dynamic state, that state must, have been set on the current command bufferIf  drawCount is equal to 1, (offset + sizeof(VkDrawIndexedIndirectCommand)) must+ be less than or equal to the size of bufferIf  drawCount is greater than 1, (stride ( drawCount - 1) + offset + sizeof(VkDrawIndexedIndirectCommand)) must+ be less than or equal to the size of buffer drawCount must be less than or equal to VkPhysicalDeviceLimits::maxDrawIndirectCount3Every input attachment used by the current subpass must3 be bound to the pipeline via a descriptor setIf any  VkSampler3 object that is accessed from a shader by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS( uses unnormalized coordinates, it must% not be used to sample from any VkImage with a  VkImageView of the type VK_IMAGE_VIEW_TYPE_3D, VK_IMAGE_VIEW_TYPE_CUBE, VK_IMAGE_VIEW_TYPE_1D_ARRAY, VK_IMAGE_VIEW_TYPE_2D_ARRAY or VK_IMAGE_VIEW_TYPE_CUBE_ARRAY, in any shader stageIf any  VkSampler3 object that is accessed from a shader by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS( uses unnormalized coordinates, it must) not be used with any of the SPIR-V OpImageSample* or OpImageSparseSample* instructions with  ImplicitLod, Dref or Proj# in their name, in any shader stageIf any  VkSampler3 object that is accessed from a shader by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS( uses unnormalized coordinates, it must) not be used with any of the SPIR-V OpImageSample* or OpImageSparseSample*U instructions that includes a LOD bias or any offset values, in any shader stageIf the  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-robustBufferAccessrobust buffer access: feature is not enabled, and any shader stage in the  VkPipeline object bound to VK_PIPELINE_BIND_POINT_GRAPHICS$ accesses a uniform buffer, it musta not access values outside of the range of that buffer specified in the bound descriptor setIf the  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-robustBufferAccessrobust buffer access: feature is not enabled, and any shader stage in the  VkPipeline object bound to VK_PIPELINE_BIND_POINT_GRAPHICS$ accesses a storage buffer, it musta not access values outside of the range of that buffer specified in the bound descriptor setAny  VkImageView being sampled with VK_FILTER_LINEAR" as a result of this command mustO be of a format which supports linear filtering, as specified by the 1VK_FORMAT_FEATURE_SAMPLED_IMAGE_FILTER_LINEAR_BIT flag in VkFormatProperties::linearTilingFeatures (for a linear image) or VkFormatProperties::optimalTilingFeatures0(for an optimally tiled image) returned by #vkGetPhysicalDeviceFormatPropertiesGImage subresources used as attachments in the current render pass mustM not be accessed in any way other than as an attachment by this command.Any w being sampled with VK_FILTER_CUBIC_IMG as a result of this command mustN be of a format which supports cubic filtering, as specified by the 4VK_FORMAT_FEATURE_SAMPLED_IMAGE_FILTER_CUBIC_BIT_IMG flag in VkFormatProperties::linearTilingFeatures (for a linear image) or VkFormatProperties::optimalTilingFeatures0(for an optimally tiled image) returned by #vkGetPhysicalDeviceFormatPropertiesAny w being sampled with VK_FILTER_CUBIC_IMG as a result of this command must not have a w of VK_IMAGE_VIEW_TYPE_3D, VK_IMAGE_VIEW_TYPE_CUBE , or VK_IMAGE_VIEW_TYPE_CUBE_ARRAYjIf the draw is recorded in a render pass instance with multiview enabled, the maximum instance index must be less than or equal to d::maxMultiviewInstanceIndex.5If the bound graphics pipeline was created with [::sampleLocationsEnable set to VK_TRUES and the current subpass has a depth/stencil attachment, then that attachment must! have been created with the 9VK_IMAGE_CREATE_SAMPLE_LOCATIONS_COMPATIBLE_DEPTH_BIT_EXT bit setValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handlebuffer must be a valid VkBuffer handle commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must! support graphics operations This command must0 only be called inside of a render pass instanceBoth of buffer, and  commandBuffer must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Inside  Graphics  Graphics See Also3, ,  VkDeviceSize@vkCmdDrawIndirect - Issue an indirect draw into a command buffer Parameters commandBuffer? is the command buffer into which the command is recorded.buffer* is the buffer containing draw parameters.offset is the byte offset into buffer where parameters begin. drawCount( is the number of draws to execute, and can be zero.strideD is the byte stride between successive sets of draw parameters. DescriptionvkCmdDrawIndirect behaves similarly to U except that the parameters are read by the device from a buffer during execution.  drawCount@ draws are executed by the command, with parameters taken from buffer starting at offset and increasing by strideZ bytes for each successive draw. The parameters of each draw are encoded in an array of _ structures. If  drawCount is less than or equal to one, stride is ignored. Valid UsageIf buffer is non-sparse then it must7 be bound completely and contiguously to a single VkDeviceMemory objectbuffer must! have been created with the #VK_BUFFER_USAGE_INDIRECT_BUFFER_BIT bit setoffset must be a multiple of 4If  drawCount is greater than 1, stride must be a multiple of 4 and must" be greater than or equal to sizeof(VkDrawIndirectCommand)If the  qhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-multiDrawIndirectmulti-draw indirect feature is not enabled,  drawCount must be 0 or 1 If the  yhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-drawIndirectFirstInstancedrawIndirectFirstInstance& feature is not enabled, all the  firstInstance members of the VkDrawIndirectCommand% structures accessed by this command must be 0The current render pass must be  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#renderpass-compatibility compatible with the  renderPass member of the VkGraphicsPipelineCreateInfo, structure specified when creating the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS.-The subpass index of the current render pass must be equal to the subpass member of the VkGraphicsPipelineCreateInfo, structure specified when creating the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS. For each set n that is statically used by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS, a descriptor set must have been bound to n at VK_PIPELINE_BIND_POINT_GRAPHICS, with a VkPipelineLayout that is compatible for set n, with the VkPipelineLayout used to create the current  VkPipeline, as described in jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-compatibility1{html_spec_relative}#descriptorsets-compatibility6For each push constant that is statically used by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS, a push constant value must have been set for VK_PIPELINE_BIND_POINT_GRAPHICS, with a VkPipelineLayout6 that is compatible for push constants, with the VkPipelineLayout used to create the current  VkPipeline, as described in jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-compatibility1{html_spec_relative}#descriptorsets-compatibility=Descriptors in each bound descriptor set, specified via vkCmdBindDescriptorSets, must8 be valid if they are statically used by the bound  VkPipeline object, specified via vkCmdBindPipelineyAll vertex input bindings accessed via vertex input variables declared in the vertex shader entry point s interface must have valid buffers boundA valid graphics pipeline must2 be bound to the current command buffer with VK_PIPELINE_BIND_POINT_GRAPHICSIf the  VkPipeline object bound to VK_PIPELINE_BIND_POINT_GRAPHICS- requires any dynamic state, that state must, have been set on the current command bufferIf  drawCount is equal to 1, (offset + sizeof(_)) must+ be less than or equal to the size of bufferIf  drawCount is greater than 1, (stride ( drawCount - 1) + offset + sizeof(_)) must+ be less than or equal to the size of buffer drawCount must be less than or equal to VkPhysicalDeviceLimits::maxDrawIndirectCount3Every input attachment used by the current subpass must3 be bound to the pipeline via a descriptor setIf any  VkSampler3 object that is accessed from a shader by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS( uses unnormalized coordinates, it must% not be used to sample from any VkImage with a  VkImageView of the type VK_IMAGE_VIEW_TYPE_3D, VK_IMAGE_VIEW_TYPE_CUBE, VK_IMAGE_VIEW_TYPE_1D_ARRAY, VK_IMAGE_VIEW_TYPE_2D_ARRAY or VK_IMAGE_VIEW_TYPE_CUBE_ARRAY, in any shader stageIf any  VkSampler3 object that is accessed from a shader by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS( uses unnormalized coordinates, it must) not be used with any of the SPIR-V OpImageSample* or OpImageSparseSample* instructions with  ImplicitLod, Dref or Proj# in their name, in any shader stageIf any  VkSampler3 object that is accessed from a shader by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS( uses unnormalized coordinates, it must) not be used with any of the SPIR-V OpImageSample* or OpImageSparseSample*U instructions that includes a LOD bias or any offset values, in any shader stageIf the  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-robustBufferAccessrobust buffer access: feature is not enabled, and any shader stage in the  VkPipeline object bound to VK_PIPELINE_BIND_POINT_GRAPHICS$ accesses a uniform buffer, it musta not access values outside of the range of that buffer specified in the bound descriptor setIf the  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-robustBufferAccessrobust buffer access: feature is not enabled, and any shader stage in the  VkPipeline object bound to VK_PIPELINE_BIND_POINT_GRAPHICS$ accesses a storage buffer, it musta not access values outside of the range of that buffer specified in the bound descriptor setAny  VkImageView being sampled with VK_FILTER_LINEAR" as a result of this command mustO be of a format which supports linear filtering, as specified by the 1VK_FORMAT_FEATURE_SAMPLED_IMAGE_FILTER_LINEAR_BIT flag in VkFormatProperties::linearTilingFeatures (for a linear image) or VkFormatProperties::optimalTilingFeatures0(for an optimally tiled image) returned by #vkGetPhysicalDeviceFormatPropertiesGImage subresources used as attachments in the current render pass mustM not be accessed in any way other than as an attachment by this command.Any w being sampled with VK_FILTER_CUBIC_IMG as a result of this command mustN be of a format which supports cubic filtering, as specified by the 4VK_FORMAT_FEATURE_SAMPLED_IMAGE_FILTER_CUBIC_BIT_IMG flag in VkFormatProperties::linearTilingFeatures (for a linear image) or VkFormatProperties::optimalTilingFeatures0(for an optimally tiled image) returned by #vkGetPhysicalDeviceFormatPropertiesAny w being sampled with VK_FILTER_CUBIC_IMG as a result of this command must not have a w of VK_IMAGE_VIEW_TYPE_3D, VK_IMAGE_VIEW_TYPE_CUBE , or VK_IMAGE_VIEW_TYPE_CUBE_ARRAYjIf the draw is recorded in a render pass instance with multiview enabled, the maximum instance index must be less than or equal to d::maxMultiviewInstanceIndex.5If the bound graphics pipeline was created with [::sampleLocationsEnable set to VK_TRUES and the current subpass has a depth/stencil attachment, then that attachment must! have been created with the 9VK_IMAGE_CREATE_SAMPLE_LOCATIONS_COMPATIBLE_DEPTH_BIT_EXT bit setValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handlebuffer must be a valid VkBuffer handle commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must! support graphics operations This command must0 only be called inside of a render pass instanceBoth of buffer, and  commandBuffer must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Inside  Graphics  Graphics See Also3, ,  VkDeviceSize>vkCmdDrawIndexed - Issue an indexed draw into a command buffer Parameters commandBuffer? is the command buffer into which the command is recorded. indexCount# is the number of vertices to draw. instanceCount$ is the number of instances to draw. firstIndex+ is the base index within the index buffer. vertexOffsetT is the value added to the vertex index before indexing into the vertex buffer. firstInstance2 is the instance ID of the first instance to draw. DescriptionaWhen the command is executed, primitives are assembled using the current primitive topology and  indexCount vertices whose indices are retrieved from the index buffer. The index buffer is treated as an array of tightly packed unsigned integers of size defined by the :: indexType, parameter with which the buffer was bound.*The first vertex index is at an offset of  firstIndex *  indexSize + offset& within the bound index buffer, where offset is the offset specified by vkCmdBindIndexBuffer and  indexSize, is the byte size of the type specified by  indexType. Subsequent index values are retrieved from consecutive locations in the index buffer. Indices are first compared to the primitive restart value, then zero extended to 32 bits (if the  indexType is VK_INDEX_TYPE_UINT16 ) and have  vertexOffset. added to them, before being supplied as the  vertexIndex value.The primitives are drawn  instanceCount times with  instanceIndex starting with  firstInstancen and increasing sequentially for each instance. The assembled primitives execute the bound graphics pipeline. Valid UsageThe current render pass must be  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#renderpass-compatibility compatible with the  renderPass member of the VkGraphicsPipelineCreateInfo, structure specified when creating the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS.-The subpass index of the current render pass must be equal to the subpass member of the VkGraphicsPipelineCreateInfo, structure specified when creating the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS. For each set n that is statically used by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS, a descriptor set must have been bound to n at VK_PIPELINE_BIND_POINT_GRAPHICS, with a VkPipelineLayout that is compatible for set n, with the VkPipelineLayout used to create the current  VkPipeline, as described in jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-compatibility1{html_spec_relative}#descriptorsets-compatibility6For each push constant that is statically used by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS, a push constant value must have been set for VK_PIPELINE_BIND_POINT_GRAPHICS, with a VkPipelineLayout6 that is compatible for push constants, with the VkPipelineLayout used to create the current  VkPipeline, as described in jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-compatibility1{html_spec_relative}#descriptorsets-compatibility=Descriptors in each bound descriptor set, specified via vkCmdBindDescriptorSets, must8 be valid if they are statically used by the bound  VkPipeline object, specified via vkCmdBindPipelineyAll vertex input bindings accessed via vertex input variables declared in the vertex shader entry point s interface must have valid buffers bound>For a given vertex buffer binding, any attribute data fetched mustf be entirely contained within the corresponding vertex buffer binding, as described in \https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fxvertex-input#{html_spec_relative}#fxvertex-inputA valid graphics pipeline must2 be bound to the current command buffer with VK_PIPELINE_BIND_POINT_GRAPHICSIf the  VkPipeline object bound to VK_PIPELINE_BIND_POINT_GRAPHICS- requires any dynamic state, that state must, have been set on the current command buffer( indexSize * ( firstIndex +  indexCount) + offset) must| be less than or equal to the size of the bound index buffer, with indexSize being based on the type specified by  indexType, where the index buffer,  indexType, and offset are specified via vkCmdBindIndexBuffer3Every input attachment used by the current subpass must3 be bound to the pipeline via a descriptor setIf any  VkSampler3 object that is accessed from a shader by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS( uses unnormalized coordinates, it must% not be used to sample from any VkImage with a  VkImageView of the type VK_IMAGE_VIEW_TYPE_3D, VK_IMAGE_VIEW_TYPE_CUBE, VK_IMAGE_VIEW_TYPE_1D_ARRAY, VK_IMAGE_VIEW_TYPE_2D_ARRAY or VK_IMAGE_VIEW_TYPE_CUBE_ARRAY, in any shader stageIf any  VkSampler3 object that is accessed from a shader by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS( uses unnormalized coordinates, it must) not be used with any of the SPIR-V OpImageSample* or OpImageSparseSample* instructions with  ImplicitLod, Dref or Proj# in their name, in any shader stageIf any  VkSampler3 object that is accessed from a shader by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS( uses unnormalized coordinates, it must) not be used with any of the SPIR-V OpImageSample* or OpImageSparseSample*U instructions that includes a LOD bias or any offset values, in any shader stageIf the  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-robustBufferAccessrobust buffer access: feature is not enabled, and any shader stage in the  VkPipeline object bound to VK_PIPELINE_BIND_POINT_GRAPHICS$ accesses a uniform buffer, it musta not access values outside of the range of that buffer specified in the bound descriptor setIf the  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-robustBufferAccessrobust buffer access: feature is not enabled, and any shader stage in the  VkPipeline object bound to VK_PIPELINE_BIND_POINT_GRAPHICS$ accesses a storage buffer, it musta not access values outside of the range of that buffer specified in the bound descriptor setAny  VkImageView being sampled with VK_FILTER_LINEAR" as a result of this command mustO be of a format which supports linear filtering, as specified by the 1VK_FORMAT_FEATURE_SAMPLED_IMAGE_FILTER_LINEAR_BIT flag in VkFormatProperties::linearTilingFeatures (for a linear image) or VkFormatProperties::optimalTilingFeatures0(for an optimally tiled image) returned by #vkGetPhysicalDeviceFormatPropertiesGImage subresources used as attachments in the current render pass mustM not be accessed in any way other than as an attachment by this command.Any w being sampled with VK_FILTER_CUBIC_IMG as a result of this command mustN be of a format which supports cubic filtering, as specified by the 4VK_FORMAT_FEATURE_SAMPLED_IMAGE_FILTER_CUBIC_BIT_IMG flag in VkFormatProperties::linearTilingFeatures (for a linear image) or VkFormatProperties::optimalTilingFeatures0(for an optimally tiled image) returned by #vkGetPhysicalDeviceFormatPropertiesAny w being sampled with VK_FILTER_CUBIC_IMG as a result of this command must not have a w of VK_IMAGE_VIEW_TYPE_3D, VK_IMAGE_VIEW_TYPE_CUBE , or VK_IMAGE_VIEW_TYPE_CUBE_ARRAYjIf the draw is recorded in a render pass instance with multiview enabled, the maximum instance index must be less than or equal to d::maxMultiviewInstanceIndex.5If the bound graphics pipeline was created with [::sampleLocationsEnable set to VK_TRUES and the current subpass has a depth/stencil attachment, then that attachment must! have been created with the 9VK_IMAGE_CREATE_SAMPLE_LOCATIONS_COMPATIBLE_DEPTH_BIT_EXT bit setValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must! support graphics operations This command must0 only be called inside of a render pass instanceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Inside  Graphics  Graphics See AlsovkCmdDraw - Draw primitives Parameters commandBuffer? is the command buffer into which the command is recorded. vertexCount# is the number of vertices to draw. instanceCount$ is the number of instances to draw. firstVertex* is the index of the first vertex to draw. firstInstance2 is the instance ID of the first instance to draw. DescriptionaWhen the command is executed, primitives are assembled using the current primitive topology and  vertexCount, consecutive vertex indices with the first  vertexIndex value equal to  firstVertex. The primitives are drawn  instanceCount times with  instanceIndex starting with  firstInstancen and increasing sequentially for each instance. The assembled primitives execute the bound graphics pipeline. Valid UsageThe current render pass must be  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#renderpass-compatibility compatible with the  renderPass member of the VkGraphicsPipelineCreateInfo, structure specified when creating the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS.-The subpass index of the current render pass must be equal to the subpass member of the VkGraphicsPipelineCreateInfo, structure specified when creating the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS. For each set n that is statically used by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS, a descriptor set must have been bound to n at VK_PIPELINE_BIND_POINT_GRAPHICS, with a VkPipelineLayout that is compatible for set n, with the VkPipelineLayout used to create the current  VkPipeline, as described in jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-compatibility1{html_spec_relative}#descriptorsets-compatibility6For each push constant that is statically used by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS, a push constant value must have been set for VK_PIPELINE_BIND_POINT_GRAPHICS, with a VkPipelineLayout6 that is compatible for push constants, with the VkPipelineLayout used to create the current  VkPipeline, as described in jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-compatibility1{html_spec_relative}#descriptorsets-compatibility=Descriptors in each bound descriptor set, specified via vkCmdBindDescriptorSets, must8 be valid if they are statically used by the bound  VkPipeline object, specified via vkCmdBindPipelineyAll vertex input bindings accessed via vertex input variables declared in the vertex shader entry point s interface must have valid buffers bound>For a given vertex buffer binding, any attribute data fetched mustf be entirely contained within the corresponding vertex buffer binding, as described in \https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fxvertex-input#{html_spec_relative}#fxvertex-inputA valid graphics pipeline must2 be bound to the current command buffer with VK_PIPELINE_BIND_POINT_GRAPHICSIf the  VkPipeline object bound to VK_PIPELINE_BIND_POINT_GRAPHICS- requires any dynamic state, that state must, have been set on the current command buffer3Every input attachment used by the current subpass must3 be bound to the pipeline via a descriptor setIf any  VkSampler3 object that is accessed from a shader by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS( uses unnormalized coordinates, it must% not be used to sample from any VkImage with a  VkImageView of the type VK_IMAGE_VIEW_TYPE_3D, VK_IMAGE_VIEW_TYPE_CUBE, VK_IMAGE_VIEW_TYPE_1D_ARRAY, VK_IMAGE_VIEW_TYPE_2D_ARRAY or VK_IMAGE_VIEW_TYPE_CUBE_ARRAY, in any shader stageIf any  VkSampler3 object that is accessed from a shader by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS( uses unnormalized coordinates, it must) not be used with any of the SPIR-V OpImageSample* or OpImageSparseSample* instructions with  ImplicitLod, Dref or Proj# in their name, in any shader stageIf any  VkSampler3 object that is accessed from a shader by the  VkPipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS( uses unnormalized coordinates, it must) not be used with any of the SPIR-V OpImageSample* or OpImageSparseSample*U instructions that includes a LOD bias or any offset values, in any shader stageIf the  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-robustBufferAccessrobust buffer access: feature is not enabled, and any shader stage in the  VkPipeline object bound to VK_PIPELINE_BIND_POINT_GRAPHICS$ accesses a uniform buffer, it musta not access values outside of the range of that buffer specified in the bound descriptor setIf the  rhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-robustBufferAccessrobust buffer access: feature is not enabled, and any shader stage in the  VkPipeline object bound to VK_PIPELINE_BIND_POINT_GRAPHICS$ accesses a storage buffer, it musta not access values outside of the range of that buffer specified in the bound descriptor setAny  VkImageView being sampled with VK_FILTER_LINEAR" as a result of this command mustO be of a format which supports linear filtering, as specified by the 1VK_FORMAT_FEATURE_SAMPLED_IMAGE_FILTER_LINEAR_BIT flag in VkFormatProperties::linearTilingFeatures (for a linear image) or VkFormatProperties::optimalTilingFeatures0(for an optimally tiled image) returned by #vkGetPhysicalDeviceFormatPropertiesGImage subresources used as attachments in the current render pass mustM not be accessed in any way other than as an attachment by this command.Any w being sampled with VK_FILTER_CUBIC_IMG as a result of this command mustN be of a format which supports cubic filtering, as specified by the 4VK_FORMAT_FEATURE_SAMPLED_IMAGE_FILTER_CUBIC_BIT_IMG flag in VkFormatProperties::linearTilingFeatures (for a linear image) or VkFormatProperties::optimalTilingFeatures0(for an optimally tiled image) returned by #vkGetPhysicalDeviceFormatPropertiesAny w being sampled with VK_FILTER_CUBIC_IMG as a result of this command must not have a w of VK_IMAGE_VIEW_TYPE_3D, VK_IMAGE_VIEW_TYPE_CUBE , or VK_IMAGE_VIEW_TYPE_CUBE_ARRAYjIf the draw is recorded in a render pass instance with multiview enabled, the maximum instance index must be less than or equal to d::maxMultiviewInstanceIndex.5If the bound graphics pipeline was created with [::sampleLocationsEnable set to VK_TRUES and the current subpass has a depth/stencil attachment, then that attachment must! have been created with the 9VK_IMAGE_CREATE_SAMPLE_LOCATIONS_COMPATIBLE_DEPTH_BIT_EXT bit setValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must! support graphics operations This command must0 only be called inside of a render pass instanceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Inside  Graphics  Graphics See Also@vkCmdBindVertexBuffers - Bind vertex buffers to a command buffer Parameters commandBuffer? is the command buffer into which the command is recorded. firstBinding[ is the index of the first vertex input binding whose state is updated by the command. bindingCountS is the number of vertex input bindings whose state is updated by the command.pBuffers, is a pointer to an array of buffer handles.pOffsets, is a pointer to an array of buffer offsets. Description$The values taken from elements i of pBuffers and pOffsets9 replace the current state for the vertex input binding  firstBinding + i, for i in [0,  bindingCountL). The vertex input binding is updated to start at the offset indicated by pOffsets"[i] from the start of the buffer pBuffers[i]. All vertex input attributes that use each of these bindings will use these updated addresses in their address calculations for subsequent draw commands. Valid Usage firstBinding must be less than VkPhysicalDeviceLimits::maxVertexInputBindings The sum of  firstBinding and  bindingCount must be less than or equal to VkPhysicalDeviceLimits::maxVertexInputBindingsAll elements of pOffsets must< be less than the size of the corresponding element in pBuffersAll elements of pBuffers must! have been created with the !VK_BUFFER_USAGE_VERTEX_BUFFER_BIT flagEach element of pBuffers that is non-sparse must7 be bound completely and contiguously to a single VkDeviceMemory objectValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handlepBuffers must# be a valid pointer to an array of  bindingCount valid VkBuffer handlespOffsets must# be a valid pointer to an array of  bindingCount  VkDeviceSize values commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must! support graphics operations bindingCount must be greater than 0Both of  commandBuffer, and the elements of pBuffers must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Both  Graphics  See Also3, ,  VkDeviceSize?vkCmdBindIndexBuffer - Bind an index buffer to a command buffer Parameters commandBuffer? is the command buffer into which the command is recorded.buffer is the buffer being bound.offset( is the starting offset in bytes within buffer0 used in index buffer address calculations. indexType is a I value specifying whether indices are treated as 16 bits or 32 bits. Valid Usageoffset must be less than the size of buffer The sum of offset! and the address of the range of VkDeviceMemory object that is backing buffer, must- be a multiple of the type indicated by  indexTypebuffer must! have been created with the  VK_BUFFER_USAGE_INDEX_BUFFER_BIT flagIf buffer is non-sparse then it must7 be bound completely and contiguously to a single VkDeviceMemory objectValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handlebuffer must be a valid VkBuffer handle indexType must be a valid  value commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must! support graphics operationsBoth of buffer, and  commandBuffer must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Both  Graphics  See Also3, ,  VkDeviceSize, CvkCmdBindDescriptorSets - Binds descriptor sets to a command buffer Parameters commandBufferF is the command buffer that the descriptor sets will be bound to.pipelineBindPoint is a  indicating whether the descriptors will be used by graphics pipelines or compute pipelines. There is a separate set of bind points for each of graphics and compute, so binding one does not disturb the other.layout is a VkPipelineLayout* object used to program the bindings.firstSet@ is the set number of the first descriptor set to be bound.descriptorSetCount' is the number of elements in the pDescriptorSets array.pDescriptorSets is an array of handles to VkDescriptorSet9 objects describing the descriptor sets to write to.dynamicOffsetCount. is the number of dynamic offsets in the pDynamicOffsets array.pDynamicOffsets is a pointer to an array of uint32_t( values specifying dynamic offsets. DescriptionvkCmdBindDescriptorSets causes the sets numbered [firstSet.. firstSet+descriptorSetCount#-1] to use the bindings stored in pDescriptorSets[0..descriptorSetCountV-1] for subsequent rendering commands (either compute or graphics, according to the pipelineBindPointQ). Any bindings that were previously applied via these sets are no longer valid.Once bound, a descriptor set affects rendering of subsequent graphics or compute commands in the command buffer until a different set is bound to the same set number, or else until the set is disturbed as described in  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-compatibilityPipeline Layout Compatibility.A compatible descriptor set must be bound for all set numbers that any shaders in a pipeline access, at the time that a draw or dispatch command is recorded to execute using that pipeline. However, if none of the shaders in a pipeline statically use any bindings with a particular set number, then no descriptor set need be bound for that set number, even if the pipeline layout includes a non-trivial descriptor set layout for that set number.QIf any of the sets being bound include dynamic uniform or storage buffers, then pDynamicOffsetsz includes one element for each array element in each dynamic descriptor type binding in each set. Values are taken from pDynamicOffsets in an order such that all entries for set N come before set N+1; within a set, entries are ordered by the binding numbers in the descriptor set layouts; and within a binding array, elements are in order. dynamicOffsetCount mustH equal the total number of dynamic descriptors in the sets being bound.xThe effective offset used for dynamic uniform and storage buffer bindings is the sum of the relative offset taken from pDynamicOffsets, and the base address of the buffer plus base offset in the descriptor set. The length of the dynamic uniform and storage buffer bindings is the buffer range as specified in the descriptor set. Each of the pDescriptorSets must6 be compatible with the pipeline layout specified by layout+. The layout used to program the bindings mustj also be compatible with the pipeline used in subsequent graphics or compute commands, as defined in the  jhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#descriptorsets-compatibilityPipeline Layout Compatibility section./The descriptor set contents bound by a call to vkCmdBindDescriptorSets may$ be consumed at the following times:.For descriptor bindings created with the /VK_DESCRIPTOR_BINDING_UPDATE_AFTER_BIND_BIT_EXT bit set, the contents may be consumed when the command buffer is submitted to a queue, or during shader execution of the resulting draws and dispatches, or any time in between. Otherwise,during host execution of the command, or during shader execution of the resulting draws and dispatches, or any time in between./Thus, the contents of a descriptor set binding mustg not be altered (overwritten by an update command, or freed) between the first point in time that it mayI be consumed, and and when the command completes executing on the queue.The contents of pDynamicOffsets/ are consumed immediately during execution of vkCmdBindDescriptorSetsZ. Once all pending uses have completed, it is legal to update and reuse a descriptor set. Valid UsageEach element of pDescriptorSets must! have been allocated with a VkDescriptorSetLayoutC that matches (is the same as, or identically defined as) the VkDescriptorSetLayout at set n in layout , where n is the sum of firstSet and the index into pDescriptorSetsdynamicOffsetCount must= be equal to the total number of dynamic descriptors in pDescriptorSets The sum of firstSet and descriptorSetCount must be less than or equal to VkPipelineLayoutCreateInfo::setLayoutCount provided when layout was createdpipelineBindPoint must be supported by the  commandBuffer s parent  VkCommandPool s queue familyEach element of pDynamicOffsets must_ satisfy the required alignment for the corresponding descriptor binding s descriptor typeValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handlepipelineBindPoint must be a valid  valuelayout must be a valid VkPipelineLayout handlepDescriptorSets must( be a valid pointer to an array of descriptorSetCount valid VkDescriptorSet handlesIf dynamicOffsetCount is not 0, pDynamicOffsets must( be a valid pointer to an array of dynamicOffsetCount uint32_t values commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must- support graphics, or compute operationsdescriptorSetCount must be greater than 0Each of  commandBuffer, layout, and the elements of pDescriptorSets must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Both  Graphics Compute  See Also, !, , BvkCmdSetStencilReference - Set the stencil reference dynamic state Parameters commandBufferD is the command buffer into which the command will be recorded.faceMask is a bitmask of o specifying the set of stencil state for which to update the reference value, as described above for . reference8 is the new value to use as the stencil reference value. Valid UsageThe bound graphics pipeline must! have been created with the "VK_DYNAMIC_STATE_STENCIL_REFERENCE dynamic state enabledValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handlefaceMask must be a valid combination of  valuesfaceMask must not be 0 commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must! support graphics operationsHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Both  Graphics  See Also, KCvkCmdSetStencilWriteMask - Set the stencil write mask dynamic state Parameters commandBufferD is the command buffer into which the command will be recorded.faceMask is a bitmask of j specifying the set of stencil state for which to update the write mask, as described above for . writeMask3 is the new value to use as the stencil write mask. Valid UsageThe bound graphics pipeline must! have been created with the #VK_DYNAMIC_STATE_STENCIL_WRITE_MASK dynamic state enabledValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handlefaceMask must be a valid combination of  valuesfaceMask must not be 0 commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must! support graphics operationsHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Both  Graphics  See Also, KGvkCmdSetStencilCompareMask - Set the stencil compare mask dynamic state Parameters commandBufferD is the command buffer into which the command will be recorded.faceMask is a bitmask of O specifying the set of stencil state for which to update the compare mask. compareMask5 is the new value to use as the stencil compare mask. Valid UsageThe bound graphics pipeline must! have been created with the %VK_DYNAMIC_STATE_STENCIL_COMPARE_MASK dynamic state enabledValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handlefaceMask must be a valid combination of  valuesfaceMask must not be 0 commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must! support graphics operationsHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Both  Graphics  See Also, KLvkCmdSetDepthBounds - Set the depth bounds test values for a command buffer Parameters commandBufferD is the command buffer into which the command will be recorded.minDepthBoundsT is the lower bound of the range of depth values used in the depth bounds test.maxDepthBounds! is the upper bound of the range. Valid UsageThe bound graphics pipeline must! have been created with the VK_DYNAMIC_STATE_DEPTH_BOUNDS dynamic state enabled Unless the 4{html_spec_relative}#VK_EXT_depth_range_unrestricted extension is enabled minDepthBounds must be between 0.0 and 1.0 , inclusive Unless the 4{html_spec_relative}#VK_EXT_depth_range_unrestricted extension is enabled maxDepthBounds must be between 0.0 and 1.0 , inclusiveValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must! support graphics operationsHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Both  Graphics  See Also:vkCmdSetBlendConstants - Set the values of blend constants Parameters commandBufferD is the command buffer into which the command will be recorded.blendConstants is an array of four values specifying the R, G, B, and A components of the blend constant color used in blending, depending on the  fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#framebuffer-blendfactorsblend factor. Valid UsageThe bound graphics pipeline must! have been created with the  VK_DYNAMIC_STATE_BLEND_CONSTANTS dynamic state enabledValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must! support graphics operationsHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Both  Graphics  See Also4vkCmdSetDepthBias - Set the depth bias dynamic state Parameters commandBufferD is the command buffer into which the command will be recorded.depthBiasConstantFactorU is a scalar factor controlling the constant depth value added to each fragment.depthBiasClamp; is the maximum (or minimum) depth bias of a fragment.depthBiasSlopeFactorR is a scalar factor applied to a fragment s slope in depth bias calculations. DescriptionIf depthBiasEnable is VK_FALSEJ, no depth bias is applied and the fragment s depth values are unchanged.depthBiasSlopeFactor5 scales the maximum depth slope of the polygon, and depthBiasConstantFactor scales an implementation-dependent constant that relates to the usable resolution of the depth buffer. The resulting values are summed to produce the depth bias value which is then clamped to a minimum or maximum value specified by depthBiasClamp. depthBiasSlopeFactor, depthBiasConstantFactor, and depthBiasClamp can% each be positive, negative, or zero.*The maximum depth slope m of a triangle ism = \sqrt{ \left({{\partial z_f} \over {\partial x_f}}\right)^2 + \left({{\partial z_f} \over {\partial y_f}}\right)^2}1where (xf, yf, zf) is a point on the triangle. m may be approximated asm = \max\left( \left| { {\partial z_f} \over {\partial x_f} } \right|, \left| { {\partial z_f} \over {\partial y_f} } \right| \right).The minimum resolvable difference r is an implementation-dependent parameter that depends on the depth buffer representation. It is the smallest difference in framebuffer coordinate z values that is guaranteed to remain distinct throughout polygon rasterization and in the depth buffer. All pairs of fragments generated by the rasterization of two polygons with otherwise identical vertices, but z>f values that differ by $r$, will have distinct depth values.For fixed-point depth buffer representations, r is constant throughout the range of the entire depth buffer. For floating-point depth buffers, there is no single minimum resolvable difference. In this case, the minimum resolvable difference for a given polygon is dependent on the maximum exponent, e, in the range of z values spanned by the primitive. If n is the number of bits in the floating-point mantissa, the minimum resolvable difference, r, for the given primitive is defined asr = 2e-n'If a triangle is rasterized using the !VK_POLYGON_MODE_FILL_RECTANGLE_NV8 polygon mode, then this minimum resolvable difference mayY not be resolvable for samples outside of the triangle, where the depth is extrapolated..If no depth buffer is present, r is undefined.!The bias value o for a polygon iso = \begin{cases} m \times depthBiasSlopeFactor + r \times depthBiasConstantFactor & depthBiasClamp = 0\ or\ NaN \\ \min(m \times depthBiasSlopeFactor + r \times depthBiasConstantFactor, depthBiasClamp) & depthBiasClamp > 0 \\ \max(m \times depthBiasSlopeFactor + r \times depthBiasConstantFactor, depthBiasClamp) & depthBiasClamp < 0 \\ \end{cases}m is computed as described above. If the depth buffer uses a fixed-point representation, m is a function of depth values in the range [0,1], and o is applied to depth values in the same range.For fixed-point depth buffers, fragment depth values are always limited to the range [0,1] by clamping after depth bias addition is performed. Unless the 4{html_spec_relative}#VK_EXT_depth_range_unrestricted{ extension is enabled, fragment depth values are clamped even when the depth buffer uses a floating-point representation. Valid UsageThe bound graphics pipeline must! have been created with the VK_DYNAMIC_STATE_DEPTH_BIAS dynamic state enabledIf the  nhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-depthBiasClampdepth bias clamping feature is not enabled, depthBiasClamp must be 0.0Valid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must! support graphics operationsHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Both  Graphics  See Also4vkCmdSetLineWidth - Set the dynamic line width state Parameters commandBufferD is the command buffer into which the command will be recorded. lineWidth* is the width of rasterized line segments. Valid UsageThe bound graphics pipeline must! have been created with the VK_DYNAMIC_STATE_LINE_WIDTH dynamic state enabledIf the  ihttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-wideLineswide lines feature is not enabled,  lineWidth must be 1.0Valid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must! support graphics operationsHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Both  Graphics  See AlsoHvkCmdSetScissor - Set the dynamic scissor rectangles on a command buffer Parameters commandBufferD is the command buffer into which the command will be recorded. firstScissorN is the index of the first scissor whose state is updated by the command. scissorCountL is the number of scissors whose rectangles are updated by the command. pScissors" is a pointer to an array of - structures defining scissor rectangles. Description/The scissor rectangles taken from element i of  pScissors2 replace the current state for the scissor index  firstScissor + i, for i in [0,  scissorCount).*Each scissor rectangle is described by a  structure, with the offset.x and offset.yM values determining the upper left corner of the scissor rectangle, and the  extent.width and  extent.height( values determining the size in pixels. Valid UsageThe bound graphics pipeline must! have been created with the VK_DYNAMIC_STATE_SCISSOR dynamic state enabled firstScissor must be less than VkPhysicalDeviceLimits:: maxViewports The sum of  firstScissor and  scissorCount must be between 1 and VkPhysicalDeviceLimits:: maxViewports , inclusiveIf the  mhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-multiViewportmultiple viewports feature is not enabled,  firstScissor must be 0If the  mhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-multiViewportmultiple viewports feature is not enabled,  scissorCount must be 1The x and y members of offset must" be greater than or equal to 0Evaluation of (offset.x +  extent.width) must2 not cause a signed integer addition overflowEvaluation of (offset.y +  extent.height) must2 not cause a signed integer addition overflowValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle pScissors must# be a valid pointer to an array of  scissorCount VkRect2D structures commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must! support graphics operations scissorCount must be greater than 0Host SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Both  Graphics  See Also, 7vkCmdSetViewport - Set the viewport on a command buffer Parameters commandBufferD is the command buffer into which the command will be recorded. firstViewportU is the index of the first viewport whose parameters are updated by the command. viewportCountM is the number of viewports whose parameters are updated by the command. pViewports" is a pointer to an array of 0 structures specifying viewport parameters. Description0The viewport parameters taken from element i of  pViewports3 replace the current state for the viewport index  firstViewport + i, for i in [0,  viewportCount). Valid UsageThe bound graphics pipeline must! have been created with the VK_DYNAMIC_STATE_VIEWPORT dynamic state enabled firstViewport must be less than VkPhysicalDeviceLimits:: maxViewports The sum of  firstViewport and  viewportCount must be between 1 and VkPhysicalDeviceLimits:: maxViewports , inclusiveIf the  mhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-multiViewportmultiple viewports feature is not enabled,  firstViewport must be 0If the  mhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-multiViewportmultiple viewports feature is not enabled,  viewportCount must be 1Valid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handle pViewports must( be a valid pointer to an array of  viewportCount  VkViewport structures commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must! support graphics operations viewportCount must be greater than 0Host SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Both  Graphics  See Also, >vkCmdBindPipeline - Bind a pipeline object to a command buffer Parameters commandBuffer? is the command buffer that the pipeline will be bound to.pipelineBindPoint is a z value specifying whether to bind to the compute or graphics bind point. Binding one does not disturb the other.pipeline is the pipeline to be bound. DescriptionOnce bound, a pipeline binding affects subsequent graphics or compute commands in the command buffer until a different pipeline is bound to the bind point. The pipeline bound to VK_PIPELINE_BIND_POINT_COMPUTE controls the behavior of  and . The pipeline bound to VK_PIPELINE_BIND_POINT_GRAPHICS controls the behavior of all  Uhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#drawingdrawing commands8. No other commands are affected by the pipeline state. Valid UsageIf pipelineBindPoint is VK_PIPELINE_BIND_POINT_COMPUTE , the  VkCommandPool that  commandBuffer was allocated from must support compute operationsIf pipelineBindPoint is VK_PIPELINE_BIND_POINT_GRAPHICS , the  VkCommandPool that  commandBuffer was allocated from must! support graphics operationsIf pipelineBindPoint is VK_PIPELINE_BIND_POINT_COMPUTE, pipeline must be a compute pipelineIf pipelineBindPoint is VK_PIPELINE_BIND_POINT_GRAPHICS, pipeline must be a graphics pipelineIf the  whttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#features-features-variableMultisampleRatevariable multisample rate feature is not supported, pipeline is a graphics pipeline, the current subpass has no attachments, and this is not the first call to this function with a graphics pipeline after transitioning to the current subpass, then the sample count specified by this pipeline must( match that set in the previous pipelineIf [j::variableSampleLocations is VK_FALSE, and pipeline, is a graphics pipeline created with a [ structure having its sampleLocationsEnable member set to VK_TRUE but without %VK_DYNAMIC_STATE_SAMPLE_LOCATIONS_EXT4 enabled then the current render pass instance must& have been begun by specifying a [ structure whose pPostSubpassSampleLocations( member contains an element with a  subpassIndex1 matching the current subpass index and the sampleLocationsInfo member of that element must match the sampleLocationsInfo specified in [# when the pipeline was createdValid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handlepipelineBindPoint must be a valid  valuepipeline must be a valid  VkPipeline handle commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must- support graphics, or compute operationsBoth of  commandBuffer, and pipeline must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Both  Graphics Compute  See Also, , VK_STENCIL_FRONT_AND_BACK is the combination of VK_STENCIL_FACE_FRONT_BIT and VK_STENCIL_FACE_BACK_BIT=, and specifies that both sets of stencil state are updated.VK_STENCIL_FACE_BACK_BIT? specifies that only the back set of stencil state is updated.VK_STENCIL_FACE_FRONT_BIT@ specifies that only the front set of stencil state is updated.-VK_SUBPASS_CONTENTS_SECONDARY_COMMAND_BUFFERS specifies that the contents are recorded in secondary command buffers that will be called from the primary command buffer, and 8 is the only valid command on the command buffer until  or .VK_SUBPASS_CONTENTS_INLINE specifies that the contents of the subpass will be recorded inline in the primary command buffer, and secondary command buffers must$ not be executed within the subpass.VK_INDEX_TYPE_UINT32< specifies that indices are 32-bit unsigned integer values.VK_INDEX_TYPE_UINT16< specifies that indices are 16-bit unsigned integer values. F_Note_: peek is undefined as we wouldn't know which constructor to useF_Note_: peek is undefined as we wouldn't know which constructor to useKLMNOPQRSTUVWXY[^Z\]_`abcdefghijklmnopqrstuvwx}z|y{~~wx}z|y{nopqrstuvjklmefghi_`abcdXY[^Z\]STUVWOPQRLMNKNone "-KSTbejkjjh@EVkObjectEntryUsageFlagsNVX - Bitmask of VkObjectEntryUsageFlagBitsNVX DescriptionVkObjectEntryUsageFlagsNVX7 is a bitmask type for setting a mask of zero or more .See Also, b, S, ^, H, Y, B, NA\VkIndirectCommandsLayoutUsageFlagsNVX - Bitmask of VkIndirectCommandsLayoutUsageFlagBitsNVX Description%VkIndirectCommandsLayoutUsageFlagsNVX7 is a bitmask type for setting a mask of zero or more .See Also, BVVkObjectTablePushConstantEntryNVX - Parameters of an object table push constant entry Valid Usagetype must be &VK_OBJECT_ENTRY_TYPE_PUSH_CONSTANT_NVXValid Usage (Implicit)type must be a valid  valueflags must be a valid combination of  valuesflags must not be 0pipelineLayout must be a valid VkPipelineLayout handle stageFlags must be a valid combination of H  values stageFlags must not be 0See Also, @, ,  hFpipelineLayout specifies the VkPipelineLayout& that the pushconstants are used withG stageFlags specifies the VkShaderStageFlags& that the pushconstants are used withHTVkObjectTableIndexBufferEntryNVX - Parameters of an object table index buffer entry Valid Usagetype must be %VK_OBJECT_ENTRY_TYPE_INDEX_BUFFER_NVXValid Usage (Implicit)type must be a valid  valueflags must be a valid combination of  valuesflags must not be 0buffer must be a valid VkBuffer handle indexType must be a valid  valueSee Also3, , , @Lbuffer specifies the VkBuffer" that can be bound as index bufferM indexType specifies the  VkIndexType used with this index bufferNVVkObjectTableVertexBufferEntryNVX - Parameters of an object table vertex buffer entry Valid Usagetype must be &VK_OBJECT_ENTRY_TYPE_VERTEX_BUFFER_NVXValid Usage (Implicit)type must be a valid  valueflags must be a valid combination of  valuesflags must not be 0buffer must be a valid VkBuffer handleSee Also3, , @Rbuffer specifies the VkBuffer" that can be bound as vertex buferSXVkObjectTableDescriptorSetEntryNVX - Parameters of an object table descriptor set entry Valid Usagetype must be 'VK_OBJECT_ENTRY_TYPE_DESCRIPTOR_SET_NVXValid Usage (Implicit)type must be a valid  valueflags must be a valid combination of  valuesflags must not be 0pipelineLayout must be a valid VkPipelineLayout handle descriptorSet must be a valid VkDescriptorSet handleBoth of  descriptorSet, and pipelineLayout must? have been created, allocated, or retrieved from the same VkDeviceSee Also!, , @, WpipelineLayout specifies the VkPipelineLayout that the  descriptorSet is used with.X descriptorSet specifies the VkDescriptorSet$ that can be bound with this entry.YMVkObjectTablePipelineEntryNVX - Parameters of an object table pipeline entry Valid Usagetype must be !VK_OBJECT_ENTRY_TYPE_PIPELINE_NVXValid Usage (Implicit)type must be a valid  valueflags must be a valid combination of  valuesflags must not be 0pipeline must be a valid  VkPipeline handleSee Also, @, ]pipeline specifies the  VkPipeline& that this resource entry references.^LVkObjectTableEntryNVX - Common parameters of an object table resource entry Valid Usage If the $VkDeviceGeneratedCommandsFeaturesNVX::computeBindingPointSupport feature is not enabled, flags must not contain %VK_OBJECT_ENTRY_USAGE_COMPUTE_BIT_NVXValid Usage (Implicit)type must be a valid  valueflags must be a valid combination of  valuesflags must not be 0See Also, @, `type defines the entry typeaflags defines which VkPipelineBindPointU the resource can be used with. Some entry types allow only a single flag to be set.baVkObjectTableCreateInfoNVX - Structure specifying the parameters of a newly created object table Valid Usage If the $VkDeviceGeneratedCommandsFeaturesNVX::computeBindingPointSupport feature is not enabled, pObjectEntryUsageFlags must not contain %VK_OBJECT_ENTRY_USAGE_COMPUTE_BIT_NVXAny value within pObjectEntryCounts must not exceed "VkDeviceGeneratedCommandsLimitsNVX::maxObjectEntryCountsmaxUniformBuffersPerDescriptor must3 be within the limits supported by the device.maxStorageBuffersPerDescriptor must3 be within the limits supported by the device.maxStorageImagesPerDescriptor must3 be within the limits supported by the device.maxSampledImagesPerDescriptor must3 be within the limits supported by the device.Valid Usage (Implicit)sType must be .VK_STRUCTURE_TYPE_OBJECT_TABLE_CREATE_INFO_NVXpNext must be NULLpObjectEntryTypes must( be a valid pointer to an array of  objectCount valid  valuespObjectEntryCounts must( be a valid pointer to an array of  objectCount uint32_t valuespObjectEntryUsageFlags must( be a valid pointer to an array of  objectCount valid combinations of  valuesEach element of pObjectEntryUsageFlags must not be 0 objectCount must be greater than 0See Also, @, , dsType is the type of this structure.epNext is NULL1 or a pointer to an extension-specific structure.f objectCountG is the number of entry configurations that the object table supports.gpObjectEntryTypes is an array of ; values providing the entry type of a given configuration.hpObjectEntryCountsK is an array of counts of how many objects can be registered in the table.ipObjectEntryUsageFlags is an array of bitmasks of , specifying the binding usage of the entry.jmaxUniformBuffersPerDescriptor is the maximum number of !VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER or )VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER_DYNAMIC used by any single registered VkDescriptorSet in this table.kmaxStorageBuffersPerDescriptor is the maximum number of !VK_DESCRIPTOR_TYPE_STORAGE_BUFFER or )VK_DESCRIPTOR_TYPE_STORAGE_BUFFER_DYNAMIC used by any single registered VkDescriptorSet in this table.lmaxStorageImagesPerDescriptor is the maximum number of  VK_DESCRIPTOR_TYPE_STORAGE_IMAGE or 'VK_DESCRIPTOR_TYPE_STORAGE_TEXEL_BUFFER used by any single registered VkDescriptorSet in this table.mmaxSampledImagesPerDescriptor is the maximum number of VK_DESCRIPTOR_TYPE_SAMPLER, )VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLER, 'VK_DESCRIPTOR_TYPE_UNIFORM_TEXEL_BUFFER or #VK_DESCRIPTOR_TYPE_INPUT_ATTACHMENT used by any single registered VkDescriptorSet in this table.nmaxPipelineLayouts! is the maximum number of unique VkPipelineLayout used by any registered VkDescriptorSet or  VkPipeline in this table.orVkCmdReserveSpaceForCommandsInfoNVX - Structure specifying parameters for the reservation of command buffer spaceValid Usage (Implicit)sType must be 9VK_STRUCTURE_TYPE_CMD_RESERVE_SPACE_FOR_COMMANDS_INFO_NVXpNext must be NULL objectTable must be a valid VkObjectTableNVX handleindirectCommandsLayout must be a valid VkIndirectCommandsLayoutNVX handleBoth of indirectCommandsLayout, and  objectTable must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to  objectTable must be externally synchronizedSee Also, , , qsType is the type of this structure.rpNext is NULL1 or a pointer to an extension-specific structure.s objectTable is the VkObjectTableNVXN to be used for the generation process. Only registered objects at the time < is called, will be taken into account for the reservation.tindirectCommandsLayout is the VkIndirectCommandsLayoutNVX that must! also be used at generation time.umaxSequencesCountU is the maximum number of sequences for which command buffer space will be reserved.v]VkCmdProcessCommandsInfoNVX - Structure specifying parameters for the generation of commands Valid Usage The provided  objectTable must? include all objects referenced by the generation process. indirectCommandsTokenCount must match the indirectCommandsLayout s  tokenCount.The  tokenType" member of each entry in the pIndirectCommandsTokens array must0 match the values used at creation time of indirectCommandsLayoutIf targetCommandBuffer is provided, it must" have reserved command space.If targetCommandBuffer is provided, the  objectTable must. match the reservation s objectTable and mustE have had all referenced objects registered at reservation time.If targetCommandBuffer is provided, the indirectCommandsLayout must0 match the reservation s indirectCommandsLayout.If targetCommandBuffer is provided, the maxSequencesCount must5 not exceed the reservation s maxSequencesCount.If sequencesCountBuffer is used, its usage flag must have #VK_BUFFER_USAGE_INDIRECT_BUFFER_BIT bit set.If sequencesCountBuffer is used, sequencesCountOffset must be aligned to "VkDeviceGeneratedCommandsLimitsNVX::%minSequenceCountBufferOffsetAlignment.If sequencesIndexBuffer is used, its usage flag must have #VK_BUFFER_USAGE_INDIRECT_BUFFER_BIT bit set.If sequencesIndexBuffer is used, sequencesIndexOffset must be aligned to "VkDeviceGeneratedCommandsLimitsNVX::%minSequenceIndexBufferOffsetAlignment.Valid Usage (Implicit)sType must be /VK_STRUCTURE_TYPE_CMD_PROCESS_COMMANDS_INFO_NVX pNext must be NULL objectTable must be a valid VkObjectTableNVX handleindirectCommandsLayout must be a valid VkIndirectCommandsLayoutNVX handlepIndirectCommandsTokens must( be a valid pointer to an array of indirectCommandsTokenCount valid VkIndirectCommandsTokenNVX structuresIf targetCommandBuffer is not NULL, targetCommandBuffer must be a valid VkCommandBuffer handleIf sequencesCountBuffer is not , sequencesCountBuffer must be a valid VkBuffer handleIf sequencesIndexBuffer is not , sequencesIndexBuffer must be a valid VkBuffer handleindirectCommandsTokenCount must be greater than 0Each of indirectCommandsLayout,  objectTable, sequencesCountBuffer, sequencesIndexBuffer , and targetCommandBuffer that are valid handles must? have been created, allocated, or retrieved from the same VkDeviceHost SynchronizationHost access to  objectTable must be externally synchronizedHost access to targetCommandBuffer must be externally synchronizedSee Also3, ,  VkDeviceSize, , , , , xsType is the type of this structure.ypNext is NULL1 or a pointer to an extension-specific structure.z objectTable is the VkObjectTableNVXN to be used for the generation process. Only registered objects at the time < is called, will be taken into account for the reservation.{indirectCommandsLayout is the VkIndirectCommandsLayoutNVX1 that provides the command sequence to generate.|indirectCommandsTokenCount) defines the number of input tokens used.}pIndirectCommandsTokens provides an array of 7 that reference the input data for each token command.~maxSequencesCountY is the maximum number of sequences for which command buffer space will be reserved. If sequencesCountBuffer is 9, this is also the actual number of sequences generated.targetCommandBuffer can be the secondary VkCommandBuffer/ in which the commands should be recorded. If targetCommandBuffer is NULLN an implicit reservation as well as execution takes place on the processing VkCommandBuffer.sequencesCountBuffer can be VkBuffer? from which the actual amount of sequences is sourced from as uint32_t value.sequencesCountOffset is the byte offset into sequencesCountBuffer" where the count value is stored.sequencesIndexBuffer must be set if indirectCommandsLayout s 7VK_INDIRECT_COMMANDS_LAYOUT_USAGE_INDEXED_SEQUENCES_BIT3 is set and provides the used sequence indices as uint32_t array. Otherwise it must be .sequencesIndexOffset is the byte offset into sequencesIndexBuffer where the index values start.VkIndirectCommandsLayoutCreateInfoNVX - Structure specifying the parameters of a newly created indirect commands layout object Description5The following code illustrates some of the key flags: void cmdProcessAllSequences(cmd, objectTable, indirectCommandsLayout, pIndirectCommandsTokens, sequencesCount, indexbuffer, indexbufferoffset) { for (s = 0; s < sequencesCount; s++) { sequence = s; if (indirectCommandsLayout.flags & VK_INDIRECT_COMMANDS_LAYOUT_USAGE_UNORDERED_SEQUENCES_BIT_NVX) { sequence = incoherent_implementation_dependent_permutation[ sequence ]; } if (indirectCommandsLayout.flags & VK_INDIRECT_COMMANDS_LAYOUT_USAGE_INDEXED_SEQUENCES_BIT_NVX) { sequence = indexbuffer.load_uint32( sequence * sizeof(uint32_t) + indexbufferoffset); } cmdProcessSequence( cmd, objectTable, indirectCommandsLayout, pIndirectCommandsTokens, sequence ); } } Valid Usage tokenCount must be greater than 0 and below "VkDeviceGeneratedCommandsLimitsNVX::#maxIndirectCommandsLayoutTokenCount If the $VkDeviceGeneratedCommandsFeaturesNVX::computeBindingPointSupport# feature is not enabled, then pipelineBindPoint must not be VK_PIPELINE_BIND_POINT_COMPUTEIf pTokens contains an entry of ,VK_INDIRECT_COMMANDS_TOKEN_TYPE_PIPELINE_NVX it must2 be the first element of the array and there must2 be only a single element of such token type.All state binding tokens in pTokens must) occur prior work provoking tokens ((VK_INDIRECT_COMMANDS_TOKEN_TYPE_DRAW_NVX, 0VK_INDIRECT_COMMANDS_TOKEN_TYPE_DRAW_INDEXED_NVX, ,VK_INDIRECT_COMMANDS_TOKEN_TYPE_DISPATCH_NVX).The content of pTokens mustJ include one single work provoking token that is compatible with the pipelineBindPoint.Valid Usage (Implicit)sType must be :VK_STRUCTURE_TYPE_INDIRECT_COMMANDS_LAYOUT_CREATE_INFO_NVXpNext must be NULLpipelineBindPoint must be a valid  valueflags must be a valid combination of  valuesflags must not be 0pTokens must# be a valid pointer to an array of  tokenCount valid  VkIndirectCommandsLayoutTokenNVX structures tokenCount must be greater than 0See Also, A, , , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.pipelineBindPoint is the VkPipelineBindPoint that this layout targets.flags is a bitmask of ( specifying usage hints of this layout. tokenCount1 is the length of the individual command sequnce.pTokens; is an array describing each command token in detail. See  and  below for details.eVkIndirectCommandsLayoutTokenNVX - Struct specifying the details of an indirect command layout token Valid Usage bindingUnit mustG stay within device supported limits for the appropriate commands. dynamicCount mustG stay within device supported limits for the appropriate commands.divisor must be greater than 0 and a power of two.Valid Usage (Implicit) tokenType must be a valid  valueSee Also,  bindingUnitc has a different meaning depending on the type, please refer pseudo code further down for details. dynamicCountc has a different meaning depending on the type, please refer pseudo code further down for details.divisor? defines the rate at which the input data buffers are accessed.iVkIndirectCommandsTokenNVX - Structure specifying parameters for the reservation of command buffer space Valid UsageThe buffer s usage flag must have the #VK_BUFFER_USAGE_INDIRECT_BUFFER_BIT bit set.The offset must be aligned to "VkDeviceGeneratedCommandsLimitsNVX::%minCommandsTokenBufferOffsetAlignment.Valid Usage (Implicit) tokenType must be a valid  valuebuffer must be a valid VkBuffer handleSee Also3, v,  VkDeviceSize,  tokenType" specifies the token command type.buffer specifies the VkBufferb storing the functional arguments for each squence. These argumetns can be written by the device.offset specified an offset into buffer where the arguments start.QVkDeviceGeneratedCommandsLimitsNVX - Structure specifying physical device limitsValid Usage (Implicit)sType must be 6VK_STRUCTURE_TYPE_DEVICE_GENERATED_COMMANDS_LIMITS_NVXpNext must be NULLSee Also, sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.#maxIndirectCommandsLayoutTokenCount" the maximum number of tokens in VkIndirectCommandsLayoutNVX.maxObjectEntryCounts5 the maximum number of entries per resource type in VkObjectTableNVX.%minSequenceCountBufferOffsetAlignment@ the minimum alignment for memory addresses optionally used in vkCmdProcessCommandsNVX.%minSequenceIndexBufferOffsetAlignment@ the minimum alignment for memory addresses optionally used in vkCmdProcessCommandsNVX.%minCommandsTokenBufferOffsetAlignment@ the minimum alignment for memory addresses optionally used in vkCmdProcessCommandsNVX.TVkDeviceGeneratedCommandsFeaturesNVX - Structure specifying physical device supportValid Usage (Implicit)sType must be 8VK_STRUCTURE_TYPE_DEVICE_GENERATED_COMMANDS_FEATURES_NVXpNext must be NULLSee AlsoVkBool32, , sType is the type of this structure.pNext is NULL1 or a pointer to an extension-specific structure.computeBindingPointSupport specifies whether the VkObjectTableNVX supports entries with &VK_OBJECT_ENTRY_USAGE_GRAPHICS_BIT_NVX bit set and VkIndirectCommandsLayoutNVX supports VK_PIPELINE_BIND_POINT_COMPUTE.RVkIndirectCommandsLayoutNVX - Opaque handle to an indirect commands layout objectSee Alsov, o, , =Dummy data to tag the  with3VkObjectTableNVX - Opaque handle to an object tableSee Alsov, o, , , , >Dummy data to tag the  withTVkObjectEntryUsageFlagBitsNVX - Bitmask specifying allowed usage of an object entrySee Also@jVkIndirectCommandsLayoutUsageFlagBitsNVX - Bitmask specifying allowed usage of a indirect commands layoutSee AlsoA>VkObjectEntryTypeNVX - Enum specifying object table entry typeSee Alsob, S, ^, H, Y, B, N, 0VkIndirectCommandsTokenTypeNVX - Enum specifying Description'6 Token type  Equivalent command  ,VK_INDIRECT_COMMANDS_TOKEN_TYPE_PIPELINE_NVX  vkCmdBindPipeline  2VK_INDIRECT_COMMANDS_TOKEN_TYPE_DESCRIPTOR_SET_NVX  vkCmdBindDescriptorSets  0VK_INDIRECT_COMMANDS_TOKEN_TYPE_INDEX_BUFFER_NVX  vkCmdBindIndexBuffer  1VK_INDIRECT_COMMANDS_TOKEN_TYPE_VERTEX_BUFFER_NVX  vkCmdBindVertexBuffers  1VK_INDIRECT_COMMANDS_TOKEN_TYPE_PUSH_CONSTANT_NVX  vkCmdPushConstants  0VK_INDIRECT_COMMANDS_TOKEN_TYPE_DRAW_INDEXED_NVX  vkCmdDrawIndexedIndirect  (VK_INDIRECT_COMMANDS_TOKEN_TYPE_DRAW_NVX  vkCmdDrawIndirect  ,VK_INDIRECT_COMMANDS_TOKEN_TYPE_DISPATCH_NVX  vkCmdDispatchIndirect !Supported indirect command tokensSee Also, ~vkGetPhysicalDeviceGeneratedCommandsPropertiesNVX - Returns device-generated commands related properties of a physical device ParametersphysicalDeviceL is the handle to the physical device whose properties will be queried. pFeatures# points to an instance of the ? structure, that will be filled with returned information.pLimits# points to an instance of the ? structure, that will be filled with returned information.Valid Usage (Implicit)physicalDevice must be a valid VkPhysicalDevice handle pFeatures must be a valid pointer to a $VkDeviceGeneratedCommandsFeaturesNVX structurepLimits must be a valid pointer to a "VkDeviceGeneratedCommandsLimitsNVX structureSee Also, , HvkUnregisterObjectsNVX - Unregister resource bindings in an object table Parametersdevice5 is the logical device that creates the object table. objectTable= is the table from which the resources are unregistered. objectCountE is the number of resources being removed from the object table.pObjectEntryType provides an array of VkObjectEntryTypeNVX& for the resources being removed.pObjectIndices4 provides the array of object indices to be removed. Valid UsageAt any pObjectIndices there must' be a registered resource already.The pObjectEntryTypes of the resource at pObjectIndices must match.;All operations on the device using the registered resource must have been completed.Valid Usage (Implicit)device must be a valid VkDevice handle objectTable must be a valid VkObjectTableNVX handlepObjectEntryTypes must( be a valid pointer to an array of  objectCount valid  valuespObjectIndices must( be a valid pointer to an array of  objectCount uint32_t values objectCount must be greater than 0 objectTable must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to  objectTable must be externally synchronized Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, , DvkRegisterObjectsNVX - Register resource bindings in an object table Parametersdevice5 is the logical device that creates the object table. objectTable5 is the table for which the resources are registered. objectCount( is the number of resources to register.ppObjectTableEntriest provides an array for detailed binding informations, each array element is a pointer to a struct of type VkObjectTablePipelineEntryNVX, "VkObjectTableDescriptorSetEntryNVX, !VkObjectTableVertexBufferEntryNVX,  VkObjectTableIndexBufferEntryNVX or !VkObjectTablePushConstantEntryNVX (see below for details).pObjectIndices; are the indices at which each resource is registered. Valid UsageThe contents of pObjectTableEntry must7 yield plausible bindings supported by the device.At any pObjectIndices there must+ not be a registered resource already.Any value inside pObjectIndices must be below the appropriate VkObjectTableCreateInfoNVX::pObjectEntryCounts limits provided at  objectTable creation time.Valid Usage (Implicit)device must be a valid VkDevice handle objectTable must be a valid VkObjectTableNVX handleppObjectTableEntries must( be a valid pointer to an array of  objectCount valid VkObjectTableEntryNVX structurespObjectIndices must( be a valid pointer to an array of  objectCount uint32_t values objectCount must be greater than 0 objectTable must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to  objectTable must be externally synchronized Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, ^, 0vkDestroyObjectTableNVX - Destroy a object table Parametersdevice/ is the logical device that destroys the table. objectTable is the table to destroy. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. Valid Usage%All submitted commands that refer to  objectTable must have completed execution.If VkAllocationCallbacks were provided when  objectTable1 was created, a compatible set of callbacks must be provided here.If no VkAllocationCallbacks were provided when  objectTable was created,  pAllocator must be NULL.Valid Usage (Implicit)device must be a valid VkDevice handle objectTable must be a valid VkObjectTableNVX handleIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structure objectTable must6 have been created, allocated, or retrieved from deviceHost SynchronizationHost access to  objectTable must be externally synchronizedSee Also, , /vkCreateObjectTableNVX - Create an object table Parametersdevice5 is the logical device that creates the object table. pCreateInfo) is a pointer to an instance of the VkObjectTableCreateInfoNVXF structure containing parameters affecting creation of the table. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. pObjectTable points to a VkObjectTableNVX= handle in which the resulting object table is returned.Valid Usage (Implicit)device must be a valid VkDevice handle pCreateInfo must$ be a valid pointer to a valid VkObjectTableCreateInfoNVX structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structure pObjectTable must be a valid pointer to a VkObjectTableNVX handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, , b, ;vkDestroyIndirectCommandsLayoutNVX - Destroy a object table Parametersdevice0 is the logical device that destroys the layout.indirectCommandsLayout is the table to destroy. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter. Valid Usage%All submitted commands that refer to indirectCommandsLayout must have completed executionIf VkAllocationCallbacks were provided when  objectTable1 was created, a compatible set of callbacks must be provided hereIf no VkAllocationCallbacks were provided when  objectTable was created,  pAllocator must be NULLValid Usage (Implicit)device must be a valid VkDevice handleindirectCommandsLayout must be a valid VkIndirectCommandsLayoutNVX handleIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structureindirectCommandsLayout must6 have been created, allocated, or retrieved from deviceSee Also, , MvkCreateIndirectCommandsLayoutNVX - Create an indirect command layout object ParametersdeviceE is the logical device that creates the indirect command layout. pCreateInfo) is a pointer to an instance of the %VkIndirectCommandsLayoutCreateInfoNVXX structure containing parameters affecting creation of the indirect command layout. pAllocator: controls host memory allocation as described in the  _https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#memory-allocationMemory Allocation chapter.pIndirectCommandsLayout points to a VkIndirectCommandsLayoutNVXH handle in which the resulting indirect command layout is returned.Valid Usage (Implicit)device must be a valid VkDevice handle pCreateInfo must$ be a valid pointer to a valid %VkIndirectCommandsLayoutCreateInfoNVX structureIf  pAllocator is not NULL,  pAllocator must$ be a valid pointer to a valid VkAllocationCallbacks structurepIndirectCommandsLayout must be a valid pointer to a VkIndirectCommandsLayoutNVX handle Return Codes ghttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-successcodes[Success ] -  VK_SUCCESS ehttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#fundamentals-errorcodes[Failure ] - VK_ERROR_OUT_OF_HOST_MEMORY VK_ERROR_OUT_OF_DEVICE_MEMORYSee Also, , , PvkCmdReserveSpaceForCommandsNVX - Perform a reservation of command buffer space Parameters commandBufferc is the secondary command buffer in which the space for device-generated commands is reserved.pProcessCommandsInfo) is a pointer to an instance of the X structure containing parameters affecting the reservation of command buffer space. Valid Usage The provided  commandBuffer mustR not have had a prior space reservation since its creation or the last reset.The state of the  commandBuffer mustP be legal to execute all commands within the sequence provided by the indirectCommandsLayout member of pProcessCommandsInfo.Valid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handlepReserveSpaceInfo must$ be a valid pointer to a valid #VkCmdReserveSpaceForCommandsInfoNVX structure commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must- support graphics, or compute operations This command must0 only be called inside of a render pass instance commandBuffer must be a secondary VkCommandBufferHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Secondary  Inside  Graphics Compute  See Alsoo, LvkCmdProcessCommandsNVX - Performs the generation of commands on the device Parameters commandBufferP is the primary command buffer in which the generation process takes space.pProcessCommandsInfo) is a pointer to an instance of the vK structure containing parameters affecting the processing of commands.Valid Usage (Implicit) commandBuffer must be a valid VkCommandBuffer handlepProcessCommandsInfo must$ be a valid pointer to a valid VkCmdProcessCommandsInfoNVX structure commandBuffer must be in the fhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#commandbuffers-lifecyclerecording stateThe  VkCommandPool that  commandBuffer was allocated from must- support graphics, or compute operations This command must0 only be called inside of a render pass instanceHost SynchronizationHost access to  commandBuffer must be externally synchronizedHost access to the  VkCommandPool that  commandBuffer was allocated from must be externally synchronizedCommand Properties'  bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkCommandBufferLevelsCommand Buffer Levels   bhttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#vkCmdBeginRenderPassqRender Pass Scope   ]https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VkQueueFlagBitslSupported Queue Types   shttps://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#synchronization-pipeline-stages-typesPipeline Type  Primary Secondary  Inside  Graphics Compute  See Alsov, %VK_OBJECT_ENTRY_USAGE_COMPUTE_BIT_NVX* specifies that the resource is bound to VK_PIPELINE_BIND_POINT_COMPUTE&VK_OBJECT_ENTRY_USAGE_GRAPHICS_BIT_NVX* specifies that the resource is bound to VK_PIPELINE_BIND_POINT_GRAPHICS;VK_INDIRECT_COMMANDS_LAYOUT_USAGE_INDEXED_SEQUENCES_BIT_NVXw specifies that the input data for the sequences is not implicitly indexed from 0..sequencesUsed but a user provided VkBuffer! encoding the index is provided.:VK_INDIRECT_COMMANDS_LAYOUT_USAGE_EMPTY_EXECUTIONS_BIT_NVX specifies that there are likely many draw or dispatch calls that are zero-sized (zero grid dimension, no primitives to render).:VK_INDIRECT_COMMANDS_LAYOUT_USAGE_SPARSE_SEQUENCES_BIT_NVXl specifies that there is likely a high difference between allocated number of sequences and actually used.=VK_INDIRECT_COMMANDS_LAYOUT_USAGE_UNORDERED_SEQUENCES_BIT_NVX- specifies that the processing of sequences cans happen at an implementation-dependent order, which is not guaranteed to be coherent across multiple invocations.&VK_OBJECT_ENTRY_TYPE_PUSH_CONSTANT_NVX1 specifies the resource entry is registered via !VkObjectTablePushConstantEntryNVX.&VK_OBJECT_ENTRY_TYPE_VERTEX_BUFFER_NVX specifies a VkBuffer( resource entry that is registered via !VkObjectTableVertexBufferEntryNVX.%VK_OBJECT_ENTRY_TYPE_INDEX_BUFFER_NVX specifies a VkBuffer( resource entry that is registered via  VkObjectTableIndexBufferEntryNVX.!VK_OBJECT_ENTRY_TYPE_PIPELINE_NVX specifies a  VkPipeline( resource entry that is registered via VkObjectTablePipelineEntryNVX.'VK_OBJECT_ENTRY_TYPE_DESCRIPTOR_SET_NVX specifies a VkDescriptorSet) resource entry that is registered via "VkObjectTableDescriptorSetEntryNVX.@ABCEGDFHIKLJMNOQRPSTVUWXYZ\[]^_a`bcdefghijklmnopqrstuvwxyz{|}~טvwxyz{|}~opqrstubcdefghijklmn^_a`YZ\[]STVUWXNOQRPHIKLJMBCEGDFA@.Nonejkjxrstuvwxyz{|}~      )*+,-./0123456789:;EFGHIJKLMNOPQRSTUVW[\]^_`abcdefghijklwxyz{|}~     #$%&'(*)+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcstuvwxyz{|}~0123456789:;<=>?@ABWXYZ[\]^xyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQ}~ H I J K L M N P O Q R S T U V W X Y Z a b c d e f g h n i j k l m o p q r s t u v w x y z { | } ~                     ! " # $ % 0 1 2 3 4 5 6 7 8 9 : ; < = > ? J K L M N O P Q R S T U V W X Y d e f g h i j k l m n o p q r s ~                            ! " # $ % & ' ( ) * U V W X Y Z [ \ ] ^ _ ` a b c d e f g h i j k l m n p o q r s t u v w x y z | { } ~  a b c d e f g       !"$%&#'();<=>?@ABCDEFGHIJKLMNOYZ[\]^_tuvwxyz{     stuvxwyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTU_`abcdefghijklmnopqrstuvwxyz{|}~./0123456789:;<=>?BC@ADEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdfeimnghjklopqrstuvwxyz{|}~     !"#$%&'()*+,-./012NOPQRSTUVWXYuvwxyz{|}~     defghijklmnopqrstuvwxyz{|}~stuvwxyz{|}~,-./01234567;<=>?@ABCDEFGHIJ@ABCEGDFHIKLJMNOQRPSTVUWXYZ\[]^_a`bcdefghijklmnopqrstuvwxyz{|}~/Nonejkk .  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./012LMNOPQR      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKL   *-. !"#$%&'()+,/0123456789:;<=>?@ABCDEFGHIJKLMNOPQSRTUVWXYZ[\]^_`abcdefghijklmnopxqrstuvwyz{|}~                           ! " # $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ \ ] ^ _ ` a b c d e f g h i j k l m n o p q      #        ! " $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B h i j k l m n o p q r s v u t w x y z { -./01234567      !"#$/0123456:;=<>?@ABCGHIJKLMNOPQRS^_`abcfghidejklmnoqprstuvwx      !"      !"#$%&'()      !"#$%&'()*+,-./0123456789:;<=KLMNOPQRSTUVWXY[^Z\]_`abcdefghijklmnopqrstuvwx}z|y{~0Nonejkk?lC  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./012LMNOPQRSTUVWXYZ[_`abcdhijklmnrstuvwxyz{|}~      )*+,-./0123456789:;EFGHIJKLMNOPQRSTUVW[\]^_`abcdefghijklwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKL     #$%&'(*)+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcstuvwxyz{|}~     0123456789:;<=>?@ABCDEFGHIJKLWXYZ[\]^_`abcdefghijklmnopqxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQ}~   *-. !"#$%&'()+,/0123456789:;<=>?@ABCDEFGHIJKLMNOPQSRTUVWXYZ[\]^_`abcdefghijklmnopxqrstuvwyz{|}~                           ! " # $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ \ ] ^ _ ` a b c d e f g h i j k l m n o p q H I J K L M N P O Q R S T U V W X Y Z a b c d e f g h n i j k l m o p q r s t u v w x y z { | } ~                     ! " # $ % 0 1 2 3 4 5 6 7 8 9 : ; < = > ? J K L M N O P Q R S T U V W X Y d e f g h i j k l m n o p q r s ~                            ! " # $ % & ' ( ) * U V W X Y Z [ \ ] ^ _ ` a b c d e f g h i j k l m n p o q r s t u v w x y z | { } ~               #        ! " $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B a b c d e f g h i j k l m n o p q r s v u t w x y z {       !"$%&#'()-./01234567;<=>?@ABCDEFGHIJKLMNOYZ[\]^_`abcdefghijklmtuvwxyz{|}~)*+,-.10/23456789:;<=>?@ABCDIEFGHJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklm     9:;<=>?@ABCDEFGHIJKLMNOPQTRSUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$/0123456:;=<>?@ABCGHIJKLMNOPQRS^_`abcfghidejklmnoqprstuvwx !"#$%&'()*+-,./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRstuvxwyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTU_`abcdefghijklmnopqrstuvwxyz{|}~      !"./0123456789:;<=>?BC@ADEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdfeimnghjklopqrstuvwxyz{|}~     !"#$%&'()*+,-./012NOPQRSTUVWXY]^_`abcdefghijklmnopqrstvuwxyz{|}~      !"#$%&'()uvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=stuvwxyz{|}~     ,-./01234567;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXY[^Z\]_`abcdefghijklmnopqrstuvwx}z|y{~@ABCEGDFHIKLJMNOQRPSTVUWXYZ\[]^_a`bcdefghijklmnopqrstuvwxyz{|}~?123456789:;<=>??@@AABBCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyzPP{|}~nnrr                            mmSS        !"#$%&'()**+,-./01234567ss89:;<=>??@ABCDEFGHIJKLMNOPQRSTUVWX + + Y Z [ \ ] ^ _ ` a b!c!d"e"f#g#h$x$x$i$j$k$l$m$n$n$o$p$q$r$s$t$u$v$w$x$y$z${%w%w%|%}%~%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%&&'''(())**********************************************+,,,,,-----.///////////////////////////////////////////////////// / / / / /////////////////// /!/"/#/$/%/&/'/(/)/*/+/,/-/.///0/1/2/3/4/5/6/7/8/9/:/;/</=/>/?/@/A/B/C/D/E/F/G/H///I/J/K/L/M///N/O/P/Q/R/S/T/U/V/W/X/Y/Z/[/\/]/^/_/`/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/{/|/}/~/////////////////////////// / /////-/-/////>/>/////////////////////////////////////////////////////////////////////////////*/*////// //////////////////////////////////////////////////////////// / / / / /////////////////// /!/"/#/$/%/&/'/(/)/*/+/,/-/.///0/1/2/3/4/5/6/7/8/9/:/;/</=/>/?/@/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/[/\/]/^/_/`/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/{/|/}/~////////////////000000000000000000000000000000000000000111111 1 1111111111111222222k2k222222222222222222222222233333333333333333333333333333333333333333333333333333333 3 3 3 3 3333333333333333333 3!444"4#4$444%4&4'4(4)44*4*4+4+4u4n4144,4-4.4/404142434445464748494:4;4<4=4>4?4@4A4B4C4D5E5F5!5!5G5H5I5J5K5[5[5L5M5N5O5O5555P5Q5R5S5T5U5V5W5X5Y5Z5[5\5]5^5_5`5a5b5c5d5e5f5g5h5i5j5k5l6m6n6o6p6q6r6s6t6u6v6w6x6y6z6{6m6n6|6}67~7777777777777777777888888889999999999X9X999999999999999999999999999999999999:::::::::::::::::::;;;;;;;;;;;;;;;;;;;;<<<<<<<<=======]=]=================>>>>>>>>>>>>????? ? ? ?? ? ?.? ? ? ? ? ? ? ? ? ? ? @ @@@ @ @ @ @ @ @ @ @ @@@@@$@$@B@ @%@Q@ @ @ @ @ @ @ @ @ !@ "@ #@ $@ %@ &@ '@ (@ )@ *@ +@ ,@ -@ .@ /@ 0@ 1@ 2@ 3AAA 4A 5A 6A 7A;A;A 8A 9A :A ;A <A =AqAhA >A ?A @A AA BA CA DA EA FA GB#B#B HB IB JB KB5B5B LB MB NB OB PB QBoBTB RB SB TB UB VB WB XB YB ZB [C \C ]CCC ^C _C `C aC bC cC dC eC fC gC hC iCCC jC kC lC mC nC oC pCCC qC rC sC tCCC uC vC wC xC yC zC {CCC |C }C ~C C C C C C C C C C C C CCCCCCCCCC|C{C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C DDD D D D DDD D D D D D D DDD D D D D DDDDAD@D D D D D D D D D D D D D D EEE E E E E E-E E E E E E E E E E E F F FFF F F F F F FFFF F F F F F FF(FF F F F F F F F F F F F F F F F F F F F F F F F F F F F F F F F F F F F F F F F F F !F "F #F $F %F &GtGtG 'G (G )G *G +GG ,G ,GtGG&GG -G .G /G 0G 1G 2G 3G 4G 5G 6H 7H 8HH 9H'H'H :H ;H <H =H >H ?H @H AH BH CH DH EH FH GH HH IH JH KH LHyHyH MH NH OH PH QH RH SH TH UH VH WH XH YH YH ZH [H \H ]H ^H _H `H{H{H aH bH cH dH eHvHvH fH gH hH iH jH kH lH mHHH nH oH pH qH rH sH tH uH~H~H vH wH xH yH zH {H |H }H ~HHH H H H H H H H H H H H H HHH H H H H H H HHH H H H H|H|H H H H H HHH H H H H H H HHH H H H HHH H H HHH H H H H H H HHH H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H HHHH H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H%HHH H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H !H "H #H $H %H &H 'H (H )H *H +H ,H -H .H /H 0H 1H 2H 3H 4H 5H 6H 7H 8H 9H :H ;H <H =H >H ?H @H AH BH CH DH EH FH GH HH IH JH KH LH MH NH OH PH QH RH SH TH UH VH WH XH YH ZH [H \H ]H ^H _H `H aH bH cH dH eH fH gH hH iH jH kH lH mH nH oH pH qH rH sH tH uH vH wH xH yH zH {H |H }H ~H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H H !H "H #I $I %I &JJJ 'J (J )J *J +JJJ ,J -JJ .J /J 0J 1J 2J 3J 4J 5J 6J 7K 8K 9KKK :K ;KKK <K =K >K ?K @K AK BK CK DK EKK FK FK GK GK HK HK IK IKKKKK/K JK KK LK MK NK OK PK QK RK SK TK UK VK WK XK YK ZK [K \K ]K ^K _K `K aK bK cK dK eK fK gK hK iK jK kK lK mK nK oK pK qK rK sK tK uK vK wK xK yK zK {K |K }K ~K LLL L L L L L LL L L L L L L L L L L L L M?M?M M M M M M MM M M M M M M M M M M M M N)N)N N N N N N NN N N N N N N N N N N N N OOO O O O O O O O O O O OOO O O O O O O O O O O O O PPP P P P P P P P P P PPP P P P P P P P P P P P P QQQ Q Q Q Q Q Q Q Q QQQ Q Q Q Q Q Q Q Q Q Q Q Q RRR R R R R R R R R RRR R R R R R R R R R R R R SMSMS S S S S S S S S SSS S S S S S S S S S S S S TTT !T "T #TTT $T %T &TqTqT 'T (T )TTT *T +T ,T -T .T /T 0T 1T 2T 3T 4T 5T 6T 7UUU 8U 9U :U ;U <U <U =UU >U ?U @U AU BU CU DU EU FU GU HU IU JV KV LV MV NV OV PV QV RV SV TV UV VV WV XV YV ZWWW [W \W ]W ^W ^W _W `WWW aW bW cW dW eW fW gW hW iW jW kW lW mW nW oW pX qXXX rX sX tX uX vX wX xX yX zX {XXX |X }X ~X X X X X X X X X X X X X X X X XXX X X X X X XXX X X X X X X XXX X X X X X XXXXXXXX X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X YY Y Z ZZZ Z [N[N[ [ [ [j[j[ [ [ [ [ [ [ [[[ [ [ [ [[[ [ [ [ [ [ [ [ [ [ [ [ [ [ [[[ [ [ [ [ [ [ [ [ [ [[[ [ [ [ [ [ [ [ [ [[[[[[[[[[ [ [ [ [ [[[[[[[[[[\\\\\\\\\\\ \!\"\#\$\%\&\&\\'\(\)\*\+\,\-\.\/\0\1\2\3\4\5]z]z]6]7]8]9]:];]V]V]<]=]>]?]?]@]@]]A]B]C]D]E]F]G]H]I]J]K]L]M]N]O]P]Q]R]S]T]U]V]W]X]Y^^^Z^[^\^]^^^_^^^`^a^b^c^d^e^f^g^h^i^j^k^l___m_n_o_p_q_r_s_t_u_v_w_x_y_z_{_|_}_~____________*_____________________________________________```aaaabb}b}bbbbbbbb,b,bbbbbbb'bbbbbbbbbbbbbbc c cccccccccccccccccjccccccccccccccccddpdpdddddddddddddddddddddddddddee e f@f@f f f fffBfBfffffffffsfDfff2fffffffffffff f!ggg"g#g$g%g&g'g(g)g*g+g,g-g.g/g0hhh1h2h3h4h:h:h5h6h7h8h9h:h;hch<h=h>h?h@hAhBhChDhEiiiFiGiHiIiJiKiLiMiNiOiPiQiRiSiTjjjUjVjWjjjjWjjHjXjYjZkkk[k\k]k^kkk_k`kakkkbkckdkekfkgkhkikjkkklkmknkokpkqkrlllsltmmumvnDnDnwnxnynznEnEn{n|n}n~nnnnnnnnooooooooppppppppppppppp>p<pppppppppqqqqqqqqqq=q?rrrrrrrrrrrrrrrrrr r rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr7r7rrrrrrrrrrrrrrrrrZrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr r r r r rrrrrrrrsososssssssssssssasas s!s"sss#s$s%s_s_s&s's(s)s*s+s,s,s,s-s.s/s%s%s0s1s2sfsfs3s4s5s\s\s6s7s8ssssssss9s:s;s<s=s>s?s@sAsBsCsDsEsFsGsHsIsJsKsLsMsNsOsPsQsRsSsTsUsVsWsXsYsZs[s\t]t^t_t`tatbtctt(tdtetftgthtitjtktlt]t^t_t`tatbtctt(tmtntttttttuuuoupuquKuKurusutu0u0uuuvuwu.u.uxuyuzuuu{u|u}u[uXuIu~uuuuuuuuuuuuuuuuuuuvvvvvvvvvvvvvvvvvvJvYv\w2w2wwwwwwwwwwwwwwwwwwwwwwwwwwwww"wwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwxxxxxxlxlxxxx/x/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx+xxxxxxxxxxxxxxxxxxxxxx x x x x xxxxxxxxxxxxxxxxxxx x!x"x#x$x%x&x'x(x)x*x+x,x-x.x/x0x1x2x3x4x5x6x7x8x9x:x;x<x=x>x?x@xAxBxCxDxExFxGxHxIxJxKxLxMxNxOxPxQxRySyTyUyVyWyXyYyZy[y\y]y^y_y`yaybycydyeyfygyhyiyjykylymynyoypyqyrysytyuyvywyxyyyzy{y|y}y~yyyyyyyyyyyyyyyyyyyyyyyyyyyyySyTyUyVyWyXyyy y,zz"z"zzzzzzzUzzzzzzzzzzzzzzz{{{{{{{{{{{|||||||||||||}}}}}}}}}y}}}S}}}}}}}}}}}}~~~~~~~~~~~~~~ ~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~w      !"#$%&'(()*+,-./0123456789:;<==>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abc^^defghijklmWWnopqrstuYYvwxyyz{|}~~""}IILL99db<<ri$$66 pV    HHFF77 !"`_#$%&'()*+,-./01234 56789:;<=>?@ABCDEFG1234 HIZZJKLJJMNO88PQRSaTUVWXYZ[\]^_`abcdefghijklmnopqrsGGtuvwxyz{|}44~^G!!  hhggR**]!     11 !"#$%&'()*+,-./0123456789:;<=>?@@AA8PO9l0 BCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ ef((~  k43Cm33ee       !"#$%&'()*+,-./0123456789:;<=>?@ABCDEF45678GHIJKL&&MNOPQRSTUVWXYZ[\]^_`abcdefghijklmno##pqrstuvwxyz{{||}}++~~g) ccuuRRQQ      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPddQRSTbbUVWXYZ[\]^_`abcdefghijklmghinopqrstuvwxyz{|}~AAMNE:      !""#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHHIIJJKKF;xLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~UUTT&&``KL  ''    !"#$%&'ii()*+,-./0123456789:;34<=>?@ABCDEFFGHIJJKLMNOPPQRSTUVWXXYZ[\]^_`a66bcdefghijklmnop55qrstuvwx--yz{|}~CCOO     ==  !"#$%&'()*+,-./0122334455v$#6789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~///34?@@@@CFGHHHKXX_bfjjwx}$vulkan-2.0.0.1-BoVqvLBrBaAqj9fSupO5i Graphics.Vulkan.Core10.ConstantsGraphics.Vulkan.Core10.CoreGraphics.Vulkan.Core10.Version9Graphics.Vulkan.Core11.Promoted_from_VK_KHR_16bit_storageBGraphics.Vulkan.Core11.Promoted_from_VK_KHR_shader_draw_parameters=Graphics.Vulkan.Core11.Promoted_from_VK_KHR_variable_pointers,Graphics.Vulkan.Extensions.VK_AMD_gcn_shader7Graphics.Vulkan.Extensions.VK_AMD_gpu_shader_half_float2Graphics.Vulkan.Extensions.VK_AMD_gpu_shader_int16:Graphics.Vulkan.Extensions.VK_AMD_mixed_attachment_samples:Graphics.Vulkan.Extensions.VK_AMD_negative_viewport_height5Graphics.Vulkan.Extensions.VK_AMD_rasterization_order/Graphics.Vulkan.Extensions.VK_AMD_shader_ballot8Graphics.Vulkan.Extensions.VK_AMD_shader_core_propertiesBGraphics.Vulkan.Extensions.VK_AMD_shader_explicit_vertex_parameter6Graphics.Vulkan.Extensions.VK_AMD_shader_fragment_mask=Graphics.Vulkan.Extensions.VK_AMD_shader_image_load_store_lod7Graphics.Vulkan.Extensions.VK_AMD_shader_trinary_minmax9Graphics.Vulkan.Extensions.VK_AMD_texture_gather_bias_lodGraphics.Vulkan.Extensions.VK_KHR_storage_buffer_storage_class;Graphics.Vulkan.Extensions.VK_NV_fragment_coverage_to_color:Graphics.Vulkan.Extensions.VK_NV_framebuffer_mixed_samplesGraphics.Vulkan.Extensions.VK_NV_sample_mask_override_coverage0Graphics.Vulkan.Extensions.VK_NV_viewport_array21Graphics.Vulkan.Extensions.VK_NV_viewport_swizzleGraphics.Vulkan.NamedType3Graphics.Vulkan.Extensions.VK_KHR_variable_pointers/Graphics.Vulkan.Extensions.VK_KHR_16bit_storage+Graphics.Vulkan.Core11.DeviceInitialization+Graphics.Vulkan.Core10.DeviceInitialization=Graphics.Vulkan.Extensions.VK_NV_external_memory_capabilities0Graphics.Vulkan.Extensions.VK_NV_external_memory7Graphics.Vulkan.Extensions.VK_EXT_sampler_filter_minmax.Graphics.Vulkan.Extensions.VK_EXT_debug_report2Graphics.Vulkan.Extensions.VK_EXT_validation_cacheKGraphics.Vulkan.Core11.Promoted_from_VK_KHR_external_semaphore_capabilitiesAGraphics.Vulkan.Extensions.VK_KHR_external_semaphore_capabilities>Graphics.Vulkan.Core11.Promoted_from_VK_KHR_external_semaphore4Graphics.Vulkan.Extensions.VK_KHR_external_semaphoreGGraphics.Vulkan.Core11.Promoted_from_VK_KHR_external_fence_capabilities=Graphics.Vulkan.Extensions.VK_KHR_external_fence_capabilities:Graphics.Vulkan.Core11.Promoted_from_VK_KHR_external_fence0Graphics.Vulkan.Extensions.VK_KHR_external_fenceAGraphics.Vulkan.Core11.Promoted_from_VK_KHR_device_group_creation7Graphics.Vulkan.Extensions.VK_KHR_device_group_creationGraphics.Vulkan.Core10.ShaderGraphics.Vulkan.Core10.Queue7Graphics.Vulkan.Extensions.VK_KHR_external_semaphore_fd3Graphics.Vulkan.Extensions.VK_KHR_external_fence_fd-Graphics.Vulkan.Extensions.VK_EXT_debug_utils.Graphics.Vulkan.Extensions.VK_EXT_debug_marker%Graphics.Vulkan.Core10.QueueSemaphoreGraphics.Vulkan.Core10.Query$Graphics.Vulkan.Core10.PipelineCacheGraphics.Vulkan.Core10.Pipeline/Graphics.Vulkan.Extensions.VK_NV_fill_rectangle5Graphics.Vulkan.Extensions.VK_NV_clip_space_w_scaling)Graphics.Vulkan.Extensions.VK_KHR_surface+Graphics.Vulkan.Extensions.VK_NN_vi_surface/Graphics.Vulkan.Extensions.VK_MVK_macos_surface-Graphics.Vulkan.Extensions.VK_MVK_ios_surface.Graphics.Vulkan.Extensions.VK_KHR_xlib_surface-Graphics.Vulkan.Extensions.VK_KHR_xcb_surface/Graphics.Vulkan.Extensions.VK_KHR_win32_surface1Graphics.Vulkan.Extensions.VK_KHR_wayland_surface-Graphics.Vulkan.Extensions.VK_KHR_mir_surface;Graphics.Vulkan.Extensions.VK_KHR_get_surface_capabilities21Graphics.Vulkan.Extensions.VK_KHR_android_surface6Graphics.Vulkan.Extensions.VK_EXT_swapchain_colorspace5Graphics.Vulkan.Extensions.VK_KHR_incremental_present)Graphics.Vulkan.Extensions.VK_KHR_display5Graphics.Vulkan.Extensions.VK_EXT_direct_mode_display6Graphics.Vulkan.Extensions.VK_EXT_acquire_xlib_display2Graphics.Vulkan.Extensions.VK_EXT_sample_locations9Graphics.Vulkan.Extensions.VK_EXT_display_surface_counter4Graphics.Vulkan.Extensions.VK_EXT_discard_rectanglesPGraphics.Vulkan.Core11.Promoted_from_VK_KHR_device_group_and_VK_KHR_bind_memory2Graphics.Vulkan.Core10.Sampler>Graphics.Vulkan.Extensions.VK_KHR_sampler_mirror_clamp_to_edge.Graphics.Vulkan.Extensions.VK_IMG_filter_cubic%Graphics.Vulkan.Core10.PipelineLayout-Graphics.Vulkan.Extensions.VK_AMD_shader_info4Graphics.Vulkan.Core11.Promoted_From_VK_KHR_subgroupGraphics.Vulkan.Extensions.VK_KHR_external_memory_capabilities6Graphics.Vulkan.Extensions.VK_EXT_external_memory_host9Graphics.Vulkan.Extensions.VK_EXT_external_memory_dma_bufMGraphics.Vulkan.Extensions.VK_ANDROID_external_memory_android_hardware_buffer;Graphics.Vulkan.Core11.Promoted_from_VK_KHR_external_memory1Graphics.Vulkan.Extensions.VK_KHR_external_memory$sel:vkSType:VkPipelineRasterizationStateRasterizationOrderAMD>$sel:vkPNext:VkPipelineRasterizationStateRasterizationOrderAMDK$sel:vkRasterizationOrder:VkPipelineRasterizationStateRasterizationOrderAMDVkRasterizationOrderAMD)VK_AMD_RASTERIZATION_ORDER_EXTENSION_NAME'VK_AMD_RASTERIZATION_ORDER_SPEC_VERSIONFVK_STRUCTURE_TYPE_PIPELINE_RASTERIZATION_STATE_RASTERIZATION_ORDER_AMD"VK_RASTERIZATION_ORDER_RELAXED_AMD!VK_RASTERIZATION_ORDER_STRICT_AMD$fReadVkRasterizationOrderAMD$fShowVkRasterizationOrderAMD;$fStorableVkPipelineRasterizationStateRasterizationOrderAMD$fEqVkRasterizationOrderAMD$fOrdVkRasterizationOrderAMD!$fStorableVkRasterizationOrderAMD5$fEqVkPipelineRasterizationStateRasterizationOrderAMD7$fShowVkPipelineRasterizationStateRasterizationOrderAMD#VK_AMD_SHADER_BALLOT_EXTENSION_NAME!VK_AMD_SHADER_BALLOT_SPEC_VERSION4$sel:vkSType:VkPhysicalDeviceShaderCorePropertiesAMD4$sel:vkPNext:VkPhysicalDeviceShaderCorePropertiesAMD@$sel:vkShaderEngineCount:VkPhysicalDeviceShaderCorePropertiesAMDI$sel:vkShaderArraysPerEngineCount:VkPhysicalDeviceShaderCorePropertiesAMDI$sel:vkComputeUnitsPerShaderArray:VkPhysicalDeviceShaderCorePropertiesAMDA$sel:vkSimdPerComputeUnit:VkPhysicalDeviceShaderCorePropertiesAMD@$sel:vkWavefrontsPerSimd:VkPhysicalDeviceShaderCorePropertiesAMD<$sel:vkWavefrontSize:VkPhysicalDeviceShaderCorePropertiesAMD;$sel:vkSgprsPerSimd:VkPhysicalDeviceShaderCorePropertiesAMD@$sel:vkMinSgprAllocation:VkPhysicalDeviceShaderCorePropertiesAMD@$sel:vkMaxSgprAllocation:VkPhysicalDeviceShaderCorePropertiesAMDH$sel:vkSgprAllocationGranularity:VkPhysicalDeviceShaderCorePropertiesAMD;$sel:vkVgprsPerSimd:VkPhysicalDeviceShaderCorePropertiesAMD@$sel:vkMinVgprAllocation:VkPhysicalDeviceShaderCorePropertiesAMD@$sel:vkMaxVgprAllocation:VkPhysicalDeviceShaderCorePropertiesAMDH$sel:vkVgprAllocationGranularity:VkPhysicalDeviceShaderCorePropertiesAMD,VK_AMD_SHADER_CORE_PROPERTIES_EXTENSION_NAME*VK_AMD_SHADER_CORE_PROPERTIES_SPEC_VERSION$sel:vkGlobalPriority:VkDeviceQueueGlobalPriorityCreateInfoEXTVkQueueGlobalPriorityEXT%VK_EXT_GLOBAL_PRIORITY_EXTENSION_NAME#VK_EXT_GLOBAL_PRIORITY_SPEC_VERSION>VK_STRUCTURE_TYPE_DEVICE_QUEUE_GLOBAL_PRIORITY_CREATE_INFO_EXTVK_ERROR_NOT_PERMITTED_EXT%VK_QUEUE_GLOBAL_PRIORITY_REALTIME_EXT!VK_QUEUE_GLOBAL_PRIORITY_HIGH_EXT#VK_QUEUE_GLOBAL_PRIORITY_MEDIUM_EXT VK_QUEUE_GLOBAL_PRIORITY_LOW_EXT$fReadVkQueueGlobalPriorityEXT$fShowVkQueueGlobalPriorityEXT2$fStorableVkDeviceQueueGlobalPriorityCreateInfoEXT$fEqVkQueueGlobalPriorityEXT$fOrdVkQueueGlobalPriorityEXT"$fStorableVkQueueGlobalPriorityEXT,$fEqVkDeviceQueueGlobalPriorityCreateInfoEXT.$fShowVkDeviceQueueGlobalPriorityCreateInfoEXT)VK_EXT_POST_DEPTH_COVERAGE_EXTENSION_NAME'VK_EXT_POST_DEPTH_COVERAGE_SPEC_VERSION*VK_EXT_QUEUE_FAMILY_FOREIGN_EXTENSION_NAME(VK_EXT_QUEUE_FAMILY_FOREIGN_SPEC_VERSIONVK_QUEUE_FAMILY_FOREIGN_EXT+VK_EXT_SHADER_STENCIL_EXPORT_EXTENSION_NAME)VK_EXT_SHADER_STENCIL_EXPORT_SPEC_VERSION,VK_EXT_SHADER_SUBGROUP_BALLOT_EXTENSION_NAME*VK_EXT_SHADER_SUBGROUP_BALLOT_SPEC_VERSION*VK_EXT_SHADER_SUBGROUP_VOTE_EXTENSION_NAME(VK_EXT_SHADER_SUBGROUP_VOTE_SPEC_VERSION1VK_EXT_SHADER_VIEWPORT_INDEX_LAYER_EXTENSION_NAME/VK_EXT_SHADER_VIEWPORT_INDEX_LAYER_SPEC_VERSION!$sel:vkSType:VkValidationFlagsEXT!$sel:vkPNext:VkValidationFlagsEXT8$sel:vkDisabledValidationCheckCount:VkValidationFlagsEXT5$sel:vkPDisabledValidationChecks:VkValidationFlagsEXTVkValidationCheckEXT&VK_EXT_VALIDATION_FLAGS_EXTENSION_NAME$VK_EXT_VALIDATION_FLAGS_SPEC_VERSION&VK_STRUCTURE_TYPE_VALIDATION_FLAGS_EXTVK_VALIDATION_CHECK_SHADERS_EXTVK_VALIDATION_CHECK_ALL_EXT$fReadVkValidationCheckEXT$fShowVkValidationCheckEXT$fStorableVkValidationFlagsEXT$fEqVkValidationCheckEXT$fOrdVkValidationCheckEXT$fStorableVkValidationCheckEXT$fEqVkValidationFlagsEXT$fShowVkValidationFlagsEXT@$sel:vkSType:VkPhysicalDeviceVertexAttributeDivisorPropertiesEXT@$sel:vkPNext:VkPhysicalDeviceVertexAttributeDivisorPropertiesEXTQ$sel:vkMaxVertexAttribDivisor:VkPhysicalDeviceVertexAttributeDivisorPropertiesEXT;$sel:vkSType:VkPipelineVertexInputDivisorStateCreateInfoEXT;$sel:vkPNext:VkPipelineVertexInputDivisorStateCreateInfoEXTO$sel:vkVertexBindingDivisorCount:VkPipelineVertexInputDivisorStateCreateInfoEXTL$sel:vkPVertexBindingDivisors:VkPipelineVertexInputDivisorStateCreateInfoEXT)VkVertexInputBindingDivisorDescriptionEXT8$sel:vkBinding:VkVertexInputBindingDivisorDescriptionEXT8$sel:vkDivisor:VkVertexInputBindingDivisorDescriptionEXT.VK_EXT_VERTEX_ATTRIBUTE_DIVISOR_EXTENSION_NAME,VK_EXT_VERTEX_ATTRIBUTE_DIVISOR_SPEC_VERSIONEVK_STRUCTURE_TYPE_PIPELINE_VERTEX_INPUT_DIVISOR_STATE_CREATE_INFO_EXTIVK_STRUCTURE_TYPE_PHYSICAL_DEVICE_VERTEX_ATTRIBUTE_DIVISOR_PROPERTIES_EXT3$fStorableVkVertexInputBindingDivisorDescriptionEXT8$fStorableVkPipelineVertexInputDivisorStateCreateInfoEXT=$fStorableVkPhysicalDeviceVertexAttributeDivisorPropertiesEXT-$fEqVkVertexInputBindingDivisorDescriptionEXT/$fShowVkVertexInputBindingDivisorDescriptionEXT2$fEqVkPipelineVertexInputDivisorStateCreateInfoEXT4$fShowVkPipelineVertexInputDivisorStateCreateInfoEXT7$fEqVkPhysicalDeviceVertexAttributeDivisorPropertiesEXT9$fShowVkPhysicalDeviceVertexAttributeDivisorPropertiesEXT"VK_IMG_FORMAT_PVRTC_EXTENSION_NAME VK_IMG_FORMAT_PVRTC_SPEC_VERSION$VK_FORMAT_PVRTC2_4BPP_SRGB_BLOCK_IMG$VK_FORMAT_PVRTC2_2BPP_SRGB_BLOCK_IMG$VK_FORMAT_PVRTC1_4BPP_SRGB_BLOCK_IMG$VK_FORMAT_PVRTC1_2BPP_SRGB_BLOCK_IMG%VK_FORMAT_PVRTC2_4BPP_UNORM_BLOCK_IMG%VK_FORMAT_PVRTC2_2BPP_UNORM_BLOCK_IMG%VK_FORMAT_PVRTC1_4BPP_UNORM_BLOCK_IMG%VK_FORMAT_PVRTC1_2BPP_UNORM_BLOCK_IMG+$sel:vkSType:VkImageFormatListCreateInfoKHR+$sel:vkPNext:VkImageFormatListCreateInfoKHR5$sel:vkViewFormatCount:VkImageFormatListCreateInfoKHR2$sel:vkPViewFormats:VkImageFormatListCreateInfoKHR'VK_KHR_IMAGE_FORMAT_LIST_EXTENSION_NAME%VK_KHR_IMAGE_FORMAT_LIST_SPEC_VERSION3VK_STRUCTURE_TYPE_IMAGE_FORMAT_LIST_CREATE_INFO_KHR($fStorableVkImageFormatListCreateInfoKHR"$fEqVkImageFormatListCreateInfoKHR$$fShowVkImageFormatListCreateInfoKHR*VK_KHR_RELAXED_BLOCK_LAYOUT_EXTENSION_NAME(VK_KHR_RELAXED_BLOCK_LAYOUT_SPEC_VERSION,VK_KHR_SHADER_DRAW_PARAMETERS_EXTENSION_NAME*VK_KHR_SHADER_DRAW_PARAMETERS_SPEC_VERSION2VK_KHR_STORAGE_BUFFER_STORAGE_CLASS_EXTENSION_NAME0VK_KHR_STORAGE_BUFFER_STORAGE_CLASS_SPEC_VERSION7$sel:vkSType:VkPipelineCoverageToColorStateCreateInfoNV7$sel:vkPNext:VkPipelineCoverageToColorStateCreateInfoNV7$sel:vkFlags:VkPipelineCoverageToColorStateCreateInfoNVG$sel:vkCoverageToColorEnable:VkPipelineCoverageToColorStateCreateInfoNVI$sel:vkCoverageToColorLocation:VkPipelineCoverageToColorStateCreateInfoNV+VkPipelineCoverageToColorStateCreateFlagsNV/VK_NV_FRAGMENT_COVERAGE_TO_COLOR_EXTENSION_NAME-VK_NV_FRAGMENT_COVERAGE_TO_COLOR_SPEC_VERSIONAVK_STRUCTURE_TYPE_PIPELINE_COVERAGE_TO_COLOR_STATE_CREATE_INFO_NV1$fReadVkPipelineCoverageToColorStateCreateFlagsNV1$fShowVkPipelineCoverageToColorStateCreateFlagsNV4$fStorableVkPipelineCoverageToColorStateCreateInfoNV/$fEqVkPipelineCoverageToColorStateCreateFlagsNV0$fOrdVkPipelineCoverageToColorStateCreateFlagsNV5$fStorableVkPipelineCoverageToColorStateCreateFlagsNV1$fBitsVkPipelineCoverageToColorStateCreateFlagsNV7$fFiniteBitsVkPipelineCoverageToColorStateCreateFlagsNV.$fEqVkPipelineCoverageToColorStateCreateInfoNV0$fShowVkPipelineCoverageToColorStateCreateInfoNV:$sel:vkSType:VkPipelineCoverageModulationStateCreateInfoNV:$sel:vkPNext:VkPipelineCoverageModulationStateCreateInfoNV:$sel:vkFlags:VkPipelineCoverageModulationStateCreateInfoNVK$sel:vkCoverageModulationMode:VkPipelineCoverageModulationStateCreateInfoNVR$sel:vkCoverageModulationTableEnable:VkPipelineCoverageModulationStateCreateInfoNVQ$sel:vkCoverageModulationTableCount:VkPipelineCoverageModulationStateCreateInfoNVM$sel:vkPCoverageModulationTable:VkPipelineCoverageModulationStateCreateInfoNV.VkPipelineCoverageModulationStateCreateFlagsNVVkCoverageModulationModeNV.VK_NV_FRAMEBUFFER_MIXED_SAMPLES_EXTENSION_NAME,VK_NV_FRAMEBUFFER_MIXED_SAMPLES_SPEC_VERSIONCVK_STRUCTURE_TYPE_PIPELINE_COVERAGE_MODULATION_STATE_CREATE_INFO_NV#VK_COVERAGE_MODULATION_MODE_RGBA_NV$VK_COVERAGE_MODULATION_MODE_ALPHA_NV"VK_COVERAGE_MODULATION_MODE_RGB_NV#VK_COVERAGE_MODULATION_MODE_NONE_NV $fReadVkCoverageModulationModeNV $fShowVkCoverageModulationModeNV4$fReadVkPipelineCoverageModulationStateCreateFlagsNV4$fShowVkPipelineCoverageModulationStateCreateFlagsNV7$fStorableVkPipelineCoverageModulationStateCreateInfoNV$fEqVkCoverageModulationModeNV$fOrdVkCoverageModulationModeNV$$fStorableVkCoverageModulationModeNV2$fEqVkPipelineCoverageModulationStateCreateFlagsNV3$fOrdVkPipelineCoverageModulationStateCreateFlagsNV8$fStorableVkPipelineCoverageModulationStateCreateFlagsNV4$fBitsVkPipelineCoverageModulationStateCreateFlagsNV:$fFiniteBitsVkPipelineCoverageModulationStateCreateFlagsNV1$fEqVkPipelineCoverageModulationStateCreateInfoNV3$fShowVkPipelineCoverageModulationStateCreateInfoNV0VK_NV_GEOMETRY_SHADER_PASSTHROUGH_EXTENSION_NAME.VK_NV_GEOMETRY_SHADER_PASSTHROUGH_SPEC_VERSION VK_NV_GLSL_SHADER_EXTENSION_NAMEVK_NV_GLSL_SHADER_SPEC_VERSIONVK_ERROR_INVALID_SHADER_NV2VK_NV_SAMPLE_MASK_OVERRIDE_COVERAGE_EXTENSION_NAME0VK_NV_SAMPLE_MASK_OVERRIDE_COVERAGE_SPEC_VERSION$VK_NV_VIEWPORT_ARRAY2_EXTENSION_NAME"VK_NV_VIEWPORT_ARRAY2_SPEC_VERSION7$sel:vkSType:VkPipelineViewportSwizzleStateCreateInfoNV7$sel:vkPNext:VkPipelineViewportSwizzleStateCreateInfoNV7$sel:vkFlags:VkPipelineViewportSwizzleStateCreateInfoNV?$sel:vkViewportCount:VkPipelineViewportSwizzleStateCreateInfoNVC$sel:vkPViewportSwizzles:VkPipelineViewportSwizzleStateCreateInfoNVVkViewportSwizzleNV$sel:vkX:VkViewportSwizzleNV$sel:vkY:VkViewportSwizzleNV$sel:vkZ:VkViewportSwizzleNV$sel:vkW:VkViewportSwizzleNV+VkPipelineViewportSwizzleStateCreateFlagsNVVkViewportCoordinateSwizzleNV%VK_NV_VIEWPORT_SWIZZLE_EXTENSION_NAME#VK_NV_VIEWPORT_SWIZZLE_SPEC_VERSION@VK_STRUCTURE_TYPE_PIPELINE_VIEWPORT_SWIZZLE_STATE_CREATE_INFO_NV,VK_VIEWPORT_COORDINATE_SWIZZLE_NEGATIVE_W_NV,VK_VIEWPORT_COORDINATE_SWIZZLE_POSITIVE_W_NV,VK_VIEWPORT_COORDINATE_SWIZZLE_NEGATIVE_Z_NV,VK_VIEWPORT_COORDINATE_SWIZZLE_POSITIVE_Z_NV,VK_VIEWPORT_COORDINATE_SWIZZLE_NEGATIVE_Y_NV,VK_VIEWPORT_COORDINATE_SWIZZLE_POSITIVE_Y_NV,VK_VIEWPORT_COORDINATE_SWIZZLE_NEGATIVE_X_NV,VK_VIEWPORT_COORDINATE_SWIZZLE_POSITIVE_X_NV#$fReadVkViewportCoordinateSwizzleNV#$fShowVkViewportCoordinateSwizzleNV1$fReadVkPipelineViewportSwizzleStateCreateFlagsNV1$fShowVkPipelineViewportSwizzleStateCreateFlagsNV$fStorableVkViewportSwizzleNV4$fStorableVkPipelineViewportSwizzleStateCreateInfoNV!$fEqVkViewportCoordinateSwizzleNV"$fOrdVkViewportCoordinateSwizzleNV'$fStorableVkViewportCoordinateSwizzleNV/$fEqVkPipelineViewportSwizzleStateCreateFlagsNV0$fOrdVkPipelineViewportSwizzleStateCreateFlagsNV5$fStorableVkPipelineViewportSwizzleStateCreateFlagsNV1$fBitsVkPipelineViewportSwizzleStateCreateFlagsNV7$fFiniteBitsVkPipelineViewportSwizzleStateCreateFlagsNV$fEqVkViewportSwizzleNV$fShowVkViewportSwizzleNV.$fEqVkPipelineViewportSwizzleStateCreateInfoNV0$fShowVkPipelineViewportSwizzleStateCreateInfoNV:::*VkPhysicalDeviceVariablePointerFeaturesKHR?VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_VARIABLE_POINTER_FEATURES_KHR'VK_KHR_VARIABLE_POINTERS_EXTENSION_NAME%VK_KHR_VARIABLE_POINTERS_SPEC_VERSION'VkPhysicalDevice16BitStorageFeaturesKHR$sel:vkMaxDescriptorSetInputAttachments:VkPhysicalDeviceLimits6$sel:vkMaxVertexInputAttributes:VkPhysicalDeviceLimits4$sel:vkMaxVertexInputBindings:VkPhysicalDeviceLimits;$sel:vkMaxVertexInputAttributeOffset:VkPhysicalDeviceLimits9$sel:vkMaxVertexInputBindingStride:VkPhysicalDeviceLimits7$sel:vkMaxVertexOutputComponents:VkPhysicalDeviceLimits<$sel:vkMaxTessellationGenerationLevel:VkPhysicalDeviceLimits6$sel:vkMaxTessellationPatchSize:VkPhysicalDeviceLimitsL$sel:vkMaxTessellationControlPerVertexInputComponents:VkPhysicalDeviceLimitsM$sel:vkMaxTessellationControlPerVertexOutputComponents:VkPhysicalDeviceLimitsL$sel:vkMaxTessellationControlPerPatchOutputComponents:VkPhysicalDeviceLimitsI$sel:vkMaxTessellationControlTotalOutputComponents:VkPhysicalDeviceLimitsF$sel:vkMaxTessellationEvaluationInputComponents:VkPhysicalDeviceLimitsG$sel:vkMaxTessellationEvaluationOutputComponents:VkPhysicalDeviceLimits:$sel:vkMaxGeometryShaderInvocations:VkPhysicalDeviceLimits8$sel:vkMaxGeometryInputComponents:VkPhysicalDeviceLimits9$sel:vkMaxGeometryOutputComponents:VkPhysicalDeviceLimits7$sel:vkMaxGeometryOutputVertices:VkPhysicalDeviceLimits>$sel:vkMaxGeometryTotalOutputComponents:VkPhysicalDeviceLimits8$sel:vkMaxFragmentInputComponents:VkPhysicalDeviceLimits:$sel:vkMaxFragmentOutputAttachments:VkPhysicalDeviceLimits;$sel:vkMaxFragmentDualSrcAttachments:VkPhysicalDeviceLimits@$sel:vkMaxFragmentCombinedOutputResources:VkPhysicalDeviceLimits8$sel:vkMaxComputeSharedMemorySize:VkPhysicalDeviceLimits6$sel:vkMaxComputeWorkGroupCount:VkPhysicalDeviceLimits<$sel:vkMaxComputeWorkGroupInvocations:VkPhysicalDeviceLimits5$sel:vkMaxComputeWorkGroupSize:VkPhysicalDeviceLimits3$sel:vkSubPixelPrecisionBits:VkPhysicalDeviceLimits3$sel:vkSubTexelPrecisionBits:VkPhysicalDeviceLimits1$sel:vkMipmapPrecisionBits:VkPhysicalDeviceLimits6$sel:vkMaxDrawIndexedIndexValue:VkPhysicalDeviceLimits2$sel:vkMaxDrawIndirectCount:VkPhysicalDeviceLimits/$sel:vkMaxSamplerLodBias:VkPhysicalDeviceLimits2$sel:vkMaxSamplerAnisotropy:VkPhysicalDeviceLimits*$sel:vkMaxViewports:VkPhysicalDeviceLimits3$sel:vkMaxViewportDimensions:VkPhysicalDeviceLimits1$sel:vkViewportBoundsRange:VkPhysicalDeviceLimits2$sel:vkViewportSubPixelBits:VkPhysicalDeviceLimits3$sel:vkMinMemoryMapAlignment:VkPhysicalDeviceLimits;$sel:vkMinTexelBufferOffsetAlignment:VkPhysicalDeviceLimits=$sel:vkMinUniformBufferOffsetAlignment:VkPhysicalDeviceLimits=$sel:vkMinStorageBufferOffsetAlignment:VkPhysicalDeviceLimits,$sel:vkMinTexelOffset:VkPhysicalDeviceLimits,$sel:vkMaxTexelOffset:VkPhysicalDeviceLimits2$sel:vkMinTexelGatherOffset:VkPhysicalDeviceLimits2$sel:vkMaxTexelGatherOffset:VkPhysicalDeviceLimits4$sel:vkMinInterpolationOffset:VkPhysicalDeviceLimits4$sel:vkMaxInterpolationOffset:VkPhysicalDeviceLimits=$sel:vkSubPixelInterpolationOffsetBits:VkPhysicalDeviceLimits1$sel:vkMaxFramebufferWidth:VkPhysicalDeviceLimits2$sel:vkMaxFramebufferHeight:VkPhysicalDeviceLimits2$sel:vkMaxFramebufferLayers:VkPhysicalDeviceLimits:$sel:vkFramebufferColorSampleCounts:VkPhysicalDeviceLimits:$sel:vkFramebufferDepthSampleCounts:VkPhysicalDeviceLimits<$sel:vkFramebufferStencilSampleCounts:VkPhysicalDeviceLimitsB$sel:vkFramebufferNoAttachmentsSampleCounts:VkPhysicalDeviceLimits1$sel:vkMaxColorAttachments:VkPhysicalDeviceLimits;$sel:vkSampledImageColorSampleCounts:VkPhysicalDeviceLimits=$sel:vkSampledImageIntegerSampleCounts:VkPhysicalDeviceLimits;$sel:vkSampledImageDepthSampleCounts:VkPhysicalDeviceLimits=$sel:vkSampledImageStencilSampleCounts:VkPhysicalDeviceLimits6$sel:vkStorageImageSampleCounts:VkPhysicalDeviceLimits0$sel:vkMaxSampleMaskWords:VkPhysicalDeviceLimits9$sel:vkTimestampComputeAndGraphics:VkPhysicalDeviceLimits-$sel:vkTimestampPeriod:VkPhysicalDeviceLimits.$sel:vkMaxClipDistances:VkPhysicalDeviceLimits.$sel:vkMaxCullDistances:VkPhysicalDeviceLimits=$sel:vkMaxCombinedClipAndCullDistances:VkPhysicalDeviceLimits5$sel:vkDiscreteQueuePriorities:VkPhysicalDeviceLimits,$sel:vkPointSizeRange:VkPhysicalDeviceLimits,$sel:vkLineWidthRange:VkPhysicalDeviceLimits2$sel:vkPointSizeGranularity:VkPhysicalDeviceLimits2$sel:vkLineWidthGranularity:VkPhysicalDeviceLimits)$sel:vkStrictLines:VkPhysicalDeviceLimits5$sel:vkStandardSampleLocations:VkPhysicalDeviceLimits>$sel:vkOptimalBufferCopyOffsetAlignment:VkPhysicalDeviceLimits@$sel:vkOptimalBufferCopyRowPitchAlignment:VkPhysicalDeviceLimits1$sel:vkNonCoherentAtomSize:VkPhysicalDeviceLimitsE$sel:vkResidencyStandard2DBlockShape:VkPhysicalDeviceSparsePropertiesP$sel:vkResidencyStandard2DMultisampleBlockShape:VkPhysicalDeviceSparsePropertiesE$sel:vkResidencyStandard3DBlockShape:VkPhysicalDeviceSparseProperties?$sel:vkResidencyAlignedMipSize:VkPhysicalDeviceSparsePropertiesB$sel:vkResidencyNonResidentStrict:VkPhysicalDeviceSparseProperties2$sel:vkRobustBufferAccess:VkPhysicalDeviceFeatures3$sel:vkFullDrawIndexUint32:VkPhysicalDeviceFeatures.$sel:vkImageCubeArray:VkPhysicalDeviceFeatures0$sel:vkIndependentBlend:VkPhysicalDeviceFeatures.$sel:vkGeometryShader:VkPhysicalDeviceFeatures2$sel:vkTessellationShader:VkPhysicalDeviceFeatures1$sel:vkSampleRateShading:VkPhysicalDeviceFeatures,$sel:vkDualSrcBlend:VkPhysicalDeviceFeatures'$sel:vkLogicOp:VkPhysicalDeviceFeatures1$sel:vkMultiDrawIndirect:VkPhysicalDeviceFeatures9$sel:vkDrawIndirectFirstInstance:VkPhysicalDeviceFeatures*$sel:vkDepthClamp:VkPhysicalDeviceFeatures.$sel:vkDepthBiasClamp:VkPhysicalDeviceFeatures0$sel:vkFillModeNonSolid:VkPhysicalDeviceFeatures+$sel:vkDepthBounds:VkPhysicalDeviceFeatures)$sel:vkWideLines:VkPhysicalDeviceFeatures+$sel:vkLargePoints:VkPhysicalDeviceFeatures*$sel:vkAlphaToOne:VkPhysicalDeviceFeatures-$sel:vkMultiViewport:VkPhysicalDeviceFeatures1$sel:vkSamplerAnisotropy:VkPhysicalDeviceFeatures6$sel:vkTextureCompressionETC2:VkPhysicalDeviceFeatures:$sel:vkTextureCompressionASTC_LDR:VkPhysicalDeviceFeatures4$sel:vkTextureCompressionBC:VkPhysicalDeviceFeatures5$sel:vkOcclusionQueryPrecise:VkPhysicalDeviceFeatures7$sel:vkPipelineStatisticsQuery:VkPhysicalDeviceFeatures>$sel:vkVertexPipelineStoresAndAtomics:VkPhysicalDeviceFeatures8$sel:vkFragmentStoresAndAtomics:VkPhysicalDeviceFeaturesF$sel:vkShaderTessellationAndGeometryPointSize:VkPhysicalDeviceFeatures9$sel:vkShaderImageGatherExtended:VkPhysicalDeviceFeaturesA$sel:vkShaderStorageImageExtendedFormats:VkPhysicalDeviceFeatures=$sel:vkShaderStorageImageMultisample:VkPhysicalDeviceFeaturesC$sel:vkShaderStorageImageReadWithoutFormat:VkPhysicalDeviceFeaturesD$sel:vkShaderStorageImageWriteWithoutFormat:VkPhysicalDeviceFeaturesG$sel:vkShaderUniformBufferArrayDynamicIndexing:VkPhysicalDeviceFeaturesF$sel:vkShaderSampledImageArrayDynamicIndexing:VkPhysicalDeviceFeaturesG$sel:vkShaderStorageBufferArrayDynamicIndexing:VkPhysicalDeviceFeaturesF$sel:vkShaderStorageImageArrayDynamicIndexing:VkPhysicalDeviceFeatures2$sel:vkShaderClipDistance:VkPhysicalDeviceFeatures2$sel:vkShaderCullDistance:VkPhysicalDeviceFeatures-$sel:vkShaderFloat64:VkPhysicalDeviceFeatures+$sel:vkShaderInt64:VkPhysicalDeviceFeatures+$sel:vkShaderInt16:VkPhysicalDeviceFeatures7$sel:vkShaderResourceResidency:VkPhysicalDeviceFeatures4$sel:vkShaderResourceMinLod:VkPhysicalDeviceFeatures-$sel:vkSparseBinding:VkPhysicalDeviceFeatures5$sel:vkSparseResidencyBuffer:VkPhysicalDeviceFeatures6$sel:vkSparseResidencyImage2D:VkPhysicalDeviceFeatures6$sel:vkSparseResidencyImage3D:VkPhysicalDeviceFeatures7$sel:vkSparseResidency2Samples:VkPhysicalDeviceFeatures7$sel:vkSparseResidency4Samples:VkPhysicalDeviceFeatures7$sel:vkSparseResidency8Samples:VkPhysicalDeviceFeatures8$sel:vkSparseResidency16Samples:VkPhysicalDeviceFeatures6$sel:vkSparseResidencyAliased:VkPhysicalDeviceFeatures7$sel:vkVariableMultisampleRate:VkPhysicalDeviceFeatures0$sel:vkInheritedQueries:VkPhysicalDeviceFeaturesVkImageFormatProperties($sel:vkMaxExtent:VkImageFormatProperties+$sel:vkMaxMipLevels:VkImageFormatProperties-$sel:vkMaxArrayLayers:VkImageFormatProperties+$sel:vkSampleCounts:VkImageFormatProperties.$sel:vkMaxResourceSize:VkImageFormatPropertiesVkFormatProperties.$sel:vkLinearTilingFeatures:VkFormatProperties/$sel:vkOptimalTilingFeatures:VkFormatProperties($sel:vkBufferFeatures:VkFormatProperties VkMemoryHeap$sel:vkSize:VkMemoryHeap$sel:vkFlags:VkMemoryHeap VkMemoryType!$sel:vkPropertyFlags:VkMemoryType$sel:vkHeapIndex:VkMemoryType7$sel:vkMemoryTypeCount:VkPhysicalDeviceMemoryProperties3$sel:vkMemoryTypes:VkPhysicalDeviceMemoryProperties7$sel:vkMemoryHeapCount:VkPhysicalDeviceMemoryProperties3$sel:vkMemoryHeaps:VkPhysicalDeviceMemoryProperties)$sel:vkQueueFlags:VkQueueFamilyProperties)$sel:vkQueueCount:VkQueueFamilyProperties1$sel:vkTimestampValidBits:VkQueueFamilyProperties:$sel:vkMinImageTransferGranularity:VkQueueFamilyProperties!$sel:vkSType:VkInstanceCreateInfo!$sel:vkPNext:VkInstanceCreateInfo!$sel:vkFlags:VkInstanceCreateInfo,$sel:vkPApplicationInfo:VkInstanceCreateInfo-$sel:vkEnabledLayerCount:VkInstanceCreateInfo/$sel:vkPPEnabledLayerNames:VkInstanceCreateInfo1$sel:vkEnabledExtensionCount:VkInstanceCreateInfo3$sel:vkPPEnabledExtensionNames:VkInstanceCreateInfoVkAllocationCallbacks&$sel:vkPUserData:VkAllocationCallbacks*$sel:vkPfnAllocation:VkAllocationCallbacks,$sel:vkPfnReallocation:VkAllocationCallbacks$$sel:vkPfnFree:VkAllocationCallbacks2$sel:vkPfnInternalAllocation:VkAllocationCallbacks,$sel:vkPfnInternalFree:VkAllocationCallbacks$sel:vkSType:VkApplicationInfo$sel:vkPNext:VkApplicationInfo)$sel:vkPApplicationName:VkApplicationInfo+$sel:vkApplicationVersion:VkApplicationInfo$$sel:vkPEngineName:VkApplicationInfo&$sel:vkEngineVersion:VkApplicationInfo#$sel:vkApiVersion:VkApplicationInfoVkPhysicalDeviceProperties,$sel:vkApiVersion:VkPhysicalDeviceProperties/$sel:vkDriverVersion:VkPhysicalDeviceProperties*$sel:vkVendorID:VkPhysicalDeviceProperties*$sel:vkDeviceID:VkPhysicalDeviceProperties,$sel:vkDeviceType:VkPhysicalDeviceProperties,$sel:vkDeviceName:VkPhysicalDeviceProperties3$sel:vkPipelineCacheUUID:VkPhysicalDeviceProperties($sel:vkLimits:VkPhysicalDeviceProperties2$sel:vkSparseProperties:VkPhysicalDeviceProperties VkExtent3D$sel:vkWidth:VkExtent3D$sel:vkHeight:VkExtent3D$sel:vkDepth:VkExtent3DPFN_vkVoidFunctionPFN_vkFreeFunctionPFN_vkAllocationFunctionPFN_vkReallocationFunctionPFN_vkInternalFreeNotification$PFN_vkInternalAllocationNotificationVK_MAX_MEMORY_HEAPSVK_MAX_MEMORY_TYPES VK_UUID_SIZE VK_MAX_PHYSICAL_DEVICE_NAME_SIZEVkSampleCountFlagBitsVkFormatFeatureFlagBitsVkMemoryHeapFlagBitsVkMemoryPropertyFlagBitsVkQueueFlagBitsVkInstanceCreateFlagsVkInternalAllocationTypeVkSystemAllocationScopeVkPhysicalDeviceType VkImageTilingvkGetInstanceProcAddrvkGetDeviceProcAddrvkEnumeratePhysicalDevicesvkDestroyInstanceVK_SAMPLE_COUNT_64_BITVK_SAMPLE_COUNT_32_BITVK_SAMPLE_COUNT_16_BITVK_SAMPLE_COUNT_8_BITVK_SAMPLE_COUNT_4_BITVK_SAMPLE_COUNT_2_BITVK_SAMPLE_COUNT_1_BIT1VK_FORMAT_FEATURE_SAMPLED_IMAGE_FILTER_LINEAR_BITVK_FORMAT_FEATURE_BLIT_DST_BITVK_FORMAT_FEATURE_BLIT_SRC_BIT.VK_FORMAT_FEATURE_DEPTH_STENCIL_ATTACHMENT_BIT,VK_FORMAT_FEATURE_COLOR_ATTACHMENT_BLEND_BIT&VK_FORMAT_FEATURE_COLOR_ATTACHMENT_BIT#VK_FORMAT_FEATURE_VERTEX_BUFFER_BIT1VK_FORMAT_FEATURE_STORAGE_TEXEL_BUFFER_ATOMIC_BIT*VK_FORMAT_FEATURE_STORAGE_TEXEL_BUFFER_BIT*VK_FORMAT_FEATURE_UNIFORM_TEXEL_BUFFER_BIT*VK_FORMAT_FEATURE_STORAGE_IMAGE_ATOMIC_BIT#VK_FORMAT_FEATURE_STORAGE_IMAGE_BIT#VK_FORMAT_FEATURE_SAMPLED_IMAGE_BIT#VK_IMAGE_CREATE_CUBE_COMPATIBLE_BIT"VK_IMAGE_CREATE_MUTABLE_FORMAT_BIT"VK_IMAGE_CREATE_SPARSE_ALIASED_BIT$VK_IMAGE_CREATE_SPARSE_RESIDENCY_BIT"VK_IMAGE_CREATE_SPARSE_BINDING_BIT#VK_IMAGE_USAGE_INPUT_ATTACHMENT_BIT'VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT+VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT#VK_IMAGE_USAGE_COLOR_ATTACHMENT_BITVK_IMAGE_USAGE_STORAGE_BITVK_IMAGE_USAGE_SAMPLED_BITVK_IMAGE_USAGE_TRANSFER_DST_BITVK_IMAGE_USAGE_TRANSFER_SRC_BITVK_MEMORY_HEAP_DEVICE_LOCAL_BIT'VK_MEMORY_PROPERTY_LAZILY_ALLOCATED_BIT"VK_MEMORY_PROPERTY_HOST_CACHED_BIT$VK_MEMORY_PROPERTY_HOST_COHERENT_BIT#VK_MEMORY_PROPERTY_HOST_VISIBLE_BIT#VK_MEMORY_PROPERTY_DEVICE_LOCAL_BITVK_QUEUE_SPARSE_BINDING_BITVK_QUEUE_TRANSFER_BITVK_QUEUE_COMPUTE_BITVK_QUEUE_GRAPHICS_BIT&VK_INTERNAL_ALLOCATION_TYPE_EXECUTABLE#VK_SYSTEM_ALLOCATION_SCOPE_INSTANCE!VK_SYSTEM_ALLOCATION_SCOPE_DEVICE VK_SYSTEM_ALLOCATION_SCOPE_CACHE!VK_SYSTEM_ALLOCATION_SCOPE_OBJECT"VK_SYSTEM_ALLOCATION_SCOPE_COMMANDVK_PHYSICAL_DEVICE_TYPE_CPU#VK_PHYSICAL_DEVICE_TYPE_VIRTUAL_GPU$VK_PHYSICAL_DEVICE_TYPE_DISCRETE_GPU&VK_PHYSICAL_DEVICE_TYPE_INTEGRATED_GPUVK_PHYSICAL_DEVICE_TYPE_OTHERVK_IMAGE_TYPE_3DVK_IMAGE_TYPE_2DVK_IMAGE_TYPE_1DVK_IMAGE_TILING_LINEARVK_IMAGE_TILING_OPTIMAL$fReadVkImageTiling$fShowVkImageTiling$fReadVkImageType$fShowVkImageType$fReadVkPhysicalDeviceType$fShowVkPhysicalDeviceType$fReadVkSystemAllocationScope$fShowVkSystemAllocationScope$fReadVkInternalAllocationType$fShowVkInternalAllocationType$fReadVkInstanceCreateFlags$fShowVkInstanceCreateFlags$fReadVkQueueFlagBits$fShowVkQueueFlagBits$fReadVkMemoryPropertyFlagBits$fShowVkMemoryPropertyFlagBits$fReadVkMemoryHeapFlagBits$fShowVkMemoryHeapFlagBits$fReadVkImageUsageFlagBits$fShowVkImageUsageFlagBits$fReadVkImageCreateFlagBits$fShowVkImageCreateFlagBits$fReadVkFormatFeatureFlagBits$fShowVkFormatFeatureFlagBits$fReadVkSampleCountFlagBits$fShowVkSampleCountFlagBits$fStorableVkExtent3D$fStorableVkApplicationInfo$fStorableVkAllocationCallbacks$fStorableVkInstanceCreateInfo"$fStorableVkPhysicalDeviceFeatures*$fStorableVkPhysicalDeviceSparseProperties!$fStorableVkQueueFamilyProperties$fStorableVkMemoryType$fStorableVkFormatProperties $fStorableVkPhysicalDeviceLimits$$fStorableVkPhysicalDeviceProperties!$fStorableVkImageFormatProperties$fStorableVkMemoryHeap*$fStorableVkPhysicalDeviceMemoryProperties$fEqVkImageTiling$fOrdVkImageTiling$fStorableVkImageTiling$fEqVkImageType$fOrdVkImageType$fStorableVkImageType$fEqVkPhysicalDeviceType$fOrdVkPhysicalDeviceType$fStorableVkPhysicalDeviceType$fEqVkSystemAllocationScope$fOrdVkSystemAllocationScope!$fStorableVkSystemAllocationScope$fEqVkInternalAllocationType$fOrdVkInternalAllocationType"$fStorableVkInternalAllocationType$fEqVkInstanceCreateFlags$fOrdVkInstanceCreateFlags$fStorableVkInstanceCreateFlags$fBitsVkInstanceCreateFlags!$fFiniteBitsVkInstanceCreateFlags$fEqVkQueueFlagBits$fOrdVkQueueFlagBits$fStorableVkQueueFlagBits$fBitsVkQueueFlagBits$fFiniteBitsVkQueueFlagBits$fEqVkMemoryPropertyFlagBits$fOrdVkMemoryPropertyFlagBits"$fStorableVkMemoryPropertyFlagBits$fBitsVkMemoryPropertyFlagBits$$fFiniteBitsVkMemoryPropertyFlagBits$fEqVkMemoryHeapFlagBits$fOrdVkMemoryHeapFlagBits$fStorableVkMemoryHeapFlagBits$fBitsVkMemoryHeapFlagBits $fFiniteBitsVkMemoryHeapFlagBits$fEqVkImageUsageFlagBits$fOrdVkImageUsageFlagBits$fStorableVkImageUsageFlagBits$fBitsVkImageUsageFlagBits $fFiniteBitsVkImageUsageFlagBits$fEqVkImageCreateFlagBits$fOrdVkImageCreateFlagBits$fStorableVkImageCreateFlagBits$fBitsVkImageCreateFlagBits!$fFiniteBitsVkImageCreateFlagBits$fEqVkFormatFeatureFlagBits$fOrdVkFormatFeatureFlagBits!$fStorableVkFormatFeatureFlagBits$fBitsVkFormatFeatureFlagBits#$fFiniteBitsVkFormatFeatureFlagBits$fEqVkSampleCountFlagBits$fOrdVkSampleCountFlagBits$fStorableVkSampleCountFlagBits$fBitsVkSampleCountFlagBits!$fFiniteBitsVkSampleCountFlagBits$fEqVkExtent3D$fShowVkExtent3D$fEqVkApplicationInfo$fShowVkApplicationInfo$fEqVkAllocationCallbacks$fShowVkAllocationCallbacks$fEqVkInstanceCreateInfo$fShowVkInstanceCreateInfo$fEqVkPhysicalDeviceFeatures$fShowVkPhysicalDeviceFeatures$$fEqVkPhysicalDeviceSparseProperties&$fShowVkPhysicalDeviceSparseProperties$fEqVkQueueFamilyProperties$fShowVkQueueFamilyProperties$fEqVkMemoryType$fShowVkMemoryType$fEqVkFormatProperties$fShowVkFormatProperties$fEqVkPhysicalDeviceLimits$fShowVkPhysicalDeviceLimits$fEqVkPhysicalDeviceProperties $fShowVkPhysicalDeviceProperties$fEqVkImageFormatProperties$fShowVkImageFormatProperties$fEqVkMemoryHeap$fShowVkMemoryHeap$$fEqVkPhysicalDeviceMemoryProperties&$fShowVkPhysicalDeviceMemoryPropertiesVkExternalMemoryFeatureFlagsNV!VkExternalMemoryHandleTypeFlagsNV>$sel:vkImageFormatProperties:VkExternalImageFormatPropertiesNV?$sel:vkExternalMemoryFeatures:VkExternalImageFormatPropertiesNVF$sel:vkExportFromImportedHandleTypes:VkExternalImageFormatPropertiesNV>$sel:vkCompatibleHandleTypes:VkExternalImageFormatPropertiesNV!VkExternalMemoryFeatureFlagBitsNV1VK_NV_EXTERNAL_MEMORY_CAPABILITIES_EXTENSION_NAME/VK_NV_EXTERNAL_MEMORY_CAPABILITIES_SPEC_VERSION,VK_EXTERNAL_MEMORY_FEATURE_IMPORTABLE_BIT_NV,VK_EXTERNAL_MEMORY_FEATURE_EXPORTABLE_BIT_NV0VK_EXTERNAL_MEMORY_FEATURE_DEDICATED_ONLY_BIT_NV5VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D11_IMAGE_KMT_BIT_NV1VK_EXTERNAL_MEMORY_HANDLE_TYPE_D3D11_IMAGE_BIT_NV6VK_EXTERNAL_MEMORY_HANDLE_TYPE_OPAQUE_WIN32_KMT_BIT_NV2VK_EXTERNAL_MEMORY_HANDLE_TYPE_OPAQUE_WIN32_BIT_NV*$fReadVkExternalMemoryHandleTypeFlagBitsNV*$fShowVkExternalMemoryHandleTypeFlagBitsNV'$fReadVkExternalMemoryFeatureFlagBitsNV'$fShowVkExternalMemoryFeatureFlagBitsNV+$fStorableVkExternalImageFormatPropertiesNV($fEqVkExternalMemoryHandleTypeFlagBitsNV)$fOrdVkExternalMemoryHandleTypeFlagBitsNV.$fStorableVkExternalMemoryHandleTypeFlagBitsNV*$fBitsVkExternalMemoryHandleTypeFlagBitsNV0$fFiniteBitsVkExternalMemoryHandleTypeFlagBitsNV%$fEqVkExternalMemoryFeatureFlagBitsNV&$fOrdVkExternalMemoryFeatureFlagBitsNV+$fStorableVkExternalMemoryFeatureFlagBitsNV'$fBitsVkExternalMemoryFeatureFlagBitsNV-$fFiniteBitsVkExternalMemoryFeatureFlagBitsNV%$fEqVkExternalImageFormatPropertiesNV'$fShowVkExternalImageFormatPropertiesNV)$sel:vkSType:VkExportMemoryAllocateInfoNV)$sel:vkPNext:VkExportMemoryAllocateInfoNV/$sel:vkHandleTypes:VkExportMemoryAllocateInfoNV.$sel:vkSType:VkExternalMemoryImageCreateInfoNV.$sel:vkPNext:VkExternalMemoryImageCreateInfoNV4$sel:vkHandleTypes:VkExternalMemoryImageCreateInfoNV$VK_NV_EXTERNAL_MEMORY_EXTENSION_NAME"VK_NV_EXTERNAL_MEMORY_SPEC_VERSION0VK_STRUCTURE_TYPE_EXPORT_MEMORY_ALLOCATE_INFO_NV6VK_STRUCTURE_TYPE_EXTERNAL_MEMORY_IMAGE_CREATE_INFO_NV+$fStorableVkExternalMemoryImageCreateInfoNV&$fStorableVkExportMemoryAllocateInfoNV%$fEqVkExternalMemoryImageCreateInfoNV'$fShowVkExternalMemoryImageCreateInfoNV $fEqVkExportMemoryAllocateInfoNV"$fShowVkExportMemoryAllocateInfoNV0$sel:vkSType:VkSamplerReductionModeCreateInfoEXT0$sel:vkPNext:VkSamplerReductionModeCreateInfoEXT8$sel:vkReductionMode:VkSamplerReductionModeCreateInfoEXT=$sel:vkSType:VkPhysicalDeviceSamplerFilterMinmaxPropertiesEXT=$sel:vkPNext:VkPhysicalDeviceSamplerFilterMinmaxPropertiesEXTZ$sel:vkFilterMinmaxSingleComponentFormats:VkPhysicalDeviceSamplerFilterMinmaxPropertiesEXTY$sel:vkFilterMinmaxImageComponentMapping:VkPhysicalDeviceSamplerFilterMinmaxPropertiesEXT+VK_EXT_SAMPLER_FILTER_MINMAX_EXTENSION_NAME)VK_EXT_SAMPLER_FILTER_MINMAX_SPEC_VERSION5VK_FORMAT_FEATURE_SAMPLED_IMAGE_FILTER_MINMAX_BIT_EXT8VK_STRUCTURE_TYPE_SAMPLER_REDUCTION_MODE_CREATE_INFO_EXTFVK_STRUCTURE_TYPE_PHYSICAL_DEVICE_SAMPLER_FILTER_MINMAX_PROPERTIES_EXT!VK_SAMPLER_REDUCTION_MODE_MAX_EXT!VK_SAMPLER_REDUCTION_MODE_MIN_EXT.VK_SAMPLER_REDUCTION_MODE_WEIGHTED_AVERAGE_EXT$fReadVkSamplerReductionModeEXT$fShowVkSamplerReductionModeEXT:$fStorableVkPhysicalDeviceSamplerFilterMinmaxPropertiesEXT-$fStorableVkSamplerReductionModeCreateInfoEXT$fEqVkSamplerReductionModeEXT$fOrdVkSamplerReductionModeEXT#$fStorableVkSamplerReductionModeEXT4$fEqVkPhysicalDeviceSamplerFilterMinmaxPropertiesEXT6$fShowVkPhysicalDeviceSamplerFilterMinmaxPropertiesEXT'$fEqVkSamplerReductionModeCreateInfoEXT)$fShowVkSamplerReductionModeCreateInfoEXTVkDebugReportFlagsEXT/$sel:vkSType:VkDebugReportCallbackCreateInfoEXT/$sel:vkPNext:VkDebugReportCallbackCreateInfoEXT/$sel:vkFlags:VkDebugReportCallbackCreateInfoEXT5$sel:vkPfnCallback:VkDebugReportCallbackCreateInfoEXT3$sel:vkPUserData:VkDebugReportCallbackCreateInfoEXTPFN_vkDebugReportCallbackEXTVkDebugReportFlagBitsEXTVkDebugReportObjectTypeEXT,VK_DEBUG_REPORT_OBJECT_TYPE_DEBUG_REPORT_EXT.VK_STRUCTURE_TYPE_DEBUG_REPORT_CREATE_INFO_EXT"VK_EXT_DEBUG_REPORT_EXTENSION_NAME VK_EXT_DEBUG_REPORT_SPEC_VERSION:VK_DEBUG_REPORT_OBJECT_TYPE_DESCRIPTOR_UPDATE_TEMPLATE_EXT8VK_DEBUG_REPORT_OBJECT_TYPE_SAMPLER_YCBCR_CONVERSION_EXT(VK_OBJECT_TYPE_DEBUG_REPORT_CALLBACK_EXT7VK_STRUCTURE_TYPE_DEBUG_REPORT_CALLBACK_CREATE_INFO_EXTVK_ERROR_VALIDATION_FAILED_EXTVK_DEBUG_REPORT_DEBUG_BIT_EXTVK_DEBUG_REPORT_ERROR_BIT_EXT+VK_DEBUG_REPORT_PERFORMANCE_WARNING_BIT_EXTVK_DEBUG_REPORT_WARNING_BIT_EXT#VK_DEBUG_REPORT_INFORMATION_BIT_EXT4VK_DEBUG_REPORT_OBJECT_TYPE_VALIDATION_CACHE_EXT_EXT$sel:vkExternalSemaphoreFeatures:VkExternalSemaphoreProperties2$sel:vkSType:VkPhysicalDeviceExternalSemaphoreInfo2$sel:vkPNext:VkPhysicalDeviceExternalSemaphoreInfo7$sel:vkHandleType:VkPhysicalDeviceExternalSemaphoreInfo"VkExternalSemaphoreFeatureFlagBits/VK_STRUCTURE_TYPE_EXTERNAL_SEMAPHORE_PROPERTIES9VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_EXTERNAL_SEMAPHORE_INFO,VK_EXTERNAL_SEMAPHORE_FEATURE_IMPORTABLE_BIT,VK_EXTERNAL_SEMAPHORE_FEATURE_EXPORTABLE_BIT-VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_SYNC_FD_BIT1VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_D3D12_FENCE_BIT6VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_OPAQUE_WIN32_KMT_BIT2VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_OPAQUE_WIN32_BIT/VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_OPAQUE_FD_BIT+$fReadVkExternalSemaphoreHandleTypeFlagBits+$fShowVkExternalSemaphoreHandleTypeFlagBits($fReadVkExternalSemaphoreFeatureFlagBits($fShowVkExternalSemaphoreFeatureFlagBits/$fStorableVkPhysicalDeviceExternalSemaphoreInfo'$fStorableVkExternalSemaphoreProperties)$fEqVkExternalSemaphoreHandleTypeFlagBits*$fOrdVkExternalSemaphoreHandleTypeFlagBits/$fStorableVkExternalSemaphoreHandleTypeFlagBits+$fBitsVkExternalSemaphoreHandleTypeFlagBits1$fFiniteBitsVkExternalSemaphoreHandleTypeFlagBits&$fEqVkExternalSemaphoreFeatureFlagBits'$fOrdVkExternalSemaphoreFeatureFlagBits,$fStorableVkExternalSemaphoreFeatureFlagBits($fBitsVkExternalSemaphoreFeatureFlagBits.$fFiniteBitsVkExternalSemaphoreFeatureFlagBits)$fEqVkPhysicalDeviceExternalSemaphoreInfo+$fShowVkPhysicalDeviceExternalSemaphoreInfo!$fEqVkExternalSemaphoreProperties#$fShowVkExternalSemaphoreProperties VkExternalSemaphorePropertiesKHR(VkPhysicalDeviceExternalSemaphoreInfoKHR"VkExternalSemaphoreFeatureFlagsKHR%VkExternalSemaphoreHandleTypeFlagsKHR%VkExternalSemaphoreFeatureFlagBitsKHR(VkExternalSemaphoreHandleTypeFlagBitsKHR0VK_EXTERNAL_SEMAPHORE_FEATURE_IMPORTABLE_BIT_KHR0VK_EXTERNAL_SEMAPHORE_FEATURE_EXPORTABLE_BIT_KHR1VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_SYNC_FD_BIT_KHR5VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_D3D12_FENCE_BIT_KHR:VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_OPAQUE_WIN32_KMT_BIT_KHR6VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_OPAQUE_WIN32_BIT_KHR3VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_OPAQUE_FD_BIT_KHR3VK_STRUCTURE_TYPE_EXTERNAL_SEMAPHORE_PROPERTIES_KHR=VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_EXTERNAL_SEMAPHORE_INFO_KHR5VK_KHR_EXTERNAL_SEMAPHORE_CAPABILITIES_EXTENSION_NAME3VK_KHR_EXTERNAL_SEMAPHORE_CAPABILITIES_SPEC_VERSIONVkSemaphoreImportFlags($sel:vkSType:VkExportSemaphoreCreateInfo($sel:vkPNext:VkExportSemaphoreCreateInfo.$sel:vkHandleTypes:VkExportSemaphoreCreateInfo.VK_STRUCTURE_TYPE_EXPORT_SEMAPHORE_CREATE_INFO!VK_SEMAPHORE_IMPORT_TEMPORARY_BIT$fReadVkSemaphoreImportFlagBits$fShowVkSemaphoreImportFlagBits%$fStorableVkExportSemaphoreCreateInfo$fEqVkSemaphoreImportFlagBits$fOrdVkSemaphoreImportFlagBits#$fStorableVkSemaphoreImportFlagBits$fBitsVkSemaphoreImportFlagBits%$fFiniteBitsVkSemaphoreImportFlagBits$fEqVkExportSemaphoreCreateInfo!$fShowVkExportSemaphoreCreateInfoVkExportSemaphoreCreateInfoKHRVkSemaphoreImportFlagsKHRVkSemaphoreImportFlagBitsKHR%VK_SEMAPHORE_IMPORT_TEMPORARY_BIT_KHR2VK_STRUCTURE_TYPE_EXPORT_SEMAPHORE_CREATE_INFO_KHR(VK_KHR_EXTERNAL_SEMAPHORE_EXTENSION_NAME&VK_KHR_EXTERNAL_SEMAPHORE_SPEC_VERSIONVkExternalFenceFeatureFlagsVkExternalFenceHandleTypeFlags&$sel:vkSType:VkExternalFenceProperties&$sel:vkPNext:VkExternalFenceProperties>$sel:vkExportFromImportedHandleTypes:VkExternalFenceProperties6$sel:vkCompatibleHandleTypes:VkExternalFenceProperties6$sel:vkExternalFenceFeatures:VkExternalFenceProperties.$sel:vkSType:VkPhysicalDeviceExternalFenceInfo.$sel:vkPNext:VkPhysicalDeviceExternalFenceInfo3$sel:vkHandleType:VkPhysicalDeviceExternalFenceInfoVkExternalFenceFeatureFlagBits+VK_STRUCTURE_TYPE_EXTERNAL_FENCE_PROPERTIES5VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_EXTERNAL_FENCE_INFO(VK_EXTERNAL_FENCE_FEATURE_IMPORTABLE_BIT(VK_EXTERNAL_FENCE_FEATURE_EXPORTABLE_BIT)VK_EXTERNAL_FENCE_HANDLE_TYPE_SYNC_FD_BIT2VK_EXTERNAL_FENCE_HANDLE_TYPE_OPAQUE_WIN32_KMT_BIT.VK_EXTERNAL_FENCE_HANDLE_TYPE_OPAQUE_WIN32_BIT+VK_EXTERNAL_FENCE_HANDLE_TYPE_OPAQUE_FD_BIT'$fReadVkExternalFenceHandleTypeFlagBits'$fShowVkExternalFenceHandleTypeFlagBits$$fReadVkExternalFenceFeatureFlagBits$$fShowVkExternalFenceFeatureFlagBits+$fStorableVkPhysicalDeviceExternalFenceInfo#$fStorableVkExternalFenceProperties%$fEqVkExternalFenceHandleTypeFlagBits&$fOrdVkExternalFenceHandleTypeFlagBits+$fStorableVkExternalFenceHandleTypeFlagBits'$fBitsVkExternalFenceHandleTypeFlagBits-$fFiniteBitsVkExternalFenceHandleTypeFlagBits"$fEqVkExternalFenceFeatureFlagBits#$fOrdVkExternalFenceFeatureFlagBits($fStorableVkExternalFenceFeatureFlagBits$$fBitsVkExternalFenceFeatureFlagBits*$fFiniteBitsVkExternalFenceFeatureFlagBits%$fEqVkPhysicalDeviceExternalFenceInfo'$fShowVkPhysicalDeviceExternalFenceInfo$fEqVkExternalFenceProperties$fShowVkExternalFencePropertiesVkExternalFencePropertiesKHR$VkPhysicalDeviceExternalFenceInfoKHRVkExternalFenceFeatureFlagsKHR!VkExternalFenceHandleTypeFlagsKHR!VkExternalFenceFeatureFlagBitsKHR$VkExternalFenceHandleTypeFlagBitsKHR,VK_EXTERNAL_FENCE_FEATURE_IMPORTABLE_BIT_KHR,VK_EXTERNAL_FENCE_FEATURE_EXPORTABLE_BIT_KHR-VK_EXTERNAL_FENCE_HANDLE_TYPE_SYNC_FD_BIT_KHR6VK_EXTERNAL_FENCE_HANDLE_TYPE_OPAQUE_WIN32_KMT_BIT_KHR2VK_EXTERNAL_FENCE_HANDLE_TYPE_OPAQUE_WIN32_BIT_KHR/VK_EXTERNAL_FENCE_HANDLE_TYPE_OPAQUE_FD_BIT_KHR/VK_STRUCTURE_TYPE_EXTERNAL_FENCE_PROPERTIES_KHR9VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_EXTERNAL_FENCE_INFO_KHR1VK_KHR_EXTERNAL_FENCE_CAPABILITIES_EXTENSION_NAME/VK_KHR_EXTERNAL_FENCE_CAPABILITIES_SPEC_VERSIONVkFenceImportFlags$$sel:vkSType:VkExportFenceCreateInfo$$sel:vkPNext:VkExportFenceCreateInfo*$sel:vkHandleTypes:VkExportFenceCreateInfo*VK_STRUCTURE_TYPE_EXPORT_FENCE_CREATE_INFOVK_FENCE_IMPORT_TEMPORARY_BIT$fReadVkFenceImportFlagBits$fShowVkFenceImportFlagBits!$fStorableVkExportFenceCreateInfo$fEqVkFenceImportFlagBits$fOrdVkFenceImportFlagBits$fStorableVkFenceImportFlagBits$fBitsVkFenceImportFlagBits!$fFiniteBitsVkFenceImportFlagBits$fEqVkExportFenceCreateInfo$fShowVkExportFenceCreateInfoVkExportFenceCreateInfoKHRVkFenceImportFlagsKHRVkFenceImportFlagBitsKHR!VK_FENCE_IMPORT_TEMPORARY_BIT_KHR.VK_STRUCTURE_TYPE_EXPORT_FENCE_CREATE_INFO_KHR$VK_KHR_EXTERNAL_FENCE_EXTENSION_NAME"VK_KHR_EXTERNAL_FENCE_SPEC_VERSION*$sel:vkSType:VkDeviceGroupDeviceCreateInfo*$sel:vkPNext:VkDeviceGroupDeviceCreateInfo8$sel:vkPhysicalDeviceCount:VkDeviceGroupDeviceCreateInfo5$sel:vkPPhysicalDevices:VkDeviceGroupDeviceCreateInfo,$sel:vkSType:VkPhysicalDeviceGroupProperties,$sel:vkPNext:VkPhysicalDeviceGroupProperties:$sel:vkPhysicalDeviceCount:VkPhysicalDeviceGroupProperties6$sel:vkPhysicalDevices:VkPhysicalDeviceGroupProperties7$sel:vkSubsetAllocation:VkPhysicalDeviceGroupPropertiesVK_MAX_DEVICE_GROUP_SIZE!VK_MEMORY_HEAP_MULTI_INSTANCE_BIT1VK_STRUCTURE_TYPE_DEVICE_GROUP_DEVICE_CREATE_INFO2VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_GROUP_PROPERTIES)$fStorableVkPhysicalDeviceGroupProperties'$fStorableVkDeviceGroupDeviceCreateInfo#$fEqVkPhysicalDeviceGroupProperties%$fShowVkPhysicalDeviceGroupProperties!$fEqVkDeviceGroupDeviceCreateInfo#$fShowVkDeviceGroupDeviceCreateInfoVK_MAX_DEVICE_GROUP_SIZE_KHR VkDeviceGroupDeviceCreateInfoKHR"VkPhysicalDeviceGroupPropertiesKHR%VK_MEMORY_HEAP_MULTI_INSTANCE_BIT_KHR5VK_STRUCTURE_TYPE_DEVICE_GROUP_DEVICE_CREATE_INFO_KHR6VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_GROUP_PROPERTIES_KHR+VK_KHR_DEVICE_GROUP_CREATION_EXTENSION_NAME)VK_KHR_DEVICE_GROUP_CREATION_SPEC_VERSION%$sel:vkSType:VkShaderModuleCreateInfo%$sel:vkPNext:VkShaderModuleCreateInfo%$sel:vkFlags:VkShaderModuleCreateInfo($sel:vkCodeSize:VkShaderModuleCreateInfo%$sel:vkPCode:VkShaderModuleCreateInfoVkShaderModuleCreateFlags$fReadVkShaderModuleCreateFlags$fShowVkShaderModuleCreateFlags"$fStorableVkShaderModuleCreateInfo$fEqVkShaderModuleCreateFlags$fOrdVkShaderModuleCreateFlags#$fStorableVkShaderModuleCreateFlags$fBitsVkShaderModuleCreateFlags%$fFiniteBitsVkShaderModuleCreateFlags$fEqVkShaderModuleCreateInfo$fShowVkShaderModuleCreateInfoVkPipelineStageFlags$sel:vkSType:VkSubmitInfo$sel:vkPNext:VkSubmitInfo&$sel:vkWaitSemaphoreCount:VkSubmitInfo#$sel:vkPWaitSemaphores:VkSubmitInfo%$sel:vkPWaitDstStageMask:VkSubmitInfo&$sel:vkCommandBufferCount:VkSubmitInfo#$sel:vkPCommandBuffers:VkSubmitInfo($sel:vkSignalSemaphoreCount:VkSubmitInfo%$sel:vkPSignalSemaphores:VkSubmitInfovkQueueWaitIdle"VK_PIPELINE_STAGE_ALL_COMMANDS_BIT"VK_PIPELINE_STAGE_ALL_GRAPHICS_BITVK_PIPELINE_STAGE_HOST_BIT$VK_PIPELINE_STAGE_BOTTOM_OF_PIPE_BITVK_PIPELINE_STAGE_TRANSFER_BIT$VK_PIPELINE_STAGE_COMPUTE_SHADER_BIT-VK_PIPELINE_STAGE_COLOR_ATTACHMENT_OUTPUT_BIT)VK_PIPELINE_STAGE_LATE_FRAGMENT_TESTS_BIT*VK_PIPELINE_STAGE_EARLY_FRAGMENT_TESTS_BIT%VK_PIPELINE_STAGE_FRAGMENT_SHADER_BIT%VK_PIPELINE_STAGE_GEOMETRY_SHADER_BIT4VK_PIPELINE_STAGE_TESSELLATION_EVALUATION_SHADER_BIT1VK_PIPELINE_STAGE_TESSELLATION_CONTROL_SHADER_BIT#VK_PIPELINE_STAGE_VERTEX_SHADER_BIT"VK_PIPELINE_STAGE_VERTEX_INPUT_BIT#VK_PIPELINE_STAGE_DRAW_INDIRECT_BIT!VK_PIPELINE_STAGE_TOP_OF_PIPE_BIT$fReadVkPipelineStageFlagBits$fShowVkPipelineStageFlagBits$fStorableVkSubmitInfo$fEqVkPipelineStageFlagBits$fOrdVkPipelineStageFlagBits!$fStorableVkPipelineStageFlagBits$fBitsVkPipelineStageFlagBits#$fFiniteBitsVkPipelineStageFlagBits$fEqVkSubmitInfo$fShowVkSubmitInfo$$sel:vkSType:VkSemaphoreGetFdInfoKHR$$sel:vkPNext:VkSemaphoreGetFdInfoKHR($sel:vkSemaphore:VkSemaphoreGetFdInfoKHR)$sel:vkHandleType:VkSemaphoreGetFdInfoKHR'$sel:vkSType:VkImportSemaphoreFdInfoKHR'$sel:vkPNext:VkImportSemaphoreFdInfoKHR+$sel:vkSemaphore:VkImportSemaphoreFdInfoKHR'$sel:vkFlags:VkImportSemaphoreFdInfoKHR,$sel:vkHandleType:VkImportSemaphoreFdInfoKHR$$sel:vkFd:VkImportSemaphoreFdInfoKHR+VK_KHR_EXTERNAL_SEMAPHORE_FD_EXTENSION_NAME)VK_KHR_EXTERNAL_SEMAPHORE_FD_SPEC_VERSION+VK_STRUCTURE_TYPE_SEMAPHORE_GET_FD_INFO_KHR.VK_STRUCTURE_TYPE_IMPORT_SEMAPHORE_FD_INFO_KHR$$fStorableVkImportSemaphoreFdInfoKHR!$fStorableVkSemaphoreGetFdInfoKHR$fEqVkImportSemaphoreFdInfoKHR $fShowVkImportSemaphoreFdInfoKHR$fEqVkSemaphoreGetFdInfoKHR$fShowVkSemaphoreGetFdInfoKHR $sel:vkSType:VkFenceGetFdInfoKHR $sel:vkPNext:VkFenceGetFdInfoKHR $sel:vkFence:VkFenceGetFdInfoKHR%$sel:vkHandleType:VkFenceGetFdInfoKHR#$sel:vkSType:VkImportFenceFdInfoKHR#$sel:vkPNext:VkImportFenceFdInfoKHR#$sel:vkFence:VkImportFenceFdInfoKHR#$sel:vkFlags:VkImportFenceFdInfoKHR($sel:vkHandleType:VkImportFenceFdInfoKHR $sel:vkFd:VkImportFenceFdInfoKHR'VK_KHR_EXTERNAL_FENCE_FD_EXTENSION_NAME%VK_KHR_EXTERNAL_FENCE_FD_SPEC_VERSION'VK_STRUCTURE_TYPE_FENCE_GET_FD_INFO_KHR*VK_STRUCTURE_TYPE_IMPORT_FENCE_FD_INFO_KHR $fStorableVkImportFenceFdInfoKHR$fStorableVkFenceGetFdInfoKHR$fEqVkImportFenceFdInfoKHR$fShowVkImportFenceFdInfoKHR$fEqVkFenceGetFdInfoKHR$fShowVkFenceGetFdInfoKHRVkDebugUtilsMessageTypeFlagsEXT#VkDebugUtilsMessageSeverityFlagsEXT1$sel:vkSType:VkDebugUtilsMessengerCallbackDataEXT1$sel:vkPNext:VkDebugUtilsMessengerCallbackDataEXT1$sel:vkFlags:VkDebugUtilsMessengerCallbackDataEXT:$sel:vkPMessageIdName:VkDebugUtilsMessengerCallbackDataEXT;$sel:vkMessageIdNumber:VkDebugUtilsMessengerCallbackDataEXT4$sel:vkPMessage:VkDebugUtilsMessengerCallbackDataEXT;$sel:vkQueueLabelCount:VkDebugUtilsMessengerCallbackDataEXT8$sel:vkPQueueLabels:VkDebugUtilsMessengerCallbackDataEXT<$sel:vkCmdBufLabelCount:VkDebugUtilsMessengerCallbackDataEXT9$sel:vkPCmdBufLabels:VkDebugUtilsMessengerCallbackDataEXT7$sel:vkObjectCount:VkDebugUtilsMessengerCallbackDataEXT4$sel:vkPObjects:VkDebugUtilsMessengerCallbackDataEXT/$sel:vkSType:VkDebugUtilsMessengerCreateInfoEXT/$sel:vkPNext:VkDebugUtilsMessengerCreateInfoEXT/$sel:vkFlags:VkDebugUtilsMessengerCreateInfoEXT9$sel:vkMessageSeverity:VkDebugUtilsMessengerCreateInfoEXT5$sel:vkMessageType:VkDebugUtilsMessengerCreateInfoEXT9$sel:vkPfnUserCallback:VkDebugUtilsMessengerCreateInfoEXT3$sel:vkPUserData:VkDebugUtilsMessengerCreateInfoEXT!$sel:vkSType:VkDebugUtilsLabelEXT!$sel:vkPNext:VkDebugUtilsLabelEXT&$sel:vkPLabelName:VkDebugUtilsLabelEXT!$sel:vkColor:VkDebugUtilsLabelEXT)$sel:vkSType:VkDebugUtilsObjectTagInfoEXT)$sel:vkPNext:VkDebugUtilsObjectTagInfoEXT.$sel:vkObjectType:VkDebugUtilsObjectTagInfoEXT0$sel:vkObjectHandle:VkDebugUtilsObjectTagInfoEXT+$sel:vkTagName:VkDebugUtilsObjectTagInfoEXT+$sel:vkTagSize:VkDebugUtilsObjectTagInfoEXT($sel:vkPTag:VkDebugUtilsObjectTagInfoEXT*$sel:vkSType:VkDebugUtilsObjectNameInfoEXT*$sel:vkPNext:VkDebugUtilsObjectNameInfoEXT/$sel:vkObjectType:VkDebugUtilsObjectNameInfoEXT1$sel:vkObjectHandle:VkDebugUtilsObjectNameInfoEXT0$sel:vkPObjectName:VkDebugUtilsObjectNameInfoEXTVkDebugUtilsMessengerEXT$PFN_vkDebugUtilsMessengerCallbackEXT)VkDebugUtilsMessengerCallbackDataFlagsEXT#VkDebugUtilsMessengerCreateFlagsEXT"VkDebugUtilsMessageTypeFlagBitsEXT&VkDebugUtilsMessageSeverityFlagBitsEXT!VK_EXT_DEBUG_UTILS_EXTENSION_NAMEVK_EXT_DEBUG_UTILS_SPEC_VERSION(VK_OBJECT_TYPE_DEBUG_UTILS_MESSENGER_EXT7VK_STRUCTURE_TYPE_DEBUG_UTILS_MESSENGER_CREATE_INFO_EXT9VK_STRUCTURE_TYPE_DEBUG_UTILS_MESSENGER_CALLBACK_DATA_EXT'VK_STRUCTURE_TYPE_DEBUG_UTILS_LABEL_EXT1VK_STRUCTURE_TYPE_DEBUG_UTILS_OBJECT_TAG_INFO_EXT2VK_STRUCTURE_TYPE_DEBUG_UTILS_OBJECT_NAME_INFO_EXT/VK_DEBUG_UTILS_MESSAGE_TYPE_PERFORMANCE_BIT_EXT.VK_DEBUG_UTILS_MESSAGE_TYPE_VALIDATION_BIT_EXT+VK_DEBUG_UTILS_MESSAGE_TYPE_GENERAL_BIT_EXT-VK_DEBUG_UTILS_MESSAGE_SEVERITY_ERROR_BIT_EXT/VK_DEBUG_UTILS_MESSAGE_SEVERITY_WARNING_BIT_EXT,VK_DEBUG_UTILS_MESSAGE_SEVERITY_INFO_BIT_EXT/VK_DEBUG_UTILS_MESSAGE_SEVERITY_VERBOSE_BIT_EXT,$fReadVkDebugUtilsMessageSeverityFlagBitsEXT,$fShowVkDebugUtilsMessageSeverityFlagBitsEXT($fReadVkDebugUtilsMessageTypeFlagBitsEXT($fShowVkDebugUtilsMessageTypeFlagBitsEXT)$fReadVkDebugUtilsMessengerCreateFlagsEXT)$fShowVkDebugUtilsMessengerCreateFlagsEXT/$fReadVkDebugUtilsMessengerCallbackDataFlagsEXT/$fShowVkDebugUtilsMessengerCallbackDataFlagsEXT'$fStorableVkDebugUtilsObjectNameInfoEXT&$fStorableVkDebugUtilsObjectTagInfoEXT$fStorableVkDebugUtilsLabelEXT.$fStorableVkDebugUtilsMessengerCallbackDataEXT,$fStorableVkDebugUtilsMessengerCreateInfoEXT*$fEqVkDebugUtilsMessageSeverityFlagBitsEXT+$fOrdVkDebugUtilsMessageSeverityFlagBitsEXT0$fStorableVkDebugUtilsMessageSeverityFlagBitsEXT,$fBitsVkDebugUtilsMessageSeverityFlagBitsEXT2$fFiniteBitsVkDebugUtilsMessageSeverityFlagBitsEXT&$fEqVkDebugUtilsMessageTypeFlagBitsEXT'$fOrdVkDebugUtilsMessageTypeFlagBitsEXT,$fStorableVkDebugUtilsMessageTypeFlagBitsEXT($fBitsVkDebugUtilsMessageTypeFlagBitsEXT.$fFiniteBitsVkDebugUtilsMessageTypeFlagBitsEXT'$fEqVkDebugUtilsMessengerCreateFlagsEXT($fOrdVkDebugUtilsMessengerCreateFlagsEXT-$fStorableVkDebugUtilsMessengerCreateFlagsEXT)$fBitsVkDebugUtilsMessengerCreateFlagsEXT/$fFiniteBitsVkDebugUtilsMessengerCreateFlagsEXT-$fEqVkDebugUtilsMessengerCallbackDataFlagsEXT.$fOrdVkDebugUtilsMessengerCallbackDataFlagsEXT3$fStorableVkDebugUtilsMessengerCallbackDataFlagsEXT/$fBitsVkDebugUtilsMessengerCallbackDataFlagsEXT5$fFiniteBitsVkDebugUtilsMessengerCallbackDataFlagsEXT!$fEqVkDebugUtilsObjectNameInfoEXT#$fShowVkDebugUtilsObjectNameInfoEXT $fEqVkDebugUtilsObjectTagInfoEXT"$fShowVkDebugUtilsObjectTagInfoEXT$fEqVkDebugUtilsLabelEXT$fShowVkDebugUtilsLabelEXT($fEqVkDebugUtilsMessengerCallbackDataEXT*$fShowVkDebugUtilsMessengerCallbackDataEXT&$fEqVkDebugUtilsMessengerCreateInfoEXT($fShowVkDebugUtilsMessengerCreateInfoEXT'$sel:vkSType:VkDebugMarkerMarkerInfoEXT'$sel:vkPNext:VkDebugMarkerMarkerInfoEXT-$sel:vkPMarkerName:VkDebugMarkerMarkerInfoEXT'$sel:vkColor:VkDebugMarkerMarkerInfoEXT*$sel:vkSType:VkDebugMarkerObjectTagInfoEXT*$sel:vkPNext:VkDebugMarkerObjectTagInfoEXT/$sel:vkObjectType:VkDebugMarkerObjectTagInfoEXT+$sel:vkObject:VkDebugMarkerObjectTagInfoEXT,$sel:vkTagName:VkDebugMarkerObjectTagInfoEXT,$sel:vkTagSize:VkDebugMarkerObjectTagInfoEXT)$sel:vkPTag:VkDebugMarkerObjectTagInfoEXT+$sel:vkSType:VkDebugMarkerObjectNameInfoEXT+$sel:vkPNext:VkDebugMarkerObjectNameInfoEXT0$sel:vkObjectType:VkDebugMarkerObjectNameInfoEXT,$sel:vkObject:VkDebugMarkerObjectNameInfoEXT1$sel:vkPObjectName:VkDebugMarkerObjectNameInfoEXT"VK_EXT_DEBUG_MARKER_EXTENSION_NAME VK_EXT_DEBUG_MARKER_SPEC_VERSION.VK_STRUCTURE_TYPE_DEBUG_MARKER_MARKER_INFO_EXT2VK_STRUCTURE_TYPE_DEBUG_MARKER_OBJECT_TAG_INFO_EXT3VK_STRUCTURE_TYPE_DEBUG_MARKER_OBJECT_NAME_INFO_EXT($fStorableVkDebugMarkerObjectNameInfoEXT'$fStorableVkDebugMarkerObjectTagInfoEXT$$fStorableVkDebugMarkerMarkerInfoEXT"$fEqVkDebugMarkerObjectNameInfoEXT$$fShowVkDebugMarkerObjectNameInfoEXT!$fEqVkDebugMarkerObjectTagInfoEXT#$fShowVkDebugMarkerObjectTagInfoEXT$fEqVkDebugMarkerMarkerInfoEXT $fShowVkDebugMarkerMarkerInfoEXT"$sel:vkSType:VkSemaphoreCreateInfo"$sel:vkPNext:VkSemaphoreCreateInfo"$sel:vkFlags:VkSemaphoreCreateInfoVkSemaphoreCreateFlags$fReadVkSemaphoreCreateFlags$fShowVkSemaphoreCreateFlags$fStorableVkSemaphoreCreateInfo$fEqVkSemaphoreCreateFlags$fOrdVkSemaphoreCreateFlags $fStorableVkSemaphoreCreateFlags$fBitsVkSemaphoreCreateFlags"$fFiniteBitsVkSemaphoreCreateFlags$fEqVkSemaphoreCreateInfo$fShowVkSemaphoreCreateInfoVkQueryPipelineStatisticFlagsVkQueryResultFlags"$sel:vkSType:VkQueryPoolCreateInfo"$sel:vkPNext:VkQueryPoolCreateInfo"$sel:vkFlags:VkQueryPoolCreateInfo&$sel:vkQueryType:VkQueryPoolCreateInfo'$sel:vkQueryCount:VkQueryPoolCreateInfo/$sel:vkPipelineStatistics:VkQueryPoolCreateInfoVkQueryResultFlagBitsVkQueryPoolCreateFlags VkQueryType:VK_QUERY_PIPELINE_STATISTIC_COMPUTE_SHADER_INVOCATIONS_BITJVK_QUERY_PIPELINE_STATISTIC_TESSELLATION_EVALUATION_SHADER_INVOCATIONS_BITCVK_QUERY_PIPELINE_STATISTIC_TESSELLATION_CONTROL_SHADER_PATCHES_BIT;VK_QUERY_PIPELINE_STATISTIC_FRAGMENT_SHADER_INVOCATIONS_BIT3VK_QUERY_PIPELINE_STATISTIC_CLIPPING_PRIMITIVES_BIT4VK_QUERY_PIPELINE_STATISTIC_CLIPPING_INVOCATIONS_BIT:VK_QUERY_PIPELINE_STATISTIC_GEOMETRY_SHADER_PRIMITIVES_BIT;VK_QUERY_PIPELINE_STATISTIC_GEOMETRY_SHADER_INVOCATIONS_BIT9VK_QUERY_PIPELINE_STATISTIC_VERTEX_SHADER_INVOCATIONS_BIT9VK_QUERY_PIPELINE_STATISTIC_INPUT_ASSEMBLY_PRIMITIVES_BIT7VK_QUERY_PIPELINE_STATISTIC_INPUT_ASSEMBLY_VERTICES_BITVK_QUERY_RESULT_PARTIAL_BIT%VK_QUERY_RESULT_WITH_AVAILABILITY_BITVK_QUERY_RESULT_WAIT_BITVK_QUERY_RESULT_64_BITVK_QUERY_TYPE_TIMESTAMP!VK_QUERY_TYPE_PIPELINE_STATISTICSVK_QUERY_TYPE_OCCLUSION$fReadVkQueryType$fShowVkQueryType$fReadVkQueryPoolCreateFlags$fShowVkQueryPoolCreateFlags$fReadVkQueryResultFlagBits$fShowVkQueryResultFlagBits&$fReadVkQueryPipelineStatisticFlagBits&$fShowVkQueryPipelineStatisticFlagBits$fStorableVkQueryPoolCreateInfo$fEqVkQueryType$fOrdVkQueryType$fStorableVkQueryType$fEqVkQueryPoolCreateFlags$fOrdVkQueryPoolCreateFlags $fStorableVkQueryPoolCreateFlags$fBitsVkQueryPoolCreateFlags"$fFiniteBitsVkQueryPoolCreateFlags$fEqVkQueryResultFlagBits$fOrdVkQueryResultFlagBits$fStorableVkQueryResultFlagBits$fBitsVkQueryResultFlagBits!$fFiniteBitsVkQueryResultFlagBits$$fEqVkQueryPipelineStatisticFlagBits%$fOrdVkQueryPipelineStatisticFlagBits*$fStorableVkQueryPipelineStatisticFlagBits&$fBitsVkQueryPipelineStatisticFlagBits,$fFiniteBitsVkQueryPipelineStatisticFlagBits$fEqVkQueryPoolCreateInfo$fShowVkQueryPoolCreateInfo&$sel:vkSType:VkPipelineCacheCreateInfo&$sel:vkPNext:VkPipelineCacheCreateInfo&$sel:vkFlags:VkPipelineCacheCreateInfo0$sel:vkInitialDataSize:VkPipelineCacheCreateInfo-$sel:vkPInitialData:VkPipelineCacheCreateInfoVkPipelineCacheCreateFlags $fReadVkPipelineCacheCreateFlags $fShowVkPipelineCacheCreateFlags#$fStorableVkPipelineCacheCreateInfo$fEqVkPipelineCacheCreateFlags$fOrdVkPipelineCacheCreateFlags$$fStorableVkPipelineCacheCreateFlags $fBitsVkPipelineCacheCreateFlags&$fFiniteBitsVkPipelineCacheCreateFlags$fEqVkPipelineCacheCreateInfo$fShowVkPipelineCacheCreateInfo VkSampleMaskVkCullModeFlagsVkPipelineCreateFlags)$sel:vkSType:VkGraphicsPipelineCreateInfo)$sel:vkPNext:VkGraphicsPipelineCreateInfo)$sel:vkFlags:VkGraphicsPipelineCreateInfo.$sel:vkStageCount:VkGraphicsPipelineCreateInfo+$sel:vkPStages:VkGraphicsPipelineCreateInfo5$sel:vkPVertexInputState:VkGraphicsPipelineCreateInfo7$sel:vkPInputAssemblyState:VkGraphicsPipelineCreateInfo6$sel:vkPTessellationState:VkGraphicsPipelineCreateInfo2$sel:vkPViewportState:VkGraphicsPipelineCreateInfo7$sel:vkPRasterizationState:VkGraphicsPipelineCreateInfo5$sel:vkPMultisampleState:VkGraphicsPipelineCreateInfo6$sel:vkPDepthStencilState:VkGraphicsPipelineCreateInfo4$sel:vkPColorBlendState:VkGraphicsPipelineCreateInfo1$sel:vkPDynamicState:VkGraphicsPipelineCreateInfo*$sel:vkLayout:VkGraphicsPipelineCreateInfo.$sel:vkRenderPass:VkGraphicsPipelineCreateInfo+$sel:vkSubpass:VkGraphicsPipelineCreateInfo6$sel:vkBasePipelineHandle:VkGraphicsPipelineCreateInfo5$sel:vkBasePipelineIndex:VkGraphicsPipelineCreateInfo2$sel:vkSType:VkPipelineDepthStencilStateCreateInfo2$sel:vkPNext:VkPipelineDepthStencilStateCreateInfo2$sel:vkFlags:VkPipelineDepthStencilStateCreateInfo<$sel:vkDepthTestEnable:VkPipelineDepthStencilStateCreateInfo=$sel:vkDepthWriteEnable:VkPipelineDepthStencilStateCreateInfo;$sel:vkDepthCompareOp:VkPipelineDepthStencilStateCreateInfoB$sel:vkDepthBoundsTestEnable:VkPipelineDepthStencilStateCreateInfo>$sel:vkStencilTestEnable:VkPipelineDepthStencilStateCreateInfo2$sel:vkFront:VkPipelineDepthStencilStateCreateInfo1$sel:vkBack:VkPipelineDepthStencilStateCreateInfo;$sel:vkMinDepthBounds:VkPipelineDepthStencilStateCreateInfo;$sel:vkMaxDepthBounds:VkPipelineDepthStencilStateCreateInfoVkStencilOpState$sel:vkFailOp:VkStencilOpState$sel:vkPassOp:VkStencilOpState#$sel:vkDepthFailOp:VkStencilOpState!$sel:vkCompareOp:VkStencilOpState#$sel:vkCompareMask:VkStencilOpState!$sel:vkWriteMask:VkStencilOpState!$sel:vkReference:VkStencilOpState-$sel:vkSType:VkPipelineDynamicStateCreateInfo-$sel:vkPNext:VkPipelineDynamicStateCreateInfo-$sel:vkFlags:VkPipelineDynamicStateCreateInfo9$sel:vkDynamicStateCount:VkPipelineDynamicStateCreateInfo6$sel:vkPDynamicStates:VkPipelineDynamicStateCreateInfo0$sel:vkSType:VkPipelineColorBlendStateCreateInfo0$sel:vkPNext:VkPipelineColorBlendStateCreateInfo0$sel:vkFlags:VkPipelineColorBlendStateCreateInfo8$sel:vkLogicOpEnable:VkPipelineColorBlendStateCreateInfo2$sel:vkLogicOp:VkPipelineColorBlendStateCreateInfo:$sel:vkAttachmentCount:VkPipelineColorBlendStateCreateInfo7$sel:vkPAttachments:VkPipelineColorBlendStateCreateInfo9$sel:vkBlendConstants:VkPipelineColorBlendStateCreateInfo6$sel:vkBlendEnable:VkPipelineColorBlendAttachmentState>$sel:vkSrcColorBlendFactor:VkPipelineColorBlendAttachmentState>$sel:vkDstColorBlendFactor:VkPipelineColorBlendAttachmentState7$sel:vkColorBlendOp:VkPipelineColorBlendAttachmentState>$sel:vkSrcAlphaBlendFactor:VkPipelineColorBlendAttachmentState>$sel:vkDstAlphaBlendFactor:VkPipelineColorBlendAttachmentState7$sel:vkAlphaBlendOp:VkPipelineColorBlendAttachmentState9$sel:vkColorWriteMask:VkPipelineColorBlendAttachmentState1$sel:vkSType:VkPipelineMultisampleStateCreateInfo1$sel:vkPNext:VkPipelineMultisampleStateCreateInfo1$sel:vkFlags:VkPipelineMultisampleStateCreateInfo@$sel:vkRasterizationSamples:VkPipelineMultisampleStateCreateInfo?$sel:vkSampleShadingEnable:VkPipelineMultisampleStateCreateInfo<$sel:vkMinSampleShading:VkPipelineMultisampleStateCreateInfo7$sel:vkPSampleMask:VkPipelineMultisampleStateCreateInfoA$sel:vkAlphaToCoverageEnable:VkPipelineMultisampleStateCreateInfo<$sel:vkAlphaToOneEnable:VkPipelineMultisampleStateCreateInfo3$sel:vkSType:VkPipelineRasterizationStateCreateInfo3$sel:vkPNext:VkPipelineRasterizationStateCreateInfo3$sel:vkFlags:VkPipelineRasterizationStateCreateInfo>$sel:vkDepthClampEnable:VkPipelineRasterizationStateCreateInfoE$sel:vkRasterizerDiscardEnable:VkPipelineRasterizationStateCreateInfo9$sel:vkPolygonMode:VkPipelineRasterizationStateCreateInfo6$sel:vkCullMode:VkPipelineRasterizationStateCreateInfo7$sel:vkFrontFace:VkPipelineRasterizationStateCreateInfo=$sel:vkDepthBiasEnable:VkPipelineRasterizationStateCreateInfoE$sel:vkDepthBiasConstantFactor:VkPipelineRasterizationStateCreateInfo<$sel:vkDepthBiasClamp:VkPipelineRasterizationStateCreateInfoB$sel:vkDepthBiasSlopeFactor:VkPipelineRasterizationStateCreateInfo7$sel:vkLineWidth:VkPipelineRasterizationStateCreateInfo.$sel:vkSType:VkPipelineViewportStateCreateInfo.$sel:vkPNext:VkPipelineViewportStateCreateInfo.$sel:vkFlags:VkPipelineViewportStateCreateInfo6$sel:vkViewportCount:VkPipelineViewportStateCreateInfo3$sel:vkPViewports:VkPipelineViewportStateCreateInfo5$sel:vkScissorCount:VkPipelineViewportStateCreateInfo2$sel:vkPScissors:VkPipelineViewportStateCreateInfo2$sel:vkSType:VkPipelineTessellationStateCreateInfo2$sel:vkPNext:VkPipelineTessellationStateCreateInfo2$sel:vkFlags:VkPipelineTessellationStateCreateInfo?$sel:vkPatchControlPoints:VkPipelineTessellationStateCreateInfo3$sel:vkSType:VkPipelineInputAssemblyStateCreateInfo3$sel:vkPNext:VkPipelineInputAssemblyStateCreateInfo3$sel:vkFlags:VkPipelineInputAssemblyStateCreateInfo6$sel:vkTopology:VkPipelineInputAssemblyStateCreateInfoD$sel:vkPrimitiveRestartEnable:VkPipelineInputAssemblyStateCreateInfo1$sel:vkSType:VkPipelineVertexInputStateCreateInfo1$sel:vkPNext:VkPipelineVertexInputStateCreateInfo1$sel:vkFlags:VkPipelineVertexInputStateCreateInfoI$sel:vkVertexBindingDescriptionCount:VkPipelineVertexInputStateCreateInfoF$sel:vkPVertexBindingDescriptions:VkPipelineVertexInputStateCreateInfoK$sel:vkVertexAttributeDescriptionCount:VkPipelineVertexInputStateCreateInfoH$sel:vkPVertexAttributeDescriptions:VkPipelineVertexInputStateCreateInfo1$sel:vkLocation:VkVertexInputAttributeDescription0$sel:vkBinding:VkVertexInputAttributeDescription/$sel:vkFormat:VkVertexInputAttributeDescription/$sel:vkOffset:VkVertexInputAttributeDescription.$sel:vkBinding:VkVertexInputBindingDescription-$sel:vkStride:VkVertexInputBindingDescription0$sel:vkInputRate:VkVertexInputBindingDescription($sel:vkSType:VkComputePipelineCreateInfo($sel:vkPNext:VkComputePipelineCreateInfo($sel:vkFlags:VkComputePipelineCreateInfo($sel:vkStage:VkComputePipelineCreateInfo)$sel:vkLayout:VkComputePipelineCreateInfo5$sel:vkBasePipelineHandle:VkComputePipelineCreateInfo4$sel:vkBasePipelineIndex:VkComputePipelineCreateInfo,$sel:vkSType:VkPipelineShaderStageCreateInfo,$sel:vkPNext:VkPipelineShaderStageCreateInfo,$sel:vkFlags:VkPipelineShaderStageCreateInfo,$sel:vkStage:VkPipelineShaderStageCreateInfo-$sel:vkModule:VkPipelineShaderStageCreateInfo,$sel:vkPName:VkPipelineShaderStageCreateInfo:$sel:vkPSpecializationInfo:VkPipelineShaderStageCreateInfoVkSpecializationInfo)$sel:vkMapEntryCount:VkSpecializationInfo'$sel:vkPMapEntries:VkSpecializationInfo$$sel:vkDataSize:VkSpecializationInfo!$sel:vkPData:VkSpecializationInfoVkSpecializationMapEntry*$sel:vkConstantID:VkSpecializationMapEntry&$sel:vkOffset:VkSpecializationMapEntry$$sel:vkSize:VkSpecializationMapEntryVkRect2D$sel:vkOffset:VkRect2D$sel:vkExtent:VkRect2D VkViewport$sel:vkX:VkViewport$sel:vkY:VkViewport$sel:vkWidth:VkViewport$sel:vkHeight:VkViewport$sel:vkMinDepth:VkViewport$sel:vkMaxDepth:VkViewport VkExtent2D$sel:vkWidth:VkExtent2D$sel:vkHeight:VkExtent2D VkOffset2D$sel:vkX:VkOffset2D$sel:vkY:VkOffset2DVkCullModeFlagBitsVkColorComponentFlagBitsVkPipelineCreateFlagBits VkPipelineShaderStageCreateFlags%VkPipelineVertexInputStateCreateFlags'VkPipelineInputAssemblyStateCreateFlags&VkPipelineTessellationStateCreateFlags"VkPipelineViewportStateCreateFlags'VkPipelineRasterizationStateCreateFlags%VkPipelineMultisampleStateCreateFlags$VkPipelineColorBlendStateCreateFlags!VkPipelineDynamicStateCreateFlags&VkPipelineDepthStencilStateCreateFlagsVkVertexInputRate VkStencilOpVkPrimitiveTopology VkLogicOp VkFrontFace VkPolygonModeVkDynamicState VkCompareOp VkBlendOp VkBlendFactorVK_CULL_MODE_FRONT_AND_BACKVK_CULL_MODE_NONEVK_CULL_MODE_BACK_BITVK_CULL_MODE_FRONT_BITVK_COLOR_COMPONENT_A_BITVK_COLOR_COMPONENT_B_BITVK_COLOR_COMPONENT_G_BITVK_COLOR_COMPONENT_R_BIT!VK_PIPELINE_CREATE_DERIVATIVE_BIT(VK_PIPELINE_CREATE_ALLOW_DERIVATIVES_BIT+VK_PIPELINE_CREATE_DISABLE_OPTIMIZATION_BITVK_SHADER_STAGE_ALLVK_SHADER_STAGE_ALL_GRAPHICSVK_SHADER_STAGE_COMPUTE_BITVK_SHADER_STAGE_FRAGMENT_BITVK_SHADER_STAGE_GEOMETRY_BIT+VK_SHADER_STAGE_TESSELLATION_EVALUATION_BIT(VK_SHADER_STAGE_TESSELLATION_CONTROL_BITVK_SHADER_STAGE_VERTEX_BITVK_VERTEX_INPUT_RATE_INSTANCEVK_VERTEX_INPUT_RATE_VERTEX VK_STENCIL_OP_DECREMENT_AND_WRAP VK_STENCIL_OP_INCREMENT_AND_WRAPVK_STENCIL_OP_INVERT!VK_STENCIL_OP_DECREMENT_AND_CLAMP!VK_STENCIL_OP_INCREMENT_AND_CLAMPVK_STENCIL_OP_REPLACEVK_STENCIL_OP_ZEROVK_STENCIL_OP_KEEP VK_PRIMITIVE_TOPOLOGY_PATCH_LIST3VK_PRIMITIVE_TOPOLOGY_TRIANGLE_STRIP_WITH_ADJACENCY2VK_PRIMITIVE_TOPOLOGY_TRIANGLE_LIST_WITH_ADJACENCY/VK_PRIMITIVE_TOPOLOGY_LINE_STRIP_WITH_ADJACENCY.VK_PRIMITIVE_TOPOLOGY_LINE_LIST_WITH_ADJACENCY"VK_PRIMITIVE_TOPOLOGY_TRIANGLE_FAN$VK_PRIMITIVE_TOPOLOGY_TRIANGLE_STRIP#VK_PRIMITIVE_TOPOLOGY_TRIANGLE_LIST VK_PRIMITIVE_TOPOLOGY_LINE_STRIPVK_PRIMITIVE_TOPOLOGY_LINE_LIST VK_PRIMITIVE_TOPOLOGY_POINT_LISTVK_LOGIC_OP_SETVK_LOGIC_OP_NANDVK_LOGIC_OP_OR_INVERTEDVK_LOGIC_OP_COPY_INVERTEDVK_LOGIC_OP_OR_REVERSEVK_LOGIC_OP_INVERTVK_LOGIC_OP_EQUIVALENTVK_LOGIC_OP_NORVK_LOGIC_OP_ORVK_LOGIC_OP_XORVK_LOGIC_OP_NO_OPVK_LOGIC_OP_AND_INVERTEDVK_LOGIC_OP_COPYVK_LOGIC_OP_AND_REVERSEVK_LOGIC_OP_ANDVK_LOGIC_OP_CLEARVK_FRONT_FACE_CLOCKWISEVK_FRONT_FACE_COUNTER_CLOCKWISEVK_POLYGON_MODE_POINTVK_POLYGON_MODE_LINEVK_POLYGON_MODE_FILL"VK_DYNAMIC_STATE_STENCIL_REFERENCE#VK_DYNAMIC_STATE_STENCIL_WRITE_MASK%VK_DYNAMIC_STATE_STENCIL_COMPARE_MASKVK_DYNAMIC_STATE_DEPTH_BOUNDS VK_DYNAMIC_STATE_BLEND_CONSTANTSVK_DYNAMIC_STATE_DEPTH_BIASVK_DYNAMIC_STATE_LINE_WIDTHVK_DYNAMIC_STATE_SCISSORVK_DYNAMIC_STATE_VIEWPORTVK_COMPARE_OP_ALWAYSVK_COMPARE_OP_GREATER_OR_EQUALVK_COMPARE_OP_NOT_EQUALVK_COMPARE_OP_GREATERVK_COMPARE_OP_LESS_OR_EQUALVK_COMPARE_OP_EQUALVK_COMPARE_OP_LESSVK_COMPARE_OP_NEVERVK_BLEND_OP_MAXVK_BLEND_OP_MINVK_BLEND_OP_REVERSE_SUBTRACTVK_BLEND_OP_SUBTRACTVK_BLEND_OP_ADD$VK_BLEND_FACTOR_ONE_MINUS_SRC1_ALPHAVK_BLEND_FACTOR_SRC1_ALPHA$VK_BLEND_FACTOR_ONE_MINUS_SRC1_COLORVK_BLEND_FACTOR_SRC1_COLOR"VK_BLEND_FACTOR_SRC_ALPHA_SATURATE(VK_BLEND_FACTOR_ONE_MINUS_CONSTANT_ALPHAVK_BLEND_FACTOR_CONSTANT_ALPHA(VK_BLEND_FACTOR_ONE_MINUS_CONSTANT_COLORVK_BLEND_FACTOR_CONSTANT_COLOR#VK_BLEND_FACTOR_ONE_MINUS_DST_ALPHAVK_BLEND_FACTOR_DST_ALPHA#VK_BLEND_FACTOR_ONE_MINUS_SRC_ALPHAVK_BLEND_FACTOR_SRC_ALPHA#VK_BLEND_FACTOR_ONE_MINUS_DST_COLORVK_BLEND_FACTOR_DST_COLOR#VK_BLEND_FACTOR_ONE_MINUS_SRC_COLORVK_BLEND_FACTOR_SRC_COLORVK_BLEND_FACTOR_ONEVK_BLEND_FACTOR_ZERO$fReadVkBlendFactor$fShowVkBlendFactor$fReadVkBlendOp$fShowVkBlendOp$fReadVkCompareOp$fShowVkCompareOp$fReadVkDynamicState$fShowVkDynamicState$fReadVkPolygonMode$fShowVkPolygonMode$fReadVkFrontFace$fShowVkFrontFace$fReadVkLogicOp$fShowVkLogicOp$fReadVkPrimitiveTopology$fShowVkPrimitiveTopology$fReadVkStencilOp$fShowVkStencilOp$fReadVkVertexInputRate$fShowVkVertexInputRate,$fReadVkPipelineDepthStencilStateCreateFlags,$fShowVkPipelineDepthStencilStateCreateFlags'$fReadVkPipelineDynamicStateCreateFlags'$fShowVkPipelineDynamicStateCreateFlags*$fReadVkPipelineColorBlendStateCreateFlags*$fShowVkPipelineColorBlendStateCreateFlags+$fReadVkPipelineMultisampleStateCreateFlags+$fShowVkPipelineMultisampleStateCreateFlags-$fReadVkPipelineRasterizationStateCreateFlags-$fShowVkPipelineRasterizationStateCreateFlags($fReadVkPipelineViewportStateCreateFlags($fShowVkPipelineViewportStateCreateFlags,$fReadVkPipelineTessellationStateCreateFlags,$fShowVkPipelineTessellationStateCreateFlags-$fReadVkPipelineInputAssemblyStateCreateFlags-$fShowVkPipelineInputAssemblyStateCreateFlags+$fReadVkPipelineVertexInputStateCreateFlags+$fShowVkPipelineVertexInputStateCreateFlags&$fReadVkPipelineShaderStageCreateFlags&$fShowVkPipelineShaderStageCreateFlags$fReadVkShaderStageFlagBits$fShowVkShaderStageFlagBits$fReadVkPipelineCreateFlagBits$fShowVkPipelineCreateFlagBits$fReadVkColorComponentFlagBits$fShowVkColorComponentFlagBits$fReadVkCullModeFlagBits$fShowVkCullModeFlagBits$fStorableVkOffset2D$fStorableVkExtent2D$fStorableVkViewport$fStorableVkRect2D"$fStorableVkSpecializationMapEntry$fStorableVkSpecializationInfo)$fStorableVkPipelineShaderStageCreateInfo)$fStorableVkVertexInputBindingDescription+$fStorableVkVertexInputAttributeDescription.$fStorableVkPipelineVertexInputStateCreateInfo0$fStorableVkPipelineInputAssemblyStateCreateInfo/$fStorableVkPipelineTessellationStateCreateInfo+$fStorableVkPipelineViewportStateCreateInfo*$fStorableVkPipelineDynamicStateCreateInfo$fStorableVkStencilOpState/$fStorableVkPipelineDepthStencilStateCreateInfo%$fStorableVkComputePipelineCreateInfo-$fStorableVkPipelineColorBlendAttachmentState-$fStorableVkPipelineColorBlendStateCreateInfo0$fStorableVkPipelineRasterizationStateCreateInfo.$fStorableVkPipelineMultisampleStateCreateInfo&$fStorableVkGraphicsPipelineCreateInfo$fEqVkBlendFactor$fOrdVkBlendFactor$fStorableVkBlendFactor $fEqVkBlendOp$fOrdVkBlendOp$fStorableVkBlendOp$fEqVkCompareOp$fOrdVkCompareOp$fStorableVkCompareOp$fEqVkDynamicState$fOrdVkDynamicState$fStorableVkDynamicState$fEqVkPolygonMode$fOrdVkPolygonMode$fStorableVkPolygonMode$fEqVkFrontFace$fOrdVkFrontFace$fStorableVkFrontFace $fEqVkLogicOp$fOrdVkLogicOp$fStorableVkLogicOp$fEqVkPrimitiveTopology$fOrdVkPrimitiveTopology$fStorableVkPrimitiveTopology$fEqVkStencilOp$fOrdVkStencilOp$fStorableVkStencilOp$fEqVkVertexInputRate$fOrdVkVertexInputRate$fStorableVkVertexInputRate*$fEqVkPipelineDepthStencilStateCreateFlags+$fOrdVkPipelineDepthStencilStateCreateFlags0$fStorableVkPipelineDepthStencilStateCreateFlags,$fBitsVkPipelineDepthStencilStateCreateFlags2$fFiniteBitsVkPipelineDepthStencilStateCreateFlags%$fEqVkPipelineDynamicStateCreateFlags&$fOrdVkPipelineDynamicStateCreateFlags+$fStorableVkPipelineDynamicStateCreateFlags'$fBitsVkPipelineDynamicStateCreateFlags-$fFiniteBitsVkPipelineDynamicStateCreateFlags($fEqVkPipelineColorBlendStateCreateFlags)$fOrdVkPipelineColorBlendStateCreateFlags.$fStorableVkPipelineColorBlendStateCreateFlags*$fBitsVkPipelineColorBlendStateCreateFlags0$fFiniteBitsVkPipelineColorBlendStateCreateFlags)$fEqVkPipelineMultisampleStateCreateFlags*$fOrdVkPipelineMultisampleStateCreateFlags/$fStorableVkPipelineMultisampleStateCreateFlags+$fBitsVkPipelineMultisampleStateCreateFlags1$fFiniteBitsVkPipelineMultisampleStateCreateFlags+$fEqVkPipelineRasterizationStateCreateFlags,$fOrdVkPipelineRasterizationStateCreateFlags1$fStorableVkPipelineRasterizationStateCreateFlags-$fBitsVkPipelineRasterizationStateCreateFlags3$fFiniteBitsVkPipelineRasterizationStateCreateFlags&$fEqVkPipelineViewportStateCreateFlags'$fOrdVkPipelineViewportStateCreateFlags,$fStorableVkPipelineViewportStateCreateFlags($fBitsVkPipelineViewportStateCreateFlags.$fFiniteBitsVkPipelineViewportStateCreateFlags*$fEqVkPipelineTessellationStateCreateFlags+$fOrdVkPipelineTessellationStateCreateFlags0$fStorableVkPipelineTessellationStateCreateFlags,$fBitsVkPipelineTessellationStateCreateFlags2$fFiniteBitsVkPipelineTessellationStateCreateFlags+$fEqVkPipelineInputAssemblyStateCreateFlags,$fOrdVkPipelineInputAssemblyStateCreateFlags1$fStorableVkPipelineInputAssemblyStateCreateFlags-$fBitsVkPipelineInputAssemblyStateCreateFlags3$fFiniteBitsVkPipelineInputAssemblyStateCreateFlags)$fEqVkPipelineVertexInputStateCreateFlags*$fOrdVkPipelineVertexInputStateCreateFlags/$fStorableVkPipelineVertexInputStateCreateFlags+$fBitsVkPipelineVertexInputStateCreateFlags1$fFiniteBitsVkPipelineVertexInputStateCreateFlags$$fEqVkPipelineShaderStageCreateFlags%$fOrdVkPipelineShaderStageCreateFlags*$fStorableVkPipelineShaderStageCreateFlags&$fBitsVkPipelineShaderStageCreateFlags,$fFiniteBitsVkPipelineShaderStageCreateFlags$fEqVkShaderStageFlagBits$fOrdVkShaderStageFlagBits$fStorableVkShaderStageFlagBits$fBitsVkShaderStageFlagBits!$fFiniteBitsVkShaderStageFlagBits$fEqVkPipelineCreateFlagBits$fOrdVkPipelineCreateFlagBits"$fStorableVkPipelineCreateFlagBits$fBitsVkPipelineCreateFlagBits$$fFiniteBitsVkPipelineCreateFlagBits$fEqVkColorComponentFlagBits$fOrdVkColorComponentFlagBits"$fStorableVkColorComponentFlagBits$fBitsVkColorComponentFlagBits$$fFiniteBitsVkColorComponentFlagBits$fEqVkCullModeFlagBits$fOrdVkCullModeFlagBits$fStorableVkCullModeFlagBits$fBitsVkCullModeFlagBits$fFiniteBitsVkCullModeFlagBits$fEqVkOffset2D$fShowVkOffset2D$fEqVkExtent2D$fShowVkExtent2D$fEqVkViewport$fShowVkViewport $fEqVkRect2D$fShowVkRect2D$fEqVkSpecializationMapEntry$fShowVkSpecializationMapEntry$fEqVkSpecializationInfo$fShowVkSpecializationInfo#$fEqVkPipelineShaderStageCreateInfo%$fShowVkPipelineShaderStageCreateInfo#$fEqVkVertexInputBindingDescription%$fShowVkVertexInputBindingDescription%$fEqVkVertexInputAttributeDescription'$fShowVkVertexInputAttributeDescription($fEqVkPipelineVertexInputStateCreateInfo*$fShowVkPipelineVertexInputStateCreateInfo*$fEqVkPipelineInputAssemblyStateCreateInfo,$fShowVkPipelineInputAssemblyStateCreateInfo)$fEqVkPipelineTessellationStateCreateInfo+$fShowVkPipelineTessellationStateCreateInfo%$fEqVkPipelineViewportStateCreateInfo'$fShowVkPipelineViewportStateCreateInfo$$fEqVkPipelineDynamicStateCreateInfo&$fShowVkPipelineDynamicStateCreateInfo$fEqVkStencilOpState$fShowVkStencilOpState)$fEqVkPipelineDepthStencilStateCreateInfo+$fShowVkPipelineDepthStencilStateCreateInfo$fEqVkComputePipelineCreateInfo!$fShowVkComputePipelineCreateInfo'$fEqVkPipelineColorBlendAttachmentState)$fShowVkPipelineColorBlendAttachmentState'$fEqVkPipelineColorBlendStateCreateInfo)$fShowVkPipelineColorBlendStateCreateInfo*$fEqVkPipelineRasterizationStateCreateInfo,$fShowVkPipelineRasterizationStateCreateInfo($fEqVkPipelineMultisampleStateCreateInfo*$fShowVkPipelineMultisampleStateCreateInfo $fEqVkGraphicsPipelineCreateInfo"$fShowVkGraphicsPipelineCreateInfo#VK_NV_FILL_RECTANGLE_EXTENSION_NAME!VK_NV_FILL_RECTANGLE_SPEC_VERSION!VK_POLYGON_MODE_FILL_RECTANGLE_NV8$sel:vkSType:VkPipelineViewportWScalingStateCreateInfoNV8$sel:vkPNext:VkPipelineViewportWScalingStateCreateInfoNVI$sel:vkViewportWScalingEnable:VkPipelineViewportWScalingStateCreateInfoNV@$sel:vkViewportCount:VkPipelineViewportWScalingStateCreateInfoNVE$sel:vkPViewportWScalings:VkPipelineViewportWScalingStateCreateInfoNV"$sel:vkXcoeff:VkViewportWScalingNV"$sel:vkYcoeff:VkViewportWScalingNV)VK_NV_CLIP_SPACE_W_SCALING_EXTENSION_NAME'VK_NV_CLIP_SPACE_W_SCALING_SPEC_VERSIONBVK_STRUCTURE_TYPE_PIPELINE_VIEWPORT_W_SCALING_STATE_CREATE_INFO_NV&VK_DYNAMIC_STATE_VIEWPORT_W_SCALING_NV$fStorableVkViewportWScalingNV5$fStorableVkPipelineViewportWScalingStateCreateInfoNV$fEqVkViewportWScalingNV$fShowVkViewportWScalingNV/$fEqVkPipelineViewportWScalingStateCreateInfoNV1$fShowVkPipelineViewportWScalingStateCreateInfoNVVkSurfaceTransformFlagsKHRVkCompositeAlphaFlagsKHR $sel:vkFormat:VkSurfaceFormatKHR$$sel:vkColorSpace:VkSurfaceFormatKHR-$sel:vkMinImageCount:VkSurfaceCapabilitiesKHR-$sel:vkMaxImageCount:VkSurfaceCapabilitiesKHR-$sel:vkCurrentExtent:VkSurfaceCapabilitiesKHR.$sel:vkMinImageExtent:VkSurfaceCapabilitiesKHR.$sel:vkMaxImageExtent:VkSurfaceCapabilitiesKHR3$sel:vkMaxImageArrayLayers:VkSurfaceCapabilitiesKHR3$sel:vkSupportedTransforms:VkSurfaceCapabilitiesKHR0$sel:vkCurrentTransform:VkSurfaceCapabilitiesKHR7$sel:vkSupportedCompositeAlpha:VkSurfaceCapabilitiesKHR3$sel:vkSupportedUsageFlags:VkSurfaceCapabilitiesKHRVkSurfaceTransformFlagBitsKHRVkCompositeAlphaFlagBitsKHRVkPresentModeKHRVkColorSpaceKHR VK_COLORSPACE_SRGB_NONLINEAR_KHRVK_KHR_SURFACE_EXTENSION_NAMEVK_KHR_SURFACE_SPEC_VERSIONVK_OBJECT_TYPE_SURFACE_KHR!VK_ERROR_NATIVE_WINDOW_IN_USE_KHRVK_ERROR_SURFACE_LOST_KHR$VK_SURFACE_TRANSFORM_INHERIT_BIT_KHR9VK_SURFACE_TRANSFORM_HORIZONTAL_MIRROR_ROTATE_270_BIT_KHR9VK_SURFACE_TRANSFORM_HORIZONTAL_MIRROR_ROTATE_180_BIT_KHR8VK_SURFACE_TRANSFORM_HORIZONTAL_MIRROR_ROTATE_90_BIT_KHR.VK_SURFACE_TRANSFORM_HORIZONTAL_MIRROR_BIT_KHR'VK_SURFACE_TRANSFORM_ROTATE_270_BIT_KHR'VK_SURFACE_TRANSFORM_ROTATE_180_BIT_KHR&VK_SURFACE_TRANSFORM_ROTATE_90_BIT_KHR%VK_SURFACE_TRANSFORM_IDENTITY_BIT_KHR"VK_COMPOSITE_ALPHA_INHERIT_BIT_KHR*VK_COMPOSITE_ALPHA_POST_MULTIPLIED_BIT_KHR)VK_COMPOSITE_ALPHA_PRE_MULTIPLIED_BIT_KHR!VK_COMPOSITE_ALPHA_OPAQUE_BIT_KHR VK_PRESENT_MODE_FIFO_RELAXED_KHRVK_PRESENT_MODE_FIFO_KHRVK_PRESENT_MODE_MAILBOX_KHRVK_PRESENT_MODE_IMMEDIATE_KHR!VK_COLOR_SPACE_SRGB_NONLINEAR_KHR$fReadVkColorSpaceKHR$fShowVkColorSpaceKHR$fReadVkPresentModeKHR$fShowVkPresentModeKHR!$fReadVkCompositeAlphaFlagBitsKHR!$fShowVkCompositeAlphaFlagBitsKHR#$fReadVkSurfaceTransformFlagBitsKHR#$fShowVkSurfaceTransformFlagBitsKHR$fStorableVkSurfaceFormatKHR"$fStorableVkSurfaceCapabilitiesKHR$fEqVkColorSpaceKHR$fOrdVkColorSpaceKHR$fStorableVkColorSpaceKHR$fEqVkPresentModeKHR$fOrdVkPresentModeKHR$fStorableVkPresentModeKHR$fEqVkCompositeAlphaFlagBitsKHR $fOrdVkCompositeAlphaFlagBitsKHR%$fStorableVkCompositeAlphaFlagBitsKHR!$fBitsVkCompositeAlphaFlagBitsKHR'$fFiniteBitsVkCompositeAlphaFlagBitsKHR!$fEqVkSurfaceTransformFlagBitsKHR"$fOrdVkSurfaceTransformFlagBitsKHR'$fStorableVkSurfaceTransformFlagBitsKHR#$fBitsVkSurfaceTransformFlagBitsKHR)$fFiniteBitsVkSurfaceTransformFlagBitsKHR$fEqVkSurfaceFormatKHR$fShowVkSurfaceFormatKHR$fEqVkSurfaceCapabilitiesKHR$fShowVkSurfaceCapabilitiesKHR$$sel:vkSType:VkViSurfaceCreateInfoNN$$sel:vkPNext:VkViSurfaceCreateInfoNN$$sel:vkFlags:VkViSurfaceCreateInfoNN%$sel:vkWindow:VkViSurfaceCreateInfoNNVkViSurfaceCreateFlagsNNVK_NN_VI_SURFACE_EXTENSION_NAMEVK_NN_VI_SURFACE_SPEC_VERSION+VK_STRUCTURE_TYPE_VI_SURFACE_CREATE_INFO_NN$fReadVkViSurfaceCreateFlagsNN$fShowVkViSurfaceCreateFlagsNN!$fStorableVkViSurfaceCreateInfoNN$fEqVkViSurfaceCreateFlagsNN$fOrdVkViSurfaceCreateFlagsNN"$fStorableVkViSurfaceCreateFlagsNN$fBitsVkViSurfaceCreateFlagsNN$$fFiniteBitsVkViSurfaceCreateFlagsNN$fEqVkViSurfaceCreateInfoNN$fShowVkViSurfaceCreateInfoNN($sel:vkSType:VkMacOSSurfaceCreateInfoMVK($sel:vkPNext:VkMacOSSurfaceCreateInfoMVK($sel:vkFlags:VkMacOSSurfaceCreateInfoMVK($sel:vkPView:VkMacOSSurfaceCreateInfoMVKVkMacOSSurfaceCreateFlagsMVK#VK_MVK_MACOS_SURFACE_EXTENSION_NAME!VK_MVK_MACOS_SURFACE_SPEC_VERSION/VK_STRUCTURE_TYPE_MACOS_SURFACE_CREATE_INFO_MVK"$fReadVkMacOSSurfaceCreateFlagsMVK"$fShowVkMacOSSurfaceCreateFlagsMVK%$fStorableVkMacOSSurfaceCreateInfoMVK $fEqVkMacOSSurfaceCreateFlagsMVK!$fOrdVkMacOSSurfaceCreateFlagsMVK&$fStorableVkMacOSSurfaceCreateFlagsMVK"$fBitsVkMacOSSurfaceCreateFlagsMVK($fFiniteBitsVkMacOSSurfaceCreateFlagsMVK$fEqVkMacOSSurfaceCreateInfoMVK!$fShowVkMacOSSurfaceCreateInfoMVK&$sel:vkSType:VkIOSSurfaceCreateInfoMVK&$sel:vkPNext:VkIOSSurfaceCreateInfoMVK&$sel:vkFlags:VkIOSSurfaceCreateInfoMVK&$sel:vkPView:VkIOSSurfaceCreateInfoMVKVkIOSSurfaceCreateFlagsMVK!VK_MVK_IOS_SURFACE_EXTENSION_NAMEVK_MVK_IOS_SURFACE_SPEC_VERSION-VK_STRUCTURE_TYPE_IOS_SURFACE_CREATE_INFO_MVK $fReadVkIOSSurfaceCreateFlagsMVK $fShowVkIOSSurfaceCreateFlagsMVK#$fStorableVkIOSSurfaceCreateInfoMVK$fEqVkIOSSurfaceCreateFlagsMVK$fOrdVkIOSSurfaceCreateFlagsMVK$$fStorableVkIOSSurfaceCreateFlagsMVK $fBitsVkIOSSurfaceCreateFlagsMVK&$fFiniteBitsVkIOSSurfaceCreateFlagsMVK$fEqVkIOSSurfaceCreateInfoMVK$fShowVkIOSSurfaceCreateInfoMVK'$sel:vkSType:VkXlibSurfaceCreateInfoKHR'$sel:vkPNext:VkXlibSurfaceCreateInfoKHR'$sel:vkFlags:VkXlibSurfaceCreateInfoKHR%$sel:vkDpy:VkXlibSurfaceCreateInfoKHR($sel:vkWindow:VkXlibSurfaceCreateInfoKHRVkXlibSurfaceCreateFlagsKHRWindowVisualIDDisplay"VK_KHR_XLIB_SURFACE_EXTENSION_NAME VK_KHR_XLIB_SURFACE_SPEC_VERSION.VK_STRUCTURE_TYPE_XLIB_SURFACE_CREATE_INFO_KHR!$fReadVkXlibSurfaceCreateFlagsKHR!$fShowVkXlibSurfaceCreateFlagsKHR$$fStorableVkXlibSurfaceCreateInfoKHR$fEqVkXlibSurfaceCreateFlagsKHR $fOrdVkXlibSurfaceCreateFlagsKHR%$fStorableVkXlibSurfaceCreateFlagsKHR!$fBitsVkXlibSurfaceCreateFlagsKHR'$fFiniteBitsVkXlibSurfaceCreateFlagsKHR$fEqVkXlibSurfaceCreateInfoKHR $fShowVkXlibSurfaceCreateInfoKHR&$sel:vkSType:VkXcbSurfaceCreateInfoKHR&$sel:vkPNext:VkXcbSurfaceCreateInfoKHR&$sel:vkFlags:VkXcbSurfaceCreateInfoKHR+$sel:vkConnection:VkXcbSurfaceCreateInfoKHR'$sel:vkWindow:VkXcbSurfaceCreateInfoKHRVkXcbSurfaceCreateFlagsKHR Xcb_window_tXcb_visualid_tXcb_connection_t!VK_KHR_XCB_SURFACE_EXTENSION_NAMEVK_KHR_XCB_SURFACE_SPEC_VERSION-VK_STRUCTURE_TYPE_XCB_SURFACE_CREATE_INFO_KHR $fReadVkXcbSurfaceCreateFlagsKHR $fShowVkXcbSurfaceCreateFlagsKHR#$fStorableVkXcbSurfaceCreateInfoKHR$fEqVkXcbSurfaceCreateFlagsKHR$fOrdVkXcbSurfaceCreateFlagsKHR$$fStorableVkXcbSurfaceCreateFlagsKHR $fBitsVkXcbSurfaceCreateFlagsKHR&$fFiniteBitsVkXcbSurfaceCreateFlagsKHR$fEqVkXcbSurfaceCreateInfoKHR$fShowVkXcbSurfaceCreateInfoKHR($sel:vkSType:VkWin32SurfaceCreateInfoKHR($sel:vkPNext:VkWin32SurfaceCreateInfoKHR($sel:vkFlags:VkWin32SurfaceCreateInfoKHR,$sel:vkHinstance:VkWin32SurfaceCreateInfoKHR'$sel:vkHwnd:VkWin32SurfaceCreateInfoKHRVkWin32SurfaceCreateFlagsKHRHWND HINSTANCE#VK_KHR_WIN32_SURFACE_EXTENSION_NAME!VK_KHR_WIN32_SURFACE_SPEC_VERSION/VK_STRUCTURE_TYPE_WIN32_SURFACE_CREATE_INFO_KHR"$fReadVkWin32SurfaceCreateFlagsKHR"$fShowVkWin32SurfaceCreateFlagsKHR%$fStorableVkWin32SurfaceCreateInfoKHR $fEqVkWin32SurfaceCreateFlagsKHR!$fOrdVkWin32SurfaceCreateFlagsKHR&$fStorableVkWin32SurfaceCreateFlagsKHR"$fBitsVkWin32SurfaceCreateFlagsKHR($fFiniteBitsVkWin32SurfaceCreateFlagsKHR$fEqVkWin32SurfaceCreateInfoKHR!$fShowVkWin32SurfaceCreateInfoKHR*$sel:vkSType:VkWaylandSurfaceCreateInfoKHR*$sel:vkPNext:VkWaylandSurfaceCreateInfoKHR*$sel:vkFlags:VkWaylandSurfaceCreateInfoKHR,$sel:vkDisplay:VkWaylandSurfaceCreateInfoKHR,$sel:vkSurface:VkWaylandSurfaceCreateInfoKHRVkWaylandSurfaceCreateFlagsKHR Wl_surface Wl_display%VK_KHR_WAYLAND_SURFACE_EXTENSION_NAME#VK_KHR_WAYLAND_SURFACE_SPEC_VERSION1VK_STRUCTURE_TYPE_WAYLAND_SURFACE_CREATE_INFO_KHR$$fReadVkWaylandSurfaceCreateFlagsKHR$$fShowVkWaylandSurfaceCreateFlagsKHR'$fStorableVkWaylandSurfaceCreateInfoKHR"$fEqVkWaylandSurfaceCreateFlagsKHR#$fOrdVkWaylandSurfaceCreateFlagsKHR($fStorableVkWaylandSurfaceCreateFlagsKHR$$fBitsVkWaylandSurfaceCreateFlagsKHR*$fFiniteBitsVkWaylandSurfaceCreateFlagsKHR!$fEqVkWaylandSurfaceCreateInfoKHR#$fShowVkWaylandSurfaceCreateInfoKHR&$sel:vkSType:VkMirSurfaceCreateInfoKHR&$sel:vkPNext:VkMirSurfaceCreateInfoKHR&$sel:vkFlags:VkMirSurfaceCreateInfoKHR+$sel:vkConnection:VkMirSurfaceCreateInfoKHR+$sel:vkMirSurface:VkMirSurfaceCreateInfoKHRVkMirSurfaceCreateFlagsKHR MirSurface MirConnection!VK_KHR_MIR_SURFACE_EXTENSION_NAMEVK_KHR_MIR_SURFACE_SPEC_VERSION-VK_STRUCTURE_TYPE_MIR_SURFACE_CREATE_INFO_KHR $fReadVkMirSurfaceCreateFlagsKHR $fShowVkMirSurfaceCreateFlagsKHR#$fStorableVkMirSurfaceCreateInfoKHR$fEqVkMirSurfaceCreateFlagsKHR$fOrdVkMirSurfaceCreateFlagsKHR$$fStorableVkMirSurfaceCreateFlagsKHR $fBitsVkMirSurfaceCreateFlagsKHR&$fFiniteBitsVkMirSurfaceCreateFlagsKHR$fEqVkMirSurfaceCreateInfoKHR$fShowVkMirSurfaceCreateInfoKHR $sel:vkSType:VkSurfaceFormat2KHR $sel:vkPNext:VkSurfaceFormat2KHR($sel:vkSurfaceFormat:VkSurfaceFormat2KHR&$sel:vkSType:VkSurfaceCapabilities2KHR&$sel:vkPNext:VkSurfaceCapabilities2KHR4$sel:vkSurfaceCapabilities:VkSurfaceCapabilities2KHR,$sel:vkSType:VkPhysicalDeviceSurfaceInfo2KHR,$sel:vkPNext:VkPhysicalDeviceSurfaceInfo2KHR.$sel:vkSurface:VkPhysicalDeviceSurfaceInfo2KHR0VK_KHR_GET_SURFACE_CAPABILITIES_2_EXTENSION_NAME.VK_KHR_GET_SURFACE_CAPABILITIES_2_SPEC_VERSION&VK_STRUCTURE_TYPE_SURFACE_FORMAT_2_KHR,VK_STRUCTURE_TYPE_SURFACE_CAPABILITIES_2_KHR4VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_SURFACE_INFO_2_KHR)$fStorableVkPhysicalDeviceSurfaceInfo2KHR#$fStorableVkSurfaceCapabilities2KHR$fStorableVkSurfaceFormat2KHR#$fEqVkPhysicalDeviceSurfaceInfo2KHR%$fShowVkPhysicalDeviceSurfaceInfo2KHR$fEqVkSurfaceCapabilities2KHR$fShowVkSurfaceCapabilities2KHR$fEqVkSurfaceFormat2KHR$fShowVkSurfaceFormat2KHR*$sel:vkSType:VkAndroidSurfaceCreateInfoKHR*$sel:vkPNext:VkAndroidSurfaceCreateInfoKHR*$sel:vkFlags:VkAndroidSurfaceCreateInfoKHR+$sel:vkWindow:VkAndroidSurfaceCreateInfoKHRVkAndroidSurfaceCreateFlagsKHR ANativeWindow%VK_KHR_ANDROID_SURFACE_EXTENSION_NAME#VK_KHR_ANDROID_SURFACE_SPEC_VERSION1VK_STRUCTURE_TYPE_ANDROID_SURFACE_CREATE_INFO_KHR$$fReadVkAndroidSurfaceCreateFlagsKHR$$fShowVkAndroidSurfaceCreateFlagsKHR'$fStorableVkAndroidSurfaceCreateInfoKHR"$fEqVkAndroidSurfaceCreateFlagsKHR#$fOrdVkAndroidSurfaceCreateFlagsKHR($fStorableVkAndroidSurfaceCreateFlagsKHR$$fBitsVkAndroidSurfaceCreateFlagsKHR*$fFiniteBitsVkAndroidSurfaceCreateFlagsKHR!$fEqVkAndroidSurfaceCreateInfoKHR#$fShowVkAndroidSurfaceCreateInfoKHR+VK_EXT_SWAPCHAIN_COLOR_SPACE_EXTENSION_NAME)VK_EXT_SWAPCHAIN_COLOR_SPACE_SPEC_VERSION*VK_COLOR_SPACE_EXTENDED_SRGB_NONLINEAR_EXTVK_COLOR_SPACE_PASS_THROUGH_EXT%VK_COLOR_SPACE_ADOBERGB_NONLINEAR_EXT"VK_COLOR_SPACE_ADOBERGB_LINEAR_EXTVK_COLOR_SPACE_HDR10_HLG_EXTVK_COLOR_SPACE_DOLBYVISION_EXTVK_COLOR_SPACE_HDR10_ST2084_EXT VK_COLOR_SPACE_BT2020_LINEAR_EXT"VK_COLOR_SPACE_BT709_NONLINEAR_EXTVK_COLOR_SPACE_BT709_LINEAR_EXT#VK_COLOR_SPACE_DCI_P3_NONLINEAR_EXT VK_COLOR_SPACE_DCI_P3_LINEAR_EXT'VK_COLOR_SPACE_EXTENDED_SRGB_LINEAR_EXT'VK_COLOR_SPACE_DISPLAY_P3_NONLINEAR_EXT$sel:vkOffset:VkRectLayerKHR$sel:vkExtent:VkRectLayerKHR$sel:vkLayer:VkRectLayerKHRVkPresentRegionKHR($sel:vkRectangleCount:VkPresentRegionKHR%$sel:vkPRectangles:VkPresentRegionKHR $sel:vkSType:VkPresentRegionsKHR $sel:vkPNext:VkPresentRegionsKHR)$sel:vkSwapchainCount:VkPresentRegionsKHR#$sel:vkPRegions:VkPresentRegionsKHR)VK_KHR_INCREMENTAL_PRESENT_EXTENSION_NAME'VK_KHR_INCREMENTAL_PRESENT_SPEC_VERSION%VK_STRUCTURE_TYPE_PRESENT_REGIONS_KHR$fStorableVkRectLayerKHR$fStorableVkPresentRegionKHR$fStorableVkPresentRegionsKHR$fEqVkRectLayerKHR$fShowVkRectLayerKHR$fEqVkPresentRegionKHR$fShowVkPresentRegionKHR$fEqVkPresentRegionsKHR$fShowVkPresentRegionsKHRVkDisplayPlaneAlphaFlagsKHR*$sel:vkSType:VkDisplaySurfaceCreateInfoKHR*$sel:vkPNext:VkDisplaySurfaceCreateInfoKHR*$sel:vkFlags:VkDisplaySurfaceCreateInfoKHR0$sel:vkDisplayMode:VkDisplaySurfaceCreateInfoKHR/$sel:vkPlaneIndex:VkDisplaySurfaceCreateInfoKHR4$sel:vkPlaneStackIndex:VkDisplaySurfaceCreateInfoKHR.$sel:vkTransform:VkDisplaySurfaceCreateInfoKHR0$sel:vkGlobalAlpha:VkDisplaySurfaceCreateInfoKHR.$sel:vkAlphaMode:VkDisplaySurfaceCreateInfoKHR0$sel:vkImageExtent:VkDisplaySurfaceCreateInfoKHR3$sel:vkSupportedAlpha:VkDisplayPlaneCapabilitiesKHR3$sel:vkMinSrcPosition:VkDisplayPlaneCapabilitiesKHR3$sel:vkMaxSrcPosition:VkDisplayPlaneCapabilitiesKHR1$sel:vkMinSrcExtent:VkDisplayPlaneCapabilitiesKHR1$sel:vkMaxSrcExtent:VkDisplayPlaneCapabilitiesKHR3$sel:vkMinDstPosition:VkDisplayPlaneCapabilitiesKHR3$sel:vkMaxDstPosition:VkDisplayPlaneCapabilitiesKHR1$sel:vkMinDstExtent:VkDisplayPlaneCapabilitiesKHR1$sel:vkMaxDstExtent:VkDisplayPlaneCapabilitiesKHR'$sel:vkSType:VkDisplayModeCreateInfoKHR'$sel:vkPNext:VkDisplayModeCreateInfoKHR'$sel:vkFlags:VkDisplayModeCreateInfoKHR,$sel:vkParameters:VkDisplayModeCreateInfoKHRVkDisplayModePropertiesKHR-$sel:vkDisplayMode:VkDisplayModePropertiesKHR,$sel:vkParameters:VkDisplayModePropertiesKHR/$sel:vkVisibleRegion:VkDisplayModeParametersKHR-$sel:vkRefreshRate:VkDisplayModeParametersKHRVkDisplayPlanePropertiesKHR1$sel:vkCurrentDisplay:VkDisplayPlanePropertiesKHR4$sel:vkCurrentStackIndex:VkDisplayPlanePropertiesKHR%$sel:vkDisplay:VkDisplayPropertiesKHR)$sel:vkDisplayName:VkDisplayPropertiesKHR0$sel:vkPhysicalDimensions:VkDisplayPropertiesKHR0$sel:vkPhysicalResolution:VkDisplayPropertiesKHR1$sel:vkSupportedTransforms:VkDisplayPropertiesKHR2$sel:vkPlaneReorderPossible:VkDisplayPropertiesKHR/$sel:vkPersistentContent:VkDisplayPropertiesKHRVkDisplaySurfaceCreateFlagsKHRVkDisplayModeCreateFlagsKHRVkDisplayPlaneAlphaFlagBitsKHRVK_KHR_DISPLAY_EXTENSION_NAMEVK_KHR_DISPLAY_SPEC_VERSIONVK_OBJECT_TYPE_DISPLAY_MODE_KHRVK_OBJECT_TYPE_DISPLAY_KHR1VK_STRUCTURE_TYPE_DISPLAY_SURFACE_CREATE_INFO_KHR.VK_STRUCTURE_TYPE_DISPLAY_MODE_CREATE_INFO_KHR6VK_DISPLAY_PLANE_ALPHA_PER_PIXEL_PREMULTIPLIED_BIT_KHR(VK_DISPLAY_PLANE_ALPHA_PER_PIXEL_BIT_KHR%VK_DISPLAY_PLANE_ALPHA_GLOBAL_BIT_KHR%VK_DISPLAY_PLANE_ALPHA_OPAQUE_BIT_KHR$$fReadVkDisplayPlaneAlphaFlagBitsKHR$$fShowVkDisplayPlaneAlphaFlagBitsKHR!$fReadVkDisplayModeCreateFlagsKHR!$fShowVkDisplayModeCreateFlagsKHR$$fReadVkDisplaySurfaceCreateFlagsKHR$$fShowVkDisplaySurfaceCreateFlagsKHR $fStorableVkDisplayPropertiesKHR%$fStorableVkDisplayPlanePropertiesKHR$$fStorableVkDisplayModeParametersKHR$$fStorableVkDisplayModePropertiesKHR$$fStorableVkDisplayModeCreateInfoKHR'$fStorableVkDisplaySurfaceCreateInfoKHR'$fStorableVkDisplayPlaneCapabilitiesKHR"$fEqVkDisplayPlaneAlphaFlagBitsKHR#$fOrdVkDisplayPlaneAlphaFlagBitsKHR($fStorableVkDisplayPlaneAlphaFlagBitsKHR$$fBitsVkDisplayPlaneAlphaFlagBitsKHR*$fFiniteBitsVkDisplayPlaneAlphaFlagBitsKHR$fEqVkDisplayModeCreateFlagsKHR $fOrdVkDisplayModeCreateFlagsKHR%$fStorableVkDisplayModeCreateFlagsKHR!$fBitsVkDisplayModeCreateFlagsKHR'$fFiniteBitsVkDisplayModeCreateFlagsKHR"$fEqVkDisplaySurfaceCreateFlagsKHR#$fOrdVkDisplaySurfaceCreateFlagsKHR($fStorableVkDisplaySurfaceCreateFlagsKHR$$fBitsVkDisplaySurfaceCreateFlagsKHR*$fFiniteBitsVkDisplaySurfaceCreateFlagsKHR$fEqVkDisplayPropertiesKHR$fShowVkDisplayPropertiesKHR$fEqVkDisplayPlanePropertiesKHR!$fShowVkDisplayPlanePropertiesKHR$fEqVkDisplayModeParametersKHR $fShowVkDisplayModeParametersKHR$fEqVkDisplayModePropertiesKHR $fShowVkDisplayModePropertiesKHR$fEqVkDisplayModeCreateInfoKHR $fShowVkDisplayModeCreateInfoKHR!$fEqVkDisplaySurfaceCreateInfoKHR#$fShowVkDisplaySurfaceCreateInfoKHR!$fEqVkDisplayPlaneCapabilitiesKHR#$fShowVkDisplayPlaneCapabilitiesKHR)VK_EXT_DIRECT_MODE_DISPLAY_EXTENSION_NAME'VK_EXT_DIRECT_MODE_DISPLAY_SPEC_VERSIONRROutput*VK_EXT_ACQUIRE_XLIB_DISPLAY_EXTENSION_NAME(VK_EXT_ACQUIRE_XLIB_DISPLAY_SPEC_VERSION'$sel:vkSType:VkMultisamplePropertiesEXT'$sel:vkPNext:VkMultisamplePropertiesEXT;$sel:vkMaxSampleLocationGridSize:VkMultisamplePropertiesEXT9$sel:vkSType:VkPhysicalDeviceSampleLocationsPropertiesEXT9$sel:vkPNext:VkPhysicalDeviceSampleLocationsPropertiesEXTN$sel:vkSampleLocationSampleCounts:VkPhysicalDeviceSampleLocationsPropertiesEXTM$sel:vkMaxSampleLocationGridSize:VkPhysicalDeviceSampleLocationsPropertiesEXTQ$sel:vkSampleLocationCoordinateRange:VkPhysicalDeviceSampleLocationsPropertiesEXTN$sel:vkSampleLocationSubPixelBits:VkPhysicalDeviceSampleLocationsPropertiesEXTK$sel:vkVariableSampleLocations:VkPhysicalDeviceSampleLocationsPropertiesEXT8$sel:vkSType:VkPipelineSampleLocationsStateCreateInfoEXT8$sel:vkPNext:VkPipelineSampleLocationsStateCreateInfoEXTH$sel:vkSampleLocationsEnable:VkPipelineSampleLocationsStateCreateInfoEXTF$sel:vkSampleLocationsInfo:VkPipelineSampleLocationsStateCreateInfoEXT4$sel:vkSType:VkRenderPassSampleLocationsBeginInfoEXT4$sel:vkPNext:VkRenderPassSampleLocationsBeginInfoEXTT$sel:vkAttachmentInitialSampleLocationsCount:VkRenderPassSampleLocationsBeginInfoEXTP$sel:vkPAttachmentInitialSampleLocations:VkRenderPassSampleLocationsBeginInfoEXTN$sel:vkPostSubpassSampleLocationsCount:VkRenderPassSampleLocationsBeginInfoEXTJ$sel:vkPPostSubpassSampleLocations:VkRenderPassSampleLocationsBeginInfoEXTVkSubpassSampleLocationsEXT/$sel:vkSubpassIndex:VkSubpassSampleLocationsEXT6$sel:vkSampleLocationsInfo:VkSubpassSampleLocationsEXTVkAttachmentSampleLocationsEXT5$sel:vkAttachmentIndex:VkAttachmentSampleLocationsEXT9$sel:vkSampleLocationsInfo:VkAttachmentSampleLocationsEXT%$sel:vkSType:VkSampleLocationsInfoEXT%$sel:vkPNext:VkSampleLocationsInfoEXT7$sel:vkSampleLocationsPerPixel:VkSampleLocationsInfoEXT6$sel:vkSampleLocationGridSize:VkSampleLocationsInfoEXT4$sel:vkSampleLocationsCount:VkSampleLocationsInfoEXT0$sel:vkPSampleLocations:VkSampleLocationsInfoEXTVkSampleLocationEXT$sel:vkX:VkSampleLocationEXT$sel:vkY:VkSampleLocationEXT&VK_EXT_SAMPLE_LOCATIONS_EXTENSION_NAME$VK_EXT_SAMPLE_LOCATIONS_SPEC_VERSION9VK_IMAGE_CREATE_SAMPLE_LOCATIONS_COMPATIBLE_DEPTH_BIT_EXT,VK_STRUCTURE_TYPE_MULTISAMPLE_PROPERTIES_EXTAVK_STRUCTURE_TYPE_PHYSICAL_DEVICE_SAMPLE_LOCATIONS_PROPERTIES_EXTAVK_STRUCTURE_TYPE_PIPELINE_SAMPLE_LOCATIONS_STATE_CREATE_INFO_EXT=VK_STRUCTURE_TYPE_RENDER_PASS_SAMPLE_LOCATIONS_BEGIN_INFO_EXT+VK_STRUCTURE_TYPE_SAMPLE_LOCATIONS_INFO_EXT%VK_DYNAMIC_STATE_SAMPLE_LOCATIONS_EXT$fStorableVkSampleLocationEXT"$fStorableVkSampleLocationsInfoEXT($fStorableVkAttachmentSampleLocationsEXT%$fStorableVkSubpassSampleLocationsEXT1$fStorableVkRenderPassSampleLocationsBeginInfoEXT5$fStorableVkPipelineSampleLocationsStateCreateInfoEXT6$fStorableVkPhysicalDeviceSampleLocationsPropertiesEXT$$fStorableVkMultisamplePropertiesEXT$fEqVkSampleLocationEXT$fShowVkSampleLocationEXT$fEqVkSampleLocationsInfoEXT$fShowVkSampleLocationsInfoEXT"$fEqVkAttachmentSampleLocationsEXT$$fShowVkAttachmentSampleLocationsEXT$fEqVkSubpassSampleLocationsEXT!$fShowVkSubpassSampleLocationsEXT+$fEqVkRenderPassSampleLocationsBeginInfoEXT-$fShowVkRenderPassSampleLocationsBeginInfoEXT/$fEqVkPipelineSampleLocationsStateCreateInfoEXT1$fShowVkPipelineSampleLocationsStateCreateInfoEXT0$fEqVkPhysicalDeviceSampleLocationsPropertiesEXT2$fShowVkPhysicalDeviceSampleLocationsPropertiesEXT$fEqVkMultisamplePropertiesEXT $fShowVkMultisamplePropertiesEXTVkSurfaceCounterFlagsEXT&$sel:vkSType:VkSurfaceCapabilities2EXT&$sel:vkPNext:VkSurfaceCapabilities2EXT.$sel:vkMinImageCount:VkSurfaceCapabilities2EXT.$sel:vkMaxImageCount:VkSurfaceCapabilities2EXT.$sel:vkCurrentExtent:VkSurfaceCapabilities2EXT/$sel:vkMinImageExtent:VkSurfaceCapabilities2EXT/$sel:vkMaxImageExtent:VkSurfaceCapabilities2EXT4$sel:vkMaxImageArrayLayers:VkSurfaceCapabilities2EXT4$sel:vkSupportedTransforms:VkSurfaceCapabilities2EXT1$sel:vkCurrentTransform:VkSurfaceCapabilities2EXT8$sel:vkSupportedCompositeAlpha:VkSurfaceCapabilities2EXT4$sel:vkSupportedUsageFlags:VkSurfaceCapabilities2EXT9$sel:vkSupportedSurfaceCounters:VkSurfaceCapabilities2EXTVkSurfaceCounterFlagBitsEXT+VK_STRUCTURE_TYPE_SURFACE_CAPABILITIES2_EXT-VK_EXT_DISPLAY_SURFACE_COUNTER_EXTENSION_NAME+VK_EXT_DISPLAY_SURFACE_COUNTER_SPEC_VERSION,VK_STRUCTURE_TYPE_SURFACE_CAPABILITIES_2_EXTVK_SURFACE_COUNTER_VBLANK_EXT!$fReadVkSurfaceCounterFlagBitsEXT!$fShowVkSurfaceCounterFlagBitsEXT#$fStorableVkSurfaceCapabilities2EXT$fEqVkSurfaceCounterFlagBitsEXT $fOrdVkSurfaceCounterFlagBitsEXT%$fStorableVkSurfaceCounterFlagBitsEXT!$fBitsVkSurfaceCounterFlagBitsEXT'$fFiniteBitsVkSurfaceCounterFlagBitsEXT$fEqVkSurfaceCapabilities2EXT$fShowVkSurfaceCapabilities2EXT9$sel:vkSType:VkPipelineDiscardRectangleStateCreateInfoEXT9$sel:vkPNext:VkPipelineDiscardRectangleStateCreateInfoEXT9$sel:vkFlags:VkPipelineDiscardRectangleStateCreateInfoEXTH$sel:vkDiscardRectangleMode:VkPipelineDiscardRectangleStateCreateInfoEXTI$sel:vkDiscardRectangleCount:VkPipelineDiscardRectangleStateCreateInfoEXTF$sel:vkPDiscardRectangles:VkPipelineDiscardRectangleStateCreateInfoEXT:$sel:vkSType:VkPhysicalDeviceDiscardRectanglePropertiesEXT:$sel:vkPNext:VkPhysicalDeviceDiscardRectanglePropertiesEXTI$sel:vkMaxDiscardRectangles:VkPhysicalDeviceDiscardRectanglePropertiesEXT-VkPipelineDiscardRectangleStateCreateFlagsEXTVkDiscardRectangleModeEXT(VK_EXT_DISCARD_RECTANGLES_EXTENSION_NAME&VK_EXT_DISCARD_RECTANGLES_SPEC_VERSIONBVK_STRUCTURE_TYPE_PIPELINE_DISCARD_RECTANGLE_STATE_CREATE_INFO_EXTBVK_STRUCTURE_TYPE_PHYSICAL_DEVICE_DISCARD_RECTANGLE_PROPERTIES_EXT&VK_DYNAMIC_STATE_DISCARD_RECTANGLE_EXT'VK_DISCARD_RECTANGLE_MODE_EXCLUSIVE_EXT'VK_DISCARD_RECTANGLE_MODE_INCLUSIVE_EXT$fReadVkDiscardRectangleModeEXT$fShowVkDiscardRectangleModeEXT3$fReadVkPipelineDiscardRectangleStateCreateFlagsEXT3$fShowVkPipelineDiscardRectangleStateCreateFlagsEXT7$fStorableVkPhysicalDeviceDiscardRectanglePropertiesEXT6$fStorableVkPipelineDiscardRectangleStateCreateInfoEXT$fEqVkDiscardRectangleModeEXT$fOrdVkDiscardRectangleModeEXT#$fStorableVkDiscardRectangleModeEXT1$fEqVkPipelineDiscardRectangleStateCreateFlagsEXT2$fOrdVkPipelineDiscardRectangleStateCreateFlagsEXT7$fStorableVkPipelineDiscardRectangleStateCreateFlagsEXT3$fBitsVkPipelineDiscardRectangleStateCreateFlagsEXT9$fFiniteBitsVkPipelineDiscardRectangleStateCreateFlagsEXT1$fEqVkPhysicalDeviceDiscardRectanglePropertiesEXT3$fShowVkPhysicalDeviceDiscardRectanglePropertiesEXT0$fEqVkPipelineDiscardRectangleStateCreateInfoEXT2$fShowVkPipelineDiscardRectangleStateCreateInfoEXT-$sel:vkSType:VkBindImageMemoryDeviceGroupInfo-$sel:vkPNext:VkBindImageMemoryDeviceGroupInfo8$sel:vkDeviceIndexCount:VkBindImageMemoryDeviceGroupInfo6$sel:vkPDeviceIndices:VkBindImageMemoryDeviceGroupInfoD$sel:vkSplitInstanceBindRegionCount:VkBindImageMemoryDeviceGroupInfoA$sel:vkPSplitInstanceBindRegions:VkBindImageMemoryDeviceGroupInfo.$sel:vkSType:VkBindBufferMemoryDeviceGroupInfo.$sel:vkPNext:VkBindBufferMemoryDeviceGroupInfo9$sel:vkDeviceIndexCount:VkBindBufferMemoryDeviceGroupInfo7$sel:vkPDeviceIndices:VkBindBufferMemoryDeviceGroupInfo/VK_IMAGE_CREATE_SPLIT_INSTANCE_BIND_REGIONS_BIT5VK_STRUCTURE_TYPE_BIND_IMAGE_MEMORY_DEVICE_GROUP_INFO6VK_STRUCTURE_TYPE_BIND_BUFFER_MEMORY_DEVICE_GROUP_INFO+$fStorableVkBindBufferMemoryDeviceGroupInfo*$fStorableVkBindImageMemoryDeviceGroupInfo%$fEqVkBindBufferMemoryDeviceGroupInfo'$fShowVkBindBufferMemoryDeviceGroupInfo$$fEqVkBindImageMemoryDeviceGroupInfo&$fShowVkBindImageMemoryDeviceGroupInfo $sel:vkSType:VkSamplerCreateInfo $sel:vkPNext:VkSamplerCreateInfo $sel:vkFlags:VkSamplerCreateInfo$$sel:vkMagFilter:VkSamplerCreateInfo$$sel:vkMinFilter:VkSamplerCreateInfo%$sel:vkMipmapMode:VkSamplerCreateInfo'$sel:vkAddressModeU:VkSamplerCreateInfo'$sel:vkAddressModeV:VkSamplerCreateInfo'$sel:vkAddressModeW:VkSamplerCreateInfo%$sel:vkMipLodBias:VkSamplerCreateInfo+$sel:vkAnisotropyEnable:VkSamplerCreateInfo($sel:vkMaxAnisotropy:VkSamplerCreateInfo($sel:vkCompareEnable:VkSamplerCreateInfo$$sel:vkCompareOp:VkSamplerCreateInfo!$sel:vkMinLod:VkSamplerCreateInfo!$sel:vkMaxLod:VkSamplerCreateInfo&$sel:vkBorderColor:VkSamplerCreateInfo2$sel:vkUnnormalizedCoordinates:VkSamplerCreateInfoVkSamplerCreateFlagsVkSamplerMipmapModeVkFilterVkSamplerAddressMode VkBorderColorVK_SAMPLER_MIPMAP_MODE_LINEARVK_SAMPLER_MIPMAP_MODE_NEARESTVK_FILTER_LINEARVK_FILTER_NEAREST'VK_SAMPLER_ADDRESS_MODE_CLAMP_TO_BORDER%VK_SAMPLER_ADDRESS_MODE_CLAMP_TO_EDGE'VK_SAMPLER_ADDRESS_MODE_MIRRORED_REPEATVK_SAMPLER_ADDRESS_MODE_REPEAT VK_BORDER_COLOR_INT_OPAQUE_WHITE"VK_BORDER_COLOR_FLOAT_OPAQUE_WHITE VK_BORDER_COLOR_INT_OPAQUE_BLACK"VK_BORDER_COLOR_FLOAT_OPAQUE_BLACK%VK_BORDER_COLOR_INT_TRANSPARENT_BLACK'VK_BORDER_COLOR_FLOAT_TRANSPARENT_BLACK$fReadVkBorderColor$fShowVkBorderColor$fReadVkSamplerAddressMode$fShowVkSamplerAddressMode$fReadVkFilter$fShowVkFilter$fReadVkSamplerMipmapMode$fShowVkSamplerMipmapMode$fReadVkSamplerCreateFlags$fShowVkSamplerCreateFlags$fStorableVkSamplerCreateInfo$fEqVkBorderColor$fOrdVkBorderColor$fStorableVkBorderColor$fEqVkSamplerAddressMode$fOrdVkSamplerAddressMode$fStorableVkSamplerAddressMode $fEqVkFilter $fOrdVkFilter$fStorableVkFilter$fEqVkSamplerMipmapMode$fOrdVkSamplerMipmapMode$fStorableVkSamplerMipmapMode$fEqVkSamplerCreateFlags$fOrdVkSamplerCreateFlags$fStorableVkSamplerCreateFlags$fBitsVkSamplerCreateFlags $fFiniteBitsVkSamplerCreateFlags$fEqVkSamplerCreateInfo$fShowVkSamplerCreateInfo2VK_KHR_SAMPLER_MIRROR_CLAMP_TO_EDGE_EXTENSION_NAME0VK_KHR_SAMPLER_MIRROR_CLAMP_TO_EDGE_SPEC_VERSION,VK_SAMPLER_ADDRESS_MODE_MIRROR_CLAMP_TO_EDGE"VK_IMG_FILTER_CUBIC_EXTENSION_NAME VK_IMG_FILTER_CUBIC_SPEC_VERSION4VK_FORMAT_FEATURE_SAMPLED_IMAGE_FILTER_CUBIC_BIT_IMGVK_FILTER_CUBIC_IMG'$sel:vkSType:VkPipelineLayoutCreateInfo'$sel:vkPNext:VkPipelineLayoutCreateInfo'$sel:vkFlags:VkPipelineLayoutCreateInfo0$sel:vkSetLayoutCount:VkPipelineLayoutCreateInfo-$sel:vkPSetLayouts:VkPipelineLayoutCreateInfo8$sel:vkPushConstantRangeCount:VkPipelineLayoutCreateInfo5$sel:vkPPushConstantRanges:VkPipelineLayoutCreateInfo%$sel:vkStageFlags:VkPushConstantRange!$sel:vkOffset:VkPushConstantRange$sel:vkSize:VkPushConstantRangeVkPipelineLayoutCreateFlags!$fReadVkPipelineLayoutCreateFlags!$fShowVkPipelineLayoutCreateFlags$fStorableVkPushConstantRange$$fStorableVkPipelineLayoutCreateInfo$fEqVkPipelineLayoutCreateFlags $fOrdVkPipelineLayoutCreateFlags%$fStorableVkPipelineLayoutCreateFlags!$fBitsVkPipelineLayoutCreateFlags'$fFiniteBitsVkPipelineLayoutCreateFlags$fEqVkPushConstantRange$fShowVkPushConstantRange$fEqVkPipelineLayoutCreateInfo $fShowVkPipelineLayoutCreateInfo0$sel:vkShaderStageMask:VkShaderStatisticsInfoAMD.$sel:vkResourceUsage:VkShaderStatisticsInfoAMD1$sel:vkNumPhysicalVgprs:VkShaderStatisticsInfoAMD1$sel:vkNumPhysicalSgprs:VkShaderStatisticsInfoAMD2$sel:vkNumAvailableVgprs:VkShaderStatisticsInfoAMD2$sel:vkNumAvailableSgprs:VkShaderStatisticsInfoAMD5$sel:vkComputeWorkGroupSize:VkShaderStatisticsInfoAMDVkShaderResourceUsageAMD,$sel:vkNumUsedVgprs:VkShaderResourceUsageAMD,$sel:vkNumUsedSgprs:VkShaderResourceUsageAMD8$sel:vkLdsSizePerLocalWorkGroup:VkShaderResourceUsageAMD3$sel:vkLdsUsageSizeInBytes:VkShaderResourceUsageAMD6$sel:vkScratchMemUsageInBytes:VkShaderResourceUsageAMDVkShaderInfoTypeAMD!VK_AMD_SHADER_INFO_EXTENSION_NAMEVK_AMD_SHADER_INFO_SPEC_VERSION#VK_SHADER_INFO_TYPE_DISASSEMBLY_AMDVK_SHADER_INFO_TYPE_BINARY_AMD"VK_SHADER_INFO_TYPE_STATISTICS_AMD$fReadVkShaderInfoTypeAMD$fShowVkShaderInfoTypeAMD"$fStorableVkShaderResourceUsageAMD#$fStorableVkShaderStatisticsInfoAMD$fEqVkShaderInfoTypeAMD$fOrdVkShaderInfoTypeAMD$fStorableVkShaderInfoTypeAMD$fEqVkShaderResourceUsageAMD$fShowVkShaderResourceUsageAMD$fEqVkShaderStatisticsInfoAMD$fShowVkShaderStatisticsInfoAMDVkSubgroupFeatureFlags/$sel:vkSType:VkPhysicalDeviceSubgroupProperties/$sel:vkPNext:VkPhysicalDeviceSubgroupProperties6$sel:vkSubgroupSize:VkPhysicalDeviceSubgroupProperties9$sel:vkSupportedStages:VkPhysicalDeviceSubgroupProperties=$sel:vkSupportedOperations:VkPhysicalDeviceSubgroupPropertiesC$sel:vkQuadOperationsInAllStages:VkPhysicalDeviceSubgroupPropertiesVkSubgroupFeatureFlagBits5VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_SUBGROUP_PROPERTIESVK_SUBGROUP_FEATURE_QUAD_BIT!VK_SUBGROUP_FEATURE_CLUSTERED_BIT(VK_SUBGROUP_FEATURE_SHUFFLE_RELATIVE_BITVK_SUBGROUP_FEATURE_SHUFFLE_BITVK_SUBGROUP_FEATURE_BALLOT_BIT"VK_SUBGROUP_FEATURE_ARITHMETIC_BITVK_SUBGROUP_FEATURE_VOTE_BITVK_SUBGROUP_FEATURE_BASIC_BIT$fReadVkSubgroupFeatureFlagBits$fShowVkSubgroupFeatureFlagBits,$fStorableVkPhysicalDeviceSubgroupProperties$fEqVkSubgroupFeatureFlagBits$fOrdVkSubgroupFeatureFlagBits#$fStorableVkSubgroupFeatureFlagBits$fBitsVkSubgroupFeatureFlagBits%$fFiniteBitsVkSubgroupFeatureFlagBits&$fEqVkPhysicalDeviceSubgroupProperties($fShowVkPhysicalDeviceSubgroupProperties0VK_NV_SHADER_SUBGROUP_PARTITIONED_EXTENSION_NAME.VK_NV_SHADER_SUBGROUP_PARTITIONED_SPEC_VERSION&VK_SUBGROUP_FEATURE_PARTITIONED_BIT_NV $sel:vkSType:VkMappedMemoryRange $sel:vkPNext:VkMappedMemoryRange!$sel:vkMemory:VkMappedMemoryRange!$sel:vkOffset:VkMappedMemoryRange$sel:vkSize:VkMappedMemoryRange!$sel:vkSType:VkMemoryAllocateInfo!$sel:vkPNext:VkMemoryAllocateInfo*$sel:vkAllocationSize:VkMemoryAllocateInfo+$sel:vkMemoryTypeIndex:VkMemoryAllocateInfoVkMemoryMapFlags$fReadVkMemoryMapFlags$fShowVkMemoryMapFlags$fStorableVkMemoryAllocateInfo$fStorableVkMappedMemoryRange$fEqVkMemoryMapFlags$fOrdVkMemoryMapFlags$fStorableVkMemoryMapFlags$fBitsVkMemoryMapFlags$fFiniteBitsVkMemoryMapFlags$fEqVkMemoryAllocateInfo$fShowVkMemoryAllocateInfo$fEqVkMappedMemoryRange$fShowVkMappedMemoryRange2$sel:vkSType:VkWin32KeyedMutexAcquireReleaseInfoNV2$sel:vkPNext:VkWin32KeyedMutexAcquireReleaseInfoNV9$sel:vkAcquireCount:VkWin32KeyedMutexAcquireReleaseInfoNV:$sel:vkPAcquireSyncs:VkWin32KeyedMutexAcquireReleaseInfoNV9$sel:vkPAcquireKeys:VkWin32KeyedMutexAcquireReleaseInfoNVH$sel:vkPAcquireTimeoutMilliseconds:VkWin32KeyedMutexAcquireReleaseInfoNV9$sel:vkReleaseCount:VkWin32KeyedMutexAcquireReleaseInfoNV:$sel:vkPReleaseSyncs:VkWin32KeyedMutexAcquireReleaseInfoNV9$sel:vkPReleaseKeys:VkWin32KeyedMutexAcquireReleaseInfoNV&VK_NV_WIN32_KEYED_MUTEX_EXTENSION_NAME$VK_NV_WIN32_KEYED_MUTEX_SPEC_VERSION;VK_STRUCTURE_TYPE_WIN32_KEYED_MUTEX_ACQUIRE_RELEASE_INFO_NV/$fStorableVkWin32KeyedMutexAcquireReleaseInfoNV)$fEqVkWin32KeyedMutexAcquireReleaseInfoNV+$fShowVkWin32KeyedMutexAcquireReleaseInfoNV,$sel:vkSType:VkExportMemoryWin32HandleInfoNV,$sel:vkPNext:VkExportMemoryWin32HandleInfoNV2$sel:vkPAttributes:VkExportMemoryWin32HandleInfoNV/$sel:vkDwAccess:VkExportMemoryWin32HandleInfoNV,$sel:vkSType:VkImportMemoryWin32HandleInfoNV,$sel:vkPNext:VkImportMemoryWin32HandleInfoNV1$sel:vkHandleType:VkImportMemoryWin32HandleInfoNV-$sel:vkHandle:VkImportMemoryWin32HandleInfoNVDWORDSECURITY_ATTRIBUTESHANDLE*VK_NV_EXTERNAL_MEMORY_WIN32_EXTENSION_NAME(VK_NV_EXTERNAL_MEMORY_WIN32_SPEC_VERSION4VK_STRUCTURE_TYPE_EXPORT_MEMORY_WIN32_HANDLE_INFO_NV4VK_STRUCTURE_TYPE_IMPORT_MEMORY_WIN32_HANDLE_INFO_NV)$fStorableVkImportMemoryWin32HandleInfoNV)$fStorableVkExportMemoryWin32HandleInfoNV#$fEqVkImportMemoryWin32HandleInfoNV%$fShowVkImportMemoryWin32HandleInfoNV#$fEqVkExportMemoryWin32HandleInfoNV%$fShowVkExportMemoryWin32HandleInfoNV3$sel:vkSType:VkWin32KeyedMutexAcquireReleaseInfoKHR3$sel:vkPNext:VkWin32KeyedMutexAcquireReleaseInfoKHR:$sel:vkAcquireCount:VkWin32KeyedMutexAcquireReleaseInfoKHR;$sel:vkPAcquireSyncs:VkWin32KeyedMutexAcquireReleaseInfoKHR:$sel:vkPAcquireKeys:VkWin32KeyedMutexAcquireReleaseInfoKHR>$sel:vkPAcquireTimeouts:VkWin32KeyedMutexAcquireReleaseInfoKHR:$sel:vkReleaseCount:VkWin32KeyedMutexAcquireReleaseInfoKHR;$sel:vkPReleaseSyncs:VkWin32KeyedMutexAcquireReleaseInfoKHR:$sel:vkPReleaseKeys:VkWin32KeyedMutexAcquireReleaseInfoKHR'VK_KHR_WIN32_KEYED_MUTEX_EXTENSION_NAME%VK_KHR_WIN32_KEYED_MUTEX_SPEC_VERSIONVK_STRUCTURE_TYPE_DEDICATED_ALLOCATION_MEMORY_ALLOCATE_INFO_NV$sel:vkAllocationSize:VkAndroidHardwareBufferPropertiesANDROID>$sel:vkMemoryTypeBits:VkAndroidHardwareBufferPropertiesANDROID0$sel:vkSType:VkAndroidHardwareBufferUsageANDROID0$sel:vkPNext:VkAndroidHardwareBufferUsageANDROIDE$sel:vkAndroidHardwareBufferUsage:VkAndroidHardwareBufferUsageANDROID5$sel:vkSType:VkImportAndroidHardwareBufferInfoANDROID5$sel:vkPNext:VkImportAndroidHardwareBufferInfoANDROID6$sel:vkBuffer:VkImportAndroidHardwareBufferInfoANDROIDAHardwareBufferAVK_ANDROID_EXTERNAL_MEMORY_ANDROID_HARDWARE_BUFFER_EXTENSION_NAME?VK_ANDROID_EXTERNAL_MEMORY_ANDROID_HARDWARE_BUFFER_SPEC_VERSIONBVK_EXTERNAL_MEMORY_HANDLE_TYPE_ANDROID_HARDWARE_BUFFER_BIT_ANDROID)VK_STRUCTURE_TYPE_EXTERNAL_FORMAT_ANDROIDAVK_STRUCTURE_TYPE_MEMORY_GET_ANDROID_HARDWARE_BUFFER_INFO_ANDROID=VK_STRUCTURE_TYPE_IMPORT_ANDROID_HARDWARE_BUFFER_INFO_ANDROIDCVK_STRUCTURE_TYPE_ANDROID_HARDWARE_BUFFER_FORMAT_PROPERTIES_ANDROID$sel:vkProtectedMemory:VkPhysicalDeviceProtectedMemoryFeatures"$sel:vkSType:VkProtectedSubmitInfo"$sel:vkPNext:VkProtectedSubmitInfo,$sel:vkProtectedSubmit:VkProtectedSubmitInfo$VK_COMMAND_POOL_CREATE_PROTECTED_BITVK_IMAGE_CREATE_PROTECTED_BITVK_BUFFER_CREATE_PROTECTED_BIT VK_MEMORY_PROPERTY_PROTECTED_BITVK_QUEUE_PROTECTED_BIT$VK_DEVICE_QUEUE_CREATE_PROTECTED_BIT%VK_STRUCTURE_TYPE_DEVICE_QUEUE_INFO_2=VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_PROTECTED_MEMORY_PROPERTIES;VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_PROTECTED_MEMORY_FEATURES'VK_STRUCTURE_TYPE_PROTECTED_SUBMIT_INFO$fStorableVkProtectedSubmitInfo1$fStorableVkPhysicalDeviceProtectedMemoryFeatures3$fStorableVkPhysicalDeviceProtectedMemoryProperties$fStorableVkDeviceQueueInfo2$fEqVkProtectedSubmitInfo$fShowVkProtectedSubmitInfo+$fEqVkPhysicalDeviceProtectedMemoryFeatures-$fShowVkPhysicalDeviceProtectedMemoryFeatures-$fEqVkPhysicalDeviceProtectedMemoryProperties/$fShowVkPhysicalDeviceProtectedMemoryProperties$fEqVkDeviceQueueInfo2$fShowVkDeviceQueueInfo2!$sel:vkOffset:VkSubresourceLayout$sel:vkSize:VkSubresourceLayout#$sel:vkRowPitch:VkSubresourceLayout%$sel:vkArrayPitch:VkSubresourceLayout%$sel:vkDepthPitch:VkSubresourceLayout$sel:vkSType:VkImageCreateInfo$sel:vkPNext:VkImageCreateInfo$sel:vkFlags:VkImageCreateInfo"$sel:vkImageType:VkImageCreateInfo$sel:vkFormat:VkImageCreateInfo$sel:vkExtent:VkImageCreateInfo"$sel:vkMipLevels:VkImageCreateInfo$$sel:vkArrayLayers:VkImageCreateInfo $sel:vkSamples:VkImageCreateInfo$sel:vkTiling:VkImageCreateInfo$sel:vkUsage:VkImageCreateInfo$$sel:vkSharingMode:VkImageCreateInfo.$sel:vkQueueFamilyIndexCount:VkImageCreateInfo,$sel:vkPQueueFamilyIndices:VkImageCreateInfo&$sel:vkInitialLayout:VkImageCreateInfo VkImageLayoutVK_IMAGE_LAYOUT_PREINITIALIZED$VK_IMAGE_LAYOUT_TRANSFER_DST_OPTIMAL$VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL(VK_IMAGE_LAYOUT_SHADER_READ_ONLY_OPTIMAL/VK_IMAGE_LAYOUT_DEPTH_STENCIL_READ_ONLY_OPTIMAL0VK_IMAGE_LAYOUT_DEPTH_STENCIL_ATTACHMENT_OPTIMAL(VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMALVK_IMAGE_LAYOUT_GENERALVK_IMAGE_LAYOUT_UNDEFINED$fReadVkImageLayout$fShowVkImageLayout$fStorableVkImageCreateInfo$fStorableVkSubresourceLayout$fEqVkImageLayout$fOrdVkImageLayout$fStorableVkImageLayout$fEqVkImageCreateInfo$fShowVkImageCreateInfo$fEqVkSubresourceLayout$fShowVkSubresourceLayout VkDeviceGroupPresentModeFlagsKHRVkSwapchainCreateFlagsKHR0$sel:vkSType:VkDeviceGroupSwapchainCreateInfoKHR0$sel:vkPNext:VkDeviceGroupSwapchainCreateInfoKHR0$sel:vkModes:VkDeviceGroupSwapchainCreateInfoKHR($sel:vkSType:VkDeviceGroupPresentInfoKHR($sel:vkPNext:VkDeviceGroupPresentInfoKHR1$sel:vkSwapchainCount:VkDeviceGroupPresentInfoKHR/$sel:vkPDeviceMasks:VkDeviceGroupPresentInfoKHR'$sel:vkMode:VkDeviceGroupPresentInfoKHR&$sel:vkSType:VkAcquireNextImageInfoKHR&$sel:vkPNext:VkAcquireNextImageInfoKHR*$sel:vkSwapchain:VkAcquireNextImageInfoKHR($sel:vkTimeout:VkAcquireNextImageInfoKHR*$sel:vkSemaphore:VkAcquireNextImageInfoKHR&$sel:vkFence:VkAcquireNextImageInfoKHR+$sel:vkDeviceMask:VkAcquireNextImageInfoKHR.$sel:vkSType:VkBindImageMemorySwapchainInfoKHR.$sel:vkPNext:VkBindImageMemorySwapchainInfoKHR2$sel:vkSwapchain:VkBindImageMemorySwapchainInfoKHR3$sel:vkImageIndex:VkBindImageMemorySwapchainInfoKHR*$sel:vkSType:VkImageSwapchainCreateInfoKHR*$sel:vkPNext:VkImageSwapchainCreateInfoKHR.$sel:vkSwapchain:VkImageSwapchainCreateInfoKHR0$sel:vkSType:VkDeviceGroupPresentCapabilitiesKHR0$sel:vkPNext:VkDeviceGroupPresentCapabilitiesKHR6$sel:vkPresentMask:VkDeviceGroupPresentCapabilitiesKHR0$sel:vkModes:VkDeviceGroupPresentCapabilitiesKHR$sel:vkSType:VkPresentInfoKHR$sel:vkPNext:VkPresentInfoKHR*$sel:vkWaitSemaphoreCount:VkPresentInfoKHR'$sel:vkPWaitSemaphores:VkPresentInfoKHR&$sel:vkSwapchainCount:VkPresentInfoKHR#$sel:vkPSwapchains:VkPresentInfoKHR%$sel:vkPImageIndices:VkPresentInfoKHR $sel:vkPResults:VkPresentInfoKHR%$sel:vkSType:VkSwapchainCreateInfoKHR%$sel:vkPNext:VkSwapchainCreateInfoKHR%$sel:vkFlags:VkSwapchainCreateInfoKHR'$sel:vkSurface:VkSwapchainCreateInfoKHR-$sel:vkMinImageCount:VkSwapchainCreateInfoKHR+$sel:vkImageFormat:VkSwapchainCreateInfoKHR/$sel:vkImageColorSpace:VkSwapchainCreateInfoKHR+$sel:vkImageExtent:VkSwapchainCreateInfoKHR0$sel:vkImageArrayLayers:VkSwapchainCreateInfoKHR*$sel:vkImageUsage:VkSwapchainCreateInfoKHR0$sel:vkImageSharingMode:VkSwapchainCreateInfoKHR5$sel:vkQueueFamilyIndexCount:VkSwapchainCreateInfoKHR3$sel:vkPQueueFamilyIndices:VkSwapchainCreateInfoKHR,$sel:vkPreTransform:VkSwapchainCreateInfoKHR.$sel:vkCompositeAlpha:VkSwapchainCreateInfoKHR+$sel:vkPresentMode:VkSwapchainCreateInfoKHR'$sel:vkClipped:VkSwapchainCreateInfoKHR,$sel:vkOldSwapchain:VkSwapchainCreateInfoKHR#VkDeviceGroupPresentModeFlagBitsKHRVkSwapchainCreateFlagBitsKHRVK_KHR_SWAPCHAIN_EXTENSION_NAMEVK_KHR_SWAPCHAIN_SPEC_VERSION%VK_SWAPCHAIN_CREATE_PROTECTED_BIT_KHR7VK_SWAPCHAIN_CREATE_SPLIT_INSTANCE_BIND_REGIONS_BIT_KHRVK_OBJECT_TYPE_SWAPCHAIN_KHR8VK_STRUCTURE_TYPE_DEVICE_GROUP_SWAPCHAIN_CREATE_INFO_KHR/VK_STRUCTURE_TYPE_DEVICE_GROUP_PRESENT_INFO_KHR-VK_STRUCTURE_TYPE_ACQUIRE_NEXT_IMAGE_INFO_KHR6VK_STRUCTURE_TYPE_BIND_IMAGE_MEMORY_SWAPCHAIN_INFO_KHR1VK_STRUCTURE_TYPE_IMAGE_SWAPCHAIN_CREATE_INFO_KHR7VK_STRUCTURE_TYPE_DEVICE_GROUP_PRESENT_CAPABILITIES_KHR"VK_STRUCTURE_TYPE_PRESENT_INFO_KHR+VK_STRUCTURE_TYPE_SWAPCHAIN_CREATE_INFO_KHRVK_ERROR_OUT_OF_DATE_KHRVK_SUBOPTIMAL_KHRVK_IMAGE_LAYOUT_PRESENT_SRC_KHR7VK_DEVICE_GROUP_PRESENT_MODE_LOCAL_MULTI_DEVICE_BIT_KHR(VK_DEVICE_GROUP_PRESENT_MODE_SUM_BIT_KHR+VK_DEVICE_GROUP_PRESENT_MODE_REMOTE_BIT_KHR*VK_DEVICE_GROUP_PRESENT_MODE_LOCAL_BIT_KHR"$fReadVkSwapchainCreateFlagBitsKHR"$fShowVkSwapchainCreateFlagBitsKHR)$fReadVkDeviceGroupPresentModeFlagBitsKHR)$fShowVkDeviceGroupPresentModeFlagBitsKHR$fStorableVkPresentInfoKHR'$fStorableVkImageSwapchainCreateInfoKHR+$fStorableVkBindImageMemorySwapchainInfoKHR#$fStorableVkAcquireNextImageInfoKHR%$fStorableVkDeviceGroupPresentInfoKHR"$fStorableVkSwapchainCreateInfoKHR-$fStorableVkDeviceGroupSwapchainCreateInfoKHR-$fStorableVkDeviceGroupPresentCapabilitiesKHR $fEqVkSwapchainCreateFlagBitsKHR!$fOrdVkSwapchainCreateFlagBitsKHR&$fStorableVkSwapchainCreateFlagBitsKHR"$fBitsVkSwapchainCreateFlagBitsKHR($fFiniteBitsVkSwapchainCreateFlagBitsKHR'$fEqVkDeviceGroupPresentModeFlagBitsKHR($fOrdVkDeviceGroupPresentModeFlagBitsKHR-$fStorableVkDeviceGroupPresentModeFlagBitsKHR)$fBitsVkDeviceGroupPresentModeFlagBitsKHR/$fFiniteBitsVkDeviceGroupPresentModeFlagBitsKHR$fEqVkPresentInfoKHR$fShowVkPresentInfoKHR!$fEqVkImageSwapchainCreateInfoKHR#$fShowVkImageSwapchainCreateInfoKHR%$fEqVkBindImageMemorySwapchainInfoKHR'$fShowVkBindImageMemorySwapchainInfoKHR$fEqVkAcquireNextImageInfoKHR$fShowVkAcquireNextImageInfoKHR$fEqVkDeviceGroupPresentInfoKHR!$fShowVkDeviceGroupPresentInfoKHR$fEqVkSwapchainCreateInfoKHR$fShowVkSwapchainCreateInfoKHR'$fEqVkDeviceGroupSwapchainCreateInfoKHR)$fShowVkDeviceGroupSwapchainCreateInfoKHR'$fEqVkDeviceGroupPresentCapabilitiesKHR)$fShowVkDeviceGroupPresentCapabilitiesKHR$$sel:vkSType:VkDisplayPresentInfoKHR$$sel:vkPNext:VkDisplayPresentInfoKHR&$sel:vkSrcRect:VkDisplayPresentInfoKHR&$sel:vkDstRect:VkDisplayPresentInfoKHR)$sel:vkPersistent:VkDisplayPresentInfoKHR'VK_KHR_DISPLAY_SWAPCHAIN_EXTENSION_NAME%VK_KHR_DISPLAY_SWAPCHAIN_SPEC_VERSION*VK_STRUCTURE_TYPE_DISPLAY_PRESENT_INFO_KHR!VK_ERROR_INCOMPATIBLE_DISPLAY_KHR!$fStorableVkDisplayPresentInfoKHR$fEqVkDisplayPresentInfoKHR$fShowVkDisplayPresentInfoKHRVkPresentTimeGOOGLE$$sel:vkPresentID:VkPresentTimeGOOGLE-$sel:vkDesiredPresentTime:VkPresentTimeGOOGLE%$sel:vkSType:VkPresentTimesInfoGOOGLE%$sel:vkPNext:VkPresentTimesInfoGOOGLE.$sel:vkSwapchainCount:VkPresentTimesInfoGOOGLE&$sel:vkPTimes:VkPresentTimesInfoGOOGLEVkPastPresentationTimingGOOGLE/$sel:vkPresentID:VkPastPresentationTimingGOOGLE8$sel:vkDesiredPresentTime:VkPastPresentationTimingGOOGLE7$sel:vkActualPresentTime:VkPastPresentationTimingGOOGLE9$sel:vkEarliestPresentTime:VkPastPresentationTimingGOOGLE3$sel:vkPresentMargin:VkPastPresentationTimingGOOGLEVkRefreshCycleDurationGOOGLE3$sel:vkRefreshDuration:VkRefreshCycleDurationGOOGLE'VK_GOOGLE_DISPLAY_TIMING_EXTENSION_NAME%VK_GOOGLE_DISPLAY_TIMING_SPEC_VERSION+VK_STRUCTURE_TYPE_PRESENT_TIMES_INFO_GOOGLE&$fStorableVkRefreshCycleDurationGOOGLE($fStorableVkPastPresentationTimingGOOGLE$fStorableVkPresentTimeGOOGLE"$fStorableVkPresentTimesInfoGOOGLE $fEqVkRefreshCycleDurationGOOGLE"$fShowVkRefreshCycleDurationGOOGLE"$fEqVkPastPresentationTimingGOOGLE$$fShowVkPastPresentationTimingGOOGLE$fEqVkPresentTimeGOOGLE$fShowVkPresentTimeGOOGLE$fEqVkPresentTimesInfoGOOGLE$fShowVkPresentTimesInfoGOOGLE$sel:vkSType:VkHdrMetadataEXT$sel:vkPNext:VkHdrMetadataEXT)$sel:vkDisplayPrimaryRed:VkHdrMetadataEXT+$sel:vkDisplayPrimaryGreen:VkHdrMetadataEXT*$sel:vkDisplayPrimaryBlue:VkHdrMetadataEXT"$sel:vkWhitePoint:VkHdrMetadataEXT$$sel:vkMaxLuminance:VkHdrMetadataEXT$$sel:vkMinLuminance:VkHdrMetadataEXT,$sel:vkMaxContentLightLevel:VkHdrMetadataEXT1$sel:vkMaxFrameAverageLightLevel:VkHdrMetadataEXT VkXYColorEXT$sel:vkX:VkXYColorEXT$sel:vkY:VkXYColorEXT"VK_EXT_HDR_METADATA_EXTENSION_NAME VK_EXT_HDR_METADATA_SPEC_VERSION"VK_STRUCTURE_TYPE_HDR_METADATA_EXT$fStorableVkXYColorEXT$fStorableVkHdrMetadataEXT$fEqVkXYColorEXT$fShowVkXYColorEXT$fEqVkHdrMetadataEXT$fShowVkHdrMetadataEXT,$sel:vkSType:VkSwapchainCounterCreateInfoEXT,$sel:vkPNext:VkSwapchainCounterCreateInfoEXT6$sel:vkSurfaceCounters:VkSwapchainCounterCreateInfoEXT"$sel:vkSType:VkDisplayEventInfoEXT"$sel:vkPNext:VkDisplayEventInfoEXT)$sel:vkDisplayEvent:VkDisplayEventInfoEXT!$sel:vkSType:VkDeviceEventInfoEXT!$sel:vkPNext:VkDeviceEventInfoEXT'$sel:vkDeviceEvent:VkDeviceEventInfoEXT"$sel:vkSType:VkDisplayPowerInfoEXT"$sel:vkPNext:VkDisplayPowerInfoEXT'$sel:vkPowerState:VkDisplayPowerInfoEXTVkDisplayEventTypeEXTVkDeviceEventTypeEXTVkDisplayPowerStateEXT%VK_EXT_DISPLAY_CONTROL_EXTENSION_NAME#VK_EXT_DISPLAY_CONTROL_SPEC_VERSION3VK_STRUCTURE_TYPE_SWAPCHAIN_COUNTER_CREATE_INFO_EXT(VK_STRUCTURE_TYPE_DISPLAY_EVENT_INFO_EXT'VK_STRUCTURE_TYPE_DEVICE_EVENT_INFO_EXT(VK_STRUCTURE_TYPE_DISPLAY_POWER_INFO_EXT)VK_DISPLAY_EVENT_TYPE_FIRST_PIXEL_OUT_EXT(VK_DEVICE_EVENT_TYPE_DISPLAY_HOTPLUG_EXTVK_DISPLAY_POWER_STATE_ON_EXT"VK_DISPLAY_POWER_STATE_SUSPEND_EXTVK_DISPLAY_POWER_STATE_OFF_EXT$fReadVkDisplayPowerStateEXT$fShowVkDisplayPowerStateEXT$fReadVkDeviceEventTypeEXT$fShowVkDeviceEventTypeEXT$fReadVkDisplayEventTypeEXT$fShowVkDisplayEventTypeEXT$fStorableVkDisplayPowerInfoEXT$fStorableVkDeviceEventInfoEXT$fStorableVkDisplayEventInfoEXT)$fStorableVkSwapchainCounterCreateInfoEXT$fEqVkDisplayPowerStateEXT$fOrdVkDisplayPowerStateEXT $fStorableVkDisplayPowerStateEXT$fEqVkDeviceEventTypeEXT$fOrdVkDeviceEventTypeEXT$fStorableVkDeviceEventTypeEXT$fEqVkDisplayEventTypeEXT$fOrdVkDisplayEventTypeEXT$fStorableVkDisplayEventTypeEXT$fEqVkDisplayPowerInfoEXT$fShowVkDisplayPowerInfoEXT$fEqVkDeviceEventInfoEXT$fShowVkDeviceEventInfoEXT$fEqVkDisplayEventInfoEXT$fShowVkDisplayEventInfoEXT#$fEqVkSwapchainCounterCreateInfoEXT%$fShowVkSwapchainCounterCreateInfoEXT2$sel:vkSType:VkSharedPresentSurfaceCapabilitiesKHR2$sel:vkPNext:VkSharedPresentSurfaceCapabilitiesKHRM$sel:vkSharedPresentSupportedUsageFlags:VkSharedPresentSurfaceCapabilitiesKHR.VK_KHR_SHARED_PRESENTABLE_IMAGE_EXTENSION_NAME,VK_KHR_SHARED_PRESENTABLE_IMAGE_SPEC_VERSION-VK_PRESENT_MODE_SHARED_CONTINUOUS_REFRESH_KHR)VK_PRESENT_MODE_SHARED_DEMAND_REFRESH_KHR9VK_STRUCTURE_TYPE_SHARED_PRESENT_SURFACE_CAPABILITIES_KHR"VK_IMAGE_LAYOUT_SHARED_PRESENT_KHR/$fStorableVkSharedPresentSurfaceCapabilitiesKHR)$fEqVkSharedPresentSurfaceCapabilitiesKHR+$fShowVkSharedPresentSurfaceCapabilitiesKHR>$sel:vkSType:VkPipelineTessellationDomainOriginStateCreateInfo>$sel:vkPNext:VkPipelineTessellationDomainOriginStateCreateInfoE$sel:vkDomainOrigin:VkPipelineTessellationDomainOriginStateCreateInfo'$sel:vkSType:VkImageViewUsageCreateInfo'$sel:vkPNext:VkImageViewUsageCreateInfo'$sel:vkUsage:VkImageViewUsageCreateInfo4$sel:vkSType:VkPhysicalDevicePointClippingProperties4$sel:vkPNext:VkPhysicalDevicePointClippingPropertiesD$sel:vkPointClippingBehavior:VkPhysicalDevicePointClippingProperties8$sel:vkSType:VkRenderPassInputAttachmentAspectCreateInfo8$sel:vkPNext:VkRenderPassInputAttachmentAspectCreateInfoG$sel:vkAspectReferenceCount:VkRenderPassInputAttachmentAspectCreateInfoD$sel:vkPAspectReferences:VkRenderPassInputAttachmentAspectCreateInfo/$sel:vkSubpass:VkInputAttachmentAspectReference<$sel:vkInputAttachmentIndex:VkInputAttachmentAspectReference2$sel:vkAspectMask:VkInputAttachmentAspectReferenceVkTessellationDomainOriginVkPointClippingBehavior"VK_IMAGE_CREATE_EXTENDED_USAGE_BIT/VK_IMAGE_CREATE_BLOCK_TEXEL_VIEW_COMPATIBLE_BITGVK_STRUCTURE_TYPE_PIPELINE_TESSELLATION_DOMAIN_ORIGIN_STATE_CREATE_INFO.VK_STRUCTURE_TYPE_IMAGE_VIEW_USAGE_CREATE_INFOAVK_STRUCTURE_TYPE_RENDER_PASS_INPUT_ATTACHMENT_ASPECT_CREATE_INFO;VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_POINT_CLIPPING_PROPERTIES:VK_IMAGE_LAYOUT_DEPTH_ATTACHMENT_STENCIL_READ_ONLY_OPTIMAL:VK_IMAGE_LAYOUT_DEPTH_READ_ONLY_STENCIL_ATTACHMENT_OPTIMAL(VK_TESSELLATION_DOMAIN_ORIGIN_LOWER_LEFT(VK_TESSELLATION_DOMAIN_ORIGIN_UPPER_LEFT0VK_POINT_CLIPPING_BEHAVIOR_USER_CLIP_PLANES_ONLY*VK_POINT_CLIPPING_BEHAVIOR_ALL_CLIP_PLANES$fReadVkPointClippingBehavior$fShowVkPointClippingBehavior $fReadVkTessellationDomainOrigin $fShowVkTessellationDomainOrigin*$fStorableVkInputAttachmentAspectReference5$fStorableVkRenderPassInputAttachmentAspectCreateInfo1$fStorableVkPhysicalDevicePointClippingProperties$$fStorableVkImageViewUsageCreateInfo;$fStorableVkPipelineTessellationDomainOriginStateCreateInfo$fEqVkPointClippingBehavior$fOrdVkPointClippingBehavior!$fStorableVkPointClippingBehavior$fEqVkTessellationDomainOrigin$fOrdVkTessellationDomainOrigin$$fStorableVkTessellationDomainOrigin$$fEqVkInputAttachmentAspectReference&$fShowVkInputAttachmentAspectReference/$fEqVkRenderPassInputAttachmentAspectCreateInfo1$fShowVkRenderPassInputAttachmentAspectCreateInfo+$fEqVkPhysicalDevicePointClippingProperties-$fShowVkPhysicalDevicePointClippingProperties$fEqVkImageViewUsageCreateInfo $fShowVkImageViewUsageCreateInfo5$fEqVkPipelineTessellationDomainOriginStateCreateInfo7$fShowVkPipelineTessellationDomainOriginStateCreateInfo4VkPipelineTessellationDomainOriginStateCreateInfoKHRVkImageViewUsageCreateInfoKHR*VkPhysicalDevicePointClippingPropertiesKHR.VkRenderPassInputAttachmentAspectCreateInfoKHR#VkInputAttachmentAspectReferenceKHRVkTessellationDomainOriginKHRVkPointClippingBehaviorKHR,VK_TESSELLATION_DOMAIN_ORIGIN_LOWER_LEFT_KHR,VK_TESSELLATION_DOMAIN_ORIGIN_UPPER_LEFT_KHR4VK_POINT_CLIPPING_BEHAVIOR_USER_CLIP_PLANES_ONLY_KHR.VK_POINT_CLIPPING_BEHAVIOR_ALL_CLIP_PLANES_KHR>VK_IMAGE_LAYOUT_DEPTH_ATTACHMENT_STENCIL_READ_ONLY_OPTIMAL_KHR>VK_IMAGE_LAYOUT_DEPTH_READ_ONLY_STENCIL_ATTACHMENT_OPTIMAL_KHRKVK_STRUCTURE_TYPE_PIPELINE_TESSELLATION_DOMAIN_ORIGIN_STATE_CREATE_INFO_KHR2VK_STRUCTURE_TYPE_IMAGE_VIEW_USAGE_CREATE_INFO_KHREVK_STRUCTURE_TYPE_RENDER_PASS_INPUT_ATTACHMENT_ASPECT_CREATE_INFO_KHR?VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_POINT_CLIPPING_PROPERTIES_KHR&VK_IMAGE_CREATE_EXTENDED_USAGE_BIT_KHR3VK_IMAGE_CREATE_BLOCK_TEXEL_VIEW_COMPATIBLE_BIT_KHR"VK_KHR_MAINTENANCE2_EXTENSION_NAME VK_KHR_MAINTENANCE2_SPEC_VERSIONVkDependencyFlagsVkAttachmentDescriptionFlagsVkSubpassDescriptionFlags VkAccessFlags$$sel:vkSType:VkFramebufferCreateInfo$$sel:vkPNext:VkFramebufferCreateInfo$$sel:vkFlags:VkFramebufferCreateInfo)$sel:vkRenderPass:VkFramebufferCreateInfo.$sel:vkAttachmentCount:VkFramebufferCreateInfo+$sel:vkPAttachments:VkFramebufferCreateInfo$$sel:vkWidth:VkFramebufferCreateInfo%$sel:vkHeight:VkFramebufferCreateInfo%$sel:vkLayers:VkFramebufferCreateInfo#$sel:vkSType:VkRenderPassCreateInfo#$sel:vkPNext:VkRenderPassCreateInfo#$sel:vkFlags:VkRenderPassCreateInfo-$sel:vkAttachmentCount:VkRenderPassCreateInfo*$sel:vkPAttachments:VkRenderPassCreateInfo*$sel:vkSubpassCount:VkRenderPassCreateInfo($sel:vkPSubpasses:VkRenderPassCreateInfo-$sel:vkDependencyCount:VkRenderPassCreateInfo+$sel:vkPDependencies:VkRenderPassCreateInfo%$sel:vkSrcSubpass:VkSubpassDependency%$sel:vkDstSubpass:VkSubpassDependency'$sel:vkSrcStageMask:VkSubpassDependency'$sel:vkDstStageMask:VkSubpassDependency($sel:vkSrcAccessMask:VkSubpassDependency($sel:vkDstAccessMask:VkSubpassDependency*$sel:vkDependencyFlags:VkSubpassDependency!$sel:vkFlags:VkSubpassDescription-$sel:vkPipelineBindPoint:VkSubpassDescription0$sel:vkInputAttachmentCount:VkSubpassDescription-$sel:vkPInputAttachments:VkSubpassDescription0$sel:vkColorAttachmentCount:VkSubpassDescription-$sel:vkPColorAttachments:VkSubpassDescription/$sel:vkPResolveAttachments:VkSubpassDescription3$sel:vkPDepthStencilAttachment:VkSubpassDescription3$sel:vkPreserveAttachmentCount:VkSubpassDescription0$sel:vkPPreserveAttachments:VkSubpassDescription'$sel:vkAttachment:VkAttachmentReference#$sel:vkLayout:VkAttachmentReference$$sel:vkFlags:VkAttachmentDescription%$sel:vkFormat:VkAttachmentDescription&$sel:vkSamples:VkAttachmentDescription%$sel:vkLoadOp:VkAttachmentDescription&$sel:vkStoreOp:VkAttachmentDescription,$sel:vkStencilLoadOp:VkAttachmentDescription-$sel:vkStencilStoreOp:VkAttachmentDescription,$sel:vkInitialLayout:VkAttachmentDescription*$sel:vkFinalLayout:VkAttachmentDescriptionVkDependencyFlagBitsVkAttachmentDescriptionFlagBitsVkSubpassDescriptionFlagBitsVkRenderPassCreateFlagsVkFramebufferCreateFlagsVkPipelineBindPointVkAttachmentStoreOpVkAttachmentLoadOpVK_DEPENDENCY_BY_REGION_BIT'VK_ATTACHMENT_DESCRIPTION_MAY_ALIAS_BITVK_ACCESS_MEMORY_WRITE_BITVK_ACCESS_MEMORY_READ_BITVK_ACCESS_HOST_WRITE_BITVK_ACCESS_HOST_READ_BITVK_ACCESS_TRANSFER_WRITE_BITVK_ACCESS_TRANSFER_READ_BIT,VK_ACCESS_DEPTH_STENCIL_ATTACHMENT_WRITE_BIT+VK_ACCESS_DEPTH_STENCIL_ATTACHMENT_READ_BIT$VK_ACCESS_COLOR_ATTACHMENT_WRITE_BIT#VK_ACCESS_COLOR_ATTACHMENT_READ_BITVK_ACCESS_SHADER_WRITE_BITVK_ACCESS_SHADER_READ_BIT#VK_ACCESS_INPUT_ATTACHMENT_READ_BITVK_ACCESS_UNIFORM_READ_BIT#VK_ACCESS_VERTEX_ATTRIBUTE_READ_BITVK_ACCESS_INDEX_READ_BIT#VK_ACCESS_INDIRECT_COMMAND_READ_BITVK_PIPELINE_BIND_POINT_COMPUTEVK_PIPELINE_BIND_POINT_GRAPHICS VK_ATTACHMENT_STORE_OP_DONT_CAREVK_ATTACHMENT_STORE_OP_STOREVK_ATTACHMENT_LOAD_OP_DONT_CAREVK_ATTACHMENT_LOAD_OP_CLEARVK_ATTACHMENT_LOAD_OP_LOAD$fReadVkAttachmentLoadOp$fShowVkAttachmentLoadOp$fReadVkAttachmentStoreOp$fShowVkAttachmentStoreOp$fReadVkPipelineBindPoint$fShowVkPipelineBindPoint$fReadVkFramebufferCreateFlags$fShowVkFramebufferCreateFlags$fReadVkRenderPassCreateFlags$fShowVkRenderPassCreateFlags$fReadVkAccessFlagBits$fShowVkAccessFlagBits"$fReadVkSubpassDescriptionFlagBits"$fShowVkSubpassDescriptionFlagBits%$fReadVkAttachmentDescriptionFlagBits%$fShowVkAttachmentDescriptionFlagBits$fReadVkDependencyFlagBits$fShowVkDependencyFlagBits$fStorableVkAttachmentReference!$fStorableVkFramebufferCreateInfo$fStorableVkSubpassDescription!$fStorableVkAttachmentDescription$fStorableVkSubpassDependency $fStorableVkRenderPassCreateInfo$fEqVkAttachmentLoadOp$fOrdVkAttachmentLoadOp$fStorableVkAttachmentLoadOp$fEqVkAttachmentStoreOp$fOrdVkAttachmentStoreOp$fStorableVkAttachmentStoreOp$fEqVkPipelineBindPoint$fOrdVkPipelineBindPoint$fStorableVkPipelineBindPoint$fEqVkFramebufferCreateFlags$fOrdVkFramebufferCreateFlags"$fStorableVkFramebufferCreateFlags$fBitsVkFramebufferCreateFlags$$fFiniteBitsVkFramebufferCreateFlags$fEqVkRenderPassCreateFlags$fOrdVkRenderPassCreateFlags!$fStorableVkRenderPassCreateFlags$fBitsVkRenderPassCreateFlags#$fFiniteBitsVkRenderPassCreateFlags$fEqVkAccessFlagBits$fOrdVkAccessFlagBits$fStorableVkAccessFlagBits$fBitsVkAccessFlagBits$fFiniteBitsVkAccessFlagBits $fEqVkSubpassDescriptionFlagBits!$fOrdVkSubpassDescriptionFlagBits&$fStorableVkSubpassDescriptionFlagBits"$fBitsVkSubpassDescriptionFlagBits($fFiniteBitsVkSubpassDescriptionFlagBits#$fEqVkAttachmentDescriptionFlagBits$$fOrdVkAttachmentDescriptionFlagBits)$fStorableVkAttachmentDescriptionFlagBits%$fBitsVkAttachmentDescriptionFlagBits+$fFiniteBitsVkAttachmentDescriptionFlagBits$fEqVkDependencyFlagBits$fOrdVkDependencyFlagBits$fStorableVkDependencyFlagBits$fBitsVkDependencyFlagBits $fFiniteBitsVkDependencyFlagBits$fEqVkAttachmentReference$fShowVkAttachmentReference$fEqVkFramebufferCreateInfo$fShowVkFramebufferCreateInfo$fEqVkSubpassDescription$fShowVkSubpassDescription$fEqVkAttachmentDescription$fShowVkAttachmentDescription$fEqVkSubpassDependency$fShowVkSubpassDependency$fEqVkRenderPassCreateInfo$fShowVkRenderPassCreateInfoD$sel:vkSType:VkPhysicalDeviceMultiviewPerViewAttributesPropertiesNVXD$sel:vkPNext:VkPhysicalDeviceMultiviewPerViewAttributesPropertiesNVX[$sel:vkPerViewPositionAllComponents:VkPhysicalDeviceMultiviewPerViewAttributesPropertiesNVX3VK_NVX_MULTIVIEW_PER_VIEW_ATTRIBUTES_EXTENSION_NAME1VK_NVX_MULTIVIEW_PER_VIEW_ATTRIBUTES_SPEC_VERSION7VK_SUBPASS_DESCRIPTION_PER_VIEW_POSITION_X_ONLY_BIT_NVX2VK_SUBPASS_DESCRIPTION_PER_VIEW_ATTRIBUTES_BIT_NVXNVK_STRUCTURE_TYPE_PHYSICAL_DEVICE_MULTIVIEW_PER_VIEW_ATTRIBUTES_PROPERTIES_NVXA$fStorableVkPhysicalDeviceMultiviewPerViewAttributesPropertiesNVX;$fEqVkPhysicalDeviceMultiviewPerViewAttributesPropertiesNVX=$fShowVkPhysicalDeviceMultiviewPerViewAttributesPropertiesNVX;$sel:vkSType:VkPipelineColorBlendAdvancedStateCreateInfoEXT;$sel:vkPNext:VkPipelineColorBlendAdvancedStateCreateInfoEXTF$sel:vkSrcPremultiplied:VkPipelineColorBlendAdvancedStateCreateInfoEXTF$sel:vkDstPremultiplied:VkPipelineColorBlendAdvancedStateCreateInfoEXTB$sel:vkBlendOverlap:VkPipelineColorBlendAdvancedStateCreateInfoEXT@$sel:vkSType:VkPhysicalDeviceBlendOperationAdvancedPropertiesEXT@$sel:vkPNext:VkPhysicalDeviceBlendOperationAdvancedPropertiesEXT[$sel:vkAdvancedBlendMaxColorAttachments:VkPhysicalDeviceBlendOperationAdvancedPropertiesEXTX$sel:vkAdvancedBlendIndependentBlend:VkPhysicalDeviceBlendOperationAdvancedPropertiesEXT`$sel:vkAdvancedBlendNonPremultipliedSrcColor:VkPhysicalDeviceBlendOperationAdvancedPropertiesEXT`$sel:vkAdvancedBlendNonPremultipliedDstColor:VkPhysicalDeviceBlendOperationAdvancedPropertiesEXTY$sel:vkAdvancedBlendCorrelatedOverlap:VkPhysicalDeviceBlendOperationAdvancedPropertiesEXTU$sel:vkAdvancedBlendAllOperations:VkPhysicalDeviceBlendOperationAdvancedPropertiesEXT>$sel:vkSType:VkPhysicalDeviceBlendOperationAdvancedFeaturesEXT>$sel:vkPNext:VkPhysicalDeviceBlendOperationAdvancedFeaturesEXTX$sel:vkAdvancedBlendCoherentOperations:VkPhysicalDeviceBlendOperationAdvancedFeaturesEXTVkBlendOverlapEXT.VK_EXT_BLEND_OPERATION_ADVANCED_EXTENSION_NAME,VK_EXT_BLEND_OPERATION_ADVANCED_SPEC_VERSION3VK_ACCESS_COLOR_ATTACHMENT_READ_NONCOHERENT_BIT_EXTEVK_STRUCTURE_TYPE_PIPELINE_COLOR_BLEND_ADVANCED_STATE_CREATE_INFO_EXTIVK_STRUCTURE_TYPE_PHYSICAL_DEVICE_BLEND_OPERATION_ADVANCED_PROPERTIES_EXTGVK_STRUCTURE_TYPE_PHYSICAL_DEVICE_BLEND_OPERATION_ADVANCED_FEATURES_EXTVK_BLEND_OP_BLUE_EXTVK_BLEND_OP_GREEN_EXTVK_BLEND_OP_RED_EXTVK_BLEND_OP_INVERT_OVG_EXTVK_BLEND_OP_CONTRAST_EXTVK_BLEND_OP_MINUS_CLAMPED_EXTVK_BLEND_OP_MINUS_EXTVK_BLEND_OP_PLUS_DARKER_EXT"VK_BLEND_OP_PLUS_CLAMPED_ALPHA_EXTVK_BLEND_OP_PLUS_CLAMPED_EXTVK_BLEND_OP_PLUS_EXTVK_BLEND_OP_HSL_LUMINOSITY_EXTVK_BLEND_OP_HSL_COLOR_EXTVK_BLEND_OP_HSL_SATURATION_EXTVK_BLEND_OP_HSL_HUE_EXTVK_BLEND_OP_HARDMIX_EXTVK_BLEND_OP_PINLIGHT_EXTVK_BLEND_OP_LINEARLIGHT_EXTVK_BLEND_OP_VIVIDLIGHT_EXTVK_BLEND_OP_LINEARBURN_EXTVK_BLEND_OP_LINEARDODGE_EXTVK_BLEND_OP_INVERT_RGB_EXTVK_BLEND_OP_INVERT_EXTVK_BLEND_OP_EXCLUSION_EXTVK_BLEND_OP_DIFFERENCE_EXTVK_BLEND_OP_SOFTLIGHT_EXTVK_BLEND_OP_HARDLIGHT_EXTVK_BLEND_OP_COLORBURN_EXTVK_BLEND_OP_COLORDODGE_EXTVK_BLEND_OP_LIGHTEN_EXTVK_BLEND_OP_DARKEN_EXTVK_BLEND_OP_OVERLAY_EXTVK_BLEND_OP_SCREEN_EXTVK_BLEND_OP_MULTIPLY_EXTVK_BLEND_OP_XOR_EXTVK_BLEND_OP_DST_ATOP_EXTVK_BLEND_OP_SRC_ATOP_EXTVK_BLEND_OP_DST_OUT_EXTVK_BLEND_OP_SRC_OUT_EXTVK_BLEND_OP_DST_IN_EXTVK_BLEND_OP_SRC_IN_EXTVK_BLEND_OP_DST_OVER_EXTVK_BLEND_OP_SRC_OVER_EXTVK_BLEND_OP_DST_EXTVK_BLEND_OP_SRC_EXTVK_BLEND_OP_ZERO_EXTVK_BLEND_OVERLAP_CONJOINT_EXTVK_BLEND_OVERLAP_DISJOINT_EXT!VK_BLEND_OVERLAP_UNCORRELATED_EXT$fReadVkBlendOverlapEXT$fShowVkBlendOverlapEXT;$fStorableVkPhysicalDeviceBlendOperationAdvancedFeaturesEXT=$fStorableVkPhysicalDeviceBlendOperationAdvancedPropertiesEXT8$fStorableVkPipelineColorBlendAdvancedStateCreateInfoEXT$fEqVkBlendOverlapEXT$fOrdVkBlendOverlapEXT$fStorableVkBlendOverlapEXT5$fEqVkPhysicalDeviceBlendOperationAdvancedFeaturesEXT7$fShowVkPhysicalDeviceBlendOperationAdvancedFeaturesEXT7$fEqVkPhysicalDeviceBlendOperationAdvancedPropertiesEXT9$fShowVkPhysicalDeviceBlendOperationAdvancedPropertiesEXT2$fEqVkPipelineColorBlendAdvancedStateCreateInfoEXT4$fShowVkPipelineColorBlendAdvancedStateCreateInfoEXT,$sel:vkSType:VkRenderPassMultiviewCreateInfo,$sel:vkPNext:VkRenderPassMultiviewCreateInfo3$sel:vkSubpassCount:VkRenderPassMultiviewCreateInfo1$sel:vkPViewMasks:VkRenderPassMultiviewCreateInfo6$sel:vkDependencyCount:VkRenderPassMultiviewCreateInfo3$sel:vkPViewOffsets:VkRenderPassMultiviewCreateInfo;$sel:vkCorrelationMaskCount:VkRenderPassMultiviewCreateInfo8$sel:vkPCorrelationMasks:VkRenderPassMultiviewCreateInfo0$sel:vkSType:VkPhysicalDeviceMultiviewProperties0$sel:vkPNext:VkPhysicalDeviceMultiviewProperties@$sel:vkMaxMultiviewViewCount:VkPhysicalDeviceMultiviewPropertiesD$sel:vkMaxMultiviewInstanceIndex:VkPhysicalDeviceMultiviewProperties.$sel:vkSType:VkPhysicalDeviceMultiviewFeatures.$sel:vkPNext:VkPhysicalDeviceMultiviewFeatures2$sel:vkMultiview:VkPhysicalDeviceMultiviewFeatures@$sel:vkMultiviewGeometryShader:VkPhysicalDeviceMultiviewFeaturesD$sel:vkMultiviewTessellationShader:VkPhysicalDeviceMultiviewFeaturesVK_DEPENDENCY_VIEW_LOCAL_BIT6VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_MULTIVIEW_PROPERTIES4VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_MULTIVIEW_FEATURES3VK_STRUCTURE_TYPE_RENDER_PASS_MULTIVIEW_CREATE_INFO+$fStorableVkPhysicalDeviceMultiviewFeatures-$fStorableVkPhysicalDeviceMultiviewProperties)$fStorableVkRenderPassMultiviewCreateInfo%$fEqVkPhysicalDeviceMultiviewFeatures'$fShowVkPhysicalDeviceMultiviewFeatures'$fEqVkPhysicalDeviceMultiviewProperties)$fShowVkPhysicalDeviceMultiviewProperties#$fEqVkRenderPassMultiviewCreateInfo%$fShowVkRenderPassMultiviewCreateInfo"VkRenderPassMultiviewCreateInfoKHR&VkPhysicalDeviceMultiviewPropertiesKHR$VkPhysicalDeviceMultiviewFeaturesKHR VK_DEPENDENCY_VIEW_LOCAL_BIT_KHR:VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_MULTIVIEW_PROPERTIES_KHR8VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_MULTIVIEW_FEATURES_KHR7VK_STRUCTURE_TYPE_RENDER_PASS_MULTIVIEW_CREATE_INFO_KHRVK_KHR_MULTIVIEW_EXTENSION_NAMEVK_KHR_MULTIVIEW_SPEC_VERSIONVkMemoryAllocateFlagsVkPeerMemoryFeatureFlags($sel:vkSType:VkDeviceGroupBindSparseInfo($sel:vkPNext:VkDeviceGroupBindSparseInfo6$sel:vkResourceDeviceIndex:VkDeviceGroupBindSparseInfo4$sel:vkMemoryDeviceIndex:VkDeviceGroupBindSparseInfo$$sel:vkSType:VkDeviceGroupSubmitInfo$$sel:vkPNext:VkDeviceGroupSubmitInfo1$sel:vkWaitSemaphoreCount:VkDeviceGroupSubmitInfo:$sel:vkPWaitSemaphoreDeviceIndices:VkDeviceGroupSubmitInfo1$sel:vkCommandBufferCount:VkDeviceGroupSubmitInfo8$sel:vkPCommandBufferDeviceMasks:VkDeviceGroupSubmitInfo3$sel:vkSignalSemaphoreCount:VkDeviceGroupSubmitInfo<$sel:vkPSignalSemaphoreDeviceIndices:VkDeviceGroupSubmitInfo0$sel:vkSType:VkDeviceGroupCommandBufferBeginInfo0$sel:vkPNext:VkDeviceGroupCommandBufferBeginInfo5$sel:vkDeviceMask:VkDeviceGroupCommandBufferBeginInfo-$sel:vkSType:VkDeviceGroupRenderPassBeginInfo-$sel:vkPNext:VkDeviceGroupRenderPassBeginInfo2$sel:vkDeviceMask:VkDeviceGroupRenderPassBeginInfo=$sel:vkDeviceRenderAreaCount:VkDeviceGroupRenderPassBeginInfo:$sel:vkPDeviceRenderAreas:VkDeviceGroupRenderPassBeginInfo&$sel:vkSType:VkMemoryAllocateFlagsInfo&$sel:vkPNext:VkMemoryAllocateFlagsInfo&$sel:vkFlags:VkMemoryAllocateFlagsInfo+$sel:vkDeviceMask:VkMemoryAllocateFlagsInfoVkMemoryAllocateFlagBitsVkPeerMemoryFeatureFlagBitsVK_DEPENDENCY_DEVICE_GROUP_BIT VK_PIPELINE_CREATE_DISPATCH_BASE3VK_PIPELINE_CREATE_VIEW_INDEX_FROM_DEVICE_INDEX_BIT/VK_STRUCTURE_TYPE_DEVICE_GROUP_BIND_SPARSE_INFO*VK_STRUCTURE_TYPE_DEVICE_GROUP_SUBMIT_INFO8VK_STRUCTURE_TYPE_DEVICE_GROUP_COMMAND_BUFFER_BEGIN_INFO5VK_STRUCTURE_TYPE_DEVICE_GROUP_RENDER_PASS_BEGIN_INFO,VK_STRUCTURE_TYPE_MEMORY_ALLOCATE_FLAGS_INFO"VK_MEMORY_ALLOCATE_DEVICE_MASK_BIT&VK_PEER_MEMORY_FEATURE_GENERIC_DST_BIT&VK_PEER_MEMORY_FEATURE_GENERIC_SRC_BIT#VK_PEER_MEMORY_FEATURE_COPY_DST_BIT#VK_PEER_MEMORY_FEATURE_COPY_SRC_BIT!$fReadVkPeerMemoryFeatureFlagBits!$fShowVkPeerMemoryFeatureFlagBits$fReadVkMemoryAllocateFlagBits$fShowVkMemoryAllocateFlagBits*$fStorableVkDeviceGroupRenderPassBeginInfo-$fStorableVkDeviceGroupCommandBufferBeginInfo!$fStorableVkDeviceGroupSubmitInfo%$fStorableVkDeviceGroupBindSparseInfo#$fStorableVkMemoryAllocateFlagsInfo$fEqVkPeerMemoryFeatureFlagBits $fOrdVkPeerMemoryFeatureFlagBits%$fStorableVkPeerMemoryFeatureFlagBits!$fBitsVkPeerMemoryFeatureFlagBits'$fFiniteBitsVkPeerMemoryFeatureFlagBits$fEqVkMemoryAllocateFlagBits$fOrdVkMemoryAllocateFlagBits"$fStorableVkMemoryAllocateFlagBits$fBitsVkMemoryAllocateFlagBits$$fFiniteBitsVkMemoryAllocateFlagBits$$fEqVkDeviceGroupRenderPassBeginInfo&$fShowVkDeviceGroupRenderPassBeginInfo'$fEqVkDeviceGroupCommandBufferBeginInfo)$fShowVkDeviceGroupCommandBufferBeginInfo$fEqVkDeviceGroupSubmitInfo$fShowVkDeviceGroupSubmitInfo$fEqVkDeviceGroupBindSparseInfo!$fShowVkDeviceGroupBindSparseInfo$fEqVkMemoryAllocateFlagsInfo$fShowVkMemoryAllocateFlagsInfoVkDeviceGroupBindSparseInfoKHRVkDeviceGroupSubmitInfoKHR&VkDeviceGroupCommandBufferBeginInfoKHR#VkDeviceGroupRenderPassBeginInfoKHR#VkBindImageMemoryDeviceGroupInfoKHR$VkBindBufferMemoryDeviceGroupInfoKHRVkMemoryAllocateFlagsInfoKHRVkMemoryAllocateFlagsKHRVkPeerMemoryFeatureFlagsKHRVkMemoryAllocateFlagBitsKHRVkPeerMemoryFeatureFlagBitsKHR3VK_IMAGE_CREATE_SPLIT_INSTANCE_BIND_REGIONS_BIT_KHR9VK_STRUCTURE_TYPE_BIND_IMAGE_MEMORY_DEVICE_GROUP_INFO_KHR:VK_STRUCTURE_TYPE_BIND_BUFFER_MEMORY_DEVICE_GROUP_INFO_KHR"VK_DEPENDENCY_DEVICE_GROUP_BIT_KHR$VK_PIPELINE_CREATE_DISPATCH_BASE_KHR7VK_PIPELINE_CREATE_VIEW_INDEX_FROM_DEVICE_INDEX_BIT_KHR&VK_MEMORY_ALLOCATE_DEVICE_MASK_BIT_KHR*VK_PEER_MEMORY_FEATURE_GENERIC_DST_BIT_KHR*VK_PEER_MEMORY_FEATURE_GENERIC_SRC_BIT_KHR'VK_PEER_MEMORY_FEATURE_COPY_DST_BIT_KHR'VK_PEER_MEMORY_FEATURE_COPY_SRC_BIT_KHR3VK_STRUCTURE_TYPE_DEVICE_GROUP_BIND_SPARSE_INFO_KHR.VK_STRUCTURE_TYPE_DEVICE_GROUP_SUBMIT_INFO_KHRVK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT_EXTMVK_STRUCTURE_TYPE_DESCRIPTOR_SET_VARIABLE_DESCRIPTOR_COUNT_LAYOUT_SUPPORT_EXTLVK_STRUCTURE_TYPE_DESCRIPTOR_SET_VARIABLE_DESCRIPTOR_COUNT_ALLOCATE_INFO_EXTDVK_STRUCTURE_TYPE_PHYSICAL_DEVICE_DESCRIPTOR_INDEXING_PROPERTIES_EXTBVK_STRUCTURE_TYPE_PHYSICAL_DEVICE_DESCRIPTOR_INDEXING_FEATURES_EXTEVK_STRUCTURE_TYPE_DESCRIPTOR_SET_LAYOUT_BINDING_FLAGS_CREATE_INFO_EXTVK_ERROR_FRAGMENTATION_EXT7VK_DESCRIPTOR_BINDING_VARIABLE_DESCRIPTOR_COUNT_BIT_EXT-VK_DESCRIPTOR_BINDING_PARTIALLY_BOUND_BIT_EXT9VK_DESCRIPTOR_BINDING_UPDATE_UNUSED_WHILE_PENDING_BIT_EXT/VK_DESCRIPTOR_BINDING_UPDATE_AFTER_BIND_BIT_EXT$$fReadVkDescriptorBindingFlagBitsEXT$$fShowVkDescriptorBindingFlagBitsEXT7$fStorableVkPhysicalDeviceDescriptorIndexingFeaturesEXT9$fStorableVkPhysicalDeviceDescriptorIndexingPropertiesEXT?$fStorableVkDescriptorSetVariableDescriptorCountAllocateInfoEXT@$fStorableVkDescriptorSetVariableDescriptorCountLayoutSupportEXT8$fStorableVkDescriptorSetLayoutBindingFlagsCreateInfoEXT"$fEqVkDescriptorBindingFlagBitsEXT#$fOrdVkDescriptorBindingFlagBitsEXT($fStorableVkDescriptorBindingFlagBitsEXT$$fBitsVkDescriptorBindingFlagBitsEXT*$fFiniteBitsVkDescriptorBindingFlagBitsEXT1$fEqVkPhysicalDeviceDescriptorIndexingFeaturesEXT3$fShowVkPhysicalDeviceDescriptorIndexingFeaturesEXT3$fEqVkPhysicalDeviceDescriptorIndexingPropertiesEXT5$fShowVkPhysicalDeviceDescriptorIndexingPropertiesEXT9$fEqVkDescriptorSetVariableDescriptorCountAllocateInfoEXT;$fShowVkDescriptorSetVariableDescriptorCountAllocateInfoEXT:$fEqVkDescriptorSetVariableDescriptorCountLayoutSupportEXT<$fShowVkDescriptorSetVariableDescriptorCountLayoutSupportEXT2$fEqVkDescriptorSetLayoutBindingFlagsCreateInfoEXT4$fShowVkDescriptorSetLayoutBindingFlagsCreateInfoEXT)$sel:vkSType:VkDescriptorSetLayoutSupport)$sel:vkPNext:VkDescriptorSetLayoutSupport-$sel:vkSupported:VkDescriptorSetLayoutSupport3$sel:vkSType:VkPhysicalDeviceMaintenance3Properties3$sel:vkPNext:VkPhysicalDeviceMaintenance3PropertiesB$sel:vkMaxPerSetDescriptors:VkPhysicalDeviceMaintenance3PropertiesE$sel:vkMaxMemoryAllocationSize:VkPhysicalDeviceMaintenance3Properties/VK_STRUCTURE_TYPE_DESCRIPTOR_SET_LAYOUT_SUPPORT:VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_MAINTENANCE_3_PROPERTIES0$fStorableVkPhysicalDeviceMaintenance3Properties&$fStorableVkDescriptorSetLayoutSupport*$fEqVkPhysicalDeviceMaintenance3Properties,$fShowVkPhysicalDeviceMaintenance3Properties $fEqVkDescriptorSetLayoutSupport"$fShowVkDescriptorSetLayoutSupportVkDescriptorSetLayoutSupportKHR)VkPhysicalDeviceMaintenance3PropertiesKHR3VK_STRUCTURE_TYPE_DESCRIPTOR_SET_LAYOUT_SUPPORT_KHR>VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_MAINTENANCE_3_PROPERTIES_KHR"VK_KHR_MAINTENANCE3_EXTENSION_NAME VK_KHR_MAINTENANCE3_SPEC_VERSION1$sel:vkSType:VkDescriptorUpdateTemplateCreateInfo1$sel:vkPNext:VkDescriptorUpdateTemplateCreateInfo1$sel:vkFlags:VkDescriptorUpdateTemplateCreateInfoF$sel:vkDescriptorUpdateEntryCount:VkDescriptorUpdateTemplateCreateInfoD$sel:vkPDescriptorUpdateEntries:VkDescriptorUpdateTemplateCreateInfo8$sel:vkTemplateType:VkDescriptorUpdateTemplateCreateInfo?$sel:vkDescriptorSetLayout:VkDescriptorUpdateTemplateCreateInfo=$sel:vkPipelineBindPoint:VkDescriptorUpdateTemplateCreateInfo:$sel:vkPipelineLayout:VkDescriptorUpdateTemplateCreateInfo/$sel:vkSet:VkDescriptorUpdateTemplateCreateInfo1$sel:vkDstBinding:VkDescriptorUpdateTemplateEntry6$sel:vkDstArrayElement:VkDescriptorUpdateTemplateEntry6$sel:vkDescriptorCount:VkDescriptorUpdateTemplateEntry5$sel:vkDescriptorType:VkDescriptorUpdateTemplateEntry-$sel:vkOffset:VkDescriptorUpdateTemplateEntry-$sel:vkStride:VkDescriptorUpdateTemplateEntry%VkDescriptorUpdateTemplateCreateFlagsVkDescriptorUpdateTemplateType)VK_OBJECT_TYPE_DESCRIPTOR_UPDATE_TEMPLATE8VK_STRUCTURE_TYPE_DESCRIPTOR_UPDATE_TEMPLATE_CREATE_INFO1VK_DESCRIPTOR_UPDATE_TEMPLATE_TYPE_DESCRIPTOR_SET$$fReadVkDescriptorUpdateTemplateType$$fShowVkDescriptorUpdateTemplateType+$fReadVkDescriptorUpdateTemplateCreateFlags+$fShowVkDescriptorUpdateTemplateCreateFlags)$fStorableVkDescriptorUpdateTemplateEntry.$fStorableVkDescriptorUpdateTemplateCreateInfo"$fEqVkDescriptorUpdateTemplateType#$fOrdVkDescriptorUpdateTemplateType($fStorableVkDescriptorUpdateTemplateType)$fEqVkDescriptorUpdateTemplateCreateFlags*$fOrdVkDescriptorUpdateTemplateCreateFlags/$fStorableVkDescriptorUpdateTemplateCreateFlags+$fBitsVkDescriptorUpdateTemplateCreateFlags1$fFiniteBitsVkDescriptorUpdateTemplateCreateFlags#$fEqVkDescriptorUpdateTemplateEntry%$fShowVkDescriptorUpdateTemplateEntry($fEqVkDescriptorUpdateTemplateCreateInfo*$fShowVkDescriptorUpdateTemplateCreateInfo8$sel:vkSType:VkPhysicalDevicePushDescriptorPropertiesKHR8$sel:vkPNext:VkPhysicalDevicePushDescriptorPropertiesKHRE$sel:vkMaxPushDescriptors:VkPhysicalDevicePushDescriptorPropertiesKHR%VK_KHR_PUSH_DESCRIPTOR_EXTENSION_NAME#VK_KHR_PUSH_DESCRIPTOR_SPEC_VERSION7VK_DESCRIPTOR_SET_LAYOUT_CREATE_PUSH_DESCRIPTOR_BIT_KHR7VK_DESCRIPTOR_UPDATE_TEMPLATE_TYPE_PUSH_DESCRIPTORS_KHR@VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_PUSH_DESCRIPTOR_PROPERTIES_KHR5$fStorableVkPhysicalDevicePushDescriptorPropertiesKHR/$fEqVkPhysicalDevicePushDescriptorPropertiesKHR1$fShowVkPhysicalDevicePushDescriptorPropertiesKHR'VkDescriptorUpdateTemplateCreateInfoKHR"VkDescriptorUpdateTemplateEntryKHRVkDescriptorUpdateTemplateKHR(VkDescriptorUpdateTemplateCreateFlagsKHR!VkDescriptorUpdateTemplateTypeKHR>VK_DEBUG_REPORT_OBJECT_TYPE_DESCRIPTOR_UPDATE_TEMPLATE_KHR_EXT5VK_DESCRIPTOR_UPDATE_TEMPLATE_TYPE_DESCRIPTOR_SET_KHR-VK_OBJECT_TYPE_DESCRIPTOR_UPDATE_TEMPLATE_KHR$sel:vkPipelineBindPoint:VkIndirectCommandsLayoutCreateInfoNVX2$sel:vkFlags:VkIndirectCommandsLayoutCreateInfoNVX7$sel:vkTokenCount:VkIndirectCommandsLayoutCreateInfoNVX4$sel:vkPTokens:VkIndirectCommandsLayoutCreateInfoNVX VkIndirectCommandsLayoutTokenNVX1$sel:vkTokenType:VkIndirectCommandsLayoutTokenNVX3$sel:vkBindingUnit:VkIndirectCommandsLayoutTokenNVX4$sel:vkDynamicCount:VkIndirectCommandsLayoutTokenNVX/$sel:vkDivisor:VkIndirectCommandsLayoutTokenNVX+$sel:vkTokenType:VkIndirectCommandsTokenNVX($sel:vkBuffer:VkIndirectCommandsTokenNVX($sel:vkOffset:VkIndirectCommandsTokenNVX/$sel:vkSType:VkDeviceGeneratedCommandsLimitsNVX/$sel:vkPNext:VkDeviceGeneratedCommandsLimitsNVXM$sel:vkMaxIndirectCommandsLayoutTokenCount:VkDeviceGeneratedCommandsLimitsNVX>$sel:vkMaxObjectEntryCounts:VkDeviceGeneratedCommandsLimitsNVXO$sel:vkMinSequenceCountBufferOffsetAlignment:VkDeviceGeneratedCommandsLimitsNVXO$sel:vkMinSequenceIndexBufferOffsetAlignment:VkDeviceGeneratedCommandsLimitsNVXO$sel:vkMinCommandsTokenBufferOffsetAlignment:VkDeviceGeneratedCommandsLimitsNVX1$sel:vkSType:VkDeviceGeneratedCommandsFeaturesNVX1$sel:vkPNext:VkDeviceGeneratedCommandsFeaturesNVXF$sel:vkComputeBindingPointSupport:VkDeviceGeneratedCommandsFeaturesNVXVkObjectEntryUsageFlagBitsNVX(VkIndirectCommandsLayoutUsageFlagBitsNVXVkObjectEntryTypeNVXVkIndirectCommandsTokenTypeNVX/VK_NVX_DEVICE_GENERATED_COMMANDS_EXTENSION_NAME-VK_NVX_DEVICE_GENERATED_COMMANDS_SPEC_VERSION)VK_PIPELINE_STAGE_COMMAND_PROCESS_BIT_NVX'VK_ACCESS_COMMAND_PROCESS_WRITE_BIT_NVX&VK_ACCESS_COMMAND_PROCESS_READ_BIT_NVX+VK_OBJECT_TYPE_INDIRECT_COMMANDS_LAYOUT_NVXVK_OBJECT_TYPE_OBJECT_TABLE_NVX8VK_STRUCTURE_TYPE_DEVICE_GENERATED_COMMANDS_FEATURES_NVX6VK_STRUCTURE_TYPE_DEVICE_GENERATED_COMMANDS_LIMITS_NVX9VK_STRUCTURE_TYPE_CMD_RESERVE_SPACE_FOR_COMMANDS_INFO_NVX/VK_STRUCTURE_TYPE_CMD_PROCESS_COMMANDS_INFO_NVX:VK_STRUCTURE_TYPE_INDIRECT_COMMANDS_LAYOUT_CREATE_INFO_NVX.VK_STRUCTURE_TYPE_OBJECT_TABLE_CREATE_INFO_NVX%VK_OBJECT_ENTRY_USAGE_COMPUTE_BIT_NVX&VK_OBJECT_ENTRY_USAGE_GRAPHICS_BIT_NVX;VK_INDIRECT_COMMANDS_LAYOUT_USAGE_INDEXED_SEQUENCES_BIT_NVX:VK_INDIRECT_COMMANDS_LAYOUT_USAGE_EMPTY_EXECUTIONS_BIT_NVX:VK_INDIRECT_COMMANDS_LAYOUT_USAGE_SPARSE_SEQUENCES_BIT_NVX=VK_INDIRECT_COMMANDS_LAYOUT_USAGE_UNORDERED_SEQUENCES_BIT_NVX&VK_OBJECT_ENTRY_TYPE_PUSH_CONSTANT_NVX&VK_OBJECT_ENTRY_TYPE_VERTEX_BUFFER_NVX%VK_OBJECT_ENTRY_TYPE_INDEX_BUFFER_NVX!VK_OBJECT_ENTRY_TYPE_PIPELINE_NVX'VK_OBJECT_ENTRY_TYPE_DESCRIPTOR_SET_NVX,VK_INDIRECT_COMMANDS_TOKEN_TYPE_DISPATCH_NVX(VK_INDIRECT_COMMANDS_TOKEN_TYPE_DRAW_NVX0VK_INDIRECT_COMMANDS_TOKEN_TYPE_DRAW_INDEXED_NVX1VK_INDIRECT_COMMANDS_TOKEN_TYPE_PUSH_CONSTANT_NVX1VK_INDIRECT_COMMANDS_TOKEN_TYPE_VERTEX_BUFFER_NVX0VK_INDIRECT_COMMANDS_TOKEN_TYPE_INDEX_BUFFER_NVX2VK_INDIRECT_COMMANDS_TOKEN_TYPE_DESCRIPTOR_SET_NVX,VK_INDIRECT_COMMANDS_TOKEN_TYPE_PIPELINE_NVX$$fReadVkIndirectCommandsTokenTypeNVX$$fShowVkIndirectCommandsTokenTypeNVX$fReadVkObjectEntryTypeNVX$fShowVkObjectEntryTypeNVX.$fReadVkIndirectCommandsLayoutUsageFlagBitsNVX.$fShowVkIndirectCommandsLayoutUsageFlagBitsNVX#$fReadVkObjectEntryUsageFlagBitsNVX#$fShowVkObjectEntryUsageFlagBitsNVX.$fStorableVkDeviceGeneratedCommandsFeaturesNVX,$fStorableVkDeviceGeneratedCommandsLimitsNVX$$fStorableVkIndirectCommandsTokenNVX*$fStorableVkIndirectCommandsLayoutTokenNVX%$fStorableVkCmdProcessCommandsInfoNVX-$fStorableVkCmdReserveSpaceForCommandsInfoNVX/$fStorableVkIndirectCommandsLayoutCreateInfoNVX+$fStorableVkObjectTablePushConstantEntryNVX*$fStorableVkObjectTableIndexBufferEntryNVX+$fStorableVkObjectTableVertexBufferEntryNVX,$fStorableVkObjectTableDescriptorSetEntryNVX'$fStorableVkObjectTablePipelineEntryNVX$fStorableVkObjectTableEntryNVX$$fStorableVkObjectTableCreateInfoNVX"$fEqVkIndirectCommandsTokenTypeNVX#$fOrdVkIndirectCommandsTokenTypeNVX($fStorableVkIndirectCommandsTokenTypeNVX$fEqVkObjectEntryTypeNVX$fOrdVkObjectEntryTypeNVX$fStorableVkObjectEntryTypeNVX,$fEqVkIndirectCommandsLayoutUsageFlagBitsNVX-$fOrdVkIndirectCommandsLayoutUsageFlagBitsNVX2$fStorableVkIndirectCommandsLayoutUsageFlagBitsNVX.$fBitsVkIndirectCommandsLayoutUsageFlagBitsNVX4$fFiniteBitsVkIndirectCommandsLayoutUsageFlagBitsNVX!$fEqVkObjectEntryUsageFlagBitsNVX"$fOrdVkObjectEntryUsageFlagBitsNVX'$fStorableVkObjectEntryUsageFlagBitsNVX#$fBitsVkObjectEntryUsageFlagBitsNVX)$fFiniteBitsVkObjectEntryUsageFlagBitsNVX($fEqVkDeviceGeneratedCommandsFeaturesNVX*$fShowVkDeviceGeneratedCommandsFeaturesNVX&$fEqVkDeviceGeneratedCommandsLimitsNVX($fShowVkDeviceGeneratedCommandsLimitsNVX$fEqVkIndirectCommandsTokenNVX $fShowVkIndirectCommandsTokenNVX$$fEqVkIndirectCommandsLayoutTokenNVX&$fShowVkIndirectCommandsLayoutTokenNVX$fEqVkCmdProcessCommandsInfoNVX!$fShowVkCmdProcessCommandsInfoNVX'$fEqVkCmdReserveSpaceForCommandsInfoNVX)$fShowVkCmdReserveSpaceForCommandsInfoNVX)$fEqVkIndirectCommandsLayoutCreateInfoNVX+$fShowVkIndirectCommandsLayoutCreateInfoNVX%$fEqVkObjectTablePushConstantEntryNVX'$fShowVkObjectTablePushConstantEntryNVX$$fEqVkObjectTableIndexBufferEntryNVX&$fShowVkObjectTableIndexBufferEntryNVX%$fEqVkObjectTableVertexBufferEntryNVX'$fShowVkObjectTableVertexBufferEntryNVX&$fEqVkObjectTableDescriptorSetEntryNVX($fShowVkObjectTableDescriptorSetEntryNVX!$fEqVkObjectTablePipelineEntryNVX#$fShowVkObjectTablePipelineEntryNVX$fEqVkObjectTableEntryNVX$fShowVkObjectTableEntryNVX$fEqVkObjectTableCreateInfoNVX $fShowVkObjectTableCreateInfoNVX VkDevice_TbaseGHC.PtrPtrVkPhysicalDevice_T VkInstance_TVkDebugReportCallbackEXT_TVkValidationCacheEXT_TVkShaderModule_T VkSemaphore_T VkFence_TVkCommandBuffer_T VkQueue_TVkDebugUtilsMessengerEXT_T VkQueryPool_TVkPipelineCache_TVkRenderPass_TVkPipelineLayout_T VkPipeline_TVkSurfaceKHR_TVkDisplayModeKHR_TVkDisplayKHR_T VkSampler_TVkDescriptorSetLayout_TVkDeviceMemory_T VkImage_T VkBuffer_T VkImageView_TVkSamplerYcbcrConversion_T VkEvent_TVkCommandPool_TVkBufferView_TVkSwapchainKHR_TVkFramebuffer_TVkDescriptorPool_TVkDescriptorSet_TVkDescriptorUpdateTemplate_TVkIndirectCommandsLayoutNVX_TVkObjectTableNVX_T