halufpv

I only play multiplayer, so it's not up to me

Any news on when an update will happen? Haven't been able to play Hind or Apache (basically, my two helos) for over two weeks

Seems like there's a lot of demand for this... Did you mention it to the team @BIGNEWY?

Sorry if this is a stupid question, but what's the point of this vs using Quest Link via cable?

I was genuinely very excited for this, VRAM maxing out has been the bottleneck on my system with DCS for a long type, and despite upgrading from 8GB to 12GB GPU, I'm still forced to run both low general/terrain textures to get a stutter free experience in VR with the Apache in Syria. The process of installing this ran just fine, but I didn't seem to get the results I expected. First, the VRAM usage isn't significantly different than it was. I always get 11-12GB, and this continued to be the case after applying the mod without changing settings (low/low). I can't say I noticed a difference in visual quality. Second, I assumed perhaps with this mod I'd now be able to at least increase the setting from low to medium/high, and while medium/low worked, high/low or high/high produced stutters. Am I right to think I was perhaps expecting too much, and that this tool is best used to artificially produce a "very low" setting for people who can't play even in low?

Honestly, even if we can't switch between VR and 2D, just the ability to "reconnect" to the VR session if the headset disconnects would massively help. This actually "sometimes" works if you do it really quick, at least on Oculus, albeit the eye tracking never works again until DCS restarts, you get insane lag for the first 10-20 seconds, and sometimes DCS crashes anyways before the lag is resolved. To reproduce: Use any Oculus quest headset, enter Oculus link then open DCS in VR mode. Enter any mission, then unplug the headset usb connection and plug again immediately. Now, as fast as you can manage, enter Oculus link mode again. DCS will open, but whether it crashes immediately, after a bit, or enters this lagging state is a lottery. If you have the Oculus Quest Pro and are using quad views, eye tracking is always frozen and the quad views high res area is wherever you were looking before you unplugged, though even then in this laggy blurry state you might be able to at least declare mayday and land

+1

This has been brought up many times before here and on reddit. It's the number 1 reason I end up giving up on DCS every time I get back into it. War thunder has it. MSFS has it. I've had this issue with various Oculus headsets where something about them crashes (eye tracking stops working, artifacts start appearing, VR session bugs out...). On every other VR sim, it switches back to 2D, I can restart the headset and get back into VR. On DCS, the mission is now unrecoverable. The amount of times this has happened to me on the apache after spending an hour sneaking into position on a multiplayer server right before I start the engagement is just too much. Please please please @BIGNEWY

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