Special K

Looking at your dcs.log there is a bit more to do: - Turn off SSLR. - Turn off SSAO. - Disable civil traffic. These are expensive things. Delete Saved Games\DCS\fxo and metashaders2 also. And increase your pagefile. You want at least 32, better 48+ GB on your fastest drive. Only one pagefile please.

No, these settings are all Windows. Do NOT disable any cores, do NOT use Process Lasso anymore on Win11. The MT stuff is running quite well now without.

@Panzerlang I see a lot of Bluescreens in your DXDiag and that you ran Prime already (which crashed also). It looks that you have some timing issues. Have not checked the latest BIOS for that board yet, but that is worth to check. On the other hand, check please if you have - Game Mode disables - Hardware Accelerated GPU Scheduling disabled - Core Isolation disabled - Core parking disabled

Yeah, I doubt you installed it, as you would know, if you did. Can you try one other thing: Go to C:\Users\<yourusername>\AppData\Local\Temp and delete the DCS directory in there. See if that makes any difference.

Try and run a slow repair with check extra files. If it would have been there, it should be removed. Do you use the OpenXR Toolkit by any chance and if yes, did you try to play without already?

Sorry, just saw that. You need to use blanks between the options dism /online /cleanup-image /restorehealth You did not put blanks between them. You just need to cut&paste. And no, it can't harm your PC. But glad that the USB power save did the trick already! (I would still run DISM just to make things clean and shiny again).

You can try that already: Open a cmd.exe as Administrator and run the following 2 commands: dism /online /cleanup-image /restorehealth sfc /scannow What you should also do is disabling any power saving on your USB slots. Reinstalling the VR software including drivers might be a thing also.

The OpenBeta branch ist still there. If you have not changed the branch, you will still have these Directories. Can you try and don't use your controllers (turn them off)?

Send a log from a crash - without the toolkit - without any mods - after you did a slow repair Best is to delete Saved Games\DCS\fxo and metashader2 and %TEMP%\DCS before you do the test.

The question was more to disable it. It seems that you need a specific order to load the plugins in the OpenXR Toolkit, and if you do not follow that, it can crash.

Do you by chance use QuadViews and / or XRNeckSafer?

This. You need to update your dedicated server to the new modular one and you are good. You are still using the old dedicated server that is deprecated now since some month. And you honestly should have run into that issues since month already as others did. @BIGNEWY: He is launching the old dedicated server through the updater. The updater launches whatever is listed in the autoupdater.cfg. As there is always the bin-mt\dcs.exe in, it does not work for the dedicated server anymore, as that does not have a bin-mt folder. If anybody is keen on "fixing" the old server, then the best way would be to amend the autoupdate.cfg only on client installs but not on server installs. I honestly would just move people over to the new one and finally abandon the old one.

They don't have any shader issues. They had a complete different question. Anyway, their log shows that they are recompling shaders, most likely because of either them having deleted fxo / metashaders or the cache is just invalidated because of a config change. There is nothing to worry about shaders in that log.

You have looked at your own log. Discord shows you the first lines of any textfile that you upload. That is not the analysis of the bot... The bot analysis looks like that. The only thing the bot was complaining about is that this log is 2 days old. null

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.

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.