Tarres

With the new models of the Snull-300PS, the 64N6 still has the maximun range issue of 160 km instead of the indicated in the DCS encyclopedia of 300km. I think it´s reported. And related to this, is it possible to add the EWR parameter to the definition of the 64N6? Regards. null

1.- In the UH-1H, there is no option to assign PTT to the cyclic (ICS and Radio) 2.- No assignation for the PTT (ICS) for the gunners

Some questions about both helos: 1.- unable to bind VOIP to the control stick in the MI-8MTV2 (solved in my end editing the LUA file associated) 2.-Mi-8MTV2: not sure if turned the "mic" switch (copilot side, upper wall) must enable "hot mic". It enables laryngophone as per manual, so maybe when "on" Hot mic must be available. 3.- same as (2), not sure if "SPU switch" in the copilot left wall must enable some sort of "Hot mic". Regards. Mike

Maybe I am wrong and it´s only in the Viggen.

Attached TRK rsi-6k.trk

We´ve been testing the VoiceChat and we think that there are a pair of bugs. 1.- In the MiG-15bis, the VoiceChat seems to not work. The radio command window doesn´t update the frequency, The kneepad shows that the frequency changes and works for the communications with tower (IA) 2.- In the Mossie, there is no VoiceChat for the T/R1154/5 (navigator position), maybe is WiP? 2.a. In the Mossie the navigator can hear the SRC522. We don´t know if this is correct. Intercom works perfect, always on like in IRL. 1 and 2, Maybe related as both have separate receiver and transmitter radios? Tested in other airframes VC works perfectly, so it seems related with the RSI-6K and T1154/R1155, designed with separate receiver and transmitter. radio sets.

Sorry, yes it worked for a short time as you said. It’s reported I think

The AV-8B is coded like a ground based airplane, so no carrier comms are available for it. If you try to land with the Hornet, you’ll see SC comms so the bug (reported years ago) is related to how the Harrier is coded in order to have standard ground ILS.

The short-long press (like in the Viggen or the Cat) was asked early when the first iteration of the VoiceChat was released. I hope that this option will be available in a near future.

Pilot and copilot radio selectors must operate independently, like in the Hind, so each one can transmit over different radios at the same time. This is a bug that has been present since the launch of the Mi-8MTV2 but now with the implementation of the multicrew has become more important.

No problem here. 1xbtr-80 and 3 soldiers. Embark and disembark work as intended.

Yes. Like correcting the 160km range of the big bird and add the tin shield to the S-300

Unfortunately it must be added in the RPC_5N62V.LUA that is coded and encrypted in DLL in the core files.

Unfortunately, it´s coded in the LUA of the TR radar: RPC_5N62V.LUA in line 17: depends_on_unit = { { { "self", 2 } }, { { "RLS_19J6" } }, { { "p-19 s-125 sr" } } }, In order to make the P-14 to work with the S-200, we need the P-14t added to the "depend on unit" line.

Unfortunately Razbam has coded the Harrier communications like a “non embarked plane” not as an embarked one.

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.

Like in the Huey.

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