diag fps: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
m (Text replacement - "\|seealso= *\[\[([^ ]+)\]\], \[\[([^ ]+)\]\]" to "|seealso= $1 $2")
m (Text replacement - "\|seealso= *\[\[([^ ]+)\]\], \[\[([^ ]+)\]\]" to "|seealso= $1 ")
Line 26: Line 26:
|x1= <code>diag_log diag_fps;</code>
|x1= <code>diag_log diag_fps;</code>


|seealso= [[diag_fpsMin]] [[diag_frameNo]], [[diag_log]], [[diag_tickTime]], [[diag_deltaTime]]
|seealso= [[diag_fpsMin]] [[diag_frameNo]] [[diag_log]], [[diag_tickTime]], [[diag_deltaTime]]
}}
}}


Revision as of 15:38, 20 January 2022

Logo A2.png1.00A2 OA Logo.png1.50tkoh logo small.png1.00Arma 3 logo black.png0.50
Hover & click on the images for description

Description

Description:
Returns average framerate calculated over last 16 frames.
Groups:
DiagnosticPerformance Profiling

Syntax

Syntax:
diag_fps
Return Value:
Number

Examples

Example 1:
diag_log diag_fps;

Additional Information

See also:
diag_fpsMin diag_frameNo diag_logdiag_tickTimediag_deltaTime

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:56 (UTC)
DreadedEntity
The engine will always calculate the last 16 frames without caring if they are frames in which the loading screen was drawn, or actual mission frames.
Retrieved from "https://community.bistudio.com/wiki?title=diag_fps&oldid=298877"