=OPS=Slider

As the title says. Happens rather randomly, hard to narrow down what causes that. Only in VR, but on both single and multithreading versions. It freezes DCS for like 0.5-1 second in irregular intervals. Log attached, maybe it will help. PC specs: R7 5800X RTX 3080 64 GB RAM DCS on an M.2 SSD dcs.log

Well, that's exactly what I did, specifically because the boat switch stays in place.

I haven't had any issues with human WSO, but we've had a jet hot on ramp. I could take control of the radar, he could take it away from me, and he could also slew the TGP, all synced just fine.

Yes, you are missing something. Castle switch is available to bind.

Warthog throttle doesn't register center position. I'm not sure if that's what you guys have in mind, but there are options like "X selected, ELSE Y". For the SE, for example, there is an option to bind "GUN, else SRM" and "MRM, else SRM". So if you have your switch set to GUN, deselecting it switches to SRM, even though the center does not register.

I've got the same problem. Ryzen 7 5800X, RTX 3080 and 64 RAM, with HP G2 as well. Same message, CPU Bound. Already ran a repair, removed all mods, deleted fxo and metashaders folders, to no effect.

Also, if you get a new, more powerful GPU, CPU will also wake up because there's gonna be more stuff to compute. At the moment since your GPU is maxed out, CPU is doing only as much as it needs to keep up in line with your GPU. Another way to look at it. Your CPU is a personal trainer. CPU went for a run with a fat GPU. It was a walk in a park for your CPU. The next day, same scenario, CPU goes for a run, but this time with a skinny GPU, so it has to give a bit more output to keep up the pace with faster GPU. Makes sense? lol

So what kind of performance increase were you expecting? You said it yourself that you know you are GPU bound, so more CPU is not gonna do anything, lol

MT is for CPU, not GPU...

We just did another test. Full mag dump from the Apache into the Tomcat's cockpit. Canopy open/closed/jettisoned, doesn't matter. The pilot is immortal. P.S. Jester died from one bullet (as expected).

Search for FSSB R3L and you'll get what you need.

It's not module specific. The Apache and the Hind are just hardware heavy modules, mainly because they are new, with new graphics standards, probably not fully optimized yet etc. I've tried again to use the motion reprojection and that drop occured again. First I took the Hornet for a ride and it was all good. As soon as I switched to the Viper, my FPS went down to 15, which, obviously, was totally unplayable. It happens with the motion reprojection turned ON, and I believe with OpenXR only. Doesn't matter which module you use. Another case is on busy multiplayer servers, then the drop happens almost immediately, within 1 minute, not more.

You don't really need to have that base to notice it's way different compared to how it was before the update. To be fair, that roll rate caught me off guard on my first take off with the new FM. Had to save it with the rudder... To be fair, it kinda feels like the Su-27 but on steroids. It has quite a lot of inertia, but it reacts quicker since the Viper is smaller. Since we are discussing the new FM here, MPO is "funny". Try to use it at more or less 260 kias and push the stick full forward. You can add some roll for "extra fun". EDIT: Completely missed Panda's post, but he's on point.

dcs.log Log attached. Fired up DCS, joined a server, performed startup, and as soon as it happened I left the server, back to the main menu (FPS still low, in range of 20-22).

I just experienced the same thing. The FPS and performance is just fine at the beginning, only to drop after a random, rather short period of time to about 20-25 FPS. Going back to main menu, FPS remain low. PC specs: Ryzen 7 5800X OC'd to 4.7, RTX 3080, 64 GB RAM, DCS on a M.2 SSD with plenty of free space. Temps are definitely not the issue in my case as I've never exceeded 60 celsius on CPU (usually low to mid 50s), and 62-63 top on GPU. EDIT: Started after the lastest OB update.