The mod still crashes when doing network tests. I thought I solved it then it just keep rearing it's ugly head again the next time I do tests. This is the BF242 mod by the way. It's a mod that makes the game look and play like BF2. I didn't create this mod but am fixing it up.
I wanted to try to get to the bottom of this, so I did a network test using the debugger so that I could look at the log files.
I started a separate game installation as the host and connected to it with the main game I play. Debugger is limited to LAN mode but the error is not effected by what mode that server is running.
The server debugger will load up without incident. However when I connect to it as the client, the debugger (for the client) spits out on odd message shortly before the ready screen comes up:
Any ideas what this error means? The server doesn't give me this error nor do I see it when doing singleplayer modes or as local host. Only the client spits out this error upon connecting to the server.
After I click ignore, it continues to load for a few more seconds and then just as you hear the ready screen sound effects the game crashes...
The client crashes out leaving the server debugger running up until it realizes the player left (since if a client crashes out or alt-f4s out there is a 20-30 second timeout period where that player is still taking up space on the server). Once the debugger figures out the client left, it then proceeds to crash too.
However the dedicated server does not crash when the client crashes out. Weird.
I was testing Market Garden in Conquest mode. I get a smiler crash out with most of the maps. Only maps that work 100% is Daqing Oilfields Day 1, Kursk, Night Ops, and Wake Island. For now the coop game mode actually seems more stable which is even more puzzling to me since most problems that occur tend to occur with COOP and not conquest.
I really want to get to the cause of the crashes. I tried remming out all the static objects for the map. Still crashes. Remmed out all vehicle spawners and the stuff in the precache...Still crashes. Remmed out the kits in the init.con file...still crashes...
By the way the above error does not show in the retail EXE and doesn't cause a crash out to desktop. It loads without incident and crashes out just before the ready screen appears just like the debugger does. The crash is of course of the "Windows Error Report" variety.
