Tarres

This. And yes, ED RSBN are included in DCS from the first KA-50 iteration as far as I known.

Seems that the old templates for Normandie 1.0 work with Normandie 2.0

Maybe is the same bug that was in the EWR for years. 120 MILES/300 KM; DCS data is coded in Meters, kilograms and seconds (standard MKS system), so 120000 is wrongly traslated into meters, instead of 300000 (meters from miles more or less). If this is the same case, the BIG BIRD values (in this example) for maximum search are coded wrongly, without the conversion between miles and meters. Was reported time ago I think.

Same for the ARK/Radio selector: 'RSI-6K Receive/ARC Switch'

Same here in a non steam installation. After pressing "OK" the mission continues without any problem.

As a purpose or prototype, XF6F-4, I think.

In the mission editor, in the (…)box, you can select the special options. One of them allows you to fly the “old version” nicknamed 2011 version.

Compnullass rose is set by default outside the boundaries of the NTTR map so it´s not possible to drag it around the map like in other maps.

Ok. Tested with Hot Start in the air with the option inertial+gyro in the ME to avoid the INS drift when doing a cold start. Expected: HSI in true heading by default. The magvar is introduced automatically (hot start), so no need to dial it. Selector Up to MAG, HSI card rotates to the magnetic heading. Selector to center, Gyro mode. HSI shows the magnetic heading. On my end: HSI in true heading by default. The magvar is introduced automatically (hot start), so no need to dial it. Selector Up to MAG, HSI card not updating to the magnetic heading so I´ve to dial it. In this example in the Caucasus, the Magvar window is set to 7º approx., so I dial 7º plus, the final data in the magvar window is 14º approx. The HSI card rotates to the correct magnetic headlining, but the value in the Magvar window now is set to 14º instead of 7º. Selector to center, Gyro mode. HSI shows the magnetic heading. Same applies to NTTR, PG and other maps. Maybe I´m doing something wrong. Magvar bug air start.trk

Thanks. I´ve the same issue with magnetic compensation when airbone.

Thanks a lot. Only thing it´s better to have the Self-coord. in the PVI in order to compare with the self-coordinates in the Abris.

As the title says, like in the Mi-8 and the Mi-24, a special option for a working collective brake.

Waiting for your test. Maybe some user error from my end.

When setting the magvar in order to set the MH in the HSI, it´s needed to input the double value of the magvar (2*magvar value). Caucaus, standard mission, magvar it´s about 6º8'. You need to input around 14º aprox to set the correct HSI in MH. Attached track. P.S Maybe related with the INS drfit? Magvar bug.trk

As a land base. It´s something related to the Harrier too, not only the Tarawa.

Thanks. User error. I forgot the L16 vs IDM difference.

Not sure if a bug or user error When a member of your flight sends you a DL AG TGT, the data is received as "Steerpoint 500" (MKTP500) instead of STP71-80. Attached screenshot null

Pause and active pause have been moved to a common binding in the UI layer for all modules.

CR is a recon aircraft; CE is the C variant build for Spain (Espagne: CE) with an ALE-40 integrated dispenser and AIM-9 compatibly. No version of the F1 can deploy 530D, so it´s a stopgap until the 530F arrives to DCS.

Regading the SON-9, yes both LUA files (KS-19 and S-60) have a "depend" line related to the SON-9. So both can fire with and without the SON-9 radar director. There are a pair of new LUAS for the KS-19 projectiles it seems.

It seems reversed as the F1B had a refuelling probe but only for refuel training, not for actual refuelling.

Any mods installed?

Thanks again. I think it´s solved on my end, Stupid user error as you can imagine...

I´ll do more tests. Yes, I´ve done all the indicate procedures. Some user error I suppose.

Thanks a lot! I´m doing some tests but I´m unable to achieve the "light on" release indication. .- Set as CPG .- Assumed weapons control .- Select bombs. .- Set angle and interval like in the data sheets we have. .-Set the counter to on when target disappear from PKI. No light indication... I think that I ´m doing something wrong. Any idea?