- class renderdoc.FrameDescription¶
Contains frame-level global information
No frame number is available.
The time when the capture was created, as a unix timestamp in UTC.
The total file size of the whole capture in bytes, before decompression.
The debug messages that are not associated with any particular event.
The offset into the file of the start of the frame.
APIEvent.fileOffsetthis should only be used as a relative measure, as it is not a literal number of bytes from the start of the file on disk.
Starting from frame #1 defined as the time from application startup to first present, this counts the frame number when the capture was made.
This value is only accurate if the capture was triggered through the default mechanism, if it was triggered from the application API it doesn’t correspond to anything and will be set to
The byte size of the section of the file that contains frame-initial contents.
The byte size of the section of the file that must be kept in memory persistently.
The total file size of the whole capture in bytes, after decompression.
- class renderdoc.DrawcallDescription¶
Describes the properties of a drawcall, dispatch, debug marker, or similar event.
Resets the drawcall back to a default/empty state.
For indexed drawcalls, the offset added to each index after fetching.
The child drawcalls below this one, if it’s a marker region or multidraw type draw.
ResourceIdidentifying the destination object in a copy, resolve or blit operation.
The 3D base offset of the workgroup ID if the call allows an override, or 0 if not.
The 3D number of workgroups to dispatch in a dispatch call.
The 3D size of each workgroup in threads if the call allows an override, or 0 if not.
The index of this draw in an call with multiple draws, e.g. an indirect draw.
0 if not part of a multi-draw.
A 1-based index of this drawcall relative to other drawcalls.
For indexed drawcalls, the first index to fetch from the index buffer.
For instanced drawcalls, the offset applied before looking up instanced vertex inputs.
The name of this drawcall. Typically a summarised/concise list of parameters.
For drawcalls, the convention is to list primary parameters (vertex/index count, instance count) and omit secondary parameters (vertex offset, instance offset).
The next drawcall in the frame, or
Noneif this is the last drawcall in the frame.
The number of indices or vertices as appropriate for the drawcall. 0 if not used.
The number of instances for the drawcall. 0 if not used.
An 8-tuple of the
ResourceIdids for the color outputs, which can be used for very coarse bucketing of drawcalls into similar passes by their outputs.
The parent of this drawcall, or
Noneif there is no parent for this drawcall.
The previous drawcall in the frame, or
Noneif this is the first drawcall in the frame.
For non-indexed drawcalls, the offset applied before looking up each vertex input.
- class renderdoc.DrawFlags(value)¶
A set of flags describing the properties of a particular drawcall.
The drawcall has no special properties.
The drawcall renders primitives using the graphics pipeline.
The drawcall issues a number of compute workgroups.
The drawcall calls into a previously recorded child command list.
The drawcall inserts a single debugging marker.
The drawcall begins a debugging marker region that has children.
The drawcall ends a debugging marker region.
Drawcalls with this flag will not be exposed and it is only used internally for tracking markers.
The drawcall is a presentation call that hands a swapchain image to the presentation engine.
The drawcall is a multi-draw that contains several specified child draws.
The drawcall performs a resource copy operation.
The drawcall performs a resource resolve or blit operation.
The drawcall performs a resource mip-generation operation.
The drawcall uses an index buffer.
The drawcall uses instancing. This does not mean it renders more than one instanced, simply that it uses the instancing feature.
The drawcall interacts with stream-out to render all vertices previously written. This is a Direct3D 11 specific feature.
The drawcall uses a buffer on the GPU to source some or all of its parameters in an indirect way.
The drawcall clears a color target.
The drawcall clears a depth-stencil target.
The drawcall marks the beginning of a render pass.
The drawcall marks the end of a render pass.
The drawcall does not contain any work directly, but is a ‘virtual’ draw inserted to encompass non-draw API calls that happened within a region, so they are included within the region where they occurred and not grouped into the next drawcall outside that region.
- class renderdoc.APIEvent¶
An individual API-level event, generally corresponds one-to-one with an API call.
The chunk index for this function call in the structured file.
The API event’s Event ID.
This is a 1-based count of API events in the capture. The eventId is used as a reference point in many places in the API to represent where in the capture the ‘current state’ is, and to perform analysis in reference to the state at a particular point in the frame.
eventIds are always increasing and positive, but they may not be contiguous - in some circumstances there may be gaps if some events are consumed entirely internally, such as debug marker pops which only modify the internal drawcall tree structures.
Also eventIds may not correspond directly to an actual function call - sometimes a function such as a multi draw indirect will be one function call that expands to multiple events to allow inspection of results part way through the multi draw.
A byte offset in the data stream where this event happens.
This should only be used as a relative measure, it is not a literal number of bytes from the start of the file on disk.
- class renderdoc.DebugMessage¶
A debugging message from the API validation or internal analysis and error detection.
The string contents of the message.
An ID that identifies this particular debug message uniquely.
- class renderdoc.MessageCategory(value)¶
The type of issue that a debug message is about.
This message was generated by the application.
This message doesn’t fall into any other pre-defined category.
This message is about initialisation or creation of objects.
This message is about cleanup, destruction or shutdown of objects.
This message is about compilation of shaders.
This message is about creating unified state objects.
This message is about changing current pipeline state.
This message is about fetching or retrieving current pipeline state.
This message is about updating or changing a resource’s properties or contents.
This message is about performing work.
This message is about the use, syntax, binding or linkage of shaders.
This message is about the use of deprecated functionality.
This message is about the use of undefined behaviour.
This message is about behaviour that could be or is not portable between different environments.
This message is about performance problems or pitfalls.
- class renderdoc.MessageSeverity(value)¶
How serious a debug message is
This message is very serious, indicating a guaranteed problem or major flaw.
This message is somewhat serious, indicating a problem that should be addressed or investigated.
This message is not very serious. This indicates something that might indicate a problem.
This message is not about a problem but is purely informational.
- class renderdoc.MessageSource(value)¶
Where a debug message was reported from
This message comes from the API’s debugging or validation layers.
This message comes from detecting redundant API calls - calls with no side-effect or purpose, e.g. setting state that is already set.
This message comes from detecting incorrect use of the API.
This message comes from detecting general performance problems that are not hardware or platform specific.
This message comes from detecting patterns that will cause performance problems on GCN-based hardware.
This message comes not from inspecting the log but something detected at runtime while in use, for example exceptions generated during shader debugging.
This message comes from replaying a capture in an environment with insufficient capability to accurately reproduce the API work. Either this means the replay will be wrong, or it may be that depending on the exact API work some inaccuracies might happen.
- class renderdoc.EventUsage¶
Describes a particular use of a resource at a specific
- class renderdoc.ResourceUsage(value)¶
How a resource is being used in the pipeline at a particular point.
Note that a resource may be used for more than one thing in one event, see
The resource is not being used.
The resource is being used as a fixed-function vertex buffer input.
The resource is being used as an index buffer.
The resource is being used for constants in the tessellation evaluation or
The resource is being used for constants in all shader stages.
The resource is being used for stream out/transform feedback storage after geometry processing.
The resource is being used as a read-only resource in the tessellation control or
The resource is being used as a read-only resource in the tessellation evaluation or
The resource is being used as a read-only resource in all shader stages.
The resource is being used as a read-write resource in the tessellation control or
The resource is being used as a read-write resource in the tessellation evaluation or
The resource is being used as a read-write resource in all shader stages.
The resource is being read as an input target for reading from the target currently being written.
The resource is being written to as a color output.
The resource is being written to and tested against as a depth-stencil output.
The resource is being used for indirect arguments.
The resource is being cleared.
The resource contents are discarded explicitly or implicitly.
The resource is having mips generated for it.
The resource is being resolved or blitted, as both source and destination.
The resource is being resolved or blitted from.
The resource is being resolved or blitted to.
The resource is being copied, as both source and destination.
The resource is being copied from.
The resource is being copied to.
The resource is being specified in a barrier, as defined in Vulkan or Direct3D 12.
ResourceUsagevalue for read-only resource use at a given shader stage.
ResourceUsagevalue for read-write resource use at a given shader stage.
- class renderdoc.TextureSave¶
Describes a texture to save and how to map it to the destination file format.
Controls handling of alpha channel, only relevant for file formats that don’t have alpha.
It is an
AlphaMappingthat controls what behaviour to use.
Selects a single component out of a texture to save as grayscale, or -1 to save all.
Controls black/white point mapping for output formats that are normal
8-bit SRGB, values are truncated so that values below the black point and above the white point are clamped, and the values in between are evenly distributed.
The quality to use when saving to a
JPGfile. Valid values are between 1 and 100.
Selects the mip to be written out.
If set to
-1then all mips are written, where allowed by file format. If not allowed, mip 0 is written
Controls mapping for multisampled textures (ignored if texture is not multisampled)
Controls mapping for arrayed textures (ignored if texture is not arrayed)
- class renderdoc.FileType(value)¶
The format of an image file
A DDS file
A PNG file
A JPG file
A BMP file
A TGA file
An HDR file
An EXR file
Raw data, just the bytes of the image tightly packed with no metadata or compression/encoding
- class renderdoc.AlphaMapping(value)¶
What to do with the alpha channel from a texture while saving out to a file.
Completely discard the alpha channel and only write RGB to the file.
Blend to the primary background color using alpha.
Blend to a checkerboard pattern with the primary and secondary background colors.
Preserve the alpha channel and save it to the file by itself.
This is only valid for file formats that support alpha channels.
- class renderdoc.TextureComponentMapping¶
How to map components to normalised
[0, 255]for saving to 8-bit file formats.
The value that should be mapped to
The value that should be mapped to
- class renderdoc.TextureSampleMapping¶
How to map multisampled textures for saving to non-multisampled file formats.
Trueif the samples should be mapped to array slices. A multisampled array expands each slice in-place, so it would be slice 0: sample 0, slice 0: sample 1, slice 1: sample 0, etc.
This then follows the mapping for array slices as with any other array texture.
- class renderdoc.TextureSliceMapping¶
How to map array textures for saving to non-arrayed file formats.
Write out 6 slices in a cruciform pattern:
+----+ | +y | | | +----+----+----+----+ | -x | +z | +x | -z | | | | | | +----+----+----+----+ | -y | | | +----+
With the gaps filled in with transparent black.
Selects the (depth/array) slice to save.
If this is -1, then all slices are written out as detailed below. This is only supported in formats that don’t support slices natively, and will be done in RGBA8.
- class renderdoc.PixelModification¶
An attempt to modify a pixel by a particular event.
Determine if this fragment passed all tests and wrote to the texture.
Trueif it passed all tests,
Falseif it failed any.
- Return type
Trueif the backface culling test eliminated this fragment.
Trueif depth bounds clipping eliminated this fragment.
Trueif depth near/far clipping eliminated this fragment.
Trueif depth testing eliminated this fragment.
Trueif this event came as part of an arbitrary shader write.
A 0-based index of which fragment this modification corresponds to, in the case that multiple fragments from a single draw wrote to a pixel.
The value of the texture before this fragment ran.
This is valid only for the first fragment if multiple fragments in the same event write to the same pixel.
Trueif predicated rendering skipped this call.
The primitive that generated this fragment.
Trueif the sample mask eliminated this fragment.
Trueif scissor clipping eliminated this fragment.
Trueif the pixel shader executed a discard on this fragment.
Trueif stencil testing eliminated this fragment.
Trueif no pixel shader was bound at this event.
Trueif viewport clipping eliminated this fragment.
- class renderdoc.ModificationValue¶
The value of pixel output at a particular event.
Returns whether or not this modification value is valid.
- Return type
Sets this modification value to be invalid.
The depth output, as a
The stencil output, or
-1if not available.
- class renderdoc.PixelValue¶
The contents of an RGBA pixel.
The RGBA value interpreted as
Tuple[float, float, float, float]
The RGBA value interpreted as 32-bit signed integer.
Tuple[int, int, int, int]
The RGBA value interpreted as 32-bit unsigned integer.
Tuple[int, int, int, int]