diag captureFrame: Difference between revisions
Jump to navigation
Jump to search
(Info about Serverside) |
m (Added captureFrameToFile to see also) |
||
| Line 25: | Line 25: | ||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
| [[Performance Profiling]], [[diag_captureSlowFrame]], [[diag_logSlowFrame]], [[logEntities]], [[exportJIPMessages]] |= See also | | [[Performance Profiling]], [[diag_captureSlowFrame]], [[diag_logSlowFrame]], [[logEntities]], [[exportJIPMessages]], [[diag_captureFrameToFile]] |= See also | ||
}} | }} | ||
Revision as of 02:41, 17 January 2017
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 captured data UI dialog appears, similar to diag_captureSlowFrame.
This can also be executed on a dedicated Server and because a Server has no UI it will behave like diag_captureFrameToFile.
Special: BattlEye's RCON variant of this command is #captureFrame
Note: Only available in specific builds. See Performance Profiling for details. - Groups:
- Uncategorised
Syntax
- Syntax:
- diag_captureFrame frame
- Parameters:
- frame: Number - next n-th frame to be captured
- Return Value:
- Nothing
Examples
- Example 1:
diag_captureFrame 1; //capture the first frame after command execution- Example 2:
diag_captureFrame 24; //capture 24th frame after command execution
Additional Information
- See also:
- Performance Profilingdiag_captureSlowFramediag_logSlowFramelogEntitiesexportJIPMessagesdiag_captureFrameToFile
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