Qcumber

Yes. 572.16. I'm guessing regarding the VRAM. Just speculating on possibilities. It sounds like that might not be the issue.

I got a powered usb/ethernet lead from Amazon. Not very expensive. About £17. https://amzn.eu/d/2WCOh7y

Schoolboy error

Try Meta without any of the link sharpening and see how it compares to VD.

Thanks. I'll try reducing textures.

I keep getting crashes with J too. For me it seems to happen when GPU and VRAM are maxed out in VR.

1000mbps vs 1200 or 2400mbps is meaningless when the actual encoding is 400-500mbps. The min requirements for a stable VD connection is about 860mbps from the router IIRC.

Are you using "standard" sharpening in meta link? If so turn this off and apply equal sharpening from elsewhere for a more direct comparison between meta and VD.

I thought I had resolved it. I did a complete repair if DCS and deleted all extra files. Factory reset of the headset. Manually replaced default nvngx_dlss.dll from 3.7 to 310.2. Reinstalled NVPI (revamped). Set preset to K. Everything worked fine for several.hours of testing with a max test time of about 20 mins. No CDTs. Then I tried flying in the F4 from a busy airport hot start. Maxed out GPU and VRAM and CDT. I've not had chance to rest much further but I suspect for me it's some form of VRAM overflow (pure speculation at this stage). I need to do more testing but am away for a few days.

Do you get any ghosting if AA is off?

DLSS is not enough of an "upgrade" at the moment. It gives me similar performance to using MSAAx2. The only real benefit for me is better AA. I am going to wait and see what the new AMD GPUs are like. Raw rasterisation performance over clever software. And see if DLSS improves.

I have been considering a 5080 or 5070ti but will wait for a) comparison reviews (3 weeks) and b) availability at MSRP (6 months!?).

Interesting. I'll do some more testing. I wonder how the 50xx handles this. This is still early for DLSS4 so maybe it will improve for lower range GPUs.

What is your refresh rate and FPS? Are you using reprojection?

VD have issued a statement on Discord: "**__Quest v74 PTC (Public Test Channel) has performance issues with Virtual Desktop, stay off the PTC__** @everyone Sorry for the ping, but we’ve had lots of reports of performance issues on the Quest v74 PTC, so make sure to opt out in the Meta Horizon phone app. If you are already on v74, opt out and then perform a factory reset to go back to v72. See below for instructions:" https://discord.com/channels/564087419918483486/592909523295928340/1333466101119455333

I still see all the artifacts with DLAA. For me using DLAA has a bigger performance hit than using MSAA. Preset J and K. I am using 310.2 and latest NVIDIA driver. I am also getting occasional CTDs with DLAA/DLSS. It appears to be when I get max GPU/VRAM use. Possibly VRAM overflow!?

Ghosting is even worse against the ground.

Yes, DLSS4 is a major step but there are some horrendous artifacts. The ghosting of planes against the ground is very bad. A stream if blurring. Spotting dots are hazy and the contrast of some objects against some backgrounds (particularly clouds) makes them difficult to see. For me the performance gain in VR with QVFR is negligible for DLSS performance compared to using MSAAx2. It does not feel like I suddenly have a 4080 or 4090. It still feels like I am using a 4070.

When you say "full resolution in Quest" do you mean the slider in the app is pushed to the right? What size of centre Res are you using? A peripheral resolution of 0.2 sounds very low. Does it not look very pixelated?

This has been discussed a lot on the VD Discord. From what I understand, the main reason for no VD usb is Meta will not allow it outside of their software.

OK. So with 1888 baseline X2 is 3776 pixels. My final output is about 3400 so very similar and not particularly excessive. To get the same resolution in VD you need to supersample by 1.15. Try adding this in via QVFR to the centre, or even as high as 1.3. Combined with DLSS 4 it should give you nice visuals. Edit: have you tried disabling link sharpening or using "quality" instead of "normal". The sharpening is way too much. That might make meta look "better" than VD.

No. It's bloody annoying. Curiously the limit is 140Mbps which is my network speed. Maybe a router setting!?

For reference it would be useful to know your final resolution rather than the multiplier so we can compare it more meaningfully. Apologies if you have already said this but there is a lot of dialogue. What is your initial resolution before applying any SS?

Why not use QVFR instead. This is the newer and better option.

What is your final resolution? Quoting multipliers can be confusing. For example, I start at 2112 in Meta and apply 1.6 for a total of 3379.