Search
You can find the results of your search below.
Results
- arma3:terrain:separate-data-layers: 12 Hits
- ata
echo %MODTAG%\%TERRAIN%_data >%TERRAIN%_data\$PBOPREFIX$
echo class CfgPatches{class %TERRAIN%_data{units... AG%\%TERRAIN%_data_layers >%TERRAIN%_data_layers\$PBOPREFIX$
echo class CfgPatches{class %TERRAIN%_data_layer... ERRAIN%_data_layers_00 >%TERRAIN%_data_layers_00\$PBOPREFIX$
echo %MODTAG%\%TERRAIN%_data_layers_01 >%TERRAIN%_data_layers_01\$PBOPREFIX$
echo %MODTAG%\%TERRAIN%_data_layers_02 >%TERRAIN
- arma3:terrain:ultimate-terrain-tutorial: 6 Hits
- l_terrain\source\
</code>
Now create file name "$PBOPREFIX$" in this directory, so it will become:
<code>
\tut\tut_tutorial_terrain\$PBOPREFIX$
</code>
Now open $PBOPREFIX$ in text editor and write the following line there:
<code>
tut\tut_tutorial_ter... e>
This is your namespace \ addon name directory, pboprefix file tells arma3_x64.exe where this addon's files
- arma2:terrain:separate-data-layers: 6 Hits
- ugen_Data
In the new directory create of course $PBOPREFIX$ and config.cpp with just the cfgPatches. In our case these are:
$PBOPREFIX$
<code>
pmc\pmc_rugen_data
</code>
config.cpp
<co... ory called <TerrainName>_Data_Layers\ and create $PBOPREFIX$ and config.cpp as mentioned earlier with _Data d... c_rugen_data_layers_00 >pmc_rugen_data_layers_00\$PBOPREFIX$
echo pmc\pmc_rugen_data_layers_01 >pmc_rugen_dat
- arma2:tools:makepbo: 4 Hits
- a pbo wysiwig
-P PrefixName this will over-ride $PBOPREFIX$ and use a direct over-ride
</code>
Notes:
rapif... only. They are not, 'binarised'
Note that if a $PBOPREFIX$ file is detected in the pbo folder. It takes pre... mply by stating ArmA, or Elite as an option. The $PBOPREFIX$ is intended to over-ride the prefix names that t... official addon names IF, -a is selected (and no $PBOPREFIX$ detected).
Note that there is no provision for
- arma2:tools:extractpbo: 2 Hits
- ), the prefix is accounted for in two ways
1) a $PBOPREFIX$ file is added to the output.\\
A $PBOPREFIX$ file if detected in the pbo itself, is NEVER extracted.\\
2) t
- arma2:port_arma: 2 Hits
- we consider our root now (pmc_ch34).
2) create $PBOPREFIX$ file in there. write there: pmc\pmc_ch34
3) cre... we consider our root now (pmc_delta).
2) create $PBOPREFIX$ file in there. write there: pmc\pmc_delta
3) cr
- arma:terrain:wrptutorial: 1 Hits
- you want to use that. I havent found use for the $PBOPREFIX$ yet but have no clue if thats good or bad.
==
- arma:ofpport: 1 Hits
- ntation
j) path definition has changed
k) topic PBOPREFIX
l) editing trick to work with folders rather tha
- arma2:terrain:bis_terrain_analysis: 1 Hits
- rrain wrp analysis
Original PBO's:
^ PBO Name ^ $PBOPREFIX$ ^ Contents ^
| south_asia_h.pbo | hsim\south_asi
- arma:misc: 1 Hits
- nto ArmA ROOT dir.
- Make sure there is proper $PBOPREFIX$ file inside this dir.
Run ArmA and you should b
- arma:tools:cpbo: 1 Hits
- is saved to and read from a special file called $PBOPREFIX$ in the directory.
You can also do command line
- arma:tools:armaunpbo: 1 Hits
- PBO files.
* Prefix header is saved into file "$PBOPREFIX$"
* Compressed files are not supported as they
- arma:terrain:misc: 1 Hits
- u should) use namespaces, you have forgot to add $PBOPREFIX$ file into the pbo and setup it properly for the