MoonsideGames
/
Refresh
1
0
Fork 1
Code Issues 1 Pull Requests 2 Projects Releases 33 Wiki Activity

clarify writeOption behavior
continuous-integration/drone/push Build is passing Details

pull/51/head
cosmonaut 2024-03-01 13:10:44 -08:00
parent b64bf06c7b
commit a3249404bc
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
include/Refresh.h
View File

@ -588,7 +588,7 @@ typedef struct Refresh_GraphicsPipelineCreateInfo
* loadOp: Determines what is done with the texture slice at the beginning of the render pass.
*
* LOAD:
* Loads the texture slice.
* Loads the data currently in the texture slice.
*
* CLEAR:
* Clears the texture slice to a single color.
@ -613,7 +613,7 @@ typedef struct Refresh_GraphicsPipelineCreateInfo
* writeOption:
* SAFEDISCARD:
* If this texture slice has been used in commands that have not completed,
* those commands will still be valid at the cost of increased memory usage.
* this option will prevent a data dependency at the cost of increased memory usage.
* You may NOT assume that any of the previous texture data is retained.
* If the texture slice was not in use, this option is equivalent to SAFEOVERWRITE.
* This is a good option to prevent stalls when frequently reusing a texture slice in rendering.
@ -1161,7 +1161,7 @@ REFRESHAPI void Refresh_BeginCopyPass(
* writeOption:
* SAFEDISCARD:
* If the destination resource has been used in commands that have not completed,
* the issued commands will still be valid at the cost of increased memory usage.
* this option will prevent a data dependency at the cost of increased memory usage.
* You may NOT assume that any of the previous data is retained.
* If the destination resource was not in use, this option is equivalent to SAFEOVERWRITE.
* This is a good option to prevent stalls on resources with frequent updates.
@ -1239,7 +1239,7 @@ REFRESHAPI void Refresh_DownloadFromBuffer(
* writeOption:
* SAFEDISCARD:
* If the destination resource has been used in commands that have not completed,
* the issued commands will still be valid at the cost of increased memory usage.
* this option will prevent a data dependency at the cost of increased memory usage.
* You may NOT assume that any of the previous data is retained.
* If the destination resource was not in use, this option is equivalent to SAFEOVERWRITE.
* This is a good option to prevent stalls on resources with frequent updates.