Mission Optimisation - Revision history

Lou Montana: Some wiki formatting

2026-01-11T16:56:35Z

Some wiki formatting

← Older revision		Revision as of 18:56, 11 January 2026
Line 47:		Line 47:

	{{Feature\|informative\|		{{Feature\|informative\|
	: {{Colorball\|red\|1.125}} means a heavy impact on performance~~<br>~~		: {{Colorball\|red\|1.125}} means a heavy impact on performance
	: {{Colorball\|orange\|1.125}} means an average impact~~<br>~~		: {{Colorball\|orange\|1.125}} means an average impact
	: {{Colorball\|green\|1.125}} means little to no performance impact.		: {{Colorball\|green\|1.125}} means little to no performance impact.
	}}		}}

Lou Montana: Some wiki formatting

2025-05-20T21:33:57Z

Some wiki formatting

← Older revision		Revision as of 23:33, 20 May 2025
Line 18:		Line 18:
	** {{Link\|https://www.moddb.com/forum/thread/arma-2-ultimate-tweak-thread\|{{arma2}} performance guide}}		** {{Link\|https://www.moddb.com/forum/thread/arma-2-ultimate-tweak-thread\|{{arma2}} performance guide}}
	** {{Link\|https://forums.bohemia.net/forums/topic/50167-pc-optimization-for-arma/\|{{arma1}} performance guide}}<!--		** {{Link\|https://forums.bohemia.net/forums/topic/50167-pc-optimization-for-arma/\|{{arma1}} performance guide}}<!--
	** [{{ofp}} performance guide]		** {{Link\|{{ofp}} performance guide}}
	-->		-->
	* Play your mission in singleplayer. If your mission runs fine, its network messages might very well be the issue. See [[Multiplayer Scripting]] for good practice tips.		* Play your mission in singleplayer. If your mission runs fine, its network messages might very well be the issue. See [[Multiplayer Scripting]] for good practice tips.
Line 28:		Line 28:


	== ~~Creating your~~ Mission ==		== Mission Creation ==

	* Be sure to create your scripts with the latest available commands and functions.		* Be sure to create your scripts with the latest available commands and functions.
Line 67:		Line 67:
	* Use [[createAgent\|Agents]] whenever possible		* Use [[createAgent\|Agents]] whenever possible
	* The more units there are, the more network updates there will be - hence the impact on both CPU and network.		* The more units there are, the more network updates there will be - hence the impact on both CPU and network.
	* If a client has a low-end machine, they ~~shouldn't~~ lead a group of many AIs as these would then be locally computed.		* If a client has a low-end machine, they should not lead a group of many AIs as these would then be locally computed.
	* [[Arma 3: Dynamic Simulation]] allows you to freeze AI that are distant from players. Many distance settings should be set according to the mission.		* [[Arma 3: Dynamic Simulation]] allows you to freeze AI that are distant from players. Many distance settings should be set according to the mission.
	{{ Feature \| ~~Informative~~ \| If you own more than one average computer, you could consider [[Arma 3: Headless Client\|Headless client]] to offload AI from the server. }}		{{Feature\|informative\|If you own more than one average computer, you could consider [[Arma 3: Headless Client\|Headless client]] to offload AI from the server.}}
	\|-		\|-
	\|		\|
Line 83:		Line 83:
	** headgear, clothing, vests, backpacks		** headgear, clothing, vests, backpacks
	** head-mounted devices (NVGs, etc.)		** head-mounted devices (NVGs, etc.)
	* Lower [[viewDistance]]		* Lower [[viewDistance\|view distance]]
	* Lower [[setTerrainGrid\| terrain details]]		* Lower [[setTerrainGrid\|terrain details]]
	* Lower the [[Arma 3: Dynamic Simulation\|Dynamic Simulation]] ~~treshold~~		* Lower the [[Arma 3: Dynamic Simulation\|Dynamic Simulation]] threshold
	* Use [[Arma 3: Simple Objects\|Simple Objects]]		* Use [[Arma 3: Simple Objects\|Simple Objects]]
	* Use '''Garbage Collection''' in order to automatically delete bodies and wreckages:		* Use '''Garbage Collection''' in order to automatically delete bodies and wreckages:
	** {{arma3}}'s Eden-integrated [[Description.ext#~~Corpse_~~.~~26_wreck_management~~\|Garbage Collection]]		** {{arma3}}'s Eden-integrated [[Description.ext#Corpse .26 wreck management\|Garbage Collection]]
	** {{arma2}}'s [[Garbage Collector]]		** {{arma2}}'s [[Garbage Collector]]
	** {{tkoh}}'s [[BIS_fnc_GC]]		** {{tkoh}}'s [[BIS_fnc_GC]]
	{{ Feature \| ~~Informative~~ \| Only the ''on-screen'' objects will strongly impact GPU. }}		{{Feature\|informative\|Only the ''on-screen'' objects will strongly impact the GPU.}}
	\|-		\|-
	\|		\|
Line 100:		Line 100:
	\| Having too many scripts running is a cause for severe performance issues and execution delays in singleplayer as well as multiplayer.		\| Having too many scripts running is a cause for severe performance issues and execution delays in singleplayer as well as multiplayer.
	* You can track the number of running scripts using [[diag_activeScripts]]; you can also use:		* You can track the number of running scripts using [[diag_activeScripts]]; you can also use:
	** [[~~diag activeSQFScripts~~]]		** [[diag_activeSQFScripts]]
	** [[~~diag activeSQSScripts~~]]		** [[diag_activeSQSScripts]]
	** [[~~diag activeMissionFSMs~~]]		** [[diag_activeMissionFSMs]]
	* A common bad practice is to [[spawn]] a function for each units that need it; the good practice would be to have a single script working with an array of units, array that is edited (unit added/removed) whenever needed:<!--		* A common bad practice is to [[spawn]] a function for each units that need it; the good practice would be to have a single script working with an array of units, array that is edited (unit added/removed) whenever needed:<!--
	--><sqf>		--><sqf>
Line 114:		Line 114:

	private _myScript = compile preprocessFileLineNumbers "myScript.sqf";		private _myScript = compile preprocessFileLineNumbers "myScript.sqf";
	while { sleep 5; alive player } do { player spawn _myScript; }; // ~~good~~		while { sleep 5; alive player } do { player spawn _myScript; }; // better

			while { sleep 5; alive player } do { player spawn TAG_fnc_myScript; }; // perfect! see [[Arma 3: Functions Library\|Functions]]
	</sqf>		</sqf>
	\|-		\|-
Line 125:		Line 127:
	* A [[while]]-loop checking without a minimum loop-[[sleep]] time is usually a sign of bad conception.<!--		* A [[while]]-loop checking without a minimum loop-[[sleep]] time is usually a sign of bad conception.<!--
	--><sqf>		--><sqf>
	while { true } // bad if you ~~don't~~ know what you are doing		while { true } // bad if you do not know what you are doing
	while { alive player } // better		while { alive player } // better
	while { sleep 1 ; alive player } // perfect		while { sleep 1 ; alive player } // perfect
	</sqf>		</sqf>
	* By default, [[Trigger]]s check their set condition '''every 0.5 second'''. If a large area is covered or condition code is too complex, this can become an issue; the triggers should then be converted to scripts if possible. Since {{GVI\|arma3\|2.00}} it is possible to change trigger intervals, either via [[~~Eden_Editor~~:~~_Entity_Attributes~~\|trigger attributes]] in [[:Category:Eden Editor\|3DEN]], or via the scripting command [[setTriggerInterval]].		* By default, [[Trigger]]s check their set condition '''every 0.5 second'''. If a large area is covered or condition code is too complex, this can become an issue; the triggers should then be converted to scripts if possible. Since {{GVI\|arma3\|2.00}} it is possible to change trigger intervals, either via [[Eden Editor: Entity Attributes\|trigger attributes]] in [[:Category:Eden Editor\|3DEN]], or via the scripting command [[setTriggerInterval]].
	* [[Trigger]]s can be made '''Server-Side only''' to save clients' resources.		* [[Trigger]]s can be made '''Server-Side only''' to save clients' resources.
	{{Feature \| important \| All of the mission-related calculation (objectives, completion distance, etc.) must be done '''server-side'''. Local effects should be calculated '''client-side'''.}}		{{Feature \| important \| All of the mission-related calculation (objectives, completion distance, etc.) must be done '''server-side'''. Local effects should be calculated '''client-side'''.}}
Line 151:		Line 153:
	\| {{Colorball\|green}}		\| {{Colorball\|green}}
	\| {{Colorball\|green}}		\| {{Colorball\|green}}
	\| [[Scheduler#~~Unscheduled_Environment~~\|Unscheduled code]] can have a high impact on the framerate, as such code is not subject to the [[Scheduler\|scheduler]]'s management (as its name suggests) and will run without limitation. Cyclic unscheduled low-performance code can make the game unplayable, up to freezing it.		\| [[Scheduler#Unscheduled Environment\|Unscheduled code]] can have a high impact on the framerate, as such code is not subject to the [[Scheduler\|scheduler]]'s management (as its name suggests) and will run without limitation. Cyclic unscheduled low-performance code can make the game unplayable, up to freezing it.
	* As only time-critical scripts should run unscheduled, [[spawn]] any other code from unscheduled environment once you have the required results:<!--		* As only time-critical scripts should run unscheduled, [[spawn]] any other code from unscheduled environment once you have the required results:<!--
	--><sqf>		--><sqf>
Line 158:		Line 160:
	/* ... */ // other unscheduled code		/* ... */ // other unscheduled code
	</sqf>		</sqf>
	{{ Feature \| ~~Informative~~ \| See also [[Scheduler#Where code starts unscheduled~~\|Where code starts unscheduled]]~~. }}		{{Feature\|informative\|See also {{Link\|Scheduler#Where code starts unscheduled}}.}}
	\|}		\|}


	== What ~~else~~? ==		== What Else? ==

	If you have applied all these recommendations and your mission still ~~doesn't~~ run well in multiplayer (but does in singleplayer),		If you have applied all these recommendations and your mission still does not run well in multiplayer (but does in singleplayer),
	it might be caused by '''mods''' that you are running which could be badly, or not at all, optimised.		it might be caused by '''mods''' that you are running which could be badly, or not at all, optimised.

Line 170:		Line 172:


	== Performance Diagnostic ~~tools~~ ==		== Performance Diagnostic Tools ==

	=== Server Commands ===		=== Server Commands ===
Line 179:		Line 181:
	** Shows performance information in the dedicated server console. Interval 0 means to stop monitoring. (since {{arma3}} v1.64)		** Shows performance information in the dedicated server console. Interval 0 means to stop monitoring. (since {{arma3}} v1.64)

	=== Diagnostic ~~commands~~ ===		=== Diagnostic Commands ===
	* [[:Category:~~Arma_3~~:~~_Scripting_Commands~~:~~_Diagnostic_Branch~~\|Diag. commands only available in Diagnostic Branch]]
	* [[:Category:~~Command_Group~~:~~_Diagnostic~~\|Diag. command available in all builds]]		* [[:Category:Arma 3: Scripting Commands: Diagnostic Branch\|Diag. commands only available in Diagnostic Branch]]
			* [[:Category:Command Group: Diagnostic\|Diag. command available in all builds]]


Line 190:		Line 193:
	* [[Code Best Practices]]		* [[Code Best Practices]]
	* [[Performance Profiling]]		* [[Performance Profiling]]
	* [[User:Dedmen\|Dedmen]]'s [[ArmaScriptProfiler]] ({{Link\|~~link=~~ https://forums.bohemia.net/forums/topic/211626-arma-script-profiler/\|~~text=~~ forum post}})		* [[User:Dedmen\|Dedmen]]'s [[ArmaScriptProfiler]] ({{Link\|https://forums.bohemia.net/forums/topic/211626-arma-script-profiler/\|forum post}})


	[[Category:Arma Scripting Tutorials]]		[[Category:Arma Scripting Tutorials]]

Lou Montana: Text replacement - "[[Arma 3 " to "[[Arma 3: "

2024-05-06T09:38:20Z

Text replacement - "[[Arma 3 " to "[[Arma 3: "

← Older revision		Revision as of 11:38, 6 May 2024
Line 37:		Line 37:
	** [[Arma 3: Revive]]		** [[Arma 3: Revive]]
	** [[Arma 3: Task Framework]]		** [[Arma 3: Task Framework]]
	** [[Arma 3 Animated Briefing]]		** [[Arma 3: Animated Briefing]]
	** [[Arma 3 Animated Opening]]		** [[Arma 3: Animated Opening]]
	** [[Arma 3: Dynamic Groups]]		** [[Arma 3: Dynamic Groups]]
	** [[Arma 3: Key Frame Animation]]		** [[Arma 3: Key Frame Animation]]
Line 69:		Line 69:
	* If a client has a low-end machine, they shouldn't lead a group of many AIs as these would then be locally computed.		* If a client has a low-end machine, they shouldn't lead a group of many AIs as these would then be locally computed.
	* [[Arma 3: Dynamic Simulation]] allows you to freeze AI that are distant from players. Many distance settings should be set according to the mission.		* [[Arma 3: Dynamic Simulation]] allows you to freeze AI that are distant from players. Many distance settings should be set according to the mission.
	{{ Feature \| Informative \| If you own more than one average computer, you could consider [[Arma 3 Headless Client\|Headless client]] to offload AI from the server. }}		{{ Feature \| Informative \| If you own more than one average computer, you could consider [[Arma 3: Headless Client\|Headless client]] to offload AI from the server. }}
	\|-		\|-
	\|		\|
Line 85:		Line 85:
	* Lower [[viewDistance]]		* Lower [[viewDistance]]
	* Lower [[setTerrainGrid\| terrain details]]		* Lower [[setTerrainGrid\| terrain details]]
	* Lower the [[Arma 3 Dynamic Simulation\|Dynamic Simulation]] treshold		* Lower the [[Arma 3: Dynamic Simulation\|Dynamic Simulation]] treshold
	* Use [[Arma 3 Simple Objects\|Simple Objects]]		* Use [[Arma 3: Simple Objects\|Simple Objects]]
	* Use '''Garbage Collection''' in order to automatically delete bodies and wreckages:		* Use '''Garbage Collection''' in order to automatically delete bodies and wreckages:
	** {{arma3}}'s Eden-integrated [[Description.ext#Corpse_.26_wreck_management\|Garbage Collection]]		** {{arma3}}'s Eden-integrated [[Description.ext#Corpse_.26_wreck_management\|Garbage Collection]]

Lou Montana: Text replacement - "Arma 3 Key Frame Animation" to "Arma 3: Key Frame Animation"

2024-04-23T20:52:35Z

Text replacement - "Arma 3 Key Frame Animation" to "Arma 3: Key Frame Animation"

← Older revision		Revision as of 22:52, 23 April 2024
Line 40:		Line 40:
	** [[Arma 3 Animated Opening]]		** [[Arma 3 Animated Opening]]
	** [[Arma 3: Dynamic Groups]]		** [[Arma 3: Dynamic Groups]]
	** [[Arma 3 Key Frame Animation]]		** [[Arma 3: Key Frame Animation]]
	** and most importantly: [[Functions]]		** and most importantly: [[Functions]]

Lou Montana: Text replacement - "{{Feature|Informative|" to "{{Feature|informative|"

2024-02-01T23:24:22Z

Text replacement - "{{Feature|Informative|" to "{{Feature|informative|"

← Older revision		Revision as of 01:24, 2 February 2024
Line 46:		Line 46:
	== Performance Impact Table ==		== Performance Impact Table ==

	{{Feature\|~~Informative~~\|		{{Feature\|informative\|
	: {{Colorball\|red\|1.125}} means a heavy impact on performance<br>		: {{Colorball\|red\|1.125}} means a heavy impact on performance<br>
	: {{Colorball\|orange\|1.125}} means an average impact<br>		: {{Colorball\|orange\|1.125}} means an average impact<br>

Lou Montana: Text replacement - " +\[ +" to " ["

2023-11-08T16:48:30Z

Text replacement - " +\[ +" to " ["

← Older revision		Revision as of 18:48, 8 November 2023
Line 18:		Line 18:
	** {{Link\|https://www.moddb.com/forum/thread/arma-2-ultimate-tweak-thread\|{{arma2}} performance guide}}		** {{Link\|https://www.moddb.com/forum/thread/arma-2-ultimate-tweak-thread\|{{arma2}} performance guide}}
	** {{Link\|https://forums.bohemia.net/forums/topic/50167-pc-optimization-for-arma/\|{{arma1}} performance guide}}<!--		** {{Link\|https://forums.bohemia.net/forums/topic/50167-pc-optimization-for-arma/\|{{arma1}} performance guide}}<!--
	** [ {{ofp}} performance guide]		** [{{ofp}} performance guide]
	-->		-->
	* Play your mission in singleplayer. If your mission runs fine, its network messages might very well be the issue. See [[Multiplayer Scripting]] for good practice tips.		* Play your mission in singleplayer. If your mission runs fine, its network messages might very well be the issue. See [[Multiplayer Scripting]] for good practice tips.

Lou Montana: Text replacement - "\[\[Eden( |_)Editor(\||\])" to "[[:Category:Eden Editor$2"

2023-07-09T12:21:20Z

Text replacement - "\[\[Eden( |_)Editor(\||\])" to "[[:Category:Eden Editor$2"

← Older revision		Revision as of 14:21, 9 July 2023
Line 129:		Line 129:
	while { sleep 1 ; alive player } // perfect		while { sleep 1 ; alive player } // perfect
	</sqf>		</sqf>
	* By default, [[Trigger]]s check their set condition '''every 0.5 second'''. If a large area is covered or condition code is too complex, this can become an issue; the triggers should then be converted to scripts if possible. Since {{GVI\|arma3\|2.00}} it is possible to change trigger intervals, either via [[Eden_Editor:_Entity_Attributes\|trigger attributes]] in [[~~Eden_Editor~~\|3DEN]], or via the scripting command [[setTriggerInterval]].		* By default, [[Trigger]]s check their set condition '''every 0.5 second'''. If a large area is covered or condition code is too complex, this can become an issue; the triggers should then be converted to scripts if possible. Since {{GVI\|arma3\|2.00}} it is possible to change trigger intervals, either via [[Eden_Editor:_Entity_Attributes\|trigger attributes]] in [[:Category:Eden Editor\|3DEN]], or via the scripting command [[setTriggerInterval]].
	* [[Trigger]]s can be made '''Server-Side only''' to save clients' resources.		* [[Trigger]]s can be made '''Server-Side only''' to save clients' resources.
	{{Feature \| important \| All of the mission-related calculation (objectives, completion distance, etc.) must be done '''server-side'''. Local effects should be calculated '''client-side'''.}}		{{Feature \| important \| All of the mission-related calculation (objectives, completion distance, etc.) must be done '''server-side'''. Local effects should be calculated '''client-side'''.}}

Lou Montana: Some wiki formatting

2023-02-27T19:58:16Z

Some wiki formatting

← Older revision		Revision as of 21:58, 27 February 2023
Line 1:		Line 1:
	{{TOC\|side}}		{{TOC\|side}}
	{{ Feature \| ~~Informative~~ \| This page is about [[Mission Optimisation]]. For ''scripting'' optimisation, see [[Code Optimisation]]. }}		{{Feature\|informative\|This page is about [[Mission Optimisation]]. For ''scripting'' optimisation, see [[Code Optimisation]].}}
	~~== Introduction ==~~

	This article will try to be a general guide about improving your '''mission's''' performance.<br>		This article will try to be a general guide about improving your '''mission's''' performance.<br>
	As usual, moderation is the key; do not expect to find on this page a magical solution that makes it possible to run thousands of AI at ~~144~~ FPS. Everything comes at a cost, the tweaks here will simply allow you to locate issues and calibrate your mission properly.		As usual, moderation is the key; do not expect to find on this page a magical solution that makes it possible to run thousands of AI at 240 FPS.
			Everything comes at a cost, the tweaks here will simply allow you to locate issues and calibrate your mission properly.


	== Before ~~anything~~ ==		== Before Anything ==

	Before optimising anything, make sure you do not have any performance issue running the game itself:		Before optimising anything, make sure you do not have any performance issue running the game itself:
Line 15:		Line 15:
	** '''Steam''' allows you to display FPS in a screen corner, in ''Settings > In game > FPS Counter''		** '''Steam''' allows you to display FPS in a screen corner, in ''Settings > In game > FPS Counter''
	* Use (unofficial) Performance Guides to get better performances:		* Use (unofficial) Performance Guides to get better performances:
	** {{Link\|~~link=~~ https://steamcommunity.com/sharedfiles/filedetails/?id=1731305438\|~~text=~~ {{arma3}} performance guide}}		** {{Link\|https://steamcommunity.com/sharedfiles/filedetails/?id{{=}}1731305438\|{{arma3}} performance guide}}
	** [https://www.moddb.com/forum/thread/arma-2-ultimate-tweak-thread {{arma2}} performance guide]		** {{Link\|https://www.moddb.com/forum/thread/arma-2-ultimate-tweak-thread\|{{arma2}} performance guide}}
	** {{Link\|~~link=~~ https://forums.bohemia.net/forums/topic/50167-pc-optimization-for-arma/\|~~text=~~ {{arma1}} performance guide}}<!--		** {{Link\|https://forums.bohemia.net/forums/topic/50167-pc-optimization-for-arma/\|{{arma1}} performance guide}}<!--
	** [ {{ofp}} performance guide]		** [ {{ofp}} performance guide]
	-->		-->
Line 24:		Line 24:
	** Lower your graphical settings (resolution, textures). If you get way better performances, at least your '''GPU''' limits you.		** Lower your graphical settings (resolution, textures). If you get way better performances, at least your '''GPU''' limits you.
	** If the game keeps having low FPS when running @ 1024×768/low textures then your CPU is most likely the issue. Mission scripts may be performance-hogging too.		** If the game keeps having low FPS when running @ 1024×768/low textures then your CPU is most likely the issue. Mission scripts may be performance-hogging too.
	{{ Feature \| important \| Please note that [[viewDistance\|view distance]] (among other settings) impacts both GPU and CPU! }}		{{Feature\|important\|Please note that [[viewDistance\|view distance]] (among other settings) impacts both GPU and CPU!}}
	{{ Feature \| ~~Informative~~ \| [[viewDistance\|View distance]] can be separately set for each clients independently from the server's value through scripting.<br>		{{Feature\|informative\|[[viewDistance\|View distance]] can be separately set for each clients independently from the server's value through scripting.<br>This can make or break performance for the client.}}
	This can make or break performance for the client. }}


	== Creating your ~~mission~~ ==		== Creating your Mission ==

	* Be sure to create your scripts with the latest available commands and functions.		* Be sure to create your scripts with the latest available commands and functions.
Line 45:		Line 44:


	== Performance ~~impact table~~ ==		== Performance Impact Table ==

	{{Feature\|Informative\|		{{Feature\|Informative\|
Line 53:		Line 52:
	}}		}}

	{\| class="wikitable"		{\| class="wikitable align-center-col-2 align-center-col-3 align-center-col-4"
	! Topic		! Topic
	! CPU		! CPU
Line 95:		Line 94:
	\|-		\|-
	\|		\|

	==== General script mistakes ====		==== General script mistakes ====
	\| {{Colorball\|orange}}		\| {{Colorball\|orange}}
Line 174:		Line 172:
	== Performance Diagnostic tools ==		== Performance Diagnostic tools ==

	=== Server ~~commands~~ ===		=== Server Commands ===

	* [[Multiplayer Server Commands#Commands\|#monitor]] 5		* [[Multiplayer Server Commands#Commands\|#monitor]] 5
Line 185:		Line 183:
	* [[:Category:Command_Group:_Diagnostic\|Diag. command available in all builds]]		* [[:Category:Command_Group:_Diagnostic\|Diag. command available in all builds]]

	== See ~~also~~ ==
			== See Also ==

	* [[Multiplayer Scripting]]		* [[Multiplayer Scripting]]

Lou Montana: Text replacement - "{{ExternalLink|" to "{{Link|"

2023-01-04T15:23:38Z

Text replacement - "{{ExternalLink|" to "{{Link|"

← Older revision		Revision as of 17:23, 4 January 2023
Line 15:		Line 15:
	** '''Steam''' allows you to display FPS in a screen corner, in ''Settings > In game > FPS Counter''		** '''Steam''' allows you to display FPS in a screen corner, in ''Settings > In game > FPS Counter''
	* Use (unofficial) Performance Guides to get better performances:		* Use (unofficial) Performance Guides to get better performances:
	** {{~~ExternalLink~~\|link= https://steamcommunity.com/sharedfiles/filedetails/?id=1731305438\|text= {{arma3}} performance guide}}		** {{Link\|link= https://steamcommunity.com/sharedfiles/filedetails/?id=1731305438\|text= {{arma3}} performance guide}}
	** [https://www.moddb.com/forum/thread/arma-2-ultimate-tweak-thread {{arma2}} performance guide]		** [https://www.moddb.com/forum/thread/arma-2-ultimate-tweak-thread {{arma2}} performance guide]
	** {{~~ExternalLink~~\|link= https://forums.bohemia.net/forums/topic/50167-pc-optimization-for-arma/\|text= {{arma1}} performance guide}}<!--		** {{Link\|link= https://forums.bohemia.net/forums/topic/50167-pc-optimization-for-arma/\|text= {{arma1}} performance guide}}<!--
	** [ {{ofp}} performance guide]		** [ {{ofp}} performance guide]
	-->		-->
Line 191:		Line 191:
	* [[Code Best Practices]]		* [[Code Best Practices]]
	* [[Performance Profiling]]		* [[Performance Profiling]]
	* [[User:Dedmen\|Dedmen]]'s [[ArmaScriptProfiler]] ({{~~ExternalLink~~\|link= https://forums.bohemia.net/forums/topic/211626-arma-script-profiler/\|text= forum post}})		* [[User:Dedmen\|Dedmen]]'s [[ArmaScriptProfiler]] ({{Link\|link= https://forums.bohemia.net/forums/topic/211626-arma-script-profiler/\|text= forum post}})


	[[Category:Arma Scripting Tutorials]]		[[Category:Arma Scripting Tutorials]]

Lou Montana: Fix code

2022-12-13T17:37:04Z

Fix code

← Older revision		Revision as of 19:37, 13 December 2022
Line 156:		Line 156:
	* As only time-critical scripts should run unscheduled, [[spawn]] any other code from unscheduled environment once you have the required results:<!--		* As only time-critical scripts should run unscheduled, [[spawn]] any other code from unscheduled environment once you have the required results:<!--
	--><sqf>		--><sqf>
	(...) // unscheduled code		/* ... */ // unscheduled code
	[_var1, _var2] spawn TAG_fnc_MyFunction;		[_var1, _var2] spawn TAG_fnc_MyFunction;
	(...) // other unscheduled code		/* ... */ // other unscheduled code
	</sqf>		</sqf>
	{{ Feature \| Informative \| See also [[Scheduler#Where code starts unscheduled\|Where code starts unscheduled]]. }}		{{ Feature \| Informative \| See also [[Scheduler#Where code starts unscheduled\|Where code starts unscheduled]]. }}