武装突袭 Wiki
探索
首页
讨论板
所有页面
社区页
交互式地图
最新博文
页面
最新页面
Contact Reports
Hotshot's Sandbox
DIK KeyCodes
Curator
武装突袭 Wiki
Product.cpp/bin File Format
Oxygen Light
最新博客
分类
Uploaded with UploadWizard
Face A2 Face101.jpg
Face A2 Face102.jpg
Face A2 Face103.jpg
Face A2 Face104.jpg
Face A2 Face105.jpg
Face A2 Face106.jpg
Face A2 Face107.jpg
含有损坏文件链接的页面
Eden Editor: Introduction
Eden Editor: Switching from 2D Editor
Eden Editor: Menu Bar
Eden Editor: Asset Browser
Eden Editor: Toolbar
Eden Editor: Status Bar
Eden Editor: Entity Attributes
社区
社区首页
社区中心
帮助中心
FANDOM
游戏
电影
电视
wiki
探索wiki
社区中心
创建wiki
尚未注册?
注册
登录
登录
注册
武装突袭 Wiki
4,828
个页面
探索
首页
讨论板
所有页面
社区页
交互式地图
最新博文
页面
最新页面
Contact Reports
Hotshot's Sandbox
DIK KeyCodes
Curator
武装突袭 Wiki
Product.cpp/bin File Format
Oxygen Light
最新博客
分类
Uploaded with UploadWizard
Face A2 Face101.jpg
Face A2 Face102.jpg
Face A2 Face103.jpg
Face A2 Face104.jpg
Face A2 Face105.jpg
Face A2 Face106.jpg
Face A2 Face107.jpg
含有损坏文件链接的页面
Eden Editor: Introduction
Eden Editor: Switching from 2D Editor
Eden Editor: Menu Bar
Eden Editor: Asset Browser
Eden Editor: Toolbar
Eden Editor: Status Bar
Eden Editor: Entity Attributes
社区
社区首页
社区中心
帮助中心
不转换
简体
繁體
大陆简体
香港繁體
澳門繁體
大马简体
新加坡简体
臺灣正體
编辑“
ArmA Build Environment Setup
”
返回页面
编辑
可视化编辑器
查看历史
讨论 (0)
正在编辑
ArmA Build Environment Setup
警告:
您没有登录。如果您做出任意编辑,您的IP地址将会公开可见。如果您
登录
或
创建
一个账户,您的编辑将归属于您的用户名,且将享受其他好处。
反垃圾检查。
不要
加入这个!
==Updated Information== ::'''''Notes from [[User:Mikero|Mikero (nee Ook?)]] 03:20, 29 November 2010 (CET).''''' With the introduction of Operation Arrowhead/Baf/PMC and Steam, considerably more needs to be done, extracting pbo's and creating a p:drive, than simply looking in ~Addons (which sometimes doesn't exist). The orginal document of this page is presented after this note. Briefly, you need to do the following *Obtain a copy of [[BI_Tools_2|BI Editing Tools 2]] and install them. ::You will end up with a My Documents\ArmaWork folder which becomes the P: drive ::'''If''' that doesn't suit you, simply copy everything in ArmaWork to where YOU have your existing p: Most of it is not required and will be over-written, but as a no brainer install, copy armawork content to your p: or copy your p: to armawork (and change setdrive of course) *Download [[http://dev-heaven.net/projects/mikero-pbodll/files Arma2P]] from dev-heaven ::This cmd file will locate all your arma folders and engines (oa, co, a2, baf, betas, steam) and extract every necessary pbo, ''in the right order'' ::If you already have p:content from other projects. Fear not. Arma2P will '''not''' erase or fiddle with YOUR files *Voila Note also that there are various 'gotchas' in creating a ''usable'' p: which the cmd file overcomes. Such as *buldozer's\dta\product.cpp is required for visitor. (NOT the engine's dta) *stringtable.xml needs to be copied to \bin *and etc. Rather than list them here, The workarounds are maintained in arma2p.cmd, as and when they rear their ugly heads =Original Text= ==Introduction/Background== ::work in progress until finished you may find the .pdf version (although older) will help in the meantime. ::The pdf version is not as clear and concise as this online version is intended to be. :::'''[http://tinyurl.com/5kd79v ArmABuildEnvironment.pdf (from RKSL)]''' :::'''[http://tinyurl.com/5txncg ArmABuildEnvironment.pdf (not 24/7)]''' ---- ==The <ArmAWork> Folder== :You can find the links to the latest ArmA Tools Suite through the [[:Category:Tools|tools section]] or through the [http://tinyurl.com/4nbc7s ArmA Editing News] forum. ===Before Tools Installation=== ====Step One==== :*'''Make a folder somewhere on your computer called 'ArmAWork'.''' ::This folder can live anywhere, however you should place it somewhere where there is going to be literally 10’s of Gigabytes of free space. ::For instance I have a physical hard drive partition called the O:\ drive. ::And, I created a subfolder in the root of this drive called ‘ArmAWork’. ::Eg. :::O:\ArmAWork ====Step Two==== :*'''Extract all the pbo’s in the <ArmAInstallationFolder>\AddOns folder.''' ::You can find community produced tools [[:ArmA:_Community_Tools|here]] to facilitate this. ====Step Three==== :*'''Move the <ArmAInstallationFolder>\AddOns\Ca folder to the <ArmAWork> folder you created in step 1.''' ::Eg. :::<ArmAInstallationFolder>\AddOns\Ca moves to O:\ArmAWork\Ca ====Step Four==== :*'''Move each of the remaining folders you extracted in the game installation and place them inside the <ArmAWork>\ca folder you moved in step 3.''' ::Eg. :::<ArmAInstallationFolder>\AddOns\air ''moves to'' O:\ArmAWork\Ca\air ====Step Five==== :*'''Run the BIS Tools Suite installation package.''' ::And, when asked point the installation at the <ArmAWork> folder you created in step 1. ===After Tools Installtion=== ::When the BIS Tools Suite installation has completed you should have a new ‘virtual hard drive’ on your computer called P:\ (By default). Although, you can have it as another drive letter and this is explained in the Installation information. ::This P:\ drive should now be populated with the necessary basic tools setup, which also would have overwritten some of the content you previously copied across from the extraction process of the game data. This is ok. ====Step Six==== :*'''Acquire the BIS Example Models packages.''' ::Go to the [http://tinyurl.com/4nbc7s ArmA Editing News] forum. Find and download the BIS example models. ::The 4 file you are looking for are... ::*ARMA_SampleVehiclesWeapons.zip (110 Megabytes approx.) ::*ARMA_SampleCharactersAnimals.zip (67 Megabytes approx.) ::*ARMA_SampleModelsEnvironmentOther.zip (60 Megabytes approx.) ::*BISampleMap.zip (31 Megabytes approx.) ---- ==Tools Configuration== ===Oxygen2 PE=== ===Visitor3 PE=== ===BinPBO/Build Tools=== ---- ==CPP's & CFG's== ---- ==Your Namespace== ===Background=== :This area of setting up your development environment is quite subjective. :A number of people have differing setups to me and what I am about to go over is just my way of doing it. My naming conventions may not fit with your way of thinking about things. :Firstly, we should note that the BIS default content for ArmA comes in a Mod namespace prefix called ‘ca’. And, it resides in the root folder of your <ArmAWork> folder. :Secondly there is a BIS supported community convention whereby a MOD team or Addon maker registers a short ‘tag’ principally for denoting addons are created by that given person or MOD team. This initiative has other benefits, like how well your addon interacts with other people's work. :This initiative is not mandatory. Although it has its merits and usefulness for some aspects I prefer to have my own subtly different naming convention. :You may develop your own naming convention or subscribe to the community initiatives. :My ‘tag’ registered at OFPEC is 'SYN'. :'''''ALL people who wish to make addons for ArmA should register a tag with this community managed initiative.''''' :This 'tag' then becomes your Namespace / Prefix / Mod Prefix or Virtual Folder Prefix. : ===Setup=== ====Step One==== :*'''Create an empty folder in the root directory of your <ArmAWork> drive the same name as your tag.''' ::Eg. :::P:\syn :::P:\aaw :::P:\rksl :::P:\bob ====Step Two==== :*'''Copy the 'ca' mod config files to your mod.''' ::Open a MSDos prompt window. ::Navigate to the P:\ca folder. ::Run the following dos command. ::<code><nowiki> xcopy *.bin P:\<YourNamespace>\ca\ /S /Y </nowiki></code> ::This command creates a duplicate set of '\ca' folders ''under'' your namespace and copies only the config.bin files to each subfolder. ---- ==Building From Your Namespace== ---- ==Adding Other's Work To Your Namespace== ---- [[Category:ArmA_2:_Editing]]
摘要:
请注意在武装突袭 Wiki上的所有贡献都将依据CC-BY-SA进行发布。
取消
编辑帮助
(在新窗口中打开)
Follow on IG
TikTok
Join Fan Lab