wowbagger

The Page File change seems to work for both Full Screen enabled and Full Screen disabled on my system. The only crash I have had since changing the Page File was once right after I switched from Full Screen disabled to Full Screen enabled. But I emptied the metashader, fxo, and temp folders right after that crash and have not had another since that time. I have tested with multiple mission restarts, and DCS restarts, and a couple of pc restarts and it seems to be holding. If it hasn't fixed the problem, it seems to have lessened it dramatically.

Agree! In some pretty limited testing, this seems to make a big difference. I haven't had a 2nd Loading crash after making this change. I haven't tested any long missions yet. But Restarts, Watch Track, and loading successive missions which would usually cause a crash have not done so after the Page File change. Cheers XPACT, I hope you have found it.

It's a hateful mission. Any mission which immediately harasses you to "keep up!" and then just quits with mission failed because you didn't immediately teleport into the proper position is some of the worst mission design you can have. It teaches you nothing, is no fun, and turns you off the whole campaign. I would recommend it just be removed altogether.

I have it happen occasionally. Once you hear "Two, rolling" you pretty much have to get out onto the runway without going slowly or stopping or you will get rear ended. I never radio for permission to taxi as I am under the impression that delays things a bit (could be wrong about that) but you still have to be careful.

Well stop! Just kidding. I'm sure it'll become available for the rest of us soon.

Okay, thanks for the reply. Good luck! Have a great weekend. edit: From my personal experience, full screen makes a significant difference. Full Screen enabled = constant reproducible crashes / Full Screen disabled = infrequent, random crashes. I'm running a RTX2080 GPU and 5600x CPU.

@Flappie and @BIGNEWY just to clarify, are you not getting any crashes of DCS at all on your setups?

Quick question about the profile. If I add a Control Panel #2 to my CM3, and run them together as a single device, do I have to redo a whole new profile from scratch or is it possible to add a device to an existing profile? Cheers

You aren't kidding. I have only flown the first mission, but man ... After nearly two hours of struggling to catch up and get into position, staying in formation (AI sucks at making direction changes ), constantly adjusting throttle, boost, rpm, and trim, checking every direction for bad guys, friendlies, and just admiring the beauty of the innumerable bombers flying below our huge (for DCS standards) escort, and finally anxiously eyeing my fuel gauge as we crossed back over the white cliffs, I was mentally exhausted, my muscles were clenched and tense, and I desperately needed to hit the head. It was awesome! What a fantastic atmosphere and experience. The sight of the bomber formation flying below us against the tableau of the Channel map is jaw dropping. For anyone, like me, who is trying to learn engine and flight management of the Thunderbolt, after flying this first mission you will have increased your knowledge and ability immensely. Thanks for the perfect introduction to what I can only assume will be a stellar campaign. (Also, I had zero performance issues at 1440p without needing to reduce bomber numbers.)

Awesome. Thanks for poking the team to get this one sorted.

There might be multiple causes coming into play. I suffered from the second mission crash bug until I switched to windowed mode. Now I can restart missions / do more than one mission in a row without guaranteed crashes. However, I still seem to get some occasional random crashes - including once just trying to load a mission in the mission editor. After game restart the mission loaded without issue.

It seems the default labels on/off action has now been changed to cycling through the different kinds of labels. Is there any way to assign a keybind to just on/off again? The new way involves a lot more button clicking to just pop the labels on / off when you need to get a quick visual orientation. A second question - has anyone figured out how the ranges for the dot neutral labels work? The file has references to hundred percent and five percent (I think) but I couldn't make much sense of the numbers during a very cursory look at it. cheers Edit: It seems, at least with my configuration, that the new dot neutral labels still work in an on/off method. It's just the older version which now cycle though one after the other. - I posted this in an existing thread in the wishlist section, but then figured it was better here - sorry for the double post.

It seems the default labels on/off action has now been changed to cycling through the different kinds of labels. Is there any way to assign a keybind to just on/off again? The new way involves a lot more button clicking to just pop the labels on / off when you need to get a quick visual orientation. A second question - has anyone figured out how the ranges for the neutral dot labels work? The file has references to hundred percent and five percent (I think) but I couldn't make much sense of the numbers during a very cursory look at it.

So many good things about this campaign. Spoiler - don't look until you've explored the map on your own: Love it. edit: can we no longer edit the spoiler title text?

Yep, I know exactly what you mean. For the last while I have been trying to convince myself to get the 109 and/or P-51 just to play these campaigns. I really have very little interest in either plane in and of itself.

Awesome, thanks for this very useful information! It's great to finally know what all these things do and their effects. If you're looking for another idea for a video I would love to have one that details all the quirks of the DCS AI and how to get the most out of them (as a pilot in a mission) and avoid some pitfalls in giving orders, expected behaviour, etc. A campaign creator of your calibre seems the ideal person to know the ins and outs. Just a thought for the future perhaps. Thanks again for this one.

Yes, you are correct. There is a BIG difference in volume between using stereo vs 5.1 or 7.1 for some reason.

the Harrier guide distribution is temporarily halted in order to avoid negative training

+1 I feel the same. GRs put out so much stuff there is inevitably some lower quality, glossed over, or inaccurate bits among it. However they seem to always try to correct the errors where they can. And more importantly, they cover a lot of stuff that no one else does. I have no problem watching GR vids. Take them for what they are and make good use of the info they put out.

Done and thanks!

I have had the same reduction of radio messages post 2.7. I've tested it over a number of modules (including FC3 planes). The messages became almost too quiet to be able to distinguish what was said against the normal background noise. I've had to turn up the master volume, reduce the world volume and in cockpit volume, and max out the helmet volume to make messages audible without blowing out my eardrums in other views.

Just wanted to say thanks for being so proactive with the post patch problem solving / info sharing. It's why Heatblur is my favourite third party developer ... by far. You guys clearly care about your product, and your customers. cheers

+1

Right that's where you want to be. Double click on the axis you want to add buttons to: Then choose which areas of the axis travel you want to activate the buttons, and save: Then Save to VPC Device: Then check which buttons were assigned by moving the axis and watching to see which buttons activate: Then finally, make sure that button on the Physical buttons state list is assigned to a logical button which is what your game will see: And Save to VPC Device once more:

You should be able to assign buttons to all the axes I think - all the same way. Why do you say you are limited? -just select the axis you want to use -then tick the boxes for the 'region of axis throw' you want to activate the button(s) (eg. 0-5%, 81-100%, whatever) -'write to rom' (or whatever it's called) -then look at the physical buttons table to see which ones were created (by moving your axis), and assign them to a logical button