DirtyMike0330

I would also recommend you join the public test channel, enable dev features, and also eye tracking (once you configure eye tracking in the headset itself). This will get your local dimming activated as well.

As Slug mentioned, I would use OTT if I were you https://www.apollyonvr.com/oculus-tray-tool It lets you set per-game profiles. So, for example, when I launch Il2, it turns ASW off since I don't need it for 90fps. When I launch DCS, it will kick on ASW 45. It has some other convenient features as well, such as changing your audio devices. So, since I use my Arctis headset with the QP, it will automagically change my windows audio devices to the Arctis when I connect the QP, and then revert back to my PC speakers when I disconnect. It will also retain any PPD and ASW settings in general, if you opt to not use profiles.

1) will it need charging first? It will have like 50-80% , but it doesn't take long to charge up fully and you might as well prior to setup. Just toss it on the dock. 2) I ordered a link cable as well, how does that work, is it power from the PC? It allows you to use the QP as a PCVR device, so you get the benefits of that. Having a hard connection and the ability to use the PC oculus software to change various settings is ideal for flight sims. You get power from the PC, but not enough to keep the headset charged indefinitely. See my first post and subsequent posts throughout this thread that link a usb-c hub (https://www.amazon.com/dp/B0BS9C9RBZ?psc=1&ref=ppx_yo2ov_dt_b_product_details) that allows you to play in PCVR mode indefinitely. As far as settings, I linked the settings from another forum member in my original post and would recommend that to you as well. 3) Will there be any conflict from currently installed software for my G2? Do I need to uninstall anything? Probably not, but I always prefer to have a clean canvas when switching ecosystems. Personally, I would recommend uninstalling anything related to WMR first. Just my preference and it is easy enough to reinstall if you go back to the G2. 4) I use OpenXR in DCS, via the shortcut, is that dispensed with now? DCS MT and MSFS launches in OpenXR natively, no need to tinker. For IL-2, I manually drop in the OpenXR .dll from https://gitlab.com/znixian/OpenOVR/-/tree/openxr 5) what software do I need? Its Occulus, so do I need something from them? Oculus Home software for your PC, Oculus Tool Tray for easily changing settings and setting up profiles that launch per game https://www.apollyonvr.com/oculus-tray-tool (or use native Oculus Debug Tool), and the mobile app for initial setup (and phone notifications, which I find very helpful). See original post for link to forum member's settings for the PC software. 6) What will I need the hand controllers for, I dont use mine at all in DCS currently with the G2...are they required for set up only in this case? ( I wont be using for anything other than DCS seated) You don't have to use the hand controllers. You can use the headset volume buttons, your mouse, or setup hand tracking inside the headset (pretty nice actually). If you want to access your desktop through Quest Link (the cable you're plugging in and then communicating with the PC software), you have to use the controller to click the DESKTOP button. Hand tracking doesn't work for that. But after that, I just power off the controller and start whatever games I'm playing. Or you can just bypass the virtual access to the desktop and use your PC monitor and mouse to launch whatever. That will make more sense once you're actually setup.

I don't think anyone has claimed that the QP is the VR Holy Grail However, considering what is currently on the market and factoring in price, FOV, performance... I personally think it is the best option if you want to have an improved FOV, with edge to edge clarity, and great performance with an adequate PC. I used the G2 for years, but could never go back to that pinpoint sweet spot and feeling of having a restricted FOV. I actually put it back on a couple weeks ago and it was a real bummer; went right back to the QP. The other thing we can't forget here is that the DCS engine sucks. I still play it a lot, but IL2, MSFS, and Elite Dangerous are a much better visual experience in VR. No headset is going to change that, ED needs to change that.

Settings > System>Link Ooooh, I'll have to enable hand tracking and try that!

My workaround for this is: When in desktop/quest link, before I start the game, I will long press to power off the controller. You should see the popup one time, which will disappear. Then they don't pop up anymore when I actually start IL2/DCS/MSFS and am playing. The only reason I power the controllers on at all is because the QP will not let you click the DESKTOP button after you launch quest link unless you use the controller apparently.

No… because, once again, you are trying to compare the edge to edge clarity of pancakes lenses to the limited sweet spot of fresnel lenses. It’s apples to oranges. Your entire logic here is flawed and you’re either trolling at this point, or just not very smart. I’m leaning towards the latter.

Exactly.

I'm not sure this works like you thought it might. You are still comparing Fresnel lenses to pancakes. And the resolution setting wouldn't change the sweet spot of the G2, it sounds like you essentially just made the whole thing less clear. Not a great comparative test, to be honest. I am going to shill this product again because it is so stupidly reliable for the QP, as far as ensuring I can play as long as I want in PCVR mode: Amazon.com: Minisopuru Powered USB C Hub, 10Gbps USB-C Hub 4 Ports Support Data & Smart Charging(Not Support Video), USB C to USB C Hub Multiport Adapter for MacBook Pro/Air, iMac, iPad, Phone, Chromebook, etc. : Electronics - https://www.amazon.com/ Some folks recommend a 3rd party Kuject cable thingie, but mine is sitting in the closet and I didn't have a good experience with it, personally.

I just popped the G2 on and started up DCS-MT; I still see the upside down and facing backwards issue unfortunately. My OpenBeta is up to date. Tried with OpenXR neck saver on and off. Edit: After a repair, it seems XRNeckSaver is still the culprit here. Starting DCS-MT without the app works fine and with the app recreates the inverted/backwards bug. Bummer.

Ask for a price adjustment with a friendly "or I will cancel"

I am on the latest software and ODT ASW settings don't persist for me either; I am just in the habit of opening it up after I connect the link cable. Which is fine, since I use ASW for some sims and disable it for others.

I tried the Kuject cable that everyone recommended but still lost battery too fast. However, this little gem here… Minisopuru Powered USB C Hub,... https://www.amazon.com/dp/B0BS9C9RBZ?ref=ppx_pop_mob_ap_share I can play all day if I want to and maintain battery level, sometimes even gain a few percent. It pushes close to 10 amps actively charging the QP while you’re playing.

I just bookmark it since I don't generally pay attention to anything else on the forum anyway. null

This is plausible because there’s enough folks here with similar high-end hardware having the same good experience with the QP. Unfortunately a local issue would be a lot more difficult to troubleshoot for the op. Speaking of which, @minimi66 you mentioned your 3080ti - is your 4090 upgrade brand new? Did you do a full wipe of previous GPU drivers prior to installing the 4090? With something like DDU? Just a random thought.

I mentioned the hub specifically for providing power to the Quest Pro; the Kuject cable solution did not work well for me, and the headset would still drain too quickly. With that hub, I can play all day and not run out of juice. The display is nice because it shows exactly how much amperage the hub is pushing out (close to 10 amps when it is charging the QP).

Yeah, that does appear to be a different one than the one I linked- mine actually has a window that shows how many amps it is pushing out when it is charging my Quest Pro up. Yours looks like the power delivery port is only the bottom one; you did use that one and not one of the sides, right?

Are you using Virtual Desktop? I thought I glimpsed that in an earlier response maybe. If so, see footer #1.

I have mine set like this because I don't like the default key binds to open the app in-game (see attached). So, once in-game, I hit ctrl + down arrow to open the app and then ctrl + up/right/left to navigate the menus. What you are looking for is under PERFORMANCE and then OVERLAY. Highlight the ADVANCED option, which should then put the overlay in your view when you exit OpenXR toolkit. This will give you your CPU/GPU performance. So, when you are flying in an area and looking at the ground, if you see stuttering, make a note if your CPU or GPU is exceeding 10ms of frame time or going haywire in some fashion. null

Just to clarify: You have confirmed you have the correct runtime selected in the Oculus Home App, your multithread launcher has "X:\DCS World OpenBeta\bin-mt\DCS.exe" --force_OpenXR in the properties target field? Are you using OpenXR Toolkit at all? I would recommend it because it will allow you to turn on a performance overlay that will show you what your CPU and GPU is doing during gameplay. Quickstart | OpenXR Toolkit - https://mbucchia.github.io/ - It is VERY simple to setup. Also just do a quick inventory to make sure you don't have any unnecessary or possibly conflicting software still installed, such as anything to do with windows mixed reality. The only annoying thing with ASW that I have noticed is with other airborne craft. If a plane flies by you quickly, they may ghost a little, this is currently unavoidable. I mostly notice it on merges; formation flying, and things of that nature are not a problem. However, your ground visuals should be smooth with ASW. I also have hyperthreading disabled

Again, a false statement. I can zip through a major city on the PG, on the deck, looking out right or left, and it is perfectly smooth. And you preface your BS with statements like "I turn off clouds". Like, why are you even in VR? Why spend money on this hardware if you are going to lower your settings so drastically? Also, why are you continuing to offer up your BS to someone with superior hardware to yours and a completely different VR ecosystem? Go away lol

I use basically the same settings P.S. I would also disable bloom in DCS, it generally doesn't look great in VR.null null

OP, the goal here is that you need to figure out why 45 ASW is not working on your system, if you are indeed selecting it but your frames are staying unlocked and hitting the 70s. We have a similar system and the same VR headset, unlike some folks giving you insane advice. I have attached pictures of my settings so you can compare. In the picture of the Oculus Home app, you would click on the Quest Pro and you can slide the render scale to the right to 1.5 or 1.7 (I have mine maxed at 1.7) With these settings, your ASW should be locked to 45 and you will have smooth gameplay in every scenario, including multiplayer. If, with these settings, your ASW is not locking you to 45, then something else is going on in your system. You do not need WMR, you do not need to drop your render resolution, you do not need anything extra. Also, I am running this on the multithreading executable.

Yeah, buy a 4090 and high-end CPU and then drop your settings to low lol You are a genius.

Again, this is terrible advice. OP doesn't need to do this with a Quest Pro, as @dburne also mentioned, due to Oculus native support. You're sharing WMR settings that don't even apply to them. OP also has superior hardware and doesn't need to render anything at 50%. Your suggestions are worthless in this scenario.