Search the Community

Lately DCS MT has been crashing constantly. Part way through a mission, halfway through, very end...Just crashing. I can hear it coming because the fans on my GPU spool down and I just have to wait for it. I've it DCS crash 10 times before I finally gave up and went to the couch. I've attached the last log from when it crashed. Doesn't make much sense to me since I really don't know what I'm looking at. From what I gathered it's a bad visualizer.dll in the actual game and not any mod. I could be wrong though. Anyone have any input or guidance on this that can help the crashing issue? dcs.log

I'm not sure what's going on. This weekend, I was doing more than an hour of Instant Action Free Flight over many maps (Caucasus, Persian Gulf, Syria, Sinai) and all went fine. Today, I wanted to try the Cold and Dark instant action on Caucasus, but I keep getting DCS crashes before I even reach the end of the startup procedure (reports were automatically sent by DCS after the crash). For example, once it crashed before RPM could reach 60% (so at the very beginning). Another time was just after alignment. Is it something known or that is specific to my computer setup?

DCS no longer runs. Every module including SU-25T. Problem is same. Few minutes after mission starts, DCS engine starts getting weird flare light flashes and black blanks, missing poly slivers, then entire DCS goes to black with crash. It kills the drivers for RTX 2060SuperFE. It is not heat related. GPU never exceeds 76, and mostly runs at 73 in DCS. With case closed, a few degrees warmer. But crash is same. I dont have to do anything. Launch mission, then dont touch anything. Dont start aircraft. Just leave it to run by itself. After some time, from few miniutes to 15 minutes, rarely longer, DCS crashes. With same symptoms. Fresh install, running without any 3rd party. Running in Window, running in maximize. No difference. System diagnostics report no error. Windows GPU Stress app no problem running for hours. HeavyLoad running for hours , and over night no problems. This is DCS specific.

So I have an 11700F in a pre built pc (judge away) been fighting bugs in DCS VR since inception but finally got the base game (I play on standalone and mostly pve on base maps). Downloaded multithread beta and did some testing with tracks between MT and OG style threading. On MT, with the in game FPS counter, it says it's CPU capped, however, I get no bottleneck notifier in single thread. Frame difference between the two is 3-5FPS but inconsistently. Any ideas other than a new CPU and MOBO??? Full specs in comments- help me find the missing frames please!!! I did some additional testing unfortunately im not smart enough to track logs or explain this but I'll try. Capped at 45fps in Quest software, I can consistently get 35-40fps in Single thread by turning basically everything down to low and a couple items to medium. However, same exact settings in MT, I still get wild fluctuations from 22fps to mayyyybe 32 was the highest I saw. The only explanation I have for this is that my single thread game is installed to the nvme and multithread beta is installed on an external USB 3.0 ssd. I MAY have answered my own question but im coming to the pros seeking advice and correction if I haven't. I'm not looking for wild 120fps on the oculus, just a good balance of being able to read DDIs and go from being heads down in the cockpit to heads up without frame drop or hitching that causes me to miss things. My tests were done using a low level track about 60sec long on an empty caucuses map in the F18, and similar results were duplicated in the uh1h. Pc Specs: Full specs Gigabyte b560 chip set I7-11700f Asus pheonix rtx 3060 v2 12gb 32gb DDR4 @3600MHZ corsair dominator Running winwing orion 2 hotas Samsung 1440p 144hz monitor Oculus Quest 2 via link cable Thrustmaster budget rudders

While moving either of the dual throttles the other throttle moves a little when the throttle pass the other and a clicking sound occurs. Would've shown better with a non-handheld steady camera. Looks, sounds worse in reality than on video. Does anybody else's throttle act and sound like this? It's disturbing because I think it is new. I fear maybe the friction mechanism starts to break down. Throttle is 4 months old.