halufpv

Everything has been working great for me except for a small annoyance. I always have a thin black line to the right and bottom of my vision where the focus view blends with the background view, and only on the right/bottom sides. I have bloom and lens effects disabled. The line is visible on both eyes. I'm the Quest Pro. The only thing I've changed from default is the focus area, made it a bit smaller as it doesn't bother me... except the black line is now closer to the center Any ideas? Edit: I noticed I don't get this effect on the KA-50, but I do on the F-16

I finally had a long day to tinker with the quest pro. DLSS + QVF is absolute magic. The trick is that even in quality mode, DLSS is quite aggressive but you can actually get your own "in between the presets" setting by just changing the resolution in openXR toolkit. I went with a slight 10% upscale (though 5% a was already noticeably better) and results are indistinguishable from rendering at native resolution but with a significant performance boost, 10-25% more frames across the board. The other tweak I made was to change the QVF focus window size, which for some reason is overriden from the 0.35 default to 0.5 only for oculus users. I have to say 0.35 is "almost ok" but you do see the eye tracking more than default. 0.4 is almost as good as default, but you get another 5-10% boost. With these two combined I'm running the Quest pro at 1.5x 90hz with ASW and it stays at 45fps locked with a 3080Ti, hell I even saw 90fps when cruising on the F-16, it was surreal and magical. 45fps while playing close to the ground on Syria on the KA-50 was unimaginable just a month ago. All hail DLSS and eye tracking (and ofc @mbucchia), I'm over the moon!

With Quad Views and DLSS, is the upscaling happening to all 4 views?

That is just the nature of local dimming. The only way to get rid of that is an OLED panel which can turn on individual pixels instead of whole areas of the screen, or just disable local dimming if the effect is too disturbing, it'll basically have the same glare everywhere instead of just around bright elements as with the quest 2 or 3

You know sometimes reviewers talk crap without actually trying it, in this case the source of "the pro is great at night" is 1 youtube video so for all I know they were just "assuming" based on specs. For me it's not as bad as "london foggy night" though I definitely get you, it's like that only on the edges. I find adjusting the position of the headset changes it and being as close as possible to the lens almost gets rid of it, but it's not viable to wear the headset like that, because of the way it only grabs onto you on your forehead getting the lens really close involves tilting it downwards so the back part of it is not really where it's comfortable if you know what I mean, but you could wear it like that for a while if it's just a night mission here and then

As I said, refreshing, clear cache and refresh, log out and back in to no avail.

Same problem here. Trying to trial MI-24 before purchasing with the Halloween sale, it says I must enable 2FA even though I already have enabled it. Have tried logging in and out and even using a different browser. For the rest of you complaining about 2FA, I'm an IT professional and I'm cringing so hard. You really have no idea what you're talking about, it's insane to think DCS accounts can be worth hundreds of dollars and be password protected only with not even great password requirements. 2FA is exactly what you'd expect and it has 0 privacy implications. To the one guy suggesting SMS as a less invasive alternative, my god this is why IT people get depressed, I threw up inside. Edit: Temporary fix for those of you with the same bug, go to the product page, press F12 in chrome, go to console and paste this, press enter, then you can press the trial button. t.OTP_ACTIVATED = true This will not "hack" the 2FA system, as the next step is to actually provide a 2FA code which I image will fail if you haven't set it up, but it fixes the bug if you run into it

Quad View does come with a CAS sharpener as default for the center portion, which I'm very much onboard with as it saves us from sharpening the non-center area. DLAA is not a sharpener, but when using it DCS provides a slider right under the option to adjust sharpness, which I can only assume is yet another CAS layer?

@mbucchia Are there any consequences of using nvidia low latency mode and/or VR pre-rendered frames in the control panel with quad view? And should I disable DLAA in DCS? I'm already using link sharpening, it feels weird to use 3 separate sharpening filters stacked like this

Received quest pro today. First impressions weren't too good compared to quest 2 just tinkering with settings in standalone mode, the FOV is better but I didn't see much more difference at first. Then I loaded into the F16 and oh boy are things easier to read, the lens and increased pixel density are actually there. At this point I was feeling better about the purchase but not totally sold. Then I installed QVF and oh my god it's night and day. For context I'm on a 3080Ti and 12400F. I was able to play in multiplayer busy server for a couple hours at 90hz ASW locked at 45 with the render resolution maxed out at 1.5x and it was smooth as butter. I used to run 72hz and even then I'd get drops when low flying. I can't overstate the performance leap. I noticed that the area that is not high res is actually noticeable, though you have to kinda look for it and it's possibly because I run link sharpening + DLAA and it causes shimmer due to the pixelated area, but still the eye tracking is not as instant as I expected. I imagine future headsets will increase the polling rate and make it actually impossible to see it. The one thing I'm not too happy about is the local dimming. The halo around bright objects against a dark background is very noticeable. This is specially bad with the HMD (tried both F16 and F18), as it makes it look as though there's a moon behind a cloud anywhere you look at. With a starry night (I tried persion gulf case 3 recovery in instant action), the whole of the sky has a bloom to it, as any star causes the entire area around it to light up. What's even more disappointing is that turning local dimming off just makes everything light up completely, as if I had turned up the brightness on the display to "overdrive" and light is leaking all over the place. It almost feels as if local dimming is a technology designed to try to mask the shortcomings of the panel, e.g turn off some of the lights when there's nothing there because it leaks so much it's otherwise terrible. This is a non-issue during day though. I'm also not impressed with the comfort, but I'll buy the globular cluster comfort kit and hopefully it'll fix the issue. All in all I'm happy enough with the upgrade, the eye tracking by itself is worth the upgrade, and everything else (better lens, better pixel density is a bonus). If you're thinking of upgrading from literally anything without eye tracking, it's a no-brainer. Keep in mind because the Quest Pro flopped as a product and the Quest 3 has now been released and is better for literally everyone except DCS players (PCVR with QVF) the prices on eBay are crashing, I got mine for 500$!!

Also, I would change nothing else on the oculus debug tool than the bitrate and ASW if you don't like it, but that's it. The minecraft graphics when loading are normal. I'd try resetting all your DCS, nvidia panel, uninstall openxr everything and see if it's still that bad. With your graphics, it shouldn't be that bad on default everything, so I suspect you've messed something up at some point. Establish a baseline and change one thing at a time

Use 500mb link encoding. Anything above is prone to problems in my experience, especially the audio stutters. I can't tell a difference and I doubt you can.

I've read through this, thanks for the writeup I learnt a lot. So as for question 1, quad view is better in that it reduces not just shading cost but also rasterization cost, though it increases CPU load because the center part is effectively rendered twice. Why is this, can't we just not render the center in the low resolution views? And, this increase on CPU load, in the context of DCS, is it the load happening on the main thread? Does it have to be? If there were answers to the ASW/turbo question, I couldn't find them. Feel free to point me to more docs I saw a comment of yours in a repo issue saying you have multiple reports of ASW working with turbo, yet both the openxr toolkit overlay and the openxr toolkit docs explicitly say it will break ASW, hence my confusion

Hey Matthieu, thanks for all your work. I have a couple questions I understand the quad view technique is fundamentally different than what openxr toolkit implements, but can you elaborate on this more? What are the tradeoffs (e.g cpu usage), or is quad view simply better for the games that support it? I notice that quad view enables turbo mode by default? Does this mess up ASW like the OpenXR toolkit version? Why is it enabled by default? If you could elaborate on the tradeoffs here as well that would be great

It's because with Oculus, your computer isn't connected to the screen directly like it would with hdmi or dp, it's instead sending a video feed to the goggles (like youtube or netflix), and the googles then render it on the screens.