Flextremes

I am on it Was loosing edits because I accidentally click the freaking back button on my mouse. Edit ... Done!

My system: Highly optimized Win 10, AMD 5800x3D, 4090, Reverb G2, Native OpenXR, almost maxed out DCS settings with FSR upscaled render resolution 3600x3600. Scene below is from F18 launch on Carrier in Persian Gulf Mission. Without Process Lasso: With Process Lasso: 'rdr CPU' seems responsible for VR frame rendering and is directly affected by scene complexity (like objects, clouds, etc..). A lower 'rdr CPU' will result in a lower 'app GPU'. DCS MT highly optimized 'app CPU', now 'rdr CPU' can have a relatively higher impact. You really want both CPU frame times combined to remain below 20ms to not start rendering at 30 fps and create mild stutters when switching between 45 and 30 fps. By dedicating cores in Process Lasso (forcing affinity) for DCS.exe and all other processes separately, you are also separating 'app CPU' and 'rdr CPU' execution. In short: STEP 1: First start DCS in VR. Select All Processes in Process lasso: Set affinity, Always, and select the last or first 4 threads of your if you have an 8 core/16 thread or more CPU. If you have fewer cores, maybe assign only 2 threads. (if applicable, only select Intel Performance Cores or cores on the AMD X3D CCD) STEP 2: Then select DCS.exe, Set affinity, Always, and select the other threads (invert selection) (if applicable, only select Intel Performance Cores or cores on the AMD X3D CCD): IMPORTANT!!!! Do not skip STEP 1, It is crucial to separate DCS.exe from other processes, only setting Affinity for DCS does not work. All other processes should be running on different cores than DCS.exe! This is tested only with OpenXR. I have not tested this with steamVR. Intel CPU users below report different results. So try and make sure you test. Do not worry about excluding system processes, when setting affinity: if it is not possible to change affinity, nothing happens. I also forced 'Always - high priority' on DCS.exe. Enable performance mode in Process Lasso. I always manually start Process Lasso before I start DCS: I do not want Process Lasso to be enabled during startup and interfere with normal usage. This config is only recommended with VR. This also works with other Simulators and games in VR. Disable 'Game Bar' - as it easily conflicts with Process Lasso settings. Always test and validate these settings yourselves. Easy way to validate frame times yourself: Choose a stable, non-moving, scene (while being parked) in the external view (with loads of objects) that has high but relatively stable 'rdr CPU' frame times. Screenshot before and after enabling Process Lasso, making sure you have the exact same view angle in VR. Make it easy by enabling screenshots in the OpenXR toolkit companion app, enable the Advanced OpenXR FPS counter, and select CTRL + F12 to create a screenshot create before and after with the exact same view in VR. Wait for frame times to stabilize before comparing/screenshotting 'rdr CPU' and 'app GPU' values.

Yeah the Team deserves a couple of Lockheed Martin C-5M Super Galaxys fully loaded with Kudos containers. I suspect it is not just MT implementation: there has been so much more, single-threaded seems also faster. I imagine a lot of performance optimization changes went under the radar. How did you measure? You will not see fps increases, but both CPU and GPU frame times, performance headroom, and stutter reduction are massively improved. It is just so much better. I did not notice any degradation in LOD and viewing distances. It is almost dumbfounding you cannot notice the improvements. Did you start the DCS.exe from the Bin-MT folder?

I literally went from flat shadows to ultra, enabled cockpit global illumination, from 60% trees to 100% and all is still perfectly smooth (higher FPS than before MT update). Can anyone suggest a track or mission file that is known to really punish CPU in DCS?

I'm on 10: highly optimized. I clearly do notice a significant boost. How do you come to this conclusion?

That sucks! Mayby delete your shader caches? Also try single thread DCS, for me it is also smoother. Good luck!

I am getting app CPU 2ms, rdr CPU 3.4ms and app GPU 12-13ms when you fly back over the airfield in your trackfile. Both CPU and GPU frame times are consistently low for me. Edit: over the city at the sea app CPU 2ms, rdr CPU 3 and app GPU 10-15 ms.

Interesting: I consistently get lower CPU and GPU times in all maps and airframes: (app CPU in the F15 in Nevada is below 1 ms ). AH64 on the Marianas map in a mission I get easily 45fps. I can imagine that other optimizations (like the flat-shadow fix) are even more responsible for this. I also use process lasso, assigned exclusively DCS to core 0-7 without HT. On the last core I run all other windows and app processes. Maybe you can try with disabling the second core in bios, some game perform even better (than with core parking enabled on the second).

Seriously, that edit was done way before I read your complaint, you are simply too fast to pull the trigger. Don't mind me making more edits with new conclusions, because this patch is pretty amazing. I hope you enjoy the MT update like I do. Why don't you share some of your own findings...

I added results single threaded for comparison, what do you mean?

Rocking a 4090/5800x3D here... F18 ready for launch on Carrier: now openXR shows 3.3ms app CPU and 3.2ms rdr CPU times... Single-threaded openXR shows 5.1ms app CPU and 4.2ms rdr CPU times... Seems like there have been more optimizations having a positive impact (ie Shadows flat bug). Edit: Good news maybe if MT does not work for you, it looks like single-threaded DCS is also much smoother. After more testing, I can also safely conclude that single-threaded is also much more smoother and responsive. I prefer to fly with Flat-shadows, which clearly is smoother. I improved by 1-2 ms GPU frame times in the F16 in the above Dubai and Marianas in single-threaded. MT is even better, improved by 2-3 ms GPU frame times in the F16 in the above Dubai and Marianas. Obviously MT is much smoother, there are less stutters, but maybe more noticeable: input latency improved considerably (might be placebo). DCS feels much more snappy and responsive. Edit 2: I am genuinely impressed. Both Syria and Marianas maps are clearly much more smoother/responsive. The positive impact on CPU also affect GPU response times favorably. Did not expect this, because with a 4090 less GPU bottlenecks are experienced. Edit 3: DCS MT seems stable so far, no CTDs yet, but only limited/quick tests of many different missions and instant actions. When starting a mission, you can see all textures (plane and ground) being loaded in. After a few secs, all is fine. So far I have never seen CPU time more than 10ms. Edit 4: I just went from low shadows to ultra, enabled cockpit global illumination, from 60% trees to 100% and all is still perfectly smooth (higher FPS than before MT update). Edit 5: Compare below the OpenXR CPU and GPU frame times in Single threaded and Multithreaded: F-18 on carrier ramp in Persian Gulf: 1st: Single Threaded... Secondly: Multi-Threaded

I am a reverb G2 user, and looking where I can donate. Cannot find paypal or something similar anywhere. Is is possible to donate to this (fantastic) project?

I did change it from: Optimize for performance to Best visual quality when I was troubleshooting, following the guide from https://vr4dcs.com/. I reviewed so many settings while troubleshooting, I forgot to mention this. This must have been the specific solution for this particular problem.

Yep, almost sunglass shape.

First, my problem is now fixed: either by deleting the fxo folder, setting lod to 'clamp' in nvidia control panel and rebooting amongst many settings I reviewed. I have zero issues now. Thanks for checking, really helpful, it is great I did not report a bug when the problem proved to be on my end. About AMD, I use ramtuner 'safe' settings to optimize ram and run 3600mhz/1800mhz FCLK> this is one is worth it. I use AMD Ryzen master to set OC in the basic setting and leave it at that for now. I just switched from 5800x to 5900x. The 5800x proved to be close to impossible to improve performance. Still learning my 5900x, but I don't hold my breath. It is awesome as it is, also for DCS. I do have access to the latest CTR tuning (overclocking tool), but my 5900x is what CTR calls a 'bronze' class, so really difficult to OC. There is more potential, but for DCS is does nothing you will get about 20% utilization max.

Nice coincidence! I just did this before just before you suggested it: awesome, this shader mod is a keeper without doubt. A easy reproduction scenario is: fly over the Vegas suburbs, at 2000ft, pause: look at the pop-in distance for small buildings and objects: close one eye, then the other. The left eye has a higher render distance then right. What hardware are you using? Maybe it is specific to my setup. thanks again for checking, no rush, there are so many more important things in life If others with similar setup as mine could check this, highly appreciated! If this is specific to me, I have a very long list of debugging to do

Nope it is everywhere. It is only noticeable at the edge of the rendering distance (set by 'visible range', does not matter what setting), where ground objects fade/pop in. Just close left or right eye, alternate, one eye pop in object are rendered slightly farther. Those object are only visible for one eye, creating a weird shimmering effect that causes minor eye strain: the brain has difficulty to compute this :). Did a cleanup/repair to be 100% sure I have a clean install with 2.7. Really appreciate you checking this. If this is me, I need to start finding out what causes this: DCS settings, Nvidia, WMR, Steam VR...

Fixed: "In the WMR settings for Headset display under experience options if you have it set to Optimise for performance you get the object desync. Set it to Best visual quality and it works as it should. " found by user Dayglow First: 2.7 is such a blessing in VR, the ED team deserve a lot praise. I'm a casual DCS fan/flyer, for more than a 2 decades (since Flanker 2), but never I have experienced such and improvement in fidelity AND performance in the same release. Maybe I found a consistent bug, that starts to stand out once you notice it. In VR, with my reverb G2 (on a RTX3090, 5900x), the render distance of trees and cities (set by the 'visible range' option) is slightly different. I find it especially noticeable with the render distance in populated areas because they are dense with objects, but of course everything is affected that is configured through the 'visible range' option. This is noticeable in both the Caucasus and Vegas map. Quite quickly I noticed a got a weird kind of shimmering in the distance. When I closed my left or right eyes, the shimmering is gone and clearly for one eye objects are rendered a little further then the other. Once you notice it it will stand out. Nothing dramatic, but this should be an easy fix for ED if this indeed is a bug. Do you notice this too? Is there a fix possible? If not, if so I will report the bug.

Yes, many x570 owners report issues. Also a few that are OK. Seems like Asus boards are most affected. The good news is: I just installed the 2702 bios for my Crosshair VIII Hero, and it seems to fix this issue for me. G2 has been super stable for hours in DCS now. Note: The right headphone does crap out sometimes, but this is clearly a build quality thing, it only happens when I move/shake the headset or adjust the right headphone.

Crosshair viii + 5800x here: my G2 will simply not work. It is a know problem with x570 motherboards. I even tried an Asmedia 1142 based USB 3.1 pcie Card (Logilink PC0081) powered bij Sata: still same problem. What a bizar problem and disappointment, specifically upgraded to a 5800x and RTX 3090 for the G2... Anyone here got the G2 working on a x570?

Excellent initiative! But this sim need a real benchmark mode so badly: I cannot understand why something decent is not implemented, it really helps tuning your hardware and settings and DCS is its own beast. Anyways, coming from a 4.5 ghz 6700k, now running a AMD 5800x & Evga 1080Ti sc2... it is now silky smooth. Comparing the CPU frame times to the lightning fast 5.2 ghz 9900ks results here, the AMD does pretty well. I knew what the 1080 ti could do, but I was wondering if the AMD 5800x (no OC, no PBO, 32MB 3800mhz CL16 16 16 32) was a good choice. Seems like it really is! Note, I really did my best to record only looking ahead, without any head movement. fpsVR Report: App: DCS HMD: Samsung Windows Mixed Reality 800ZBA0 (90.002 Hz, IPD 66.0) GPU: NVIDIA GeForce GTX 1080 Ti (27.21.14.5638) CPU: AMD Ryzen 7 5800X 8-Core Processor Delivered fps: 44.42 Duration: 0.4min. GPU Frametimes: Median: 16.9 ms 99th percentile: 21.2 ms 99.9th percentile: 22.3 ms frametime <11.1ms(vsync): 0% CPU frametime: Median: 10 ms 99th percentile: 17.7 ms 99.9th percentile: 18.9 ms frametime <11.1ms(vsync): 87.4% Max. SteamVR SS: 180% Render resolution per eye: 1940x2432(by SteamVR settings, Max.) (HMD driver recommended: 1447x1813)

Interesting thread, I also use an older 6700k @ OC to 4.5 Ghz. Will upgrade in the next few months to either 5950x or 10900k. I wonder what ZEN 3 OC potential is. But this is not main reason why I reply to this thread. I just want to point out for 6700k, 7700k and 8600k (and older) owners that it is really worth to DISABLE meltdown and spectre vulnerability fixes. This will improve your IPC by a whopping 10 to 15%. Use inspectre for this, disable both and reboot. I am not too worried about security, since there are hardly any active malware/virus out there that use this vulnerability. If you are, just temporarily disable for a DCS session. Only downside is you need to reboot for enabling/disabling. My cinebench score improved by 15% > I am confident DCS will benefit also.