slug88

Yeah, I believe it's completely incorrect, but I haven't done enough testing to say so with absolute certainty. And outside of that post I've never heard of anyone finding a solution to the wingmen problems. By the way, my guess as to why this hasn't been fixed, is because at some point ED completely rewrote their wingman code for DCS:A-10, and rather than fixing an obsolete system they presumably decided to just wait until the DCS:WH/DCS:BS compatibility patch to update the BS system to the current standard. Of course this is all pure conjecture on my part :).

Completely new and vastly better sound engine, improved terrain graphics, and fixes to various small bugs are among the reasons I recommend updating.

I read this forum very regularly, and in all my reading I have never come across a wingman issue in 1.02 that wasn't already present in 1.01. Also, see this thread: http://forums.eagle.ru/showthread.php?t=54035

That's where airmanship enters the equation :D.

Slewing the Maverick onto target is rather easy if your velocity vector is pointing at or near the target. In other words, pretend you're on a super long range gun run and start flying directly towards that enemy tank from 10mi. Slewing and locking the Mav on him will be trivially easily as soon as you get in range, no TGP or SPI's required.

Wingman AI is the same in 1.02 as it is in 1.01. In fact it was the 1.01 patch that broke wingman AI. Therefore, if you want fully functioning wingman, you'd need an install of 1.00.

You're probably the first :).

If possible, upgrading to Windows 7 (or Vista) would give you a substantial FPS boost.

They aren't? http://saitek.com/uk/down/drivers.php ftp://ftp.saitek.com/pub/software/full/Saitek_X52_Flight_Controller_SD6_64.exe (64bit) ftp://ftp.saitek.com/pub/software/full/Saitek_X52_Flight_Controller_SD6_32.exe (32bit)

SimHQ review: http://www.simhq.com/_technology3/technology_174a.html

Sure there is. This way takes a few steps, there may be others that are simpler: 1. Using the TAD, set bullseye as hook 2. change cursor to HOOK:CURSOR mode (displayed direction is from hook to cursor) 3. move the cursor to match the bullseye call 4. set markpoint at cursor, hook markpoint 5. set TAD as SPI And now you've got an SPI at the bulls call. You could even eliminate the first step if there was a BULLS:CURSOR mode, but I don't recall there being one.

Probably because the SA-19 is not radar guided: http://en.wikipedia.org/wiki/9K22_Tunguska#Missiles So it seems the Tunguska uses its radar to detect you, but the guidance itself is by SACLOS.

That was a lot of fun to watch. Make more :)

I like this :D

Only problem with a Cold War Turned Hot scenario is that we have the A-10C, which was first deployed operationally in 2003, and which would be very out of place over 1980's Germany.

Hung stores are probably your own fault :).

As far as I'm aware this is already implemented in the current beta. Or am I completely mistaken?

Looks more like Flanker 2.5 to me..

No voices in the current beta. Presumably we'll have them in a future beta.

It works for me and many others. I don't see anywhere in the FAQ where it explicitly says it can't be mapped. How do you know mapping it to the keyboard isn't working for you? Are you seeing the EAC warning lamp remaining lit after activating it?

Actually there are less than 20 questions on that FAQ page (of which yours was one.)

Please read the FAQ before posting about beta issues: http://forums.eagle.ru/showthread.php?t=58400 (This issue has been posted about dozens of times already.) To clarify: if you map the EAC switch to your keyboard/joystick, you should be able to turn EAC on and off. The switch inside the cockpit won't move, but you should see the EAC caution light on the right hand caution panel disappear.

Yep. You're not reading the FAQ :): http://forums.eagle.ru/showthread.php?t=58400

Maybe in game, but surely not in real life.