arma3-macvsog-columbia-items

Arma3 MACV-SOG Columbia - Object and Procedure for object creation

This article will provide information on how to create a new Arma 3 inventory object from scratch. From an idea into an item that has the shape we want, the weight we chose, the texture we desire and that is available as a mod in order to make it accessible for multiplayer missions.
I will follow the procedure described in this repository to create new Item for MACV-SOG such as seismic sensor, etc. The result will be a mod compiling all those items. You can find the mod here: https://steamcommunity.com/sharedfiles/filedetails/?id=3332232289
If the procedure is wrong/not clear don't hesitate to create an issue and I will gladly update it.

Requirements

Blender version 3.6 (versions higher have issues with Arma 3).
- With this plugin installed https://github.com/AlwarrenSidh/ArmAToolbox/releases/tag/v4.0.5
GIMP http://www.gimp.org/
Arma 3 Tools.
Access to https://paa.gruppe-adler.de/, else .paa images will need to be generated manually (explained later in the document).

Procedure

1. Setup
2. P3D object creation through Blender
3. Blender P3D to Arma P3D through Object Builder
4. Create an icon for our inventory object
5. Create the configuration
- 5.1 Create the configuration for the object
- 5.2 (Optional) extra configuration to create a Thing object required for addAction method
6. Import object into Arma 3 using Addon Builder
7. Local testing through Addons
8. Create a public mod using Arma Tool Publisher
- 8.1 One single item inside a public mod
- 8.2 Multiple items inside a public mod
9. Add custom actions on object

1. Setup

open section

Create this folder and file structure anywhere on your computer (this will be our workspace).

In the above example, a sensor (a seismic sensor used by MACV SOG in order to monitor movement of NVA soldiers) is the new object I want to create. This will be our MAIN folder.
data folder will contain the object textures, in .paa format (currently an empty folder).
Icons folder will contain the icon for our object, in .paa format (currently an empty folder).
Objects folder will contain the 3D object in .p3d format (currently an empty folder).
Config.cpp file will contain the configuration for our object and will allow us to configure its weight, name, etc. (currently an empty file).

2. P3D object creation through Blender

2.1 Create 3D Object

Create a 3D item in Blender that has the desired shape.
At the end of the item creation, make sure it is a single 3D object (top right of blender) and that “Arma Object Property” is selected.

Pressing CTRL + T will triangulate the 3D objects (make its faces only triangles) and remove any ngons (Arma does not want ngons).

2.2 Add custom texture

2.2.1 Work locally on Blender to see how texture is looking

Create a UV map by selecting the object and clicking on “U”. Making an easy one to work with is sometimes tricky but adding some seams in Blender can help.

Then export the UV map as a .png (object_uv_map.png), then using any editing software, update the .png to have the texture you want and save it as a new .png (object_texture.png). Keep in mind that the resolution MUST be 512x512.

Go back to Blender, make sure your object has a default material (not empty) and open the “Shader Editor” (Shift + F3).
Right click and add an “Image Texture” with as path, the path of the object_texture.png.

Then, if you go back to the 3D Viewport you will be able to see the object with the new texture.

Finally, export the 3D object and .p3d file and save it to a temporary location like “Downloads” or “Desktop”.
N.B. The main purpose of adding texture in Blender is to visualise how it will look onto the object and make sure it is looking good.

2.2.2 Export texture to .paa

Go to https://paa.gruppe-adler.de/ and convert object_texture.png into a .paa (object_texture.paa).
- Manual steps (if website is down):
  - Use the TexView 2 (Arma 3 Tools) to convert the .png into a .paa (Use ‘RGBA’ and in the other section use ‘DXT5’).
- Save the generated object_texture.paa in data folder. This is important because when exporting as a mod, the path to the texture needs to follow this syntax:
  - “yourAddonName\data\yourTexture.paa”

2.3 Improve texture using maps

This is optional but will result in a more realistic looking object with roughness and texture instead of looking flat, glassy with our own texture.

2.3.1 Normal map (for depth)

N.B. following the tutorial https://kcclemo.neocities.org/creating-height-and-normal-maps/ will work but I will be going over it in this document in case the website goes down.
Open the texture object_texture.png (obtained in section 4.2.2) in GIMP.
Select Image>Mode>Grayscale.
- Pixels more black: low points.
- Pixel more white: high points.
If needed, you can invert the colors using Colors>Invert.
In the Levels dialog:

Arrange the 3 triangles to correspond to the above picture.
Now we can save the new picture (keep in mind that we need to have a resolution of 512x512) and this will give us our detector_bump.png.
We need to convert this new png into a normal map. To do this, you can use the following website (if down, will need to find a tutorial on how to create normal map…) https://cpetry.github.io/NormalMap-Online/.
- Drag and drop your detector_bump.png in the website, and uncheck “Displacement”, “AO” and “Specular”.

Then below the middle picture, rename it to detector_nohq and save.
Convert the .png into a .paa (see "2.2.2 Export texture to .paa").
Save the generated detector_nohq.paa in the data folder.
We now have our normal map detector_nohq.paa and it can be moved to the data folder.

2.3.2 Ambient occlusion map (for shadows)

Blender can be used to generate the occlusion map.

Go in the render view, with the following setup:
- Render Engine: Cycle
- Bake>Bake Type: Ambient Occlusion
Select the object and click on the “Bake” button and this will give the following result.

In the top left, click on image*>save as, and then save it as detector_as.png.
Convert the .png into a .paa (see "2.2.2 Export texture to .paa").
Save the generated detector_as.paa in the data folder.
We now have our ambient occlusion map detector_as.paa and it can be moved to the data folder.

2.3.3 Specular map (for reflectiveness of the material)

N.B. The whitest will mean the more reflective a texture is. The blackest, the less reflective a texture is.
To generate the Specular map, I used https://cpetry.github.io/NormalMap-Online/ and selected “Specular” (middle picture and top right) and reduced the strength in order to make the object blacker (less reflective).

Then below the middle picture, rename it to detector_smdi and save.
Convert the .png into a .paa (see "2.2.2 Export texture to .paa").
Save the generated detector_smdi.paa in the data folder.
We now have our specular map detector_smdi.paa and it can be moved to the data folder.

2.3.4 Bundle all maps in .rvmat file

You can use the below “default” template and change the name of .paa files to suit your model.

class StageTI
{
    texture="#(argb,8,8,3)color(0,0,0,0)";
};
ambient[]={1,1,1,1};
diffuse[]={1,1,1,1};
forcedDiffuse[]={0,0,0,0};
emmisive[] = {0,0,0,0};
specular[] = {0.15,0.15,0.15,1};
specularPower = 80;
PixelShaderID = "Super";
VertexShaderID = "Super";
class Stage1
{
    texture="detector\data\detector_nohq.paa";
    uvSource="tex";
    class uvTransform
    {
        aside[]={1,0,0};
        up[]={0,1,0};
        dir[]={0,0,0};
        pos[]={0,0,0};
    };
};
class Stage2
{
    texture="#(argb,8,8,3)color(0.5,0.5,0.5,0.5,DT)";
    uvSource="tex";
    class uvTransform
    {
        aside[]={1,0,0};
        up[]={0,1,0};
        dir[]={0,0,0};
        pos[]={0,0,0};
    };
};
class Stage3
{
    texture="#(argb,8,8,3)color(0,0,0,0,MC)";
    uvSource="tex";
    class uvTransform
    {
        aside[]={1,0,0};
        up[]={0,1,0};
        dir[]={0,0,0};
        pos[]={0,0,0};
    };
};
class Stage4
{
    texture="detector\data\detetector_as.paa";
    uvSource="tex";
    class uvTransform
    {
        aside[]={1,0,0};
        up[]={0,1,0};
        dir[]={0,0,0};
        pos[]={0,0,0};
    };
};
class Stage5
{
    texture="detector\data\detector_smdi.paa";
    uvSource="tex";
    class uvTransform
    {
        aside[]={1,0,0};
        up[]={0,1,0};
        dir[]={0,0,0};
        pos[]={0,0,0};
    };
};
class Stage6
{
    texture="#(ai,32,128,1)fresnel(2.45,0.75)";
    uvSource="none";
};
class Stage7
{
    texture="a3\data_f\env_co.tga";
    uvSource="tex";
    class uvTransform
    {
        aside[]={1,0,0};
        up[]={0,1,0};
        dir[]={0,0,0};
        pos[]={0,0,0};
    };
};

What is important here is to include the 3 .paa file we generated:
- detector_nohq.paa
- detector_as.paa
- detector_smdi.paa
N.B. with a path from the MAIN folder (ex: detector\data\detector_smdi.paa).

We now have our detector.rvmat file.

2.4 End result for data folder

Add the end, you should have 5 files into the data folder.

3. Blender P3D to Arma P3D through Object Builder

3.1 Detect object components

Open the .p3d file previously exported with Arma 3 Object Builder (see Arma 3 Tools).
Select the entire 3D object and go into “structure/topology/find components”. This will create the required components for Arma 3 objects.

3.2 Add texture to Arma 3 object

Go back to the Object Builder, select the object (all nodes) and click “E” to open the “Face Properties” menu.
- In texture, select your .paa texture then click “Apply” and “Ok”.

Then in the “material” path (below the “texture” path) put the path to the detector.rvmat (it must be under path “yourObject/data/yourObject.rvmat”) then click “Apply” and “Ok”.

Save and export as .p3d and save it in the Objects folder.

3.3 (Optional) Adding more LODs

OPTIONAL: ONLY FOLLOW THIS STEP IF YOU WANT TO ADD ACTION ON THE ITEM.

If you want to be able to add scripts onto the object through 'addAction' then we need to add 3 extra types of LODs (see https://community.bistudio.com/wiki/LOD#Roadway):
- Geometry:
  - Defines where the model will collide with other objects. Should be very simple, and has to fulfill the following criteria in order to work:
    - Object must be named ComponentXX (where XX is a consecutive number between 01 and 2048 (a limit in earlier games might have been 99).
    - Must have 'Mass' (Alt-M). A minimum of 10 is required for character collision.
    - Must be closed and convex. Always validate your Geometry LOD. (Validating Geometries)
    - Some object types require that every component must have some mass assigned in order to work properly. Does not apply to vehicles It must be smaller than the size limit.
- View Geometry:
  - The visible geometry of the model.
  - As an example: If you have an object with this LOD properly configured, you will not be able to spot other units through the model. AI will not be able to spot other units through the model. If this LOD is not present the Geometry LOD will be used instead.
- Fire Geometry:
  - Defines where the model will collide with bullets & rockets. If this LOD is not present the ViewGeometry LOD will be used instead. If the ViewGeo LOD is not present either then Geometry LOD will be used instead. Should be simplified as much as possible, but can be a bit more complex then Geometry or Geometry Phys:
    - Object must be named ComponentXX (where XX is a consecutive number between 01 and 2000). (see Geometry LOD)
    - Must be closed and convex (see: Validating Geometries).
Open the .p3d file in Arma Object Builder.

Select all nodes (Ctrl + A), click on '1.000' in the top right, duplicate. Then on the '2.000' that was created, property and select 'Geometry'.
Under the 'Component01', right click and create a new component named 'Component02'.

In the top left, select 'Create' and create a 'Box' that will contain the object.
Delete the initial object.

Select the box (Ctrl + A) and add mass (bottom lef).

Select the 'Geometry' LOD, duplicate it, remove the weight. Then go into properties of the new LOD and select 'View Geometry'. Duplicate the 'View Geometry LOD' and create a 'Fire Geometry' LOD.

Then for each new LOD ('Geometry', 'View Geometry' and 'Fire Geometry'):
- Double-click on them (in order to edit them).
- Select the entire cube (Ctrl + A) go into “structure/topology/find components”. EXTREMELY IMPORTANT AND EASY STEP TO MISS!
Finally, save as .p3d and override previous .p3d.

4. Create an icon for our inventory object

open section

Create a .png representing your objects (a print screen of blender can work).
Resize it to be 512x512 pixels.
Convert the .png into a .paa (see "2.2.2 Export texture to .paa").
Move the generated .paa file into the Icons folder.

5. Create the configuration

5.1 Create the configuration for the object

Open and edit the config.cpp file and paste the below content into it:

class CfgPatches
{
    class sensor //name of folder containing objects, icons and config.
    {
        units[]={};
        weapons[]={};
        requiredVersion=0.1;
        requiredAddons[]={"A3_Characters_F"};
    }
}


class CfgMagazines
{
    class CA_Magazine;
    class colsog_inv_sensor: CA_Magazine
    {
        author = "Gerard";
        mass = 11;
        scope = 2;
        value = 1;
        displayName = "Seismic sensor";
        picture = "\sensor\icons\sensorIcon.paa";
        model = "\sensor\objects\sensorObj.p3d";
        type = 256;
        count = 1;
        initSpeed = 18;
        nameSound = "handgrenade";
        maxLeadSpeed = 6.94444;
        descriptionShort = "Seismic sensor";
        displayNameShort = "Seismic sensor";
    };
};

‘Mass’ is the mass of your new object and actual in-game weight will be divided by 10 (ex: 11 mass in the configuration means 1,1 pound of mass in game).
‘Picture’ needs to point to the icon .paa previously generated (with path from MAIN folder).
‘Model’ needs to point to the icon .p3d previously generated (with path from MAIN folder).

5.2 (Optional) extra configuration to create a Thing object required for addAction method

OPTIONAL: ONLY FOLLOW THIS STEP IF YOU WANT TO ADD ACTION ON THE ITEM.

Open and edit the config.cpp file to add the below extra content. This will create a 'Thing' object with same 3D model as the magazine object:

class CfgVehicles 
{
    class Thing;
    class colsog_thing_handsid_sensor : Thing  
    {
        access = 0;
        scope = 2;
        model = "\handsidsensor\objects\handsidsensor.p3d";
        displayName = "Handsid sensor";
        faction = "Default";
        vehicleClass = "Objects";
        simulation = "thing";
        scopecurator = 2;
        author = "Gerard";
        destrType = "DestructNo";
    };
};

This object will allow us to add actions on it such as ACE actions or regular Arma actions.
(example: If 'colsog_inv_sensor' magazine item present in player inventory, action to drop and activate sensor. Then the script deletes magazine item from player's inventory and spawn a new 'colsog_static_sensor' static object and the action can be added on this static object. Required because action not possible to add on magazine items).

6. Import object into Arma 3 using Addon Builder

open section

Open the Addon Builder (Arma 3 Tools).
- Addons source directory: path to MAIN folder.
- Destination directory: Path to Arma 3 !Workshop.
Toggle:
- Clear temp folder.
- Binarize.
  - Enable extended logging.
Then you can click on PACK (bottom right).

This will generate and save a .pbo file into the specified folder in !Workshop.

7. Local testing through Addons

7.1 Testing locally

Copy the .pbo generated during the previous step and paste it directly into the Addons folder of Arma 3.

Restart Arma 3 (if it was previously launched), go into the Eden editor and now the object (sensor) will be visible in the arsenal under the magazine section (since in the configuration we are extending the magazine class).

You can also run the following line in order to make it spawn into the inventory of the player:
```
player addItem “colsog_inv_sensor”;
```

7.2 Possible issues and how to fix them

7.2.1 Texture are reversed

If you see that texture are reversed in-game there is a simple way to fix that issue.

Open the .p3d object in the object folder:
Select all the nodes.
In the top left, select 'Faces\Reverse'.

Save as .p3d and override the object in the object folder.
Continue from Step 6.
- fixed result:

7.3 Testing locally addAction on static item

7.3.1 AddAction script on static item

You can use the below script and executed in a mission. This will make the static item spawn and add a custom action on it. If this work, you will be able to add custom actions/scripts on it.
```
private _pos = getPosATL player; 
private _sensor = "colsog_thing_handsid_sensor" createVehicle _pos;
 
[_sensor, ["Greetings!", { hint "Hello!"; }]] remoteExec ["addAction"];
```

8. Create a public mod using Arma Tool Publisher

8.1 One single item inside a public mod

We need to create a mod with our new object in order to make it available during multiplayer missions.
Open Arma 3 Tool Publisher.
- Mod content: path to the generated folder containing the .pbo file previously generated (see "6. Import object into Arma 3 using Addon Builder").
- You can fill in other information such as tag, description, etc.
- Agree with the Steamworks licence and click Publish (or Update if you are updating a previously published mod).

Once successfully uploaded to the Steam workshop, your mod will be available for other to subscribe and then your new object will be able to be used in multiplayer missions.
example: https://steamcommunity.com/sharedfiles/filedetails/?id=3332232289

8.2 Multiple items inside a public mod

The steps are the same as in section 8.1 but there are some differences: the different sub-folders will be merged and the configuration files updated.
data folder will contain all files for the various items (in my example we want to have 3 items in a single mod).

Make sure that in all .rvmat files, the path to .paa are correct.
```
texture="rtcolumbiaitems\data\prc77battery_nohq.paa";
```
Icons folder will contain the different icons and thus need different names.

Objects folder will contain the 3D object in .p3d format (currently an empty folder).
- Make sure path to .paa texture and .rvmat is correct in the "Arma Object Builder".
  - Else:
    - open the Arma Object Builder
    - Update the path to .paa and .rvmat
    - Save as .p3d and override old .p3d objects.

Config.cpp file Needs to be updated to contain the information related to the 3 items.

class CfgPatches
{
    class rtcolumbiaitems 
    {
        units[]={};
        weapons[]={};
        requiredVersion=0.1;
        requiredAddons[]={"A3_Characters_F"};
    }
}


class CfgMagazines
{
    class CA_Magazine;
    class colsog_inv_handsid_sensor: CA_Magazine
    {
        author = "Gerard";
        mass = 100;
        scope = 2;
        value = 1;
        displayName = "Handsid sensor";
        picture = "\rtcolumbiaitems\icons\iconHandsidSensor.paa";
        model = "\rtcolumbiaitems\objects\handsidsensor.p3d";
        type = 256;
        count = 1;
        initSpeed = 18;
        nameSound = "handgrenade";
        maxLeadSpeed = 6.94444;
        descriptionShort = "Handsid sensor";
        displayNameShort = "Handsid sensor";
    };
    class colsog_inv_prc77_battery: CA_Magazine
    {
        author = "Gerard";
        mass = 44;
        scope = 2;
        value = 1;
        displayName = "PRC-77 Battery";
        picture = "\rtcolumbiaitems\icons\iconPrc77Battery.paa";
        model = "\rtcolumbiaitems\objects\prc77battery.p3d";
        type = 256;
        count = 1;
        initSpeed = 18;
        nameSound = "handgrenade";
        maxLeadSpeed = 6.94444;
        descriptionShort = "PRC-77 Battery";
        displayNameShort = "PRC-77 Battery";
    };
    class colsog_inv_sensor: CA_Magazine
    {
        author = "Gerard";
        mass = 15;
        scope = 2;
        value = 1;
        displayName = "Seismic sensor";
        picture = "\rtcolumbiaitems\icons\iconSeismicSensor.paa";
        model = "\rtcolumbiaitems\objects\seismicsensor.p3d";
        type = 256;
        count = 1;
        initSpeed = 18;
        nameSound = "handgrenade";
        maxLeadSpeed = 6.94444;
        descriptionShort = "Seismic sensor";
        displayNameShort = "Seismic sensor";
    };
};

Then, follow same steps as section 8.1 in order to publish the new mod with the multiple items inside of it.
final result see 3 items in a single mod

9. Add custom actions on object

open section

Adding it to the item directly is not ideal and really hard for several reasons I will not list here.
Solution is to have a player action that is conditioned by the presence or not of the new object in the player’s inventory. Upon use, the object can be deleted from the player’s inventory, etc.
Will add scripts adding behaviour to a new object we have created in https://github.com/gerard-sog/arma3-macvsog-columbia-scripts . (This part is WIP and currently nothing available, will try to have something for the 30th September 2024).

Examples

PRC-77 battery

Seismic sensor

Seismic: These sensors contained seismic detectors. That is, they detected movement in the earth -- similar to earthquake detectors -- such as vehicle(s) moving past or footsteps. Seismic devices required a small spike to be driven into the ground; this spike contained the sensing element. If the ground moved, the sensing element moved and activated a radio transmitter that transmitted a beep, alerting the monitor to the fact that something was moving near the sensor location.

The Handsid (Placed on the Ground by Foot Soldiers)

The initial sensor program was called PRACTICE NINE until 14 June 1967, ILLINOIS CITY until 15 July 1967, and DYE MARKER until 8 September 1967, when MUSCLE SHOALS was adopted to indicate the air-supported subsystem in eastern and central Laos. In June 1968, the program was renamed IGLOO WHITE and consisted of three components: (1) munitions and sensing devices which were placed across and along suspected routes of infiltration to detect and impede enemy foot or vehicular movement; (2) orbiting aircraft which received signals from these sensors, amplified them, and retransmitted them; and (3) an Infiltration Surveillance Center (ISC) which received the transmitted signals from the aircraft and analyzed them to produce reliable tactical information for planning and interdiction operations.

Special thanks

Lukinator (SOG Discord): for helping me build this procedure.
HorribleGoat (Arma Discord): for input about adding actions on objects.
Kay (RT Columbia Discord): for the previous discussions about creating mods and scripting.

Name		Name	Last commit message	Last commit date
Latest commit History 31 Commits
combined-items/rtcolumbiaitems		combined-items/rtcolumbiaitems
images		images
items		items
README.md		README.md

gerard-sog/arma3-macvsog-columbia-items

Folders and files

Latest commit

History

Repository files navigation

arma3-macvsog-columbia-items

Requirements

Procedure

1. Setup

2. P3D object creation through Blender

2.1 Create 3D Object

2.2 Add custom texture

2.2.1 Work locally on Blender to see how texture is looking

2.2.2 Export texture to .paa

2.3 Improve texture using maps

2.3.1 Normal map (for depth)

2.3.2 Ambient occlusion map (for shadows)

2.3.3 Specular map (for reflectiveness of the material)

2.3.4 Bundle all maps in .rvmat file

2.4 End result for data folder

3. Blender P3D to Arma P3D through Object Builder

3.1 Detect object components

3.2 Add texture to Arma 3 object

3.3 (Optional) Adding more LODs

4. Create an icon for our inventory object

5. Create the configuration

5.1 Create the configuration for the object

5.2 (Optional) extra configuration to create a Thing object required for addAction method

6. Import object into Arma 3 using Addon Builder

7. Local testing through Addons

7.1 Testing locally

7.2 Possible issues and how to fix them

7.2.1 Texture are reversed

7.3 Testing locally addAction on static item

7.3.1 AddAction script on static item

8. Create a public mod using Arma Tool Publisher

8.1 One single item inside a public mod

8.2 Multiple items inside a public mod

9. Add custom actions on object

Examples

Special thanks

About

Topics

Resources

Stars

Watchers

Forks

Releases

Packages 0

Languages

Packages