Chaplain

He means the vector expansion, which gives six degrees of freedom. I also have that, and it works wonders in FS2004. On the other hand, I never try to "click" items in FS2004's 3D cockpits. I look at gauges while Track IR is active, and I look at lever positions, but I only make adjustment via hotkeys, joystick buttons and/or Game Commander voice commands. The 3D cockpit jumps around a bit to much with Track IR active to try to use mouse clicks. I agree Track IR would be nice in SB, if it was handled like in FS2004, where it is only active in the 3D-cockpit view. So, for example, if one is playing the TC in an M113, it would be active when scanning but it would shut off when aiming the M2HB. If it was active all the time, then it would be a real pain in the behind to turn it on and off.

I would agree with HotTom that AI units should be able to tell when a route is clearly impassible. However, I know of a case where 3 M2's went over a cliff that was clearly marked in their IVIS system and was part of the pre-exercise safety briefing. No one knows why they did it because the PL and PSG both died, along with 3 other crew members. :-( Therefore, "clearly impassible" may not be so easy to define. Regardless, I think that it is the player's responsibility to monitor his units, so I would see no need to give the AI the ability to figure its own way around such an obstacle. Maybe AI units in this situation should give a radio call saying they have arrived at implassible terrain and need guidance? And, of course, scenario designers should test the passibility of routes themselves. If this happens to computer-controlled units, as opposed to player-controlled units, I think it is the scenario designer's responsibility to adjust the scenario until it stops happening. In that case, it is certainly not the responsibilty of the developers to create AI that can sort this out on its own.

With this new forum software, PMs are off by default. That is not typical, and Wedge may not realize it...

Used flight yokes and other higher-end simulator gear regularly sell for just a slight amount less than retail. Based on what I have seen, this gentleman could reasonably ask for anything under $120. As long as he has an agreement to replace a dead-on-arrival dongle, I'm sure he'll get a buyer for $100.

OK - I used all lower case. Thanks, TK.

"Firmware Field Update failed."

Thanks!

Two issues I'd like to see addressed: 1. I want one side to have to hold an objective for X full minutes from the moment they first take control of it. Once they have held it for the required time, the scenario ends. 2. I want one side to be penalized (points, not destroyed vehicles) if they enter a region before a particular event occurs. Once they see the event notice, they can enter freely. (I tried this one, but it doesn't work the way I thought it would.)

Doublemint > gum (Hah - my first post in this silly game! If you get to 4,000 replies, I'll do it again.)

The units I was in used "Black" for the HQ section, not "Alpha," and the platoon colors were sometimes in a different order. My ITV platoon was E Co, 2d Plt, but we were "Red", not "White." Some units are sticklers for going by the SOI, and don't use "friendly" callsigns at all.