all versions "crashing?" with too many paks

the_loaf

New member
i posted this in the wrong section last year, but haven't been able to find an answer
i saw this also mentioned in 2019 in this thread:
http://www.chronocrash.com/forum/index.php?topic=4043.0

basically if i have too many paks (more than 7 or 8) in my older, i cannot find a version of openbor that will work. the program thinks for a moment when launching then closes. has this been addressed anywhere else?

this is the only log written

Total Ram: 34262425600 Bytes
Free Ram: 22746456064 Bytes
Used Ram: 6258688 Bytes

debug:nativeWidth, nativeHeight, bpp, Hz  1920, 1080, 24, 60
 
I don't think anyone was ever able to reproduce this. There are people with dozens of paks that don't have any problem. What OS are you running?

DC
 
i have this but only with some particular pak files, some of my own pak files and world heroes by maggas, i think there is something in these paks that makes this happen.
So i have like 20 paks and when i sorted paks and moevd the ones that were crashing when loading to the bottom of the list (adding X to their name) then pak selector worked fine unless i wanted to load these bad pak files on the bottom of the list.
Whats interesting is that these bad paks work fine when theres like only 5 pak files in folder.Its a strange issue, im sure theres a reason.
 
the_loaf said:
is it possible to use an older version to avoid it?
i've gone down the list to 6212 with no luck

the_loaf

I did some tests and it really happens from builds 6203 to 6330. From 6196 and below It didn't happened.
You don't need to have a real game pak, you can reproduce this error using multiple copies of an empty pak.

The build 6391 has a bigger limit, it will crash with 19 paks. I found where the problem is in the source code, but until I fix it you can use the build 6196.
As soon I have some news, I will post here.
 
thank you!
i was actually mistaken about 6212 - i had tested the version right after that. so far 6212 has not auto quit either
 
the_loaf thanks for identifying when the builds break it helped pin point when the issue occurred and fix it. Here is a test build based on 6391 with the fix for the menu please test it and report back.

https://www.mediafire.com/file/7owy4joj6r39wzf/OpenBOR-6391-MenuFix.zip/file

@DC I have made a pull request with the fix. This was reproducible just put more then 18 paks in paks folder and keep pressing down till you reach the bottom after the 18th mod the list should move down instead it crashes.
 
it seems like it's working!
all 180 paks are displayed, and i can scroll through the list entirely

i launched a couple random paks with no issue

thank you
 
msmalik681 said:
the_loaf thanks for identifying when the builds break it helped pin point when the issue occurred and fix it. Here is a test build based on 6391 with the fix for the menu please test it and report back.

https://www.mediafire.com/file/7owy4joj6r39wzf/OpenBOR-6391-MenuFix.zip/file

@DC I have made a pull request with the fix. This was reproducible just put more then 18 paks in paks folder and keep pressing down till you reach the bottom after the 18th mod the list should move down instead it crashes.

msmalik681
Code:
#define		MAX_MODS_NUM		18
Is this you are talking about? I already made this change yesterday and am playing some mods to see if this change will not crash anything... I hope my tests and info in my previous post helped a little.
I will add this fix in the 6392 test build.

It seems that we have to talk about some things in the engine dev to avoid confusion, but we can talk later.
 
Kratus that is the one there was some other little linux specific stuff I wanted to add too.

Get Damon Caskey to add you to the developers list then you can post in the developer section.
 
Sorry for necroposting but I come across the same problem. I try getting around it by adding another folder for pak files and renaming the folder i want OpenBOR to load accordingly.
 
Back
Top Bottom