Tarres

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.

No, you can't do that combo. In your example button 2 (or 6) is a modifier. A modifier can't be a selection button.

The Zvezda K55 was an IR missile only. As you can see in the Polish manual, the weapon selector page of the weapons section indicates that the R55 is an IR missile only. And as you can see, RS2U, kh66, nuclear weapons, SPS pods and gunpods were added as gameplay features as Cobra has said.

Have you got Microsoft .NET 3.5 installed? Yesterday one member of my squad had this problem and he solved the problem reinstalling the .NET 3.5

SRS Controls are only for those modules that doesn't allow to export data about radio selection and/or PTT. SRS controls are for: FC3 aircrafts. A-10C and Mirage for radio selection and PTT. Gazelle (not possible to select radio in the Sim) KA-50, Bf-109 and FW-190 for PTT In other modules like the Huey, the radios and PTT are selected through the Sim, so the controls from the SRS are not used.

I thought that it was a bug of the Huey (reported) but it seems that it's a general bug of the map. Neither Mirage or Huey can receive VOR signals in the NTTR. For the Mirage it's only an annoyance due to it has a TACAN and a INS but for the Huey the VOR is the main navigation system due to the only NDB that Nevada has. Thanks in advance and sorry if it has been reported.

The Eagle has 2 sets of AN/ARC-164 so it´s correct. You only have UHF communications.

@toxic You can tune "264" with the V/UHF radio in manual mode. UHF radio only works with presets. No problems here to tune 264 in manual mode. @Panthir. Maybe the server doesn't allow to export data, so DCS-SR will not work.

The F-5E only has an UHF radio (225-399.975Mhz) I don't have any problems contacting ATC in manual or Preset mode. I've binded the PTT to my Hotas and work both, the PTT in the throttle and the NWS acting as PTT when I'm inflight.

I´ve written Zeen and he will investigate the Helios problem. He is using SR&Helios without problems, aside a problem with their ports and their ISP.

Adding the NWS as PTT for the F-5E. New Lua code sent to Ciribob for the next release. Regarding the sound, I´ve to set the "Boost options" in the 50-150% to prevent an excess of background sound, with and without "Radio effects"

Open dcs-simpleradiotandalone.lua and edit line 234 from: _data.radios[1].frequency = 251.0*1000000 to _data.radios[1].frequency = 126.0*1000000

The Huey is fully implemented, so the radio is selected with the radio selector in the sim and the PTT is the one of the sim. The radio buttons and the PTT button in the simpleradio client are only for the modules that don´t allow to export the radio selector and/or PTT data: A10C: radio selector and PTT KA-50: PTT FC3: radio selector and PTT Mirage: radio selector and PTT BF-109: PTT FW190: PTT Gazelle: radio selector and PTT Hawk: PTT C101: PTT All other modules are fully implemented, so the selection of the radio and the "push to talk" are done within DCS.

No problems here. But I ´ve had a similar problem with an app that exports the CDU, MFDs and radios to my iPad. Unfortunately I was unable to solve it, so when I use the app, if I change the plane from the A10C to another plane I´ve to close DCS, close the App and start DCS again to avoid problems with the data export. "Unknown" in the GUI is a problem with the data export LUA(99%).

Simpleradio working with the F-5E. Ciribob has the code for the new LUA.

+1

Ciribob I ´ve sent you an updated google document. I´ve been unable to edit the doc via web. Note: testing a new LUA for the F-5E underway.

R-828...soviet ergonomics... :)

Sorry, I didn't see the post when I was writing. Try to add -- to all the lines in the export.lua except for the line referred to simple radio. Even with the others apps not running, it can be a chance to have problems with the Lua. DCS.log clean? This is strange. I think that you mean "DCS-simple radio log" Edit: nevermind.

Can you try with this Export.lua? It only has the line for the simpleradio. Export.lua