Supreme Cmdr

quote: Originally posted by Spuzzum: A bit late, but what I meant was that the game would be locked up. Not crash-wise, but I wasn't able to click on the menu nor was I able to use any keyboard commands (since those were disabled). ...and your point being??

quote: Originally posted by JJ: i know this is unsupported but nebody else getting ctd's up the wazoo also? Its just the first port, so there are some kinks in it.

quote: Originally posted by Snark: I've found beaming down marines to be almost useless unless you land them _very_ close to some hostiles and issue the SAD command. Otherwise, they tend to stand around motionless (this is after being "prepped"). -S They are not super human - and I've mentioned this before. If the enemy is not within range, they won't do anything. The same works for the enemy. This is not some game which tosses out enemies based on some scripted trigger. There is real AI at work and they're not stupid. If you drop your marines out of range of the enemy, as in most tactical games, you have to then give them marching orders or direct orders (SAD, strike etc).

quote: Originally posted by Brian1: Odd. Well it's not a bug then. Just strikes me as odd in that playing a Military career at one of my own side's bases if your system is at 0% rather than 1% they won't provide parts. It has nothing to do with the integrity of the system. Have you not been paying attention?

quote: Originally posted by Rico Jansen: The trick is there's something missing in SC's recap of the procedure. ] How can it be my recap if I'm not the one reporting it. What the hell are you talking about? What'd I miss?

quote: Originally posted by Captain Dread: I was watching my BC and a fighter in external view a few times, and it seemed to me also that AI controlled guns sweep in a line across the trajectory, pause, then do it again, never actually keeping any sort of sustained fire, but instead just strafing/sweeping. Doesn't really bug me, just a comment supporting SS's observation. ...and the issue is what, exactly? (I must've missed something)

quote: Originally posted by Skeletun: I cant seem to find this in any other forum, nor does it appear in the FAQ's. Thats because it is unrelated to BCM. As such, you are on your own.

Driver problem. Nothing I can do about it. Either use Detonator Destroyer and remove the nVidia driver and re-install it or just try previous drivers. And why is this in here? There is a video thread. And if you go fiddling around with settings (e.g. getting rid of your hardware acceleration altogether, as you state), you are on your own. The FAQ does NOT tell you do to that. So, you had better uninstall and start from scratch, as indicated in that other tech support topic showing you how to do that. [ 12-29-2001: Message edited by: Supreme Cmdr ]

To increase the AI for all officers, stick these in a batch file echo Setting all officer AI to 100 playmod set officer 1 ai 100 playmod set officer 2 ai 100 playmod set officer 3 ai 100 playmod set officer 4 ai 100 playmod set officer 5 ai 100 playmod set officer 6 ai 100 playmod set officer 7 ai 100 playmod set officer 8 ai 100 And if you want to be sure that they are on-station, add these. Note that the 'as' keyword will be changed back to 'assignment' in the next version. echo Setting all officers to ON STATION playmod set officer 1 as 744 playmod set officer 2 as 744 playmod set officer 3 as 744 playmod set officer 4 as 744 playmod set officer 5 as 744 playmod set officer 6 as 744 playmod set officer 7 as 744 playmod set officer 8 as 744 [ 12-29-2001: Message edited by: Supreme Cmdr ]

quote: Originally posted by Cmdr Nova: Back from vacation!Hehe.... Playmod = my first actual first-hand test of the RANDOM!!!! Meaning what??? Did you actually use it?

quote: Originally posted by Jigoku San: DON'T USE set cheat 1 (the set all crew ai ect to 100 oneoh and some reason my bridge always gets knocked down to 50%... haven't figured that one out yet... Will look into them both. I actually noticed the secone one last night myself when I built and tested it.

Here are the correct values for the 'assignment' keyword (playmod.txt line 223). This correction will be in the next version of that text file. For now, cut and paste into your version. code: assignment 744 (on station) 841 (transporter) 858 (searching) 860 (medibay) 861 (detention hold) 879 (prep for combat) 745-760 (FC1-16 pilot) 761-776 (FC1-16 co-pilot) 842-857 (SC1-16) 883-898 (OC1-16) [ 12-29-2001: Message edited by: Supreme Cmdr ]

quote: Originally posted by Epsilon 5: /me whistles while looking in the sc's direction Search and you might find better. Don't worry. I saw that earlier and am not going to say anything. Wait until the saved game authentication check kicks in.

quote: Originally posted by SmileyMan: I watched the whole thing through Tacops, and I just can't believe how cool this game is. It just gets better and better. ...now just think: MULTIPLAYER And just wait until the NPC's SA (Situation Awareness) is beefed up and they start to make use of dropped/switched weapons, DJPs, supply stations etc (in some pre-mp patch update coming soon), then you'll see. [ 12-28-2001: Message edited by: Supreme Cmdr ]

Pugwash, there are some errors and old data in most of your files at that link. e.g. [*]Tradeing has the incorrect spelling on one page [*]Moon is not a valid Navitron target (since its in the same Earth space region as the planet Earth [*]Some of the race/alliance info is incorrect [*]Some of the launch base names are incorrect You might want to go over that data again, fix some of the formatting issues etc.

yeah, yeah JJ. Now fix that post.

quote: Originally posted by Jerold Keenan: Really? Well, i'll work all this out with them... at least they haven't taken my money and I can still cancel the order (They don't take your money till they ship the game!). Yes. Really. This has been a known fact for almost a year. You can only order via BMT Micro for International shipments.

I have released the first BC3K to BCM port of the Playmod cheat. I also included a batch file which sets some cheats. Don't forget, cheats are UNSUPPORTED. So, use at your own risk.

Wrong thread.

quote: Originally posted by Skeletun: Another issue/question. In version 1.0.02 The SFM Jetpack thingy was patched. But on my system it never worked for SFM's but did work for the AE. I upgraded to the 1.0.03 and same thing. AE has the JetPack X looking thing in space. And other SFM's have the 1/2 AE Model Jetpack. Recently upgraded to 1.0.04RC1 and same thing. Before each upgrade I Uninstall, download patch reinstall, apply patch (yes I applied .03 followed by 04RC1 on the same install. I've noticed this with both A new Commander game and the SFM Instant action. Is this a problem with my system or is something missed? My system stats have recently changed...Windows XP w/512mb Ram..all else the same. I'll change that soon as I find the instructions in the forum somewhere. Reproduced in the TA SFM scenario. Seems to be something with that script. Am on it. Thanks!

quote: Originally posted by Epsilon 5: You already said that if the host-computer quitted the game it was over. Is that still true? Yes. And don't confuse public and 3000AD hosted fleet servers. This distinction was made almost two years ago. Yet you're asking me this; again.

quote: Originally posted by Snark: Though I'd still humbly suggest packing opposing mission-zones a little closer together in future revisions -- for people who like more old-fashioned roll-in-and-fry-the-bastards-then-leave-before-they-know-what-hit-them stuff. Thanks for your replies! I can't. If I did, they'd detect and attack each other - bringing your system to its knees in most cases. When I placed the mzones on planets, I did that carefully so that they were reasonably beyond each other's radar range. Even in some cases however, units with long radar ranges will still detect hostiles and attempt to go there - even attempting to cross oceans in some cases. One of the things I'm going to do in a future update is prevent units from leaving their immediate mzone area.

quote: Originally posted by Steve Schacher: Or am I totally off-base without enough empiracle evidence to back up my observation (it wouldn't be the first time, huh?)? Yes. You are.

quote: Originally posted by Captain Dread: Ok, here are two problems I found I slammed my firestorm into the surface of a planet after launching all my shuttles, and was heavily damaged. I got out of the ship in FP mode, and ordered a shuttle to land near me. It landed. I walk up to the shuttle and I end up being able to walk through the front half of the ship, and am unable to land on top of it with my jetpack. I get into the shuttle fine with that board/dock/get into command, then I try flying my shuttle into the firestorm. I keep flying straight through it, no damage to either ship. I flew every way possible through the firestorm, through every area, almost every angle, and there is NO collision with ANYTHING or damage. Sorta ruined the realistic aspect of the game. Can ya fix it? I was on Polaris II (in case you need help reproducing it) Works fine here And I can't fix what I cannot reproduce. So please don't ask me to fix anything. I have my own priorities and they have nothing to do with yours. And if something like that ruins your impression of the realistic aspect - don't do it. Simple I think. ps: The next person to post in these threads when not running the current version of the game is getting (a) the post deleted ( banned from the site. I guess everyone seems to be forgetting my LOW TOLERANCE rules. Take my advice. Don't. [ 12-28-2001: Message edited by: Supreme Cmdr ]

The damage is propagated on the entire ship. You do take damage but it will depend on your speed of impact. If the damage is too small, you won't see a change. And if you have shields and armor, why would you take damage? You guys do know who about shields and armor, right? right? If not, go read the manual and quit spamming my threads.