XPACT

I used it few times in 2.7 and it worked as expected. This is my guess, you were probably fighting more advanced fighters that are jamming and radar dropped out of track while scan mode. If you see JAM (English avionics) or АП (Native avionics) on the HUD you can't use both TWS and TWS2. Some jets are jamming in pulses or when you STT them in that case it would also drop out of TWS.

In single player Windows 7/8 compatibility works for me also, no crashes so far, but when I want to fly with my small group of friends online my FPS will tank from usual 60-80 to unplayable slide show of 20 FPS. If I wanted crash free experience and good FPS I would constantly need to swap compatibility mode, which is a no go for me so I just keep it at Windows 10 and slowly but surely reaching proficiency in black magic so crashes are kept at minimum.

Mine are green, we shouldn't drop this it could lead us somewhere.

No, it hasn't been fixed. dcs.log-20210520-160814.zip

That is only partially true, game could manage ram usage better but... truth is even if you have 32GB of RAM or more swap file is there to be your fail safe, without it system would be at risk of crashing and corruption at moment there is no space left in main memory, not to mention many apps commit memory, so basically imagine your programs are using 26GB of RAM that means you have 6GB left at your disposal right, but then you open an app that commits to 8GB and will probably use only 3GB while running, guess what you will run into virtual memory low error because you are 2GB over your commit charge, now you can try and argue that program is written badly, maybe it is but even if you had swap file in this case nothing would be written to it unless you go over real usage of 32GB or close to it but you wouldn't experience any virtual memory low related error if you had swap file. Yes, to contrary belief if you have swap file OS won't just write gibberish to it when it doesn't need to, so drive trashing isn't happening. DCS.exe is currently using only 11GB of main memory but is also committed to another 11GB, basically saying hey I might need that memory and I need to have guarantee that it will be ready if needed, program is basically guarding itself from possible memory run out. I also have 32GB of RAM but guess what my commit charge is 34GB with DCS open, so without swap file I would be no go.

Hornet will steadily but surely become an alien ship if forum doesn't get locked Jokes on the side if there is real world data to prove it... I just hope if ED actually makes FF MiG-29 that it will be true to what we know about it not being undermodeled or overmodeled.

Yup, but still not a word if they know what the issue is or if they are trying to fix it.

Did you try setting them on Ultra, that alleviates the issue for me, it's still there but much less noticable.

Guess we are all too much up to date Windows, graphics and other drivers... everything is up to date. I tried Win8 compatibility mode and so far so good. I don't see much difference in load times on my machine. EDIT: ok launch and shutdown are a bit longer than usual (shutdown especially, lasts around 8-10 seconds of black screen), but mission loading is pretty much the same

Cleared everything, crash on mission reload at first game launch after deleting those caches.

If they fix it for VR be sure it's also fixed for 2D. Blurriness, jittering is stronger in VR since you have two 2D scenes being rendered and clouds (due to the way they are currently rendered) jitter/move a bit differently for every eye that makes the effect much more prominent.

Gentlemen one of us will have to volunteer and send his PC to ED

You have to account that majority of people that don't have any issue won't search for nor vote in those polls. But it is for sure widespread occurrence and is confirmed for some time now not to be our systems but indeed something in the game code/possibly windows etc. There are people here that have machines with same hardware and software that was installed on the same day, yet one crashes and other doesn't.

Did you try this?

That escalated quickly

Khmm, I don't want to be devils advocate here, from BIGNEWYs comment this seems like we are few in numbers, they don't want to disclose numbers but I don't have any reason to doubt that we are minority, so I wouldn't be too optimistic about hotfixes considering this one

I guess that is statistic from "send crash report" that you manually have to do when the game crashes? On the other hand if they are sent automatically at every crash that statistic is more valuable, can we get official statement on how many % of players are experiencing crashes with 2.7?

Log is using UTC time zone

Cannot be done "properly" with DX11, we will have to wait for Vulkan on that one.

I am deleting FXO to keep me going from second mission crash problem almost regularly (when the crash happens) I didn't delete them when I updated to newest beta yesterday but since their deletion can trigger crashes back, I won't touch it for now... Had black boxes with every 2.7 version so I don't believe that is the case

Just checked event viewer to be sure and in my case (second mission loading) d3d11.dll and dx11backend.dll crashes, those Security Events aren't timed with them at all. Nothing in my event viewer happens before or after it's just the application that errored out. Btw my current windows problem reports page mind you this PC is running all kinds of software and is not purely used for DCS yet only thing that is crashing is it... but as you can see I am currently having pretty good stability time since 3rd of May

dcs.log

Yup, Vega 64 here, I also still see them from time to time

Electrical system, INS drift, Shkval, vector based HUD textures so they don't create artifacts etc... those are not listed but hopefully worked on also...

I saw that movement even on demo videos before their release in Wags showcases and I was instantly worried about their implementation, now in 2D if you set clouds to ULTRA at least for me effect is much more subtle and almost non existent in many cases compared to jump fest that occurs on low, standard and high. Fundamentally I think this issue comes from the way clouds are rendered/updated and that means either a complete rewrite with a different idea, yikes, or some kind of smart way to improve it without big performance impact (that is the main problem I think, it can be stopped with higher update rate but then requires much more processing power). I think DX11 is barely breathing for some time now and is in need of replacement ASAP, low level APIs are the way to go especially in complex sims like this one surely is.