
gallium can't directly support vertex attribute instance rate zero, since the instance rate is also used to determine if the data is per-vertex or per-instance in the first place (hence divisor zero meaning the data is per vertex). While it's an optional feature for VK_EXT_vertex_attribute_divisor, some apps require it to work (it's a standard d3d10 feature and widely supported), hence translate it away as MAX_UINT32 divisor instead (which at this point probably makes more sense than to change the gallium interface), which should work all the same. Reviewed-by: Roland Scheidegger <sroland@vmware.com> Reviewed-By: Mike Blumenkrantz <michael.blumenkrantz@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/16526>
7 lines
268 B
Plaintext
7 lines
268 B
Plaintext
WGL_ARB_create_context_robustness
|
|
d3d12 ARB_robust_buffer_access_behavior
|
|
VK_EXT_robustness2 for lavapipe
|
|
VK_EXT_image_2d_view_of_3d on RADV
|
|
zink GL_EXT_memory_object_win32 and GL_EXT_semaphore_win32 support
|
|
vertexAttributeInstanceRateZeroDivisor support for lavapipe
|