? best out of Quest 3 ?

I used to experience the problem in my Q2 until I followed the instructions in this thread:

Source: https://www.reddit.com/r/OculusQuest/comments/11whl3d/workaround_found_for_transparent_horizontal_lines/


The issue is to do with the image being split into 5 parts for encoding - the solution was to force 1-slice or 3-slice encoding (I used 3-slice and never had the problem again).

I’ve not tried it with the Q3 yet (I’ve not seen it with Link) though something may have changed with encoding if it’s happening in AirLink now. I’ll have a check to see if my registry is still set at 3-slice. Edit2: it had reverted to 5-slice.

Edit: apparently since I last read the thread, the Oculus Debug Tool has been updated and you can deselect sliced encoding (it’s in one of the more recent comments) and choose either H.264 or H.265 codec 👍
You absolute star, thank you!
 
I am going to return my Quest 3. Hope Saturn (huge chain of stores in Germany) takes it back.
1. Link is . . . unreliable is a nice way of putting it. My mainboard's USB-C port is not recognised at all (works like a charm with the Rift S!), the other ports . . . "wonky" would be a good way of describing it. SOMETIMES it works, mostly not. I haven't got more than half an hour out of it -- most of the time was spent troubleshooting. Note that NONE of my many USB devices have ANY problems with ANY of my USB ports.
2. When looking to open the panels (navigation, comms etc.), I have to lower my head (unnaturally so) to get to open them and STAY open. Never had that problem with the Rift S. I tried resetting HMD -- no joy. SERIOUSLY annoying. Worse, I cannot look straight an object to focus on it, I have to point the headset BELOW and peek up, which puts more stress on my neck. I've had several serious spinal disk incidents, keeping my head bent forward, even for a short amount of time, becomes painful in no time at all. With the Rift S, that was never an issue.
3. Too dark. I tried upping gamma, but that only results in it looking washed out.
4. (The REAL killer): No matter the settings, it just isn't as smooth as with the Rift S. Given that I have a 5800X3D and an RTX 4090 (B550 Pro 4, 64 GB of DDR-4 3600, NVME2 w. 4GB (PCIE-4, decent speed), Win10, runs everything else fabulously, I was not expecting something like micro-stuttering. It FEELS slightly off. Difficult to explain, but it's a real killer.

Those four, taken together, mean I'll try to return it (ordered it online, picked it up and paid via debit card). It's still in mint condition, wore it about half an hour. Keeping my fingers crossed they'll take it back...

Next VR set will have to have a display port. Not going to fall into the airlink/link trap again. I'm happy for whoever it works for, of course. :)
 
Last edited:
I am going to return my Quest 3. Hope Saturn (huge chain of stores in Germany) takes it back.
1. Link is . . . unreliable is a nice way of putting it. My USB-C port is not recognised at all (works like a charm with the Rift S!), the other ports . . . "wonky" would be a good way of describing it. SOMETIMES it works, mostly not. I haven't got more than half an hour out of it -- most of the time was spent troubleshooting. Note that NONE of my many USB devices have ANY problems with ANY of my USB ports.
2. When looking to open the panels (navigation, comms etc.), I have to lower my head (unnaturally so) to get to open them and STAY open. Never had that problem with the Rift S. I tried resetting HMD -- no joy. SERIOUSLY annoying. I've had several serious spinal disk incidents, keeping my head bent forward, even for a short amount of time, becomes painful in no time at all. With the Rift S, that was never an issue.
3. Too dark. I tried upping gamma, but that only results in it looking washed out.
4. (The REAL killer): No matter the settings, it just isn't as smooth as with the Rift S. Given that I have a 5800X3D and an RTX 4090, I was not expecting something like micro-stuttering. It FEELS slightly off. Difficult to explain, but it's a real killer.

Those four, taken together, mean I'll try to return it (ordered it online, picked it up and paid via debit card). It's still in mint condition, wore it about half an hour. Keeping my fingers crossed they'll take it back...

Next VR set will have to have a display port. Not going to fall into the airlink/link trap again. I'm happy for whoever it works for, of course. :)
I can’t comment on points 1 & 2 (I’ve had no issues there) but for the other points:

3. Did you adjust the headset brightness? I’d also check the Accessibility options to make sure the Contrast setting isn’t altered.
4. Have you altered the Link settings? The default is 72Hz so you should at least set that to 80Hz like the Rift S.
 
I can’t comment on points 1 & 2 (I’ve had no issues there) but for the other points:

3. Did you adjust the headset brightness? I’d also check the Accessibility options to make sure the Contrast setting isn’t altered.
4. Have you altered the Link settings? The default is 72Hz so you should at least set that to 80Hz like the Rift S.
Thank you for replying so swiftly!

I tried changing to 80 and 90Hz, but it still felt slightly off. Headset brightness I had not checked -- no idea how that's done. (I'm not TOTALLY incompetent as far as computers are concerned, but HMD is something different, and Meta's FAQ was not much help... plus I didn't have much time, family stuff to take care of). I also tried all USB ports. The cable SHOULD be fine (a 10-foot, 20 Euro cable), but connection speed is about 2GBit/s, which seems on the low side of things, given that most promise up to 5, and some, even 10...
EVEN IF I managed to rectify points 1, 3, and 4, point two sticks in my craw, sideways. The Rift S, while slightly heavier, is excellent, as I can really look at an object and focus on it, I still don't have to look slightly down and then glance upwards like I was looking over the rim of my glasses at a student who's trying to hoodwink me . . . ;) . Strange to note that you don't have that issue. Maybe I got a model that's just . . . different. :D
 
Thank you for replying so swiftly!

I tried changing to 80 and 90Hz, but it still felt slightly off. Headset brightness I had not checked -- no idea how that's done. (I'm not TOTALLY incompetent as far as computers are concerned, but HMD is something different, and Meta's FAQ was not much help... plus I didn't have much time, family stuff to take care of). I also tried all USB ports. The cable SHOULD be fine (a 10-foot, 20 Euro cable), but connection speed is about 2GBit/s, which seems on the low side of things, given that most promise up to 5, and some, even 10...
EVEN IF I managed to rectify points 1, 3, and 4, point two sticks in my craw, sideways. The Rift S, while slightly heavier, is excellent, as I can really look at an object and focus on it, I still don't have to look slightly down and then glance upwards like I was looking over the rim of my glasses at a student who's trying to hoodwink me . . . ;) . Strange to note that you don't have that issue. Maybe I got a model that's just . . . different. :D
Headset brightness is one the Q3 quick settings menu (the time/battery/signal icons) in the upper right. Connection speed is limited in the Oculus desktop software - originally my bitrate was defaulted at “variable” with a maximum of 100mbs, so I changed that to “fixed” at 200mbs. It is possible to go higher using the Oculus Tray Tool - I’ve had Link at 500mbs - but I leave it at 200mbs because I often use AirLink and my router doesn’t like 500mbs for that 😅

I’m not sure why your view is like it is - the only thing I can think of is like when I have to sit the headset on my face correctly because it will happily sit just a touch too low, I can tell this because the centre of the view is not quite in focus. The Rift S never had this problem thanks to the halo strap.
 
Headset brightness is one the Q3 quick settings menu (the time/battery/signal icons) in the upper right. Connection speed is limited in the Oculus desktop software - originally my bitrate was defaulted at “variable” with a maximum of 100mbs, so I changed that to “fixed” at 200mbs. It is possible to go higher using the Oculus Tray Tool - I’ve had Link at 500mbs - but I leave it at 200mbs because I often use AirLink and my router doesn’t like 500mbs for that 😅

I’m not sure why your view is like it is - the only thing I can think of is like when I have to sit the headset on my face correctly because it will happily sit just a touch too low, I can tell this because the centre of the view is not quite in focus. The Rift S never had this problem thanks to the halo strap.
NOW I feel stupid. I had not thought of checking whether the headset is actually really adjusted on my (big) head. I was being careful, since I wear glasses, and I did not want to scratch the lenses.
Should they tell me to take a hike, I shall try another cable, adjust brightness, adjust link speed, and DEFINITELY make sure it sits correctly on my oversized noggin'.
THANK YOU. :D
 
Hi DDM

If you still have the headset, have you tried running the debug tool? It is found...
Installation drive:\Oculus\Support\oculus-diagnostics

You should see at the bottom a mini menu for HUD. Select the performance one and you should see a couple of graphs in VR. The one on the left is the Hz and the one on the right is the performance headroom. Your Hz will be either 90 or 45, depending on what you have the HMD set to inside Oculus Home. Ideally you want your Hz to be 90. And staying there. What does your graph show?

Don't forget, no PC is currently able to run elite at Ultra at max resolution settings and 90Hz on the Q3 atm
 
Im also looking around for a new headset. Sporting the Rift S and is really happy with clarity and performance on my 5800X3D / 4070ti system.

The quest looks like a good deal, but like others here, I only mostly use VR for seated stuff. I am actively considering the Varjo Aero or maybe the Pimax Crystal. The last one is a Pimax product, and it would seem its like a hit/miss thing for you to get a working or non-working unit. For that kind of money thats just unacceptable.

Wired VR is in a ty place right now, as the "value offers" spends ressources on stuff that I dont need.

Anyway to the question: Is there any truth to the claim that Q3 requires a more powerful computer than say they Varjo due to all the hoops and loops needed with compression etc?
 
Last edited:
Back
Top Bottom