Lou Montana/Sandbox – User
Lou Montana (talk | contribs) m (Fix line return) |
Lou Montana (talk | contribs) m (Add See Also) |
||
Line 1: | Line 1: | ||
{{SideTOC}} | {{SideTOC}} | ||
{{ Informative | This page is about [[Mission Optimisation]]. For ''scripting'' optimisation, see [[Code Optimisation]]. }} | |||
== Introduction == | == Introduction == | ||
This article will try to be a general guide about improving your '''mission's''' | This article will try to be a general guide about improving your '''mission's''' performance.<br> | ||
As usual, moderation is the key | As usual, moderation is the key; do not expect to find here a magical solution to run thousands of AI at 144 FPS. Everything comes at a cost, the tweaks on this page will simply allow you to calibrate your mission properly. | ||
Line 93: | Line 92: | ||
| {{colorball|green}} | | {{colorball|green}} | ||
| | | | ||
* A [[while]]-loop checking without a minimum loop-[[sleep]] time is usually a sign of bad conception. | Checking a condition too often is usually a source of poor performance. Does your code execution need to be frame-perfect, or can you afford a delay of some seconds? | ||
* A [[while]]-loop checking without a minimum loop-[[sleep]] time is usually a sign of bad conception.<code>[[while]] { [[true]] } {{codecomment|// already "bad" if you don't know what you are doing}}<br>[[while]] { [[alive]] [[player]] } {{codecomment|// better}}<br>[[while]] { [[sleep]] 1 ; [[alive]] [[player]] } {{codecomment|// perfect}}</code> | |||
* [[trigger|Triggers]] check their set condition '''every 0.5 second''' (hardcoded value). If a large area is covered or condition code is too complex, this can be an issue. Convert them to scripts then. | * [[trigger|Triggers]] check their set condition '''every 0.5 second''' (hardcoded value). If a large area is covered or condition code is too complex, this can be an issue. Convert them to scripts then. | ||
|- | |- | ||
Line 118: | Line 118: | ||
If you want to be sure, run the same mission with and without mods. If you have a big difference in performance, look no further. | If you want to be sure, run the same mission with and without mods. If you have a big difference in performance, look no further. | ||
== See also == | |||
* [[Multiplayer Scripting]] | |||
* [[Code Optimisation]] | |||
Revision as of 15:04, 29 June 2019
Introduction
This article will try to be a general guide about improving your mission's performance.
As usual, moderation is the key; do not expect to find here a magical solution to run thousands of AI at 144 FPS. Everything comes at a cost, the tweaks on this page will simply allow you to calibrate your mission properly.
Before anything
Before optimising anything, make sure you do not have any performance issue running the game itself:
- Open the editor, place a unit in the area you like and test your computer.
- Arma 3 displays FPS when you go into video options
- Steam allows you to display FPS in a screen corner, in Settings > In game > FPS Counter
- Use (unofficial) Performance Guides to get better performances:
- 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.
- Usual bottlenecks:
- 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.
Creating your mission
- Be sure to create your scripts with the latest available commands and functions.
- In Arma 3 use remoteExec / remoteExecCall and DITCH BIS_fnc_MP FOR GOOD! See Arma 3 Remote Execution for more information.
- In Arma 2 network communication is done using the Multiplayer framework.
- Use the available frameworks and functions for each topic, unless you replace them by third-party ones:
Performance impact table
Topic | CPU | GPU | Net- work |
Solution |
---|---|---|---|---|
AI units quantity |
Template:colorball | Template:colorball | Template:colorball |
|
Objects quantity |
Template:colorball | Template:colorball | Template:colorball | The less objects, the more FPS you will have.
|
High-frequency scripts |
Template:colorball | Template:colorball | Template:colorball |
Checking a condition too often is usually a source of poor performance. Does your code execution need to be frame-perfect, or can you afford a delay of some seconds?
|
High-frequency network messages |
Template:colorball | Template:colorball | Template:colorball |
|
What else?
You have applied all these recommendations and yet, your mission still doesn't run well in multiplayer (but does in singleplayer); an answer to that is that you are using mods, of which some are not well optimised, if at all.
If you want to be sure, run the same mission with and without mods. If you have a big difference in performance, look no further.