HunterICX

Same issue, after a hour or 2 my DCS just crashes to desktop and I have 32GB RAM + 32GB Pagefile set on a SSD with more then 100GB available space. errors indicate it just ran out of memory to use.

I'm sorry Flappie but this is not a RAM issue, nvwgf2umx.dll and the crash stacks look to be part of the Nvidia drivers so it seems his GPU drivers are bricking themselves running DCS. I'd suggest a DDU (Display Driver Unistaller) under Windows Safe Mode, reinstall the GPU drivers using the latest stable release from Nvidia. Hopefully that'll solve the problem.

Hi, I was flying online for a good hour and while I was returning to the carrier group I was attempting to hail the CV59 Forrestal , I already tuned in through the Jester TAC page and while it didn't appear in the comms menu in DCS I went back to the Jester Menu to double check and just have him tune in again but this time when I hovered and attempted on click on the Next Page my DCS froze and crashed. All files came out clean when I verified the files through steam. Not sure if it's of help but checking the crash on the reliability tab in Windows Name of the module with errors :F14Avionics.dll (translation of the highlighted area) is what I noticed. dcs.log-20220410-151941.zip

It's not the VRAM, Maxing out VRAM that requires more video memory than your card has will result in the frame rate dropping as it's forced to use system memory to hold some of the textures, meaning it has to shift data back and to between them. But since the system Memory is already stretched to it's limit with DCS , it's just a matter of time depending on your physical memory and pagefile and ofcourse your settings because higher quality textures means that more needs to be stored onto the system memory before the game crashes because it simply runs out memory to keep it running.

The drive the pagefile is set on has 78GB left but it's also the C:\ drive where Windows is on I think that'd be enough but when I checked the Dxdiag in the log DCS really escalating the pagefile size, I'll swap the pagefile setting to my 2nd SSD (where DCS is installed which has 235GB available) see if I can fly for longer. I had this outofmemory issue not so long ago (last oct I think) as well where it crashed after just 1 hour, I ran a Windows Memory Diagnotistic and Memtest86 (gave it a few passes) back then and it found no error with my RAM.

Hi , I was flying roughtly 3 hours in the A10C on Syria (Multiplayer) when suddently whilst in the F10 map ( I noticed grey squares just before the game crashed) I've attached the log file. Whilst looking I spot outofmemory errors and the one from the title) I'm Up to date with Windows and my AMD drivers. Running DCS latest OB. dcs.log-20220128-234101.zip

I'll have to do more flying when I have the chance but so far I haven't seen the black boxes (mind you I have recently executed a whole DCS wipe and reinstalled it clean) Will report back later when I got a few more hours of flying done and report later.

So I guess having my pagefile set to 32GB isn't going to do much if DCS just keeps up using my entire stock of RAM and pagefile like that? Is this a thing that has to be fixed internaly in DCS or is there something I can do about it?

There's 92Gb available on my C/ Drive , I'll increase my pagefile first and run tests again when I get the chance. thanks for pointing that out, 4GB pagefile is pretty small considering I'm already close to maxing out on my dedicated RAM when playing on Syria at War.

@Flappie Already ran a Windows Memtest and Memtest86 ran a few passes, came up empty in that area. Also ran a repair, cleared shaders from DCS, DirectX and AMD. Also updated my GPU drivers as there happen to be one pending for me to install. I'll try other modules and other maps as well as this happened on a busy day on Syria at War, the game was already taking 31,6GB of RAM before I even got into the Tomcat. If it still crashes then I'll try disabling the XMP , this problem is something I haven't experienced before the latest OB update and I had never had issues with have the XMP profile enabled.

Had 2 crashes today flying the F14 on Syria at War. Both happened when I was on the ground at incirlik after a sortie rearming and refueling. Logs are attached to this post dcs.log-20211031-131205.zip dcs.log-20211031-150825.zip

Still getting them as of last's weeks OB update and Hotfix.

Cleared the DirectX Shader cache, Cleared the AMD GPU Shader cache, Cleared the FXO and Metashader folders, latest OB Still getting them:

I really wish HB would add a Jester Menu option to set him to "Fuel call outs only" to not be blasted by 100 star wars puns and jokes in rapid succession. I'm fine with his occasional jokes but the spamming of it during a moment where I have to conencentrate is really annoying

Can't say I have experienced this (VKB MCG Pro , dual stage trigger) and I've been firing some heaters lately in a merge and they come of one at a time but I'll keep an eye on it if it does happen under certain circumtances.

From what I red from you it really shows how much you know about FM's and developing. It'd be better if you don't come back as you'll just end up wasting everyones time. --- I surely think the sticky wheels will be adressed at some point but it's not really that much of a bother that it takes away the rest of what the F14 has to offer (besides I take off from the boat whenever possible) that it takes a high priority imo, there's other stuff I much rather see adressed first that I believe will come in due time and when it's ready to be added.

It was a MP mission, I've asked the server admin if he remembered but he said he didn't manually added fog he just chose a preset. All I can tell about that it was one with 2 layers of clouds at different altitudes. I did upload cutted clips of that screencap perhaps it helps giving you an idea.(excuse my fat fingers wasting an aim9) : You see green dots happen around 22-25sec for a brief sec.

Also I spotted this in one of the recordings when at a certain angle in a dogfight:

Still getting them as well as of the latest OB update:

That is strange because as I stated in the post above, I did clear my FXO and METASHADER folder beforehand. I don't know how they end up in the logs. Just for future attempts or having to clear, can't I just delete the 2 folders as a whole?

dcs.log

2 patches further, drivers updated, ran repair again, cleared my Fxo & Metashaders and I'm still getting them. Just doing any of the free flights / Instant actions for any module and I can reproduce it. Just in case I'm running a AMD Vega64 drivers: 21.3.1

Same here, using a AMD Vega 64 drivers 20.11.2 Clean DCS, no Mods, Ran a repair already but that didn't help. They don't appear all the time, they appear briefly like in a flash of a second when I fly around and look around. And they don't appear when looking in a free camera like F2.

Where do you hit the tank? front, rear, sides? if you're shooting them on the front modern tanks like the M-1 are hard to kill.

Yup make sure the Canopy Lock and Seal lever are in the up position as seen here: