Rotareneg Posted February 5, 2017 Share Posted February 5, 2017 I crashed twice during the OPFOR scenario today. The mission was loaded from a saved session after the host crashed last week, just in case that matters. This message was recorded at the end of the logs: [18:48:31,213] WARN : RaknetNetworkTransport::ServiceNetwork() was blocked for 26091ms After rejoining this message (and variations with different unit IDs) was rapidly spammed at the top of the screen, and resulted in an almost 4 meg log file before it crashed again: [18:51:12,589] ERROR: Error receiving state block data. Can't find Blue combatant with ID 0x22322B-3/2/C Attached is an archive with the logs from the sessions and the dumps from the crashes. crash_logs.7z 0 Quote Link to comment Share on other sites More sharing options...
Gibsonm Posted February 5, 2017 Share Posted February 5, 2017 When you say "saved session" do you mean you as the client saved it after the host crashed, or you you mean the host somehow reloaded it post crash and then saved it? 0 Quote Link to comment Share on other sites More sharing options...
TankHunter Posted February 5, 2017 Share Posted February 5, 2017 Client saved after host crashed. Rotar and Zaphod had the same issue apparently, but no one else did. 0 Quote Link to comment Share on other sites More sharing options...
Gibsonm Posted February 5, 2017 Share Posted February 5, 2017 I'm not an expert, but I suspect whatever the client saved after the host crashed would be corrupted (since it didn't disconnect gracefully, etc.). 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.