frostycab

Any idea if ED will be releasing an interim patch for this, or will they make us wait another month? I loved this campaign but never seemed to find enough time to finish it, and I'm dying to try it again, so it would be great if they'd stop borking all your hard work.

So I need to know: Am I missing something or it Mission 2 still broken? Smoke now takes off and follows me to the tanker, and the refueling goes fine. After he's tanked he rejoins on my wings and we head off merrily to WP4. As we get there we check in with MAGIC, but as soon as they reply with "Roger, continue" Smoke rolls right, dives for the deck and buggers off back to the fleet, where he proceeds to orbit the carrier at 2000ft and 300 knots at a range of 10 miles. I've tried anchoring at WP for another hour (Left AP on and watched some Netflix) but nothing else ever happened. So, is it me and something I'm doing/not doing, or is it broken? EDIT: Never mind. Just saw the other post explaining that M2 and M3 didn't get into the latest patch for some reason.

Yeah, I'm sorry to report that I'm not having any luck with that particular method, though I will (tentatively for the moment) say I've found another possible solution. Normally I tend not to update the firmware on my VPC devices as I remember someone saying that you always need to fix all your input luas due to the hardware ID changing when you do so. Since I was having to remap my controls for each new session anyway I thought I'd try it and it seems to have done the trick. I've only made a very quick test so far, and will need to confirm everything when I have more time. It's kind of the nuclear option, but also not .

I'm not at my computer so can't test at the moment, but I'll give this a try when I can. If MacGyver-ing it works then great, and hopefully I'll be able to get some flying done without wasting time on every load, but if it does work I still hope that someone will be able to explain what changed and why the "correct" way of doing it stopped working. I'll pop back and mark your post as solution once I've had a chance to confirm it.

It's in all the modules I've tried recently. Whenever I fly a helicopter I adjust the response curve to stay between my idle and mil-power detents since I don't want to use the finger-lifts to get full-range of collective, but even then in the Apache, Huey, Mi-8, and Mi-24 my curves are gone on each restart. After a bit of a break from DCS I was just in the mood to get back into it, but without a solution I can't be bothered to deal with this every time.

Oh thank God!!!!!! It's not just me! I've been fiddling with things for nearly 2 weeks and it's driving me round the twist. It's not just the curves that are resetting, but sometimes it even forget if you've set an axis to be a slider or not.

So happy to hear this! I was just about to ask about M2 as Smoke won't even follow me all the way to WP1. He just turns right and orbits the task force, though once he did suddenly decide to come an refuel when I'd finished before randomly ejecting. LOL Looking forward to trying again when the update occurs.

Thanks. I'm running the MT standalone version. build 59263 from 2 weeks ago. I've disabled the launcher and moved all DCS-related folders out of Saved Games, allowing the sim to create new ones. The problem still persists. I am able to change and make new assignments, and any modifications to the response curves or deadzones are fine during a session, even if I fly multiple scenarios. However, after exiting DCS and relaunching all user-defined curves and deadzones have reset to default values. It's a real head-scratcher, and I genuinely can't see how it could be something on my end, though I'm happy if it can be fixed any which way.

After a break form flying I came back it at the weekend. As usual, I expected to need to reassign a few things, and for now it seems like assigning buttons and axes is working ok. However, tuning adjustments to those axes is being lost every time I exit DCS. For example, I have a Virpil CM3 throttle, and have physical detents on it. In planes like the Hornet I use the lower one for idle thrust and the upper one for military power, pushing past it for afterburner. I go into the control settings, open the axis tune window and set up as a slider as opposed to axis, set deadzones and curves to match my HOTAS, and then go flying. When I'm done I close down DCS from the main menu. On the next load ALL axis adjustments are gone. Every time. The axis is still assigned properly, but it loses reverts back from slider, has no deadzones and no curves. Somebody on Discord suggested it could be a permissions issue with my Saved Games folder, but as far as I can see any other control changes are being saved just fine. I can remap keys, buttons and axes to other functions and they'll stay like that on subsequent reloads, which would suggest to me that the profile is being saved properly. I have tried manually saving the profile after tuning too, but when I reload the save file the tuning is still missing. It's made flying an utter pointless chore for me at the moment, as I need to spend time setting up each aircraft before I fly it over and over again. Any suggestions?

I really wish they would just give a simple in-game way to set all this up. One button to record idle position, one for full military power, and one for full AB.

OK, someone on the HB Discord managed to work it out. I needed to disable the "Force Feedback" in the MISC options page in DCS. Apparently it causes problems for non-FFB controls sometimes. Didn't even know it was there.

Not that I can see. SFM is still unchecked in the Gameplay options. Good suggestion though.

I've run into a small(?) problem with the pitch trim. It doesn't work for me. To be more precise, I've checked the CBs are all in, and I can see the pitch trim indicator moving, but it doesn't appear to affect the stabilisers at all. Trimming full up or full down shows no movement on the external view, and as soon as I attempt a takeoff the aircraft just wants to pitch up with neutral stick even with full down trim commanded and set. I have to hold the stick at half-forward deflection just to maintain pitch. I've looked through and I can't find any control conflicts anywhere. Does anyone have any ideas?

When the news of the delay broke I just thought "Oh well, an extra day to learn from the manual." Then I started reading some of the replies on here and for some reason this got stuck in my head...

You know it's May 22nd all day, right?