Sandman1330

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....

Sigh.... Now basically unusable. After 30mins play, crash. Has anyone figured out if it's possible to restore your DCS session? I get the blue screen, the headset resets, and I'm kicked out. But DCS is still running, and still thinks it's GTG. Any way to get WMR connected to DCS again without losing the current session? I could live with this if that's the case, but as it stands I can't do a 30 min liberation mission because as soon as this thing cuts out I can't continue!

It’s absolutely garbage. I’m glad for you that you got a good specimen, but believe me your experience is not typical.

Yeah I’m on my second V2 cable, blue screen crashes every half hour or so now. I hope a new generation of headsets is on the horizon so I can get something else. Very frustrating.

It was almost exactly the scenario you describe. The rest of my flight of 4 spawned into spots 14, 15 and 16, while I spawned further forward. As soon as I started moving, the other 3 started moving forward as well. Because of the way spots 15 and 16 are angled into each other, when they all started moving forward at the same time as I did, they collided. I haven't had a chance to try and replicate it again, but I tried that same mission several times and it happened every time.

Same problem. I have the new v2 cable as well. It's getting worse, I can't get through 30mins now without the screen flashing blue and resetting. DCS keeps running but I get kicked out of VR and back to the cliffhouse. It's like it's momentarily losing connection, then regaining it. I've tried multiple USB ports, turning off USB suspend... I'm getting SUPER fed up with this G2. It's a hot mess piece of garbage.

Thanks, I'll see what I can do. That track should work, there were no mods involved, so that's strange. However, I think it's vital you try to replicate this on a multiplayer server. It seems the pathfinding / spawn points are different in multiplayer servers than in single player. I find when I do an SP mission, the aircraft spawn in different locations than if it's on a multiplayer server. It does seem to work better in SP. I'll see if I can replicate it again on a lighter mission.

Ahaha, as I was reading your post, I was like "this guy is totally a B412 pilot." Then I got to the end and and was like, oh yeah, figures! While I can't speak for the Apache specifically, I concur with your assessment. I find the SCAS in the DCS Apache always seems to be working against me. Though (a little off topic), I'm not sure your assessment of API movement in SAS mode on the 412 is entirely correct. What you've stated is consistent with how our flight manual says it SHOULD work, but if I push against the mag brake in the 412, I'm still getting API movement (and even autotrim fails), which would imply the APIs are still moving. There is also a use case where the APIs should work against you a little bit (in SAS mode), and this is in dampening aggressive stick movement. If I slam the stick to the side, the APIs will actually move against me to dampen that movement somewhat and make it less jarring. But they should quickly catch back up.