Asset and state files

USAGE_android.md

@@ -306,6 +306,9 @@ option values.
 | Capture Specific Frames | debug.gfxrecon.capture_frames | STRING | Specify one or more comma-separated frame ranges to capture. Each range will be written to its own file. A frame range can be specified as a single value, to specify a single frame to capture, or as two hyphenated values, to specify the first and last frame to capture. Frame ranges should be specified in ascending order and cannot overlap. Note that frame numbering is 1-based (i.e. the first frame is frame 1). Example: `200,301-305` will create two capture files, one containing a single frame and one containing five frames. Default is: Empty string (all frames are captured). |
 | Quit after capturing frame ranges | debug.gfxrecon.quit_after_capture_frames | BOOL | Setting it to `true` will force the application to terminate once all frame ranges specified by `debug.gfxrecon.capture_frames` have been captured. Default is: `false` |
 | Capture trigger for Android | debug.gfxrecon.capture_android_trigger | BOOL | Set during runtime to `true` to start capturing and to `false` to stop. If not set at all then it is disabled (non-trimmed capture). Default is not set. |
+| Use asset file | debug.gfxrecon.capture_use_asset_file | BOOL | When set to `true` assets (images, buffers and descriptors) will be stored separately into an asset file instead of the capture file. |
+| Dump assets | debug.gfxrecon.capture_android_dump_assets | BOOL | Setting this triggers a dump of all assets into the asset file. Since android options cannot be set by the layer, dumping is done whenever this option switches between from `false` to `true` or from `true` to `false`. Default is: `false` |
+| Write state files | debug.gfxrecon.capture_write_state_files | BOOL | When set to `true` for each frame captured its corresponding state will be stored in a separate capture file. Specifying a specific state file can start replaying from the corresponding frame. Default is: `false` |
 | Capture File Compression Type | debug.gfxrecon.capture_compression_type | STRING | Compression format to use with the capture file. Valid values are: `LZ4`, `ZLIB`, `ZSTD`, and `NONE`. Default is: `LZ4` |
 | Capture File Timestamp | debug.gfxrecon.capture_file_timestamp | BOOL | Add a timestamp to the capture file as described by [Timestamps](#timestamps). Default is: `true` |
 | Capture File Flush After Write | debug.gfxrecon.capture_file_flush | BOOL | Flush output stream after each packet is written to the capture file. Default is: `false` |
@@ -468,6 +471,17 @@ An existing capture file can be trimmed by replaying the capture with the captur
 enabled and a trimming frame range or capture trigger enabled. (However, replay for
 some content may be fast enough using the trigger property may be difficult.)
 
+### Asset files
+
+When doing a trimmed capture, `debug.gfxrecon.capture_use_asset_file` gives the
+option to dump all assets (images, buffers and descriptors) separetly in a
+different capture file called the asset file. When this option is enabled
+assets are tracked and only those that are changed during a tracking period
+(outside of a trim range) are dumped into the asset file. This first time a
+trim range is encountered (or the hotkey is pressed) all assets will be dumped,
+but the next time this happens only the assets that have been changed will be
+dumped. This should speed up the dumping process.
+
 ### Capture Limitations
 
 #### Conflicts With Crash Detection Libraries