diag captureFrameToFile: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) |
Lou Montana (talk | contribs) m (Text replacement - "\|seealso= *\[\[([^ ]+)\]\], \[\[([^ ]+)\]\]" to "|seealso= $1 ") |
||
Line 26: | Line 26: | ||
|x2= <code>[[diag_captureFrameToFile]] 24; //capture 24th frame after command execution</code> | |x2= <code>[[diag_captureFrameToFile]] 24; //capture 24th frame after command execution</code> | ||
|seealso= [[Performance Profiling]] [[diag_captureSlowFrame]] [[diag_logSlowFrame]] [[diag_captureFrame]] | |seealso= [[Performance Profiling]] [[diag_captureSlowFrame]] [[diag_logSlowFrame]] [[diag_captureFrame]] [[logEntities]], [[exportJIPMessages]] | ||
}} | }} |
Revision as of 15:49, 20 January 2022
Description
- Description:
- This command starts counting frames from the moment it is executed and when the count reaches the number passed as param, the current frame is captured and
written to a log file in the same directory as the .rpt file.
The full Path to the log file is logged to simultaneously.
The data in the log file can be copied and pasted into the diag_captureFrame UI dialog to get a visualisation later on. - Groups:
- DiagnosticPerformance Profiling
Syntax
- Syntax:
- diag_captureFrameToFile frame
- Parameters:
- frame: Number - next n-th frame to be captured
- Return Value:
- Nothing
Examples
- Example 1:
diag_captureFrameToFile 1; //capture the first frame after command execution
- Example 2:
diag_captureFrameToFile 24; //capture 24th frame after command execution
Additional Information
- See also:
- Performance Profiling diag_captureSlowFrame diag_logSlowFrame diag_captureFrame logEntitiesexportJIPMessages
Notes
-
Report bugs on the Feedback Tracker and/or discuss them on the Arma Discord or on the Forums.
Only post proven facts here! Add Note