winseros / pboman3

The GUI tool to work with ArmA PBO files.
GNU Affero General Public License v3.0
109 stars 15 forks source link

PBO Manager halving the file size #26

Closed Raideralexis closed 1 year ago

Raideralexis commented 2 years ago

I'm trying to edit a mission but when it's time to repack it, pbo manager halves the size of the pbo. Using your old pbo manager doesn't seem to cause any problems..

.

Raideralexis commented 2 years ago

I'm trying to edit a mission but when it's time to repack it, pbo manager halves the size of the pbo. Using your old pbo manager doesn't seem to cause any problems..

. Error1

Captura

winseros commented 2 years ago

The previous version did not apply file compression, while the new one - does. Please let me know whether the new file still functional despite the reduced size.

logimy commented 2 years ago

Please let me know whether the new file still functional despite the reduced size.

No, it doesn't. I've tried to repack Antistasi into PBO file with compression and mission has stopped working correctly.

winseros commented 2 years ago

Can you share the original file and the repacked one?

stubbornick commented 2 years ago

I have the same issue with KP Liberation mission. Here are original and repacked versions: https://github.com/stubbornick/pboman3/tree/develop/examples In game you can choose mission slot, but after you click "Continue" on map you will get no menu forever (like it is still loading). Checked on dedicated server. No changes to mission done.

winseros commented 2 years ago

Hi, @stubbornick. Now I see this strange behavior, though can not understand its origin yet.

For some reason, after applying compression to .sqf scripts, they refuse being execVM-ed. Though they still perfectly get call-ed and spawn-ed.

As a workaround, you may disable compression while packaging. For that, you put a file with the pbo.json in the mission root. The file content should be:

{
    "compress": {
        "exclude": [
        ],
        "include": [
        ]
    },
    "headers": [
    ]
}

You may ensure the compression got disabled by looking at the pbo size.

Meanwhile I'll try to figure out why compression makes ArmA so strangely "partially-crazy".

ghost commented 2 years ago

i have some problem with Arma 3 Domination mission (altis map) After compression revive (if player is killed) in mission not working

fixed by edit pbo.json to:

{
    "compress": {
        "exclude": [
        ],
        "include": [
        ]
    },
    "headers": [
        {
            "name": "Mikero",
            "value": "DePbo.dll.8.35"
        },
        {
            "name": "version",
            "value": "22082616"
        }
    ]
}

also because of this, the players had various errors about the lack of files

winseros commented 2 years ago

I think it worth disabling compression of sqf by-default.

Nighthawk42 commented 1 year ago

I think it worth disabling compression of sqf by-default.

I concur. Until I found the JSON excludes, I too kept having my missions halved and they'd break around 80% of the time if SQF compression was enabled. Compression is nice, but in this day and age of mass storage might make it fairly moot unless you have hundreds of PBOs making up a addon or such.

winseros commented 1 year ago

I disabled the default script compression.