-
Posts
16,954 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Supreme Cmdr
-
Fatal error starting from Syganstar (resolved)
Supreme Cmdr replied to eric3045's topic in Battlecruiser Series
You can delete that PTYPE014.TGA file now. The patch fixes this problem automatically. -
This patch is just an interim which addresses several critical issues. Because it is not a final patch, it has an expiration date. The final patch will be released prior to the date expiring. Send all premature expiration notices to [email protected] . The patch is on the downloads page There are some oddities with marines on the planet surface related to CD and them flying without jetpacks. Thats what was WIP prior to my decision to release this. The VCF is also included in the patch. Comments welcome - but NO bug reports in this thread please. [ 11-22-2001: Message edited by: Supreme Cmdr ]
-
No. All those INI files have a digital key. Change just one of them and the game will refuse to run. You have been warned
-
How do you read urgent messages?
Supreme Cmdr replied to JaguarNMT's topic in Battlecruiser 3000AD (Legacy)
OK, Who last had that wet Trout? -
quote: Originally posted by Joel Schultz: The ugly : A DOS batch file for the main CD "autorun" entry point?! OK, maybe my aesthetic sense is going overboard and being excessively picky. But it annoys me that a DOS console pops into existence briefly every time I put in the CD. [ 11-21-2001: Message edited by: Joel Schultz ] Blame MS. Nothing I can do about it. Unlike some games which pop-up autorun each time the CDROM is in the drive (VERY ANNOYING), I use a batch file to check for C:WINDOWSBC3K.INI or C:WINNTBC3K.INI and if found, I know the game is installed, so the install just quits. Would you rather the install pop-up each time you put the CDROM in or have to disable AutoRun (which you might need at other times)?
-
Steve I got the files and looked at DX Diag I CANNOT believe that after ALL this time, you were still running on a system with an OLDER version of DirectX. You know, people's posting rights have been revoked here for much less. Last warning to all of you. [ 11-21-2001: Message edited by: Supreme Cmdr ]
-
What are your system specs and video driver version? Do I have to keep telling you noobs to post your system specs? Why not edit your profile and stick it in your sig so that you don't forget?
-
How do you read urgent messages?
Supreme Cmdr replied to JaguarNMT's topic in Battlecruiser 3000AD (Legacy)
Use the up/down arrows keys in COMMLINK -
Search the forum using TRADE as a search criteria
-
quote: Originally posted by Kenada: So if you cant buy a new asset... odd... I wonder why he did it that way... Because its not that kind of game?
-
Read the bottom half of the tutorial. I think I mention it there, or in the manual.
-
quote: Originally posted by Rip: Shoot it's got his name in it more than SCs. It does? I sure as hell 'ope not. Read it again. Slowly.
-
Pack up all the files in the SAVE file (into a zip) and send to [email protected] Also put your bcmsetup.ini and bcmconfig.ini in there too. I also need a DXDIAG printout from the DirectX control panel applet.
-
CTD When Leaving Navitron (resolved)
Supreme Cmdr replied to surfnlt's topic in Battlecruiser Series
Found and fixed with Soback's help* *We've been working on it via private message and emails. I gave him some exact steps and requested more info. We narrowed his problem (with the enlarged NID/MAP menu) to him going to Navitron and exiting. On close examination, the fix indicates that this particular problem caused both issues reported here (CTD on exit from Navitron and growing NID/MAP menus). It is related to the route finding code and some destinations. -
Config key mappings...(resolved)
Supreme Cmdr replied to AlbietheOne's topic in Battlecruiser Series
Don't worry, I'll do something about it. And since you like the FP mode that much, I'll move it up the TODO list. [ 11-21-2001: Message edited by: Supreme Cmdr ] -
quote: Originally posted by The Mule: I am not sure I understand your question....I am running DX8.1 and they are all running fine. When I was running DX8.0 they were all running fine. None of them are DX8.1 dependant, but they are all compatible with DX8.1...so does that mean they are all compliant with DX8.1 as well? This includes older games such as Starsiege and games I bought yesterday at EB such as Aquanox, Wolfenstein, IL-2, and Empire Earth. Oh well, not the end of the world...dont sweat it. All those games are DX 7. Wolf is OpenGL. The point I'm making is that if there is a driver and DX8 issue, I can't fix it. As you've seen, problems WITH the game, which are reproducible, can be fixed. I can't fix (a) what I can't reproduce ( hardware problems. Your original report reeks of a hardware problem and I simply can't into that right now. At the moment, my focus is on game related issues and getting a patch out asap (hopefully before I got to bed or first thing in the morning) and then I can spend as much time on hardware (and the odd wild goose chase) as possible. As you have seen, there have been several false alarms which I spent time on. Thats time take away from fixing actually game problems. See the problem? [ 11-21-2001: Message edited by: Supreme Cmdr ]
-
I'll remind Andrei to look into it. He's good at crazy stuff like that cuz I can't be bothered. So, be nice to him.
-
OK, thats a standard OS crash. Thinking... Well, it could be any number of things. If it was related to your original report, it would crash immediately on jumping (which is what u seemed to be reporting). Nothing I can do atm because I don't want to go on a wild goose chase. Your original report has gone from one extreme to the next. Once you find a common denominator, let me know and we'll go on from there. Until then, make sure your drivers are up to date, that you haven't set an CONFIG option that your system can't handle etc. In fact, delete the bcmconfig.ini file and start a new game. Do NOT alter the defaults. Now run the game as you did before and report back to me.
-
I've never tried it on 4xFSAA. And I can't be bothered by it either. FSAA is a driver dependent issue - nothing - to do with the game itself because its not something we [developers] program. Its handled entirely by the driver. And the fact that BCM also uses TnL, just makes it that much fuzzier. Have you tried it with TnL disabled in CONFIG. Anyway, this is not a tech support issue, so I'm moving the thread. And next time you post, you might just want to post more details. You know, stuff like video card make/model, driver version etc. You know, usefull stuff. [ 11-21-2001: Message edited by: Supreme Cmdr ]
-
It would help if you actually posted USEFUL info. You know, graphics things like : what screen res you are running at desktop bit depth (16,24,32) game res/bit depth (16,32) etc
-
Yes but how many of them were DX 8.1 compliant?
-
Try running the game in a Window using /w1 and when it dies, you can give me the error code. I've tried it here and have no problems. But I'll keep checking into it.
