Bridge Commander Central
BC Forums => BC Technical Support => Solved Problems => Topic started by: Kirk on May 02, 2008, 05:41:30 PM
-
I've had to restart my BC install from scratch, so I've been very meticulous with my ship plugins, and trying to keep the file sizes as small as possible. I am having a weird problem with only one custom plugin though, the wrong ship icon is showing up when the ship is played, but not in the QB menu, also there is nothing in the console. Here is the plugin, and screenshots of the problem
will be up shortly are up.
-
Which of the 2 ships are you having problems with exactly?
The problem is strange, since they both should use the same icon (they use the same information).
-
Both, and I checked the .tga file, it is the correct file.
-
Then I think I'll need a screenshot.
-
Of what? I provided screenshots of the actual problem. Do you want a console report or my file folders? Regardless of what people may think, I cannot read minds. (Joking :P)
-
They weren't attached when I posted.
I suspect that you have another ship called Century, this time a Nebula class, but the icon for this particular ship is registered to the same species (number) as that Nebula class, mostlikely one that is loaded later.
-
I don't really understand what you mean by "species," however, I did try the USS Century, and it works fine. Now, I'm really confused.
-
Try changing the name of the ship that doesn't work by adding a space after the name (but before the " or ')
-
I changed the abbrev, should I change the long name?
-
Try it first with just the abbrev, changing the longname could mess up other things.
-
The abbrev didn't do anything.
-
Then try changing the longname as well, in the same manner.
I've just confirmed that it won't mess up like all BCMP generated plugins when you do that (thiank you DJ, or whoever made the plugin).
Attach it as well when you have tried it. The changed plugin that is.
-
No luck, here is the the plugin. By the way, the original plugins were from DJ's ships, however, I have combined and modified them.
-
I think you added the same one as before, since I don't, directly, see any changes I mentioned.
-
I removed the parentheses from the long name. What specifically do you think would make a difference, as I have ships that have differing abbrev and long names. I also shortened the abbrev name to 'EntFDJ' and the was still no change. I also made sure that I deleted the .pyc after every change. I am going to try changing both the abbrev and long names to 'EntFDJ'.
Edit: No luck, here's the plugin. I hope I did what you asked.
-
This ought to do it.
-
Nice abbrev name Mleo, however it didn't work. I am at a loss.
Should I try separating the two ships' plugins?
I tried splitting the plugins and the problem persists. Why doesn't the problem show up with the USS Century?
-
And when you play as the Century it also works?
Have you tried changing to another icon, just to try it out? Say, KessokMine?
iconName = 'Century'
becomes:
iconName = 'KessokMine'
-
The Century is fine when I play it, and changing the icon name had no effect.
-
The Century is fine when I play it, and changing the icon name had no effect.
Then it would seem something else is amiss.
Type this into the console after you have started QB (you don't have to setup and started a battle for this):
import Foundation
print Foundation.ShipDef.EnterpriseF
print Foundation.ShipDef.EnterpriseF.iconName
Capitalisation matters.
-
Here you go. By the way, I changed the icon to the worker bee in the last troubleshooting step.
-
Ok, try this next:
import Foundation
print Foundation.ShipDef.EnterpriseF.__dict__.keys()
-
Here you are. Took me a few tries before I realized that there was supposed to be two underscores.
-
Those are double __ not single _
-
:( I figured it out.
-
About the underscores or the real problem you are having? If it's the latter, please enlighten us.
-
The underscores, I'm baffled about my problem.
-
So what did it say after you found the __ problem?
-
It is in the picture I posted, at the bottom of the report.
-
You know, you really should not be having this problem. :(
I'll whip up some debug scripts tomorrow, I doubt I should do this now (considering I overlooked the info you provided in the screenshot).
-
It's ok MLeo, take your time.
-
I've been looking through the scripts, and normally this shouldn't be able to happen, otherwise changing the name would have taken care of it.
Can you try disabling QBAutostart and see if that changes anything?
-
Tried and I had the same results. I don't get it. I've looked at the plugin hundreds of times. Hell, I had a dream that we figured out the problem. (The solution in the dream by the way was that there was a period in import App.) I've tried replacing other important scripts with my backups and the problem still persists, and only on this one ship. Ugh, I'm off to bed.
Aaagh! This problem is popping up all over the place! More ships are succumbing to this disease. It's not limited to replacing with the Nebula icon either. Some are being replaced with the Akira icon, and the console still reveals nothing. Also, it's not limited to multi-ship plugins, single ship plugins are also having problems.
:( Please don't forget about me Mleo, I still need your help.
-
Bump, my problem still exists and I am still without ideas.
-
I'm afraid EDITs don't generate e-mails. :(
Try disabling all mutators except for the first 3.
-
Sorry about the edits. I figured if I edited the post, it would show as new, yet I wouldn't be double or triple posting.
The problem is still there.
-
You know, this ought to be impossible. :(
Did you do anything between these random changes?
-
I dunno for sure, but I'm starting to lean towards some sort of data corruption. Perhaps a download messed up a bit or the install didn't copy 100% correctly?
-
I don't think I've changed anything. I've even gone back and restored some of the KM 1.0 scripts, except for the plugins, from time to time. I always check to see if the icons and other related files are there, plus if my download was corrupted, wouldn't winrar tell me? I'm going to go through and restore the KM scripts again, and see if anything changes.
Problem has been solved here. (http://bc-central.net/forums/index.php/topic,3929.0.html)
-
plus if my download was corrupted, wouldn't winrar tell me?
Not always.