Meta Quest Pro Settings

[YoYo]

10 hours ago, freehand said:

I am behind the times then lol

As far as I know, this particular patch was region-by-region in different time, so it may be that everyone had it released at a different time. Patch v55 was not released immediately for everyone. I also had a different one than some of the people here. So there is nothing strange here. 

[skywalker22]

29 minutes ago, YoYo said:

As far as I know, this particular patch was region-by-region in different time, so it may be that everyone had it released at a different time. Patch v55 was not released immediately for everyone. I also had a different one than some of the people here. So there is nothing strange here. 

.. if you follow steps on the link I provided, you can update as soon as it comes out.

[slughead]

9 minutes ago, skywalker22 said:

.. if you follow steps on the link I provided, you can update as soon as it comes out.

And risk having a useless headset.... the PTC for the last three releases at least has been riddled with bugs.. after all, it is a "public test channel". Use it at your own risk. You can see all the complaints in the PTC megathreads for each version here:

 

Announcements - Meta Community Forums (atmeta.com)

[Sile]

vor 50 Minuten schrieb slughead:

And risk having a useless headset.... the PTC for the last three releases at least has been riddled with bugs.. after all, it is a "public test channel". Use it at your own risk. You can see all the complaints in the PTC megathreads for each version here:

 

Announcements - Meta Community Forums (atmeta.com)

I opted out of PTC because of that. And many reports about bricked controllers in v55 PTC.
Plus the annoyingly high update Frequency in PTC - always combined with lengthy controller updates.

I suggest staying in stable. The rollout interval is about 4 weeks. So once a Version becomes stable you might get it on day 1 or after 4 weeks. 
I don't care because most changes are for standalone usage and don't bring features that are considered to improve my cable link scenario.

[freehand]

I am not part of the PTC and waited for roll out just to be clear.

[mbucchia]

@nikoel after some back and forth with @Sile and some experiments, I can now confirm that the crash on removing/putting back the headset looks like an Oculus bug and nothing I can fix. It is exacerbated by the Turbo Mode, but nonetheless an Oculus bug.

EDIT: I have one last idea for a disgusting hack to try to fool the Oculus runtime, but after that I have no other avenues.

Edited August 1, 2023 by mbucchia

[nikoel]

1 hour ago, mbucchia said:

@nikoel after some back and forth with @Sile and some experiments, I can now confirm that the crash on removing/putting back the headset looks like an Oculus bug and nothing I can fix. It is exacerbated by the Turbo Mode, but nonetheless an Oculus bug.

EDIT: I have one last idea for a disgusting hack to try to fool the Oculus runtime, but after that I have no other avenues.

 

Thank you

I will post a bug on the Meta forums 

[nikoel]

@Sile and everyone experiencing this bug is the “disable proximity sensor” trick inside debug tool working for you to counteract this?
 

It does nothing for me and I’m suspecting that it’s an other dead feature but thought I’d ask first 

[Sile]

Last time i tried it did nothing for me.

Thinking of taping it:  I can't even find that sensor. In pictures of the Quest 2 it is clearly visible. Does it work differently for the pro ...? And is that feature only for other models?

Edited August 1, 2023 by Sile

[nikoel]

30 minutes ago, Sile said:

Last time i tried it did nothing for me.

Thinking of taping it:  I can't even find that sensor. In pictures of the Quest 2 it is clearly visible. Does it work differently for the pro ...? And is that feature only for other models?

 

It’s right inbetween the lenses. Only some surfaces trigger it. Just hover your finger over it and you’ll be able to pinpoint it. For me tape did nothing, but black-tac worked. I used insulation tape, so maybe masking tape would have worked

YMMV

 

 

Edited August 1, 2023 by nikoel

[Sile]

@nikoel thanks, found it!

But good news. Have just been testing the latest experimental build from @mbucchia and had no (turbo mode on) crashes when taking off the headset in a 15 min test session. 

Took it off multiple times for 10 to 30s.

Edited August 1, 2023 by Sile

[nikoel]

7 minutes ago, Sile said:

@nikoel thanks, found it!

But good news. Have just been testing the latest experimental build from @mbucchia and had no (turbo mode on) crashes when taking off the headset in a 15 min test session. 

Took it off multiple times for 10 to 30s.

 

You be sayin’ that the aforementioned dirty, disgusting hack works…?!

I’m not even remotely surprised; Mbucchia coded it. Of course it works 

[mbucchia]

2 hours ago, nikoel said:

You be sayin’ that the aforementioned dirty, disgusting hack works…?!

I’m not even remotely surprised; Mbucchia coded it. Of course it works 

Yes ahah the horrible hack worked. It looks like the Oculus runtime isn't properly resetting their frame state machine upon beginning a new session. I had to add some unnecessary calls (that would fail on non-Oculus platform) to force it back to a good state. I will report the issue to the Oculus dev.

I'll have that new version out later this week.

 

Thank you @Sile for all the testing!

Edited August 1, 2023 by mbucchia

[YoYo]

Great support @mbucchia like always, Thank you!

[autracer]

Hi Pilots

I‘ve Problems since a few days with quest link USB-C/ USB-C.
When i use open xr tools, i have a brighter gap on the bottom side from my view.
It renders with less colors.
Without aktive tools, the picture is clear.


Gesendet von iPad mit Tapatalk

[theperson]

9 hours ago, autracer said:

Hi Pilots

I‘ve Problems since a few days with quest link USB-C/ USB-C.
When i use open xr tools, i have a brighter gap on the bottom side from my view.
It renders with less colors.
Without aktive tools, the picture is clear.


Gesendet von iPad mit Tapatalk

Try lowering your Encode Resolution (Width) in either oculus tray tools or the oculus debug tool

[autracer]

Try lowering your Encode Resolution (Width) in either oculus tray tools or the oculus debug tool

Thx, give it a try


Gesendet von iPad mit Tapatalk

[slughead]

19 hours ago, autracer said:

Hi Pilots

I‘ve Problems since a few days with quest link USB-C/ USB-C.
When i use open xr tools, i have a brighter gap on the bottom side from my view.
It renders with less colors.
Without aktive tools, the picture is clear.


Gesendet von iPad mit Tapatalk

I have had this too. I haven't seen it again since setting the dynamic bitrate offset to 50 and leaving encode dynamic bitrate to default, i.e. enabled.

 

null

[Tomcat388th]

I dont know if this would even apply since I'm running a quest2 but here is what I'm running with link cable. The encoding and bitrate numbers I got either form this post or another quest pro post.

[biotech]

49 минут назад, Tomcat388th сказал:

I dont know if this would even apply since I'm running a quest2 but here is what I'm running with link cable. The encoding and bitrate numbers I got either form this post or another quest pro post.

Enc. res. 3902 is to high for Quest Pro. Try 3664. Higher values make no sense.

[YoYo]

6 minutes ago, biotech said:

Enc. res. 3902 is to high for Quest Pro. Try 3664. Higher values make no sense.

See his posts and tests.

[autracer]

Try lowering your Encode Resolution (Width) in either oculus tray tools or the oculus debug tool

Thx Guys. ODT solved the issue.


Gesendet von meinem SM-G980F mit Tapatalk

[Tomcat388th]

On 8/5/2023 at 1:35 PM, YoYo said:

See his posts and tests.

Yep that was the post I've have been happy with these setting for my Quest2 I consider my system mid range. MP servers run really smooth and I have a nice clear and readable cockpit F18. For anyone looking at my screen shots this is for my quest 2 setup I dont want to derail the original post

[Slammin]

For anyone using Globular Cluster comfort kit, a free upgrade to v2 is available.  I'm awaiting mine but I hear very positive things about it.  Just message john5936 on Discord for your free upgrade.

[autracer]

Benchmarks:

Nice Benchmarks. Give em a try.


Gesendet von iPad mit Tapatalk