arma2:beginner_editing_guide
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
arma2:beginner_editing_guide [2009-11-24 10:14] snakeman added what you should not do part. |
arma2:beginner_editing_guide [2022-06-25 13:54] (current) snakeman added link. |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| This guide //should// get a complete newbie into ArmA 2 editing. While it might not do Newbie -> Hardcore conversion, it is still vital for anyone getting into editing. While this is not a tutorial to get some specific task done, its the core essence of editing, if you don't know absolutely anything, this will get you started. | This guide //should// get a complete newbie into ArmA 2 editing. While it might not do Newbie -> Hardcore conversion, it is still vital for anyone getting into editing. While this is not a tutorial to get some specific task done, its the core essence of editing, if you don't know absolutely anything, this will get you started. | ||
| + | |||
| + | If anyone wants to join PMC team to work on some of our addons/mods, we would teach beginners each step of addon making, it would be great learning experience. You could then use these learned skills to make your own addons/mods. If you are interested, get in touch with us [[https://www.pmctactical.org/|PMC Tactical]]. | ||
| Line 10: | Line 12: | ||
| PBO files are addons in a packet. | PBO files are addons in a packet. | ||
| - | PBO files are located in the <arma2 root>\addons\ directory, or in any directory you specify to be used with the -mod parameter. More info in [[arma:startup_parameters|startup parameters]] and in [[arma:modfolders|mod folders]] pages. | + | PBO files are located in the <arma2 root>\addons\ directory, or in any directory you specify to be used with the -mod parameter. More info in [[arma:startup_parameters|startup parameters]] and in [[arma:moddirs|mod folders]] pages. |
| Don't confuse the pbo files to the <addon_name>.pbo.bi.bisign as those are the signature key files for multiplayer purposes. | Don't confuse the pbo files to the <addon_name>.pbo.bi.bisign as those are the signature key files for multiplayer purposes. | ||
| Line 19: | Line 21: | ||
| Config.cpp is the games configuration file for the given addon. Config.cpp can be also found in the <arma2 root>\bin\ directory which is the games main configuration file. Config.cpp is what makes the addon work. | Config.cpp is the games configuration file for the given addon. Config.cpp can be also found in the <arma2 root>\bin\ directory which is the games main configuration file. Config.cpp is what makes the addon work. | ||
| - | If config.cpp file is binarized it will become "config.bin" and cannot be read with text editor. You can create text format config.cpp file from the .bin file with unRap tool. You really don't have to worry about creating bin out of cpp file right now. | + | If config.cpp file is binarized it will become "config.bin" and cannot be read with text editor. You can create text format config.cpp file from the .bin file with deRapify tool. You really don't have to worry about creating bin out of cpp file right now. |
| Config.cpp file can be (usually) found on each addon's PBO root directory. | Config.cpp file can be (usually) found on each addon's PBO root directory. | ||
| Line 28: | Line 30: | ||
| P3D files are the 3D models. | P3D files are the 3D models. | ||
| - | P3D files can be found really in any dir, in BIS addons they are in the root of the PBO file. | + | P3D files can be found really in any dir, in BIS addons they are //usually// in the root of the PBO file. |
| Line 41: | Line 43: | ||
| Terrains are always in WRP files, like chernarus.wrp for Chernarus. Terrains are edited in Visitor 3. | Terrains are always in WRP files, like chernarus.wrp for Chernarus. Terrains are edited in Visitor 3. | ||
| + | |||
| + | You need to create elevation's for your terrain, this can be done either in [[:tools:wilbur|Wilbur]] or in gray scale image on your favorite image editor. Then you import this elevation into [[arma2:tools:visitor3|Visitor 3]] (v3), place your objects and finally import big satellite mask and satellite texture images. Just before you bring your terrain into in-game, you need to export the actual WRP file out of v3, then pack all to pbo and you're done. | ||
| Line 48: | Line 52: | ||
| Missions will be on two locations, in <arma2 root>\Missions\ and <arma2 root>\MPMissions\ directories, its quite self explanatory but single player missions go to "Missions" dir and multiplayer missions go to "MPMissions" dir. These dirs can have sub directories if you wish to sort your many missions. Also these dirs can have mission directories or pbo's. | Missions will be on two locations, in <arma2 root>\Missions\ and <arma2 root>\MPMissions\ directories, its quite self explanatory but single player missions go to "Missions" dir and multiplayer missions go to "MPMissions" dir. These dirs can have sub directories if you wish to sort your many missions. Also these dirs can have mission directories or pbo's. | ||
| + | |||
| + | //Please read below for Mission Editing for additional details.// | ||
| Line 59: | Line 65: | ||
| ====== arma2.RPT file? ====== | ====== arma2.RPT file? ====== | ||
| - | arma2.RPT file (RPT) found in your ArmA 2 root directory is very important when you want to debug your work, just run the addon/mission in-game for a moment (even few seconds should be enough) and then exit game, then open the RPT file with any text editor and look for warning/error lines in there which are related to your addon. //Take a note that the <arma2>.RPT file is the file name of your ArmA 2 executable, usually and default its "arma2" but it can be anything else too.// | + | arma2.RPT file (RPT) found in your ArmA 2 root directory is very important when you want to debug your work, just run the addon / mission in-game for a moment (even few seconds should be enough) and then exit game, then open the RPT file with any text editor and look for warning / error lines in there which are related to your addon. //Take a note that the <arma2>.RPT file is the file name of your ArmA 2 executable, usually and default its "arma2" but it can be anything else too for example Operation Arrowhead it is "arma2oa".// |
| For more details check out [[arma2:arma2.rpt|arma2.RPT]] page for some errors we have found. | For more details check out [[arma2:arma2.rpt|arma2.RPT]] page for some errors we have found. | ||
| Line 66: | Line 72: | ||
| ====== Tools and Utils? ====== | ====== Tools and Utils? ====== | ||
| - | [[arma2:tools:cpbo|Cpbo]] util packs and unpacks PBO files.\\ | + | [[arma2:tools:extractpbo|ExtractPbo]] util unpacks / opens PBO files.\\ |
| - | [[arma2:tools:binpbo|BinPBO]] official BIS tools to pack PBO files, also binarizes addons.\\ | + | [[arma2:tools:makepbo|MakePbo]] util packs PBO files.\\ |
| - | [[arma2:tools:visitor3|Visitor 3]] (V3) edits and saves WRP terrain files.\\ | + | BinPBO official BIS tools to pack PBO files, also binarizes addons.\\ |
| - | [[arma2:tools:oxygen2|Oxygen 2]] (o2) edits and saves MLOD format P3D 3d model files.\\ | + | Visitor 3 (V3) edits and saves WRP terrain files.\\ |
| - | [[arma2:tools:texview2|TexView 2]] loads tga images and saves paa/pac texture files.\\ | + | Oxygen 2 (o2) edits and saves MLOD format P3D 3d model files.\\ |
| - | [[arma2:tools:unrap|unRap]] unpacks the binary config.bin and .rvmat files. You can use your favorite text editor to edit config.cpp and non binary .rvmat files. | + | TexView 2 loads tga images and saves paa/pac texture files.\\ |
| + | unRap unpacks the binary config.bin and .rvmat files. You can use your favorite text editor to edit config.cpp and non binary .rvmat files. | ||
| For text file editing (scripts sqs, sqf, mission.sqm, rvmat's and config.cpp) we highly recommend using good editor like [[:editing_tools#text_editing|EditPadPro or Notepad++]] so it will highlight the syntax for you and most importantly formats the text properly, notepad is NOT suitable for script/config editing. | For text file editing (scripts sqs, sqf, mission.sqm, rvmat's and config.cpp) we highly recommend using good editor like [[:editing_tools#text_editing|EditPadPro or Notepad++]] so it will highlight the syntax for you and most importantly formats the text properly, notepad is NOT suitable for script/config editing. | ||
| Line 134: | Line 141: | ||
| Mission editing is really easy, in game just open mission editor and off you go. As long as you have one unit selected as "Player" you can use the preview button to play your mission normally. | Mission editing is really easy, in game just open mission editor and off you go. As long as you have one unit selected as "Player" you can use the preview button to play your mission normally. | ||
| - | When you save a mission, the drop down menu gives you choices for export to missions directory or mpmissions directory, this creates the pbo file out of the mission and placed it to the proper dir for you. If you just choose the directory name, it just saves the mission into the Users\<YOURNAME>\Missions\ directory. This users dir is controlled through -profiles parameter. | + | When you save a mission, the drop down menu gives you choices for export to Missions directory or MPMissions directory, this creates the pbo file out of the mission and placed it to the proper dir for you. If you just choose the directory name, it just saves the mission into the Users\<YOURNAME>\Missions\ directory. This users dir is controlled through -profiles parameter. |
| + | |||
| + | When you play multiplayer (MP), any played missions are downloaded from the server and placed on MPMissionsCache directory. If you want to edit or play these missions on your computer, you need to unpack the pbo and move the created directory into Users\<YOURNAME>\Missions\ directory. If you want to host MP session with these missions, copy them into MPMissions directory. | ||
| Of course when you get more deeper into mission editing there is all kinds of trickery with scripts and stuff. | Of course when you get more deeper into mission editing there is all kinds of trickery with scripts and stuff. | ||
| Line 154: | Line 163: | ||
| ====== Notes ====== | ====== Notes ====== | ||
| - | As you see this guide is //very// beginner stuff in attempt to just orientate the newbie into the basic concepts, so feel free to ask more specific questions in our forums [[http://tactical.nekromantix.com/forum/viewforum.php?f=53|ArmA 2 Editing]] area. We would like to write a bit more advanced tutorial next, to go through few specific things, your questions in the forum would really help us to focus on what is important. | + | As you see this guide is //very// beginner stuff in attempt to just orientate the newbie into the basic concepts, so feel free to ask more specific questions in our forums [[https://www.pmctactical.org/forum/viewforum.php?f=53|ArmA 2 Editing]] area. We would like to write a bit more advanced tutorial next, to go through few specific things, your questions in the forum would really help us to focus on what is important. |
| //In PMC Tactical no newbie is looked down upon, we were all newbies once. Its our goal to build this wiki so it will help even the complete beginner guys to learn how to edit.// | //In PMC Tactical no newbie is looked down upon, we were all newbies once. Its our goal to build this wiki so it will help even the complete beginner guys to learn how to edit.// | ||
arma2/beginner_editing_guide.1259057692.txt.gz · Last modified: 2009-11-24 10:14 by snakeman
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
