VR Discussions, Questions & Feedback

Surprised you're getting a clearer picture with Virtual Desktop than with the Link cable. Are you maybe not running high resolution and bitrate with link cable? The resolution you can set in the Oculus desktop app, and the bitrate in the Oculus Debug Tool. Using H.264 you can paste in a number up to 940 for the bitrate. (need to paste, as typing in doesn't let you go as high)

 

I am also getting a significantly better image, framerate and graphics quality with Virtual Desktop over direct Link Cable. No matter what bitrate i set in the Debug Tool the visual artifacts were awful, while with Virtual Desktop they are non-existant and framerate is smooth.

 

Maybe I need to revisit it, and see what I'm missing out on What codec and bitrate are you using with Virtual Desktop?

 

H264+ and currently playing at 320 bitrate

 

You're right... Downloaded .dll the link you provided and put it in my game folder and OpenXR Toolkit works! Thank you very much for your help!

I was surprised too. Was running 200 bitrate through virtual desktop with h264 then 300(or320, can't remember) with h264+ in that setting. Probably wont use this again though as the linked version (opencomposite + openXR toolkit) with the .dll looks just as good now.

I set the oculus debug tool to 700 before(running 700 now with this new setup too), didnt seem any better but I think it might have something to do with what UrsineSaturn9 mentioned? almost like it wasnt working until now.

Yeah I feel your pain, spent all yesterday into the early hours trying to solve it. Maybe try that .dll linked above?

I have spent today tweaking again and think I'll settle for what I have got now, much less artifacting on the tarmac and distance specifically. getting a fair bit of aliasing though, specifically at night (back of those LMDhs look partularly jagged which is a shame), but I think it'll have to be a compromise unless anyone has manged to reduce it considerably.

One think I have noticed in the OpenXR toolkit is it says runs at 45fps then says GPU bound (feel like if anything should bottleneck my pc its my cpu) but when I turn turbo on it runs at 90, with only some frame drops when 29 cars are around me. love to not have the boost on as I'm aware its an experimental mode, just not sure why I seem to be constricted at 45fps if its not on. Again something obvious to some who knows what they are doing I'm sure.

 

R7 5800X and 3060Ti, but now (don´t ask me why) Madness Engine likes more cars at MEDIUM than LOW for FPS here. For VR, a lot of changes in LOD and textures loading aren't so straight foward. The only tip I believe it's right is: test everything in a lot of situations.

 

Sounds like ASW kicking it. You can disable that in Oculus Debug Tool, but you need to toggle it on/off every time after you launch Oculus Home or the setting doesn't stick (or use the KB shortcuts if you prefer).

Turbo mode is kinda like magic. If it works, it works! Also, I prefer to use the override resolution function in OXRTK rather than use Oculus sliders or pixel density so I can precisely set the resolution to something I know will be stable for most situations on my PC without being GPU limited (~3000x2500 per eye for me with FSR 72%, sharpening 90%)

 

Wow you have a weak GPU so I am impressed if you can have a smooth experience

is that also at night or rain conditions?

I mean I have now a 4080super and I was optimistic to enjoy rain and night locked 90fps but I still have scenarios with light reflections or heavy rain mist where the card struggles

what’s your headset and rendered resolution?

 

I thought I tried that but maybe I hadn't, will try in the morning.

Ah ok you mean upscaling/sharpening set to FSR? what do you set in the oculus debug tool or does it not matter if OXRTK is overriding it?

It look so much better now this feels like the leap up I was looking for so thanks for the help.

The next thing I'd like to figure out is the aliasing on the cars at night. It looks like its when the edges are illuminated by headlight that it sticks out the most. Day time I only really get noticeable aliasing on fencing(there is a few other places but thats the top of my head one) but its not much at all compared to lit up car edges. I'll try a few things tomorrow and see where I get.

Just for documentation going to put this here too, as I spent hours searching here and the rest of the internet, then trying things over the past couple days to get the quest 3 working with openXRtoolkit and with settings I'm happy with (for) now. trial and error in places and I suspect a lot could be changed for the better(if anyone spots any let me know) but I thought I'd post all my settings here if it helps anyone (and for me sometime soon when I reinstall everything and forget how to do this).

Spoiler: Quest 3, OpenComposite & OpenXR Toolkit Setup

SETUP


-------------
INSTALLS & DOWNLOADS

1- Install OpenComposite - downloade here - Campbell Suter (ZNix) / OpenComposite · GitLab
2- Install OpenXR Toolkit - download here - Quickstart
3- Drop LibOVRRT64_1.dll into steamapps>common>Automobilista 2 - download here https://github.com/rodolZ80/bypass-oculus-detector/releases

--------------
OPENING & RUNNING AMS2

1 - Open OpenComposite, set to below (not sure If this is needed to do this each time?)


2 - Open Oculus Debug Tool Settings (C:\Program Files\Oculus\Support\oculus-diagnostics)

Once opened redo settings set to the below, then service> Restart/start Oculus Device depending if the oculus app was already open or not

4 - connect quest 3 to oculus pc app via link cable & enable link
5 - Open OpenXR toolkt (not sure this is needed each time?)
use settings below

6- click play on AMS2 in steam and select "Launch Automobilista 2 in Steam VR Mode" (Steam VR shouldnt open if worked correctly)
7- If OpenXRToolkit is working you will get a greeting menu in VR and promped to press ctrl Down(or the assigned open menu control) to adjust settings.

--------------

In game OXRTK Settings
Upscaling/sharpening:FSR
Anamorphic: Off
Size 100% (2720x2976)
Sharpness: 23%
Fixed foveated Rendering: off
Turbo Mode:On
Frame Rate Throttling:90

Contrast: 39.5
Brightness:46.6
Exposure:56.1
Saturation:49.2
Vibrance:0
Highlights:55.4
Shadows:8.9
World Scale 100%
-----------
AMS2 PERFORMANCE & VISUAL FX SETTINGS

In-game performance settings
(C:\Users\{username}\Documents\Automobilista 2)

I'll put it here if its helpful to download
graphicsconfigopenvrdx11.xml
------------
Visual FX options in ingame settings
Post Processing Filters - ON
Exterior Sun Flare - Full
Interior Sun Flare - Chroma
Bloom - ON
Heat Haze - ON
Exposure Compensation - 1.00
Rain Drops - YES
Vignette - NO
Crepuscular Rays - YES
Screen Dirst - YES
Cockpit Mirrors - ON
-----------

MISC.

Nvidia Control Panel Settings


------------

I'll update this if I find/get told better options to use

 

Max resolution, but I use vertical FOV at 0.275 and horizontal at 0.675 (don´t loose any horizontal real FOV with this setting). Night/ rain with headlights and more than 10 cars visible, even with this extreme low vertical fov, ASW kicks in and can´t handle all the time 120FPS.

 

Ok now I understand as you set a very extreme FOV so you get the benefit in performance
I am leaving mine at full FOV both horizontal and vertical for now so of course it’s taxing on GPU power but its the way I like it. again, for now.

you have set 120hz in your headset parameters so you have a Quest2 right?

 

Nice read about VR the last couple of posts. As said earlier, I’m about to receive my quest 3 and I hope I can make it work. Dreaming of the simple setup up with the Rift CV1 back in the days to bad this won’t be the case with the Quest 3 if I read all the problems here.

 

Turbo mode breaks/disables Motion reprojection so I assume it does the same with ASW
It lets the CPU go on generating frames rather than waiting for the GPU to finish processing the last one.
It actually works quite nicely as an on/off switch for Motion Reprojection. You can bind a hotkey to turn it on/off and then if you're in a race and you're struggling to hit 90fps (or whatever your target is) you can hit the button to turn it off and go into ASW, which some people prefer to the stutters etc.
You were probably just on the threshold of hitting 90fps - the small boost from using Turbo mode and takling ASW away as an option meant you were spending most of the time at 90

 

Could it be that the latest few updates (with the better shaders) have negative impact for VR-performance? I lost quite some FPS but my Quest3 also forced me to install a newer Oculus- and Link-software so it could also have to do with those updates. The updates could also have reset some settings (maybe in Oculus software, maybe in Oculus Debug Tool?...). Unfortunately I haven't documented my previous settings anywhere...
The picture quality is gorgeous though, but have to find a way to crank my FPS up again...

 

Debug Tool I just set 0.8 vertical Tangent Multiplier and toggle the ASW on/off. Pixel density just left at 0, as the OpenXR Toolkit setting overrides this anyway.
FSR scaling at 72%
Sharpening at 90%
Haven't tried turbo yet I don't think in AMS2

 

I go for 0.9 Horizontal 0.8 vertical on the Quest 3 and even with headset as close as you can get it’s barely noticeable especially in tin top cars. ASW off as well.

 

I used to go 0.9/0.7 horizontal/vertical before I upgraded my PC to 7800x3d / 3080, but even at 0.9 I can notice it on the Rift S. Quest 3 (and 2) probably has more overscan than Rift S (and slightly bigger hFOV to begin with I think)

 

I am on a RTX4080 and I use openXR with toolkit but I didnt get what this virtual desktop is about?!
Can someone explain it to me why you use that 3rd party app that is sold on Steam?
My headset is an HP Reverb G2.

 

Here we're talking about Virtual Desktop for wireless headsets. It's the same dev but a different app and it's for streaming directly to a wireless headset, Quest, Pico etc. It's not something you need to think about.

 

Is it also the case with you that the spark of the vehicle in front is displayed correctly in the left eye, but much too far to the right in the right eye? At first I thought that no sparks were visible in the right eye, but they are simply further to the right.