KY_Redleg Posted March 7, 2023 Posted March 7, 2023 All, I have the following: Headset: Quest2 connected via cable CPU: 11th Gen Intel(R) Core(TM) i5-11400F @ 2.60GHz GPU: NVIDIA GeForce RTX 3060 12GB Memory: 64.0 GB Speed: 3000 MHz I can't seem to get more than 30FPS single player and maybe 22 FPS multiplayer. Am I expecting too much? When running in VR, my CPU is not pegged and neither is my GPU. I've followed a lot of the tweaks on the forum and reddit, so far, this the best I'm getting. I attached my settings. Any advice appreciated! Redleg
dutchili Posted March 7, 2023 Posted March 7, 2023 PD and MSAA have the most impact on your CPU. The 90 hz refresh rate also requires a lot of frame generation. I'd suggest to set 72hz (gives you 36 fps which appear to be fluid), set PD to 1.0 and to compensate increase the Oculus render resolution. Reduce Textures to medium. you should be able to set visible range to high. Let's us know if this helped.
speed-of-heat Posted March 7, 2023 Posted March 7, 2023 Drop the refresh rate to 72hz and drop the in game Pixel Density to 1.0 ... as a start and supersampling and render resolution each of these is multiplicative .... so set them to one and then start playing with 1 only 1 of them SYSTEM SPECS: Hardware AMD 9800X3D, 64Gb RAM, 4090 FE, Virpil T50CM3 Throttle, WinWIng Orion 2 & F-16EX + MFG Crosswinds V2, Varjo Aero SOFTWARE: Microsoft Windows 11, VoiceAttack & VAICOM PRO YOUTUBE CHANNEL: @speed-of-heat
KY_Redleg Posted March 7, 2023 Author Posted March 7, 2023 Thanks All! That definitely helped. I was able to get MSAA set to 2x and PD to 1.1 and still maintain 36FPS. So what is the bottleneck on my system? CPU or GPU? Thanks! 1
edmuss Posted March 7, 2023 Posted March 7, 2023 Both will bottleneck quite readily in DCS unfortunately. If you put a bigger GPU in then it will be held back by the CPU, if you put a bigger CPU in then the GPU will be screaming along and the CPU will (possibly) be idling most of the time. I would say you're probably pretty well balanced at the moment actually (for a relatively low spec DCS VR machine), ideally you want to be GPU bound as it's the end of the line before the headset and can't affect other components - if you're CPU bound then it can drag the GPU down with it. Using a performance overlay check your CPU and GPU frametimes, nominally if CPU is higher than GPU then you're CPU bound and vice versa. Ryzen7 7800X3D / RTX3080ti / 64GB DDR5 4800 / Varjo Aero / Leap Motion / Kinect Headtracking TM 28" Warthog Deltasim Hotas / DIY Pendular Rudders / DIY Cyclic Maglock Trimmer / DIY Abris / TM TX 599 evo wheel / TM T3PA pro / DIY 7+1+Sequential Shifter / DIY Handbrake / Cobra Clubman Seat Shoehorned into a 43" x 43" cupboard.
Tomcat388th Posted March 7, 2023 Posted March 7, 2023 Here are my settings but mycpu is a 5800x3d and my ram 3600 the rest is the same as yours and I do run airlink. I will only note what settings I have different from your screen shots Quest2 90 Hz4128x2096 nvida cnt pnl anisotropic filtering Application-controled antialaising mode Enhance the application antialaisning setting 2X DSR factor OFF MFAA OFF Shader cache 10GB Texture Filt Negative lod Clamp Texture Filt Quality VR pre rendered frame 3 Ocululus tool tray Game settings tab Default Super Samp 0 Adaptive gpu scaling on Link Tab Distortion curve high Encode res 3960 Encode bit rate 0 Sharpening enabled Dcs Res of cockpit display 1024 Anisotropic filt 16x SSA 1.5 Pixel Den 1.0 I'm also using the openxr toolkit using FSR upscaling with 90% size and 40% sharpness These setting are pretty well giving me a solid 45fps whether I'm in SP or MP even on 4YA's Syria server. This is using the oculus runtime and the force open xr shortcut for DCS. J Ryzen7 5800X3D. 64 gb ram, 6950XT 16gb, Winwing Orion F18, MFG Crosswind Rudder, 42 inch lg tv, Quest PRO USN VF31 F14A AE2 1985-1989 CV 59 NAS Oceana IL ANG 183FW/170FS F16C Block 30 Big Mouth 1989-2006 Full time tech Retired E8
Recommended Posts