VMike

@ChillNG No worries. I just completed mission 1, finally! It was awesome and I'm looking forward to the rest.

I can now confirm my issue is the same as others are reporting in this thread. VRP and PUP enabled causes an instant crash when switching to A/G and CCRP. Hopefully this will be fixed internally. No issue with the campaign though! Edit: Marking this as solved because it is not a campaign bug.

Hello, I am experiencing a crash to desktop in the same place every time I fly mission 1. As soon as I reach steerpoint 3 and begin pushing to steerpoint 4, flight lead says fence in, I switch to A/G mode and the crash occurs. I have attempted various adjustments to try and complete this mission but have been unable to get past fencing in probably 5 or 6 times. Things I have tried: Multiple slow repairs of DCS, increased pagefile size to 32GB, removed the few mods I had installed (about a dozen f-16 liveries, a scratchpad script downloaded from ED user files, and some f-16 and various terrain module-related kneeboard images), but nothing seems to help. Same crash, same place, every time. I have successfully completed SEDLO's f-16 Syria mission with no issues, so same map in roughly the same areas and with lots of triggers and such going on. My system: i7-14700k, 4070 Ti Super, 32GB DDR5 RAM, Windows 11, installed on 2TB Samsung 990pro m.2 SSD, MSI Afterburner monitoring shows nothing out of the ordinary with my system when the crash occurs, i.e. no power limits being reached, no thermal throttling, no spikes in core clocks, temps, or memory usage anywhere. Built the computer just over a week ago, all new parts, performed memtest86 after building and had no memory errors. Log files: I will attach, but they do not seem to contain any entries in the few minutes leading up to the crash. For example, the latest log which I will attach has it's last entry at 2024-03-29 20:50:52.014, however I made note of the time when the crash occurred which was at 20:54, so about 3 minutes later. All of the logs I've looked at after the crashes are incomplete, missing the "log closed" entry at the bottom. Sorry for the wordy post, just wanted to be as clear and detailed as possible. It feels to me like a DCS issue and not necessarily something on my end, but perhaps someone more knowledgeable could weigh in? Thanks in advance, from what I could tell in the first 20-30 minutes of the campaign so far it seems very well done and I really would like to finish the 1st mission and move on. dcs.log

Glad to hear it! To be fair others have said they are noticing differences in the steering too so I think it will be improved in the future. But with a decent curve for the rudder and the NWS disengaged it feels alright to me.

Are you both using the paddle switch to disconnect nose gear steering above ~80 knots? I too find the nose wheel steering to be a bit sensitive but minor corrections below 80 knots and then disconnecting to steer only with rudder for the rest of the takeoff roll makes it much more manageable.

Just to update here as well, the cat 2 workaround as suggested above by @CH4Pz worked for me.

I was able to get the mission to work by launching from cat 2 instead of 3, like @CH4Pz did in the other thread. Waited until about 30 seconds before Blade launched while he was hooking up, then I started my turn to rock after 2,500ft. This method did take 2 attempts, the first try I was hooking up on cat 2 and the carrier started a turn to starboard about 90 degrees. I waited for the turn to stop, then launched, and after that there were no comms and Blade did the same BRC track without turning. So I restarted and luckily everything worked. In my opinion there is definitely something strange going on with this mission, but the cat 2 workaround does work at least.

I replied in the other post as well, but yes in all 4 attempts of mine so far I follow procedure carefully, fly BRC to 7 miles, then turn to Rock. Once at Rock, I orbit there waiting for Blade but he never turns off of BRC or comes out of burner. Guard monitoring enabled. Honestly I am blown away by the design of this campaign, really excellent job @baltic_dragon. I am sure a ton of hard work went in to this, so thank you thank you thank you! Also as an avid Fighter Pilot Podcast listener, I absolutely love hearing Jell-O on the radios. That's the only reason I came here and registered to report a bug, because this campaign is so close to being perfect!

Hi @baltic_dragon, thank you for the replies. I did indeed fly to Rock and orbit there for some time waiting to see if Blade would ever make his way there. But he never did make any sort of turn. Guard monitoring was enabled as well. I'm going to try what @CH4Pz did above and see if I can have some success like they did.

Tried a 3rd time and I was wrong about him flying heading 140, he flies 104, carrier BRC. So he doesn't turn at all, just keeps climbing in full burner.

Reported as a bug. Same issue here with Blade.

I have attempted this mission twice so far and am 0 for 2. There is already a post in the main thread but no bug report yet. Blade launches immediately after me, but he never turns or comes out of burner. He flies heading 140 or so at about 35 degree nose-up attitude in full burner, on and on. I gave up after about 10 minutes of this each time. I read all documentation and briefings carefully, I'm following the instructions. Disappointed but skipping this mission for now.