Jump to content

Recommended Posts

Posted (edited)

Recently started flying DCS again after several months off. To my dismay I am locked at 10FPS in VR in maybe 7 ouf 8 starts. Occasionally there is a normal start during which fps is in 80-90+ range. I've never experienced any similar problem in the past. This is using latest Varjo update, Nvidia drivers and QVDFR. Anyone else seeing similar issues?

Edited by Stellatny45
Posted

I have started to experience crap like this about couple weeks ago...   I am all good locked at 45fps then randomly frametime shoots up a I sink to 20fps for 5-10sec...
Tried everything so far... remove mods, check windows power setting, updated nvidia driver and reset its settings... nothing works and it seems to get worse rather than better. 🫤 

i9 14900K / 64GB / RTX 4090 / Varjo Aero / Winwing Orion2 + F15EX / Virpil Wrbrd + Alpha Stick + ACE pedals

Posted

Check to see if openvr is enabled or disabled in varjo base.  I think some hardware/steamvr configurations causes varjo performance to tank if openvr support is enabled.

Just untick the openvr box, leaving openxr enabled and see if it improves it 🙂

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.

Posted (edited)

What I've learned so far is that I can run DCS MT in the Aero as long as I do not invoke the Varjo foveated mod. Unfortunately that only gets ~60fps in free flight scenarios. If Varjo foveated is activated fps drops to 10. I have confirmed that Steam VR is using Varjo as the active XR runtime. Varjo foveated log reports:

2024-01-29 06:57:19 -0800: Using OpenXR system: AERO
2024-01-29 06:57:19 -0800: supportsFoveatedRendering = 1
2024-01-29 06:57:19 -0800: Trying to locate configuration file at 'C:\Users\Dad\AppData\Local\Varjo-Foveated\settings.cfg'...
2024-01-29 06:57:19 -0800:   Found option 'peripheral_multiplier=0.70'
2024-01-29 06:57:19 -0800:   Found option 'focus_multiplier=1.5'
2024-01-29 06:57:19 -0800:   Found option 'horizontal_focus_scale=1'
2024-01-29 06:57:19 -0800:   Found option 'vertical_focus_scale=1'
2024-01-29 06:57:19 -0800:   Found option 'turbo_mode=1'
2024-01-29 06:57:19 -0800:   Found option 'no_eye_tracking=0'
2024-01-29 06:57:19 -0800: Peripheral resolution: 1162x994 (multiplier: 0.700)
2024-01-29 06:57:19 -0800: Focus resolution 1614x1614 (multiplier: 1.500/1.500)
2024-01-29 06:57:19 -0800: Peripheral resolution: 1162x994 (multiplier: 0.700)
2024-01-29 06:57:19 -0800: Focus resolution 1614x1614 (multiplier: 1.500/1.500)
2024-01-29 06:57:24 -0800: Creating swapchain with resolution: 1396x1192
2024-01-29 06:57:24 -0800: Creating swapchain with resolution: 1396x1192
2024-01-29 06:57:24 -0800: Creating swapchain with resolution: 1614x1614
2024-01-29 06:57:24 -0800: Creating swapchain with resolution: 1614x1614
2024-01-29 06:57:27 -0800: Application is using Quad Views for this session.

Again, these problems are new to me after having been away from DCS for several months.

Edited by Stellatny45
Posted
10 minutes ago, edmuss said:

Check to see if openvr is enabled or disabled in varjo base.  I think some hardware/steamvr configurations causes varjo performance to tank if openvr support is enabled.

Just untick the openvr box, leaving openxr enabled and see if it improves it 🙂

Will do & report back!

Posted
37 minutes ago, edmuss said:

Check to see if openvr is enabled or disabled in varjo base.  I think some hardware/steamvr configurations causes varjo performance to tank if openvr support is enabled.

Just untick the openvr box, leaving openxr enabled and see if it improves it 🙂

Thanks. I did what you suggested and was able to get a solid 90fps on a default takeoff and circuit of Vaziani!

  • Like 1
Posted

Good stuff, always the simple things!
I don't know if the issue lies with valve or varjo, I think it's the former though with a steamvr update (possibly a beta?).  I've not had the problem and can run openvr and openxr via varjo base without issue; I'm on an older GPU though, perhaps it affects the 40xx?

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.

Posted

im running a 4090 with VR and XR enabled it doesn't have an impact on performance either way (for me)

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

1569924735_WildcardsBadgerFAASig.jpg.dbb8c2a337e37c2bfb12855f86d70fd5.jpg

Posted

I'm still running 3090 series and 5900x. I recall the Varjo foveated mod instructions suggesting to leave both modes enabled in Varjo base. I am using the Steam beta.

Posted (edited)

The bug is there since end of december after a SteamVR stable update. (Bug has been reported in the beta, but no one cared.)

It  affects DCS even if the Varjo OpenXR is used. (SteamVR components are used for tracking) -  It throttles DCS to 10 fps.

Only people with Steam DCS / or Steam MSFS are affected for some reason. I use DCS standalone and don't have the problem.
A friend experienced it when setting up his new aero. He switched to DCS standalone and had no issues any more.

A workaround is disabling OpenVR in Varjo Base. Another workaround is using an older SteamVR Version, e.g. the 1.27.5 beta.

I'm losing hope this will geht fixed: https://steamcommunity.com/app/250820/discussions/3/4036978698787139585/
It feels like the Aero is already dying. 😞

Edited by Sile
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...