4 Tricks to boost VR Performance in DCS
ฝัง
- เผยแพร่เมื่อ 3 ธ.ค. 2024
- Here's 4 tricks for those who paly DCS in VR but can't afford a high end rig. I hope it helps.
DCS Graphics settings guide:
• DCS 2.9 Optimization G...
Empty VR Hangar mod:
www.digitalcom...
Good advice 👍 Its true that the fastest fps your machine can achieve does not always give you the smoothest results. In my experience a constant frame rate is more important. A faster rate which drops every now and then results in stutters. So absolutely right to lock them at a rate your machine can constantly sustain.
Definitely going to mess around with the LODs now, nice tip
Tip for measuring IPD if you own binoculars. Place them on your face and alter their distance until you have a perfect view and in focus. Now simply measure from the edge of the eye piece to the corresponding edge of the other eye piece (in cm) and you’ll have a close representation to you individual IPD.
Great advice!
@@ReflectedSimulations Absolutely. Pretty easy to do.
Mine would have been the mirror and ruler thing. Get in front of a mirror and hold a ruler against it. Look into your left eye with the left eye, aiming though the 0cm / inch marking, then close the left eye and do the same with the right one without moving your head. With that, you can basically read off your IPD from the ruler, because you're taking the distance from two perfectly parallel lines of sight that are exactly your IPD apart.
Thanks for this Reflected. The Empty Hangar mod is one I did not know about. Cheers
I tell you what, that OpenXR Toolkits has been a godsend for my Reverb G2. It turned my DCS experience from slideshow to cinematic!!
Agreed!
Same
As in 24fps cinematic? 😄
I thought Meta stopped supporting OpenXR. I guess not!
I started using Quadviews & Quadviews companion with the g2 & that really gave me an fos boost. Still using it now with the crystal light.
Never tried that LOD bias slider. Got 90fps on my 5800x, 64gb, 4080s rig (finally! The 3070 was not enough!) in a Q3 set to Godlike within VD. Mostly. Recently I just came back to DCS with the new Moza AB9 base and hopped straight into a quick cold'n'dark with the F-4E just to sit in the cockpit for the first time - and there I was at a fully packed field similar to the one seen in the video here - and I was down in the 50s with that. Wouldn't need SSW (the VD one) typically, but here it would come in -han- hoofy. I was already contemplating setting the headset to just 72Hz and settle with that, but maybe I don't even need to.
I also run OpenXR Toolkit only to set the Fixed Foveated Rentering to the most conservative preset, which barely impacts the visual quality, but is already noticable in fps gain well enough. Also, as of recently, DCS has integrated a "Quad Views" setting itself, maybe that's worth trying as well as trying to use thet Quad Views tool instead of OpenXR Toolkit.
Never tried the empty hangar, but I noticed that switching to and from F10 became a lot smoother since I got the 4080s, and also got even better (also, same goes for loading times in general, dunno why!) after I just switched HAGS on a few days ago since I wanted to try out the new MSFS (bought the Limited, but have to wait for it to ship, got no Game Pass from MS, 'coos I bought it late, so I got a 14 day 1€ Game Pass to get access) with the option to switch 40 series frame generation on, which requres HAGS, especially after I've gotten a MOZA Cockpit update yesterday that said it comes with Telemetry FFB support for 2024. Long story short: You might wanna try enabling HAGS, actually. I literally feared getting issues with DCS, but instead, it got better! (still on Win 10 here and I've heard it basically is good to go if you got Win 11, but on 10 it might cause micro stuttering issues).
As i ask for a quest3 for Christmas, this will be usefull. Thanks !!👍
-Fing- Hooves crossed you'll get one (and not the S which doesn't have those pancace lenses you'd want!) :)
Nice! Some things I didn't know. Great!
Fun fact - Fixed FOVeated Rendering may also decrease performance in CPU-bound scenarios. So if you're close to being CPU bound, this may be detrimental.
But excellent tips with LOD factor (I've been neglecting that one), and setting the IPD!
That's only if using Quadviews AFAIK, VRS (which OpenR uses for foveated rendering) should not
@@BurntPlaydoh Quadviews may be more noticeable, true. But on openXR with the toolkit, I did notice a definite increase in performance after disabling foveated rendering. Had me quite surprised as well.
I agree that this is purely anecdotal, but switching it on/off an comparing is probably still better than just assuming it always increases performance?
@ It doesn't change the rendering pipeline, there isn't any reason that CPU workload would increase as far as I'm aware
No offense, but I doubt your comparisons were nearly as controlled as what DF, Lukas Wolta, or MBucchia have done
@@BurntPlaydoh Dang, I miss Lukas S / Wolta / Woona!
@@CakePrincessCelestia Same, he had some of the most informed and informative VR content that could be found
Another thing that helped me is reducing the roughmet texture sizes on a lot of the newer modules and assets. I used to get a lot of stutters as I approached certain modules (usually Tomcats and Phantoms) due to the texture loading.
that's something that needs to be brought up to Heatblur I guess
Love your videos, love your campaigns! I recently purchased jagdflieger campaign and getting into it is great! Your work and detail is top notch!
Is there anyway you can do custom Skins for the 109? Ive tried finding skins like in IL2 Sturmovik but they arent as popular in DCS world.
Thanks! I’m glad tou like the campaign. I don’t really have much time to make custom skins other than what’s needed for the campaigns
Thank you so much my friend
Great tips R, thanks
Makes me want to fire up my Aero and do some Arctic Thunder
You can try pixel density 1.3 and DLSS performance. It works fine for me.
Good Video! However, I would advise against the use of the ingame frame limiter. The frame limit is governed by the main render thread (running on a CPU core). I would keep any unnecessary task away from that. From extended testing I concluded for me, that the least impact on consistent frametimes comes with the use of an external fps limiter. You can use your GPU driver or my tool of choice Afterburner/RivaStatistics. However - full disclosure - these are experiences from 2D gameplay at much higher fps. If that translates equally to VR, I can only assume.
@@MrSpinkser thanks! So I’d be better off with limiting my fps in the nvidia settings?
That's a real pain if you switch between VR and flatscreen on a high-refresh monitor though, much simpler to swap between settings profiles in the launcher
@ from my testing... I would say so. When I experimented with it the differences in frame time smoothness/regularity were pretty obvious when looked at the ingame frametime graph.
Of course I tested in a different environment (2D/4k/highish fps)...
So you're mileage may vary.
Agreed. When I lock my fps to 70, I get jitters and micro-stutters. I changed limit to 180 and the stutters went away. I was shocked to have smooth 70 fps on Q3
@@ReflectedSimulations Note, the NVidia control panel doesn't limit you to increments of 5 either. You can set it to whatever FPS you want. It's what I use for VR.
Hey, another trick for custom max fps settings, you can manually change it in the option file ( I think it's in the savegame folder )
Damn the VR hangar is the one thin killing my FBS. This is the sad. I made my own, ED does not like me having nice things.🤣
Process Lasso is a Tool to get +10-20 fps
I also prefer process lasso, even with Win 11, smoother for me
How?
I thought Reflected surely had to have a server rig with 2 4090s for development purposes
Hahaha I wish
I can't get the EmptyHangar mod to work. I've tried a few different file structures without success. Currently I have it setup as this through OSGME.....C:\Users\XXXXX\Saved Games\DCS\_OVGME Mods\Empty_VR_Hangar\Scripts\DemoScenes Any thoughts on what the file structure needs to be?
@@bigrivercod it goes to the main dcs folder not saved games
Thanks for that. I’ve now got it working,. Not sure if it is the way I have OSGME set up, but I have to cut and paste the OpenHangar file in to the main DCS folder as OSGME doesn’t put it in the correct location
Merci :)
De rien :)
Good video, just one tip, instead of fixed foveated rendering try quad views, even without dynamic foveated rendering it does really well. It ends up saving me around 60% pixel rendering on the quest 3! Means I can run at 72fps without any ASW vs 50-55fps
How do I do that?
@@ReflectedSimulations If you search for Quad Views Mbucchia you should find a github repo with the app to download, basically it's another VR API layer similar to how the OpenXR toolkit works. In fact I think it recommends to uninstall XR Toolkit prior to installing quad views. Once you've installed it you should be up and running. When you run DCS in VR it creates a log in the quad views install folder that lets you know how many pixels you're saving - honestly it works really well. You just have to tweak it right to have a balance between performance and not having too much blur on your peripheral.
Give me a shout if you want a copy of the quad views settings I use
Edit: I also use this in tandem with Virtual Desktop btw, you don't have to do that but I found the VDXR more performance over using meta link
OK I just installed quad views. It's great, but for some reason OXRTK gives me smoother terrain movement when I roll my plane at low altitude. With QV I'm getting little chops/stutters. Any advice?
ah I used to have this and tbh I’ve changed so many settings that I can’t remember what exactly solved it. Just a quick one to check since you mentioned you use asw, go into the quad views settings (found in appdata/local(I think else roaming)/quad-views-foveated and open settings.cfg. If turbo mode = 1 change to 0 and save
Hello ! Thanks for your vidéo. 2 questions : I have a PICO 4 and i don't have the foveated rendering option in the openxr toolkit menu ingame, is it compatible ? and i would know were to put the hangar mod please ! Thanks !
the file goes into DCS/Scripts/DemoScreens - I don't know about the PICO
Thanks ! 😊
I read that openxr doesn’t work anymore in 2024 is that true ?
It's not being actively supported by the devs that wrote it anymore, so it won't get updates anymore. Still works, though. But if at some point for some reason it breaks, that'll be it.
@@CakePrincessCelestia that's bad news, Turbo mode is the only thing giving me smooth gameplay
Amazig how many folks think IPD has nothing to do with pupal distance! Of course the source has to know your pupil distance! If it doesn't how does it render the scene to fit the setting in your headset! You can prove it with moving it to zero. Guess what... Everything ends up 2d!
Your current HMD setting is fed into DCS on basically all popular models AFAIK. That setting only matters if none of the physical IPD settings on your HMD are close to your IPD.
Don't you find the warbirds are flaping during fights with 35 FPS ?
yes, a bit
@@ReflectedSimulations if youwantto prevent it, I have not found any other way than lowering graph until it becomes constant 90FPS no reprojection. maybe it works at 72Hz.. can't wait to try with the crystal light
FYI IPD config is wrong represented in DCS, DO NOT USE IT, leave in the off option. the real configuration name would be World Scale like in Steam vr wich make things bigger or smaller but it does not have anything to do with IPD, the default "IPD" in dcs already is a 1:1 scale with real world. IPD is changed physically in most Headsets in the lens to adjust were the center of the lens should be
what is the default value in DCS?
I use the Pimax crystal, that has far better clarity and resolution then my 1440p monitor. So I haven't touched the LOD thing
Doesn't your game crash when you use open xr,
?
?
No, DCS natively supports Openxr lmao
Thanks for the great info. Cant see a difference above LOD 0.6 even with the Varjo Aero. On occasion, I have the FPS tank completely for a couple of seconds. Any tips how to find the culprit, maybe what Windows task that might be?