Notes |
|
|
I was able to reproduce this by deleting the single player pilot, exiting the game and going back in. If I just pick the multi pilot it works. If I go to the single tab then back to the multi tab without creating a single player pilot it crashes. |
|
|
|
Just tested the 10-22 build and received the same error. |
|
|
(0008593)
|
taylor
|
2007-10-25 23:41
|
|
The not-being-able-to-create thing is a known issue, and not really a bug. The game simply does a check to see if the last pilot used was a single or multi player, then jumps to that part of the menu. If no pilot exists (usually happens when you remove all pilots) then it will force you to create a pilot before you can switch between single/multi again. It can be rather annoying, but we aren't like to change how that works (anytime soon at least).
It's certainly not supposed to crash either way though, so I'll take a look at that. |
|
|
|
Actually it will let you switch between single/multi if no pilot exists just by hitting ESC then clicking on the single/multi tab. |
|
|
(0008595)
|
taylor
|
2007-10-26 03:47
|
|
Hmmm, didn't do that for me last time I tried it.
But, the bug is fixed either way. I was a simple case of a pilot-file-fix gone wrong. In order to prevent pilot file corruption, it was necessary to allow you to exit the pilotslect menu without the game trying to save the selected pilot. And you would do this by pressing ESC. Unfortunately, this was intended solely for the purposes of exiting the game, so when you do it to escape from the text input it set this variable which said that the game was going to exit and to not save the current pilot. This also made it avoid setting up various player pointers and that's where the crash was coming from.
There will be a new build at some point this weekend with this. And I'll mark this bug as resolved once I have a chance to commit the fix to CVS. |
|
|
(0008610)
|
taylor
|
2007-10-28 17:12
|
|
|