diag captureFrameToFile: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "\[\[Category:[ _]?Scripting[ _]Commands[ _]Arma[ _]3(\|.*)]]" to "{{GameCategory|arma3|Scripting Commands}}") |
Lou Montana (talk | contribs) m (Text replacement - "\[\[Category:[ _]?Scripting[ _]Commands[ _]Arma[ _]2(\|.*)\]\]" to "{{GameCategory|arma2|Scripting Commands}}") |
||
| Line 43: | Line 43: | ||
[[Category:Scripting Commands|{{uc:{{PAGENAME}}}}]] | [[Category:Scripting Commands|{{uc:{{PAGENAME}}}}]] | ||
{{GameCategory|arma2|Scripting Commands}} | |||
{{GameCategory|arma3|Scripting Commands}} | {{GameCategory|arma3|Scripting Commands}} | ||
Revision as of 17:29, 8 January 2021
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.
Note: Only available in specific builds. See Performance Profiling for details. - Groups:
- DiagnosisPerformance Logging
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 Profilingdiag_captureSlowFramediag_logSlowFramediag_captureFramelogEntitiesexportJIPMessages
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