Sandman1330

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.

OK, thinking aloud a bit here... I used to play RPG games (WOW, mostly). I haven't for a very long time, but I remember for some of the instances that required a large number of different roles to cooperate, there was an in-game system set up to help put together the group and the various different roles necessary (tank, healer, DPS, etc.) I've gotten back into Liberation recently, and I got to thinking. Putting together a strike package is not all that different. You need different roles - Strike, CAP, SEAD. Relying on AI to do this is... less than ideal. What if there was an in-game UI to help you find those roles, part of the multiplayer UI. I envision it working something like this: 1. Server host starts the server, and in doing so, checks off any roles and airframes that he may need (2 x F14 CAP, 2 x F/A-18 SEAD, etc.). Of course, it doesn't have to be a liberation mission. It could be anything from a simple mission where he just wants one live wingman (like an Op BACTRIA), to a massive liberation campaign requiring many roles. 2. Player logs on and wants to find something to do. He can go to the LFG UI and check off which airframes or roles he's willing to do. 3. That player would then be matched with server missions waiting on those roles. He should have the chance to read the briefing, where the server host could put things like SRS IP, skill levels requested, of course mission brief, etc. On reading that, the player could choose to accept that role or not, depending on whether he feels it would be a good fit for him. 4. Once the server host has filled up all (or enough) of his roles, he can unpause or start his mission and game on. 5. If there are no servers waiting, perhaps there could be a list of how many players in what airframe / role are currently waiting, so a possible server hoster could host a mission targeted at what's in highest demand. My one fear is the DCS multiplayer community may not be large enough for this to be effective, given the huge number of airframes and roles there are to choose. Only ED would have the data to parse and determine if enough DCS players are active in multiplayer for this to work. However, an easy LFG mechanism like this may encourage more to go MP as well. I know that I personally want to do more MP, but I haven't yet found one of the virtual squadrons that has events and requirements that fit my schedule and style. The ability to simply jump in and find a group quickly could encourage more participation. I'm open to others' thoughts on how feasible this may be, or ways to improve the implementation.

That's fair. I'm just trying to dissuade the attitude that anyone who hot / auto starts somehow isn't a serious DCS player, or is less skilled than someone who can cold start from memory. This is a case of "correlation doesn't imply causation." For some of us, cold starting is boring - every RL pilot I know who plays DCS skips the start! Cold starts may be effective in discouraging the taxiway takeoff type individual from joining that server, true. But as others have said, disabling auto starts wouldn't significantly improve that situation, as those players are probably already dissuaded due to the time necessary on a cold / auto start. It might also dissuade perfectly legitimate folks from joining too. I'm afraid the only real motivation for disabling auto starts is to further propagate the elitist attitude that one must cold start in order to be a serious player.

There's also the real life pilots who realize the ability to cold start an aircraft in a game doesn't make you a DCS god. I fly milsim. I also hot / auto start all my aircraft because I cold start them for a living and can't be bothered to make my leisure time feel like my work time.

Some have mentioned engine power due to speed, this is a factor but minor. What you are seeing is a result of the graph above. At lower airspeeds, to maintain altitude, you need higher angle of attack. This leads to more induced drag. As you get into high AOA regimes, induced drag spikes. Conversely, as you go faster, AOA reduces (therefore less induced drag), but parasite drag (drag from air resistance on the airframe) increases exponentially. The dip at the bottom, where the sum of the two drags is least, is called L/D max (lift/drag maximum). This is your most efficient airspeed. If you get slower than this without increasing power, you'll keep slowing down as induced drag will continue to increase. If you get faster than this then set the same power setting, eventually your aircraft will find the same equilibrium where your power equals your drag, except it'll be on the right hand (faster) side of the curve. If you're closer to L/D max when this happens, you'll actually observe that you accelerate until the parasite drag increases enough to equal your thrust.

So, we all know the pathing for taxi is.... challenging. One of the greatest causes of AI collisions while taxiing seems to be that your AI wingmen will follow you when you start taxiing, without hesitation, without regard for other traffic. Normally, this can be avoided by only starting your taxi when the deck is relatively clear. However, today I ran into one where my 4 ship was sited in such a way that, any other aircraft notwithstanding, as soon as I start taxiing my loyal wingmen start moving, and run directly into each other. This seems caused specifically by the fact that as soon as I move, they start moving. If I wait, AI traffic flow seems to be reasonably deconflicted. As soon as I move, the rest of my flight starts moving, with no regard whatsoever for other traffic, including the rest of my flight. liberation_nextturn-20220823-151710.trk Track attached.

I've been playing DCS for... jeez, at least 10 years. I've invested a lot of money. I have most modules, most maps. And I'm getting so frustrated lately I'm considering walking away from it all. What good are phenomenal modules like the Hornet, Viper, Apache, Tomcat.... Just about every module, just phenomenal work - what good are they when the base engine is a dinosaur? High end PCs can't make this game work well in VR, and crashes like this... I just lost another Liberation mission due to this crash. At 50 miles, check in for Case III approach, and crash. No other game I play requires so much work just to get it running smoothly, or crashes so frequently. I'm just finding more frustration than enjoyment lately. I truly, truly hope they are close to the engine revamp they are promising. Because all of the wonderful work on the modules is for naught when you can't use them to their potential. I want to help in any way I can, I really do, but aside from reporting bugs that often go unacknowledged, I don't know what else to do.

Following up on my issue, I removed the rain from the mission and flew the exact same profile again. The only difference was no rain (no "wet deck".) And the game did NOT crash. Seems like a separate issue for me. Edit: Spoke too soon. This time, clear weather, approaching the boat for a Case I. About to call see you at 10, so right around 10NM from the boat. Same style crash, just a freeze. This time I have this in the log: So, the wet deck may have been a red herring. In both cases, it seems to be an error loading textures of some type. Tomcat, perhaps? dcs2.log

I may be a victim of this as well. Twice it happened to me, crashed in the same location each time: Flying F18C, Night time, gray and rainy, Persian Gulf map, flying from Al Minhad out to the boat to practice Case III. Inside of 10NM from the boat (once it happened 4 or 5 miles, the second time around 9 or 10), DCS freezes. This was on a multiplayer server. I'm not sure if it's related to the Tomcat bug. There are AI Tomcats flying in the mission, and static Tomcats on the boat. Though there were also static tomcats sitting next to me when I departed Al Minhad, so it wasn't the first time those textures were loaded. Unfortunately no track as it hard crashed. I did do a few successful Case III where I departed off the boat and returned to the boat. The crash only happened when I departed Al Minhad for the boat. This could be due to the length of time, as it took longer departing from Minhad, or due to something else. There is also this line in my log: 2022-08-10 21:28:35.648 ERROR_ONCE DX11BACKEND: texture 'wet_map_map' not found. Asked from '' Makes me wonder if it was something to do with the Carrier's wet deck, but I've had no issues loading directly onto the carrier... dcs.log

As per title. Messed up on the first mission (F16 TGP.... infuriating), so to fly it again I went skip to push time. It just ends the mission. Edit: Strange. I tried F2 (request lowdown) instead to see if it was just misplaced flags. It gave me lowdown, but then skip to push time worked. Edit2: Even stranger, it now seems to work as intended... The difference may have been that the first time I did it, I did it from a "fly again" rather than a clean start. I tried using "fly again" a second time and had the same problem.

Yeah about 1 in 10 times it would work, the rest of the time was a mix of strobing and black screen. I just gave up and reverted back to the main driver.