diag frameNo: Difference between revisions
Jump to navigation
Jump to search
m (Text replacement - "<h3 style='display:none'>Notes</h3> <dl class='command_description'> <!-- Note Section BEGIN --> <!-- Note Section END --> </dl> <h3 style='display:none'>Bottom Section</h3>" to "") |
Lou Montana (talk | contribs) m (Text replacement - "(\| * )+\}\}" to "}}") |
||
Line 28: | Line 28: | ||
| [[diag_fps]], [[diag_fpsMin]], [[diag_log]], [[diag_tickTime]], [[diag_deltaTime]] | | [[diag_fps]], [[diag_fpsMin]], [[diag_log]], [[diag_tickTime]], [[diag_deltaTime]] | ||
}} | }} | ||
Revision as of 15:27, 18 January 2021
Description
- Description:
- Returns number of frame currently displayed.
- Groups:
- DiagnosisPerformance Logging
Syntax
- Syntax:
- diag_frameNo
- Return Value:
- Number
Examples
- Example 1:
_currFrameNo = diag_frameNo;
Additional Information
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
- Posted on November 19, 2014 - 23:51 (UTC)
- DreadedEntity
- Avoid using hard-coded frame-specific events, the total amount of drawn frames is persistent across all missions. It does not get reset until the game is closed.