Crash Master

Does one delete the folders or the contents? Or does it matter?

Thank you sleighzy - deleting the metashaders2 folder seems to have worked. What is that all about?

Thanks for the suggestion, but that does not seem to have resolved the issue. I also removed Malwarebytes from my PC as a precaution. Here is the latest log file: dcs.log-20241001-160735.zip

After updating today, I attempted to open DCS and was able to get as far as Main Menu and began an instant mission but crashed before mission completed loading. Malwarebytes did not like World\bin-mt\DCS .exe so I put it in the Safe Files list (never happened before today). Upon attempting DCS restart, I get to the "15 Years of DCS" splash screen, then crash. Tried slow and fast repairs to no avail. Most recent log attached. dcs.log-20240930-235308.zip

These are all outstanding, congrats to everyone involved. Tough duty for the judges!

The problem is a failing drive which I have since confirmed with additional testing.

Thanks so much for your help, Flappie. Comforting to know there are responsive, knowledgeable people here to help.

FYI - I had my antivirus turned off when working on it yesterday. I just installed on my OS C drive and everything works perfectly, so perhaps it is a drive issue. I'm happy to leave it there for now, but my concern is running out of room, which is why I had it installed on a separate drive by itself. I've been thinking about replacing D with an SSD anyways, so this may be the time. Ironically, I tried to uninstall DCS from D and the files were corrupted, so I couldn't access .bin or even run a repair, I can't even uninstall using Windows. Just for fun, I thought about reformatting D and simply copying the DCS files from C to D, just to see what happens. I don't mind spending the time, do you see any danger in that?

So, the full repair worked, and I was able to run DCS with the included aircraft and terrain. I decided to start installing my modules one at a time to continue testing, and after installing the first one and testing with the different default graphic settings, performance got increasingly worse, until the load times became unbearable. I did another slow repair and tried to test again with no luck. The time from launch to main DCS screen was 16 minutes. After selecting a mission, the load process took over 30 minutes and nearly completed until it crashed. That report is attached. I also installed the exes you suggested with no noticeable change. I think today I will install on my OS drive (C:) just to see what happens. dcs.log-20240328-002535.zip

Thanks for your response. I checked RAM and everything seems fine. Attempted another clean installation this morning and got the error message shown. Retry does nothing and cancel just takes me back to desktop. Did a cleanup and quick repair with no change. Running a slow repair right now, but that will take a while. I was at least able to get to the main DCS screen prior to today. Any ideas?

I've been running DCS for many years without significant problems until I did a clean install a few days ago and have not been able to get DCS to launch since. Have done multiple Uninstall/installs, cleanups, repairs (short and long), disk repairs, anything I can think of. Drivers are up to date. I did see that, even though my installation directory is D:, several files are being installed on C:, including Logs, Metashaders2, Config, etc. I've never noticed that before, is this normal? Attached logs from several attempts this morning. dcs.log-20240325-173541.zip dcs.log-20240325-160905.zip dcs.log-20240325-161630.zip dcs.log-20240325-162300.zip dcs.log-20240325-171059.zip

Does the a/c you're in have the "aged cockpit" option in settings? Is that what you're seeing?

For me the issue is different than cockpit reflections and has more to do with glare from sun and bright clouds, and is more prevalent in VR than 2D. The tendency for glare to completely wash out the HUD is normal, I suppose, and should be expected when flying "toward the light", but it just seems a bit excessive, especially in OpenXR. As I said earlier, it seemed more tolerable in WMR for Steam. I haven't seen any other complaints about it here, so maybe it's my settings or me just being whiney. I don't know how to get a screen shot from VR, but I would if I could.

+1 from me. I spend most of my time in the A-10C II and, depending on the angle of the sun, it will completely wash out the HUD display. Does not seem to be as intense in Steam VR I've noticed.

RTX 3080 Ti

I've found that you can also turn off Terrain Object Shadows in settings. Spoke too soon; this does not work. The solution is to disable SSS as has already been mentioned here several times.

Can't help you with re-size, but the game speed settings do show, in the far right corner in red text.

Try LCtrl+Y. That is the info bar toggle. Is that what you're looking for?

Based on my limited collection of aircraft modules, I see the F-18 and F-15 (Flaming Cliffs) each have simple Instant missions (Cold Start, Hot Start, Free Flight). There may be others, but this is what I have.

It's been some time since I've flown the P-51, but I recall experiencing the same thing, constant nose up pitch that would not trim out. I discovered swithing the controls from "Easy" to "Real" allowed me to trim it out. Could that be what your experiencing?

G2 - exactly what C3PO said above. FOV concerns are overblown IMHO

Under controls in the UI Layer: Time accelerate = L Ctrl + Z, Time Decelerate = L Alt + Z, Time Normal = L Shift + Z

Make sure yourtrigger is correctly mapped in controls. Sounds dumb, but it's happened to me before. Does it fire when you press the space bar on your keyboard?

I had the same issue, but there is a setting in the game options that allows you to hide the stick, which is what I had to do before I began in VR. BTW, there's no shame in using Active Pause, especially when learning.

I've been using a G2 very satisfactorily with less horsepower than you have. I highly recommend it but do check into the AMD chipset thing, as it is real. I haven't looked lately, but there may be a solution for it by now.