Gaswell

</span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote </td></tr><tr><td id="QUOTE">Unless you do that they will religiously keep the safety's on their weapons.<span id='postcolor'> ... except if you're using engage at will, and give someone a target. That'll override the hold fire order, if I'm not too mistaken.

Never seen anything like that.

Engage at will, dude. That's the only way to go.

</span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote </td></tr><tr><td id="QUOTE">Call me when you guys have coded all that stuff!<span id='postcolor'> Actually, you can easily modify a lot of the AI's behaviour by scripting. To use an example from one of my earlier posts, it is trivial to create a script that forces mounted infantry out of cargo once they go into combat behaviour, then allow them to enter again when all is clear. However, this makes mission- and author-specific AI, which is not necessarily a good solution.

Sorry, no programmable hotkeys AFAIK. With time the command menus become second nature so don't worry too much. The most important thing when handling AI soldiers is IMHO spotting. You can usually spot much better than the AI (unless in forested areas), which should give your squad a definitive edge. If the AI knows all nearby threats and targets it becomes much more effective in combat. The guide in Avon's FAQ is very helpful.

The truck in the first campaign mission. Most excellent.

Shabadu, you gotta get a decent graphics card, preferably a Geforce2 or 3. There's just no way around it. With 1GHz, Geforce2 and 256MB RAM I have a silky smooth ride in 1024x768x32, even with a lot going on. Battlefields? No problemo. Shadow, I must admit that the T23 keyboard is actually quite comfortable. Good wrist support.

Well, what do you know... I'm typing on a T23 right now. Seems like a nice piece of machinery so far. Except for its cramped undersized keyboard...

I though all notebooks had very cramped undersized keyboards...

I've seen the AI use single shots, apparently when firing on targets behind partial cover (inside buildings, peeking over hilltops, etc.) But IMHO you're usually a lot more deadly when firing bursts; maybe the AI feels the same way? My biggest gripe with the AI is that mounted infantry (be it in a car, truck or APC) doesn't immediately dismount when making contact. Instead they stay inside and become sitting ducks.

Currently 1600x1200x32, but I'm reverting back to 1024x768x32 soon. I get a lot of weird warping when I pull higher res than that, especially when there's a lot of objects on screen. Maybe it's my Geforce2, which is about to be retired.

1.40 is a must-have. Previous versions had a serious friendly-fire issue that has now been fixed. The AI has also been tweaked; during my last run through the campaigns I noticed a lot of improved behaviour, both friendly and enemy.

I've had multiple instances of the same script running, without any problems. Just keep your vars local.

I put the charges 55, 25, and 0 meters away from the Cadet mode waypoint marker, and when the last tank reaches the first charge at 55 meters, I set them off. Kills the entire convoy every time.

My favourite has got to be the M16 with M203 or mortars.

That's what the "GUARD" waypoint does; the group goes to the waypoint location and looks for something to guard (usually a trigger with type "Guarded by East/West/Resistance", or nearby friendlies under attack).

</span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote </td></tr><tr><td id="QUOTE">Well.... i dunno this is really an infantry game and NATO got much better small arms <span id='postcolor'> I once ran some tests (with 1.30, mind you) where two 6-man squads move into contact with one another on an airfield runway. Given similar skill levels, an AK74-equipped squad would usually defeat anything except M16s, heavy grenade launchers, or snipers. Turns out that the 3-round bursts of an AI assault rifle would kill much more effectively than the single shots the AI tended to use when firing scoped rifles, or the overhead fire you got from an AI machine gun. So my conclusion back then was that the AI was at a disadvantage when using the new NATO hardware. I haven't tried this with 1.40, but that's next on my list.

@zovirl Ahem... it sure doesn't work the way I said. Car drivers will do a full stop (with "Wait" as status until you get on board), while armored vehicles just continue on their merry way without noticing. I could've sworn I remembered how that one worked. I must be getting old and rusty...

Interesting. Gotta try that ASAP, but Christmas is getting in the way of my game time. Oh well, there's always next year...

Yep, I definately got a CTD while using join and lead repeatedly...

It should be possible to make a bounding overwatch script - the real trick would be to make it useful in the context of the current command menu system, ie. so that only the selected squad members will do bounding overwatch. zovirl, nice work on the commander guide. I wished I had such a guide when I first started learning about the command system. I've even got a remark too. The "Wait for me" command is useful to give to a vehicle that you've already ordered to move somewhere. The vehicle will stop and wait until you get on board, then continue to its previous designation.

SENTRY: The group will move to the waypoint location, then wait there until they spot an enemy. Once an enemy have been spotted, the group will continue to their next following waypoint.

Lock On After/Before Launch, right? I think I remember something from my Longbow 2 days.

"Super AI" could mean a CPU-eating, more human-like AI.

I can't imagine it being too hard to show backblast visually (no backblast damage, please, or the AI would cause mayhem) by adding a simple smoke effect whenever an AT weapon is fired.