Bridge Commander Central
BC Forums => BC Technical Support => Topic started by: Retribution on June 13, 2008, 07:36:53 AM
-
#loveFFX#
Okay guys, usual story here. Custom install, debug window hating me for it.
Every time I try to abort the mission or exit the game, I get a debug window. They are very very similar and have been maximized for your viewing pleasure. It's got me stumped (not exactly uncommon) and it's starting to drive me nuts. I don't want to have to keep playing the game in windowed mode just so I can hit X on those things to get back to windows.
Thanks for any help guys.
-
im not a scripting expert,
But it appears to be a problem with the slipstream drive plugin.
-
This is what it looks like to me:
BC is triggering a new mission event, but it's doing so on the Abort Mission (and thus also Exit Game) button, and since it's exiting, there is no Episode.
Contact the author and point him to this thread.
-
this is a link to the Slipstream Tech Support forum:
http://bcs-tng.com/forums/index.php?board=68.0
-
I've got the same problem, when exiting the game (fullscreen) it crashes, but since I use VISTA now i have no problem terminating the process. As MLeo already said it is trying to do something where it shouldn't. I think the autor might left out a command at a teminate function, a simple check if a mission still exists or something like this...
So far for the traceback error...
But what all that statements before that are, I don't have a clue where your install prints that... :?
-
Those statements before aren't errors.
Try this in the console:
print "Not everything you see here is an error"Finish taht with Enter. ;)
Most of that are FoundationTriggers, and possibly the FoundationTechnologies PhaseCloak.