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?

I have to admit, I don't remember ever seeing a new module released without some sort of sim update/patch at the same time.

The best thing about threads like this is that they keep me up to date on which people I never want to fly with. LOL

Discount is still live on the HB site

Thanks for highlighting the problem here. Yes, they could just delay for a few hours, and everyone would be sat at their computers for hours getting all worked up about things and complaining more and more. By simply saying "We'll push it back until tomorrow" they've been upfront and said "Don't waste your whole day waiting for a fix because it might take a while." They've freed the most anxious people from the tension for today, and also given themselves time to test and re-test whatever fix they come up with so that this hopefully doesn't happen again.

That's actually the most annoying thing from my point of view. I can't see anything on the HB website about a delay, nor does there appear to be anything on their Twitter. You either have to search through the various pages of this thread to find the actual announcement of a delay, or try to work it all out by sifting through all the comments on their Discord. A simple announcement that's easy to find and in an obvious place would be better. As for the delay itself, I'm ok with it. If something is broken then something needs fixing. No point crying about about it.

If you feel like sharing how you get a 25% return on investing that money elsewhere in just 5 months I'm sure we'd all love to hear it! Anyway, for everyone who's saying "I don't care if it's not all working! I just want to fly an F-4!!!" I found a solution: https://www.mobygames.com/game/108/chuck-yeagers-air-combat/

For the purposes of working out the issue I've kept things simple in the bindings. I've just run through a series of tests to once again check if I'm missing anything. Buttons 65 and 66 are both held in the ON state when my HOTAS throttles are in the physical detent position. I have tried with them in both the ON and OFF states. The default engine start keyboard bindings have no effect in the A-10C II, though they do work as expected in the older A-10C. I have tried loading a cold & Dark quick mission and selected the autostart, again with the HOTAS buttons in both the on and OFF states. The autostart runs through the prestart items, but when it reports "LEFT ENGINE START" nothing happens. This is true with the "Set OFF" button ON or OFF. I have tried testing in both the MT and non-MT versions of the openbeta. This appears to only be an issue with the aircraft loading in a cold state. Testing the bindings in the Takeoff or Free Flight quickstart missions results in normal operation of the throttle cutoffs. EDIT: This is most curious. I had another thought and created a quick mission in the editor, simply dropping in a cold start aircraft and tested with that. This time the throttles moved as expected, so it would appear to be an issue with the Cold Start quickstart mission itself. I've only tried on the Caucusus map, so will have a go on some of the others to see if it's an isolated problem.

I'm using a Virpil CM3 with virtual buttons set at the bottom end of the throttle axes, which works fine for everything else. I did try with the "set OFF" bindings at first, but then came to the conclusion that was wrong when the dame things wouldn't start. For them to refuse to strat even after clearing those bindings and unplugging the HOTAS is making my brain melt.

I find myself really agreeing with this, though perhaps for a different reason. It doesn't matter how nice the next generation of CPUs or GPUs or RAM or anything else is if you can't frikkin' get hold of it anywhere. Yeah, I know the almost perfect storm of 2020-21 played a big part in things, but if you struggle to find next-gen stuff in stock anywhere, and then can't afford it even if you do because of scalpers then it doesn't benefit you at all.

When I mentioned mounting the pump the other way I was referring to flipping it upside down so the pipes enter and exit at the top of the pump. I know the pump should always be below the highest point of the radiator to avoid air bubbles displacing coolant in the pump head. With regards to the fan placement, I wanted to get it built to this stage before deciding on a final layout. Yes, the rad fans are exhausting, while the base fans are intakes. I dod have another fan that was intended for the rear but I stupidly ordered a 140mm instead of 120mm so it won't fit. I'll be changing that soon. I'm trying to decide whether to vertically mount the GPU against the side once the necessary brackets are in stock, with the option of mounting another set of 120mm exhausts behind it to really pull through OR just adding 3 more 140mm intakes in the same place to aid in creating positive pressure in the case. Doing the latter, coupled with a rear exhaust should help with airflow over the motherboard. If I go for the vertical mount option then I'll probably reverse the rear 120mm to be an intake so all the exhaust goes out the side. As for what I consider to be heavy load, I'm thinking of DCS and MSFS in vr with high settings, though some core temps still regularly hit 100C even when doing mundane tasks. Even just booting into BIOS shows the CPU sitting at 88C, and I hope I'm not dumb to think that's a little bit high. What you see on the floor is what remain of my old system, now cannibalised for the drives. Doing so has made me realise that I should be cleaning out my rig more often, as the GPU fins were a solid block of dust. Cleaning continues.... LOL It did live on the floor for a while due to limited space, though I'm not daft enough to put it on a fluffy carpet. I actually had it on a big piece of cardboard to provide a hard surface and so I could slide it around easily when I needed to get at it. Trust me, the new rig is getting pride of place. I'm hoping to finally move into my new flat by Christmas, so once I'm in I can work out furniture placement and really show it off. The old rig itself will eventually be cleaned up and hopefully run better than it did. I could use it as a streaming rig, or perhaps as my day-to-day web/email PC which would allow me to keep the new one uncluttered and purely for gaming. Alternatively, it could end up following its predecessor and finding itself donated to my older brother. He loves MSFS, and is currently flying with my old i7-6700K and 1070 GPU, so an i9-9900K with a 2070 Super should be an improvement.