BMS 4.34 crash on joining online campaign
-
@Bad:
Yes right, i saw that. The only remaining issue (DB side) is related with the MB339 (i can fix if you want). I’ll also check your campaign file because last time we was in contact i was not really availalbe
I just fixed after the suggestion you sent me on discord. Really appreciated Bad Boy
D. -
I just fixed after the suggestion you sent me on discord. Really appreciated Bad Boy
D.I’ve checked your last 2.3.3 installer (the one that Khronik was pointing to me) and the MB339 database issue are still there. Do you have a most recent version ?
UCD 402 ("MB339") - Error -> Squadron and corresponding flight are using different specific types UCD 402 ("MB339") FLT - Info -> Flight is not linked to a squadron
-
@Bad:
I’ve checked your last 2.3.3 installer (the one that Khronik was pointing to me) and the MB339 database issue are still there. Do you have a most recent version ?
UCD 402 ("MB339") - Error -> Squadron and corresponding flight are using different specific types UCD 402 ("MB339") FLT - Info -> Flight is not linked to a squadron
Hi Bad Boy
In our discord chat you told me: “I think i have a good solution for your MB939 squadron that you want the players to join first when committing into the online session. There will be at least one aircraft in this squadron (one because it is mandatory regarding the database sake) but if a stupid player forgot to join his dedicated squadron then :
first : only one MB939 will be available
second : when he will try to add a MB939 flight (add package) the MB939 will not be available in the list of available aircraft
how to do that :
remove the MB939 entry in the teplanes.lst (while the MB939 is still there in the VALIDAC.act file)”. In other words no mention for this problem.
D. -
Hi Bad Boy
In our discord chat you told me: “I think i have a good solution for your MB939 squadron that you want the players to join first when committing into the online session. There will be at least one aircraft in this squadron (one because it is mandatory regarding the database sake) but if a stupid player forgot to join his dedicated squadron then :
first : only one MB939 will be available
second : when he will try to add a MB939 flight (add package) the MB939 will not be available in the list of available aircraft
how to do that :
remove the MB939 entry in the teplanes.lst (while the MB939 is still there in the VALIDAC.act file)”. In other words no mention for this problem.
D.Hi Danguard
This sentence was a solution for your server dedicated Airbase. Not a fix for the database errors.
I’ll respond to your pm in the day
-
We have only had 1 or 2 users over the last few days that has experienced the crash on receiving units using the exact same build/version that was exhibiting the crash on receiving units earlier in the event progression. For the 1 or 2 users who reported the issue since this weekend, attempting another time corrected the issue for them.
The server has also been running for over 24hrs without a crash (1-2 reboots within 48-60hrs), with more than 30+ users flying on the server going in and out.
If this is in-fact a database problem, it sure seems very selective. I’m not sure if BMS sends all units on a client connection, but if this was in-fact db error or corruption then I would have assumed for it to be more widespread.
One factor that has changed is the number of players that were initially connected or trying to connect just after the start of the event (more than 30+ users connecting at once). Now it’s maybe 6-8 at once I assume.
I’m still at a loss of how a corrupted unit can allow some to connect without issue (at least on the first attempt) and then manifest itself persistently for others.
Possibly it has been destroyed or isn’t being sent due to the campaign progression?
@Bad:
I’ve checked your last 2.3.3 installer (the one that Khronik was pointing to me) and the MB339 database issue are still there. Do you have a most recent version ?
UCD 402 ("MB339") - Error -> Squadron and corresponding flight are using different specific types UCD 402 ("MB339") FLT - Info -> Flight is not linked to a squadron
The BFS 2.3.3 link is the same build that the crash logs were sourced from. Your suggestion concerning the MB339 came after your request for the theater link, and 2.3.3 is what is currently active on the server since the beginning of the event.
-
Could you investigate if the clients who are crashing are also maybe the ones who moved one (or more) ground units on the map.
Anyway Mav-JP will add a guard (only in MP) to not allow the client to change the battalion’s path to an objective (i mean to not “move to” anymore the battalions in MP)
-
@Bad:
Could you investigate if the clients who are crashing are also maybe the ones who moved one (or more) ground units on the map.
Anyway Mav-JP will add a guard (only in MP) to not allow the client to change the battalion’s path to an objective (i mean to not “move to” anymore the battalions in MP)
I crashed dozens of times and never in my life I had moved a ground unit on FO.
They already disabled the option to move ground units and it kept happening.
-
….
They already disabled the option to move ground units and it kept happening.
This is not working with the current 4.34 but is already fixed in our dev version
-
Please provide full crashlog and’dmp
This is likely a corrupted ground entity on server side we need to investigate
Sorry, I completely overlooked your message in the flurry of responses
Here’s a link to the full dump, log and screenshot:
https://www.dropbox.com/s/a64zhg2el221ozs/2019-10-06_213804_crash.zip?dl=0
-
Coming to the news on that topic. I was running a test today on a campaign created on the basis of the TvT setup. Most people (a handful) were stuck on receiving units. I could connect from my other computer (same router) without any trouble. It was not permanent, some could at first connect fine. Starting a TE goes well too.