Sile

Seriously??? Hourglass was there before meta-foveated for me.

I had 1. after the first run of DCS with MetaFov. Log file is in there. Folder 2. is there after installation, but isn't named "Meta-Foveated" - it's "OpenXR-Meta Foveated" or similar. (not at home atm)

Do you have turbo mode (OpenXR Toolkit) enabled by any chance? For me DCS freezes every time i have turbo mode enabled and take off the headset. I have read about at least one other person with the same problem plus occasional freezes when switch to/from F10 map. Maybe try turbo mode off.

Factory reset should be possible without app. "... follow these steps: -Press both the power button and volume down buttons at the same time -Hold them and wait until you see a screen with various options on it (this doesn't look like the standard Quest Pro view) -Then release the buttons -Use the volume buttons to move up and down through the various options in the menu -Highlight the option to factory reset and then press the power button to choose it -You'll then need to agree to reset the headset and that will kick the process off" (Source: https://www.pocket-lint.com/how-to-factory-reset-your-meta-quest-pro/)

Yes, this is the correct location! The user get's guided through the calibration process by a wizzard after clicking "calibrate".

Nevermind. I forgot to calibrate eye tracking in the headset. Never used it before. *sweatsmile* It works! P.S.: Maybe add this step in the wiki as a step or troubleshooting. P.P.S.: And thank you!!!!

uh. how can i test if my eye tracking is working. something feels wrong. i don't think i have missed a step and the log looks promissing (attatched). openxr Explorer shows it correctly. DCS starts fine. the settings have an effect, but not the expected: but when i reduce horizontal_focus_section=0.2 and vertical_focus_section=0.2 they only reduce overall resolution - i expected to be able to see the edges of focus area. XR_APILAYER_MBUCCHIA_meta_foveated.log

@markturner1960 This thread is for "Foveated Rendering Support for DCS". Don't you already have a spearate thread for your log in issues?

Thanks for posting your feedback here. Can't wait to test myself. Still at work atm and was hoping to read some feedback here. I'm confused that you still need ASW since i could disable it before DFR was available. And interesting to hear you are also getting DCS crashes with Turbo Mode in OXR Tools in MT when taking off the Headset.

No, seperate Tool. But Turbo Mode and sharpening option included and set by config file.

You can disable Guardian completely in the Headset. You might need to enable dev mode for your meta account and for the headset software (via your phone app) for it to work. Maybe it's available without dev, i'm not sure. Or dev is necessary for it to stay off after a reboot of the headset. - Put on your headset, then go to Settings. - Select “System”, in the left menu, you now have, the line “Developer.” Click on it - At the top of the Developer Settings screen, you can use the toggle button to disable Guardian. I don't do it because the passthrough (2x tap on headset) doesn't work without guardian.

"Available in Stock"

I think at the moment things are different for ST and MT. - ST needs the --force_OpenXR Parameter in the shortcut if u want to use OpenXR API. Otherwise ST defaults to Oculus API. More here but i fear that's not true/updated for the current MT Client anymore. - MT defaults to OpenXR API. No Parameter needed. In the log you should see OpenXR somewhere in that line. So i think you are not running OpenXR, see above - ST needs startup parameter. This is what i get in MT Client Log: "VISUALIZER (Main): LAUNCH IN VR OpenXR: Meta Quest Pro" With OpenXR API you can set either SteamVR (in it's Settings -> OpenXR) or Oculus ( in Oculus home) as OpenXR Runtime. Try what works best for you. And yes. You can simply make a shortcut to the .exe in "bin-mt". But I would just copy the ST Shortcut, rename it and change "bin" to "bin-mt" in both relevant fields. And add the parameter for OpenXR, if desired.

I have sound jitter / crackling in the QPro in DCS, too. Not tested any other sim, yet. So back to using my normal headset over the Qpro . Following this thread if someone finds a fix...

Hi, i use 51xx*xxxx but will maybe try and switch down to 48xx*xxxx if there is no difference. In OXR Toolkit i use CAS Sharpening at 50 or 60% and Foveated Rendering (fixed) at Quality and Wide. Oculus Debug Tool: Encoding Bitrate 900 (Link Cable) and Encode Resolution Width at 0 or 3.600 (don't see a difference). Distortion Curvature: low Link Sharpening: Normal (with v55 - "Enable" with < v54) ASW disabled Maybe try "Texture Filtering - Negative LOD Bias" at Clamp in NVidia Control Panel Settings. Might reduce Shimmering. And maybe there is still some shimmering left and i don't notice since it's so much reduced compared to MSAA OFF or 2x.

Maybe an internal PCIe USB-C expansion card (with power connector to power supply) might help, or an external (powered) USB-C Hub or e.g. a Kuject or Syntech Quest Charging Cable with external power.

https://mixed-news.com/en/meta-quest-2-next-update-brings-new-pc-vr-feature/ "The new feature allows the artificially generated images to be calculated on the VR glasses instead of the PC, which should reduce the load on the graphics card and improve performance."

Some thoughts in response: - "Clarity" (or do you mean sharpness?) is way better with QPro. Sharpness is ~90% of G2's tiny Sweetspot over nearly the whole FOV. Colors are much better. Brightness is better. Local dimming is great. - Too much OXR Toolkit sharpening together with Quests Link sharpening is too much, yes. - Fov is much improved with the QPro vs. G2 for me. Especially when tilted slightly forward. Maybe this differs from person to person. - Battery does drain to 80% with Link cable, but then remains there stable with proper USB-C Port. I think this is per design. If you start below 80% with link cable it shoud charge to 80% and stay there. - No eytracked foveated rendering in DCS is possible with QPro. - I'm surprised of the good sound quality as well. Some additional thoughts: - No face gasket es great in summer here. I don't sweat in my face any more. This bothered me so much that i switched to 2D instead of using my G2 in summer. - 72 Hz allows dialing up of DCS Settings an still stay smooth above Headset refresh rate. (e.g. 4x MSAA here and running great - no shimmering any more)

doesn‘t make it better, I fear

Shouldn't the question be formulated "Which VR API do you like to use"? Anyway. See what you mean. I'm fine with OpenXR API in MT.

@MadKreator Author found a fix. maybe it works for you, too:

This also isn't out of context. It was posted on mbucchias (Author of OpenXR Toolkit) discord in the context of quest pros eye tracking. It was an answer to @slughead asking for clarification on quest pros eye tracking capability with dcs after you claimed it would work. (20th of may 2023)

No, sorry can't help you on this topic.

Thank you. No things are not simple (for me). Especially in VR and coming from the WMR side. With and without command line argument i get in MT: "VISUALIZER (Main): LAUNCH IN VR OpenXR: Meta Quest Pro" I suspect MT is running OpenXR regardless of command line argument. And the chain is different for MT and ST. The sticky post isn't up to date for the MT client: "DCS has a chain of VR vendors in priority oculus, OpenVR, Varjo, etc. OpenXR was in that chain in top priority, now it is removed from this chain and only available when you explicitly specify it in command line of DCS." This changed after the MT Update, where OpenXR got the default for MT.

Ok finally I had some time to test it. DCS starts with or without command line argument. (--force_OpenXR) How can i tell DCS uses Oculus API when starting without it? I suspect it starts in OpenXR mode regardless of the command line argument. Yes OpenXR Toolkit works with both ways.