![]() ![]() ![]() Note it reports the size incorrectly but this is a UI issue in the BSA tool.Įdit: Updated. Furthermore, I just created a 6GB BSA with Beth's BSA tool with no issues. I don't see where you're getting a 32-bit variable from. The offset is a ulong, which is an unsigned 64-bit integer. If the BSA goes beyond 4GB (or 2GB if they are using signed integers), you wouldn't be able to place a file after offset 0xFFFFFFFF (or 0x7FFFFFFF), because you cannot specify its offset. ![]() Even the folder/file path lengths, if your typical path is 40 bytes long, that's still over 100M files.īut what about the file record? According to, that offset is a 32 bits variable. Which means the limit is 2^32 files and 2^32 folders, not 2^32 bytes. There is nothing about the file headers that disallow it currently. If you're the person who responded to me an hour ago about the 2GB limit. We had a private discussion here about it but someone posted about it on Reddit so I went ahead and discussed it. Yeah, that's my image, and I'm the main person in that thread.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |