VR Discussions, Questions & Feedback

wait what? this will give me a performance increase? oh god, I have a 4k screen atm lol

 

it did with me! But beware: the first screen looks low res. but once you enter the game its "vr" resolution.

 

same here, but be aware, using the mouse in VR it can sometimes lose focus if you click outside of this window and it is smaller than your native res, e.g. a 1920 x 1080 window. Or sometimes you can have another app/window opens on top of this. but it is simple to refocus the mouse if/when this happens.

 

Is there a chance, that we will ever get stereoscopic mirrors? Assetto Corsa has that feature and for me in VR it makes a huge difference in immersion. Feels also easier on the eyes to just look in a mirror like a mirror is expected to be instead of looking at a 'screen' that is mounted at mirror distance.

 

We can only hope.

 

I'm happy now with these settings and 120Hz. Really good:

 

Looks great. But to be honest...thats the Desktop View a d not the VR View.
Your real Fov is alot smaller with your Settings.

This should be mentioned again in order to be able to compare better.

Ps:I think I found a little fix yesterday. I usually use stationary mode in the Oculus Guardian, as I can now see, it works a little better with the room view if you draw a radius of 3m (ect) around you. In the stationary view, the Guardian is sometimes moved so awkwardly (happens when you take the glasses off every now and then) that the round area is shown on the floor. So you no longer sit completely in the middle. This reminder of the limit can lead to small hiccups (really small) but noticeable. Draw a generous radius around you to prevent this popping up and to relieve the strain on the oculus when decoding.

 

With these FOV settings I don't loose any real horizontal FOV with Quest 2. And with 120Hz, isn't necessary anything bigger than visible FOV. 0.675 and 1.0 looks the same for my IPD and I have FPS for free in headset. The "FOV" seting in Quest 2 isn't really about FOV, its the size of the rendered image in headset screen, and with higher FPS and refresh rate, you really don´t need a buffer besides visible.

And the vertical FOV is bigger than a real racing helmet, so, I'm happy with these settings.

PS: the rendering in 2D is from left eye, and with a lower horizontal FOV than visible in headset.

 

PS2: I disabled Guardian. Runs better without this.

 

Quest 3 Virtual Desktop users, how many use the "H.264+" codec ? For many months i used that one with 320 bitrate and while decent, there was always noticeable latency and still visual artifacts.

Today i decided to try the "AV1 10-Bit (Quest 3)" and even at the maximum of 200 bitrate it seems to look just as good if not slightly better than H.264 and the latency also. Anyone else tested this ?

 

I’m running H.264+. Recently purchased a Quest 3, and haven’t tried any other codecs yet. Also read somewhere that H.264+ is the one working best with AMD cards…

 

I didn't want to criticize that at all. I do it the same way. 0.8x0.8 for me. Unfortunately I can't go any deeper without seeing the edges. I even used 0.8x0.3 with a racing helmet. But since an update, the helmet view has unfortunately been moved too far up. I think it looks somehow broken or buggy. Since I like to drive the Formula Junior and the P3, I use 0.8x0.8 again for open cars, it bothers me to hide too much vertical fov. It looks like you are looking at a 16:9 3D screen. But with GT3 and stuff like that I don't have any problems with it. It even seems (according to the helmet view fov) more real.

ps: You are absolutely right. Shut down the Guardian completely. I hadn't even thought of something so simple. Thanks!

 

What GPU do you have? I get only a stable 90FPS. With 90 FPS in the Oculus settings. And in AMS all maxed out. But I never see 120FPs. And certainly not during rain.

 

Should have wrote my specs: RTX 3060 Ti, Ryzen 7 3800X, 64 GB Ram, Windows 10 .
Maybe the H.264+ is more suited for AMD.

 

AV1 at 200mbs has plenty of compression artifacts. Just try Monaco and checkout the tarmac texture. I run H264+ at 500mbs. I do have a dedicated 6ghz router for the purpose though. AV1 artifacting is less noticeable at other tracks though so it really depends.

Even at 500mbs you can notice compression artifacts, but they are less noticeable than AV1 at 200mbs.

As far as compression artifacting goes, you can't beat wired at 940mbs, but Wireless via Virtual Desktop is the best way I can keep my Quest 3 charged whilst playing. Tried everything, but best result is to plug my headset direct into wall so wireless H264+ at 500mbs it is.

 

I am also plugged into wall and that keeps the battery at 95% all the time every time. I trued plugged into the PC but i cannot go above 320 MB bitrate without having audio cutting out and then the battery also running out slowly.

How did you reach 500 mb bitrate though, did you turn off the automatic bitrate adjustment ? I thought it was important to keep it on, i have a Wifi6 router.

 

Yeah, turned off "Automatic bitrate adjustment". Never ever used it. It took me ages to be able to run 500mbs though. Bought a TP-Link Archer AXE75/AXE5400 wifi6 6ghz router for the sole purpose that sits literally 3 feet from my headset. Runs solid 500mbs, no stutter.

I should add that I tend to run 72hz though so I can ramp up the visuals and have some headroom (I hate stutter). Having said that I can run AMS2 easily at 90fps during the day. 11900K/RTX4090.

 

4070 Super. The trick is play with Quest FOV adjustments.

With this GPU, I can use link in Max Quest 2 resolution and 650 bitrate, and get rid of a lot of compression.

Rain and headlights on I go for 60 FPS with ASW auto. 120hz reprojection (ASW) is amazing, and I really can't feel when it kick in or any big difference even in daylight with ASW 60FPS in 120Hz. 120 FPS in rain, only with REALLY lower settings with headlights on.

 

With my setup, the best I can get out of FOV adjustment without noticing my FOV visibly shrink in the headset is about 95% which makes it completely pointless so I never bother with that. I don't know how people get away with FOV figures like 85, that closes in my view so much in my Quest 3 its not worth it.

 

Do you not feel like you're missing out on a lot of image clarity by having to to lower settings to run 120hz, or is it locked 60hz?