gitea/SDL3_fork
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

gpu: Document why VertexID/InstanceID builtins are unreliable

Browse Source
This commit is contained in:
Ethan Lee
2024-12-24 14:52:32 -05:00
parent dd83908109
commit 65e0fed5b3
1 changed files with 16 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
include/SDL3/SDL_gpu.h
View File

@@ -1419,8 +1419,10 @@ typedef struct SDL_GPUBufferRegion
* *
* Note that the `first_vertex` and `first_instance` parameters are NOT * Note that the `first_vertex` and `first_instance` parameters are NOT
* compatible with built-in vertex/instance ID variables in shaders (for * compatible with built-in vertex/instance ID variables in shaders (for
* example, SV_VertexID). If your shader depends on these variables, the * example, SV_VertexID); GPU APIs and shader languages do not define these
* correlating draw call parameter MUST be 0. * built-in variables consistently, so if your shader depends on them, the only
* way to keep behavior consistent and portable is to always pass 0 for the
* correlating parameter in the draw calls.
* *
* \since This struct is available since SDL 3.1.3 * \since This struct is available since SDL 3.1.3
* *
@@ -1439,8 +1441,10 @@ typedef struct SDL_GPUIndirectDrawCommand
* *
* Note that the `first_vertex` and `first_instance` parameters are NOT * Note that the `first_vertex` and `first_instance` parameters are NOT
* compatible with built-in vertex/instance ID variables in shaders (for * compatible with built-in vertex/instance ID variables in shaders (for
* example, SV_VertexID). If your shader depends on these variables, the * example, SV_VertexID); GPU APIs and shader languages do not define these
* correlating draw call parameter MUST be 0. * built-in variables consistently, so if your shader depends on them, the only
* way to keep behavior consistent and portable is to always pass 0 for the
* correlating parameter in the draw calls.
* *
* \since This struct is available since SDL 3.1.3 * \since This struct is available since SDL 3.1.3
* *
@@ -3025,8 +3029,10 @@ extern SDL_DECLSPEC void SDLCALL SDL_BindGPUFragmentStorageBuffers(
* *
* Note that the `first_vertex` and `first_instance` parameters are NOT * Note that the `first_vertex` and `first_instance` parameters are NOT
* compatible with built-in vertex/instance ID variables in shaders (for * compatible with built-in vertex/instance ID variables in shaders (for
* example, SV_VertexID). If your shader depends on these variables, the * example, SV_VertexID); GPU APIs and shader languages do not define these
* correlating draw call parameter MUST be 0. * built-in variables consistently, so if your shader depends on them, the only
* way to keep behavior consistent and portable is to always pass 0 for the
* correlating parameter in the draw calls.
* *
* \param render_pass a render pass handle. * \param render_pass a render pass handle.
* \param num_indices the number of indices to draw per instance. * \param num_indices the number of indices to draw per instance.
@@ -3053,8 +3059,10 @@ extern SDL_DECLSPEC void SDLCALL SDL_DrawGPUIndexedPrimitives(
* *
* Note that the `first_vertex` and `first_instance` parameters are NOT * Note that the `first_vertex` and `first_instance` parameters are NOT
* compatible with built-in vertex/instance ID variables in shaders (for * compatible with built-in vertex/instance ID variables in shaders (for
* example, SV_VertexID). If your shader depends on these variables, the * example, SV_VertexID); GPU APIs and shader languages do not define these
* correlating draw call parameter MUST be 0. * built-in variables consistently, so if your shader depends on them, the only
* way to keep behavior consistent and portable is to always pass 0 for the
* correlating parameter in the draw calls.
* *
* \param render_pass a render pass handle. * \param render_pass a render pass handle.
* \param num_vertices the number of vertices to draw. * \param num_vertices the number of vertices to draw.