VR Discussions, Questions & Feedback

Try the helmet view in the game. You can go down to 0.3 vertical if you want the real driver fov. Take a look at Max Helm.
Reddit - Dive into anything

 

The difference with OSW/ASW is the latency. Especially on the steering wheel and pedals. Half frames, half as accurate. But that also has a lot to do with the steering wheel and the car in the game. The entries are delayed. The slower the steering wheel and car, the less you notice it.
And beside that 120/60 is good. 72/36 is noticable

 

Max Quest 2 resolution, 1.1 supersampling and 650 fixed bitrate (the max I can go with link stable).

Daylight, 120Hz full grid fixed, with a mix of high/ultra settings. Lower vertical FOV is life!

 

I like to "cheat" .675 in vertical FOV, because I don't loose the necessary vertical FOV in side view.

 

AV1 10bit (Quest 3) with Adaptive Quantization turned on is a winner for me.

 

I think it depends on your IPD how much you get out of the FOV adjustment. I have an IPD of 70, and run around 70% FOV now. Still experimenting, though.

 

No, I don't think it has much to do with IPD. Mine is 69, and I have a Quest 3 and can see the edges of the screen. I think it's more about the distance of your eyes from the lenses that determines how good your FOV is. I bought a very thin aftermarket facial interface, which let me press the quest very close to my eyes. With the default or a halo interface, your FOV is worse, and thus you can get away with FOV adjustments.

 

I'd have to agree it's more about the distance from the lenses. My IPD is 59, right on the minimum for the Q3.

 

In Quest 2 at least IPD and eyes distance to lenses have influencie, in my testings. I use glasses, so, my "scuba" FOV is crap anyway, but I use the highest IPD. If I set .675 horizontal FOV in lower IPD settings, I can see the internal bars of the screen.

 

Never tested but I am away from pc now. Does lowering vertical FOV in Oculus debug tool work in Virtual desktop?
BTW AV1 10 bit on 90HZ is way to go for me. Even we play while seating and Link cable is not much of an issue, playing without it actually free you to enjoy and forget that that you are playing game.

 

You are probably right, I totally forgot I have an aftermarket facial interface, which put my face a bit further away from the lenses

 

It doesn't work.

 

Max Quest 2 encoder resolution? is that 3680x1920 total or can it be pushed higher? What about the games rendering resolution in SteamVR/OpenXR, did you just match it to the encoder resolution or is it different?

I ask because I tried to get a PSVR2 running at 120hz and looking good and couldn't really do it without severely limiting the image quality, and that's with a 4090. I quickly switched back to 90hz. Maybe I should try again?
Just curious if you think the trade off is worth it for the extra frames? Can you notice a difference in smoothness over WIFI?

 

I run in default 3680x1920 encoding and Max Quest 2 resolution. I really do not need to compromise image quality with lower FOV settings. Will try to go up a little in encoding resolution.

I only use link cable. My wi-fi router is crap.

 

You do get that you're running the game at a really low resolution don't you? For eg. Virtual Desktop modes are "Low: 1728x1824 Medium: 2016x2112 High: 2496x2592"
When I ran a Pico4 with a 3090 I ran around 3100x3100 per eye 90hz. You're not even hitting the 1:1 pixel scaling of your headset panel when you factor in the distortion profile.
But if you're happy with it running at 120hz at low res, fair enough, who is anyone to judge you.

 

You are doing a little confusion with these numbers.

Quest 2 and 3 users have to live with compression when in PCVR, and lower encoding resolution than headset display. A Display Port headset is another thing: no compression.

Another thing is the app render resolution, supersampling, etc. All these settings improves image quality even in a compressed final image streamed to these headsets. With a compressed image of 4096 width, the decoder of Quest 2 can't handle without glitches, so, I run in default and ramp up bitrate. And the image quality is the best I can get with this crap encoding hell. Higher bitrate is better for headsets streaming than bigger image resolution.

My Quest 2 Link settings. The max image quality I can get with Quest 2 in my tiny FOV:



And my ingame settings, a mix of HIGH/ULTRA settings, without grass because I don't like grass and lower a bit particles to don´t bother of distant sparks in VR:

Not really "low resolution".

 

And one REALLY important note, regards the point about Virtual Desktop compressed image resolution and wireless PCVR:

If a connection have better bitrate than other, usually the streamed compressed-uncompressed final image is better in headset - even at a bit lower encoding resolution - regards bigger bitrate vs bigger resolution.

 

And a final point about why I'm loving 120Hz in AMS2:

I recorded this video at fixed 120FPS. As all you can see, the transition from 120 to 60 FPS with ASW looks even better than in the video, because of fake frames, and I can't even feel the kick in of ASW and only can notice it's active when I look at the side and see minor ghosting in really fast moving vertical objects like poles.

As said, I'm happy!

 

I’m happy with my steady 90fps. No frame dropping no AWS kicking in. I instantly notice the AWS kicks in, in your vid. A no go for me.

 

ps: both are true. Both the distance between the eyes and the distance to the glasses have an influence on the Fov. You're both right.

Win/win ;D