*Link Sharpening* also improves clarity by sharpening blurriness at basically no cost. I like the *Quality* option. *Distortion Curvature* on *LOW* also helps by spreading the "pixel clarity" from the center more uniformly across your vision at almost no performance impact. Other than that, you were spot on with the settings and what they do.
Only one thing to add to this video to make it perfect, if you have enough free performance you can use pixels per display pixel override option, it acts as a way of supersampling overriding the option on the oculus app. For example, i saw you are running x1.7 on your oculus app, well you can add a factor (like 1.05, 1.1, 1.15, 1.20) that way you are increasing your rendering resolution even more (by a 5% , 10%, 15%, 20%) wich translates on a crisppier image on your quest. If you havent tried it , go and do it, im currently running 1.15 after the rain update (i was running 1.30) and it increases the image quality by A LOT
That is fascinating. I will give that a try. Thank you for the tip, I was wondering what that option did, but finding definitive information can be tricky. Thank you for clearing that up for me. What graphics card are you using (and cpu) to run at 1.15?
Question: After changing "Pixels Per Display Pixel Override" do I need to restart Quest 3 or App, or disable and then enable Oculus Link? Or detach then attach cable? Other tiny thing I am missing? I've tried 1.15 then 1.30 and don't notice any difference, and if it helps in Meta App I have 90Hz 1.1x ratio.
Hi @DaniumMR and @olderGamersPerspective, I have 2 questions for you guys, about this. 1. I do some changes at the APP for the FOV, but nothing happens on my quest 3, only with the OTT app. What am I doing wrong? I open the Debug Tool, I change the numbers, turn on the Quest 3 and nothing. 2. With the Pixel Per Display, should I leave at the APP 1x or keep 1.7x? What's the best way to maximise the visual with the right cost to my pc? I'm struggling to get it as perfect and stable as possible and I have a quite strong PC to be honest.
To update you both: The FOV will only work, at least on my side, if you change the numbers at the first line, not the hidden ones and after you change the numbers, you hit ENTER. With this, will you see the numbers below (individuals Horizontal and vertical) change. This way, I can turn on the VR and enter in the VR world. And found out, 0.8 and 0.75 works fine to me. Now, I'm curious to know how the Pixel Per Display should work.
Hi, Im experimenting with a device peripheral for the quest. I just wondered if you knew of any settings in any of these debug tools that would allow you to read or even stream the controller data whilst you are using any game?
I found this on the Meta forum: communityforums.atmeta.com/t5/General-Development/Retrieve-and-send-Controller-Inputs-from-to-an-Application/td-p/753646 Not sure if it is what you want, but it's the closest I could find.
Hi thanks alot for this easy to follow tutorial. As off lately my 3070 with a 5800x is not pulling all these iRacing updates, found that openXr with the toolkit adjustments allready made it run better. Will try adjusting these.
Hi, glad it's all helping. One of the frustrating things about VR is getting everything to optimal, or at least optimal enough, to fully enjoy the experience. For me it feels like time travelling back to the late 90's where we had to optimise a PC just to get it to run a very basic game (probably booting the game from DOS). But hey ho, it is what it is, and VR is without a doubt, a very cool experience.
You can (and perhaps should) experiment with settings per game. iRacing I found with my system could only tolerate a setting of 450 on encode bitrate, otherwise I got the occasional audio stutter, which also gave a graphical glitch, but that's just iRacing, so I suspect that something like AMS2 and AC1 (when played off line) could go higher. It's a case of try it and see what your system can cope with.
Im using 1.0 and 0.6 in my Quest 3 fov settings when doing iracing. The fov is good enough in the q3 for the black bars on the sides get visible quite early. Top and bottom black bars are no issue though, and as someone on the internet suggested, you can see them as part of your imaginary helmet if so :)
Yes, I do like the idea of the imaginary helmet :) At the moment, I seem to be okay with these settings at the default, but with Rain in coming on iRacing, maybe I will need that feature soon :)
www.amazon.de/-/en/gp/product/B09QMGS6CH I bought this one in March 2023, not sure if the one they are selling is the same, but mine is USB-C to USB-C, and plugs directly into a USB-C port on my mainboard.
No silly questions on this channel. Air link is dependent on the wifi router and connection to your PC. So be aware that setting the Encode Bit rate too high will cause your display to freak out. Start with zero and increase by 50, try it out and see if it works fine, if so, increase by 50 again. If it does freak out at some point, disconnect the headset from the PC in the normal way (end a link session) and then decrease it by 50. It's a real trial and error way of figuring out which setting will work best for your PC. FOV tangent Multiplier will help if you have poor performance, so you can also try that, but it won't do anything if your Encode Bit rate is too high.
It certainly works with iRacing, whether or not it can help with these issues will depend on a lot of other factors, like headset and computer and so on. Why not jump over to the older gamer discord channel - discord.gg/pHJpvNff Lots of friendly people there to help you out. Post this question in the VR help section.
I am running a somewhat aging PC. After getting a quest 3 for Christmas this year, I figured why not try out running some games via pcvr just to try it out. When I am altering the FOV settings, it doesn’t seem to be doing anything. Everything else is allowing me to tweak the image quality and performance, but FOV doesn’t appear to be changing. Is it possible there are some games that just override or ignore this setting? Am I doing something wrong?
The FOV settings in iracing do you mean? These I generally don't touch when using VR as they are supposed to be already set by the headset you are using.
HI; Thank you for this complete guide for using the Oculus Debug Tool. I have a PC with I5-13500 2.5 Ghz, 32 GB RAM, RTX 4060ti 8 Gb. Do you have any suggestions on how to set up the tool? Do you also know these two tools for Meat quest 3 "Oculus Tray Tool" and OpenXR Toolkit Companion app? Thanks for the support.
Hi, I am glad you found this video helpful. I don't use the Oculus tray tool anymore as it stopped working on my windows 11 system, although others have reported it works fine on theirs. It is a cool app, but it appears to have stopped being developed. Details on the OPenXR toolkit can be found in this video - ua-cam.com/video/6dXvAhSyzrY/v-deo.htmlsi=zFFtDsTSDvuQiA1d
Great channel, sir! So, what is the consensus on the ideal headroom? Somewhere above 50% seems smooth to me. Obviously, 100% is ideal, but the graphics would be crap for me.
Hi, thank you for the feedback. The consensus is varied. When I uploaded my first 4070Super video, I tried to keep the headroom at 50%, but the consensus then was I left too much Performance headroom on the table, which is fair comment. Sooooo, I did another 4070Super video where I tried to be a bit more reckless with the headroom, and after doing some optimisation, I was able to turn up most of the settings to high, and get, quite frankly, a totally new experience in iRacing. It really did feel like I was using a brand new sim. In this case, the headroom is around 25 to 35%, which when I add rain to that (see my latest video on Rain in VR - ua-cam.com/video/uL84F6mtZVE/v-deo.htmlsi=S5UTd-AZH7WihtQM ) I saw a drop across the board, although not a massive drop, towards 11% when racing in Very Heavy rain. So I think, if you can race in the dry, and get about 25% to 30%, and you have the settings where you like them, then that's about what you should be racing at. I will admit, being an older gamer, my first video was far to cautious, and with this new devil may care, older gamer, I am having a lot more graphical fun. I just need to work out now how to be faster :)
FOV tangent 0.9/0.87 is literally free performance for my 68 IPD with facial interface at the second farthest position. I lose zero visibility, it's literally the same as default, no black stuff at all. To find the best settings, I just started with them pretty low like 0.6, to make the black bars obvious, and then increased by 0.1 steps until I couldn't see them at all anymore, then I backed off again for fine tuning. In my case, the horizontal blackness was last seen between my eyes at the center, while vertical blackness died last at the bottom edge.
I will give these settings a try and see what they look like, Sounds ideal for anyone suffering from performance issues, in VR, in the rain for example. I suffer at the moment from a drop in frame rates when on the grid with more than 30 cars, so this will be something I will dial in later today and see if it helps. Thank you for the tip.
@@OlderGamersPerspective the best numbers may vary, depending on your IPD, distance to screen and your individual device, but using the same method as I did, you'll certainly find some setting which will give you max performance boost without any loss. The only thing I hate is having to input the numbers again every single session, I'd like to be able to save them so I could set and forget.
I can´t get rid of the HUD anymore even though its set to "none". There´s still a HUD saying "Recording (next line) FPSnext line (next line) HGPU bound...how can I turn that off again?
@@OlderGamersPerspective thanks for the reply. But my Problem has been solved already. It was not the OTT (ODT) Hud, it was the OpenXR Hud which I accidently turned on and mixed up with the OTT HUD.
Absolutely brilliant video. Yip Meta, put it in an obscure location, make it scary looking etc etc. Do you have any videos like this on the Quest 2 in general, eg if using it with a PC to play Steam PC games what are the best actual options for the different methods, Cable, Air link, Steam link, Virtual Desktop and which apps/programs need to be running for each case, eg if using a cable do I need the Oculus (Meta) app running on PC or can I just use SteamVR app? Should you turn off your monitor? Also what is the actual order of starting things, boot up Quest 2, go into headset, start what???
Thank you for the feedback. I use cable link and the meta app to connect with steam games, and the Oculus option in the launch area. Take a look here - ua-cam.com/video/LVZgrGMls3s/v-deo.htmlsi=yHLn_g3UkyldVNnj I talk there about the options you have to connect to your PC, including the steam app in the headset. And also the order of things being turned on, which is PC, boot up meta app, connect headset, turn it on, and then connect to PC. That's the way I do it, but small variations in this order shouldn't matter too much. Leave the monitor on when you are using VR, but you can reduce the size of the window where iRacing is displayed on the monitor to help save resources. As I said, most of this information is put a bit more clearly in that video, which I released yesterday.
@@OlderGamersPerspective Thanks for the reply, I'll check out your other video. BTW once you do the settings in the ODT do you need to run it each time you play PCVR games alongside the Meta app and Steam/SteamVr or are these settings saved and remembered. BTW have you any experience/knowledge of the so called Oculus killer that disables the oculus dash (whatever that is(!) when using steamvr? Cheers.
@@V081WLBlue it does depend on how you connect to steam. If you check out my other video on a guide to connecting to vr for SIM racers, that should answer a few of your questions. The oculus dash killer I haven't used, but it sounds interesting, so I'll take a look. Thank you for the tip
Hey, on the topic of "ASW is used even when its disabled in the ODT"... I dont think this is what is occurring. I believe that without ASW when you fall below your performance target the system can half the frame rate as a way to easily maintain good vsync with the headset displays. Im not sure of this, but I think its true (fps halved but ASW does not kick in).
Yes, I think you are right. But I have a sneaky suspicion that the device used to implement this halving of frames is related to, or at least on speaking terms, with ASW. If you see what I mean. Any idea where this setting is? And how it could be turned off? Or is it just the way it is?
I just got it worked out, i had SSW enabled at Virtual Desktop. I copy pasted Your settings from here and it is working fine now. Need to tweak few settings now directly in openXR and it should go fine. Thanks!! @@OlderGamersPerspective
Hello, I have found this video very helpful but I have one very big problem I've only tried Encoded bItrate 350 and 200 and it is very laggy and the movement is super delayed. Do I have to set the bitrate higher or lower?
*Link Sharpening* also improves clarity by sharpening blurriness at basically no cost. I like the *Quality* option.
*Distortion Curvature* on *LOW* also helps by spreading the "pixel clarity" from the center more uniformly across your vision at almost no performance impact.
Other than that, you were spot on with the settings and what they do.
Thank you for the feedback, I will try out these settings to see if I can squeeze some extra clarity from the quest 3 :)
Only one thing to add to this video to make it perfect, if you have enough free performance you can use pixels per display pixel override option, it acts as a way of supersampling overriding the option on the oculus app. For example, i saw you are running x1.7 on your oculus app, well you can add a factor (like 1.05, 1.1, 1.15, 1.20) that way you are increasing your rendering resolution even more (by a 5% , 10%, 15%, 20%) wich translates on a crisppier image on your quest. If you havent tried it , go and do it, im currently running 1.15 after the rain update (i was running 1.30) and it increases the image quality by A LOT
That is fascinating. I will give that a try. Thank you for the tip, I was wondering what that option did, but finding definitive information can be tricky. Thank you for clearing that up for me.
What graphics card are you using (and cpu) to run at 1.15?
Question: After changing "Pixels Per Display Pixel Override" do I need to restart Quest 3 or App, or disable and then enable Oculus Link? Or detach then attach cable? Other tiny thing I am missing?
I've tried 1.15 then 1.30 and don't notice any difference, and if it helps in Meta App I have 90Hz 1.1x ratio.
when i restart the pixels per display pixel override just resets to 0 how do i fix this?
Hi @DaniumMR and @olderGamersPerspective, I have 2 questions for you guys, about this.
1. I do some changes at the APP for the FOV, but nothing happens on my quest 3, only with the OTT app. What am I doing wrong? I open the Debug Tool, I change the numbers, turn on the Quest 3 and nothing.
2. With the Pixel Per Display, should I leave at the APP 1x or keep 1.7x? What's the best way to maximise the visual with the right cost to my pc? I'm struggling to get it as perfect and stable as possible and I have a quite strong PC to be honest.
To update you both:
The FOV will only work, at least on my side, if you change the numbers at the first line, not the hidden ones and after you change the numbers, you hit ENTER.
With this, will you see the numbers below (individuals Horizontal and vertical) change. This way, I can turn on the VR and enter in the VR world.
And found out, 0.8 and 0.75 works fine to me.
Now, I'm curious to know how the Pixel Per Display should work.
Hi, Im experimenting with a device peripheral for the quest. I just wondered if you knew of any settings in any of these debug tools that would allow you to read or even stream the controller data whilst you are using any game?
I found this on the Meta forum:
communityforums.atmeta.com/t5/General-Development/Retrieve-and-send-Controller-Inputs-from-to-an-Application/td-p/753646
Not sure if it is what you want, but it's the closest I could find.
Hi thanks alot for this easy to follow tutorial. As off lately my 3070 with a 5800x is not pulling all these iRacing updates, found that openXr with the toolkit adjustments allready made it run better. Will try adjusting these.
Hi, glad it's all helping. One of the frustrating things about VR is getting everything to optimal, or at least optimal enough, to fully enjoy the experience.
For me it feels like time travelling back to the late 90's where we had to optimise a PC just to get it to run a very basic game (probably booting the game from DOS).
But hey ho, it is what it is, and VR is without a doubt, a very cool experience.
Thanks for the great guide! Do change settings per game, or does a good setting for one game also work for others?
You can (and perhaps should) experiment with settings per game. iRacing I found with my system could only tolerate a setting of 450 on encode bitrate, otherwise I got the occasional audio stutter, which also gave a graphical glitch, but that's just iRacing, so I suspect that something like AMS2 and AC1 (when played off line) could go higher.
It's a case of try it and see what your system can cope with.
Im using 1.0 and 0.6 in my Quest 3 fov settings when doing iracing. The fov is good enough in the q3 for the black bars on the sides get visible quite early. Top and bottom black bars are no issue though, and as someone on the internet suggested, you can see them as part of your imaginary helmet if so :)
Yes, I do like the idea of the imaginary helmet :)
At the moment, I seem to be okay with these settings at the default, but with Rain in coming on iRacing, maybe I will need that feature soon :)
Which USB link cable are you using?
www.amazon.de/-/en/gp/product/B09QMGS6CH
I bought this one in March 2023, not sure if the one they are selling is the same, but mine is USB-C to USB-C, and plugs directly into a USB-C port on my mainboard.
Sorey if this is a silly question as new to pcvr, do these settings also need changing if just using air link?
No silly questions on this channel.
Air link is dependent on the wifi router and connection to your PC. So be aware that setting the Encode Bit rate too high will cause your display to freak out.
Start with zero and increase by 50, try it out and see if it works fine, if so, increase by 50 again. If it does freak out at some point, disconnect the headset from the PC in the normal way (end a link session) and then decrease it by 50.
It's a real trial and error way of figuring out which setting will work best for your PC.
FOV tangent Multiplier will help if you have poor performance, so you can also try that, but it won't do anything if your Encode Bit rate is too high.
@@OlderGamersPerspective Thanks for your reply
Hi super sampling works with debug tool for IRACING ? to upgrade the quality and remove blur etc??
It certainly works with iRacing, whether or not it can help with these issues will depend on a lot of other factors, like headset and computer and so on.
Why not jump over to the older gamer discord channel - discord.gg/pHJpvNff
Lots of friendly people there to help you out. Post this question in the VR help section.
I am running a somewhat aging PC. After getting a quest 3 for Christmas this year, I figured why not try out running some games via pcvr just to try it out.
When I am altering the FOV settings, it doesn’t seem to be doing anything. Everything else is allowing me to tweak the image quality and performance, but FOV doesn’t appear to be changing. Is it possible there are some games that just override or ignore this setting? Am I doing something wrong?
The FOV settings in iracing do you mean? These I generally don't touch when using VR as they are supposed to be already set by the headset you are using.
HI;
Thank you for this complete guide for using the Oculus Debug Tool.
I have a PC with I5-13500 2.5 Ghz, 32 GB RAM, RTX 4060ti 8 Gb. Do you have any suggestions on how to set up the tool?
Do you also know these two tools for Meat quest 3 "Oculus Tray Tool" and OpenXR Toolkit Companion app?
Thanks for the support.
Hi, I am glad you found this video helpful.
I don't use the Oculus tray tool anymore as it stopped working on my windows 11 system, although others have reported it works fine on theirs. It is a cool app, but it appears to have stopped being developed.
Details on the OPenXR toolkit can be found in this video - ua-cam.com/video/6dXvAhSyzrY/v-deo.htmlsi=zFFtDsTSDvuQiA1d
Great channel, sir! So, what is the consensus on the ideal headroom? Somewhere above 50% seems smooth to me. Obviously, 100% is ideal, but the graphics would be crap for me.
Hi, thank you for the feedback.
The consensus is varied. When I uploaded my first 4070Super video, I tried to keep the headroom at 50%, but the consensus then was I left too much Performance headroom on the table, which is fair comment.
Sooooo, I did another 4070Super video where I tried to be a bit more reckless with the headroom, and after doing some optimisation, I was able to turn up most of the settings to high, and get, quite frankly, a totally new experience in iRacing.
It really did feel like I was using a brand new sim.
In this case, the headroom is around 25 to 35%, which when I add rain to that (see my latest video on Rain in VR - ua-cam.com/video/uL84F6mtZVE/v-deo.htmlsi=S5UTd-AZH7WihtQM ) I saw a drop across the board, although not a massive drop, towards 11% when racing in Very Heavy rain.
So I think, if you can race in the dry, and get about 25% to 30%, and you have the settings where you like them, then that's about what you should be racing at. I will admit, being an older gamer, my first video was far to cautious, and with this new devil may care, older gamer, I am having a lot more graphical fun.
I just need to work out now how to be faster :)
Great vid with great points - don't suppose you've found a way to move or pin the performance window off to the side?
Sadly not, and yes, it is a pain. If I find a way, I will make a video about it.
FOV tangent 0.9/0.87 is literally free performance for my 68 IPD with facial interface at the second farthest position. I lose zero visibility, it's literally the same as default, no black stuff at all. To find the best settings, I just started with them pretty low like 0.6, to make the black bars obvious, and then increased by 0.1 steps until I couldn't see them at all anymore, then I backed off again for fine tuning. In my case, the horizontal blackness was last seen between my eyes at the center, while vertical blackness died last at the bottom edge.
I will give these settings a try and see what they look like, Sounds ideal for anyone suffering from performance issues, in VR, in the rain for example. I suffer at the moment from a drop in frame rates when on the grid with more than 30 cars, so this will be something I will dial in later today and see if it helps.
Thank you for the tip.
@@OlderGamersPerspective the best numbers may vary, depending on your IPD, distance to screen and your individual device, but using the same method as I did, you'll certainly find some setting which will give you max performance boost without any loss. The only thing I hate is having to input the numbers again every single session, I'd like to be able to save them so I could set and forget.
I can´t get rid of the HUD anymore even though its set to "none". There´s still a HUD saying "Recording (next line) FPSnext line (next line) HGPU bound...how can I turn that off again?
Open the oculus debug tool, look towards the bottom and you should see a section called visible hud, set this to none.
@@OlderGamersPerspective thanks for the reply. But my Problem has been solved already. It was not the OTT (ODT) Hud, it was the OpenXR Hud which I accidently turned on and mixed up with the OTT HUD.
@@MemphisBelle291 got it. Good that you got it sorted out and have a great time in SIM :)
Absolutely brilliant video. Yip Meta, put it in an obscure location, make it scary looking etc etc. Do you have any videos like this on the Quest 2 in general, eg if using it with a PC to play Steam PC games what are the best actual options for the different methods, Cable, Air link, Steam link, Virtual Desktop and which apps/programs need to be running for each case, eg if using a cable do I need the Oculus (Meta) app running on PC or can I just use SteamVR app? Should you turn off your monitor? Also what is the actual order of starting things, boot up Quest 2, go into headset, start what???
Thank you for the feedback.
I use cable link and the meta app to connect with steam games, and the Oculus option in the launch area. Take a look here - ua-cam.com/video/LVZgrGMls3s/v-deo.htmlsi=yHLn_g3UkyldVNnj
I talk there about the options you have to connect to your PC, including the steam app in the headset. And also the order of things being turned on, which is PC, boot up meta app, connect headset, turn it on, and then connect to PC. That's the way I do it, but small variations in this order shouldn't matter too much.
Leave the monitor on when you are using VR, but you can reduce the size of the window where iRacing is displayed on the monitor to help save resources.
As I said, most of this information is put a bit more clearly in that video, which I released yesterday.
@@OlderGamersPerspective Thanks for the reply, I'll check out your other video. BTW once you do the settings in the ODT do you need to run it each time you play PCVR games alongside the Meta app and Steam/SteamVr or are these settings saved and remembered. BTW have you any experience/knowledge of the so called Oculus killer that disables the oculus dash (whatever that is(!) when using steamvr? Cheers.
@@V081WLBlue it does depend on how you connect to steam. If you check out my other video on a guide to connecting to vr for SIM racers, that should answer a few of your questions. The oculus dash killer I haven't used, but it sounds interesting, so I'll take a look. Thank you for the tip
Great explanation and funny video! 😆
Thank you for the feedback and I am glad you found it useful and entertaining :)
Another ODT video? I am in!!!!
Cool :)
Hey, on the topic of "ASW is used even when its disabled in the ODT"... I dont think this is what is occurring.
I believe that without ASW when you fall below your performance target the system can half the frame rate as a way to easily maintain good vsync with the headset displays.
Im not sure of this, but I think its true (fps halved but ASW does not kick in).
Yes, I think you are right. But I have a sneaky suspicion that the device used to implement this halving of frames is related to, or at least on speaking terms, with ASW. If you see what I mean.
Any idea where this setting is? And how it could be turned off? Or is it just the way it is?
I am having that issue. When in pit and after just leaving the pit I got 90fps. After few turns the framerate drops to 45. ASW is disabled in ODT.
What are your settings for the Oculus app?
I just got it worked out, i had SSW enabled at Virtual Desktop. I copy pasted Your settings from here and it is working fine now. Need to tweak few settings now directly in openXR and it should go fine. Thanks!! @@OlderGamersPerspective
@@jacekzmija3123 Coolness. I am glad it worked out for you. Enjoy :)
Hello, I have found this video very helpful but I have one very big problem
I've only tried Encoded bItrate 350 and 200 and it is very laggy and the movement is super delayed. Do I have to set the bitrate higher or lower?
Hi, are you connecting via cable or wifi?
@@OlderGamersPerspective im connected via wifi and im using airlink
and also I have an RTX 2060, amd ryzen 5 5600x 6-core processor, 15.92 RAM and my screen is 1920 x 1080 with 60hz
and is there any way to make things that are far away in the game not to look blurry and with crispy pixelated corners?
which head set are you using?
Great video again!
Cool, thank you for the feedback. I am happy you enjoyed the video.
Great effort can ben seen in your videos! HUGE RESPECT
Thank you, I really appreciate the feedback and I am glad you enjoyed the video. It was also fun to make :)