Difference between revisions of "diag scope"

From Bohemia Interactive Community
Jump to navigation Jump to search
m (Text replacement - " {3,}\|" to " |")
m (Text replacement - " {2,}\}\}" to " }}")
Line 43: Line 43:
| [[exitWith]], [[diag_fps]], [[diag_fpsMin]], [[diag_frameNo]], [[diag_log]], [[diag_tickTime]], [[diag_deltaTime]]
| [[exitWith]], [[diag_fps]], [[diag_fpsMin]], [[diag_frameNo]], [[diag_log]], [[diag_tickTime]], [[diag_deltaTime]]

Revision as of 00:30, 19 January 2021

-wrong parameter ("arma3dev") defined!-[[:Category:Introduced with arma3dev version 2.01|2.01]]
Hover & click on the images for description


Returns script scope depth. When script is directly executed by the engine or a new script is added to the scheduler, the scope depth is 0. The examples of such execution are event handlers, spawn, etc. isNil Code will also create a parent scope. Any use of call and such will stack execution creating child scopes and increasing scope depth.
DiagnosisPerformance Logging


Return Value:


Example 1:
[] spawn { systemChat str diag_scope; // 0 call { call { systemChat str diag_scope; // 2 isNil { systemChat str diag_scope; // 0 call { systemChat str diag_scope; // 1 }; }; }; }; };

Additional Information

See also:
exitWithdiag fpsdiag fpsMindiag frameNodiag logdiag tickTimediag deltaTime


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

[[Category:Introduced with arma3dev version 2.01]][[ Category: arma3dev: New Scripting Commands | DIAG SCOPE]][[ Category: arma3dev: Scripting Commands | DIAG SCOPE]]