Special K

If you use FreeSync on the one side with trying to reach 144 Hz or anything that is a divisor of it, and you put the game on 60 Hz, where it has to be 72 at least, 2 things are fighting against each other. Try setting the slider to 72 and see if it also happens or disable FreeSync.

First - the F/A-18 does not reset trim on WoW but on gear up, according to the documentation. Second, it does that only, when flaps are on half. Taking off with flaps on auto will not reset the trim, thus you stay with 12 which you can easily monitor on your FCS page. I get the report of Ahmed though and from the looks of it, it is already being looked into.

Happy to focus on experiences and stuff that eats up memory and work on that. I am also happy to report these kind of things and bring it to the right place. Can't guarantee for any fix / implementation though. Some things sound easy but are in fact not, some might be but will be killed by priorities. But I am happy to support that fight as I fully agree that it is a disadvantage for DCS itself. People want to play and not everyone has a beast of a machine at home.

Guys, as I commented below that video already, what you are doing here is black magic. You are misusing the Windows scheduler to "magically solve" an issue that DCS has, namely not freeing used memory properly. Whenever you unfocus an application (ALT+TAB), you tell Windows that it is not the #1 priority application anymore. Now the Windows memory management will mark all your nice memory pages that you have used a second ago as candidates for swapping. As DCS is the main user of your RAM and VRAM at that time and Windows is eager to free some of that up, it is very happy about your move. It's doing what you ask it to do - freeing up memory, in this case either for the application that you swapped to (youtube, notepad++, your file explorer, whatnot, something that was used before you started DCS) or your DWM. It now loads that into memory. Now you switch back to DCS. What happens? Well, it depends. If you have lots of RAM, in first place nothing. It will mark the memory pages from your DWM, Notepad, whatnot as disposable. Whenever you now need RAM for DCS, you'll get it much easier. Until the point where you need that stuff again, that you just swapped out earlier. Doing it with a lot of RAM might not even get you to the point that you see what you are doing. It's the same "black magic" trick that someone put out about a year ago where he said, giving the DCS process less memory solves issues. You just give DCS less memory to play with. On the other hand, if you **don't** have enough RAM, you're doing something really really bad to your system. The amount of swapping with DCS is already ridiculously high and you force your system to do even more of it. This will result in lots of swapping, even more wearing of your disks, etc. Don't get me wrong, I appreciate the ideas you guys develop to get rid of long standing issues and I fully second that we need a better memory management INSIDE of DCS. But this is not the right way of doing it. There is no magic key that frees up memory inside of DCS. This magic key only asks Windows to move it out of sight for a while.

Your DCS is not running out of memory. It crashes somewhere in the renderer. But you can always increase your pagefile. That would show if it is a memory issue or not. Make it 65536 initial and max and lets see. And check if your GPU driver is up-to-date.

Can you try another thing: Turn off SSAO. Consider using DLAA. Set Shadows to Medium. Turn down Anisotropic Filtering. Set Water to Medium or Low. Set Preload Radius to max. 60000. Delete %LOCALAPPDATA%\TEMP\DCS.openbeta

You still have mods in: ECHO19_F16,ECHO19_FA18,Tacview,DCS-SRS I'd recommend removing the ECHO19 stuff and Tacview for now. Besides that, you should lower your Preload Radius to 60000. Your Windows needs an update, too. Delete Saved Games\DCS(.openbeta)\fxo and metashader2 after you fixed the above and try again. Do you use Reshade? If yes, remove it also for now.

Yes, you guys need to be on MT and have a recent GPU driver (>> 500) installed. And an RTX card. Deleting options.lua made it available for some people, too. We still have people where all that is true but DLSS doesn't show up. The message in the logs states that DLSS isn't available on this hardware, where it truely is. If anybody has an idea, would be highly appreciated.

Can you try the suggestion I posted above with the DNS flush / ARP cache clear please? 400 can come if your client sends a wrong routing, bases on DNS changes that might have happend on the route. That's what I suggest atm, but it's not verified properly yet.

If some of you still have this issue, can you please try the following and report back if that helped: Open a cmd.exe as Administrator and run the following two commands: ipconfig /flushdns arp -d Then reboot and try again. Report back please, if that helped. We're only talking about error code 400, nothing else.

That's a setting in your BIOS. Hyperthreading. You see it at your CPU settings.

Can you be so kind and try disabling HT as we are at something rn, which "might" help in your case, too?

And one additional thing, can you disable Hyperthreading please in your BIOS and try without?

You always need to talk about the whole system. Many people play with a 4090 without issues, so it must be something in your specific combination. Stuttering has 2 main causes: - CPU - Swapping So you are either swapping to a slow disk (HDD or even a SATA SSD is too slow for a proper pagefile if heavily used) or your CPU is hitting its limits. If you look at this picture: https://discord.com/channels/542985647502393346/551106084157390874/1124643034638852157 you see that one of your threads is at 100% already. This can cause the stutters you see and the FPS limitations. Can you send me a recent dcs.log, dxdiag.txt and the following files from your Saved Games\DCS(.openbeta) folder please: - Logs\dcs.log - Config\autoexec.cfg - Scripts\export.lua If some of these files don't exist, please give feedback that they aren't there.

Can any of you guys provide a dcs.log of such an incident please? I'd like to see if any error is logged. If you can create one with debug logging enabled, that would be appreciated.

Haven't seen any DM, are you sure you got the right Special K? Check in the ED help channels, there you'll find me quite easily.

Is that an X570 Pro? Can't see the Mainboard version in there. Your system has some serious issues. The dxdiag is full of Bluescreens that are being logged. Can you DM me in Discord? That's easier than in here and we can talk German over there. Refer to this report please as I have too many people I'm taking to.

If you let it create a new folder, all is defaults in there. If you use the old one with -w DCS.openbeta_server, you'll use the existing config.

This is not a software issue and not related to this bug. This is a hardware issue with your PC. Can you please run a tool named dxdiag and save everything by pressing the respective button. That creates a file named dxdiag.txt. please provide that, so we can have a look. Which PSU do you have?

Post your video, so people can see what you're doing wrong. I couldn't replicate what they said, neither in this mission nor in any other. They won't accept that they are not flying well. In their eyes it's the fault of the plane or the systems or the mission. As neither a bug report at ED nor a tester taking his time to try to replicate the "issue" came to a conclusion that means that they are right, they decided to get their confirmation in here. I'd recommend watching their video. It explains everything in the first 3 minutes of watching.

Well, MT is using your system much more than ST ever would have done. You were just lucky that no other games or programs created issues so far, which should have been very likely with running the (old) setup with XMP.

You run mixed RAM, you can't run them with XMP. Your system will be instable. That's why I suggested to remove the 8 GB. You might want to get a larger SSD, too. If you don't have enough headroom for a proper pagefile, you might run into issues, too.

Have you changed the pagefile already and is your RAM configured using XMP?

Ok, so you only want one pagefile on your fastest SSD. I'd recommend even 32 GB. And you want to have 10% of freespace. What puzzles me more on your setup is the small PSU. 500W isn't that much and below the recommendations of the hardware you use. Can you run a tool named dxdiag please and press save everything at the bottom. Then send the generated dxdiag.txt in here please.

You're hijacking another thread here. And you say, you have a hardware issue, mainly a bad cooling on your GPU but won't do anything about it and compare DCS with another game where you think it is comparable (which it in fact isn't). So what's that all about? Get your cooling sorted and you're good. I've read your issue that you opened up with ED and came here as you posted a link. That error that you get is definitely a hardware / driver thing. You won't fix it with anything else but working on them. Did you try to remove the driver with DDU already or do you by chance use the studio driver? Here is a link for some more ideas, especially the registry fix you can try, too: https://thegeekpage.com/dxgi-error-device-removed/