Dentedend10

This is absolutely phenomenal! DCS is a completely new experience to me. I'm not even sure what made such a huge difference in the way the sim looks, as I was mostly expecting performance boost. Maybe turning off the bloom effect, CAS sharpening, or turbo mode. Basically whatever shimmering I had before is 90% gone! Clouds look amazing, everything is sharper, and no shimmering. What a treat! Thank you so much for your work on this! The only thing I noticed is on Marianas map in the F14, where usually ASW kicks in, I was seeing the usual ghosting I used to see with ASW. However, I thought foveated rendering might not work with ASW. Anyways just minor observation, getting back into the virtual cockpit for now!

Amazing!! Can’t wait to try it

Hi, I’m running the QPro with 4x MSAA as well. However, I’m still getting some shimmering especially outside the cockpit. Can I ask you your settings how you got rid of it? I have render res set in oculus app to 1.2 (48xx*xxxx can’t remember number exactly). DCS settings are high to Med. I use OpenXR toolkit. do you use any type of sharpening?

I've just noticed the updates haven't made it into the Open Beta yet. I'll try these files next time.

Took a couple comparison shots to see if it is worth going with the higher resolution in Oculus app. To me it seems that there is minor difference inside the cockpit between 4864*2448 vs 5408*2736 and basically no difference when I look outside. There is quite the performance difference though. This makes me want to stick with the lower res. What is other people's perception?

Thank you, disappointing to read that. OpenXR Toolkit and its features allow us to enjoy VR much more. Unfortunately Aero is still double the cost of the QPro (with trackers and controllers). Maybe next year when more headsets come to the market the cost will start coming down or other alternatives appear

Is this something that could be worked out on ED’s part? DFR works great in MSFS and would be great to have in DCS not just for Aero uses but for other devices with eye tracking as well. - Quest Pro user

Hi, I’m having the same issue with shimmering. Also on Quest Pro. I was hoping the QPro would be high enough resolution to get rid of that. Set LOD to Clamp. I wonder if this is current VR / headset resolution limitation? For instance do Varjo users have shimmering? also, in Nvidia control panel, anyone played around with DSR (dynamic super resolution) settings? Would that help?

Hi, thanks for your response. The ejection isn’t happening due to pressing a button. It happens because my VR hands touch the ejection handle when the controllers are in my lap. Therefore, adding a modifier doesn’t change anything as the ejection isn’t happening due to pressing keys.

Hi, accidental ejection happens many times as I play with the controllers and I have to place them in my lap many times. The software recognizes the controllers touching the ejection handle and results in me ejecting in the worst possible scenarios. while I love the fact that you can activate the ejection handles like that, could we have an option for the F18 to deactivate that? Currently I can only fly if I dearm the ejection seat all together which is not very realistic. thank you!

SOLVED - OpenXR MC was interfering. Had to set a parameter to 0 to disable the software from using the controller for tracking. Now both controllers show up

Have you tried changing the runtime in SteamVR settings? It might have to do with the fact that MT version only runs in OpenXR. I have similar issue with left hand controller but am on a Quest Pro running OpenXR - Oculus runtime. When I run it without OpenXR (ST version) the controllers show up fine.

Do you btw use the controllers? Are they working for you in MT?

If you run MT, it's running OpenXR. If you run ST without command line, Oculus API is running - I know it because I cannot open OpenXR toolkit and my second QP controller shows up. If I run ST version with command line, OpenXR is running - I know it as I can open up the toolkit and my second hand controller isn't working. This also shows the second hand controller isn't working because of the OpenXR API I believe MT forces OpenXR - my second controller isn't working because of that. If Oculus API was running then my controller would show up - I think

Hi, After some experimentation, it seems if I run DCS with OpenXR, then my MEta Quest Pro second controller (left hand) isn't recognized. If I run DCS with Oculus API (not forcing OpenXR) then I can see both controllers. If I run MT version, then only one controller shows up (further proof that OpenXR messes with second controller). I hope that this can be addressed. Thank you

I also have to add that the tracking is way better than G2. My room is not the best lit and anytime I turned to arm the ejection seat in the F14 the G2 tracking would get lost. The QP tracks beautifully all around, in case that’s a consideration for you. I still haven’t been able to get my second controller show up in DCS though, waiting for help on that. with the resolution turned up on QP I think finally I can say goodbye to the G2

Hi, right hand controller is working properly in game, the left hand isn’t showing up. this is with Open Beta MT, Oculus Runtime. the issue isn’t the controller as it’s working fine in MSFS under identical settings. Any help or suggestion is appreciated I narrowed the issue further: ST version, no command line - both controllers work (I believe DCS is running in Oculus API) ST version, command line forcing OpenXR - only right controller works MT version, OpenXR is the only option - only right controller works. This is pointing me in the direction that DCS with its current OpenXR implementation might not recognized second Quest Pro controller.

Thanks a lot! I’ve given it a try, and it does make a difference. Now I’ll try to maximize it with still acceptable performance and I’ll try without FSR later. well for me what breaks immersion most is when I look at another plane next to me and the wings are all shimmering - now with the Quest Pro I was able to turn up MSAA to 4x so that almost solves it. the other thing is the gauges - initially I wasn’t happy how they looked compared to G2 but now with increased resolution they are starting to look better, still with good performance. I’ll report back once it’s fully tuned. The aero does seem to have all what I’m looking for with the high res and DFR. But it is hard to justify $3000CAD (with base stations and controllers). And the performance might still be questionable

I see. It’s also at 1.0 (4128*2096) at 72 Hz

I left PD at 1.0 in DCS. Other than that I’m only running OpenXR Toolkit with FSR supersampling set at 100 (just found it is crisper with FSR on than without). Am I missing something?

Thanks anyways, yea maybe that would solve the controller issue

For people who went from G2 to Quest Pro. Aren’t you missing that sweet spot high res? I’m honestly debating sending it back and rather waiting it out for an Aero. I agree that colours are better, edge to edge clarity, much better performance, etc. but I really notice the lower res when looking at my gauges in the F14.

My understanding is that the API is OpenXR even when you run DCS natively with Oculus Runtime. API first, and then Runtime. I might be wrong though. regardless, controllers seem to work in MSFS under pretty much identical settings. DCS won’t recognize my left hand controller. are you running Quest Pro with controllers?

I was running SteamVR as I need motion compensation for motion sim and OPENVR MC was the only one available. Now that there is OpenXR MC I’d like to not run SteamVR due to the reported bottleneck. I’m not sure if I understood what you’re saying there. I can run Quest Pro without oculus app and oculus runtime? How do I that?

Hi, I’ve been trying to switch to Oculus runtime from SteamVR. now when I launch DCS, only the right hand controller is recognized. Both controllers show up in msfs with same runtime. This is in MT version, open Beta, using OpenXR toolkit. Any ideas? thanks