Break

Still broken in today's patch

Here's a pic:

It's a problem with all aircraft right now.

The red NAV lights cast a yellow/greenish reflection on the ground at night. Tested on the newest open beta with a gamma of 1.3. Also DIM/BRIGHT option needs to be adjusted for the 2.5.6 lighting, currently very little difference. DIM should be way less visible during daylight. Would really appreciate it if this module got a bit of love before multicrew :) Thank you!

I have this problem too, latest Open Beta, tested on both Nvidia 445 drivers. i5-4670K @4,4 GTX 1070 16 GB of RAM

As detailed in the declassified NATOPS, a mode 3 code is enterable by pressing the IFF button until XP shows. Could this be implemented in DCS:F18 so we can squawk over SRS?

Prog 1 drops 6 flares in a pairs of two with an interval of 0,75 seconds. Prog 5 drops 3 chaff in single with an interval of 0,5

1) if it's between the X52 and the X56, go with the X52. I heard the X56 struggles with build quality and has poor ergonomics. If you do decide you might consider something else, take a look at Thrustmaster. Especially the T16000M and the TWCS are excellent value. (And i'm usually a Logitech fanboy) 2) Considering you've already flown warbirds, you have a better understanding of flight dynamics than most beginners, so really you should take the plane you're most interested in. You might be able to get the fullest potential out of the F-5 quicker than the F-18, but that's just because the latter is way more complex and versatile. All said, the F-18 is an easy aircraft to fly, so I'm pretty sure you'd have no problem with it.

I've had the same issue happen to me aswell with GBU-12s.

I can confirm this. If you forget to set your flaps and take off, the hornet will pull up violently and will require a good amount stick input to somewhat stabilize. Trimming it out is possible though. My knowledge isn't enough to say whether this is a bug or a feature. Maybe it has something to do with T/O trim not being deactivated automatically after takeoff?