ArmA 2 CreatePewObjects
ArmA 2 Forum, ArmA 2 Home, ArmA 2 Config, ArmA 2 File Formats, ArmA 2 Missions, ArmA 2 3D Modeling, ArmA 2 Scripting, ArmA 2 Terrain, ArmA 2 Texturing, ArmA 2 Tools
CreatePewObjects either generates, or uses, an ObjectTemplate configuration file. See also CreatePewObjects User Guide.
The purpose of which is to have a stock library of 'standard' items that you always add to your island. ca/buildings eg.
The name of this config file is arbitrary (you declare it's name).
The result is that any given .pew file will either supply information to this configuration for future use, or, use the configuration data to alter a PEW.
Therefore, there are two modes of operation:
CreatePewObjects -E PewFile[.pew] ConfigFile // EXPORT CreatePewObjects -I PewFile[.pew] ConfigFile // IMPORT and delete all existing objects CreatePewObjects -A PewFile[.pew] ConfigFile // ADD to
Official syntax:
CreatePewObjects -option PewFile[.pew] ConfigFile [OutputPew[.pew]]
There is no default option. You must specify whether you want to E)xport , I)mport or A)dd option.
The output.pew is optional and (obviously) only relevant when importing and creating a new pew. If not specified, the original pew will be altered.
ObjectTemplate configuration file
These are humanly readable class text statements.
You can quite easily add additional object classes to this file by hand.
You could export two or more pew files and concatenate the results, by hand, into a single config file, removing those objects you don't want in your library.
(It is suggested, that if you do indeed manually alter this file. you pass Rapify.exe -L over it to Lintcheck that it is 'OK').
The overall intent is to build up a stock library of common objects, often numbering in 100's, that you ordinarily have to manually add, one-by-one, to any island you create.
The other intent is to REMOVE ALL OBJECTS, often numbering in the thousands. When you need to start again.
Note the two modes of import operation -I to delete all and add some. -A to simply add new objects to that existing.
Note that if any given object in your config template already exists in the pew, it, is ignored. You can safely add 'extra' objects without having to remove from your template your favorites.
Final Note
Deleting ALL objects is a work in progress. It will work, but *may* fail, if any road nets are involved.
Default template variables:
ulModelIndex = 2; // information output only, not used for import if not specified ulObjectType = NATURAL ulMarkerType = ELLIPSE; dblxyRandomScale[]={50.0000,50.0000,0}; dblxyRandomRotate[]={20.0000,20.0000,0}; dblxyRandomOrientation[]={180.0000,180.0000,0}; dblxyGeometryBounds[]={10.0000,10.0000}; dblxyResolutionBounds[]={10.0000,10.0000}; GeometryAutoCenterPos[]={0.0000,0.0000,0.0000}; ResolutionAutoCenterPos[]={0.0000,0.0000,0.0000}; sbUnknownFlag=1; ulOutlineColour,ulObjectColour == -1 (default)
Requires DePbo.dll - Check Mikero tools homepage in Dev-Heaven.