Quest Pro - VirtualDesktopXR and Quadviews

[VR Flight Guy in PJ Pants]

18 minutes ago, slughead said:

Night mission. Look at the moon. Can be replicated in both.

Only manage to capture the the LCD screen on F/A-18C cockpit, not much difference. Will try your idea.

[slughead]

Just now, VR Flight Guy in PJ Pants said:

Only manage to capture the the LCD screen on F/A-18C cockpit, not much difference. Will try your idea.

That's because there is no difference. It's an on/off thing only.

[VR Flight Guy in PJ Pants]

2 minutes ago, slughead said:

Thanks. You have many settings dialled down compared to me, but the main thing here is that ASW is always enabled. I prefer to stay out of ASW as much as possible, as the ghosting of jets is meh. So I run at 72fps compared to your 45fps, which gives you a large headroom to increase your PD.

Agree on the above, plus, by going back to 72Hz, it generates much less ghosting problem on my end, especially when QVFR is involved. I used to use 90Hz too much

[VR Flight Guy in PJ Pants]

Some super low quality, unprocessed TTL images here. Oculus OpenXR, setting as per in video above. May try again when the room gets darker

Dim off:

Dim on:

Edited July 29, 2024 by VR Flight Guy in PJ Pants

[Maddaawg]

5 hours ago, slughead said:

VD has its own OpenXR implementation, VDxR, which is completely independent of Meta's OpenXR implementation. Thus, it is very unlikely that Meta will be able to break VDxR, which is why I am switching to VD. I also think it is unlikely that DCS could break HTCC either unless they completely rewrite how they use the mouse.

For HTCC, your referring to while using VDxR, because earlier in this thread @mbucchia said v68 could break it and other OXR tools. I think this is due to ED mishandling OXR and so VD should be safe with VDxR?

[slughead]

I will try to make sense of this as you're mixing things up.

7 minutes ago, Maddaawg said:

For HTCC, your referring to while using VDxR

If you use v67 of Meta Link, you can use HTCC with either VDxR or Meta. Meta may or may not correct their bug in PTC v68. They're a law unto themselves.

 

4 minutes ago, Maddaawg said:

said v68 could break it and other OXR tools

That's correct. Meta has broken it in the PTC of v68.

 

4 minutes ago, Maddaawg said:

I think this is due to ED mishandling OXR

Nothing to do with ED. This is purely Meta's doing.

 

6 minutes ago, Maddaawg said:

VD should be safe with VDxR

Yes, as VDxR is an entirely separate OpenXR link to your PC and completely unrelated to Meta Link.

[Maddaawg]

40 minutes ago, slughead said:

I will try to make sense of this as you're mixing things up.

If you use v67 of Meta Link, you can use HTCC with either VDxR or Meta. Meta may or may not correct their bug in PTC v68. They're a law unto themselves.

 

That's correct. Meta has broken it in the PTC of v68.

 

Nothing to do with ED. This is purely Meta's doing.

 

Yes, as VDxR is an entirely separate OpenXR link to your PC and completely unrelated to Meta Link.

Yep, I did mix up the two players that are causing OXR tools to have issues, just another reason to go with VD. PTC v68 is on Meta and may or may not break several tools in the final version, and QuadViews is currently broken from ED but has a dll fix that @mbucchia would prefer we don't use but rather complain to ED.

I'm happy with VD and getting rid of all the headaches of OpenXR compliance. Is the reason VDxR not an issue because VD dev's patch it to circumvent what ED does to OXR?

40 minutes ago, slughead said:

Yes, as VDxR is an entirely separate OpenXR link to your PC and completely unrelated to Meta Link.

I just re-read this, so even if ED or Meta breaks OXR it won't matter in regard to HTCC?

Edited July 29, 2024 by Maddaawg

[slughead]

2 minutes ago, Maddaawg said:

Is the reason VDxR not an issue because VD dev's patch it to circumvent what ED does to OXR?

You’re mixing it up again  The problem isn’t so much ED but Meta not following the OpenXR standard and/or generally generating buggy code.

I thought the latest DCS release resolved the issues with OXFR. It certainly works for me over Meta Link and VDxR and there is a mention in the release notes that it has been fixed. Whilst is says fixed for Pimax,  I think it’s fixed for all.

[Maddaawg]

5 minutes ago, slughead said:

You’re mixing it up again  The problem isn’t so much ED but Meta not following the OpenXR standard and/or generally generating buggy code.

I thought the latest DCS release resolved the issues with OXFR. It certainly works for me over Meta Link and VDxR and there is a mention in the release notes that it has been fixed. Whilst is says fixed for Pimax,  I think it’s fixed for all.

 

I had already edited my post, what I mean is either ED or Meta:

 

13 minutes ago, Maddaawg said:

I just re-read this, so even if ED or Meta breaks OXR it won't matter in regard to HTCC?

 

[slughead]

2 minutes ago, Maddaawg said:

 

I had already edited my post, what I mean is either ED or Meta:

 

 

That should be the case.

[Maddaawg]

2 hours ago, Maddaawg said:

You’re mixing it up again  The problem isn’t so much ED but Meta not following the OpenXR standard and/or generally generating buggy code.

My confusion is from a lack of sleep and coffee. I am 7.5 miles or 6.5NM in front of the Park Fire in California. Our property has been evacuated but I am already in Seattle waiting for a lung transplant. I sleep from 2am to 7am to monitor the fire all day and night and stress 24/7 between it and my lungs. I get some relief from browsing DCS stuff but I haven't really played since the fire started. So I really have no idea if this or that is fixed or what is or will be broken, I'm just trying to engage in other things in between scouring the internet for the Park Fire.

[slughead]

18 minutes ago, Maddaawg said:

My confusion is from a lack of sleep and coffee. I am 7.5 miles or 6.5NM in front of the Park Fire in California. Our property has been evacuated but I am already in Seattle waiting for a lung transplant. I sleep from 2am to 7am to monitor the fire all day and night and stress 24/7 between it and my lungs. I get some relief from browsing DCS stuff but I haven't really played since the fire started. So I really have no idea if this or that is fixed or what is or will be broken, I'm just trying to engage in other things in between scouring the internet for the Park Fire.

That's understandable. Stay safe.

[Mr_sukebe]

7 hours ago, slughead said:

I haven't experienced this. I would try the following:

1. Play some headset-only games to eliminate a problem with the headset itself - this may not necessarily be enough to cause the problem.
2. Use the DCS VR preset to reduce the load on the system as much as possible. 
3. Reset the Oculus Link to default settings.
4. Try Virtual Desktop, but I'd not go as far as buying a dedicated router just to find the fault this.

Night mission. Look at the moon. Can be replicated in both.

My thanks for the suggestions.

Using the DCS VR preset resolved it.  The toughest test that I believe I currently have is the F4 on the Falklands from cold, and it passed that with flying colours.  Whilst the graphics were dialled down against previously, there wasn't a humongous difference, and the trade off was definitely worth it.

Roll on the 7800x3d that I'm currently planning.

[slughead]

Just now, Mr_sukebe said:

My thanks for the suggestions.

Using the DCS VR preset resolved it.  The toughest test that I believe I currently have is the F4 on the Falklands from cold, and it passed that with flying colours.  Whilst the graphics were dialled down against previously, there wasn't a humongous difference, and the trade off was definitely worth it.

Roll on the 7800x3d that I'm currently planning.

Thanks great news! I hear the F4 is quite a processor hog. Hopefully in time they’ll optimise it.

[Qcumber]

32 minutes ago, slughead said:

Thanks great news! I hear the F4 is quite a processor hog. Hopefully in time they’ll optimise it.

The F-4 is not too bad. It depends on the map and setting. For meiIt has about 10% more GPU use compared to the F-16 but a bit less than the F-14. 

 

[gonvise]

8 hours ago, slughead said:

Thanks. You have many settings dialled down compared to me, but the main thing here is that ASW is always enabled. I prefer to stay out of ASW as much as possible, as the ghosting of jets is meh. So I run at 72fps compared to your 45fps, which gives you a large headroom to increase your PD.

Sure, it's a matter of taste. I for one can tolerate a bit of ghosting on jets, especially since I'm not flying alongside other jets very often, and with the last nvidia DLSS DLL ghosting is no longer noticeable anywhere, not even in the trees, but what I can't change is the quality and fluidity of that setup. With no ASW or with SSW the head or plane turn is not constant, depends on the fps at that time,  if you look at the sky it is...meh

[slughead]

8 minutes ago, gonvise said:

Sure, it's a matter of taste.

Absolutely.

[Jive]

I have VD running DCS really nicely at the moment so I shouldn't really mess with it but I'm curious if anyone knows where QuadViews takes it's config info from for VD? 

I made my QV adjustments in the companion app with a pretty aggressive 5% render in the non-foveated region which appears to be the case with Link. For example if I take a screenshot the image is super blurred. When I do the same in VD the image is maybe 25-30% res instead so it seems that it's maybe taking stock config info, which again actually plays really nice but you know, tinkering. 

@mbucchia am I way off or is it a different config file? 

[Phantom711]

@Jive

Very good question. I was wondering the same since in the config it only has an [Oculus] line and some others… So should there be a [Virtual Desktop] line also? How would we know how to name it exactly?

Edited August 7, 2024 by Phantom711

[mbucchia]

@Jive @Phantom711

The use if the section is optional, any setting outside of a section (beginning of the file) will apply to all runtime/apps.

To use sections, refer to https://github.com/mbucchia/Quad-Views-Foveated/wiki/Advanced-Configuration#general-notes

• Sections with the syntax [<string>] are matched against the OpenXR runtime name. Use the log file (see Troubleshooting) and search for string Using OpenXR runtime: to find the name of your runtime. Only matching one word is sufficient, for example if your OpenXR runtime is "Varjo OpenXR Runtime 3.10.1" then using the section name [Varjo] is sufficient.

I don't recall the runtime name for VDXR, but you can look it up the log file as explained. I think it's [VirtualDesktopXR].

[Qcumber]

4 hours ago, Jive said:

I have VD running DCS really nicely at the moment so I shouldn't really mess with it but I'm curious if anyone knows where QuadViews takes it's config info from for VD? 

I made my QV adjustments in the companion app with a pretty aggressive 5% render in the non-foveated region which appears to be the case with Link. For example if I take a screenshot the image is super blurred. When I do the same in VD the image is maybe 25-30% res instead so it seems that it's maybe taking stock config info, which again actually plays really nice but you know, tinkering. 

@mbucchia am I way off or is it a different config file? 

I just use a generic config file and adjust it as needed for VD or meta. It keeps it simple. I can post it here if that helps. 

[Jive]

2 hours ago, Qcumber said:

I just use a generic config file and adjust it as needed for VD or meta. It keeps it simple. I can post it here if that helps. 

Yes please, thanks!

[VR Flight Guy in PJ Pants]

5 hours ago, mbucchia said:

@Jive @Phantom711

The use if the section is optional, any setting outside of a section (beginning of the file) will apply to all runtime/apps.

To use sections, refer to https://github.com/mbucchia/Quad-Views-Foveated/wiki/Advanced-Configuration#general-notes

• Sections with the syntax [<string>] are matched against the OpenXR runtime name. Use the log file (see Troubleshooting) and search for string Using OpenXR runtime: to find the name of your runtime. Only matching one word is sufficient, for example if your OpenXR runtime is "Varjo OpenXR Runtime 3.10.1" then using the section name [Varjo] is sufficient.

I don't recall the runtime name for VDXR, but you can look it up the log file as explained. I think it's [VirtualDesktopXR].

From the log:

Using OpenXR runtime: VirtualDesktopXR 1.0.5

[Qcumber]

22 hours ago, Jive said:

Yes please, thanks!

Sorry for the delay

 

settings.cfg