diag captureFrame: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "<code>([^ ]*)\[\[([a-zA-Z0-9_]+)\]\]([^ ]*)<\/code>" to "<code>$1$2$3</code>") |
Lou Montana (talk | contribs) m (Text replacement - "{{Feature|Important|" to "{{Feature|important|") |
||
(2 intermediate revisions by the same user not shown) | |||
Line 14: | Line 14: | ||
|descr= 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]]. | |descr= 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]]. | ||
{{Feature| | {{Feature|important|BattlEye's RCON variant of this command is '''#captureFrame'''}} | ||
|s1= [[diag_captureFrame]] frame | |s1= [[diag_captureFrame]] frame | ||
Line 22: | Line 22: | ||
|r1= [[Nothing]] | |r1= [[Nothing]] | ||
|x1= < | |x1= <sqf>diag_captureFrame 1; // capture the first frame after command execution</sqf> | ||
|x2= < | |x2= <sqf>diag_captureFrame 24; // capture 24th frame after command execution</sqf> | ||
|seealso= [[Arma 3: Diagnostics Exe]] [[Performance Profiling]] [[diag_captureSlowFrame]] [[diag_logSlowFrame]] [[logEntities]] [[exportJIPMessages]] [[diag_captureFrameToFile]] | |seealso= [[Arma 3: Diagnostics Exe]] [[Performance Profiling]] [[diag_captureSlowFrame]] [[diag_logSlowFrame]] [[logEntities]] [[exportJIPMessages]] [[diag_captureFrameToFile]] | ||
}} | }} |
Revision as of 00:24, 2 February 2024
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.
- Groups:
- DiagnosticPerformance Profiling
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:
- Arma 3: Diagnostics Exe Performance Profiling diag_captureSlowFrame diag_logSlowFrame logEntities exportJIPMessages diag_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
Categories:
- Scripting Commands
- Introduced with Arma 2: Operation Arrowhead version 1.63
- Arma 2: Operation Arrowhead: New Scripting Commands
- Arma 2: Operation Arrowhead: Scripting Commands
- Arma 3: Scripting Commands: Diagnostic Branch
- Arma 3: Scripting Commands: Profiling Branch
- Arma 3: Scripting Commands
- Command Group: Diagnostic
- Command Group: Performance Profiling