Hey James,
you can use “Timing Regions” to mark a time span that exists over multiple frames.
They are shown in their own custom track and look something like this:
[Image Removed]They are intended for low-frequency events, so if you ran more than a few instances at the same time the visualization might not be easy to read anymore.
The generic usage for them looks like this:
`// As a class member or similar storage
uint64 RegionId = 0;
// To open the region
RegionId = TRACE_BEGIN_REGION_WITH_ID(TEXT(“MyRegionName”));
// To close the region
if (RegionId != 0)
{
TRACE_END_REGION_WITH_ID(RegionId);
}`You can also open/close regions just using the string without storing an ID, but that could get ambiguous if you have multiple open regions with the same string name.
Kind Regards,
Sebastian