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.

I don't have an autoexec.cfg in that location. Is this a file that normally exists, or one that is created by the user in some cases such as this?

Figured that might be the case. Given how many changes by ED affect missions it must be hard work keeping them in a state that you intend them to be played in. In some missions are the engines also supposed to be worn to the point that taking off is a significant challenge or is the suggestion elsewhere i read that the wear factor might have been amplified by a patch possibly accurate? I'm split on the idea, i do like the challenge of operating an airframe that shows the characteristics of age, and also the challenge of weight and high altitude operation. Just seemed a little tricky. I'm turning over the idea of writing a guide for this campaign, not spoilers, but rather a written tutorial on how to use the different navigation and weapons features of the Mi8. How to use the 828 for navigation is not covered in English documentation (or i could have missed it), as well as bombing, also not documented well. I didn't realize that bombs had their own separate weapon release to all of the other weapons... that caught me for half an hour. I don't know if i mentioned it, but i don't think there has been a campaign I've enjoyed more than this yet. It's been great. Also, forgot to mention... night missions are great too.

Negatives first... First major hurdle was probably the fog. I don't know if this was created before the new weather engine or not, but there are a few missions where we have to follow rivers and so on and it gets really difficult, unreasonably so. I like a challenge, but this was too much... maybe dial back the fog a bit. Have attached a screen cap, river is between mirror and cockpit window, max speed was ~ 80kM/h. Some triggers are difficult to find. The one where the player uses direction finding to search for a radio signal can be difficult to trigger. The mission where bombs are used, it's not stated so, but all bombs need to be expended off the helo to progress the mission. I did the bombs one several times killing the required targets with spare bombs left over and it would not progress. Sling loading (not a fault of the mission creator) Seems be difficult to find out what parameters are needed to be met, not a lot of documentation on this. Some long waits for loading Leaves you wondering if something isn't triggering right. Maybe shorten loading times a little or include some dialogue to inform the player that things are progressing. Something like "Almost loaded" or "Not long to wait" or something. Weak engines in some missions I heard that engine wear / engine de-rating might have changed in a patch. There are 2 or 3 missions where it is extremely difficult to get of the pad. If there have been changes then it might be more difficult than it was originally designed to be. Not impossible, but very much a challenge. Positives! Wide and varied tasks! There are so many different things to do, and different skills and systems to master in this. You make use of... Doppler nav ARK-UD nav R-863 VHF / UHF for comms R-828 Low VHF for comms and navigation ARK-9 ADF for nav --almost forgot to add -- Nigh operations with the old NVG's You literally get a chance to try every possible type of nav the Mi8 has to offer, and it feels practical Excellent work i think. Weapons, some missions will call on rockets, some missions cannon, some will use bombs and even door gunners get a go. Plenty of ferrying, pickup, put down in tight and sometimes interesting place. Many missions include accompanying AI, in one case you need to signal them with your signal flares... another feature of the Mi8 put to work. All in all well crafted, and an opportunity to truly master every part of the helo. Have done about 5 campaigns, maybe not a lot, but this one does stand out as being great, especially for covering many systems and tasks. Thanks!

Came here for similar issue... I killed all 3 buildings with 4 bombs used / 2 bombs remaining, mission would not progress. Ran it again killing 3 buildings with 3 bombs and still nothing. Now just come here and find i need to expend all ordinance for the mission to progress. If it needs all of the bombs to be used it should say so, seems like my last run would have been a win if I'd tossed away my remaining bombs. Frustrating to know i quit and missed a potential win. Trigger either needs changing or briefing needs to mention using all bombs. It's very possible and reasonable that someone would run into the same issue.

Wonder if it might be worth creating a standardized test mission that we can download, test and return our before / after notes? Would also be a way to ensure that the mission consists of an appropriate mix of assets presently with and without LOD's, something like what might be seen on a busy online server.

2 pieces there I totally agree with. On a multiplayer server with a dozen users and moderately complex mission in hitting 98% system memory. I have a 5800X, 32GB CL16 3600MT/s ram an RTX3070 a decent SSD. There is no way I should be struggling with performance yet I do. For those with VR I'd like to say I don't know how you do it, but it looking like you're struggling to do it at all. I've got just under USD$500 worth of modules I'm looking to buy on hold due to poor performance from ED (and growing as more interesting aircraft release). Change my mind.

This was a real challenging one, probably due to the lack of crane / sling experience i have in DCS. It was more a problem of understanding what was required than it being a piloting skill. I did find a feature in the bindings that shows a screen that helps with locating the cargo for pickup, and locating the dropoff location. I don't know if i was supposed to lower the load a little or a lot. I just kept trying stuff and eventually i got unloaded OK. More instruction would be nicer. Can anyone share any solid info how loading and unloading works? As a side note the text in the mission briefing and in the English text subtitle says to go South West, when we really need to go South East Can @=RAF=Armen make this correction and maybe share some sling loading tips?

Just flying this mission now. First issue is that the dialogue says to turn right at the river over the hill from outpost 3. This is wrong, over the hill past outpost 3 you proceed along a fairly main road for at least a few KM At this point you then make radio contact with the Mi24's, they said they couldn't see me and asked for a signal flare. Above behind left seat is the panel for flares, there are 2 rows of red/green/yellow/white each with a power switch, switch this on (i switch these on at startup) and press button to launch a signal flare. At this point you're at the intersection where you now make the right turn to go up river and the Mi24's will form up on your left. The river branches right fairly soon, check the map in the briefing you'll see the 3 towns (orange areas), just past the last town drop to 200m altitude by radar altimeter. Eventually i find what i'm looking for... but on this last run both Mi24's decided to crash into the side of the mountains. Was unable to complete this, lost both wingmen in the canyon, saw wreckage against one of the walls of the hills. On referring to the TacView it seems 1 wingman collided with terrain and the other ran away. Tacview track attached. didn't save the DCS track. Tacview-20220920-021001-DCS-Granica_9.zip.acmi

F-111C or D Su-34 A recent medium bomber would be nice to have. Would love a modern / near modern complex western chopper, say a CH-53E Super Stallion ? Kamov Ka27 or Ka52 or something from the range?

Encountering this issue too. Was OK a few days ago. Was glad to find the forum had a dark mode down the bottom of the page, and now it's unusable.