Bridge Commander Central
BC Forums => BC Technical Support => Topic started by: Dalek on August 04, 2008, 04:57:33 PM
-
Yeh, I have KM 1.0, loved all my controls (fleet orders, silent running etc.), installed a mod, had all the requirements and now POOF! It's all gone. Mutators show that the Extension 1.0 is on and all the other mutators, yet it's all gone. The mod is the NX Class Pack *MEDIUM*. Please help!
-
Console report please.
-
Console report please.
OK. Let me sort it out.
-
I think you just need to re-set your keyboard controls.
Assuming you are talking about those.
Otherwise, if you are talking about buttons, then we need a console report.
-
Try uninstalling the mod to see if you get the controls back.
-
OK, trying to uninstall mod.
Thing is though, it doesn't kill my game. Where should I open the console report? At the Quick Battle bridge or at the beginning of the game?
-
Uninstalled mod, didn't work.
But here's something I've realised. There are still some buttons left:
Kiska (Helm) still has DS9FX and Thrusters
Felix (Tactical) still has Secondary Targetting
Saffi (Second in Command) still has Core Ejection.
-
I've finally got the Console Report.
-
Alright dale first, this
Try uninstalling the mod to see if you get the controls back.
is never the answer. In fact, doing that can cause more problems.
Second, you aren't catching the error early enough. At the top I can see there is a syntax error, but not where it is. Please run the game in windowed mode and get us a shot of the first error window that pops up.
-
OK. Stay logged in, I'll get it for you.
-
I can't scroll up the report. What should I do?
-
You shouldn't have to, if you run the game in windowed mode, a debug window will pop up at the first error.
-
Windowed mode? How would I do that?
Edit: Found out, done it.
-
This.
-
OK, got pic. But I think it's worse than the other one.
-
Use a console logger.
It's mostlikely a shuttle plugin that's faulty.
Or a QBAutostart plugin.
-
It's mostlikely a shuttle plugin that's faulty.
Or a QBAutostart plugin.
Query-Why would it be a shuttle? The mod I installed had nothing to do with shuttles.
Where would I get a console logger...
-
Because it's talking about the ShipManager, that's a Shuttle Launching Framework component.
-
OK, got pic. But I think it's worse than the other one.
You didn't restart after switching to windowed mode did you? You need to do that to get the dosbox.
-
is never the answer. In fact, doing that can cause more problems.
I disagree since uninstalling mods have eliminated problems for me on countless occasions.
The thing is people don't delete every single file from the mod (one file could be the source
of the problem) or they don't back up their old files and they are overwritten.
Uninstalling mods is effective in the process of elimination.
-
The problem is, while it does solve the symptoms, it doesn't solve the problem.
And most people don't know all the files associated with a mod, and what if it's a faulty update?
If I'm in a cynical mood, I would say it's to amputate an arm to cure a scrape wound. Yes, when I'm really cynical. ;)
-
Like I said, a lot of folks simply won't backup there files which could solve a lot of issues such as dealing
with a faulty update. The reason why I like uninstalling a mod is because 99% of the time the problem will
go away, then I can do a manual install and localize the problem to a single script. If that doesn't work then
I leave it to the pros such as yourself.
-
But you could also simply use a console logger to discover the error (the specific script, line number and function where the error is located) and lower your work by what, 1000%? lol
-
No man, I like deleting stuff. :arms:
-
Well, I said that I uninstalled the mod, but I must have left something. So I tracked it down, deleted it. BC is fine, but I'm still wary of it. As MLeo said
The problem is, while it does solve the symptoms, it doesn't solve the problem.
so I feel like uninstalling my BC to basically wipe it clean and start fresh. If anything, I'd rather do that in case my BC craps up later on. You lot have been really helpful to me, I'll give a cookie to all of you since I'm feeling helpful.
-
So did the console logger yield anything?
-
Well, I said that I uninstalled the mod, but I must have left something. So I tracked it down, deleted it. BC is fine, but I'm still wary of it.
This is true in nearly all cases; I've encountered this problem on numerous occasions. If BC is working fine now I'd say leave it alone and not fuss with reinstalling BC. I know how much of a pain that is.
Also, I think what MLeo meant was while deleting the files resolves the symptoms it doesn't offer any insight into what specific script is causing the problem, hence the console report. I use console tracker 1.7 for this.