ChariotOfFLAME

Duplicate of

Remember, even if it’s “Meh” when you put it on, give it a few flights in weather, night, sunset, and mid day, then make your final judgment.

Good shout: I was on my phone and couldn’t read the log. Also, make sure the OpenXR plugins are in the correct order using either the registry or this really nice tool OpenXR API Layers GUI. It’ll tell you if they are out of order. This caught me out when moving to WIN11 last month

You could try a Bigscreen Beyond 2 as a reasonable sidegrade, but to be honest the boutique PC VR ship has sailed; unfortunately, it’s not super profitable at scale. If money is no object, however, maybe reach out to a retailer about the Somnium VR1

Can you expand more on the steps you have taken to try to resolve this problem? It’s hard to help if we don’t know what you’ve done already. Have you made Pimax the default OpenXR runtime? DCS in VR is an OpenXR application now, so you’ll need to do that.

I had a 3090ti 24GB. The frame times are not great these days and OP will run into the same issues they are today. Stick to 40 series or higher imho

Yeah, I’m very underwhelmed for all the reasons listed above. Most important for us is battery life: - best case: ~4hrs - worst case: less than an hour (for real, wtf?!?!) That makes it a novelty and not a gaming device, and removes the capability to go untethered for us DCS folks (if you even can play while it’s charging, which is unclear). If it’s more than $600, the market won’t bear it at all. It’s a Quest 3+, essentially, so it needs to be priced that way or it’s going to only sell to tech YouTubers and Steam chads.

Here’s a mod you can use to remove it until/in place of an option from ED:

Pure speculation, but Meta may have made updates that aren’t compatible with Win10 due to it being past EOL now

A long time ago, I switched to using a sabrent powered USB hub that lets you power each port individually and plugging all non-essential USB devices into that instead of the MOBO, then only turning on what I need when I need it. I went from having tons of disconnects and big stutters to much more clear and clean with few to no disconnects in 1 purchase.

I wonder if anyone has tried creating a different software stack for the Q3. Probably not due to needing to create their own SLAM service and OpenXR implementation

Pretty sure once it runs on Vulkan, that should be a lot easier

@BIGNEWY can we get this pinned? Seems like a good thread for the growing Linux crowd pre-Vulkan release

Thats what people say, but I’ve had tons of success with an aftermarket link cable that also charges the headset myself

Sounds like a centering problem. Bind the VR Recenter button (default is numpad 5) and try that

For those interested, this feature was mentioned as an addition to the F-16 and F-18 in the latest update notes. I would also love a toggle to turn this off, as the fact that the helmet visor is a 3D texture that has to be tracked to the head position in realtime and not just a camera filter that is overkayed over the viewports in a purely 2D fashion, has performance impacts. @BIGNEWY My proposal would be a “Visor” graphics option with 3 selections: - Advanced: as it is now - Simple: a “camera filter” of the visor texture with no cutout that still has a scrolling animation when lifting the visor to remove the filter, but the helmet is no longer modeled in the viewport, nor is there a need to track the filter to the viewport. EDIT: Simple should essentially be this community mod: https://www.digitalcombatsimulator.com/en/files/3347561/ - Off: reverts to pre-update behavior, with no helmet modeling and no filter. I would imagine it would operate similar to the IHADS option in the Apache. Also, the animation for raising and lowering the visor is extremely slow. I’d love to see it cut in half! Maybe have some folks try the motion at their desks and film it with a smartphone. Time their movements, then take the average of the most realistic looking attempts and adjust the animation duration accordingly (ye olde Disney animation research method!)

@mbucchia do you have any thoughts on the theory above in the last paragraph?

It could also be improperly ordered OpenXR layers. That’s what it was for me when I installed Win11 recently

I don’t think so: I think there’s a size issue between the aircraft models and the world

1. Always launch from the .exe or shortcut. This will ensure that DCS launches in the way it is expecting, which will give you the best chance at a consistent experience 2. Anything you set in the NVIDIA control panel will act as an override and will take precedence over everything else (with the exception of settings you set to “auto” or “let the application decide”). Settings you set in the NVIDIA App will override the settings you previously set in the DCS launcher/in-app, or vice versa, depending on whichever you set last. I recommend using the launcher for these settings

Yeah, I’ve noticed the smallness too. Most evident in places I’ve actually been like London and Paris. but the jets are the correct size, right? Or are they too small as well?

This was using the out-of-the-box ED flight model. The only mods we used was our custom livery and a few of the other airshow aircraft

Hey folks! @Brother_Leb and I have been working the past 5 years to polish up a Blue Angels Solos performance worthing of filming and posting, and we've spent the past 6 months making this for you! Here is the Legacy Blue Solos High Show, a full high show performance and love letter to the U.S. Navy Blue Angels. Hope you enjoy!

This is the official HP replacement: Go to https://partsurfer.hp.com/?searchtext=22j68aar the link may not work right, but partsurfer is what you need.

It may be due to some sort of USB management in windows. I highly suggest going to your USB devices menu and ensuring that all of your USB devices are not set to sleep when inactive.