Odd crash
-
Ok my buddy and I both installed 4.34 and spent the better part of the day reading and running through our setups. After that we decided to start a new campaign and we wanted to see IFF in action so we picked Iron Fortress since we could fly block 50s out of Kunsan. First mission went off fine. We wanted to see if 4.34 was any more stable than 4.33 so we tried a second mission without a reboot. It launched just fine but when we were most of the way towards the North EoR my buddy crashed and I, as the server, didn’t crash but I was also no longer taxiing around in my F-16 either. I had just stopped with no more cockpit display. I hit the Esc key to see if it would respond and it did right off the bat. I exited the mission and the debrief screen simply said the mission was still in progress. Odd but I just chalked it up to attempting a second flight without reboot. I went to exit to the desktop and at that point BMS crashed.
The mission had been saved so we just both restarted BMS and tried it again. This time the wind was changed and we were going to South EoR. On the way there I saw several explosions on the North side of the base and shortly thereafter Ground notified us that the entire package was cancelled and to return to parking. Very unique and cool to see. Two of the AI had already lined up on the runway and they promptly turned back towards taxi fairly close to where I had been holding short. For some reason the AI logic wasn’t paying attention to collision logic at all as they were both side by side and aiming for the exact same aim point. Right before they were going to merge they just vanished from view. My buddy and I turned around and were just starting to taxi away from the South EoR and we got the exact same crash scenario. Client properly crashed to desktop and mine was just no longer in an F-16 and just sitting there as server.
After I got out of that mission and prior to attempting to exit I did a look at Kunsan AB to see what had happened. Three runway bits were damaged and the control tower had been destroyed. However the taxiway we were on was not showing affected at all. I then tried to exit BMS and crashed again. So we both decided a full reboot of our systems was in order.
Third time was the charm. This time it actually gave us a scramble mission. This is why the base was getting hammered with us still on it is we had 4 Q-5s, 2 Su-25s, and 2 MiG-23MLs very close in. We gave them the unwelcome committee and landed back at Kunsan. My buddy exited first since, of course, clients exiting after the server has left 3D is a great way to induce a crash. His debrief said we had failed. I wasn’t surprised as I’ve seen more scramble mission fails than I care to ever remember due to how the logic of how fail/success of that mission is figured. I then exited out but my debrief screen was completely different than my wingman. It showed us diverted and divert mission as a success and both with excellent ratings.
So not sure what caused the second mission to not induce a scramble or why it crashed the same way as mission one. Also not sure why our debrief screens for the exact same flight showed completely different outcomes. I’m not counting much of anything from the first mission even though it matched the outcome of the second due to us testing MP stability.
-
Did you restart the game after the first flight?
-
@Bad:
Did you restart the game after the first flight?
Yes of course. That is why I discount the first flight error as it was a test. The second flight was done with both of us restarting BMS from the desktop. The third flight was with both of us rebooting our computers.