Just watched a video from VR Flight Sim Guy (thanks and kudos to him) saying trying the latest Oculus V27 beta with no other tools like Debug or Tray tool and the Link cable and it just works.
So I have 1660 Super GPU and Ryzen 7 2700, both stock with 16Gb RAM and all I can say is give it a try. For me its the best visuals I have had, just set to 72 Hz recommended and the resolution to 1.0 in Oculus V27 device settings.
Give it a go and hopefully it will be as good for you
Where do you find the Oculus device settings ? Is that with using the Oculus Tray tool ?
I have V27 Oculus Beta, and definitely VR looks great within the cockpit and in the foreground, ( even though i have an older Rift S), but things out by the horizon are somewhat blurry and jagged, so for example it is hard to eyeball an airport thats several miles out, because it blends into the scenery. (resolution is poor)
Do you have any comparison with the Oculs Ques 2 vs the rift S ? is the Quest 2 sharper specially at the horizon, and do you get a wider field of view ?
The main thing is there is no need now to use anything but the oculus app on the pc so no tray or debug tool now required.
Previously before V27 without such additional apps the VR was very jerky.
Sorry I have only used the Quest 2 so cannot say about comparisons, but just using the V27 only has given the best sharpeners into distance
I agree, Something has changed. I can now have ground traffic ,air traffic and medium clouds with no stuttering even over a large city. The only issue now is the brightness on city buildings and in the distance? It’s as if there is constant bush fires.
Did you modify any settings in the NVIDIA control panel… like VSync to fast or pre-rendered frames to 1 or 2?
Sync fast and prerender frames 1 in nvidia control panel
A couple things:
(1) This beta has a bug that forces your headset to run at 72Hz no matter what setting you choose. This is part of the reason for people seeing “performance improvements,” because it frees up performance headroom.
(2) This beta fixed the frame sync problem that previously required us to set V-Sync to “fast” in the Nvidia control panel. Now even without that setting, the frame rate syncs correctly and ASW is more stable, as well as allowing the sim to reach the full refresh rate of the headset which wasn’t possible before (unless V-Sync was set to “fast”).
Beyond that, I’m not seeing anything any different than prior versions.
What ASW setting do you choose in the OTT?
Yep, this is the exact reason for “performance increasing” or so in this case the perception of better performance due to headsets being stuck at 72hz. Those that ran on 90hz before v27 will see big improvements.
Which was all possible anyway on previous versions simply by selecting 72hz.
You can choose whatever you want. The important thing is to know how much performance headroom you have, and your achievable frame rate without ASW, so that you know which ASW setting will work without choking.
The way to do this is to turn on the Performance Overlay HUD, which will show you the realtime framerate as well as performance headroom. Launch the sim, activate VR, and load up to a place that puts the highest demand you expect to encounter (e.g. plane, weather, city density…) Then, with VR still active, click the ASW mode drop-down in OTT and disable ASW completely. Now take a look in your headset and see what framerate you’re getting. This tells you which ASW setting you can use and get stable performance. For example, if you have the Quest’s refresh rate set to 72Hz, and you want to use the half-framerate ASW lock (it’ll be called Force 45Hz with ASW which is a misnomer, it’s really half the refresh of your headset), then you need to have a base framerate greater than 0.5*72Hz = 36fps. Thus you need to make sure your framerate stays consistently above 36fps at all times, to be able to use the Force 45Hz ASW option.
I realize that sounds confusing but it’s really pretty simple. You need to make sure you can attain a framerate consistently higher than the fps you want to lock ASW at, or it won’t be able to do its job without dithering to an even lower rate. You do this by turning off ASW completely, seeing what framerate you’re getting, and then lock ASW to a framerate less than that.
By using the performance overlay HUD I mentioned, you can see on the framerate graph what the ASW lock options are doing, too. When it’s enabled, you should see a very flat, stable line at the value you chose once ASW is enabled. If it’s still jumping all over even after things have finished loading, then you need to dial back the performance demands somewhere else, or lock ASW to an even lower value.
I have a question about quest 2 frame rates that someone may or may not be able to answer…
I’ve never been able to get my FPS above half the quest’s hz setting. So at the moment with V27, I hit a hard wall at 36fps. That’s fine and smooth enough for me, but I always have ASW turned off in OTT and I don’t get why it can vary by single digits below 36hz, but I can’t get anything over that… I’d just think if my pc is capable of running at 38 or 40 FPS at 30,000ft, why can I not benefit from the extra few frames?
Why is that limit in place? If I had a super computer, would the next step up literally be 72hz? (I know that’s not possible even with a 3090 but hypothetically)
Or is this actually because OTT is failing to turn off ASW and so I’m getting a lock at half frame rate and just not noticing any ASW jitters or tearing…?
Not a deal breaker at all but it does bug me not knowing why
I did not use the OTT, just set 72 refresh in main Oculus app and let the new V27 Beta do therest automatically and it seems to give me better results than I could manually tweaking. With a lower end GPU 1660Super there was not much spare bandwidth and try as I might with tweaking I could only go so far. Now with letting the Occulus software decide I get better than I ever did manually. Of course there is still the option to tweak. Also the flightsim guy has a top end pc latest intel cpu and a 3090 and he found the same that just let it do its thing and it gives better results than previously. So I would suggest try it to see if it just works for you (pretty quick to try) and maybe it works for you as well.
If you want to be sure about whether or not ASW is actually being disabled, turn on the ASW Status overlay HUD. There is a drop-down list of overlays you can choose from on the same tab of the Tray Tool which give a wealth of useful information. On the ASW one, it’ll just show text that says something like “ASW Status: Available” or “ASW Status: Not available.” If ASW really is disabled, it’ll say “not available.” If it’s active and generating frames, it’ll tell you that too.
As for your framerate being capped at 36, it’s possible ASW isn’t actually off (Do what I said above to be sure). But it’s also possible that’s where your performance headroom is forcing the frame sync to render. One thing that many people seem to not realize about VR is that frame sync is critical. You can’t just run intermediate, dithering frame rates without creating judder. This is because of the stereoscopic rendering for each eye, and how we perceive things being out of sync between them. What would be just an ugly frame tear on a 2D screen is a jarring stutter in VR. Because of this, “getting a few extra frames” in VR isn’t of any use. There are certain thresholds you have to hit, and if you don’t, the frame sync of the VR runtime will force the fps to an even multiple of the native refresh rate (assuming it’s actually working correctly… Link has been pretty darn buggy in this regard ever since its conception. The native pcvr headsets-Rift and Rift S-have much smoother performance with ASW, and that’s sad, because ASW is by far the best motion smoothing algorithm of any VR system. But they haven’t done a very good job of robustly porting it over to Link.)
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.