sabreman

I've flashed 4 different version of the bios, no dice. I've also pulled another older video card from a different machine and that didn't work as well. At this point I'm giving up. bought a new motherboard on amazon, It'll be here Tuesday. If that doesn't fix it I'll return it and buy a new power supply. Wish me luck I guess.

So I have ran every single test available and haven't had a single error or issue. At this point I genuinely have no idea. I'll give flashing different bios versions a shot for sure, but I'm at the point where I think I just need to start swapping parts and seeing what works (my money is currently on motherboard).

So I have been able to 100% confirm it's a hardware issue. I ripped the SSD out of my computer and hooked it up to an old laptop through a seta>usb hookup, and after windows updated it's drivers (and a restart) DCS worked flawlessly. So now I at least know that it's neither the drive nor software. The hard part comes trying to figure out what component is actually bad. I did swap my two ram sticks around to see if that would do anything, but no dice, also made sure everything was connected well. I've now switched to testing with OCCT (thanks DCS support for showing me this app exists!), so far I've hit all of the standard stability tests for like 5-10 minutes without any errors, so I'm gonna switch to running them all for at least an hour at a time to see what breaks. Anyone have any insights on how to troubleshoot mysterious hardware issues that only show up in very specific circumstances? I'm fairly certain it's not my GPU or CPU, and I've definitely heard of both power supplies and ram chips causing really hard to diagnose issues..... Edit: As an small update, second memtest passed with zero errors overnight, so at this point I think I can confidently rule out ram. I'll still run all ram-related tests from occt to be safe though. Currently running the power supply test while at work, we'll see what happens.

An interesting development: While messing with the mission editor, I can use it in "SAT" view mode all day, scroll, zoom, place units etc. But DCS continually generates "DCS has Crashed" dialogs in the background as I do things. The attached log for instance has like 10+ "crashes" in the ED terrain dll, while I was able to use the mission editor without issue. Edit: For <profanity>s and giggles I tried multiplayer again, and the game actually loads in and connects. I can actually spectate, and as long as I dont move around too much It runs. If I hit F2 to try and spectate a player it'll usually crash, though one time I managed to spectate like 3 different players for about 2-3 minutes before trying to load into a su-25 and crashing then. Attached is the new log file. Still seems to be crashing due to the terrain access violation. dcs.log-20251020-204528.zip

So, just for fun I did another full wipe + reinstall, this time actually wiping the disk with zeros instead of just deleting the partitions. Still no dice. To answer the previous questions: Originally this was a local account. On re-install I used a microsoft account, then switched it to local. Both times the games crashed. Yes the account is an admin. I've properly set the exclusions, you'll find a screenshot of the windows defender menu attached. The drives SMART checks good, also attached (I've also manually checked for trouble codes in device manager, there are none) My old windows install, before all this happened, was on a different drive. It started having these issues, so when I reinstalled windows it was on this new drive, so this problem is following the Windows + DCS combo, not the drive. I didnt see any 1b0 errors, but attached is a screenshot of the most recent event viewer output for the DCS crash. My IGPU is currently disabled in the BIOS. Attached is the newest crash log from my new new install. This continues to get a big fast shoulder shrug from me. At this point the only thing I can think of to do is to start swapping components with other machines in my house, which I would MUCH prefer not to do because everything else runs linux and this computer is packed tight. I'll keep fiddling with things and report back. Edit: just noticed I accidentally ran MT version last time, ran the normal one just to be sure and obviously no dice. dcs.log-20251020-193948.zip

Disabled it, but no dice still. Here's the newest crash log. dcs.log-20251019-165852.zip

I ran it once during this troubleshooting process as admin. I got into the game both before and after that, and have wiped the saved games folder many times. No, I did not have that file, though creating it did not have any effect.

Just as a troubleshooting idea, and because I have literally no idea what else to try, I made a brand new DCS account and tried the game with it (and everything but the base free modules removed). Same outcome, no dice.

No. These issues started on my previous install with outdated BIOS drivers. I hadn't fired up DCS for like, 2-3 months and when I tried this whole shtick kicked off. I thought a complete wipe would solve it, but here we are. Quite the problem.

I've reinstalled my whole OS friend, which included a full drive wipe, and yes I have ALSO tried renaming the folder. As a follow up to my last post, it seems that the crash is now somewhat random. The same mission now crashes on lodaing world assets or whatever. Seems like a race-condition of some kind.

Any ideas? I've been unable to play DCS for a few weeks now because of this issue. Edit: Out of desperation I've un-installed the hornet and reset all my settings to the lowest possible, and the game loaded! I got like 4 frames of gameplay before it crashed again. Note, this was the first frogfoot instant action mission, which I've tried before. However, this is definitely progress and the new crash log is attached. Seems to be the same terrain engine error as before. I'll keep editing this post as i keep troubleshooting. dcs.log-20251018-174927.zip

I have completed all of the above steps to no avail. XMP was not enabled. And yes, my previous install was also on this update. Attached is the most recent crash log. dcs.log-20251017-030541.zip

I've done that, and have the same result. Attached is the new crash log. dcs.log-20251016-215945.zip

Good Afternoon, Like the title says, my game crashes at this step regardless of what aircraft, mission, server, etc I'm using. I'm able to get into the game and use the mission editor, but trying to actually start anything results in this outcome. Attached is my crash log. This is on a brand-new (clean formatted) and fully updated windows 11 install with a brand new DCS install. The only module I have currently enabled outside of the default free ones, is the hornet. I have ran memtest and verified that my RAM is fully functional. I'm on the Latest BIOS drivers and NVIDIA drivers. Page file is system manged. Both the Saved Games, and the main DCS folders are exceptions in windows defender. This computer with the same hardware, used to work flawlessly a few months back. Please let me know if you need more information. Edit: I've now confirmed this is a hardware issue. See page 2 for more details. dcs.log-20251016-205211.zip

I'm pretty sure I've had this happen with hostiles as well, I'll try to reproduce it tomorrow.

A fairly consistent bug it seems, but the bottom donor half of the hafu doesn't seem to exist on the attack radar page a good chunk of the time. Sometimes I can get it to show up, but most of the times It's just the top half. This happens in both SP and MP, here's a pretty crappy screenshot of a fastmission with both the radar and SA page up, as you can see the friendlies are fully IDed by the DL but I can only see the top half. Attached is the super short track file, you can see both the intended behavior and the bug happening too afaik. Edit: Note that contacts that my radar doesn't see, behave as they should showing a small hafu of the appropriate shape/color as the donor information. sa.trk

Honestly, I dont understand why people are trying to argue with a real F-14 pilot about this. The point of DCS is to simulate these aircraft with as much accuracy as physically possible, including all the sounds. So if you find the sound annoying touch shit! This is how the real deal sounded, according to people who are MUCH more qualified to talk about this then anyone else on these forums. Bottom line: This is accurate. If you don't like it either turn it down or mod it away.

Yeah everything works the same way, just dont do step 1.

Easy peasy solution: 1) Go into SRS settings and set "Allow INCOCKPIT DCS controlled PTT" to on 2) Go into DCS controls settings, RIO controls, Radio category and bind "Mic button UHF" to something (also Mic button ICS if you wanna use SRS for ics) 3) In game, turn on your radio (set it to t/r or t/r+g) then select the channel you want to use. Or set it to manual and tune in the frequency. Remember, the UHF repeater displays the pilots radio settings, not yours. 4) Hit your newly bound PTT button and you'll be able to talk all you want. If you wish, you can go to your "XMTR Sel VHF / UHF 2 ANT" panel (right bellow the CADC panel) and switch what radio you talk on. UHF 1 will let you talk on the pilots radio (he's still in control of the frequency and it's power state though), UHF 2 on yours, and both on both.

Shame I have to post in such an old thread, but the same thing is happening to me.

Two quick bugs I guess: The mach indicator goes from 0.5 to 1.0 in like, 2 intervals. Considering you spend most of your time bellow mach 1, this seems totaly useless. The RWR doesn't make any sounds at all. Is this intended behavior?

According to the manual, you should be able to modify the 3 built-in NDB frequencies using the mission editor. However, when selecting a mig-15 in the editor, I don't even have a "frequencies" tab. Here's the relevant area from the manual:

Well I just went and tried it again and it worked fine. Not sure what was wrong yesterday but I waited for a while (not at 100%) and they didnt turn on. Oh well, good to know though.

As you can see from the bellow picture, I have the UV Rheostats up to 100%, but none of the "glowy" elements for the instrument panel are glowing. This makes it almost impossible to fly at night since you can't see the attitude indicator The lights you see are the normal flood lights and their dial is on the left panel.

This is a really nice quality of life improvement (and your hud mod). It really should be included in the official updates!