v81

This just does the same as the keyboard keybind, toggles between the 2 modes. The desired outcome is that when bound to a switch the RWR is silent on one position of the switch, and sounding on the other position. If i use the existing binding i have to move the switch on (seen by sim as button down) to change modes, and to change modes again the switch needs to be moved to off and then back on again. Thrustmaster Warthog for example, when bound to the EAC switch the RWR is on but in silent mode when physical switch is in the off position, and in audible mode when the switch is on the on position.

Confirming and adding to this. Ka50-2, Ka50-3, Mi-24, Mi-8 all affected. Tuning light should go out after tuning process is complete. Process should not be instant, but rather take a second or 2 depending on how much adjustment is required. My (modern) real world radio with micro processor controlled internal tuning unit is relay based and takes 2 seconds at most, 70's soviet tech might have taken longer, but having it take a random period of time up to 2 seconds is fine for a sim. Additionally, the Mi8 manual incorrectly identifies the tuning button as an automatic gain control button, and skips over describing the tuning process. Pg 115-117 The Ka50-2 and -3 Manuals correctly ID the button and describe the process. Ka50-3 Pg 6-77 near top of page.

Looking for a hand setting up a switch to handle the SU-25T SPO-15 mode select. The default is [R Shift]+[R] The keyboard\default.lua has this line... {combos = {{key = 'R', reformers = {'RShift'}}}, down = iCommandChangeRWRMode, name = _('RWR/SPO Mode Select'), category = _('Sensors')}, I think I'm part way there adding this to joystick\default.lua {pressed = iCommandChangeRWRMode, name = _('RWR/SPO Mode (HOTAS switch)'), category = _('Sensors')}, The above results in unpredictable behaviour, as if the button is being mashed cycling the SPO mode 20 or so times a second. Working from the PDF guide but I'm struggling to get over the line. Any suggestions? Have not seen a lot of examples for aircraft without clickable pits.

Hasty? You either A) thought it would pass un-noticed, or B) didn't care enough to inform your customers. Making this post you just made 24 hours early would have put an entirely different spin on this. THIS is why i wait sometimes a year or so before buying modules.

Excellent... was it not worth adding to the patch notes?

Sorry i missed your 10th birthday Mi8 bug. Clearly a forgotten module!

Not long now and it will be 9 years. But we have clouds right? You can put lipstick on a pig but it's still a pig.

If the purple text was your edit i much appreciate you took the time to do that. On you're initial post i was still unsure how I'd gone wrong as i had the switch under the sight set to AA guns. The last part of your post i think explains it all... i was fiddling with the DG / DM switch. Both images in my OP were captured while the sim was paused. I highly zoomed the in pit view to make sure the reticle and target were clear, so maybe that is throwing you astray. The distance we seen in the pit screen cap is as shown in the F10 map cap, 1.7nm +/- any error on the bearing/range line i drew on the map.

Sit in the pit and follow the training mission exactly as the voice over explains it, assume no prior knowledge. It doesn't work. If the training mission is missing an essential step then it clearly is broken.

Have been wasting time on the startup training for an hour now and have come to find this. How is it that it can be broken for a year and not get looked at? If you're selling this module then it should work. At the very minimum a clear and concise Errata document should be available for each module clearly stating known bugs.

Gunsight range indicator seems to be off my a massive amount. Paused the sim mid flight to check and if my understanding of the sight is correct that's supposed to be an Su24 at approx 1100ft distance. Switch to the F10 map and i measure 1.7NM or 10,330 ft If my understanding is correct it's not out by just a little. Rather it's out by an order of magnitude. Could be very well an extra zero got lopped off, meaning sight bars ~1,100ft = distance of 11.000 ft. Just getting to know the F5-E and this is making it hard. Also sight reports in range if i understand the dot correctly, but really??? In range at a map distance of 1.7 miles on an A-A target at 300 kts?

In which decade? 8.5 years old and counting.. Wouldn't be a big deal if it were purely cosmetic, but the gunsight gets broken/lost along with this bug.

No... Just no. You don't get away with making this about me posting a bug report in the wrong place. This is concern about EDs lost direction where they're talking about clouds and other things no one cares about.... yet again. Multiple bug reports dating back to DSC v 1.4 (correction, DCS v 1.2.7) exist for the Mi8 issue. One point two.... Let that sink in. Back then multiplayer and single player were separate executables. 8 years, coming on 9 if I recall. Bugs properly reported, tracks, screen shots, video, detail. This is one example of hundreds. I have no interest in new clouds when core game play is broken. Your lack of concern shows your lack of intimate experience with DCS so excuse me if I don't take you seriously.

I love how it's always xxx can't be fixed because that is a task for a team working on some other unimportant rubbish, or it isn't related to the team working on this. That excuse doesn't fly.

I'd love to see evidence of this work. Meanwhile there are hundreds over bugs older than 2 years that remain ignored. NS430 (a paid module) is broken on the Caucuses map (5 years). Mi8 hardpoints bug was carried forward from DCS version 1.x and still remains ignored. ED have only proven to me that they can not competently triage bugs and treat paying customers like paying customers.