Panzerlang

'Pondering playing the Pimax-Super lottery...roll the dice or don't even look at the casino...'

And here's the real head-fk...the 13900k has FIFTEEN PHYSICAL CORES, running at 5.5ghz (native, not OC'ed). DCS is multi-threaded so it has access to all of them. Meanwhile, over at IL2 Great Battles, one core and no stutters. A less demanding engine but whut? The DCS engine is fifteen times + more demanding? Or is it a component on all motherboards that simply cannot channel fifteen cores' worth of data sufficiently well enough?

Putting a 4090 with your 10900k would probably be a partial waste of money, that CPU would bottle-neck the GPU to some degree or other. There is a significant improvement in visuals with the Crystal vs the G2 (I had a G2) but you need a well matched CPU with a 4090 to have it run well. For you that's a financial quadruple whammy (Crystal + mobo + CPU + GPU). Not forgetting a new CPU cooler and maybe RAM (DDR4 to DDR5).

Putting this here too, hopefully ok... I'm guessing this is a new item in W11 24H2, 'Game Bar'. The picture says most of it. Unfortunately the screenie doesn't capture the DCS FPS window but that, as always, was giving the "CPU Bound, Main Thread" message, in mostly red but sometimes yellow. Meanwhile the Game Bar window (have to alt-tab to see it) shows CPU at 37%. I'm assuming the Game Bar app is functioning correctly. On the up-side, this Game Bar has a video capture function and I could see no sign of it sucking resources that impacted visibly on the game. It records from the VR one-eye monitor output though, so the resolution isn't great. Other great news, the Mig21s that used to stutter past me while taxying are now almost totally stutter free. I think the fresh W11 install has fixed a lot of issues. But back to the main issue and what is my dumbass missing here? CPU at only 37% while the game is running (not paused) but DCS says "CPU Bound"? Eh? Whut?!

I'm guessing this is a new item in W11 24H2, 'Game Bar'. The picture says most of it. Unfortunately the screenie doesn't capture the DCS FPS window but that, as always, was giving the "CPU Bound, Main Thread" message, in mostly red but sometimes yellow. Meanwhile the Game Bar window (have to alt-tab to see it) shows CPU at 37%. I'm assuming the Game Bar app is functioning correctly. On the up-side, this Game Bar has a video capture function and I could see no sign of it sucking resources that impacted visibly on the game. It records from the VR one-eye monitor output though, so the resolution isn't great. Other great news, the Mig21s that used to stutter past me while taxying are now almost totally stutter free. I think the fresh W11 install has fixed a lot of issues. But back to the main issue and what is my dumbass missing here? CPU at only 37% while the game is running (not paused) but DCS says "CPU Bound"? Eh? Whut?!

Yeah, good point. Why should any fully-owned piece of hardware require an online login?! Imagine if that was needed for the CPU or GPU etc. Fix it Pimax, this kind of intrusive meddling is unacceptable. You have absolutely zero right to require an owner of your hardware to have to be logged into your server in order to use his fully-purchased hardware. We don't need 'social credits' either.

Uum...did you guys try to actually use the headset? I get the server message but the headset works.

They added some new world features.

I just did a fresh install of W11-Pro and it's now on 24H2 version. I'm using the integrated Pimax Quadviews on MY OG Crystal and it's working at least as well as the previous external solution. It did seem to run a bit better than the external even when I tried it on my old W11 install. Intuitively it makes sense to use native software, IF it has no obvious issues, and so far the Pimax solution appears to have none. I don't think the companion app will work with it though and I'm not going to risk breaking something by trying it. Lol. The API Layers GUI does NOT see the Pimax API and I think the companion app is coded to work with MBucchia's API. The GUI does see the Necksafer API however (it's the only entry in it) and that works perfectly too, though I do now have to recentre my headset in each new DCS session (with the controller). Recentre headset with Pimax controller, THEN recentre Necksafer/DCS-VR with the joystick button I assigned.

Yeah, the intro video in the launcher always does a jerk (the carrier) before it settles down. We can't know how much of it is down to potentially iffy code or if it's purely different combinations of hardware struggling with well optimised but very demanding code. I'm certainly no expert on the hardware but, intuitively, I'm aware that motherboards (for instance) come with countless different types, brands and qualities of components. That then have to interface and interact with other bits of hardware that themselves have varying types and qualities of components. Then add weirdness. Why do two taxying Mig21s stutter past my parked plane on the ground when, in the air, I see dogfighting planes that exhibit zero stutter? No idea. THAT is counter-intuitive. Regardless of all that, DCS loads a HUGE and very complex map AND has very complex AI routines running all kinds of assets (planes, ships and vehicles). That requires as much top-end hardware as you can throw at it and your CPU is a weak link in that equation. So is mine, unfortunately and as soon as the 9800X3D is available at a regular price I'll be upgrading to it. And will probably still see a bit of stutter.

I had the original ButtKicker, it was noisy as hell on the seat strut, got hot and would clip very easily (and the magnet inside would clatter loudly against its case). Dayton pucks became stupidly hot. I now have two big LFEs and they are superb. Powerful and next to no heat. I use a 700w amp to power them, with SimHaptic software.

That's because those games aren't making so many demands on the CPU. You have a whole bunch of OS processes using the CPU, let's say 10% and DCS tries to use 94%. That 4% over the top causes stutter. Your other games are 50%, 63% etc, lots of overhead left over. Two possible solutions...more powerful CPUs and/or ED get into AI and use it to rewrite/optimise the DCS code.

As they do with all games, it's just that DCS is exceptionally demanding. I've just reinstalled my W11 and with both 23H2 and 24H2 it's running pretty decently but not at all perfect.

I'm going to guess it's your CPU that's causing it. All my FPS-window messages are "CPU Bound" and that's with a 13900k running at 5.5ghz (with a 4090). DCS munches CPUs.

Yeah and here in Japan the usual leeches are buying up the 9800s and putting them on Amazon for x3 the RRP. No hurry, my i9 is doing ok.

I did a complete W11 Pro reinstall a couple of days ago and 24H2 went in yesterday. I now get mostly "CPU Bound, Main Thread" instead of "CPU Bound, Rendering Thread". Decently smooth on the deck, using exclusively the Crystal's Quadviews etc.

Well, I never use the headset's own power button, that thing is totally FUBAR. If I don't properly close Pimax Play the headset stays powered on (not good), shown by it's tiny green light being on. So it's drawing power from the hub and running hot. Turn off Pimax Play and the tiny blue light comes on, which means all the headset is doing is having its battery re-charged.

Are you closing down Pimax in the taskbar's "Show Hidden Icons" window? I just checked Task Manager and I have no Pimax stuff running.

Used to fly with Pye?

If I recall correctly, Mark from GYGO YT channel had the same issue and it was as Moxica says.

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