diag scope: Difference between revisions
Jump to navigation
Jump to search
Killzone Kid (talk | contribs) (Created page with "{{DISPLAYTITLE:diag_fps}} {{Command|Comments= ____________________________________________________________________________________________ | arma3dev |Game name= |2.01|Game...") |
Killzone Kid (talk | contribs) No edit summary |
||
Line 48: | Line 48: | ||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
| [[diag_fps]], [[diag_fpsMin]], [[diag_frameNo]], [[diag_log]], [[diag_tickTime]], [[diag_deltaTime]] |SEEALSO= | | [[exitWith]], [[diag_fps]], [[diag_fpsMin]], [[diag_frameNo]], [[diag_log]], [[diag_tickTime]], [[diag_deltaTime]] |SEEALSO= | ||
| |MPBEHAVIOUR= | | |MPBEHAVIOUR= |
Revision as of 18:01, 30 September 2020
Description
- 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.
- Groups:
- DiagnosisPerformance Logging
Syntax
- Syntax:
- diag_scope
- Return Value:
- Number
Examples
- 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
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
[[Category:Introduced with arma3dev version 2.01]][[ Category: arma3dev: New Scripting Commands | DIAG SCOPE]][[ Category: arma3dev: Scripting Commands | DIAG SCOPE]]
Notes
Bottom Section