Meta Quest Pro Settings

[YoYo]

1 hour ago, biotech said:

Turbo Mode option in OXR Toolkit or in DFR tool causes such CTD when headset goes to stanby mode. Switch off Turbo if it is on.

 

Good to know, I have Turbo Mode = on however for now, I stay with Turbo turned on, I fly anyway without ASW and it's always a few more frames.

Edited July 21, 2023 by YoYo

[gonvise]

1 hour ago, slughead said:

The Oculus Developer Tool has a "Bypass Proximity Sensor" option. This may work. What will work 100% is some tape over the sensor just between the lenses. Just remember to turn off your headset when you're done with it.

This works?? Thanks!!! but... have a fixed image for a long time can damage the lenses? in other previous glasses it was not recommended.

[slughead]

Just now, gonvise said:

This works?? Thanks!!! but... have a fixed image for a long time can damage the lenses? in other previous glasses it was not recommended.

As I said... "turn off the headset when you're done with it".

[gonvise]

37 minutes ago, slughead said:

As I said... "turn off the headset when you're done with it".

Yeah, that's clear, but is it safe to take your glasses off for, say, 15 minutes and leave a fixed image on the lenses?

[slughead]

1 hour ago, gonvise said:

Yeah, that's clear, but is it safe to take your glasses off for, say, 15 minutes and leave a fixed image on the lenses?

You'd need to ask the manufacturer.

[dburne]

4 hours ago, gonvise said:

Yeah, that's clear, but is it safe to take your glasses off for, say, 15 minutes and leave a fixed image on the lenses?

 

I would never do that with my Aero. It is safe if just at the home screen as the headset will go into standby mode. I oftentimes leave mine like that throughout the day when I am using off and on during the day.  With a game being displayed who knows, that I would not do myself.

[freehand]

Never had a problem with the quest pro not turning off or on.

And never had a crash.

Edited July 21, 2023 by freehand

[Tophatter14]

Just wanted to say thanks to all those who contributed their settings, tips and troubleshooting.  Mine is now running nicely (with foveated rendering) and it's awesome. 

[nikoel]

@mbucchia I recall you replying to my bug report in one of the pages on this or one of the other three threads (which has now basically blurred into one thread split into 4) saying that you were no longer sure if it was DFR or something else causing the CTD

I had turbo off to correct for this issue, but would love to turn it back on again as the experience for me is better with Turbo. Do you happen to know if it's DCS, Toolkit, Meta or DFR yet?

[mbucchia]

6 hours ago, nikoel said:

@mbucchia I recall you replying to my bug report in one of the pages on this or one of the other three threads (which has now basically blurred into one thread split into 4) saying that you were no longer sure if it was DFR or something else causing the CTD

I had turbo off to correct for this issue, but would love to turn it back on again as the experience for me is better with Turbo. Do you happen to know if it's DCS, Toolkit, Meta or DFR yet?

Can you tell me exact steps to reproduce? I tried yesterday with a Quest 2 (cause that's all I have that can use the Oculus runtime), and I have no issues when removing the headset.

[mbucchia]

@nikoel the only crash I got taking the headset off/on is with "double Turbo" aka having Turbo on in both Quad-Views-Foveated and OpenXR Toolkit. That's a really bad idea in the first place (and one of the reasons I ask people to reset all settings in OpenXR Toolkit). Use Turbo either in one or the other.

I'm not sure this is your issue, but I couldn't get a crash unless I intentionally made that mistake. 

[Sile]

Getting 100% crashes on Quest Pro when OXR toolkit is disabled and Turbo is on in Quad Views when removing the headset.

Also without Quad Views (uninstalled) and only OXR Toolkit enabled and OXR Turbo on and removing the headset.

Sometimes when switching from F10 to Cockpit with either Turbo.

Edited July 23, 2023 by Sile

[mbucchia]

1 hour ago, Sile said:

Getting 100% crashes on Quest Pro when OXR toolkit is disabled and Turbo is on in Quad Views when removing the headset.

Also without Quad Views (uninstalled) and only OXR Toolkit enabled and OXR Turbo on and removing the headset.

Sometimes when switching from F10 to Cockpit with either Turbo.

 

Can you do the following? Preferably with Quad-Views-Foveated and no other program like OpenXR Toolkit. 

1) open ADMIN command prompt

2) run `wpr -start %ProgramFiles%\OpenXR-Quad-Views-Foveated\Tracing.wprp -filemode`

3) run DCS and reproduce the crash

4) back to the command prompt, run `wpr -stop trace.etl`

5) ZIP up the `trace.etl` file (the ZIP step is important!) that was created (it is created in the current folder, aka the one you can see the prefix for in the command prompt) and send it to me

Thanks.

[Sile]

Will do, but it will take a while till i get home.

Edited July 24, 2023 by Sile

[Ramstein]

On 2/22/2023 at 11:23 PM, Ginsu80 said:

I recently upgraded my old Rift S to a Quest Pro. Does anyone have any settings or tweeks for the pro. The visual quality is much better but performance wise I've definitely taken a hit. I have been using Oculus Tray Tool and fiddling with some of the settings, without a whole lot of luck. Wondering if anyone has had more luck that me. 

Currently running a 5800x3d and 3080ti, DCS and windows on SSD, 64gb of ram. 

how it the Quest Pro compared to the Rift s ?

[Sile]

vor 17 Stunden schrieb mbucchia:

Can you do the following? Preferably with Quad-Views-Foveated and no other program like OpenXR Toolkit. 

1) open ADMIN command prompt

2) run `wpr -start %ProgramFiles%\OpenXR-Quad-Views-Foveated\Tracing.wprp -filemode`

3) run DCS and reproduce the crash

4) back to the command prompt, run `wpr -stop trace.etl`

5) ZIP up the `trace.etl` file (the ZIP step is important!) that was created (it is created in the current folder, aka the one you can see the prefix for in the command prompt) and send it to me

Thanks.

Sent per PM.

[nikoel]

On 7/24/2023 at 6:39 AM, mbucchia said:

Can you do the following? Preferably with Quad-Views-Foveated and no other program like OpenXR Toolkit. 

1) open ADMIN command prompt

2) run `wpr -start %ProgramFiles%\OpenXR-Quad-Views-Foveated\Tracing.wprp -filemode`

3) run DCS and reproduce the crash

4) back to the command prompt, run `wpr -stop trace.etl`

5) ZIP up the `trace.etl` file (the ZIP step is important!) that was created (it is created in the current folder, aka the one you can see the prefix for in the command prompt) and send it to me

Thanks.

nullObviously I am doing something wrong. But the idiot checks have revealed nothing, Command Prompt - Yes, Admin - Yes, Copy and paste the code without the quotes and in it's entirety - Yes. Filepath checks out

 

null

Edited July 25, 2023 by nikoel

[mbucchia]

2 hours ago, nikoel said:

nullObviously I am doing something wrong. But the idiot checks have revealed nothing, Command Prompt - Yes, Admin - Yes, Copy and paste the code without the quotes and in it's entirety - Yes. Filepath checks out

 

null

 

I got the trace from someone else already so it's ok

[Sile]

vor 3 Stunden schrieb nikoel:

nullObviously I am doing something wrong. But the idiot checks have revealed nothing, Command Prompt - Yes, Admin - Yes, Copy and paste the code without the quotes and in it's entirety - Yes. Filepath checks out

 

null

`wpr -start %ProgramFiles%\OpenXR-Quad-Views-Foveated\Tracing.wprp -filemode`

replace %ProgramFiles% with the complete path and add " " before and after the path:    "C:\Program Files\OpenXR-Quad-Views-Foveated\Tracing.wprp"

otherwise i also got the error you describe.

Edited July 25, 2023 by Sile

[autracer]

I thought so, but I better asked. Sorry for a dumb question

You never can ask a dumb question, you only can get dumb answers.


Gesendet von iPad mit Tapatalk

[YoYo]

10 minutes ago, autracer said:

You never can ask a dumb question, you only can get dumb answers.


Gesendet von iPad mit Tapatalk

Thats true :).

[freehand]

Received my update yesterday ver 55. 

[YoYo]

35 minutes ago, freehand said:

Received my update yesterday ver 55. 

I've had this patch for like 2-3 weeks now, honestly no changes to DCS or in other simulators. Its mainly dedicated to users of goggles in the wireless option and games from QP memory.

[freehand]

14 minutes ago, YoYo said:

I've had this patch for like 2-3 weeks now, honestly no changes to DCS or in other simulators. Its mainly dedicated to users of goggles in the wireless option and games from QP memory.

I am behind the times then lol

[skywalker22]

6 hours ago, freehand said:

I am behind the times then lol

Not that much. Anyway, you can always get updates as soon as they are available, just follow this steps for the 1st time:

https://www.meta.com/help/quest/articles/headsets-and-accessories/using-your-headset/quest-ptc/