drPhibes

Just curious, but what are your sources regarding the HARMs? I have done quite a bit of searching for actual info on this, and all I've found so far is references to wikipedia (which is not a credible source without proper citation).

What exactly is the connection between Bell and the Gazelle? Other than that the two words rhyme?

It does, but the different models aren't sorted alphabetically, so the F-5 isn't grouped with the other F's Edit: just to clarify: I'm talking about the liveries dialog. The edm files are in the coremods folder.

This is pure speculation, but from a sw/hw developer's point of view, moving the open beta version into the release branch does make some sense. More updates are coming for 2.5, and in order to test them out in the open beta branch while still having a mostly functional version of 2.5 available, this is the only practical way of doing it.

Nope. https://forums.eagle.ru/showpost.php?p=1483439&postcount=30

As an affordable (but very good; at least when combined with FaceTrackNoIR v200) alternative to TrackIR, I can recommend the Delanclip. 35$ + shipping.

Nope, it's due to the thermal sensing organs of the Sidewinder (Crotalus cerastes). http://snakesarelong.blogspot.no/2012/09/snakes-that-can-see-without-eyes.html

Because it's a SIDEwinder-based ARM?

The answer is quite simple; pressing the idle cut off switch shuts down the engine when the throttle is at idle. Don't touch the switch unless you plan on shutting down the engine.

https://forums.eagle.ru/showpost.php?p=3408896&postcount=12

Try reducing the Y-axis saturation for the slew axis. And you could try adding a slight deadzone.

It doesn't. As long as you don't have the flashing 1111s , you can use other codes. I don't know which code range they have simulated in the av8, but I have tested 1111, 1234 and 1688, and they all work fine.

No. Source: https://forums.eagle.ru/showpost.php?p=2869238&postcount=28

Make sure that you are in TGP mode, and not HTS (enabled/disable by double clicking sensor select down). Then click the NWS/undesignate button.

I see no logical reason why the two flight director/steering bars should work opposite of each other, so I assume it's a bug.

It works with the TPOD, but not with the DMT (yet). Version 2.5.0.14304.321

The seeker points at the correct area, but the HUD indication is incorrect at the moment.

DMT: * Switch on the DMT using the switch on the center console * Sensor select switch aft 1/2 times until you enter TV mode (not LST) * Point the flight path vector in the general target area and press the TDC down / action button to lock the camera on the selected position. You can then slew it using the slew buttons (but not the slew axis yet) TPOD: * Press the TPOD button on the MPCD menu * Press the STBY button to switch the camera on. * Press the TDC button ( -> TDC = on ) * Point the flight path vector at the target area, and press one of the slew buttons to lock the camera on the selected position. * Slew using the slew buttons (slow) or axis (fast)

Avionics hardware is usually quite primitive, with limited memory and processing power, which some times has impractical consequences like this.

http://www.boeing.com/defense/support/qf-16/index.page 1. Multi million dollar jet 2. Piloted by a human being (remotely)

He hasn't deleted it from all threads yet: Perhaps this is like on the gun forums, where 90% of the members claim to be ex-navy seals...

There are several snow camo skins in the user files.

Just define the pattern manually using waypoints.

Wind direction might be an issue. If, for instance, only RWY 09 on airport X has AWLS, and the wind is blowing from the west ( = RWY 27 is the active runway) the navaids for RWY 09 may be switched off, at least if AWLS works like ILS does (in real life and DCS). I haven't tested this myself, but it's worth checking.

No. The upcoming module has a new 3d model, so the old template is incompatible with the new one.