BinBPO mission files packing problem

[Spudgunner]

===========EDIT=================
PROBLEM SOLVED: There is a limit to the number of file extensions BinBPO will take. So I had to remove some unused ones and add the ones I needed. Also, the Prefix file ($PBOPREFIX$) generated automatically was wrong. It just said missions and not ca\missions.
The files extensions I needed where *.paa;*.sqf;*.sqs;*.sqm;*.bikb;*.fsm;*.ogg;*.html;*.cfg;*.unit;*.desc;*.hpp;*.bin;*.ext
================================
I having problems running ArmA 2 after minor editing & repacking of the original mission files (addons/missions.pbo). So far, all I've edited was the Bootcamp missions.

Errors:

Boot camp: the missions have disappeared. Nothing to select.
Campaign: error message "No entry: Ca\missions\campaign\descriptions.ext.campaign. Although there is an clickable region with no text to start the campaign.
Armory: Error message "missing Ca\armory\data\scripts\init.sqf.


BinPBO settings:

Binarise.
Path to signature file is left blank.
Use source path is ticked (P:\missions).
Addon prefix is set to automatic.
Added the .hpp, .ext & .bin to the list of files to copy.


Any idea what I'm doing wrong?

[callihn]

As far as I'm aware no there is no such a limit nor is $PBOPREFIX$ generated automatically by BinPBO or at least mine does not have such a feature nor setting and using binarise is probably where your problem is, if you unpbo your new file you'll probably see that it did not pack everything.

[Spudgunner]

As far as I'm aware no there is no such a limit nor is $PBOPREFIX$ generated automatically by BinPBO or at least mine does not have such a feature nor setting and using binarise is probably where your problem is, if you unpbo your new file you'll probably see that it did not pack everything.
Perhaps we're not using the same version of BI's BinBPO. Mine can be set to generate the prefix file which can be modified in the settings.

The default file extension list wasn't comprehensive enough to cover the files I needed to pack. That's why some files were being skipped. In the end, I had to work out the extensions needed & add them to the list. Unfortunately there's a limit to how many extensions the list field can hold (luckily not a hassle in my case). There should be an "all files" setting. Perhaps there is but its not documented. Maybe leaving it blank will work in this way, I'll test that when I'm doing more work. Also, I Binarised the PBO and it worked fine - all files were packed.

[UNN]

There should be an "all files" setting.

Use *.*

[callihn]

Perhaps we're not using the same version of BI's BinBPO. Mine can be set to generate the prefix file which can be modified in the settings.

The default file extension list wasn't comprehensive enough to cover the files I needed to pack. That's why some files were being skipped. In the end, I had to work out the extensions needed & add them to the list. Unfortunately there's a limit to how many extensions the list field can hold (luckily not a hassle in my case). There should be an "all files" setting. Perhaps there is but its not documented. Maybe leaving it blank will work in this way, I'll test that when I'm doing more work. Also, I Binarised the PBO and it worked fine - all files were packed.

Care to share a screenshot and perhaps a link?

I've only been around since 01/10 and downloaded it from the link in the BIKI.

Has there been an update?

Where is this information kept?

Checking About and there is not even a version number listed nor is there one in the Readme which says:

For more information about the tool visit http://community.bistudio.com/wiki/BinPBO

That link mentioned nothing about changelogs or versions.

The Readme also says:

Supported formats
=================================
input: folder
output: PBO file (ARMA addon)

How to use (Window mode)
=================================
Binarize: uses a temp folder and stores there compressed files then packs them.
Create signature: If you have *.bi.biprivatekey file you can sign you addon and then this addon can by used on secured servers in MP games.
Clear temp folder: before binarizing, the subfolder for the current project is emptied.
List of files to copy directly: files with matching file-mask will be copied to the temp folder and then packed. Take effect only when binarize is enabled.
Path to signature file: *.bi.biprivatekey file with signature, addons created with a signature can be added to secure servers.
Path to temporary folder: path for the folder which stores binarized files, default destination is temp in Windows, if no value is present then the last folder is used, if you use the same folder, the next time you binarize the same addon it will take less time.

How to use (Command line mode)
=================================
BinPBO.exe [source_path [destination_path] [-WINDOW]] [-PACK|-BINARIZE [-CLEAR][-TEMP temp_path] ] [-DEBUG] [-PREFIX prefix_path] [-HELP] [-PROJECT project_path] [-SIGN privatekey_file] [-INCLUDE file_name]
source_path: path to folder to make PBO addon.
destination_path: path to folder to save the final PBO. If destination_path is not present then one level up from source_path is used to store the PBO file.
Without any parameters, BinPBO will start in window mode.
BinPBO.exe with source_path parameter executes a program in console mode; you can disable it by using parameter -WINDOW.
Parameters
=================================
-HELP: shows information about the program and parameters.
-PACK: only stores the folder to a PBO.
-BINARIZE: uses a temp folder and stores there compressed files, and then packs them.
-CLEAR: before binarizing, the subfolder for the current project is emptied.
-TEMP: path for the folder which stores binarized files, default destination is temp in Windows, if no value is present then the last folder is used, if you use the same folder, the next time you binarize the same addon it will take less time.
-DEBUG: shows output from the binarizing and packing process.
-PREFIX: relative path to files used in addon, if not present then this value is calculated automatically.
-PROJECT: path to folder where project starts from, if you are packing only the path of a project.
e.g.: project is P:\MyMOD
addon is P:\MyMOD\Tanks\T72
-SIGN: *.biprivatekey file with signature, addons created with a signature can be added to secure servers.
-INCLUDE: create a new list of file-masks to direct copy to PBO from record in file, separator is ";".

Also it uses a Addon source directory, the only option for adding files is for copying files directlyto the destination directory without putting them into the .PBO