Hard Light Productions Forums
Hosted Projects - Standalone => Diaspora => Diaspora Tech Help => Topic started by: doctorfrog on May 19, 2013, 08:52:59 pm
-
I and my friends are trying to get some multi going in Diaspora. Three of the five of us are having this same issue:
- Options screen works fine in single player main menu
- Options screen works fine in single player mission (F2)
- Options screen inaccessible, and game crashes, in multiplayer main menu
- Options screen inaccessible, and game crashes, in multiplayer mission (F2)
Here is the output from my latest crash:
Assert: (pos >= 0) && (pos <= num_pos)
File: slider.cpp
Line: 84
ntdll.dll! ZwWaitForSingleObject + 21 bytes
kernel32.dll! WaitForSingleObjectEx + 67 bytes
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
kernel32.dll! BaseThreadInitThunk + 18 bytes
ntdll.dll! RtlInitializeExceptionChain + 99 bytes
ntdll.dll! RtlInitializeExceptionChain + 54 bytes
Again, three of us are having this issue, identically. Two of us are just fine.
-
Can you post your pilot file please? You'll find it in Diaspora/data/Players/Multi/inferno
You can also try moving that file somewhere safe and then creating a new pilot with the same name. That should fix it.
-
Is Player profile corruption a common thing? My profile was not corrupted but I did experience a bout with not being able to use respawn, no matter how many I changed the mission file. I ended up reinstalling the entire game. Should I have also created a new player in that case? We usually play coop with each other. I will have my friend answer as soon as he can.
-
Player corruption was unfortunately a big problem. Hopefully this won't be an issue in the next patch we release as we'll probably move up to 3.7 builds of FS2_Open which have completely rewritten pilot code.
Your particular issue sounds new, but I'd definitely try a new pilot before a reinstall in almost every case.
-
Thank you for the quick reply. I will try that tonight and let you know what happens. Let me know if I can provide you any more detailed or helpful info.
-
I'd also like to express my gratitude for the assistance you've provided.