diag captureFrame: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
m (Added captureFrameToFile to see also)
m (template:command argument fix)
Line 11: Line 11:
This can also be executed on a dedicated Server and because a Server has no UI it will behave like [[diag_captureFrameToFile]].<br>
This can also be executed on a dedicated Server and because a Server has no UI it will behave like [[diag_captureFrameToFile]].<br>
Special: BattlEye's RCON variant of this command is #captureFrame<br>  
Special: BattlEye's RCON variant of this command is #captureFrame<br>  
'''Note''': Only available in specific builds. See [[Performance Profiling]] for details. |= Description
'''Note''': Only available in specific builds. See [[Performance Profiling]] for details. |DESCRIPTION=
____________________________________________________________________________________________
____________________________________________________________________________________________


| '''diag_captureFrame''' frame|= Syntax
| '''diag_captureFrame''' frame|SYNTAX=


|p1= frame: [[Number]] - next n-th frame to be captured |= Parameter 1
|p1= frame: [[Number]] - next n-th frame to be captured |PARAMETER1=


| [[Nothing]] |= Return value
| [[Nothing]] |RETURNVALUE=
____________________________________________________________________________________________
____________________________________________________________________________________________
   
   
|x1= <code>[[diag_captureFrame]] 1; //capture the first frame after command execution</code> |= Example 1
|x1= <code>[[diag_captureFrame]] 1; //capture the first frame after command execution</code> |EXAMPLE1=
|x2= <code>[[diag_captureFrame]] 24; //capture 24th frame after command execution</code> |= Example 2
|x2= <code>[[diag_captureFrame]] 24; //capture 24th frame after command execution</code> |EXAMPLE2=
____________________________________________________________________________________________
____________________________________________________________________________________________


| [[Performance Profiling]], [[diag_captureSlowFrame]], [[diag_logSlowFrame]], [[logEntities]], [[exportJIPMessages]], [[diag_captureFrameToFile]] |= See also
| [[Performance Profiling]], [[diag_captureSlowFrame]], [[diag_logSlowFrame]], [[logEntities]], [[exportJIPMessages]], [[diag_captureFrameToFile]] |SEEALSO=


}}
}}

Revision as of 14:37, 7 April 2019


Hover & click on the images for description

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

Notes

Bottom Section