Tarres

The sound that we have for now is the "seeking sound". This sound is heard when the seeker head is enabled and ready, approx. 20 seconds after the switch that controls the seeker head is enabled. When the seeker head is locked on a target, the sound increments in tone and volume and the light on the left side of the ASP is enabled if the missile g-limits for launch are correct. Like in the L-39.(Same equipment) This sound, the sound that we have now, is heard too when the radar head of a R-3R is lock on a target. In this case, no changes in the tone or volume of the sound exists to indicate a "Launch autorized". The LA is indicated by the radar light in the left side of the scope and the left light of the ASP. This bug is reported and in WiP stage, pending to implement in a public release, according to the Mantis bug tracker.

Thanks to the team for this great first module and for the efforts to stablish this type of communication with the community. Regarding the "A", or as you say the "M", the differences would be, if I understand correctly: A: manual selection of program and release of CM. SA: semi auto. This is the point that I don´t understand. What´s the difference? Does the "Spirale" system select the program and the pilot "consent" the release of CM? Auto: the "Spirale" suite selects the program and release the CM according to the threat. Not available yet, WiP.

@Zeus, with this implementation, is the Eclair pod recognized as a "Countermesures pod"? I remenber that you said that the team were waiting for a proper "implmentation on the ED side" to make the Eclair pod "fully functional" If yes and I´ve understood the sytem, the amount of CM will be: Parachute equipped: Spirale:112+16. Defined as fixed in the M2000.lua. No changes could be made in the ME. Eclair: 18+16 added to the Spirale, total: 130+32. Defined as fixed. No changes could be made in the ME. Only one thing that I don´t understand is the "Arret" position of the DRM and the ability to use the Programs but no the "Emergency" button. It´s a bit contradictory. It´s great to see how this module becomes better and better.

Excelent as always. Quick question, if DRM is off ("Arret"), "Decoy release" shouldn´t be set as "None" as in the "Panic release" column?

It´s an ED bug. Reported and WiP as far as i know.

There is no beacon to show in the ARK-22 in NTTR, except Mercury, but it is defined as an "Airport Homer beacon" and the function of the ARK-22 doesn't recognise it. It's the same problem that exists with Gelendzhik, Sochi and others in the Caucasus. I've made a little mod to solve this in the Caucasus and the excelent Gospadin "Aditional beacons for Nevada" also solves and improve this feature.

UHF is only AM

Same without CTLD, using the default "embark" and "disembark" orders from the ME and F7 menu in flight. Same applies to the Hip.

@Pepin, you need to comment the first line and turn off the Aries plugin from the TS to avoid problems with the AriesRadio. Simply write -- before the first line. The line will turn green. That indicates that the line is "commented". Like this: --dofile(lfs....)

By mistake I applied the mod "clean cockpit English version"... and no "DCS stopped working" since then, neither loading a single mission or loading a mission via the mission editor. I don´t understand.

Bf109 manual, pg 107. Table of FuG16 operation.

Confirm that the SW position of the SPU-9 in the KA-50 is a "spare position", not operational in the KA-50. So, no SW radio in the KA-50. It´s like the SW position of the SPU-7 in the Mi-8, a spare position. Maybe it´s used in other airframes. SPU-7&9 are common systems used in a lot of airframes. Not all positions are operative in all airframes.

It has been reported in the bug tracker and assigned on 16-03-2016 to Dolphin. Waiting for resolve and implementation.

PM sent. The KA-50 only has 2 radios. The SPU-9 is a standard selector for a lot of soviet planes, not all have all radios.

One question regarding the KA-50, 600Mhz is out of the range of short wave frequencies. SW are in the range of 3-30Mhz. Maybe 6Mhz instead of 600Mhz.

Yes there is a small bug due to the add of the "Intercom radio". It´s corrected for the next release. As a "Hotfix" you can use the following LUA. Sorry for the inconvenience. DCS-SimpleRadioStandalone.lua

The idea is that, when the PTT selector in the Throttle will be "clickable", upgrade the lines in the LUA.It's an easy task.

No, in the ARC-164 , the "VHF FM GUARD" position, it´s a position to receive VHF FM transmisions on the VHF FM GUARD standard frequency, 40.5FM If I recall correctly. As you can see, the MODE positions are: OFF-Manual-Chan (presets) and 2 GUARD positions, AM for 243AM and FM for 40.5FM

Yes. Look at the NTTR mod from Gospadin. But in the Caucasus, the map uses the old definition system where the TACAN/VOR/RSBN systems seem to be binded to an airfield definition. It seems that the system, in the Caucasus map, will change to a more flexible system like in the NTTR and other future maps.

Bugs in the "guard section of the radios" of the lua regarding the Mi-8 and the Huey due to the "reorganization of the radios". The KA-50 lacks the guard channel. PM sent with the afected lines.

Gospadin has an excelent mod that add the decomisioned NDB and other NAVAIDS to the NTTR. It would be great that the NAVADIDS could be linked to the "year of the mission". A mission set nowadays only would have one NDB (Mercury) but one set in the 50-70 would have more NDB, according to the reality of that time frame. Link to the post: http://forums.eagle.ru/showpost.php?p=2676126&postcount=1 Maybe the "selection by years" it could be implemented in the medium term for all the maps.

Clean installation. When I select a Mi-8 to change weapons, the weapon screen doesn´t load. The "skin preview" doesn´t show anything. It occurs in ME and in "Prepare mission". Logs attached. SOLVED. Corrupted config. dcs.log.txt

The ARK-22 works independently from the R-800L, the "ARK switch" is to use the R-800L1 in "directional mode" to point to the radio emitter. But as a "stop gap, it´s the only solution.

PM sent.

Yes, we used it and everyone needs to have it installed. Gospadin, I´ve made a small change in the definition of a pair of beacons to "Homer" to be able to make it work better, to have the beacon listed in the KA-50 right datacard of the ARK channels.