Matching Quest 3 Link to Virtual Desktop resolution / look (+ other issues). Help wanted!

[RafaPolit]

Good evening friends.

I have been playing VR for a while now, always using Virtual Desktop for the Quest 3.  Up until recently, this worked really nice, but as of 5 days ago I get screen freezes on the Headset (while the game inside the PC still runs perfectly normal).

I'm trying to resolve the issue with VD support, but it is coming slow (read here, almost no replies or help whatsoever).

In the meantime, I have been trying to switch to Cable Link for a "better" experience... and it has proven all but smooth (or working at all!).

I've seen many videos on the subject, each broadcaster claiming better results than the other and almost all giving contradicting advice, so it's hard to have some solid feedback.

Here are my goals and where I'm failing:

1. Resolution

I have DCS VR multiplier set to 1, I would like to first stablish my base resolution.  With VD I set it to Ultra (I used Godlike before), and the in-game sharpness / resolution is UNMATCHED by anything I can setup in Meta Quest Link + OculusDebugTool with even slower framerates.

What would be the equivalent resolution to VD "Ultra" on Meta Quest Link?  As a side note, Meta Quest Link appears to be working, for some reason changing the values on the OculusDebugTool.exe (which I'm sure worked at some point), now seem to take no effect.  I'm running it as admin and restarting the service after changing values, but I have been unable to make changes from the tool.  Oculus Tray Tool seems really old and not updated, plus it says has issues with W11... is anyone still using this? What are my alternatives?

2. Weird "frame ghosting" effect

With Quest Link cable connected, I have an issue where, at one point during the first few minutes of streaming the game, one or both eyes would enter a "laggy" status.  It kind of looks that the frames render 2 or 3 at a time and they are all presented simultaneously.  So, if I move my head kind of quickly, a particular know will actually show itself in three consecutive locations simultaneously.... but FPS seems to be 3 times slower, although the metrics don't show this condition as true.

The weird thing is that, when I thig bug finally occurs, if I close the game and return to the "grid world" of the Quest Link software, I STILL have that issue on the eye (or eyes) where this phenomenon was present during game.  It is never triggered outside the game, but it survives the game closing and it perdures as long as I don't close the Quest Link app on the headset.  As soon as I do, and I return to the app, movement is "smooth" until I get back into the game and into a plane, and the problem begins anew.

Maybe this is sliced encoding, or something similar... I believe I have reprojection disabled, but, again, I have this feeling that OculusDebugTool is not having any effect, so I would like some pointers to help figure that out as well.

 

These are my two main problems at this point, I'd appreciate all the help I can get, or pointers to where to read or videos to watch.

Thanks in advance, best regards,

Rafa.

 

[Phantom711]

Still using Oculus Tray Tool, but Ivam also still on Win10.

Here are my settings:

Please note, that I have a Quest Pro, but it should be the same for the most part. Except for Encode Resolution…but opinions on that vary widely. 

I‘ve never had a problem with cabled link.
 

Two questions though:

1. Are you using the official cable or an aftermarket one? Did it pass the speedtest alright?

2. Just in case you ever experimented with the Meta Airlink at some point…make sure in the Oculus Link Launch window, you have „cabled link“ selected.

Edited June 3, 2024 by Phantom711

[kablamoman]

1 hour ago, RafaPolit said:

Good evening friends.

I have been playing VR for a while now, always using Virtual Desktop for the Quest 3.  Up until recently, this worked really nice, but as of 5 days ago I get screen freezes on the Headset (while the game inside the PC still runs perfectly normal).

I'm trying to resolve the issue with VD support, but it is coming slow (read here, almost no replies or help whatsoever).

In the meantime, I have been trying to switch to Cable Link for a "better" experience... and it has proven all but smooth (or working at all!).

I've seen many videos on the subject, each broadcaster claiming better results than the other and almost all giving contradicting advice, so it's hard to have some solid feedback.

Here are my goals and where I'm failing:

1. Resolution

I have DCS VR multiplier set to 1, I would like to first stablish my base resolution.  With VD I set it to Ultra (I used Godlike before), and the in-game sharpness / resolution is UNMATCHED by anything I can setup in Meta Quest Link + OculusDebugTool with even slower framerates.

What would be the equivalent resolution to VD "Ultra" on Meta Quest Link?  As a side note, Meta Quest Link appears to be working, for some reason changing the values on the OculusDebugTool.exe (which I'm sure worked at some point), now seem to take no effect.  I'm running it as admin and restarting the service after changing values, but I have been unable to make changes from the tool.  Oculus Tray Tool seems really old and not updated, plus it says has issues with W11... is anyone still using this? What are my alternatives?

2. Weird "frame ghosting" effect

With Quest Link cable connected, I have an issue where, at one point during the first few minutes of streaming the game, one or both eyes would enter a "laggy" status.  It kind of looks that the frames render 2 or 3 at a time and they are all presented simultaneously.  So, if I move my head kind of quickly, a particular know will actually show itself in three consecutive locations simultaneously.... but FPS seems to be 3 times slower, although the metrics don't show this condition as true.

The weird thing is that, when I thig bug finally occurs, if I close the game and return to the "grid world" of the Quest Link software, I STILL have that issue on the eye (or eyes) where this phenomenon was present during game.  It is never triggered outside the game, but it survives the game closing and it perdures as long as I don't close the Quest Link app on the headset.  As soon as I do, and I return to the app, movement is "smooth" until I get back into the game and into a plane, and the problem begins anew.

Maybe this is sliced encoding, or something similar... I believe I have reprojection disabled, but, again, I have this feeling that OculusDebugTool is not having any effect, so I would like some pointers to help figure that out as well.

 

These are my two main problems at this point, I'd appreciate all the help I can get, or pointers to where to read or videos to watch.

Thanks in advance, best regards,

Rafa.

 

Have you tried asking for help on the Virtual Desktop discord? This is their primary means of providing support.

With regards to your first question:

Quest 2/Pico Neo 3/Quest Pro/Quest 3
Potato: 1440x1536
Low: 1728x1824
Medium: 2016x2112
High: 2496x2592
Ultra: 2688x2784
Godlike: 3072x3216 (Quest Pro/Quest 3)

I'm not much help for the second question, as I have yet to use the link cable myself.

There is a new beta version of Virtual Desktop and the streamer app -- perhaps they are worth a try?

[RafaPolit]

12 minutes ago, kablamoman said:

Have you tried asking for help on the Virtual Desktop discord? This is their primary means of providing support.

...

There is a new beta version of Virtual Desktop and the streamer app -- perhaps they are worth a try?

Thanks! Yeah, I'm in contact with them regarding the problems with VD, I just wanted to mention this here to avoid suggestions like: "just use VD!", which I would agree myself, but it's "a work in progress".  They are replying in the support discord for the Beta version (which is the one I'm using), but veeeeerrrrrryyyyy slowly.  Thanks for the resolutions.

[RafaPolit]

49 minutes ago, Phantom711 said:

Still using Oculus Tray Tool, but Ivam also still on Win10.

Here are my settings:

Please note, that I have a Quest Pro, but it should be the same for the most part. Except for Encode Resolution…but opinions on that vary widely. 

I‘ve never had a problem with cabled link.
 

Two questions though:

1. Are you using the official cable or an aftermarket one? Did it pass the speedtest alright?

2. Just in case you ever experimented with the Meta Airlink at some point…make sure in the Oculus Link Launch window, you have „cabled link“ selected.

 

These help, thanks a lot.

I'll first need to ensure that my changes in the Oculus Debug Tool are actually making changes at all, as yesterday I set up the FOV to 0.3 x 0.3 and still could see the entire screen of FOV.  So something is not right.

After that, I'll look into the settings, albeit some of them are "not possible" in the Debug Tool, mainly that Encode Resolution.

As to your questions:

1. Yes, official cable, I get 2.4 on the speed test, so yeah, perfectly fine (I think! )
2. That is a good hint, no idea where in the Launch window will that reside, but I'll make sure.  I know I did try the Quest Air Link at one point, but quickly moved away from it.

 

Another annoyance I have is that the PC never detects the Quest 3 if I attach the cable to the Quest while already connected to the PC.  For some inexplicable reason, it only works when I have it previously attached to the headset and I connect the PC end afterwards.  I makes no sense to me and sounds more like Voodoo than it does science, but it's perfectly consistent for me.  No idea why, but makes it hard to go fishing behind the PC every time I want to connect the headset.

Thanks again for the feedback, I'll keep on reporting my progresses (or lack of in this case )

[Phantom711]

vor 7 Minuten schrieb RafaPolit:

That is a good hint, no idea where in the Launch window will that reside, but I'll make sure.

When you click on „Quest Link“ and then the little window opens up, where it still says something like „Rift S“ and there is the blue „Launch“ button at the bottom…on the top of that window you can/have to cycle between cabled link and Airlink.

For the FOV…don‘t forget to press the SAVE button to the right of it before launching the Meta PC App/starting Quest Link. For some of the functions, OTT possibly needs to remain running in the background.

Edited June 3, 2024 by Phantom711

[RafaPolit]

Thanks, found the "Use Air Link", it's disabled, yes.

I don't have OTT, I'm using the Debug tool, as OTT says it has problems with W11.

But I think that I can, at least, confirm I have a valid configuration system as I can modify the FOV and present the HUD overlay, etc.

I'm going to run the Pixel multiplier from the Oculus App (with the slider) putting it a 70Hz and 1.2x which gives, roughly, the same resolution that kablaboman reported earlier.

[Phantom711]

And maybe don‘t even fiddle around with ODT or OTT yet, until you have solved your stability issue in the first place.

If you used OpenXR Toolkit Companion, you might want to temporarily disable that as well.

[av8orDave]

2 hours ago, RafaPolit said:

Good evening friends.

I have been playing VR for a while now, always using Virtual Desktop for the Quest 3.  Up until recently, this worked really nice, but as of 5 days ago I get screen freezes on the Headset (while the game inside the PC still runs perfectly normal).

I'm trying to resolve the issue with VD support, but it is coming slow (read here, almost no replies or help whatsoever).

In the meantime, I have been trying to switch to Cable Link for a "better" experience... and it has proven all but smooth (or working at all!).

I've seen many videos on the subject, each broadcaster claiming better results than the other and almost all giving contradicting advice, so it's hard to have some solid feedback.

Here are my goals and where I'm failing:

1. Resolution

I have DCS VR multiplier set to 1, I would like to first stablish my base resolution.  With VD I set it to Ultra (I used Godlike before), and the in-game sharpness / resolution is UNMATCHED by anything I can setup in Meta Quest Link + OculusDebugTool with even slower framerates.

What would be the equivalent resolution to VD "Ultra" on Meta Quest Link?  As a side note, Meta Quest Link appears to be working, for some reason changing the values on the OculusDebugTool.exe (which I'm sure worked at some point), now seem to take no effect.  I'm running it as admin and restarting the service after changing values, but I have been unable to make changes from the tool.  Oculus Tray Tool seems really old and not updated, plus it says has issues with W11... is anyone still using this? What are my alternatives?

2. Weird "frame ghosting" effect

With Quest Link cable connected, I have an issue where, at one point during the first few minutes of streaming the game, one or both eyes would enter a "laggy" status.  It kind of looks that the frames render 2 or 3 at a time and they are all presented simultaneously.  So, if I move my head kind of quickly, a particular know will actually show itself in three consecutive locations simultaneously.... but FPS seems to be 3 times slower, although the metrics don't show this condition as true.

The weird thing is that, when I thig bug finally occurs, if I close the game and return to the "grid world" of the Quest Link software, I STILL have that issue on the eye (or eyes) where this phenomenon was present during game.  It is never triggered outside the game, but it survives the game closing and it perdures as long as I don't close the Quest Link app on the headset.  As soon as I do, and I return to the app, movement is "smooth" until I get back into the game and into a plane, and the problem begins anew.

Maybe this is sliced encoding, or something similar... I believe I have reprojection disabled, but, again, I have this feeling that OculusDebugTool is not having any effect, so I would like some pointers to help figure that out as well.

 

These are my two main problems at this point, I'd appreciate all the help I can get, or pointers to where to read or videos to watch.

Thanks in advance, best regards,

Rafa.

 

Some anecdotal stuff from someone who uses both Quest Link and Virtual Desktop and still can't decide which is better:

- If you're using OculusDebugTool, it doesn't seem to save the pixel density / supersampling settings. You have to change it (for example to 1.3) and then leave the ODT program open while playing DCS, then repeat the next time you start your computer or after you close the ODT software.

- I've found that to get a true "like-for-like" comparison, you have to use the same pixel density settings in both program. For example, if you were to use a pixel density of 1.3 in OculusDebugTool with Quest Link, you'd need to dial the DCS pixel density in the VR settings tab up to 1.3 when using Virtual Desktop (even if using "godlike" mode). 

- I'll note that Quest Link seems to have started defaulting to having reprojection on even if you disable it. I say this because sometime around the last update of the Meta software, when stressed, DCS framerates started going from 72 fps straight to 36 fps, even after hitting "Ctrl-1" to disable reprojection/ASW. It used to just drop to whatever framerate was sustainable... now it is straight to 50% of the refresh rate as with reprojection. 

- I currently think that Virtual Desktop is the better solution, but I'm honestly not totally sure.

Probably not much help, but my 2 cents. Good luck sorting it out. I hope for the day where VR hardware / software seamlessly integrates into games, and where it can handle the game at reasonable framerates without jumping through hoops.

[RafaPolit]

Thanks, actually all these help a lot.  Maybe I am playing with too many variables.  It may be a good idea to remove some moving parts.  I disabled OXRTC, it seems to get a little more jerky.  Also, What I would IDEALLY want is to have all settings "identical" in OXRTC and DCS so as to "swap" between VD and Link, and just adjust the parameters locally on the others.  That way, I only need to remember "two sets of settings".  One for VD and one for Link, and not a combination of: when in VD then OXRTC with these values and DCS with these others, but when on Link I have to change this and that here and there.

So, it's looking a bit better at this point, which is fantastic. Thanks so much for the help.

Quick additional question:
Pixel Density (ODT) vs Render Resolution (in Link app)... are they the same? Should I set BOTH? Do you prefer to tinker in one over the other?  As I see it PD seems to be doing some oversampling while keeping the resolution, but I may be wrong? Thanks for any insight.

[RafaPolit]

These are the settings that are, currently, working decently good:

 

I have a Ryzen 5900X, 3080Ti, and 64GB of DDR4, DCS running on dedicated NVME.
I'm still tweaking things, so, if you have suggestions, counter ideas, anything, all is welcome.

[Phantom711]

vor 52 Minuten schrieb RafaPolit:

Pixel Density (ODT) vs Render Resolution (in Link app)... are they the same? Should I set BOTH? Do you prefer to tinker in one over the other?  As I see it PD seems to be doing some oversampling while keeping the resolution, but I may be wrong?

They all do the same thing, but will get multiplied with one another. So for a start it might help to leave all at 1.0 and only manipulate one of them. It does no harm to change them, as long as you know, what you are doing. (Not sure actually, if the OTT/ODT settings just override the Meta App settings or also multiply, which I would guess)

I would avoid contradictory settings though…like 0.8 in the Meta App and then PD 1.2 in DCS. Again, it shouldn‘t do any harm…it‘s just pointless…

I have the Meta App set to 1.3 (max), but since I want more, I have the PD in DCS set to another 1.3 or so (That‘s with a 4090 though and DFR on the QPro).

Edited June 3, 2024 by Phantom711

[RafaPolit]

Thanks, yeah, makes sense.

I was thinking the same thing, but 1.3 on the ODT gave me just a tad under-resolution to what I'm used to in VD in ultra with whatever sharpening algorithms they use.  Running 1.2 and 1.2 on both gave me closer to what I am used to and it's starting to "saturate" the max 72Fps.

If I put 1.3 x 1.3 I'm probably going to start a fire either inside my PC or in my eyes, so I'd probably avoid that.

[RafaPolit]

This seems to be the sweet spot for me at this point, having the Link app at 1.0x:

 

I have two items that I am on the fence about:
- Any advice on Sliced Encoding?
- Any advice on Adaptive GPU Performance Scale?

Other than those, I am more or less happy with this and having DCS with DLSS Quality.  This matches my VD settings, which I am happy about.  Some planes / helos can do without DLSS and only DLAA, the Apache is particularly harsh and I can even go for DLSS Performance.  So I have that setting to play with.

Seems like a good balance.  I really like to thank you guys for providing guidance and feedback.  Best regards,

Rafa.

[Phantom711]

vor 10 Stunden schrieb RafaPolit:

Any advice on Sliced Encoding?

Not sure, but I believe it is for Airlink only...but I´ve never heard anyone mention it as a cool feature or something.

 

vor 10 Stunden schrieb RafaPolit:

Any advice on Adaptive GPU Performance Scale?

I think this would dynamically adjust the resolution. I don´t know if this works at all though. And I doubt that it would look nice.

[Qcumber]

On 6/3/2024 at 7:14 PM, RafaPolit said:

Good evening friends.

I have been playing VR for a while now, always using Virtual Desktop for the Quest 3.  Up until recently, this worked really nice, but as of 5 days ago I get screen freezes on the Headset (while the game inside the PC still runs perfectly normal).

Switching between VD and quest link causes the freezing issue for me. I found that clearing the FXO shaders helps. 

In terms of general VR performance keep things as simple as possible. In terms of VR make sure you have the correct router setup and adjust bitrate so that the latencies are all white. 

I prefer oculus link cable as it has slightly better quality due to pushing the bitrate to 960 Mbps. Also ASW is better than VD SSW. 

As has been said above keep super sampling in one place. In VD use godlike. In oculus push the slider to the far right for full resolution (about 2700) then add about 1.15 in ODT to push it to around 3100 pixels. Use 72 Hz settings on both. 

If you do use OXRTK then disable turbo mode. This can cause crashes with oculus link. 

[Reflected]

On 6/4/2024 at 2:14 AM, RafaPolit said:

Good evening friends.

I have been playing VR for a while now, always using Virtual Desktop for the Quest 3.  Up until recently, this worked really nice, but as of 5 days ago I get screen freezes on the Headset (while the game inside the PC still runs perfectly normal).

I'm trying to resolve the issue with VD support, but it is coming slow (read here, almost no replies or help whatsoever).

In the meantime, I have been trying to switch to Cable Link for a "better" experience... and it has proven all but smooth (or working at all!).

I've seen many videos on the subject, each broadcaster claiming better results than the other and almost all giving contradicting advice, so it's hard to have some solid feedback.

Here are my goals and where I'm failing:

1. Resolution

I have DCS VR multiplier set to 1, I would like to first stablish my base resolution.  With VD I set it to Ultra (I used Godlike before), and the in-game sharpness / resolution is UNMATCHED by anything I can setup in Meta Quest Link + OculusDebugTool with even slower framerates.

What would be the equivalent resolution to VD "Ultra" on Meta Quest Link?  As a side note, Meta Quest Link appears to be working, for some reason changing the values on the OculusDebugTool.exe (which I'm sure worked at some point), now seem to take no effect.  I'm running it as admin and restarting the service after changing values, but I have been unable to make changes from the tool.  Oculus Tray Tool seems really old and not updated, plus it says has issues with W11... is anyone still using this? What are my alternatives?

2. Weird "frame ghosting" effect

With Quest Link cable connected, I have an issue where, at one point during the first few minutes of streaming the game, one or both eyes would enter a "laggy" status.  It kind of looks that the frames render 2 or 3 at a time and they are all presented simultaneously.  So, if I move my head kind of quickly, a particular know will actually show itself in three consecutive locations simultaneously.... but FPS seems to be 3 times slower, although the metrics don't show this condition as true.

The weird thing is that, when I thig bug finally occurs, if I close the game and return to the "grid world" of the Quest Link software, I STILL have that issue on the eye (or eyes) where this phenomenon was present during game.  It is never triggered outside the game, but it survives the game closing and it perdures as long as I don't close the Quest Link app on the headset.  As soon as I do, and I return to the app, movement is "smooth" until I get back into the game and into a plane, and the problem begins anew.

Maybe this is sliced encoding, or something similar... I believe I have reprojection disabled, but, again, I have this feeling that OculusDebugTool is not having any effect, so I would like some pointers to help figure that out as well.

 

These are my two main problems at this point, I'd appreciate all the help I can get, or pointers to where to read or videos to watch.

Thanks in advance, best regards,

Rafa.

 

I'm having the same pixelating bug. Have you found a solution?

[ischicopter]

There is currently no way to make Oculus link, Airlink, ALVR or Steamlink look as good as VD.

Period.

 

[Qcumber]

2 hours ago, ischicopter said:

There is currently no way to make Oculus link, Airlink, ALVR or Steamlink look as good as VD.

Period.

 

I would disagree. I've used both VD and link cable and the quality is comparable. 

[diego999]

6 hours ago, ischicopter said:

There is currently no way to make Oculus link, Airlink, ALVR or Steamlink look as good as VD.

Period.

 

 

For me it was the opposite. Link offers the best quality, with VD as a close second but just not the same. Airlink is noticeable worse than the other two.

 

 

[ischicopter]

You are both wrong. Just compare the maximum encoder resolutions between link and VD.

keep in mind: encoder res is not the same as render res. They both need to match for best quality. Simply not possible with link. Cable Or not.

Also link has no AV1 encoding, no foveated encoding, no headset-based reprojection; it eats up your PC’s ressources instead.

It is inferior in all possible ways. I am not sponsored btw . 
 

I should add: it doesn’t matter what your experience was when the facts are against you.

You probably had a bad setup and/or wrong settings.

 

[RafaPolit]

On 1/18/2025 at 9:57 PM, Reflected said:

I'm having the same pixelating bug. Have you found a solution?

Sorry for the late reply.  I have almost given up on VD completely, and mostly due to DCS incompatibility.  It simply works perfect for X amount of minutes, and then, all of a sudden, it freezes in one frame and cannot be recovered.  The game on the desktop monitor is still playing, even recognizing the headset movement, but on the headset the frame is stuck.  Looks like an encoding bug or problem. Closing VD on the Quest3 simply brakes the bond between VD desktop and headset, if you reopen it you will get a black screen.  VDs solution is to set game "Boost game priority", and it fixes the issue, but it than creates stutters every few seconds, which are really anoying.

So, I'm back to using Cable Link and have found a few solutions and few problems that can be helped:

- I run the resolution in OculusDebugTool.exe at 1 and configure DCS to have 1.3 pixel density.  Going the other way around has less performance for me
- I have put some fixed foveated rendering on OpenXR Toolkit
 

Problem:

- Every now and then, the Link software starts missreporting the headset movement, or gets "laggy" or "jumpy".  Let me explain: it's the behavior described above as #2.  What I believe is happening is that the headset is not reporting "fluid" movements like X position 1 -> 2 -> 3 -> 4 in a 4 second interval, but reports 1 -> 2 -> 1 -> 3 -> 2 -> 4.  Something like that. So it appears as if I were shaking my head with twitches instead of fluent movements.  Even if I close the game, this keeps happening in the link home screen (the one in the white infinite grid).

Solution:

- I have found that if I double-tap myself out of the Quest game and into passthrough mode and quickly double-tap myself in, this problem is resolved and I get fluent movement once more.  

I found this out by chance, since I had to stop the jerkiness as I was getting sick, and when I returned to the game it was fixed.

It's a pain to do it and brakes immersion, but beats by a mile the alternative with VD to simply close the game and lose all the progress made.

 

By the way, all this I'm describing is exclusively playing your and Baltic's campaigns, so it's a privilege to interact with you as you are my source of entertaining in this game.  Thanks a lot!

 

Best regards,

Rafa.

Edited January 31 by RafaPolit

[david_joe]

8小时前，RafaPolit说：

Sorry for the late reply.  I have almost given up on VD completely, and mostly due to DCS incompatibility.  It simply works perfect for X amount of minutes, and then, all of a sudden, it freezes in one frame and cannot be recovered.  The game on the desktop monitor is still playing, even recognizing the headset movement, but on the headset the frame is stuck.  Looks like an encoding bug or problem. Closing VD on the Quest3 simply brakes the bond between VD desktop and headset, if you reopen it you will get a black screen.  VDs solution is to set game "Boost game priority", and it fixes the issue, but it than creates stutters every few seconds, which are really anoying.

So, I'm back to using Cable Link and have found a few solutions and few problems that can be helped:

- I run the resolution in OculusDebugTool.exe at 1 and configure DCS to have 1.3 pixel density.  Going the other way around has less performance for me
- I have put some fixed foveated rendering on OpenXR Toolkit
 

Problem:

- Every now and then, the Link software starts missreporting the headset movement, or gets "laggy" or "jumpy".  Let me explain: it's the behavior described above as #2.  What I believe is happening is that the headset is not reporting "fluid" movements like X position 1 -> 2 -> 3 -> 4 in a 4 second interval, but reports 1 -> 2 -> 1 -> 3 -> 2 -> 4.  Something like that. So it appears as if I were shaking my head with twitches instead of fluent movements.  Even if I close the game, this keeps happening in the link home screen (the one in the white infinite grid).

Solution:

- I have found that if I double-tap myself out of the Quest game and into passthrough mode and quickly double-tap myself in, this problem is resolved and I get fluent movement once more.  

I found this out by chance, since I had to stop the jerkiness as I was getting sick, and when I returned to the game it was fixed.

It's a pain to do it and brakes immersion, but beats by a mile the alternative with VD to simply close the game and lose all the progress made.

 

By the way, all this I'm describing is exclusively playing your and Baltic's campaigns, so it's a privilege to interact with you as you are my source of entertaining in this game.  Thanks a lot!

 

Best regards,

Rafa.

I have a similar problem. VD uses Av1 encoding and the screen freezes from time to time. Please switch to HEVC 10bit.
After updating the new version of the driver yesterday. 572.16 I encountered stuttering. The VR screen stutters intermittently within a few minutes. I am looking for a solution.

[Reflected]

15 hours ago, RafaPolit said:

Sorry for the late reply.  I have almost given up on VD completely, and mostly due to DCS incompatibility.  It simply works perfect for X amount of minutes, and then, all of a sudden, it freezes in one frame and cannot be recovered.  The game on the desktop monitor is still playing, even recognizing the headset movement, but on the headset the frame is stuck.  Looks like an encoding bug or problem. Closing VD on the Quest3 simply brakes the bond between VD desktop and headset, if you reopen it you will get a black screen.  VDs solution is to set game "Boost game priority", and it fixes the issue, but it than creates stutters every few seconds, which are really anoying.

So, I'm back to using Cable Link and have found a few solutions and few problems that can be helped:

- I run the resolution in OculusDebugTool.exe at 1 and configure DCS to have 1.3 pixel density.  Going the other way around has less performance for me
- I have put some fixed foveated rendering on OpenXR Toolkit
 

Problem:

- Every now and then, the Link software starts missreporting the headset movement, or gets "laggy" or "jumpy".  Let me explain: it's the behavior described above as #2.  What I believe is happening is that the headset is not reporting "fluid" movements like X position 1 -> 2 -> 3 -> 4 in a 4 second interval, but reports 1 -> 2 -> 1 -> 3 -> 2 -> 4.  Something like that. So it appears as if I were shaking my head with twitches instead of fluent movements.  Even if I close the game, this keeps happening in the link home screen (the one in the white infinite grid).

Solution:

- I have found that if I double-tap myself out of the Quest game and into passthrough mode and quickly double-tap myself in, this problem is resolved and I get fluent movement once more.  

I found this out by chance, since I had to stop the jerkiness as I was getting sick, and when I returned to the game it was fixed.

It's a pain to do it and brakes immersion, but beats by a mile the alternative with VD to simply close the game and lose all the progress made.

 

By the way, all this I'm describing is exclusively playing your and Baltic's campaigns, so it's a privilege to interact with you as you are my source of entertaining in this game.  Thanks a lot!

 

Best regards,

Rafa.

Thanks! Can you tell me how to 'double tap'? I have no idea what that means

[beastfang]

2024/6/4 AM2点14分，RafaPolit说：

Good evening friends.

I have been playing VR for a while now, always using Virtual Desktop for the Quest 3.  Up until recently, this worked really nice, but as of 5 days ago I get screen freezes on the Headset (while the game inside the PC still runs perfectly normal).

 

I have encountered this problem several times, and it was solved by restarting the computer and quest3

This is my setup, hope it helps

nullnull