sleighzy

I dropped your zip into the DCS log analyzer and got the following output: Memory Timing Issues Remove any overclocking (XMP) from your RAM. Your System ran out of Memory Increase RAM or add a custom page file Your GPU ran out of VRAM Reduce Terrain Textures and Shadows. Doublecheck your pagefile. Given the amount of RAM you have on your system, and your video card, this can be a little unexpected. However this is definitely evident in the log file. I would recommend deleting the Saved Games\DCS\fxo and metashaders2 folders as there have been occurrences in the past with older cached textures causing out of memory errors even with systems with large amounts of VRAM and RAM. Disable core parking. Additional advice: Verify that this is configured correctly in Windows: Game Mode disabled Hardware accelerated GPU scheduling disabled Core Isolation disabled Remove the OH6GunnerExport script for performance reasons. Follow the above, see if this resolves anything, and if not then drop another log file. Note that the DxDiag log file in the zip indicates issues, may be similar, with other processes on your machine. There's a few for GameInputSvc.exe (Windows Game Input Service).

@Nightstorm, attach your DCS log file after replicating the issue.

Have you tried rolling back to 566.36? seems to be a stable one folk are using. This does not have DLSS4, but you can just replace the nvngx_dlss.dll file in DCS with an updated lib that does. Can use DLSS Swapper pretty easily for this. Still need to update the preset to use though. I’d say take one of your DCS log files when a crash occurs to the Eagle Dynamic DCS Discord server and drop in the #dcs-log-analyzer channel. And/or attach here. Might get more feedback re: reason for crashes. You may have some dcs.log.<timestamp>.zip files from previous crashes you can also drop there.

You've applied an affinity mask to your game shortcut. This may not be correct, I don't know where you got that F value from, as it looks like you've made most of your CPU unavailable. I would seriously remove that. Command line: "C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt\DCS.exe" --affinity=F --restarted system affinity mask: 111111111111111111111111 process affinity mask: 1111 CPU: AMD Ryzen 9 5900X 12-Core Processor [2x L3 caches] CPU has uniform cache size 32 MB (per cache) all CPU cores have the same efficiency class 0 CPU cores have different performance classes: [8-9] logical cores with performance class 9: {2, 3} logical cores with performance class 8: {0, 1} common cores: {0, 1} render cores: {2, 3} IO cores: {} unavailable cores: {4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23} You also have a number of mods. Remove those and run a slow repair of the game along with the option to remove extra files. Delete the Saved Games\DCS\fxo and metashaders2 folders as well. Note, this may not resolve the issue...see notes further down re: memory timing issues. The DxDiag report has identified the following issues. Application Errors SimShaker for Aviators Beta.exe: was hung for 9.71s and killed, was hung for 12.62s and killed DCS.exe: was hung for 5.83s and killed, was hung for 12.08s and killed Memory Timing Issues Remove any overclocking (XMP) from your RAM. The memory timing issue crash seems to align with the shutting down of the game in both log files so potentially the cause here. You have 64Gb of RAM. Is this 2 x 32 or 4 x 16? There's also an error with the SimShaker script: Error attempt to index a nil value Line 43 Script C:\Users\mark\Saved Games\DCS.openbeta\Scripts\SimShaker-export-core\Protocol.lua

Please raise your own crash report and attach your DCS logs vs. using somebody else’s post, your issue may be completely unrelated.

This log was also after the multiplayer servers listed. TacView recorder was also loaded at this point hence also mentioning it. @Shimakaze514 , this log shows that it took roughly a minute from launching DCS to getting the list of servers up. This does not seem unreasonable. The fact that your PC froze and then rebooted itself following this (if this is what is meant by autorestart) would potentially point at some deeper Windows issue. Hopefully the DxDiag report contains more info.

Correct, the main menu freeze is weird and cause is still unknown. However, if somebody drops a log here with additional stuff that should be addressed then I’ll call it out so they don’t have issues further down the road. Can you run the Windows DxDiag tool, save the report, and then attach that here also. also when you say “auto-restart” do you mean that your Windows reboots itself automatically?

I'd recommend cleaning up your installation first to get it in a known state initially, should be done after every update. Remove your custom mods Run a slow repair with the option to remove extra files Delete Saved Games\DCS\fxo and metashaders2 Play the game and then reapply mods afterwards and delete fxo and metashaders2 again. You can use something like ParkControl to check if your cores and being parked, and unpark them if so. Log analyzer called out a few points: Remove the OH6GunnerExport script for performance reasons. If you have FPS issues, try turning off VSYNC in graphics settings. Set Clouds to High. Set Water to Low. Disable civil traffic. Decrease Visib Range to Ultra or lower. Turn down Anisotropic Filtering. Enable Full Screen mode. Set Shadows to Medium. Decrease Terrain Textures. Upgrade your OS to Windows 11 to better support your CPU or disable cores 12,13,14,15 in Windows or Process Lasso Note: this comment re: disabling cores came from the DCS log analyzer, I would not use this as your first tool, sort out the other items.

This log shows a few interesting things: You only have 16Gbs of RAM....kind of. It shows 14043Mb which is a weird number. Might be worth looking into that to ensure no problems there, e.g. run RAM tests. Don't know what kind of performance you're getting in multiplayer. You have your preload radius set to 100000 which is quite high for your specs. Given you only have 8Gb VRAM on your GPU and 16Gb RAM (kind of) I'd drop that right down to 30000 You have a 58Gb page file set. That's larger than the general recommendations, e.g page file being roughly double (and a half) of physical RAM. Is this on your fastest SSD with at least 10% free space remaining? Disable TacView as well Enable fullscreen.

Please attach your C:\Users\username\Saved Games\DCS\Logs\dcs.log file (may just be a text document named "dcs" if your Windows is hiding file extensions). Attach a screenshot as well of what you're seeing. Are you using the Meta Link app for connecting? And this is freezing for 2D as well, or just VR?

You need to attach a DCS log file for review as it may provide more insights as to the root cause. I also wouldn’t just start disabling CPU cores if you see them at 100% as you’re reducing the amount of processing power of your PC. The menu etc. is also not multithreaded so results will vary. If disabling half your CPU with Process Lasso didn’t solve your problem then I would revert that change for now. It may mask further underlying problems. Revisit it if needed. Provide a log first.

Turn off the guardian, or reset it in a position so that when learning forward you aren't getting close to it.

Speaking of the bin-mt directory this is now just for backwards compatibility as DCS is all multithreaded. Use the DCS exe (or standard DCS shortcut) for the one in the bin directory. There were also known issues with Winwing MFDs if running DCS as administrator so if you're using your own shortcut then make sure "Run as Administrator" isn't ticked on the compatibility tab of the shortcut. The log analyzer also says to disable hotplugging in the DCS controls settings. This may already be disabled (disable if not) in which case it can be due to USB power issues. I can see unplug events for TrackIR in one of the logs. You mentioned a PSU power problem, and have a lot of peripherals plugged in. Also turn off power management in Windows Device Manager for your root USB controllers. Leg2ion touched on this above. Could try unplugging these additional peripherals and see if the issue persists.

Numerous varying issues showing up in those logs. There is one from your Winwing scripts, although a rename of the Saved Games would remove that script, I don't know if it's related. The Winwing script errors seem to show up around the same time and the error stack trace of the crash does indicate doing something with lua. This is the Saved Games\DCS\Scripts/wwt/wwtExport.lua file. Other issues from the DxDiag logs: Memory Timing Issues Remove any overclocking (XMP) from your RAM. The DxDiag logs show issues for Winwing, TrackIR5, SimAppPro, WWTStream so potentially a larger problem overall. Repair your Windows by running the following each of the following commands and then restarting your PC. These need to be from a command prompt run as administrator. dism /online /cleanup-image /restorehealth sfc /scannow Also noted in the DCS log analyser from the DxDiag logs: Microsoft Update / Store issues Make sure you have enough free disk space. (based on your logs this looks to be fine) Run the wsreset.exe command in a command prompt to reset the Microsoft Store cache. I also see you have dropped your own dxgi.dll file in the bin-mt directory, there's only a couple of reasons for doing this, but could potentially remove till this is resolved.

This log is full of errors and mods + texture changes so makes hard to read, and muddies the waters to know if the log contains a root cause. When you say you removed the mods did you delete them from your Saved Games directory and then also delete the fxo and metashaders2 folders in Saved Games? Doing a clean install won't touch the Saved Games\DCS folder so anything in there will have remained. I'd recommend removing all mods from Saved Games and the core game, run a slow repair with the "Remove extra files" option checked, delete fxo and metashaders2 folders, and then provide another log. Additional notes from the DCS log analyzer: Turn down Anisotropic Filtering. If you have FPS issues, try turning off VSYNC in graphics settings. Turn off SSAO. (this is a performance hit with little benefit) If you have stability or performance issues pointing to your GPU, rollback the GPU driver to version 566.36 Verify that this is configured correctly in Windows: Game Mode disabled Hardware accelerated GPU scheduling disabled

Awesome-sauce!! Thanks for the update. Something definitely weird there, will keep in mind for future reference if it crops up for other folk. Changes were made a number of patches ago when the new launcher was introduced so that this was opened when DCS was started, so has been around longer than the last patch. I don't know what Steam is trying to do when selecting the OpenXR option. Stick with the way you're launching it now and you can't go wrong

I don't have an answer at this stage sorry. Can you drop another log here after replicating again given you've made these changes.

For the C++ Redistributables download and install/repair the latest x64 version from here vs the one that ships with the game https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170 Renaming the Saved Games\DCS folder also has the side effect of removing the fxo and metashaders2 folders in there…which is a good thing. You should always delete those if experiencing issues… and definitely after every DCS update.

Sweet, yeah they're on the latest 572.83 version which had 5000 series fixes. Will check the recent Discord channel references on specific versions. Was just a side note, likely unrelated.

Please attach your C:\Users\username\Saved Games\DCS\Logs\dcs.log file (may just be a text document named "dcs" if your Windows is hiding file extensions) after replicating the issue.

Running a slow repair of the game, as well as ticking the remove extra files option, will get it back to a clean slate with needing to reinstall everything. Rename the Saved Games\DCS as has been mentioned previously as a repair or reinstall will not touch that location in case there are any issues there. Can you also drop your DCS log file here for further review. Make sure to load completely into a mission.

Could you drop your log file here as well. Do you run Quad Views (this has turbo mode enabled by default in case this is messing with the measurements that Qcumber is mentioning)? This would show up in the DCS log file to. EDIT: I see in your VR settings screenshot that Quad Views is toggled on, and that there is an exclamation mark beside it. The exclamation mark is fine, but indicates you have OpenXR API layers installed. So possibly you have Quad Views installed, will wait for your confirmation. You can use the Tallymouse companion app to turn off turbo mode vs. manually in the QVF config settings file https://github.com/TallyMouse/QuadViewsCompanion. That screenshot also shows you have Bloom Effect enabled, turn that off if using Quad Views. A lot of the Quad Views functionality replaces OpenXR Toolkit so you could remove OXRTK vs. running them both together. Possibly unrelated but there are known performance issues with later versions of the Nvidia driver and 5000 cards. A number of people have been dropping back to the 566.36 version so could try that as well (could use DDU on the drivers prior to installing 566.36 to ensure clean).

The logs show this is crashing really early on, not long after your peripherals are loaded. You mentioned that a clean saved games works but crashes after putting back your inputs config and options. I would highly recommend adding back just one input at a time in case one of those is causing the crash. Then do the same with the options.lua file. Will help narrow down if there is one in particular. If you find it's just one of them then try rebinding again manually. Running a repair of the game doesn't touch your saved games folder so it's likely this is one of them if it works when clean and crashes when not. I also note that the vJoy shows as being forcefeedback, not sure where that it set but could try setting that to off as well. The DxDiag report in the zip file also shows you have blue screen events occurring on your system. This is the output from the log analyzer: Your system crashes with Bluescreens. The following kernel-events have been detected: VIDEO_TDR_FAILURE,VIDEO_ENGINE_TIMEOUT_DETECTED Remove any overclocking (including XMP). Run SFC and DISM to check your Windows. Check for any updates of your BIOS or chipset drivers. For the SCF and DISM checks you can run the below commands using a command prompt run as administrator. Run each command separately and then restart your PC. sfc /scannow dism /online /cleanup-image /restorehealth The error trace also references VCRUNTIME140. Not saying that this is the issue but you could try repairing that as well. Is a 1 minute job. Just download the latest C++ distributables from the Microsoft site and run the repair option. https://aka.ms/vs/17/release/vc_redist.x64.exe The link above is the direct download of the x64 version from the Microsoft site if you're worried about running that exe: https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170

Remove all your custom mods and run a slow repair of the game, choosing the option to remove other files. You only have 32Gb of RAM. Add a custom page file on your fastest SDD, remove any system managed ones, with Initial and Max values of 32768, click Apply, and restart your PC. Turn off / remove TacView. You have a low spec'd machine and this will be a performance hit. In addition to this your TacView is currently writing to a OneDrive folder which if synch'ing to the cloud could have other performance issues. Drop your Preload Radius from 100000 to 30000 - 60000. Delete your C:\Users\username\Saved Games\DCS\fxo and metashaders2 folders. This is from within VR. Does it work fine in 2D?

What's the gold shield in that VD overlay beside the bitrate? Do you have like secure encrypted network connections enabled (I can't remember the specific VD setting). Turn that off, or whatever you have enabled that is causing that shield to be displayed.