Differences

This shows you the differences between two versions of the page.

--- arma3:tools:mikero-tools-user-guide [2017-02-06 01:57]
snakeman added updated cmd line.
+++ arma3:tools:mikero-tools-user-guide [2018-01-12 10:06]
snakeman updated exclude from pbo list.
@@ Line 1: / Line 1: @@
 ====== Mikero Tools User Guide ======
-Human readable easy to understand no fuss examples how to use Mikero Tools.
+Human readable easy to understand no fuss examples how to use [[arma3:tools:mikero-tools|Mikero Tools]].
+====== extractPbo ======
+How to unpack addons to your P:\ drive.
+ExtractPboDos is the command line tool which is to be used with batch (.bat) files.
+**Unpack config.cpp and all models:**
+<code dos>
+@echo off
+extractPboDos -P -F config.bin,*.p3d C:\WhateverPath\addons p:\
+pause
+exit
+</code>
+**Unpack EVERYTHING:**
+<code dos>
+@echo off
+extractPboDos -P C:\WhateverPath\addons p:\
+pause
+exit
+</code>
+====== pboProject ======
+Updated for pboProject v1.94
+Exclude from pbo file name list:
+<code>
+*.xcf,*.psd,*.psb,thumbs.db,*.txt,*.h,*.dep,*.cpp,*.bat,*.bak,*.tga,*.png,*.log,*.pew,*.hpp,*.lbt,*.tpp,source
+</code>
+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:
+<code dos>
+@echo off
+echo Start time: %time%
+pboproject -w=p:\ +mod=C:\ArmA3Mods\myTerrain p:\tag\tag_myTerrain
+pboproject -w=p:\ +mod=C:\ArmA3Mods\myTerrain p:\tag\tag_myTerrain_cfg
+echo End time: %time%
+pause
+exit
+</code>
+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.
+The above .bat also lists starting and ending time, which is nice stats for those larger projects (especially terrains) :)
@@ Line 41: / Line 93: @@
 </code>
 You need to replace <steamPath> with your full steam directory path.
-====== pboProject ======
-Updated for pboProject v1.94
-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:
-<code dos>
-@echo off
-echo Start time: %time%
-pboproject -w=p:\ +mod=C:\ArmA3Mods\myTerrain p:\tag\tag_myTerrain
-pboproject -w=p:\ +mod=C:\ArmA3Mods\myTerrain p:\tag\tag_myTerrain_cfg
-echo End time: %time%
-pause
-exit
-</code>
-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.
-The above .bat also lists starting and ending time, which is nice stats for those larger projects (especially terrains) :)

PMC Editing Wiki

User Tools

Site Tools

Differences

Page Tools