arma3:tools:mikero-tools-user-guide
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
arma3:tools:mikero-tools-user-guide [2017-03-06 11:10] snakeman added extractpbo header. |
arma3:tools:mikero-tools-user-guide [2020-01-01 04:26] (current) snakeman [extractPbo] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Mikero Tools User Guide ====== | ====== 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]]. |
| Line 13: | Line 13: | ||
| <code dos> | <code dos> | ||
| @echo off | @echo off | ||
| - | extractPboDos -P -F config.bin,*.p3d C:\WhateverPath\addons p:\ | + | extractPboDos -P -F=config.bin,*.p3d C:\WhateverPath\addons p:\ |
| pause | pause | ||
| exit | exit | ||
| </code> | </code> | ||
| + | |||
| + | Note that the '=' on -F parameter was introduced in 2019 for pay tools and we don't know if its on the latest free tools as well (don't have free tools to test). If you get error with "-F=filename" parameter then simply remove the '=' heh. | ||
| + | |||
| **Unpack EVERYTHING:** | **Unpack EVERYTHING:** | ||
| <code dos> | <code dos> | ||
| Line 28: | Line 31: | ||
| ====== pboProject ====== | ====== pboProject ====== | ||
| - | Updated for pboProject v1.94 | + | Updated for pboProject v2.45 |
| + | |||
| + | 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. | 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. | ||
| Line 45: | Line 53: | ||
| </code> | </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. | 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. | ||
| + | |||
| + | Note for v2.45: some versions earlier the pause option in console was added, you need to add -P parameter for "no pause" and then pboproject works again in batch mode without pauses. With -P if you get error it will be written to pboproject console... which will be immediately closed leaving you no time to see the error (you have to check logs in p:\temp\ directory). You should use "if errorlevel 1 goto PboError" in your bat file to stop at errors on long batch files. | ||
| Most common errors are missing files (wrong paths) or class Land_ stuff. | 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) :) | The above .bat also lists starting and ending time, which is nice stats for those larger projects (especially terrains) :) | ||
| + | |||
| + | Killing binarize_x64.exe causes pboproject to abort and cleanly return \source\ dir to its original location. I assume same happens if binarize crashes on itself. | ||
arma3/tools/mikero-tools-user-guide.1488798633.txt.gz · Last modified: 2017-03-06 11:10 by snakeman
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
