arma:editing_beginners
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
arma:editing_beginners [2009-11-24 10:14] snakeman added what you should not do part. |
arma:editing_beginners [2016-11-15 07:54] snakeman switched tactical.nekromantix.com to www.pmctactical.org domain. |
||
|---|---|---|---|
| Line 10: | Line 10: | ||
| PBO files are addons in a packet. | PBO files are addons in a packet. | ||
| - | PBO files are located in the <arma 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 <arma 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. |
| Dont confuse the pbo files to the <addon_name>.pbo.bi.bisign as those are the signature key files for multiplayer purposes. | Dont confuse the pbo files to the <addon_name>.pbo.bi.bisign as those are the signature key files for multiplayer purposes. | ||
| Line 19: | Line 19: | ||
| Config.cpp is the games configuration file for the given addon. Config.cpp can be also found in the <arma 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 <arma 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 28: | ||
| 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 41: | ||
| Terrains are always in WRP files, like sara.wrp for Sahrani. Terrains are edited in Visitor 3. | Terrains are always in WRP files, like sara.wrp for Sahrani. Terrains are edited in Visitor 3. | ||
| + | |||
| + | You need to create elevation's for your terrain, this can be done either in Wilbur or in gray scale image on your favorite image editor. Then you import this elevation into [[arma: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 50: | ||
| Missions will be on two locations, in <arma root>\Missions\ and <arma 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 <arma root>\Missions\ and <arma 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 134: | Line 138: | ||
| 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 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 160: | ||
| ====== Notes ====== | ====== Notes ====== | ||
| - | As you see this tutorial is //very// beginner stuff in attempt to just orientate the newbie ArmA editor into the basic concepts, so feel free to ask more specific questions in our forums [[http://tactical.nekromantix.com/forum/viewforum.php?f=29|ArmA 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 tutorial is //very// beginner stuff in attempt to just orientate the newbie ArmA editor into the basic concepts, so feel free to ask more specific questions in [[http://www.pmctactical.org/forum/viewforum.php?f=29|PMC Tactical forums ArmA 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.// | ||
arma/editing_beginners.txt · Last modified: 2022-06-25 13:54 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
