Hoirtel

So for me if I launch airlink with a encode bitrate in ODT above 200 it will lag. My current setting of 900 (cable) it won't even launch. I have to set this back to 0 and then can max the options in the headset which is upto 200. Sadly I don't think this is using AV1 as it looks bad. Anyone else know how to use higher bitrate over airlink?

I think the other posts are correct, DLAA is part of DLSS, but DLAA can be run on its own too. So far through my testing I have found what I think somebody esle already said. For those of us that are running VR headsets of around 2Kx2K res (Q2, Q3, QPro, G2) its seems the options are no shimmering but a bit of blur and ghosting (DLSS/DLAA + Supersampling) or go with the only option we had before: sharpness and clarity but with shimmering. After way too much testing my own preferred option will be to stick with the shimmering. This is because I do like oculus ASW and I am so used to it now. With a powerfu GPU I find that shimmer can be reduced a bit with 1.2 upsxcaling +MSAA x2 + MFAA (in the nivida control panel). This last one is subtle but does make a difference on top of other options. Small improvement with small perf impact too. However at the end of the day it is really down to which route you prefer and works best on your system. I think the only way to have clarity and low/no shimmering is to have a high resolution headset with lots more pixels. That way the shimmering will just be less as there is more physical ability to show detail and the requirement for AA will be less. Not tried one myself, hopefully will do at some point.

It does look like DLAA is greyed out when DLSS is on, which looks like it is a forced setting. But could also be me reading the settings page wrong. They look so similar to me once enabled, with DLAA being a bit less ghosting and artificing, but higher performance requirement.

Hmm..I'll try lowering it until I see it. The main place I saw it was in the terrain textures, particularly the green fields of normandy.

Not tried 500 but 450 looked bad to me, was using 900/940/960 all looked the same and much better. Now down to 800 and still looks good. I'm not using the headset audio though. I will try lower as I think it is bets to keep this as low as you can. My old Q2 setting was 450 which was why I was so surprised to see bad compression on the Q3 at this rate. I think meta have link software updates to do. Same thing happened with the Q2 at release.

Is quad views actually better performing than the normal foveated rendering? Both without an eye tracked headset.

Out of interest did you go from your system drive (c) nvme to an additional data SSD, or were they perhaps both additional drives. Just wondering what this might be I have DCS on gen4 NvME SSD and while it's not a stutter fest, it could be smoother.

I don't use the headset audio anyway. Just prefer headphones.

Great, thanks for the details. So I have supersampled and it improves DLAA, still less sharp in distance but that is probably the price of no shimmering at all. Probably done DCS VR for too long and got used to it. Now it's a bit of blur and ghosting, totally different experience. I used openxr overide but then did 1.2/1.3 in ODT which I feel is much the same but prefer the multiplier to a pixel level option. Also running 940 bitrate. Anything else looks compressed on the terrain. The old advice was not to use in game PD, but I suppose its all new rules now! Maybe I will try that. I will also try your 30hz setting, I usually run at 80fps/40 reprojected. It's that rendering a third of the frames and reprojecting more? With all this SS I feel I really need to keep a closer eye on my 12vhwpr cable... Eek. 4090 seems to love the punishment though! Runs well even with all that and high settings. Nuts.

Where are you supersampling? Are you on link? I have just been tinkering with VD and really can't say I get on with it over link, but DLAA looks really bad. Must have something wrong! My GPU driver was also 537.45 so gonna update to 545.84. If you are using openxr on link was is your approx GPU render time (advanced FPS counter)

Yeah seems to be. Although running DLAA for me looks very bad. All distance very blurry. I am running over link with reprojection at the moment. Maybe I should switch to VD and try to not use ASW. For those that use VD with the Q3, should I add DCS to my steam library. Currently launching off the desktop...

So 2.9. Back to the drawing board with Q3 settings! My first question. Will DLSS replace reprojection... My download is in progress.

Six faulty headsets seems more than unlucky.... I have checked mine a few times and I really can't see any dead pixels? I can see glare in the right conditions but it's not invasive in gameplay. I also don't see any mura but maybe I don't notice it? Not sure what the best test is for that.

I tried the tip on VR flight SIM guys channel. Basically for link running the high bitrate setting but also setting the oculus render Res to 1.0 and then overiding system Res in the openxr toolkit to as high as you can manage. I can totally confirm this is very sharp and clear, much better than max render Res in oculus. On his tips he also says link sharpening on quality, I still think normal is sharper but YMMV. Maybe settings tips are pointless at mo. Just got it dialled in and its all to change tomorrow lol.

LMAO you totally called this. I laughed when I saw it because of your post. However I agree with the bitrate but not tried the Render Res +openxr yet. Yes at low bitrates. 900+ is really nice. I don't think meta support av1 at all yet. It can be done in VD and looks good, but you need full FPS all the time as reprojection looks bad. Link (air or cable) reprojection I think is great.

Menu (left controller) streaming, see options for disable/auto/force spacewarp.

Depends how much you looked. All meta headsets default to the "recommended" render res, which is really bad looking. I used Q2 for 3 years, no problem at all spotting anything. I flew with a lot of other people, on a lot of different setups and I have honestly never not been able to spot something that somebody else can see. Vice versa has happened though.

Bit of an update since I have now had time to test & tweak. Based on my experience and what others have posted online, I am almost certain meta isn't supporting AV1 through any sort of link yet. I see horrible compression unless I use the 900 bitrate "trick" in oculus debug tool. This actually removes nearly all of it and things look really quite nice.. To my understanding AV1 should get great results at 200mb but this doesn't happen for me on either link. I don't think you can run airlink over 200, someone tell me if this is wrong. I have used VD and this is very nice looking, can't seem to get it to do wired link yet but it does work nicely with my 6E router, and almost looks the best (ultra or godlike). The main problem for me is that the oculus ASW is terrible through VD, all of the distance is blurry and wobbly. I actually like oculus ASW, one of the few that seem to but for me (on link) it is really good, minimal artifacting and allows me to run very high settings, great eye candy down load and in cities etc. VD also has no (official) openxr at this current time, this is in testing so there might be improvements in perf to come and maybe I will try to move away from ASW if that gets better. I am a new VD user so tips welcome. One surprise is that running at 900mb over link (with and without ASW) I really notice how responsive the headset runs. I also am sure I see I performance improvement, which is bizarre. I actually wonder if the Q2 decoding was a bottleneck previously. I seem to be spending much more time at 80fps (headset set to 80hz) that I ever saw before, and even in my heavy test tracks where I would see dips to below 40fps (reprojection rate) these now do not happen. Odd. I also take back what I said about comfort, its actually awful. I have used the Q2 with stock face plate and strap for three years (yes.. stock strap) and this hurts my head and face after 1 hour. The stock strap also is just different enough to my catch ears whereas the old one didn't, this also means that my headset now doesn't fit either so I will have to buy a new strap that I can use a headset with. Not such a low cost now. I really think the PCVR has a little maturing to do yet on either VD or link but the 900bitrate looks like it will be my current option. I actually think the Q3 will get really nice in link once the updates are fleshed out.

I'm trying VD. It does look good but I think the reprojection makes everything in the distance terrible. Or I haven't got the settings right.

I bought VD the other day. From what I can see Meta doesn't yet support AV1 in via the links. I haven't tried it yet but hoping this will help my compression issues. Sounds like you have had a good experience!

Argee - high on my list of things to tinker with next. I may have made a mistake thinking that I would start off with all my Q2 settings. Perhaps I should reset NVCP and clear directx cache/metashaders and start again. Prob get 2.9 soon and then it will be all new anyway.. EDIT - BN just said not this week literally as I posted.

I would say 30% improvement to clarity is about right. It is much better. Colors probably the same, maybe better, definitely not worse. Its the night time whwre I see the most difference, the night is still dark gray (no local dimming!) but the improvement in clarity/lenses makes the visible lights on other aircraft/airfields/towns etc much much better. I am really pleased with this. For me the Q2 lenses additional glare ruined the night lights a bit, now fixed! I am going to try VD, it will be nice to know that I am using AV1 and get the extra info I agree the outside is where it shows. This is where all my compression issues are. One of my test scenarios is in F16 low flying across normandy/london. The grassy areas look really very compressed at the moment. Much more tinkering to do though. The cockpit looks great, but on a max res Q2 I could still read everything, Q3 is sharper and clearer no doubt at all.

Local dimming will.make a nice difference at night yes. If you are suffering with low GPU power then DFR will be very helpful. I used fixed fr on q2 on and off. I can't say I noticed the lower rendered areas much, maybe I will now with pancakes. I like to record the mirror and so if I can run it off altogether then I do. Another point - Meta has a win with recording VR. I can start and stop the recording with my hands in DCS. Records in the headset and stabilised too. Very easy.

Yes it is a bit, and not having used one I can't say, but I can't see it would be a massive difference. I could be wrong, but I doubt reviews would have said it was that clear if it was much worse.

It's hard to advise properly. Headsets are a bit subjective. Pancake lenses are much better than Fresnels. Fact. Q3 supports that. Screen Res is the same (ish), colours are probably not as good. They are quite different generations. I never mentioned tracking because I expect it will be the same as the Q2 which was rock solid. I also really like metas ASW, but some don't I'm still leaning towards a quest pro coming from the G2. They have a crystal here in the states on Amazon but I don't trust I won't have any issues after the 30 days return policy. I definitely don't have the time to deal with their support over there. There are only 4 support folks in pimax currently according to their discord channel. Only advantages will be local dimming and dfr, so depends if that's worth it to you. I'm glad I waited for Q3 but if you can get a pro cheap enough (and it does include a strap!) Then probably worth it. If you intend on using passthrough then I hear it's worse it the pro. No wonder it didn't sell for this feature. It's not great in q3 It's possible the 2nd generation onboard chip in q3 will outweigh any pro advantages. Early days yet.