Tarres

Returning to the UH-1 after some time and flying in multicrew, the copilot doesn´t have any control for the landing/search light on the collective. There is no available binding for these controls. I don´t remember if this controls were implemented, so not sure if it´s a bug or not. On a side note, VoIP bindings are not available for the warthog stick (not present in the Joystick Warthog.lua) Thanks in advance.

In Syria, Sinai and Kola there are a few DME stations. DME stations cover from 960 to 1215 Mhz I think. In the beacons.lua are coded as VOR frequencies (108-113 Mhz). In a VORDME station, I can tune the TACAN system to the appropriate Tacan/DME channel and receive distance with no bearing. So it works as intended. In a DME station, I can´t tune it with the appropriate channel. I don´t know if it´s a Map bug or a core base problem, they are the firsts DME stations.

I think that we forget the elephant in the room: the 21 never was intented to be a module. It was a mod from LOMAC 1.1, after that, it was intended to be a separate program with proprietary missiles, bombs, objects... When the 21 became a full module, the first split/legal problem affected the company, and the mod creator left the company (with the base code?). After a few years the company was split again and now I think that only 2-3 persons in a part time job are involved. Any upgrade requires a whole rebuild from scratch. P.D. as @portman said, the L-39 can fly RSBN in manual mode in every map without RSBN stations.

With all the problems that the module and the developers have been facing (2 company splits), the fact that the module started as a Lomac mod (the first one) and with all the old code from Lomac that is in the module, the only way to address it is make it again from scratch.

You can use the RSBN in manual mode (input course and distance in the system)in a sort of dead reckoning navigation in all maps. I suppose that in the medium term maybe we could get a mobile RSBN station like the mobile Tacan.

Thanks to confirm. Yes it’s a bug. Both switches are “hot mic on/off” after reading documents related with these airframes and the radio communication equipment.

Thanks. For us is only with modules in multicrew and only after the second crew member is on the cockpit

As per titles says, ATC comms not working in multicrew with more than 1 crewmember. Tested with UH-1H and Mi-8MTV2. 1st test: only pilot: ATC works OK. 2nd test: pilot ask ATC BEFORE 2 player joins: ATC respond. AFTER 2 player joins, ATC stops to respond. 3er test: copilot joins BEFORE start comms with ATC. ATC not respond. Thanks in advance. P.S. Tested with AH-64DBLKII, same issue.

As per title says. Upper right triangle panel, "laryngophone" switch (mic switch): if set to "on" (up position) prevents the use of the radio and only allows for Intercom communication. Track attached. P.S. It seems, after reading some documents, that it´s a "hot mic" switch between the crew, so it seems a bug. mic switch.trk

@BIGNEWY FC3 problem solved in my end. @12:00 (GMT+2) I´ve launched DCS and no warning window is present. FC3 planes are showing as separate planes, all functional. Module manager advise me to install FC3 module, but all aplanes are functional and present with campaigns, quick missions... etc.

Solved here.

Launched now and I´ve got functional FC3 planes. They are present as "independent modules": A10A, Su-25, MiG-29...etc No "Authorization warning" when launched DCS.

No. Maybe mod issue related.

Yes, until M3 make a 21 v2.0. Very difficult with old the old code from Lomac that the 21 code has. It needs a whole new code from scratch. (Sorry for my English, writing from a mobile)

@skywalker22 MiG-21Bis uses a proprietary system for all the beacons (you can even place a beacon over the sea if you want). Remember that was designed to be a program outside DCS envoirement at first. When it became a DCS module no work was done in order to have a properly functional navigation system. RSBN system was designed and implemented in DCS from Blackshark 1 onwards. The same applies to the NDBs, 21 requires a proprietary beacon in order to make their ARK system to be functional. ARK systems works as intended in DCS L39 (manual) and ARK-15 (Yak-52 with preprogrammed frequencies via ME)

Only UHF.

Mods?

Thanks. Maybe I don’t understood the radio diagram of the uhf set. The “pull DF off” knob gets me wrong.

Solved as per developer indications in another topic.

Ok. It´s a bit strange that a receiver can select at the same time both the "comm antenna" and the "ADF antenna". Thanks.

Same here. I think it is related with the “active window”. Sometimes I have to “press the mouse left/right click” anywhere in the cockpit to make dcs the active window in order to close the manual or something related with the HBUI

No. Only with F10. Some training missions have this bug.

Minor bug or adjustment in the WRSC panel. “ALT” or “RELEASE” placard illuminates to indicate what mode is active. Each mode is related to a release mode: .- ALT for the Offset/TGT/AGM-45/TGT-LABS. The ALT placard illuminates to indicate that the WRCS entry for the Alt/Release is in ALT mode. .- RELEASE for the LAYDOWN mode. The RELEASE date placard illuminates to indicate that the WRCS entry for the Alt/Reiease is in RELEASE mode. As per official docs. Thanks in advance.

I wonder if a stopgap could be to remove the lines that in the Lua file declares the number of chaff and flares associated to the object. This only could be done and tested by the developers. If it works, an additional entry for an “IA 21bis with ASO-2” (only flares) and another for an “IA 21bis with the POMIG Yugoslavian Pod” (the one in the game, not adopted IRL) could be declared in the sim.

Yes. It’s solved with the June 5th update.