Human readable easy to understand no fuss examples how to use Mikero Tools.

DeP3D scans useful information from a model P3D.

Geometry Properties:

dep3d -P -G model.p3d

Files Used:

dep3d -P -FL model.p3d

LOD Properties:

dep3d -P -LP model.p3d

Named Selections:

dep3d -P -S model.p3d

Fully working batch file to run arma3 sample character models info into _p3d_properties.txt file:

@echo off
set A3SAMPLEDIR="<steamPath>SteamApps\common\Arma 3 Samples\Addons\Test_Character_01"
set MIKEROD3P3D="C:\Program Files (x86)\Mikero\DePboTools\bin\dep3d"
%MIKEROD3P3D% -P -G %A3SAMPLEDIR%\A3_character_example.p3d >_p3d_properties.txt
%MIKEROD3P3D% -P -FL %A3SAMPLEDIR%\A3_character_example.p3d >>_p3d_properties.txt
%MIKEROD3P3D% -P -LP %A3SAMPLEDIR%\A3_character_example.p3d >>_p3d_properties.txt
%MIKEROD3P3D% -P -S %A3SAMPLEDIR%\A3_character_example.p3d >>_p3d_properties.txt
pause
exit

You need to replace <steamPath> with your full steam directory path.

For those who build many addons or frequently update some addon, there is no better way to run pboProject that from dos batch file using command line.

First you need to configure pboProject using the normal graphical user interface. The values are saved (like exclude dirs/files etc) and used when you run it from command line.

Command line:

pboproject -w=p:\,mod=c:\arma3mods\myAddon p:\myTag\myAddon

When you get error, look at the pboProject console window and also the log directory which is P:\temp\ which contains two logs or at least one, depending did you manage to get through binarize phase. Check these logs and read what the error says, if you don't know what the error means, google it as there is very likely possibility that someone has already asked about the error in forums etc.

Most common errors are missing files (wrong paths) or class Land_ stuff.