Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem


The only thing I can think of that might cause this that was added in 2.2.x is re-enabling of Advanced Supersample Filtering. You can try disabling this under VR Settings > Video (set Advanced Settings in the lower left to Show).
Also, if you go to C:\Program Files (x86)\Steam\logs you should find a vrclient_DCS.txt file.
The start of each run is demarcated with:
Further down you will see output like the following:
I'd be interested in what these say for your setup between 2.2.3 and 2.1.10.
Steam VR 2.2.3- Stutter-DCS-Unplayable with Update
I had enabled SteamVR Beta until it updated a couple of days ago. When the Beta update dropped-DCS became uplayable due to stuttering. Prior to the Beta update a couple of days ago no stutters or issues. I disabled SteamVR Beta and it returned to no stutters or issues. When Steam VR 2.2 dropped a couple of hours ago it is now unplayable, due to stutters the same as when the Beta update dropped.
90 FPS prior to 2.2.3 update
9-10 FPS after 2.2.3 update
Disabled Advanced Super Sampling-No Effect
Before I touch my headset I start Steam VR and DCS. It is at 90 FPS. After picking up my headset or slightly move the headset, the FPS immediately drops to 9-10 and STEAM VR goes into stand-by mode and asks my to put on the headset. but the headset still has screen views. As long as the headset isn't moving the FPS is 90. Once it slightly moves the FPS drops to 9-10 and SteamVR goes in to stand-by mode. FPS remains 9-10 while SteamVR is in Stand-by mode, the headset is moving, but showing the screen.
Windows 11
Varjo Aero
RTX4090
i9-13900k
DDR5 6800 96GB
The SteamVR environment itself is no problem at all, but in-game it is just horribly broken.
Varjo Aero, 7950x3d, 4090.
Varjo OpenXR locked to 10fps
Switching to Steam OpenXR game loads robot the load screen but then crashes when trying to play.
Therefore cant play DCS.
Incidentally MSFS was the same 10fps issue, but switching to Steam openXR fixed it.
Before it helped to opt out of beta, this isn't possible now.
What's strange is everyone with the problem seems to have DCS in Steam.
Standalone Users seem to be unaffected. Friend switched form SteamDCS to Standalone and the issue was gone.
Disabling OpenVR in Varjo Base seems to help mitigate the issue as well.
https://developer.valvesoftware.com/wiki/SteamVR/Installing_GPUView
That sounds broken. Did the Varjo Aero always behave this way, or is this new?
If you set "Pause VR when headset is idle" to Off, does this make any difference?
(Under VR Settings > Video w/ Advanced Settings = Show)
I can confirm this works. SteamVR does throw an error when launching, but everything works fine after clicking the message away.
It seems with 2.2.3, SteamVR gets loaded everytime I put on the Aero, even when not running a game or something in OpenVR. This somehow causes the performance problems when running an OpenXR game it seems.
hi, what do you mean by "SteamVR gets loaded?"
Do you see the little steamVR window now with the new steamvr?
(because the vrserver.exe server got loaded before in background for tracking and was only visible in task manager)
This wasn't the case before. Actually, before when I was in an OpenXR game, Steam wouldn't show anything about me being in VR. I know before some parts of SteamVR gets loaded because of the lighthouse tracking, but something has changed for sure with 2.2.3.