My experience with Oculus Quest 2

User Support Hub Virtual Reality (VR)
1

First to comment that my experience with VR has been zero, I have known it since it began, but it always seemed to me that it was in its infancy and had a lot of development left. Last year, taking advantage of black friday, I decided to experience this technology and bought what I was told and the quality-price was one of the best. Today I consider the Coulus Quest 2 a very good product, but to get to say this, I’ve been looking for the sweet spot with FS2020 since I bought them, I don’t know how many tutorial videos I’ve seen, each one explaining their settings that I have no doubt works for them, but for me it was exasperating. Logically little by little you are understanding the reason for the adjustments and without wanting it you are getting closer to the optimal adjustment and on that I wanted to make some small reflections.
We have to understand that our equipment is not the same or similar to the one in the tutorial videos, so you cannot take these adjustments literally.
My team is as follows:
Asus Rog Maximus Hero XI
Intel i9-9900K at 4.8Ghz
G Skill 32 Gb at 3600 Mhz
Asus RTX3070 8Gb. O.C.
Nvme.2 Samsung 500 Gb (I have more Nvme and SSD disks but Samsung has the S.O. (Windows 10) and FS2020.
And from this you have to build your setup.
After many wrong setups I decided to start building the house from the foundations.

  1. The objective is to ensure that what you see has fluidity, without visual distortions and with the greatest possible definition. Getting all this in one package is the task.
  2. When I see colleagues who do not have especially powerful equipment and go to 90 Hz and within FS2020 the panel refresh rate is medium or High, I think it is an error. Going to 90 Hz does not influence anything to improve the search for targets, if you play car simulators or other types of games if you should look for those settings. The refreshment of the panels consume essential resources that we will need to win the objective. That said, I’ve gone to 72Hz and the refresh rate to Low on the cockpit panels.
  3. I have looked for an airport that contains a bit of everything, in my case LPMA (Madeira) and to test settings, starting from the head and doing a take-off and see the fluidity of the takeoff and the solidity of the image inside the cabin.
    I only use the Ouculus Debug Tool, I do not recommend the OTT more than anything because of its complexity, to say that it is an excellent application, which I do not rule out now that I have a little more experience using it, at the moment only with ODT.
  4. The first thing I did was adjust the Render of FS2020, I had to go down to the value 60 so that everything went well, in Oculus it went to 72 Hz and 1.3 (5408x2736) which seemed idyllic, but at 60 there is no definition, with which I raised the render and the Oculus to 80 at 72Hz and 1.2 (4864x2448) and this was the sweet spot for me, I also took the opportunity to upload some settings within FS2020.
    In ODT it looks like this: Pixels Per Display: 1.9-FOV 0.7 and 0.7
    Adaptive GPU: Default the Asyncronous: Disable, Distortion Curvature: Low-Encode resolution: 3856 this value is trial and error, the higher you can take the value the better, maximum 4000 until you get a horizontal line in the lower third of the lenses - y Link Sharpening: On.
    I do not want or try to copy these settings as if it were your solution, what I intend is to give you a methodology on how to get to these settings.
    In short, first look in Oculus for your configuration, 72,80,90 or 120 depending on the equipment you think you have, maximum rendering resolution and from there touch FS2020 and adjust your render.
    Thanks
1 Like
2

This is what I have success with - I have to use ASW for fluid helicopter (H135 freeware) tailrotor yaw rotation and I recently upgraded (???) to Windows 11 which has a known stutter problem that can only be solved by setting the ODT to show the console window (magic!!).

Oculus PC App - 72Hz @ 1.3x (4704x2384)
ODT+OTT - PPD=1.3, FOV+0.8;0.8 , ASW=30Hz (one-third of 72 = 24HZ/FPS pretty much locked)
NIS Scaler (input res = 2304x2336, output res to MSFS = 1612x1635) 70%, 40%
MSFS - RS=100%, TAA, mostly medium, TOD=150,OLD=115, 8x,2x2
NOTE: I read somewhere to let the ODT console window show?? YES!!!

3

Today I configured everything to execute the FS2020 render at 105, which is an excellent value for me, at the cost of that I had to lower the SuperSampling to 1.0 (4224x2128), I think that a configuration of this style is better than having what to use a render in pe game 80 and in Oculus use 72Hz-1.3 (5408x2736), since the render of the game is the one that gives the quality to the processing even if it is represented with fewer pixels and to compensate for that I use the Pixel by Display since there it does improve, in the other I would not give you anything because it is at its maximum resolution. Obviously the ideal would be to use a render of 100-105 with 1.3 of SS, but my team does not execute it smoothly.

4

What is OTT?

Did you use a cable or a wifi connection?

Thanks.

5

OTT = Oculus Tray Tool (google it). Some folks don’t want to use it becuse most of it’s settings are available with ODT but if you like ASW for smoothness of the view looking sideways, then you need to use it because ODT doesn’t provide 30Hz which gives me the one-third of 72Hz = 24FPS.

7

Good idea with the 24fps, using that on my 2700X + 1080Ti (511.23) + Quest 2 (v37) and it is quite smooth.

I’m using Adaptive ASW, not sure if there’s any difference with 30Hz.
Also HAGS and Game-Mode ON.

8

Yep, same here.

9

You can also try Activities>Discovery flights>Naples.
Loads fast and always the same starting point, clouds, water, city scenery and an airfield to land.

10

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.