slughead

They were probably already committed to a timeline and may not have been able to fix it in time or had the resources available.

I've taken my own steps and moved to Virtual Desktop.

Under C:\Program Files\Oculus there is a Staging and sometimes a tmp folder. Rename the Staging folder to Staging.bak Rename the tmp folder to tmp.bak Create a new file called Staging (you can create a new txt file called Staging.txt, then rename it to Staging) Create a new file called tmp. By creating files to replace the folders, the Oculus updater can no longer copy the download file to the staging folder because it's now a file. Hence, this blocks your Oculus / Meta Link application from being updated. Reverse the changes to allow updates again. This only stops the app on the PC from being updated. It doesn't stop the headset OS update from happening (which "could" be incompatible with the PC app should the versions not match). I also make a copy of a good working Oculus folder, e.g., Oculus to Oculus.v67, so I can quickly revert if necessary.

I think you’d be best to ask this on the VD discord which is their support forum. Then you’ll get answers from the VD team.

If you are using OpenXR Toolkit, Quad View Foveated Rendering, HTCC, or any third-party OpenXR layer tool, disable them. They're not compatible with Meta Link v68 anymore due to Meta's changes. If you want to keep using those tools, switch to the Virtual Desktop app, which uses its own VDxR link instead of Meta Link.

If you are using OpenXR Toolkit, Quad View Foveated Rendering, HTCC, or any third-party OpenXR layer tool, disable them. They're not compatible with Meta Link v68 anymore due to Meta's changes. If you want to keep using those tools, switch to the Virtual Desktop app, which uses its own VDxR link instead of Meta Link.

Yes, as my current home's Wi-Fi is a mesh network. So, I purchased a dedicated router. It's a TP-Link BE9300. Overkill, overpriced. You can get much cheaper routers that will do the job well, I am told. The list provided by VD is here: • Discord | #general-support | Virtual Desktop I also use these battery packs to keep my headset charged. I put them in a shirt or jeans pocket. Running without a cable is freedom. INIU Power Bank, 20000mAh Fast Charging Portable Charger, 22.5W Powerbank with USB C Input & Output, Battery Pack PD3.0 QC4.0 for iPhone 15 14 13 12 11 Pro Max Mini Plus Samsung S22 S21 S20 iPad etc : Amazon.co.uk: Electronics & Photo

There is a fixation on the bit rate. Yet, unless you compare with the same codec, the bit rate is somewhat meaningless as the newer codecs that VD can support, which Meta Link doesn't require a far lower bit rate to achieve the same compression. So far, I'm happy with the visuals and performance I get with VD. Each to their own though, but do consider codec when discussing bitrate. It is very much apples and pears otherwise.

Not a lot really. Just follow the instructions here: • Discord | #start-here | Virtual Desktop and here: Home · mbucchia/Quad-Views-Foveated Wiki · GitHub However, I stopped using QVFR a while ago as I found it more of a CPU hog over cities and caused more ASW. I did try it again with VD, but I found it caused the clouds to become pixelated, so I turned it off once again.

If you use any other OpenXR layers, such as QVFR or HTCC, they are also affected and likely to be causing the crash. You can use the OpenXR Toolkit and all the other OpenXR tools generated by mbucchia and Fred (HTCC, Openkneeboard) with VD.

Absolutely.

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

That's understandable. Stay safe.

That should be the case.

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 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.

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

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.

I haven't experienced this. I would try the following: Play some headset-only games to eliminate a problem with the headset itself - this may not necessarily be enough to cause the problem. Use the DCS VR preset to reduce the load on the system as much as possible. Reset the Oculus Link to default settings. 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.

Maybe not enough. Try electrical insulation tape. You may need a few layers to block the infra-red.

Stick some tape over the sensor. That should allow you to run the headset without it on your head. Phantom711 is correct regarding local dimming. This is only applicable to the headset display panels. It cannot be shown to work via a scene recording; the image on the physical display panel must be recorded to demonstrate local dimming. Local dimming should be the same whether VD or Quest Link enables it. It should just turn on or off in the headset. Neither VD nor Quest Link will do any special processing on the image. Thus, there would be no difference in contrast, colours, etc., just light bleed around bright objects. Any difference in colour, contrast, etc., is due to something else.

i9-13900K, 4090, 64GB DDR5, Gigabyte Z790, NVMEs, SSD, Quest Pro. I was having fun and games yesterday. DCS was performing incredibly badly, even over Link. It turned out that, somehow, the Intel Defaults had been set in my BIOS. Something crazy must have happened to my machine. It took me a little while to work that out. Just a quick check in the task manager's performance tab to watch the CPU running at 2GHz instead of about 5GHz was the final giveaway. I stopped using QVFR a while ago as it zaps performance over dense cities. So, with my rig, there isn't really anything to be gained as it is powerful enough to maintain 72fps most of the time. I mostly use OXRTK for stats, although I will probably disable that, too, as I'm not always going to be looking at stats, and it's just another thing eating CPU cycles. I have hand tracking on in VD. It seems to work well in both VD and DCS. As you say, without it enabled, there is no hand tracking at all in DCS with HTCC. 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.

Here's where I am with VD.... it just works. Godlike with PD of 1.0 in DCS is about the same visuals I was getting with Meta Link set to x1 and DCS PD at 1.4 ish. These give me a reasonably locked 72fps with all settings maxed out. @gonvise you must have many settings dialled down to be running with a PD of 1.8/2.0 or are you running with ASW always enabled? It would be interesting to see your DCS config. One weird thing I noticed is that if I have QVFR enabled, the clouds look blocky or pixelated. Yuck! Despite what setting I chose in the config they were always pixelated. So I've turned it off again.

Are you comparing the same encoder on VD and Link? Also, remember that different encoders can run at lower bitrates and generate the same quality. So, if the two use different encoders, trying to run at the same bitrate isn't a valid comparison.

That’s my plan. Just have a lot going on at the moment which is frustrating.