*** Oculus Quest 2 Owners Thread ***

Done a bit of testing and it seems that 300 bitrate is the sweetspot. Although I wouldn't call it 100% stable it's a lot better than it was at 500.

I wish oculus would release a headset with proper display port support instead of this bs streaming crap.
 
jonnylaris said:
1 in the Oculus app and 1.5-1.6 in ODT
Click to expand...

Yeah, you should set the ODT back to default of 0. And change the Rendering resolution to whatever value you feel that the game is still playable.

In the Oculus App, 1 isn't native resolution, it's undersampled. So when you use SS in the Debug tool, it's applying super sampling to an undersampled image.

In actual fact, 1.7x render resolution is the real native resolution.

You should set all the values in the Oculus debug tool back to default. And change the Encoder bitrate to 250/300 and use the highest render resolution you can.
 
melmac said:
Yeah, you should set the ODT back to default of 0. And change the Rendering resolution to whatever value you feel that the game is still playable.

In the Oculus App, 1 isn't native resolution, it's undersampled. So when you use SS in the Debug tool, it's applying super sampling to an undersampled image.

In actual fact, 1.7x render resolution is the real native resolution.

You should set all the values in the Oculus debug tool back to default. And change the Encoder bitrate to 250/300 and use the highest render resolution you can.
Click to expand...

I'm not sure if this is true because either way it displays at the same resolution in steam VR for example.

All super samping does is increase the rendering resolution. There is no such thing as an "undersampled image", it's just how many pixels are being output.

I'll try it here anyway and tell you if I see a different in picture / fps but I very much doubt it.
 
Last edited:
jonnylaris said:
I'm not sure if this is true because either way it displays at the same resolution in steam VR for example.

All super samping does is increase the rendering resolution. There is no such thing as an "undersampled image", it's just how many pixels are being output.

I'll try it here anyway and tell you if I see a different in picture / fps but I very much doubt it.
Click to expand...

You can believe what you want.

But, The facts are that, because of distortion in the lenses, 1 to 1 native resolution is at the max render resolution in the Oculus app. And yes, at any other value than max you are undersampling at the centre of the lenses.

Render resolution is not equal to super sampling.
 
melmac said:
You can believe what you want.

But, The facts are that, because of distortion in the lenses, 1 to 1 native resolution is at the max render resolution in the Oculus app. And yes, at any other value than max you are undersampling at the centre of the lenses.

Render resolution is not equal to super sampling.
Click to expand...

Tested your method of setting rendering res to 1.7 and ODT to 0 and it made zero difference.

Both methods resulted in the exact same image quality and FPS.
 
I've submitted a support ticket to make Oc
melmac said:
You can believe what you want.

But, The facts are that, because of distortion in the lenses, 1 to 1 native resolution is at the max render resolution in the Oculus app. And yes, at any other value than max you are undersampling at the centre of the lenses.

Render resolution is not equal to super sampling.
Click to expand...

Just to back this up, oculus coder -

https://twitter.com/x/status/1328145529042137088
 
chorse said:
I can't work out how to access filesystem via windows 10, i've tried the first handful of guides I've found but no joy. It just won't show as a drive.
Any tips?
Click to expand...
Did you solve this? I'm having the same problem. Sidequest can see my quest 2 from my pc, i can sideload apps ok, but i can't access the quest as another drive in windows explorer.

EDIT: sidequest has an equivalent to windows explorer where you can drag and drop files from your pc to quest 2 and vice versa. would still like to know why it doesnt appear in windows explorer though.
 
subroutine said:
I've submitted a support ticket to make Oc

Just to back this up, oculus coder -

https://twitter.com/x/status/1328145529042137088
Click to expand...

I never argued that 1.7 render resolution on q2 was native, I knew that.

My argument is that render resolution IS super sampling, which is why I saw no difference in my tests.

Doesn't matter if you set it on Steam, Oculus or ODT, they all do the same thing.

Explained in detail here.
 
Weird thing happening for me with Audica - I just completed the first lot of levels and started on the next set - for the first time I'm having to swipe the gun to knock the 'balls' out of the air and to do the chain shots. Now, these worked in training, but they are not working here - the chain shots just don't register bar the initial shot and knocking the ball out of the way seems completely random and worked a couple times at most.

I went back to the tutorial to see what I'm doing wrong but the tutorial stops at the chain link shot saying I need to hold the trigger (which I am). It's weird because the one where you just hold the trigger is working fine.

Any ideas?

Edit - weird, so I tried taking batts out and putting back in controllers - no joy. I tried re-launching the game - no joy. I went into settings to see if there was maybe something I had changed...couldn't see anything, thought I'd try one of the songs again and it worked!?
 
Last edited:
AFAIK, setting the render resolution in oculus home auto sets the Encode resolution width which does effect the image quality. ODT has no effect on that setting.
 
Got my Quest 2 last night, played around with it and some Oculus apps, as well as using Oculus link to play Phasmaphobia with some friends (VR co-op horror game). Had an absolute blast and a right laugh, but went to bed feeling like it would very much be a gimmick and after the novelty worn off I'd probably not use it again.

Then this morning I play Star Wars: Squadrons in VR. Good lord! My mind was absolutely blown. Such an incredible experience and that game is just meant to be played in VR. Looking around the X-Wing cockpit, and frantically looking around when enemies fly behind you etc just absolutely amazing. That has completely changed my mind, and if there are more experiences like that to have then I'll be very happy

Bought Half-Life: Alyx for later as well
 
Since V25 I get 2.0 Gbps USB test speed whatever USB port I try. Things are working fine, all smooth with using Encode Bitrate = 400Mbps. I used to get around 2.6 to 2.8. This is with Anker cable rather than Oculus fibre optic one

My case is fairly old so I got a "EZDIY-FAB 2-Port USB3.0 Type A and USB3.1 Type C GEN 2-5.25 inch Front Panel USB Hub" fitted today, to give me extra front USB 3.0 ports plus a USB C port. Looks great & brings my case up to modern standards.
These extra ports also give 2.0 Gbps in the Oculus USB test.

Anyone getting more that 2.0 Gbps since V25 ?
 
Andy D said:
Since V25 I get 2.0 Gbps USB test speed whatever USB port I try. Things are working fine, all smooth with using Encode Bitrate = 400Mbps. I used to get around 2.6 to 2.8. This is with Anker cable rather than Oculus fibre optic one

My case is fairly old so I got a "EZDIY-FAB 2-Port USB3.0 Type A and USB3.1 Type C GEN 2-5.25 inch Front Panel USB Hub" fitted today, to give me extra front USB 3.0 ports plus a USB C port. Looks great & brings my case up to modern standards.
These extra ports also give 2.0 Gbps in the Oculus USB test.

Anyone getting more that 2.0 Gbps since V25 ?
Click to expand...

your right

I've dropped from 2.9 to 2.1 ?

incidentally, i still haven't got the move app from V.2.1
 
Mine has dropped to 1.8Gbs from 2.7Gbs. On the Official Link cable too.

I am on an AMD x570 motherboard. What are you guys using?

I wonder is it reserving bandwidth for the Link connection?
 
You must log in or register to reply here.
Back
Top Bottom