Tarres

Short answer. The NDB and RSBN in the 21 are leftovers from when the 21 was a Flaming Cliffs unofficial mod. RSBN navigation has been coded in DCS from the beginning (Ka-50 version 1) but the old code in the 21 has never been updated. Same for the ARK-10 operation. Unfortunately only a rewrite of all the code related to the systems can solve this.

Same here. Six to eight seems to be the limit to achieve stable use of the VC. But in the Aerobatics server, we´ve achieved a stable use for 8-10 in one of our tests.

Ok. I see it now.

Not a bug. It´s a solved bug. Pilot and copilot can use different radios. So each one can select the radio in use in each position using the SPU-7 selector in each crewmember position. The bug was that the SPU-7 was synchronized.

Yes I known, I´m talking about the sim.

It seems solved. Thanks!

Wait... The Big Bird provides more coverage than the Tin Shield? In the ME both have the same coverage (-/+ 10km)

It seems still bugged. Now I need to dial 0º in the magvar window. Attached TRKMagvar bug air start 16-11-23.trk Edit. I barely remember how to use the MH/DG. I´ll more tests tomorrow.

Last test with 9 clients was a curious failure. I, as a server, only saw 3 other members but the other 8 were able to saw and talk each other without problems.

2.- Yes, this switch. 3.- Attached image.

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.