Panzerlang

Thanks Duc. I currently have one SSD installed and my CPU is now idling (or running Edge) at 19c. Before the Big Wipe it was never below 32c, so it would appear something on the wiped OS was constantly running the CPU. Interesting.

If you have the Mig21, can you do the cold start on the Caucasus map and just watch the two other 21s taxi past your nose? In VR if you're on that. I'm very interested to know if they'll stutter/jerk for you too. I'm also in the middle of an OS re-install. It's up and running but I have to wait until monday for the two 2TB SSDs to arrive. I bought all the maps and they wouldn't fit on the 1TB drive. I'm hoping fresh everything will give some DCS improvements.

Yes, QV DFR. I love ChatGPT. So Pimax 1.0 is 100% native resolution. I've switched off everything that hits the CPU but still the two Migs have issues. I don't know how many other AI entities are doing stuff in the Cold Start mission but if a 13900k 15 P-Core CPU at 5.5ghz can't handle basic-level DCS without tripping over its shoelaces I think I'll take up Solitaire. Lol. Thanks Slug.

Thanks Slug. In the VR preset, with 1.0 and 1.0, I still see the two Migs taxiing past jerking a little but the red message that intermittently flashes up in the FPS window is "Main Thread", not "Rendering Thread". I'm beginning to wonder if maybe my CPU is broken.

I was lost before, now I've had a blindfold put on too. Lol. I just ran it at 1.0 and 1.0. I can't find "Render Resolution" in the log, so I'm putting it here. I'm now clueless how to best set these two values in regard to each other. Which is the least taxing on the CPU? dcs.log

You've lost me. I have 2.0 (two point zero) in the headset. Plus 0.5 in PD, that's a total of 2.5.

I'll have to run VR again to get that, last use last night was in 2D. How is 2.0 in the Pimax headset equal to 1.0 in DCS PD? When I switch those around (max in PD, min in headset) the image appears identical resolution-wise. I just find the headset's to give slightly sharper text in the cockpit.

I have max in the headset (2.0) and min in DCS (0.5). I might have to try lowering that, because in the Mig21 Cold Start the two taxiing Migs that go past me were jerking, and even with the VR preset it wasn't eradicated. Also flashes of red message in the FPS window referencing Main Thread.

And yet without QV I get serious degradation of graphics (stutters up the ying yang). It's a trade-off, yes, but in my case at least QV is a must. And that's with powerful hardware (4090 and 13900k).

Well, you are using a 4090 to drive a G2.

Ah, that's the confusion. Yes, I was talking about an ethernet cable via an adapter.

Also, use this to at least see if your headset works with something else. If this crashes too it's either your OpenXR is jankey (this is SteamVR) or your headset is fubar. Aircar on Steam You'll need SteamVR of course, it's free on Steam.

Which Pimax Play version do you have? If you don't already have this, try it out and run OpenXR from it (it gives extra settings in the Device Windows). How to use Pimax OpenXR Note: I find the native Pimax OpenXR to be a little better than the external one. You don't need to disable the external one, Pimax takes over. But if you go back to the external one it seems you need to reboot your PC after switching back before it'll run properly again (for me anyway, ymmv). Also this, so you can see what API layers you have running etc. GitHub - fredemmott/OpenXR-API-Layers-GUI: UI for managing OpenXR API layers

Just to clarify, the Pimax render setting and DCS Pixel Density setting are interchangeable. You can mix them together (don't know of any reason to do that though) but as already mentioned, I find the Pimax option gives a better image quality (text in the cockpit is clearer for the most visible example). Pimax at max, DCS at min.

The Res of Cockpit displays is wrong, it should be at 1040. I accidentally hit the Low button and missed setting that back.

Taking absolute GPU liberties. Ignore the resolution, I opened in 2D for greater ease of taking a screenie. The only setting that affects the VR stutter is having the view distance at Extreme. There's a huge free-flight area on the Caucasus map where you can see for miles. Panning the view around that causes lots of spikes but once everything has loaded it becomes smooth again. But the loading is ongoing, so it's all a bit spikey. On High the spiking goes away. This is on a 4090 and i9 13900k at 5.5ghz, 32GB RAM and clearly shows how the CPU is the limitation. There are zero GPU messages in the FPS window, it's just a yellow "CPU Bound, Rendering Thread". With View Distance on High my DCS runs 95% smooth, with the 5% being the occasional jerk. With a lesser GPU these liberties can't be taken but I have no idea where the threshold is at. Anyway, FWIW.

It didn't with the Pico4 until I'd messed around with Network settings. I persisted only because of the YT videos that clearly showed it should/could/would. Lol.

It's there.

If you have a very good GPU (a 4090 basically, lol) the issue with DCS is the CPU. Even the most powerful one finds it hard to keep up. The FPS counter in the game has shown only "CPU Bound" messages, mainly on the graphics rendering thread. Today I'll see what settings that involve the CPU can be dialled back and try it out.

What makes you think VD won't work on a cable connection? It worked fine that way with my Pico4. I don't know for sure but I strongly suspect Core Parking was the culprit.

If your current install isn't causing any problems I'd say stick with it. Windows is very robust now. You'll probably need to reactivate it with the new mobo.

What's DCS's Pixel Density set at? In my testing I found Pimax' render setting to give a superior image quality. So, Pimax at 2.0 (or 1.5/1.0, given your GPU) and DCS PD at 0.5. If that doesn't fix it you need to rule out graphics as a cause by going full potato in the graphics settings, everything to lowest possible. Then cross your fingers when you test it. Have you successfully run the PCL in any other VR games?

I set 72hz in the headset, FPS slider overides a LUA file setting of 72fps so the closest I can get in DCS is 70fps. My eyes did eventually mostly accommodate to the 72hz (not perfect) but no real difference with 90hz (with fps slider cap at 70fps or 300fps). But the game now runs 95% smooth as silk on the deck. Above 1000m (guestimate and varies slightly) it's 100% smooth. I'm plenty happy with that.

Go from page 2 in this thread. Core Parking and Core Isolation, disable Process Lasso, huge improvement on my rig.

Are you using QV Companion? Maybe your focus edge is too sharp? Companion lets you set that in pixels.