Supreme Cmdr

Siddown, fool

OK, thanks, looks like a region file is missing. I'm on it.

quote: Originally posted by Kalshion: ..... I didn't know you could that.... Esh, learn something new everyday No, next time pay attention and don't spam the board threads with rubbish.

Thanks. I think I can take it from here. I just need to install one of those cards you have, in a test machine and take it from there.

quote: Originally posted by Cougar_DK: This is precisely the thing it tried to say last night. Great to hear I'm not alone. It works fine in BCM. Yeah, but what you posted was rubbish, compared to what he posted. Learn how to be descriptive and your posts won't be deleted.

The console server crashing has already been reported in the tech support area. I plan on looking into it tonite.

quote: Originally posted by JCMan: 1. This may sound odd, but in UC, unlike BCM, I noticed that whenever im flying over an ocean (Actually being directly above all the water) I can't ever get high enough to break to space. I usually need to find a large chunk of land to use. Funny because I can get higher and actually break to space when over land, and when im over water It's like Im allready over my craft's altitude limit. Does anyone have any tips on how to get back into space? It can get real annoying when there is no good sized chunks of land around. Thats odd, because it shouldn't make a difference. But I will look into it.

I checked the code last night. Its disabled. But I can't remember why I disabled it. I must have had a reason for disabling it. Once I figure that out, I will re-enable it. It probably has something to do with the fact that back when it used to work, there was only one single career, the Commander. With the added careers, the WAYPOINT and other buttons are not valid and would cause problems. ....or something like that. But, until I find out why I disabled it, its going to stay disabled. I will however enable it this weekend and go through my changelogs to see why I disabled it. And if its a career thing, I'll just re-enable it for the Career commander. *topic revised for clarity*

It looks like the planet is too large for the card's Z buffer. It works just fine back here. But I have added it to my list of things to look at.

No. I'll just change it so that the ship used in that scenario is a MK3 instead of a Megaron. Confusing solved.

I can't enable it for planets because it would kill the performance. Besides, just going to a hostile base is enough to give you all the threats you want.

quote: Originally posted by Gol_Stoan: The prepatch version of the game worked fine with 53.03, I wonder what changed. Thats what I want to know. Its definitely not the graphics engines, cuz I didn't touch it.

The turret heading is different when decoupled. Looks like I never did explain this in the manual. I will add it to the manual revision file later this weekend. *topic moved*

LMAO!!!

I already said that I was going to revise it in the final 1.00.02 patch, so you babies can quit yammering about it. It won't be exactly as it was in BCM/G, but it will be similar to, if not better than. And joystick control for vehicles will also be impmented.

The sound card causing performance issues, is a completely different issue entirely. So, ladies, lets not get confused.

Go to guru3d.com and try the 53.04 drivers. Those are ones I am using and not having that problem on my FX5900 Ultra. If you are truly brave, try the 56.xx drivers as well. You are the official guinuea pig on this, so let me know which driver fixes it.

Yeah, I will re-map those in the next patch for you annal types who won't let me slip anything past.

quote: Originally posted by TheRedComet: well i suppose when the GBS III is out for the public , we would be able to create MP universes of our own? could add a whole lot of replay value to it. No. And I'm probably not going to release GBS-III either.

Yep, looks like the shader. Did you recently update your drivers as well? Anyway, backup your UC.EXE file. Then download this file and unzip it into your game folder. Run it (with clouds on) and tell me if you get the same results as with the RC1 patch.

quote: Originally posted by Chaoticmass: My problem is a little different. It just crashes anytime FP view is attempted. Though, it could have something to do with my card not meeting the minimum requirements of the game Thats right. Your card does not have a vertex shader. quote: Originally posted by netshaman: I only can say that my video card don't seem to appreciate certain type of lighting... It's an ATI radeon 8500. Strange eh ? Gimme a break. Catalyst 7.78 drivers? quote: Originally posted by Nicholas Dogris, Ph.D.: OK, I am getting a CTD during the the first mission of the campaign. I set the navitron toward LV103 and engage the auto pilot. I ready 5 marines for combat and sit back and watch the show. As I approach the hyperspace gate at Kruger in the Omega Centauri system the CTD happens. Works fine here Nick. You're sure you're not running the 1.00.02 patch with a 1.00.01 saved game?

It is being culled at a certain distance. Thats normal.

If there is no UCCONFIG.INI, the game won't start. Anyway, it sounds like you've hosed something on your system.

The problem seems to be in the clouds vertex shader. Have you recently updated your drivers?

No, there are no maps in the game. The mp world is its own galaxy with connected space and planetary regions. Who needs a map, when you have an entire planet ps: I think I found the crash problem in the server (and the console). More later.