Search the Community

I started this topic to track and discuss challenges with getting the best performance out of the system. I usually test each setting a couple of times. 27-1-2025 Nvidia 571.96 DLSS 4.0 Installed the new drivers. 25-1-2025 Adjusted GPU Overclock Increased CPU PBO Scalar and reduced some of the GPU overclock to further increase fps and frametimes. Time will tell if it also stays stable on the MP-servers. 18-1-2025 Clean W10 Complete reinstall of W10 returned another 5fps and better frametimes. Over the years the system got bloated with all sorts of traces from old hardware that I upgraded (2x GPU and CPU) and software that I tried and not fully removed. The system is snappy and clean again! I considered W11, but there are too many bad stories out there, no clear advantage for AMD and GUI modifications with taskbar etc W10 is easier. The only thing I still notice is that it seems that when I hit the FPS limit some sort of trouble in FPS and frametimes appears. When I stay a bit below 90, like 88fps, it is more stable. 27-12-2024 Current Overclock settings 64GB ----- EXPO: ON (timings default as stated on the DIMMS) 9800X3D ----- Turbo Game Mode: ON PBO: +200 Curve Optimizer: -20, FCLK Infinity Fabric: 2200 UCLK DIV1 Mode: UCLK=MEMCLK, SCALAR 10X 4090 ----- Core Voltage: +100 Core Clock: +120Mhz Memory Clock: +900Mhz, Fan: Power Limit 133%, Temp Limit 84. This GPU overclock is stable and gives me 4-5 extra FPS, even when i am CPU bound. My setup Windows 10 - latest version - Windows 11 will not happen until I will get serious latency advantages. Motherboard: ROG STRIX X870E-E Gaming WIFI Systemboard VR Headset: Varjo Aero SSD for DCS and Windows, separated DCS Settings Most are set to the max. SSS, Secondary Shadows, SSAO, SSLR are disabled; they do not bring much visually. Visibility Range Extreme. I have Visible Range set to High. Increasing this further is not bringing much visual improvement and really takes away performance. MSAA Mask Size 0.42 is my sweetspot. Testing Setup and approach My Windows has been heavily tweaked and optimized and I am currently still running the same Windows I started with 5 years ago. I upgraded my systemboard, CPU and GPU a couple of times but did not reinstall Windows. I think at certain moments in the past I even went too far with tweaking and should have dialed back and better register what I was doing. So a clean install will be somewhere in the near future because I am certain I have left quite some performance on the table. For the basic quick test of setting adjustments or hardware/software updates I start a the default A-10C mission Runway Startup on the Marianas Map. I use Marianas because this mission is quite demanding and quite stable almost from the start with AI not doing much. I let it run a couple of times for 20 seconds and track the performance with CapFrameX to calculate the average FPS, 1% and 0.2% lows of the runs. Many other missions give me 90FPS, so adjusting settings with such missions will not give me noticeable visible differences. If I want to visually see the performance I open up the the FPS overlay inside DCS. I sometimes also open up the new XRFrameTools application to visualize my frametimes. Once a setting looks pretty okay I log into our Wing's Multiplayer server, startup OBS recording and give it a spin to see how it goes. I usually get 90FPS flat in this setup, while running OBS recording. Testing log From now on I will start adding my complete testing logs to this main posting. Where relevant I will add charts to visualize the difference between certain options. Certain tests were eye-openers. It was/is a dreadful process going through all the settings and quite a few settings were insignificant in my case. Frame Times, average FPS, 1% and 0.2% Lows My main goal is to find the ones that will bring more stability (reduction of intrusive stutters) and performance (increase of FPS/frametimes). Sometimes it is like searching for a needle in a haystack. Seeing the settings that made a difference might bring quick wins to others as well. Overall the average FPS is not improving that much by all the tweaking, it is easy though to screw up your system and reduce FPS. But once the FPS are pretty decent it is hard to get substantial improvements. My biggest wins are with the 1% and 0.2% lows, reducing these give a much better overall experience than to have 1-2 more average FPS. The overall FPS can be high, but when you have a few microstutters here and there it is very annoying and for me breaks the immersion in VR. Caution Please be careful, not all what works for me might work for you. Do everything at your own risk. I had some crashes, especially with the overclocking, so always make backups and restore points. I also don't have my overclock software start automatically anymore when tweaking, because that also caused an issue once causing me to keep rebooting into a crashing configuration. null null null

Hello everyone, DCS is non stop crashing on me. Sometimes one thing works, then it crashes again after getting it going. then the fix won't work. Search for hours on forums and you tube videos and sometimes find another solution that works once or twice. One of the last crashes, I noticed, that I changed resolution to my projector and the game crashed. Changed the resolution back and the game work for a little bit. I have played with that resolution setting for hours before and had no issue. If its not one thing is another with DCS. I tried numerous things including reinstalling DCS, Windows (back and forth between 10 and 11), Drivers. I have set my page file, run as administrator, set DCS app to high performance in windows and nvidia control panel. Spent more time probably trying to fix DCS and get it working then flying at this point. This game is so awesome and I love flying, but its getting close to wanting to give up on DCS altogether. The these crashes are on start up, never while playing. It never gets past the LOGO on startup. Doesn't go black, just Logo pops up and then after 5 - 20 secs crash advisory window pops up. I know DCS is a delicate game and seems numerous people have so many of the same problems while others no problems at all. I'm not sure if its the same issue or a different one at this point but can someone take a look at these crash files and let me know if anything sticks out to them or something I should try. info on my pc: RTX4090, AMD Ryzen 5950x, 64gb of ram, ROG Crosshair VIII Formula MOBO, 1200watt PSU, 5 virpil hotas and panel devices (powered by USB hub), Winwing MIP( consisting of 4 devices and 3 MFD screens. Powered through USB HUB). TrackIR w/pro clip. DCS open beta (i had numerous crashes when on stable too) Thanks everyone, Cheers. dcs.20230214-225913.crash dcs.20230214-225913.log dcs.20230214-230130.crash dcs.20230214-230130.log dcs.20230216-041045.crash dcs.20230216-041045.log dcs.20230216-041741.crash dcs.20230216-041741.log

Hello, since we mostly share the same hardware components and peripheral drivers like Virpil's, logitech's, AMD's, Thrustmasters' and so on, we can build similarities. Has anyone had failed Win10 updates lately, in particular 05-2022 KB5013942? Cheers

NOTE: I do not believe this is a DCS defect, however this behaviour commonly occurs when in DCS Problem At least twice a week (at times much more - i play DCS every evening) and within the first 15minutes of a SPlayer VR DCS session the following has been occurring over the last year - Black Screen, Fans 100 percent, hard-reset or power-cycle is the only option to restart (12VHPWR sense pin LED indicates normal signal) History I first encountered this issues last year with a new gaming rig however windows event viewer was reporting WHEA errors - in response i RMA'd the 4090 which turned out to have bad capacitors. About 3 months after installing the new 4090, i again started to encounter the same behaviour with similar frequency and symptoms. Just prior to black screen event, the Windows Event viewer reported the nebulous and useless Event ID 56 ACPI 2. I was able to eliminate this event from being reported by Windows by setting NVCPL to prefer max performance and restart (no fast start) PC prior to any DCS session. Over the last 10months i have tried many settings to resolve or at least minimize (see below). Currently the Windows Event Viewer reports (albeit with a timestamp nowhere near the black screen event) \Device\Video3 UCodeReset TDR occurred on GPID: 100. What i have tried to solve or at least mitigate Variations of this behaviour is littered en mass in forums across the internet (NVidia, Reddit, Overclock.net, etc.); as such and as expected with anything on the internet, the unstructured responses, recommendations, etc wildly vary from moronic, insulting, helpful. There is of course no systemic solution as influencing hardware, software, OS & BIOS configuration varies materially enough that a resolution for one particular person's ecosystem does not work for others. Removed all useless bloatware e.g. gamebars, overlays, RGB crap software, razer trash, armoury crate toiletware, ... NVCleanStall 552.44 driver; Disable Telemetry, disabled NVIDIA HD Audio Device sleep timer, enable Msg Sig Interrupts (default, High Priority) BIOS, Disable PCIe Native Power Management & ASPM, Enable Resizeable BAR, power limits set to Intel spec for 13700K Windows 10: Disabled hardware accelerated GPU scheduling, Disable PCIe link Power Management, TDR delay to 15seconds, no fast start on boot NVCPL: Neg Load Bias Allow, Prefer Max Performance NOTE: Have not tried the more controversial settings such as turning off C-State in BIOS Power Supply: MSI MPG A1000G PCIE5 (12VHPWR) GPU: ASUS TUF RTX 4090 GAMING w/ latest (23-2-22) VGA Bios. I use the anti-sag adjustable support brace (although a stupid design by asus) to help support the card and (hopefully) avoid slot contact issues that might lead to the behaviour i am experiencing. AC Power: I don't use my UPS as it is only 900Watt, instead using a high quality monster power surge protector. Not sure how sensitive the MSI power supply is to voltage variations (while under higher than normal load) in wall power? I do, of course, actively profile and log all relevant sensors via HWINFO and i use the Remi Mercier's FanControl (github) for all heat mgt. Nothing recorded is ever out of temp, voltage, etc bounds for any measured component when the black screen occurs At my wits end with this and truly hoping i don't have to RMA my 4090 again.