VR Discussions, Questions & Feedback

Can someone give me list what I need / how to setup to have the latest and greatest VR setup with Quest 3 + VD where I'm able to crop the FOV?

Got a new PC and previously I was using
- open composite
- openXR toolkit (non-modded with FFR, but no FOV cropping)
- Virtual desktop (VDXR, H.264+)
(I was able to get this working very well with the limitations of my old PC, steady 80fps, no stutters and all that)

Now the VD has the FOV Tangents, but those don't seem to work correctly with OpenComposite and not at all on SteamVR (at least for me) and I haven't touched the modded openXR toolkit with the FOVCroping feature.

I could use the way I was doing it before, but if there is now better way (definitely want either FFR or FOV croping to get better headroom for the game).

ps. I'm using the LAN adapter with quest, so it's definitely VD based solution and not Link cable.

 

I use Oculus Tray Tool with Link cable and i am quite happy. I modified fov, encoding bitrate, etc. It is flawless for me.

 

Follow this guide, the link for the OpenXR toolkit 1.3.8 (modded) is in the description. I use the same setup as you, VD over LAN cable on a Quest 3. The FOV crop saves much more performance than FFR, even at conservative settings. I use 70% vertical, 93% horizontal, no FFR at all, perfectly happy with it.

 

Okay, so there is still no way to use VD's own FOV tangents with AMS2, you have to use OpenXR toolkit and all that? (even with my old computer, I got good performance no matter the conditions with just tuning the FFR well (and some in game settings, like having reflections on low), way before there was this modded version with FOV crop functionality available).

 

I haven't tried VD's FOV tangents TBH, as I have set up the OpenXRtoolkit cropping before that was available and couldn't be bothered. It might work though. But the modded toolkit was super easy to set up

 

VD's own FOV tangents work fine, I use them
I prefer SteamVR because of the fpsVR and Reality Mixer apps.

 

So what do you have exactly installed to make it work with Quest 3 and AMS2? Just game, VD and steam vr? Do you have the SteamVR set in the VD Streamer app (when you can also select "auto" and VDXR)?

When I tried the FOV tangets and started the game in SteamVR mode, they didn't do anything (I had open composite installed, but it was set to "SteamVR"). I just realized that in the VD Streamer app, I had the VDXR selected (so not auto or SteamVR), maybe that interfered?

 

Just game, VD and SteamVR. I have the streamer set to SteamVR, but I don't think that matters when OpenComposite isn't installed. I'm starting the game by starting VD, then starting SteamVR from within VD, then starting AMS2 from SteamVR.
(I have played a bit with OpenComposite in the past as well, but then by manually copying the DLL's back and forth so I had full control over which runtime was used.)

 

It makes no difference to me whether I crop the FOV with VD or Toolkit. Both perform equally well. But it definitely works. VD/Ethernet/Opencomposite/VDXR.

 

This is really strange, it didn't work for me at all when using OpenComposite no matter what I tried. The game menu's got twisted if I had OpenXR/VDXR selected and turned my head and on track there was no fov crop (and yes, I tried dramatically reduce the vertical fov to make sure it's visible).

EDIT: do you have the quest 3 pc link app installed?

 

Yes, the Oculus app is installed.

Did you perhaps forget to restart after cropping the FOV?

 

Ok I've had my 9070 XT OC for a week now and it's awesome, 100% Res in SteamVR (up from 70% previously) with pretty much solid 90fps with higher in game settings. Rain/Night do bog it down slightly so I'm yet to make some adjustments for those scenarios, but overall it's a massive jump in performance from my old 3070ti.

Anyway, anyone else running AMD and have you got any tips for the Adrenalin Software settings? I've had a look and a Google but can't seem to work out what might be good for VR and what might not work at all in VR.

 

I have my Steamdeck set up to control AMS2 menus to save the headache of fumbling with a keyboard in VR. Usually pressing "Esc" backs out of the menu and saves , but on some things such as the screen where you select the track date/weather and the ai difficulty page it requires a click on the "save" box before it saves the changes.
Does anyone know the shortcut key for Save?

 

Great buy. Much more VRAM now. With a 4070 Super and "just" 12GB of VRAM, I lowered textures settings to MEDIUM and tweak settings to minimize texture streaming and keep 80 FPS in the more demanding scenario with 20 cars on track, anytime, any position.

 

Fired automobilista up today 1st time in a few weeks. Before the latest update my vr was running almost perfect. Today though it’s turned back into a stuttering mess after update. I have tried all the usual tricks ie verified files, checked space warp isn’t at 45fps, restarted couple of times. I tried a couple of combos in game but same outcome

anyone experienced the same and have a solution?

my specs should be in my sig below

thanks

 

Also experiencing oddities with Quest 3, some recent update really messed things up. I use Virtual Desktop and currently fiddling with different Nvidia drivers to try if it improves.

 

Can't say that i've experienced any issues, but i'm still running an older version of the nvidia gpu drivers.
Quest 2 using VD with ethernet adapter.

Might be worth checking task manager to see if something is using a lot of cpu/gpu other than ams2

 

Virtual Desktop Quest 3 Nvidia users:

Since the latest recent Q3 update i had very bad microstutters even if the headroom and fps counter and all performance stuff was showing that it should run smooth as butter.

So i took a gamble and updated my GPU drivers to the newest possible 591.44. It fixed ALL of my performance issues ! For a long time i was running drivers from several months back. Maybe i got lucky with this Nvidia update but hey it works.

 

I see you have a Neo which I am struggling with at the moment. the close up image is great really sharp and clear, but distance is a terrible blur. e.g. Old Spa down towards the kink are 3 distance boards. as they get closer on my approach, I can only actually read them when they are almost alongside, like with the front end of the Vintage F1 car. I've tried the TAA settings but not found any that help. I have the Neo too, mine with an RTX 5080. any suggestion what I might try would be appreciated.

 

Something that really irritates me with VD is how they recommend old drivers (566.36) but never give a reason why. From what I've seen it's usually a very isolated problem that may affect a small percentage of users. It would help if they'd say "why" they think it's smart to stay on a driver that was released over a year ago so people can make an informed decision. I quit listening to their recommendations as I don't find their tech support to be helpful in any way.