Sandman1330

Thank you BD, but it’s not necessary. I may have overreacted a bit as I was very much looking forward to 2.8 fixing the DCS side issues so I could proceed with the campaign, only to be hit with this other bug. I won’t be asking for any refunds, and I genuinely do recognize these issues aren’t on your end I did express my thoughts to ED regarding how the base engine is seriously beginning to impact the playability of complex missions, as bugs begin to stack one on top of another. Based on their response I’m not convinced my input was taken seriously, but short of purchasing no more modules for the time being, there isn’t much else to do! If you have the ear of the devs, if you haven’t already done so, perhaps identifying to them the difficulties you and your loyal followers are facing may help?

I’ve tried submitting bug reports, with tracks and logs, but they usually go unanswered to be honest. And it’s not as if “2, ejecting” isn’t already a well known joke around these parts… The last straw for me today has been Raven One. I’ve been trying to work through it for the last few weeks but it’s been mostly unplayable due to crashes (I’ve been very active providing bug reports and logs on the F14 AI bug issue), then just when that issue may be solved, the campaign is broken by triggers. It’s just frustrating to purchase a campaign, then wait for the next patch to actually play it, only to find that patch breaks it in a different way.

Sorry, I didn’t mean performance in this patch, just in general. The AI BFM is a nice update. But AI elsewhere is hopeless, easily seen in an even moderately complex Liberation mission. Wingmen who just randomly crash, run out of fuel, don’t do anything to support the mission. Effectively, DCS is functional for very simple things. Go do some BFM, go do some BVR, go do an isolated bombing or CAS mission. Anything more complex and it starts to fall down on performance and poor AI. Single player campaigns are so highly scripted to work around these limitations that the triggers break with updates. And the simple stuff isn’t enough after awhile.

Not a good patch from my side: 1. Vaicom Pro rendered unusable; 2. Raven One Dominant Fury triggers broken; 3. Night carrier launch crews are messed up (their wands float in space); 4. Issues with shadows; 5. (Ongoing issues) Promised performance improvements not materializing, bad AI, etc... I'm losing faith. It might be time to take a break from DCS. I've been trying to work through Raven One, but the constant crashes due (we think) to the AI F14 bug rendered it unplayable. Now that bug (might) be fixed, but the mission won't progress due to trigger issues. Maybe I'll return when (if) 3.0 arrives, but I just find myself fighting frustration every time I try to get something going in this game lately. It's too bad, I've been playing this game since... 2014? Edit: so before people start coming aboard me for this, note I’m not throwing stones or being belligerent in any way. I do care about this software and this community, so I feel it important the devs know why they are losing a customer, and that I do hope to return one day. But the simple fact is the current state of the game has fallen below the standard I believe is reasonable considering the… $1000 or so I’ve invested in the company?

So, since Mission 8 (and most others) kept crashing, I figured I'd wait until the 2.8 patch before trying to proceed with the campaign. Well, 2.8 has broken Mission 8. Noone pushes from waypoint 1. All the flights call pushing, but they just keep orbiting waypoint 1. I mean, I'm sorry and I know this will be an unpopular opinion but... the campaign has been unplayable since I bought it. Crashes, bugs, workarounds, broken triggers.... Most of it is on the ED side, but it doesn't change the fact that I've purchased an unplayable campaign. I haven't enjoyed a single mission yet that has gone flawlessly without some kind of bug or crash. I'm seriously considering a support ticket for refund. I don't like it as I've enjoyed BD's work up to now (and I don't believe most of these issues are even his fault), but until folks start voting with wallets, we'll continue to waste money and time on buggy substandard software. Am I being too harsh? I can't be the only one feeling this way...

Could you elaborate? I waited.... forever... for Red to engage. I circled and circled after Red was cleared to engage, he didn't do anything. So I thought, am I supposed to engage? When I fired, then I got the voiceover that Red was engaging. Then, after I'd destroyed the vehicle Red was supposed to destroy, I got the voiceover to engage myself. So I strafed the second vehicle. And nothing happened. So I strafed the third vehicle. Still nothing happened. Then DCS crashed. Was I supposed to wait even longer? I mean, I'd waited 5+ minutes after Red said he was already in a position to engage and was cleared. I could have rifled 10 mavericks in the time I waited.

No dice. F14 disabled in mod manager, still crashed on Mission 8.

Hopefully the Heatblur fix solves the problem. In the event it doesn’t, disabling the F14 in the mod manager has so far seemed to work for me. I haven’t played much, it in that time I haven’t seen another crash.

Regarding the wheel chock workaround for Mission 6, my experience is actually the opposite: You have to leave the wheel chocks ON until the tomcat hits you. If I have wheel chocks ON, I don't take any damage. If I have wheel chocks OFF, I take damage.

Is it preceded by a brief blue screen flash? This is a frequent problem, usually caused by a number of factors. Could be a bad cable, could be USB suspend kicking in (turn this off!), could be the headset going to sleep (WMR settings, tell it never to sleep). And I see you have an AMD system similar to mine - there have been known compatibility issues with AMD chipsets forever. I get this now and again and still haven't been able to chase it down, I think it's a hardware issue with my headset itself (or the aforementioned AMD compatibility), but mine is always preceded by a blue screen in the headset.

I’ve received a tip in the Raven One forum to disable the F14 module in the mod manager. OFC it means you can’t fly the tomcat but apparently it has worked for some. I haven’t tried it yet but we will see how it shakes out.

Oh cool, will do, thx.

I know there are a lot of crash threads, but none that I've found have specifically mentioned these two missions. Yesterday, Mission 3 kept crashing consistently at waypoint 8, just as it transitions to the RTB phase. After 4 attempts, skipped the mission. Today, Mission 4 crashed on return to the boat (20NM out). It sounds like the AI Tomcat bug (game just freezes up, no error message, no crash log, just frozen), but I hadn't seen it mentioned in any other threads for these specific missions yet. Anyone else, or am I alone on this one?

Are people still having this problem, or is it just me? I'm having consistent crashes in the Raven One Dominant Fury campaign, in every case it's on RTB to the boat... The campaign is effectively unplayable due to these crashes.

My issues are coming and going. Right now (knock on wood) I haven’t seen the issue in awhile. I’m wondering if it’s not my cable. The issue seemed to stop when I updated my AMD Adrenaline drivers… But I thought I had it solved before only to have it return, so time will tell.

My local computer store has re-stocked, they now have plenty of stock. Yay! Here's hoping prices will fall even more.

Concur, and it makes sense. Since AM5 mobos and DDR5 are so expensive, AM4 still provides a lower cost option with DDR4. Intel’s latest support both DDR4 and DDR5, AM5 is DDR5 only.

Oh I'm not saying they aren't available, but the sites I've been monitoring (Amazon, Newegg, local computer store) are all quickly dwindling in stock over the last few days.

5800X3D seem to be selling out across the board… I wonder if they’re clearing stock for good, or if they’ll keep this one alive and are just selling out from people who waited for AM5 reviews. I’m not in a position to buy yet, so if I miss my window, I guess c’est la vie.

+1

I'm on the fence too. Currently using a 3900X on an X370 board. I'm tempted to step up to AM5 for all the platform improvements, but the investment will be significant. My other option is to drop in a 5800X3D and milk it another year. After reading the Tom's Hardware review, I'm leaning towards grabbing a 5800X3D. Check out the MSFS benchmarks: 5800X3D is still outperforming even the 7950X in MSFS (and actually most games), but by a huge margin in MSFS. I think MSFS is about the closest they have to DCS.

Interesting, I still can't find it in the AMD Adrenaline software. Can you give me a steer on where you found it?

Yeah I’ve turned off all of those. The only one I found yesterday that’s new is the “allow windows to turn off this device to save power” option buried in device manager. We will see if maybe that helps. Other than that, yesterday I upgraded to newer beta AMD drivers (they were up to date on the stable branch, but I just wanted some kind of change in the driver to see if it makes a difference). I have a few other troubleshooting things to try, like going back to my V1 cable, but I’m running out of ideas.

I disagree. 5 mins of searching these forums / Reddit / discord etc will reveal many complaints. Just google Reverb G2 blue screen crashing. It’s been ongoing for years. Lots of incompatibility issues with AMD motherboards too. Thanks, but that setting is physically not present on my system. Google tells me that’s typical of AMD cards. Lots of good advice to parse here. I have an old powered card from my own Rift days that I might put in and try, for testing sake. I only use it for DCS these days, so can’t say for sure if it’s across the board, and I’m using OpenXR. It is just strange that it was fine for months after getting my V2 cable, then this issue started coming around once in awhile, and has increased in frequency to regularly now. Nothing else (hardware) has changed, drivers are always a wildcard but the way it started slow and came more frequent leads me to think it’s another cable issue.

Thank you for your reply. I'm in the same boat: Motherboard USB-C doesn't work, I can ONLY use one specific bank of USB A with the adapter. BIOS is up to date. I also already have the V2 cable, but I suspect it may be the issue again as I've had it for awhile now. I don't want to buy a new cable for over $100, and it's out of warranty, so we'll see... I don't even have the option for HAGS (seems like it's not a thing with AMD cards, I did alot of searching to try and find it, but it's not even present on my system). As for powered hubs, I have the V2 cable which is supposed to not need that. Maybe I'll try a powered hub, just to see, but I'm not optimistic. I think I have a bad cable. Though interestingly, by finding the Reverb in Device Manager, I've come across a setting "allow windows to shut off this device to save power." It was enabled. I've now disabled it, we'll have to see if that makes a difference....