Sandman1330

Sorry! Here's one attached.OH58D tailwind.trk

Something about the Kiowa FM has bugged me since it came out. When hovering with a moderate tailwind, or hovering backwards, the aircraft does.... something I don't understand. The rotor RPM spikes off the chart, the aircraft starts falling as if it's in VRS (but it's not), and yaw becomes nearly uncontrollable. I feel like this might be trying to simulate LTE, or VRS. But it can't be VRS because it occurs with no descent rate, and it can't be LTE because the pedals are still effective. Neither explains the spike in rotor RPM. I've attached a track. What the heck is this??? In 2000+hrs flying real helicopters I've never seen or heard of anything like this. Please tell me it's a bug and it will be fixed, it's extremely annoying - combat does not always allow one to hover into wind (the enemy could be downwind from you!) kiowa tailwind.trk

This just happened to me after Speed and Angels Mission 13. Love how bugs from 5 years ago work their way back in... can't end mission.log dcs.log debrief.log

Nothing like playing the whole mission through, then after refueling and sitting happy off the tanker's right wing, lead breaks HARD right after fuelling, straight into me. Boom, done. 2 hours down the drain. After fuelling is it just fly back to the ship and land? Anything else I'm missing if I just skip? Really don't want to fly the whole thing again... On a side note, maybe a suggestion, can we make the player immortal during certain phases (primarily when we're expected to fly form off such an unpredictable AI?) Those sudden breaks that AI makes are just too damn unpredictable (not to mention unrealistic)...

Possibly!

OK after troubleshooting, it looks like the trigger won't accept the voiceattack "salute" command (though it correctly triggers the ground crew). You have to use the 's' key (which I have bound to salute), and this will progress the trigger.

Mission 10 (night CQ). Do the startup (autostart as I'm lazy and hate cold starts - don't judge, I do them for a living), once alignment complete, Chig says "are you ready?". Nothing after this - no response from Slick, no checklists, no radio calls. Tried hitting space to see if there was user input required, still nothing. Trying to progress, using salute command takes me to Cat 1 (not Cat 3). Launch, standard SC comms but no mission comms. I've stopped there everytime as I don't want to waste time on a mission that isn't going to progress.... It seems the mission is stalling at "Are you ready?" PS - briefing says to set the front radio to Lion Tac (button 13), but when I do that, I stop hearing all the radio chatter.

Is the grade sheet supposed to autofill, or is it meant for manual entry? My grade sheet is blank and I’m complete up to mission 5…

I wonder if there is any chance of an AC-130 variant in the future?

Any update on this bug? I'm sitting on what I feel is a great idea for a mission but can't really achieve my objective with this issue breaking the gameplay, thanks!

Hope you’re right. But as I read the text, even before I got to that point, I started to wonder if this would work with heavily scripted missions. It does sound more like a persistence save for units, etc - there wasn’t a mention of saving script states. Maybe it’s implied

If I read this right, the save function will not work with payware campaigns? Bummer…

Thanks, I tried 0, but not 1. Either way it has no effect - they leave the hesco towers and run around. I’ve made them immortal for the purposes of prolonging the fight against a superior enemy force, but the mission flow won’t work with them running around outside the FOB.

Is this still being investigated? I’m trying to build a mission that has infantry in the HESCO towers, but they disperse and leave the tower as soon as they come under fire, even with disperse turned off.

I don't think it's fair to refer to those who disagree with the development of this module as "complainers." It's more akin to shareholders of a company who may disagree with the direction the company board or CEO are taking the company. Many of us have spent significant amounts (thousands) over the years on ED modules - I have almost every single module and map. That's a significant investment in the DCS World ecosystem. If I feel the direction the company is going could jeopardize my enjoyment of the product that I have invested significant funds into, I have the right to speak up. That's not complaining, that's voicing my concerns to protect my investment. Calling those of us complainers who disagree with what we believe to be a shift in the company's focus, what we see as a reduction in the standard of documentation required to make an accurate module, is unfairly belittling. You don't have to agree with us, but you should respect our right to disagree (respectfully) with the decision.