Supreme Cmdr

Congrats!!!!

Cruiser, check your email. Below is a 1.00.11RC1 patch with this fix. It is not an official patch, so use at your own risk. Download the file, copy it to your game folder. Backup your existing UCAWA.EXE file, then run the self-extracting archive. EDIT: file removed I also included a saved game which shows this fix. Unless you use the invincibility cheat, you won't last more than a minute or so. Oh, and this saved game will probably rip your graphics card's head off and piss down its neck. In other words, unless your system can muster it, you're gonna have a bleeder on your hands. [ 01-04-2006, 10:45 AM: Message edited by: Supreme Cmdr ]

Well, I can't protect a D2D version, sorry. So you just have to wait for the official patch which should be out sometime next month. ...actually, I can just send you the StarForce version executables and a CD-KEY for it. Just be sure to backup your UCAWA.EXE and UCAWAMP.EXE files (the D2D versions) so that you don't overwrite them. Just a sec....

quote: Originally posted by Grimm Spector: so I go buy it anyway, just to give it a shot, even though that first IA mission seems to make no possible sense, and discovered it has the same problem the older ones have, three problems that I encountered. You clearly have no clue what you're talking about. You obviously installed the game and played it, without spending any time reading the manual or playing the tutorial. The game AI - the most advanced anywhere - isn't and never was stupid. If you knew how the game actually worked, you'd know that. If a ship take impact damage and a pilot gets injured enough, they will die. Nothing to do with AI. Pilots will take damage if they are inexperienced. Intruders usually come from cloaked ships. They only beam into your ship from the current region. Nowhere else. You have no business running anything in the background when playing a game. Please don't send me any bugs reports (or any further PMs about your mad coding skillz. I don't care. If you're a programmer, go write your own game) because anything and everything is already fully documented.

quote: Originally posted by Cruiser: I don't know if your fix was general or only for the Megaron, so I post this if it helps. I will not post any more investigations of ship turrets unless you want me to - don't want to be a pain What I did is not ship specific; it is a global revision which should affect all ships. In 1.00.05, the 1mm margin of error before a collision (from turrets against their own ships) was too low for some ships. So I have increased it to 2mm and it seems to work. I haven't released a new patch in a while, mainly because it is a pain having to release different patches for different versions (Starforce, Direct2Drive, TryMedia); especially since I have no control over when the other services will protect and make their patches available once I give them the unprotected files. Which version of the game do you have? The BMT Micro (Starforce) version? If so, I can release a new EXE for you to try out.

Weird, I must've missed that post Denny.

My games are all CPU bound due to the AI. So, the CPU and memory really have to be up to snuff. If you're getting slow and/or bad performance on the planet, then the problems are due to the amount of processing, since the planetary engine requires more resources than space. Have you tried turning off all options for the planet to their lowest settings? Note also that UCG uses character models with a LOT more polys than those used in UC. In fact, the UCG character models are based on the UCAWA versions, but with lower poly counts.

LMAO!!! Serves the little rotter right. Kids these days. No respect whatsoever. quote: Selling My Kid's XBox 360--$100 My kid has been an absolute terror for the last month. He has been demanding more and more from my wife while constantly pestering us to give him his X-box 360 early so he can play it. Last night was the last straw when he kicked my $2000 stereo system after I refused to give it to him early. It is an X-box 360 system. It has the console, harddrive, a couple of cables, and some sort of little headset or something. So we have decided to get some revenge this Christmas. I will need to keep the box. To purchase this system, you must be able to pick it up at my house or at work during normal hours. Call in advance so I can get the wife to take the kid out for a drive or distract him downstairs. I am asking $100 cash. I will also need you to bring a bag of charcoal so I can fill the box up with. Let me stress again that you will get the full contents of the box-the 360, controller, headset, those cords, etc. YOU WILL NOT GET THE BOX, as we will need it along with the charcoal for a little x-mas surprise. I would prefer that this goes to a kid who deserves it and treats his mom nice, but I will sell it to anybody just to get rid of it. If nobody buys this by christmas eve, I will just go and toss the contents of the box in a dumpster.

Why don't you download the freeware copy of BCM first, before going out and spending money on BCMG? Check our downloads page for the links to it. At least then you will know how it performs. If it does well on your laptop, so will BCMG, since they use the same engine. btw, the reason you will get crashes on the planet is if that card does not support pixel shaders. Since it is a laptop chipset paired with a crappy CPU, it is highly unlikely that it has the required pixel shader. Also, the demos are vastly scaled down versions of the game, though use the same kernel.

You didn't miss it. It was in the Area51 section where the problem was first reported. So I moved it today into the general tech support section.

Yes. The processor is crap. Anyway, there are one or two people here running the game on a laptop. Let them post their specs so you can compare. But your system is borderline.

Read this

Someone reported that some of the Megaron turrets weren't firing and I have traced it to the same problem tweaked in 1.00.05. So I've tweaked this calculation further and it seems to work fine now. Will roll it into the next .11 patch.

There shouldn't be any difference in how they operate. There was a problem in UCAWA in which the new collision detect would reject an op and resulted in the turret not firing. I'll run some tests and see if there is something else going with it. The turrets perform the same on all ships (e.g. try the Firestorm). So if there is a problem with one ship, then its probably related to the position of the turret vector in that ship.

Your notebook does not meet with the minimum requirements for the game.

Infinium Announces Lapboard, Reveals Financial Problems

Everything I've read about it says that its rubbish, pointless and gory beyond belief. Why would I want to go see it?

http://forums.xbox.com/1235568/ShowPost.aspx

uhm, IGN owns Direct2Drive

quote: Originally posted by Grayfox: lol how much "political nonsense" is there? Oh, just the usual sh*t about who owns a particular piece of mud, dirt and particularly desolate plot of land somewhere on a map. And the usual debate about that whole an eye for an eye farce (which doesn't solve anything) that has been going on for God only knows how long now.

Yet another controversial Spielberg masterpiece. Ignore the political nonsense and just go see this thoroughly entertaining movie. Not a single dull moment in its 2hr 44min span. I plan to see it again before I dive for the DVD 10/10

Just a reminder that Playmod and PTEStudio (from the GBS tools) is not compatible with the IGN and TryMedia download versions of UCAWA and UCG, be due to the copy protection (in the game's INI files) used by those services. EDIT: I'm going to get in touch with these two parties to see if they will protect these tools. If they do, I will make those two executables available for download. The other tools will work just fine btw. [ 12-26-2005, 07:26 PM: Message edited by: Supreme Cmdr ]

Here we go again.

I have recompiled it for both UCG and UCAWA. Check the downloads page for each version. [ 12-26-2005, 09:01 AM: Message edited by: Supreme Cmdr ]

You will get this if you have been tinkering in INI files. Don't do it.