Strong05

I believe it's a result of the h264 encoding taking place due to the Q3 not having an actual display port or HDMI port. I've seen the same thing with a 4090 see link below for my experience and why I'm returning mine.

Added my settings to the first post for the quest 3 and the G2.

As to the Quest 3 vs the G2 you can see my comparison here: One thing not mentioned is that the Crystal and the Varjo Aero both have dynamic Foveated Rendering, which means eye tracking and only rendering in high fidelity what you are looking at. I haven't had a chance to use this yet but from everything I've read it's a game changer that allows for great FPS with minimal compromise. Lots of great videos on youtube exploring this feature and comparisons of most of the widely used headsets.

What? I have not talked nor compared anything about the Pimax crystal once, in my original post nor does it have anything to do with my response. I have both the Quest 3 and G2 in my possession, for which my comparison is solely focused on. And yes the quality of the imagine of the Q3 does greatly depend on the link settings you have. The image is not generated via a native video connection. Please read my reply that was a direct response to you. It's also possible the way you are streaming the game to your headset is superior to what I'm doing. You mentioned you are using USB to connect what USB data transfer speeds were you able to achieve? I am also interested in your settings for the G2. It seems to me that something is off for our experiences with these two headsets to be so different. But as I said in the OG post YMMV. Let's try to keep this thread on topic and constructive, so that others that may want to move from the G2 to the Q3 can learn something from it.

Per Meta here is the Q3 resolution: https://www.meta.com/quest/quest-3/#specs - 2064x2208 pixels per eye That come out to 4,557,312 pixels per eye The G2's resolution is: https://support.hp.com/us-en/document/c06938191 2160 x 2160 panel resolution per eye Which comes out to 4,665,600 pixels per eye. So in fact no the G2 has a higher resolution. However the more telling metric for what the clarity should look like is PPD (pixels per degree). Which based on Meta's website it should have the edge: 25 PPD and the G2 is only 22.08 PPD. https://vrlowdown.com/reverb-g2-vs-quest-2/ So the lack of a display port or HDMI port is really hurting the clarity of the Quest 3 as it should have the better image quality full stop.

On edge to edge clarity we agree. However, if you are in the sweet spot of the G2 it is significantly sharper and clearer then the Quest 3. Is it possible you have an incorrect setting for the G2? Are you using the G2 with steam (I recall this could look worse then the Q3) or with WMR and openxr? Your settings in WMR can also ruin the image of the G2, so interested to know what exactly you have it set too to make it look worse then a Q3. I'm not using out of the box settings for the Q3 either, I'm using the quest link with 940mbps in the oculus tool settings which is almost double the band width of the default settings and it's still not as clear as the sweet spot in the G2. I also have super sampling turned all the way up in the oculus software, where as with the G2 I'm not running any super sampling. LET ME BE CLEAR, changing those 2 settings greatly increased the clarity of the quest 3 over "out of the box" settings for the quest 3 and it's still not as clear as the G2. You can see the video compression fuzziness in all of the writing in the cockpit and shimmering on other airplanes parked a spot or 2 away (with MSAA set to 2x for both headsets, also I haven't changed a single DCS setting between the 2 headsets). So no, the quest 3 is absolutely not as sharp as the G2 in the sweet spot. I need all the visual clarity I can get to V-ID in cold war and WWII servers. If you can live with the reduced clarity in the sweet spot because the edge to edge clarity is far superior to the G2 I totally get that, but that's not worth $500 to me, especially now that the G2 is effectively worthless due to Microcrap. Enjoy the quest, I will be returning mine. Maybe valve will release a new headset that doesn't cost an arm and a leg.

Picked up a Quest 3 a week ago and have been playing with all the settings to try and get the most out of the link. Unfortunately the Quest 3 clarity in the sweet spot just doesn’t compare. On top of that there is a pretty big performance hit. The quest 3 lenses are much clearer edge to edge, but that’s the only thing going for it. The headset was very uncomfortable for any extended play/flight time (this can be fixed with the pro head strap or one of many 3rd party offerings). At the end of the day it’s down to your preference, edge to edge clarity(quest 3) or higher clarity (g2). It’s just not enough of a difference to justify the cost for me and I will be returning it. If your a first time VR user then this is still a good choice, the only negative is it takes a lot of fiddling with settings to get decent clarity, otherwise your left with a shimmering (at distance) blurry (up close) image that doesn’t do the headset justice. Hope this helps anyone interested in upgrading, YMMV. My rig: 5800x3d, 32 GB RAM, 4090. Both headsets are running in OPENXR, with DCS running natively in OPENXR. null For the G2 WMR is set to: Adjust level of detail in WMR home: Low App window resolution: 720p Experience options: Best visual quality adjust display resolution: 4320x2160 (best quality) frame rate: 60 Hz null

This is has been a sore spot and complaint for years that ED refuses to acknowledge or address. Not sure why, as sometimes I feel like half my time in game is re-assigning controls. To be fair it wasn't as big of an issue 10 years ago when there were only a hand full of modules but now it's a significant chunk of time flushed away. You can also rename your existing default files to the new controller names and then the game will see them and use them. Please ED add some way to holistically back up all of your key binds and important them easily (like one click or moving the folder over) for when you have to refresh windows or build a new computer. @NineLine

This is a bit of a long shot but you might try searching on youtube for TechYesCity's windows optimization video (he has one for 10 and 11). It's like a 10 or 20 minute video of him going through all the settings and turning off all of the bloat. Worst case you have a faster PC at the end best case it resolves your problem.

Having the same problem with V ID. Resolution is certainly part of the problem but the other is that the airplanes appear to be way to dark regardless of time of day or clouds. It's like the plans all have some kind of cloaking device that makes it impossible to see the paint or markings of the plane.

Looking for any feedback or settings that might help improve V ID. Using G2 (V1) with 4090 and 5800x3d. I suspect there are 3 main factors that help or hinder V ID ability in game/VR: 1. Clarity: Not much I can do here other then super sampling or MSAA (aside from buying a varjo which isn't in the cards), but I'm not sure this will really help much. I believe the main factor here is hardware and pixel density. 2. FPS/Ghosting: This is one reason I got a 4090 to alleviate ghosting, which makes it really tough to tell what your looking at when there are 3 of them superimposed on each other at different times/frames in the same frame. I'm getting 90fps most of the time now with my settings so this one is well mitigated. 3. Gamma and contrast: This is the one I'm hoping to resolve or make better. I'm not sure if this is a game engine problem, hmd problem or a setting problem or all of the above. Unless it's the middle of the day and perfectly clear it is really hard to make out paint schemes and see color on an airplane, which means I'm left trying to id on profile alone (which is harder when you don't have enough PD). I've also noticed that aircraft will "vanish" in shadows of mountains. I've been in a turn fight on the deck and lost visual in a mountain shadow with the only way to see him being to turn labels on. I mean if he flares I can see the flare but the guy is invisible otherwise. I've tried turning up the gamma some, and I guess I can turn it up more but the cockpit looks fine and I feel like it's going to start washing stuff out (especially mid day). Is anyone else having this problem? Any suggestions on how to improve this so that I can at least see something other then grey/black when looking at other airplanes and/or so they don't go invisible when they fly into a mountain shadow? Thank you in advanced for any constructive suggestions or feedback.

Interested in this as well.

Just encountered the same problem here. Weirdly I've run both the latest drivers and the ones before without this problem (I rolled back to Nov 22 from the latest (8 Dec) during the GPU's are cracking because of a drive update scare) and now I get the flashing with both of those driver sets. Tried a clean install with either and I still get it. I wonder if DDU wipe would resolve the problem? Edit: Rolling back to 22.5.1 resolved the issue for me.

There really isn't much difference between a 6900, 6950, and 6800 xt. Talking maybe 5% or best case 20% better. The 12Gb 3080 got nearly identical performance to the 3080ti. I'm running openxr with motion smoothing off. PD set to 1 in game and 100% in open XR tools. No frame limiters either, just the undervolt and a slight bump in GPU freq. I am running with SAM on, I did briefly try a 7900 and SAM actually reduced frames (I returned the 7900 because the performance was worse then my 6800xt). I've tried reducing render scale/PD and I immediately notice the difference in cockpit. I got the 6800XT because that's all that was available (purchased 2 years ago). I would take a 3080 12gb, ti, or 3090 (pending the price isn't outrageous) over the AMD cards any day.

I'm undervolting, which actually increases performance. Jays2cents has a good video on how to do this. Apologies if I wasn't clear, the 6800 XT is absolutely a better performer in VR then a 1080 ti for DCS. However, the drivers (motion smoothing/reprojection) is better for Nvidia, and just generically speaking I have found that Nvidia cards support VR better which includes the 1080 ti (even though it will be significantly slower then a 6800 XT).