Pak file size limit?

Aerisetta

Active member
Hello

I am currently paking a game with borpak

After paking it is about 5.7 gigs

Unfortunately, after paking, when i run it, it just crashes

BorLog says

Total Ram: 67938779136 Bytes ( 64791 MB )
Free Ram: 48168226816 Bytes ( 45936 MB )
Used Ram: 8175616 Bytes ( 7 MB )

debug:nativeWidth, nativeHeight, bpp, Hz 2560, 1440, 24, 60
OpenBoR v4.0 Build 3 (commit hash: e2381e9), Compile Date: May 31 2026

Game Selected: ./Paks/WoL.pak

FileCaching System Init....... invalid pak header pointer
Disabled
Initializing video............
'data/video.txt' not found.
Initialized video............ 320x240 (Mode: 0)

Timer init................... Done!
Initialize Sound.............
Loading sprites.............. Done!
Loading level order..........
********** An Error Occurred **********
* Shutting Down *

Error loading level list from data/levels.txtTotal Ram: 67938779136 Bytes ( 64791 MB )
Free Ram: 48156667904 Bytes ( 45925 MB )
Used Ram: 41787392 Bytes ( 39 MB )

Release level data...........
Done!

Release graphics data........ Done!
Release game data............


Release game data............ Done!
Release timer................ Done!
Release input hardware....... Done!
Release sound system......... Done!
Release FileCaching System... Done!

**************** Done *****************

Error loading level list from data/levels.txt
 
Hello

I am currently paking a game with borpak

After paking it is about 5.7 gigs

Unfortunately, after paking, when i run it, it just crashes

BorLog says

The legacy packer is indeed limited to ~2GB because it's using signed 32 bit ints for the tables.

But wow the timing... I literally just last night sent an alpha build for other devs to test.

It will probably be released in a couple of weeks

I rewrote the tables to use unsigned values, so it can pack about 4GB in 32 bit mode, and it also has a new 64 bit mode that can pack ~9 exabytes (about 9 billion gigabytes). The only catch is you'll need the latest engine version to run the 64 bit mode packs..

DC
 
@Mr.Q!, @Aerisetta,

The specific error may or may not be due to size, but regardless, exceeding 2GB with the current packer is never going to be stable. There are some hacky solutions I've seen out there in forks that basically just shove larger buffer numbers in and call it a day, but you won't get far going that route without bugs. Mine is a full rewrite of the packing tool and the engine's on board extractor.

DC
 
Back
Top Bottom