arma2:scripting
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
arma2:scripting [2012/08/26 12:08] – added initjipcompatible.sqf info. snakeman | arma2:scripting [2024/08/01 22:38] (current) – links added. snakeman | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Scripting ====== | + | ====== |
+ | |||
+ | [[https:// | ||
ArmA 2 will be largely compatible with Armed Assault. To make porting of content from ArmA as simple as possible, there are few important things: | ArmA 2 will be largely compatible with Armed Assault. To make porting of content from ArmA as simple as possible, there are few important things: | ||
Line 9: | Line 11: | ||
* in order to maintain smooth frame rate in real-time content, time limit for all scripts in each frame is enforced by the engine in ArmA 2. Generally speaking, in case of more demanding scripts, be prepared that their result may come way later and also there probably can suffer from significant latency. It is under evaluation if and how possibly allow user scripts to change how much time they may take from the CPU in every frame. | * in order to maintain smooth frame rate in real-time content, time limit for all scripts in each frame is enforced by the engine in ArmA 2. Generally speaking, in case of more demanding scripts, be prepared that their result may come way later and also there probably can suffer from significant latency. It is under evaluation if and how possibly allow user scripts to change how much time they may take from the CPU in every frame. | ||
- | * SQS script format will be fully supported in ArmA 2. | + | * SQS script format will be fully supported in ArmA 2 (but they should never be used). |
**initJIPcompatible.sqf** initJIPcompatible.sqf gets called from the MP mission framework (scripts in modules MP directory). A script waits until the player object is initialized and execs initJIPcompatible.sqf on clients (all clients, even those that were allready there at mission start as it is basically the same). Has nothing todo with init.sqf. | **initJIPcompatible.sqf** initJIPcompatible.sqf gets called from the MP mission framework (scripts in modules MP directory). A script waits until the player object is initialized and execs initJIPcompatible.sqf on clients (all clients, even those that were allready there at mission start as it is basically the same). Has nothing todo with init.sqf. | ||
Line 34: | Line 36: | ||
Global scripts dir or common scripts dir is very useful. This feature has been known since OFP, check out the details from [[arma: | Global scripts dir or common scripts dir is very useful. This feature has been known since OFP, check out the details from [[arma: | ||
+ | |||
+ | Howto create and use [[arma2: | ||
+ | |||
+ | [[arma2: | ||
+ | |||
+ | [[arma2: | ||
+ | |||
+ | [[arma2: | ||
+ |
arma2/scripting.1345982917.txt.gz · Last modified: 2012/08/26 12:08 (external edit)