Bridge Commander Central
BC Forums => BC General => Topic started by: MrSFX on September 02, 2018, 03:11:33 AM
-
Back on my old pc which was a pentium g645, 4gigs ram and a gt 630 I had no problems running BCKM,yet on what I've built in march with GTX 1050 TI, R3 1200, 8Gigs ram it lags and is slow in performance. How to fix it
-
Lower graphics quality, if not already. It's an old game and having a more powerful computer doesn't mean anything really.
-
Hello MrSFX, did you find a solution for the performance problem?
I have a friend with the same problem and we tried all the standard fixes for old games like:
Starting as Admin and Compatibility on WinXp Serivce Pack 3
Reinstalling the game and drivers to the newst version
Turning on the Legacy Components
Turning of antivirus program
Changing graphic settings
Using a No-CD Patch
Nothing we did brought us closer to a solution, maybe you had better luck?
-
I just beat a bad case of lag myself. turned out it's the old "have you tried turning it off, then on again" chestnut in my case; the comp needed restarted.
a couple suggestions
1. don't run ALL the mutators
2. reduce the size of your textures, which is the MAIN cause of hiccups
Mario is right, of course. BC tends to choke on sizes above 1024's
-
There was also a non-official patch/script released somewhere I think? (BR might remember) which allowed BC to access more memory? (a fix I think for the old memory leak issue?)
-
Lurok - is this what you're referring to?
https://ntcore.com/?page_id=371
-
That's the one :thumbsup:
-
that'd actually help with a homebrew I picked up with the same kind of engine memory leak. didn't even know that existed. cheers, guys.
-
so much for THAT. my comp refused to OPEN the thing :facepalm:
-
so much for THAT. my comp refused to OPEN the thing :facepalm:
What kind of error did you get?
-
Works OK on my end with BC and others, I've had it for years...
-
it does the exact same thing that flash movies I've been saving over the years does. tries to open itself in an open dialogue, then just goes "couldn't run executable"