Blackhawk163

Just use TallyMouse's YouTube video suggestions for DCS in VR. It's a very well done video and has a great breakdown on how to achieve a right balance of visuals and performance. I can't recommend it enough.

Ryzen 9800x3d/64gb DDR5 amd expo/RTX 5090/4tb m2/ Win11 pro/Pimax crystal light The video is Super smooth for me, I got fps as high as 115fps sustained in the air and 75 on the ground whilst playing the artic thunder campaign for the F/A 18 C. Same for my test with the F16 doing the Caucus Map, free flight mission.

I know it's probably been said already across multiple threads, but just do what TallyMouse's latest VR YouTube video suggests. Especially if you own a Pimax device. My specs are in the signature. Zero stuttering smooth and a super enjoyable experience.

That's so weird, I have a some what similar system. I'm am running a b650 board (so no pcie 5 for me) same speed ram as yours with a 9800x3d and an MSI 5090oc and I can tell you that I'm getting 60+fps with everything nearly on and the resolution on the Pimax CL at native. I will say that I'm not running any AA, as it's sharp enough at that resolution. Smooth with no over the port and starboard side stutters.

Flint, is all this with shipping included?

You can go as small as 1028x768, you just have to manually input it. It's what I use.

Sorry for the very late reply. I'm sorry that I can't answer the technical aspects of your question, as I'm not well versed in it all. I just do a lot of trial-and-error type experimentation. I never really liked DLSS even in its newer state, it helps, but I don't like the softer look to the game. Also look to reduce some settings in DCS. I know that when I had the 4080/5080 (just upgraded to the 5090) I set clouds to normal and textures (not ground textures) to medium as well as LOD to .4 as well as other tweaks. I played around with all this until I could look outside either side of the aircraft and observe the scenery moving smoothly. Once there I started to add some settings back in until it started to stutter. Sorry that I can't get into the technical weeds.

important to note that this only works with those who purchased the hand controllers.

Glad I stayed away from the latest firmware then. Running the latest Play version but on the previous FW. No problems so far.

What version of Pimax play are you on? If you downgrade to 1.29 or even 1.36 does the problem go away?

I had the same issues, if you’re willing to give up on some setting sliders (primarily for local dimming) I rolled back to 1.29.01 on the software side of things. That seems to have solved some issues and has given me volume control back on my headset. I’m on the newest firmware and the jitters are gone. &nbsp I don’t know where Pimax is going with their software, but the latest iterations have been getting worse.

Per product description: ZOTAC GAMING GeForce RTX 4080 SUPER AMP DLSS 3 16GB GDDR6X 256-bit 23 Gbps PCIE 4.0 Nothing wrong with the card, never had an issue, just shy of a year old. It was upgraded to the 5080, and it is currently is sitting in its original packaging waiting for a new home. Most Maps (Marianas islands lol is a nope) at 100% settings without DLSS ran at 90-120fps (limit of my monitor) in 4k 2d obviously. Activate DLSS and I was getting 120 locked (with Marianas at 100-115) 4k 2d VR saw FPS at 60-72 sustained although with the resolution lowered (pimax crystal light) down from 1.0 to .78-80. Using recommended VR settings found throughout the net. QV and or FFR enabled. Lock it in a little higher with DLSS enabled (I personally don’t like using it) $850 conus. I cover shipping you cover the fees. pics on request. sold

Task manager reported 12 instances of HBUI running, of which I was able to stop 9, with the remaining 3 being unable to force quit (as soon as I stopped one of the three it would spring back up). This is with OPXRTK enabled, which still results in the F4 being the only module that I have as incompatible with it as it locks down to 32fps. Behavior not present if OXRTK not enabled, although all but 3 instances of HBUI can't be stopped until DCS is restarted.

I would agreed if all the modules did this, but as it stands, at least in my case and computer configuration, it (opxrtk) is only incompatible with the F4 module. I think it’s a combination of things in my case, perhaps it’s the 5080 vs the 4080s that I had before, could be a driver issue with the 5000 series. What I do know is that I failed troubleshooting 101 before I made this thread (and the other in the DCS core one too) by not disabling any software not needed to run DCS. Once I ran it with OPXRTk off everything was fine. Now I guess the question is why this is the case with the F4.

I’ll do that (just lost power as of this writing lol) soonest. I do know that the module absolutely hates openxr toolkit. I was able to identify the conflict there. When running with it disabled there’s no problem. Enable it and the problem returns. This is new I think as I’m pretty sure I was running opxrtk back in October.

That’s what I’m about to do. However it will be a dremel.

I can confirm that this DOES NOT work on some Orion 2 throttles the mechanism has been changed

My mistake, I missed the Orion 1 part of your post.

Yikes for that price you could’ve just paid little more and gotten the cam/damper kit. You would’ve gotten the stock springs and more for backup. Unless if they’re out of stock wherever you are.

Cheers John, thanks for the update, I can't wait to finish the campaign.

any work around that doesn't involve either flying the a10c or skipping the mission?

Well poop. All dreams dashed lol. Thanks for the update.

That's the new FFB that's coming out no? As for that extra panel, I wants it lol

I remember the first time I did AAR in that other sim. Watching the basket oscillate and then the connection wave. Chefs kiss right there

I failed the troubleshooting 101 checklist, and will be flying crop dusters for a while lol OpenXRtk is the culprit. Disabled that and everything was right as rain. f4 back to 60 fps, some minor performance spikes with other modules (not enough to reduce so much as a frame), but the f4 ran flawless. Now I know. Going to see what exactly is going on now with the toolkit.