Differences

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

--- arma2:port_arma [2011/08/06 10:07] – removed pmctodo status as it seems fine as is. snakeman
+++ arma2:port_arma [2024/08/02 12:25] (current) – links added. snakeman
@@ Line 1: / Line 1: @@
 ====== ArmA to ArmA 2 port ======
+[[https://www.pmctactical.org/forum/viewforum.php?f=50|ArmA 2 Forum]], [[:arma2|ArmA 2 Home]], [[arma2:config|ArmA 2 Config]], [[arma2:file_formats|ArmA 2 File Formats]], [[arma2:missions|ArmA 2 Missions]], [[arma2:modeling|ArmA 2 3D Modeling]], [[arma2:scripting|ArmA 2 Scripting]], [[arma2:terrain|ArmA 2 Terrain]], [[arma2:texturing|ArmA 2 Texturing]], [[arma2:tools|ArmA 2 Tools]]
 How to port Armed Assault addon to ArmA 2. Also know as how to convert ArmA addon / mod. See also [[arma2:port_ofp|port OFP addon]].
@@ Line 517: / Line 519: @@
 That is the nutshell of how to port working ArmA character to ArmA 2. The soldier is then pretty much done, there is not more fine tuning than that.
-This tutorial is very short and not very descriptive, feel free to ask questions and/or offer solutions in [[http://tactical.nekromantix.com/forum/viewtopic.php?f=53&t=21950|Porting ArmA (1) addon]] forum topic.
+This tutorial is very short and not very descriptive, feel free to ask questions and/or offer solutions in [[http://www.pmctactical.org/forum/viewtopic.php?f=53&t=21950|PMC Tactical forum Porting ArmA (1) addon]] topic.
 ====== Terrain ======
-Many objects in ArmA are not included in ArmA 2 anymore, this causes serious problems for porting terrains. The simplest way is to just include the objects found in your ArmA terrain into the extra "objects pbo" alongside with your new ArmA 2 terrain. This might not be the best choice regarding download sizes if you have rich ArmA object usage, but there just isn't any other practical way of doing it.
+Many objects in ArmA are not included in ArmA 2 anymore, this causes serious problems for porting terrains. The simplest way is to just include the objects found in your ArmA terrain into the extra "objects pbo" alongside with your new ArmA 2 terrain. This might not be the best choice regarding download sizes if you have rich ArmA object usage, but there just isn't any other practical way of doing it. Also remember that if each and every terrain maker includes this and that objects, then we end up the ArmA objects duped all over the community dozens of times and just using one major addon like CAA1 would be much better. However using CAA1 for just "few" objects is not practical due its (about 2gb) size.
 To be more specific about objects you can just switch to ArmA 2 ones, are roads.
@@ Line 537: / Line 539: @@
 | ca\roads\sil | ca\roads2\asf1_ |
 | ca\roads\silnice | ca\roads2\asf1_ |
+Some of the ArmA roads when changed to use ArmA 2 roads, cause ugly caps appearing in the road network, not on each and every piece but just maybe one, we do not have the object name and we assume its one object. Its most likely the ca\roads2\asf2_ road type.
 **The above roads list is work in progress and unconfirmed! please use caution when using this guide!**
-PMCTODO this terrain header is work in progress, please post to our forums if you wish to help.
+**ArmA To ArmA 2 Roads**
+When porting ArmA roads into ArmA 2, meaning you just swap using arma ca\roads\asf25 to arma2 ca\roads2\asf25 then you get slight gaps in the road curves and perhaps other parts too, its barely noticeable though.
+Possible solutions would be to remake the roads using actual ArmA 2 objects, but most cases that is not viable option (too much work).
@@ Line 552: / Line 560: @@
 Of course the "pos_driver" can be anything, BIS uses "pos driver" without the underscore, we use with underscore. The memory point name is defined in config.cpp for the vehicle.