Bridge Commander Central

BC Forums => BC Technical Support => Previous "Black Screen of Death" Fixes => Topic started by: cor on September 09, 2007, 05:53:25 PM

Title: BSOD - ImportError: No module named bcdebug (Century Class USS Enterprise 1701-F)
Post by: cor on September 09, 2007, 05:53:25 PM

Hello All,

Well, after months of waiting in anticipation, I installed DJ Curtis' latest creation, but unformately, BC locks up after I install the ship.

I've attached a screenshot of the problem.  Can anyone assist me, please?

Thank you.

Title: RE: BSOD - ImportError: No module named bcdebug (Century Class USS Enterprise 1701-F)
Post by: Blackrook32 on September 09, 2007, 05:55:03 PM

I see the problem. Try making your own plugin for the custom/ships .py -BR32

Title: RE: BSOD - ImportError: No module named bcdebug (Century Class USS Enterprise 1701-F)
Post by: MLeo on September 09, 2007, 06:09:48 PM

I'm still downloading it and there are already problems with it?


Go to scripts/Custom/Ships/EnterpriseF.py and open it, then remove (or rather, but a # in front of it) the first line of the file.

It's possible there will be other problems with it after that, but I don't expect it.
[EDIT] There won't be additional problems after you either removed the first line, or commented it out.
Attached for future reference.

Title: RE: BSOD - ImportError: No module named bcdebug (Century Class USS Enterprise 1701-F)
Post by: cor on September 09, 2007, 06:27:25 PM

Hi Blackrook and MLeo,

Thank you for the quick reply.  I will post back in a few.

Title: RE: BSOD - ImportError: No module named bcdebug (Century Class USS Enterprise 1701-F)
Post by: cor on September 09, 2007, 07:01:11 PM

It Worked!!!!  Setting course for the Seven Sisters in The Pleiades star cluster  :D

Title: RE: BSOD - ImportError: No module named bcdebug (Century Class USS Enterprise 1701-F)
Post by: NeoKaede on September 10, 2007, 10:41:39 AM

Quote from: MLeo on September 09, 2007, 06:09:48 PM

I'm still downloading it and there are already problems with it?


Go to scripts/Custom/Ships/EnterpriseF.py and open it, then remove (or rather, but a # in front of it) the first line of the file.

It's possible there will be other problems with it after that, but I don't expect it.
[EDIT] There won't be additional problems after you either removed the first line, or commented it out.
Attached for future reference.

Ship files don?t need an "Import Foundation" statement?

Title: RE: BSOD - ImportError: No module named bcdebug (Century Class USS Enterprise 1701-F)
Post by: MLeo on September 10, 2007, 01:47:25 PM

Quote from: NeoKaede on September 10, 2007, 10:41:39 AM

Quote from: MLeo on September 09, 2007, 06:09:48 PM

I'm still downloading it and there are already problems with it?


Go to scripts/Custom/Ships/EnterpriseF.py and open it, then remove (or rather, but a # in front of it) the first line of the file.

It's possible there will be other problems with it after that, but I don't expect it.
[EDIT] There won't be additional problems after you either removed the first line, or commented it out.
Attached for future reference.

Ship files don?t need an "Import Foundation" statement?

They do actually, FOundation.<<Something>>ShipDef ;)