Differences

This shows you the differences between two versions of the page.

--- arma:ofpport [2009-04-16 10:58]
snakeman added wip stuff for config porting. formatted, fixed typos, etc.
+++ arma:ofpport [2009-04-17 11:04]
snakeman added mission porting information.
@@ Line 186: / Line 186: @@
 In all LODs choose zasleh selection, in Face Properties (E) put User Value to 0 and untick Enable Shadow completely. Then in Properties (SHIFT-E) set Lighting (Obsolete) setting to Normal. Its funny that it says obsolete, but if you leave it to for example Shining, then your muzzle flash is blackened out heh.
+====== Mission ======
+Porting a mission is semi easy with just the classnames being changed.
+Triggers (sensors), Radios and Gamelogic's all seem to be the same classnaming in OFP and ArmA, so there is no problems.
+It is merely copying the mission dir into the users dir, then initially porting over init.sqs to init.sqf as that is usually very short script. Then loading the mission first time in ArmA and the errors start to pour in. Mostly its missing OFP classnames which have to be removed or changed, mostly its just changing like missing CoC Unified Artillery pieces to "Barrels" classname, then when you finally got the mission loaded, just delete these Barrels or change them to the ArmA artillery pieces. Other classnames are always up to the mission, you just need to work your way through them either by just deleting them or changing them to ArmA counterparts.
+For starters the biggest thing is to get the mission loading in the mission editor. When the mission is loaded and you can preview it, you will most likely start to get errors from those SQS scripts or the other OFP style mission making. It really comes down to how complex the mission is, if its very simple one you have not much work to do, but complex missions are harder to downright impossible to port (at least 1:1 scale).

PMC Editing Wiki

User Tools

Site Tools

Differences

Page Tools