Bridge Commander Central
BC Forums => BC Technical Support => Topic started by: CassandraSaturn on October 30, 2017, 05:50:10 AM
-
hello. i'm seeking for assistance with BC because i installed BC months ago, i did everything right. but i can't even seem to get it running on my win7 computer. maybe i missed a step? i installed BC from a website that had all those classic old computer games that i used to play on old Windows 98 computer including Wolfstein as well.
i downloaded BC from this site: https://www.myabandonware.com/game/star-trek-bridge-commander-a3c
i had issues with because of bwink32 and other issues also related to 32s things.
can you please help me with that?
-
As a rule of thumb it is recommended to not install the game in the default directory of "program files" on anything newer than XP. It needs to be installed in a folder like C:\\games for best stability because of how Windows treats programs in that folder.
Unfortunately that is all I can help with as we cannot support cracked games. We cannot guarantee their stability or comparability with systems or any future mod installs.
That's the end of comments here.
-
Unfortunately that is all I can help with as we cannot support cracked games. We cannot guarantee their stability or comparability with systems or any future mod installs.
i think that strict rule can be relaxed a bit...
it is one thing if someone asks where to download it online, but if they already have it, we can try to help... there is a good chance the game will have problems with stability and other problems, that should be urged of course...
-
It's sort of a grey area, but I tend to agree with Jimmy on this. After all, game is 15 years old. Not like the Activision-Cops will be sniffing around for people running a cracked copy these days. And a cracked copy of BC, is virtually indistinguishable from uncracked (other than not requiring a disc, I don't think there are any differences at all).
-
It's sort of a grey area, but I tend to agree with Jimmy on this. After all, game is 15 years old. Not like the Activision-Cops will be sniffing around for people running a cracked copy these days. And a cracked copy of BC, is virtually indistinguishable from uncracked (other than not requiring a disc, I don't think there are any differences at all).
yeah, they don't come after anybody. i had this game from that site for almost two years now and i still can't figure out why it doesn't show me anything but black screen of death. i fixed bwink32 issue last night yesterday.
-
It's sort of a grey area, but I tend to agree with Jimmy on this. After all, game is 15 years old. Not like the Activision-Cops will be sniffing around for people running a cracked copy these days. And a cracked copy of BC, is virtually indistinguishable from uncracked (other than not requiring a disc, I don't think there are any differences at all).
And this leads to another thing... With Activision having lost the publishing rights to Trek games, and Totally Games being possibly defunct (the Wikipedia page for the company says they went under in 2015 but there's no source; other online sources are vague on whether or not they're still around)... At what point is the game abandonware and we have more leeway with it? And would they even care? Activision has much bigger money makers and has had them for years (World of Warcraft is the big elephant in the room). The game is 15 years old, going on 16 - if it was a person it'd be old enough to drive.
Just my thoughts but I know this is kind of a frowned upon topic so that's all I'll say on it unless anyone wants to add.
-
totally agree, Morgan...
how people got BC should no longer matter if they post they downloaded it...
asking where to download BC tho - we cannot help and guide to that; asking for a copy of BC or where to download it still is a violation of forum rules...
i still can't figure out why it doesn't show me anything but black screen of death.
please be advised that a downloaded copy of BC has a significantly higher chance of crashes, errors with mods and just problematic overall... most issues of a downloaded copy just cant be addressed and fixed...
if you do get a BSOD, tho, please feel free to post a screenshot of the console report (or the console log itself if possible) and we can try to address it...
-
As I said elsewhere, my first BC experience way back when, was via a pirated copy (an ISO of the original disc + no-disc crack). It was virtually indistinguishable from the real deal (other than not requiring a disc), and my copy had no pre-installed mobs. It was just the original.
Depending on the copy, and what included mobs, support may be... difficult.
-
As I said elsewhere, my first BC experience way back when, was via a pirated copy (an ISO of the original disc + no-disc crack). It was virtually indistinguishable from the real deal (other than not requiring a disc), and my copy had no pre-installed mobs. It was just the original.
Depending on the copy, and what included mobs, support may be... difficult.
here is no mobs, no mods, and it's full game copy.
-
totally agree, Morgan...
how people got BC should no longer matter if they post they downloaded it...
asking where to download BC tho - we cannot help and guide to that; asking for a copy of BC or where to download it still is a violation of forum rules...
please be advised that a downloaded copy of BC has a significantly higher chance of crashes, errors with mods and just problematic overall... most issues of a downloaded copy just cant be addressed and fixed...
if you do get a BSOD, tho, please feel free to post a screenshot of the console report (or the console log itself if possible) and we can try to address it...
okay where do i find console report?
-
okay where do i find console report?
Easiest method is with this little script by USS Frontier - Console Tracker: https://www.nexusmods.com/startrekbridgecommmander/mods/427/?
Just drop that .py file in your "scripts/Custom/Autoload" folder, load up the game, and then exit and you'll have a console report text file in your "scripts/Custom" folder.
It logs everything automatically so you don't even have to think about it.
-
Easiest method is with this little script by USS Frontier - Console Tracker: https://www.nexusmods.com/startrekbridgecommmander/mods/427/?
Just drop that .py file in your "scripts/Custom/Autoload" folder, load up the game, and then exit and you'll have a console report text file in your "scripts/Custom" folder.
It logs everything automatically so you don't even have to think about it.
ahh thanks. i will try that.
-
i installed the console tracker, but it didn't give me console report. it didn't show up in my bc files maybe i installed it wrong?
-
USS Frontier's Console Logger requires foundation, If you don't have that yet, it (and almost every mod) wont work.
The simple variant of console report is to open the console, (using the '~' tilde key on english keyboards directly below escape) pressing enter and posting a screenshot of the result.
-
well, i give up. i'm gonna have to get official full game on CD somehow. i tried everything. even your suggestion. i think i have borked it.
-
have you successfully patched the game to BC 1.1?
i think that is required also to be able to pull down the console report...
-
Screenshot you posted on discord shows that you are missing sfx and scripts directories.
-
the old fashioned way to pull a report was to hit the tab key, then hit enter when the console popped up, and take a screenshot of the resulting report
-
well, i give up. i'm gonna have to get official full game on CD somehow. i tried everything. even your suggestion. i think i have borked it.
I know BC can get irritating at times. To overcome a lot of the inherent engine problems BC's modding framework is essentially a collection of bandaids that need to be applied the right way in order to fully work.
When installing BC, you should always, no matter what:
* Install BC into the C:\Users\Public\Games directory if you're running anything newer than Windows XP.
* Install the 1.1 patch immediately after installing BC. Without it, mods will not work correctly.
The next steps from here depend on whether you're building an install from scratch or installing KM. If you're going with KM (which most people do), the next step is to simply install KM. That's it. If you're building your own install, you have to install things in a certain order:
* Foundation (Included with BCUT which is a necessary modding tool)
* NanoFX 2
* MVAM
* Bridge Plugin
* QB Autostart
* BCS:TNG: The Beginning
* Galaxy Charts
* DS9FX
Once those frameworks are in place, you can install ships and scripts in any order you choose.
-
I know BC can get irritating at times. To overcome a lot of the inherent engine problems BC's modding framework is essentially a collection of bandaids that need to be applied the right way in order to fully work.
When installing BC, you should always, no matter what:
* Install BC into the C:\Users\Public\Games directory if you're running anything newer than Windows XP.
* Install the 1.1 patch immediately after installing BC. Without it, mods will not work correctly.
The next steps from here depend on whether you're building an install from scratch or installing KM. If you're going with KM (which most people do), the next step is to simply install KM. That's it. If you're building your own install, you have to install things in a certain order:
* Foundation (Included with BCUT which is a necessary modding tool)
* NanoFX 2
* MVAM
* Bridge Plugin
* QB Autostart
* Galaxy Charts
* DS9FX
Once those frameworks are in place, you can install ships and scripts in any order you choose.
Morgan,
Which should be first, DS9FX or The BEGINNING? Like I know they both need QBR/Autostart to run, much like addship0.4 and so on. But, would DS9FX and BEGINNING screw with each other if installed in the wrong order?
Because I do like, KM. But, the ships, balance and the straight stubbornness I have "I'd Rather Do It Myself" attitude. And that MOD Crashes a lot too.
-
The Beginning was released first, and if I recall correctly DS9FX might have some fixes for it as well (not certain, double check that with Mario).
TL;DR: The Beginning first, then DS9FX. When in doubt, go by release date.
I do like, KM. But, the ships, balance and the straight stubbornness I have "I'd Rather Do It Myself" attitude. And that MOD Crashes a lot too.
Hell yeah man! I run a home-grown, ground up BC install myself. Nothing against KM, but I prefer my own ships/hardpoints. I also don't like my BC install too... bloated... I guess is the word.
The crashing, though, isn't just a KM deal. Modded BC is pretty unstable KM or no KM. Most of it appears to be NanoFX related. I made a post several years ago to help with optimizing BC - http://www.bc-central.net/forums/index.php/topic,7056.0.html That should help you at least slim down BC and keep crashes to a minimum.
Let me know if you need any more info!
-
The Beginning was released first, and if I recall correctly DS9FX might have some fixes for it as well (not certain, double check that with Mario).
TL;DR: The Beginning first, then DS9FX. When in doubt, go by release date.
Hell yeah man! I run a home-grown, ground up BC install myself. Nothing against KM, but I prefer my own ships/hardpoints. I also don't like my BC install too... bloated... I guess is the word.
The crashing, though, isn't just a KM deal. Modded BC is pretty unstable KM or no KM. Most of it appears to be NanoFX related. I made a post several years ago to help with optimizing BC - http://www.bc-central.net/forums/index.php/topic,7056.0.html That should help you at least slim down BC and keep crashes to a minimum.
Let me know if you need any more info!
http://www.bc-central.net/forums/index.php/topic,10315.msg218138.html#msg218138
It's Nanofx 2.0 Surely .... I will miss the blinkers, the darker look in the environment, weapon's flash and target plasma streams. i was going to reinstall with Nanofx 2.0, but I'll wait until after I perfect my HPs, Textures and projectiles. And Replacing all the ships and textures from KM, seams to be an over ambitious mission.
-
Sadly NanoFX is needed for just about everything. You can, however, disable everything except WarpFX. I still leave ExplosionFX on because I typically don't run BC long enough for all the memory to leak anyways. That'll buy you some time.
Another piece of advice: Avoid 2048x2048 ship textures if you can help it. I only use them on ships that don't have smaller ones. 1024x1024 still gives good visuals and uses 4x less memory.
Even unmodded BC will crash after a few hours. BC was kind of rushed out.
-
Uhm, first battle, first ship explosion = "STBC Has Stopped Working, Windows is looking for a solution."
And, I never allow more than 1024 x 1024. And that's the pain in the ass, If I want WC, then I open up PixBuilder Studio and resize. And, a lot of mods, if you think about are a bit cheater. Like the AI doesn't know to boost/redistribute shields, or order you to self-destruct. :dance
The reason for my original question regarding DS9/BCS was that maybe, try again with that mod .. .. Even though the transporting of the enemy to my ship had ALWAYs pissed me off. :evil:
-
Uhm, first battle, first ship explosion = "STBC Has Stopped Working, Windows is looking for a solution."
Yeah that's the most annoying thing in the world. And there's never a console dump to go with it to tell you what's wrong.
What can you tell me about what was going on when it happened? First battle, first ship explosion. Do you remember which ships? Which map? Which bridge? Anything you can remember, no matter how seemingly insignificant, could help (most of the time when this crash isn't related to standard BC memory leaks it's either a scripting error somewhere or a missing texture for something I've noticed).
-
It's random. But, usually to start with. I'll get into my Venture Refit. The fight either a copy of it or a Warbird, Vorta something. It doesn't ever seem to matter what ship, I mean really it happened on a Plasma Stream once. And the last thing to report on log is a sentence about splash radius. Or wait, found an old log.
Setting splash damage for Plasma Stream0 to (91.875000, 1.837500)
AttributeError: Redirect
-
What you're describing in the console dump is normal. I'd disable SpecialFX in NanoFX and try it again.
There are also some files from KM that can help with stability. The crash fixer is one (located in the Custom/Autoload folder), along with the FixMem.py file in the QBAutostart folder. Not cure-alls, but definitely helpful.
Did you also do the 4GB patch?
-
4gb_patch.exe
ReSet.py
000-Fixes20030221.py
But, I'll try it when I finish moving my room around ... Thanks!
-
4gb_patch.exe
ReSet.py
000-Fixes20030221.py
But, I'll try it when I finish moving my room around ... Thanks!
0000-CrashFixer.py - This one as well.
Let me know how everything turns out!