diag fps: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
No edit summary
mNo edit summary
Line 51: Line 51:
<dt class="note">[[User:DreadedEntity|DreadedEntity]]</dt>
<dt class="note">[[User:DreadedEntity|DreadedEntity]]</dt>
<dd class="note">
<dd class="note">
Be careful with where you place [[diag_fps]] in your scripts, putting it in the very beginning of my init.sqf resulted in extremely low numbers, 5-9 on several tests. Waiting 1 second then using the command again resulted in accurate fps. That means that 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.
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.
</dd>
</dd>
</dl>
</dl>
<!-- DISCONTINUE Notes -->
<!-- DISCONTINUE Notes -->

Revision as of 21:57, 15 December 2014


Hover & click on the images for description

Description

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

Syntax

Syntax:
diag_fps
Return Value:
Number

Examples

Example 1:
diag_log diag_fps;

Additional Information

See also:
diag_fpsmindiag_framenodiag_logdiag_tickTime

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

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.