You copied the Doc URL to your clipboard.

Automated Trace View

The Automated Trace View allows you to run a range of standard MGD commands automatically when a certain frame is encountered. For example, you could run your application and automatically take a frame capture on frame 10, do a frame capture with overdraw mode switched on at frame 20 and do a frame capture with fragment count mode enabled at frame 30.

Note: Currently you can only add automated trace commands after an application has started.

To add an automated trace command, first select and pause the process you want to add commands to and then open up the Automated Trace View.

Select Add Command and the Add Automated Trace Command dialog will be opened.

Here you can select the type of command you want and which frames it should apply to. You must specify at least one frame number to add a command. For a frame number to be considered valid, it must:

  • be greater than the current frame plus one
  • not already have an automated command associated with it

If the list of frames is invalid the Frame number(s) text box will be highlighted in red. A tooltip on text box will give you the reason why.

Note: 'Empty' frame numbers (a series of commas with no number between them) and duplicate frame numbers are ignored.

When you have a valid list of frames, select the Ok button.

You can then add more commands (and remove existing ones).

When you are happy with the list, press the button. When the trace reaches frames which you have added commands to, those commands will be executed.

Note: Automated trace commands for a frame will be ignored if:
  • you send a play, step, or capture command in that frame
  • you send a play, step, or capture command in the frame before that frame