Ian Boys UK

TIC = Troops in Contact Blufor = yes, friendlies Opfor = yes, opposing forces, baddies DC = Danger Close, doesn't refer to enemies close, it refers to dropping indirect fire (artillery etc) very close to your own troops such that they might be at risk. For example, you might initially fire further then move the actual impacts slowly closer rather than risk a drop short hitting your side. Call for fire = yes, often starts with how many tubes you want to fire, such as "Fire Mission Battery" = 6 guns, Fire Mission 3 batteries = 18 etc. CFF can be explosive (impact, delay or air fusing), smoke or illumination. Also pattern - stretched out along road or clumped at a bridge/chokepoint etc. CFF naval = yes, used in Falklands etc FAC in old speak, JTAC these days.

Jester has stopped talking during dogfights. Bandits x2 close, ACM cover up, Aim9 selected. No bandit calls or speed readouts any more.

Thank you! User error. It works properly when done properly. Sorry.

Here's a track. Same problem. I16 wheels.trk

My wingman (AI) taxies out to the runway, pauses and gets chocked under his wheels on the runway. Not realistic or necessary.

After take off, the wheels won't come up beyond the position shown. Not overspeeding. Every time the same. The tube in the cockpit shows full retraction.

Looks fantastic!

Thank you for fixing the padlock so fast. Really appreciate it! Please could you do it for the Phantom too? It would make such a difference.

Unfortunately the padlock keys don't work in the FF Mig-29, joining the I-16 and Phantom. As your team is core DCS and you already have them in the FC3 Mig-29, please please add them. I don't use headtracking and they make all the difference to the enjoyment.

OK, someone on Youtube says Ekran needs to be tested before engines are on

I really appreciate that since the beta Wags showed you guys removed the flashing HMS graphics. Thank you for listening to the feedback.

OK I have found that the AFCS start up takes control of the stick and deflects it. So the way that works for me is to completely let go of the stick while it's going through the start. I can imagine a FF stick might be an issue? but I don't know.

Ekran Fail track Mig29 Ekran Fail.trk

I imagine it might be user error but ... 1) Can't get the Ekran to test and work. Says Ekran fail on the main Ekran screen. 2) I've only once got the CAY / AFCS to work and thereby activate the Damper. Works fine in Autostart. I think I'm doing the same thing each time?

I have once got it to work but only once, and I can't tell how/why.