slughead

Yeah, ok I get that, fair enough. That flight is more of a system performance test that I run. Since the last patch (not today's) I've not managed to get this to happen again. The AI is keeping a decent altitude when he's not on my wing. I have another that I will raise in a separate thread of the AI wingman ejecting when he/she/it calls bingo. Thanks for taking the time to review these.

Turn it down to 80 and try again. Of course, if it drops lower than 80 you will have the same ghosting of fast-moving planes. It's all a trade-off.

This one? I read the reviews... Hence my earlier point about reliability and regulatory checks. I don't want to trust my thousands of pounds PC and near thousand pounds headset to an iffy cable. Kuject Design 16FT Link Cable for Oculus Quest 2, with Separate Charging Port for Ultra-Durable Power, USB 3.0 Type A to C Cable for VR Headset Accessories and Gaming PC : Amazon.co.uk: PC & Video Games

That's your system unable to keep up with a 90Hz refresh rate. As soon as that happens, you end up in projection. Aircraft flying past fast whilst in projection appear double or ghosted. This for me is not micro stutter. It's much more pronounced. With the landscape, people refer to it as a judder during high G turns. You'll either need to reduce the headset refresh rate, or turn down your settings. You' won't get rid of it completely though. The more demanding the terrain (cities, buildings, objects), multiplayer etc the harder it is to stay out of reprojection.

Microstutters with barrel rolls? The micro stutters I am talking about are flying straight and level, say 3000 ft AGL looking to 3 or 9 o'clock and towards the ground and used to see the landscape skip once maybe every few seconds. This is typically the app losing sync with the headset and skipping 1 frame. Barrel rolls are huge changes of movement such as fast high G turns so this sounds to me that you are seeing fps drop below the refresh rate of the headset and switching to projection (if you have that enabled). If not enabled it would be a far worse experience. We normally call this judder rather than "micro" stutter. If you are running at 90Hz, you will be hitting the limits of your system much more often and easier. No CPU upgrade is going to help with this. Vulcan might with multi-threaded GPU API. Perhaps if you could try to capture this using OBS studio and put a video on youtube we can be certain that we are on the same page. There is an OpenXR plugin for OBS studio so you can capture the VR stream rather than the mirror. I haven't tried it myself yet.

I also bought the full face mask and have hardly used it The two detachable side masks I think are probably good enough for the most part. So save yourself some money and just try the side ones for any night flights - nothing worse than being blinded by your monitor as you turn your head during a night flight.

Perhaps. You've now got more information to go on now though which isn't hearsay. I am on 2 sx 32GB (64GB total) DDR5 DRAM at 5200MHz with a Gigabyte Z790 motherboard and an i9- 13900K processor.

I think we are going to have a long wait for the perfect headset. Decades rather than years in my opinion sadly.

Me too but you could still reach a point where the processor thermal and/or power throttles itself. If you run the Intel XTU software you can see if this happens. I haven't disabled e cores and I have hyperthreading enabled. I also have HAGS enabled and DCS MT set to high priority along with the Oculus Server set to high priority. That may have been the "bloom effect" setting under the VR options causing that. It needs to be off as per the instructions. I run turbo mode as part of QVETFR. The other performance gain you can get is by reducing the FOV slightly to .85. You also say you are running at 90Hz. I run at 72Hz. That's a bit performance boost again.

I am not or rarely seeing micro stutters now. I take it by micro-stutter you mean a single skip of the landscape and not ASW/reprojection judder? As you are using a QP, get the quad view foveating rendering enhancement from here. This will give you 58% fewer pixels for your GPU to push and you will barely notice a difference. What you will notice is a large gain in headroom and the micro-stutters will mostly go away providing you haven't got some other process running on your right causing your problem. Also, is your motherboard PCIe 4.0 or 3.0? If 3.0, you are not getting as much bandwidth to your GPU (4090) as you could and this could be a significant factor. Your sig shows you running at 5.2GHz. That may be ok at idle but what is happening under load? If the thermals are high, the CPU is likely to be thermal or power throttled and you could end up running much much slower than if you didn't overclock it. I am running a 13900k at stock settings, i.e. not manually overclocked. Also, also... are you running Win10 or 11? Win11 I believe is better for new intel processors and is designed for them whereas Win10 isn't.

The best thing.... Meta was offering 30 days no-quibble return. So if you don't like it, you can return it. I bought all of my QP gear from Amazon. At the time I also got a 12-month interest-free option from Amazon. So was a win-win for me. The official cable is called "Meta Quest Fibre Optic Link Cable". I can't find any on Amazon anymore. You should be able to buy from the Meta store. Argos have them. They are not cheap though. They are said to be fibre optic. So USB-C at each end with a built-in fibre converter and then fibre between combined with power conductors. For what they cost I'm not going to cut mine open t check they are actually fibre-optic

Yes. Follow the instructions provided on the wiki where you get the software. You can use the QP over Airlink. Obviously, you're going to lose battery power and I'm not sure it's going to be glitch-free even on wifi6e. Most of us run DCS on a QP with a cable. I use the official cable. The battery still discharges but at a lesser rate. Some have used powered cables, some have had success to keep the battery charged for longer, and others haven't noticed anything different. For now, I am keeping to the official cable as I have seen some horrible melting problems from the tat sold on Amazon and the like. I think it's too easy for untested items from cheap production countries to end up on eBay or Amazon these days without going through regulatory checks.

Comparing the 60Hz psychedelic hallucinogenic head-pounding mode of the G2 to the 72Hz of the QP is night and day. I do not see any flicker in the QP at 72Hz and use it all the time. I'd not say that the QP is a significant increase over the G2 for FOV. If you want a larger FOV, you're looking at a pimax I think? The problem is that the wider the displays, the more pixels, the more demanding of your system. Hence with current technology, it is a trade-off and so we have headsets that we can still see the edges of the panels/headset at our extremities of eye movement. I think it will be a very long time before we see headsets that are fully immersive. I don't think the QP is an improvement over the G2 for night flights. If it is, again, it is only marginal. Probably need OLED panels for good night flights. This is where the QP excels in my opinion. With clarity on par if not as good as the G2 but across the whole image, 72Hz refresh rate and quad-view foveated eye tracking resulting in 58% fewer pixels for the GPU to push, you will remain out of reprojection/ASW for longer. But, I will caveat that and say a 4090 is a must. The QP, 72Hz, QVFET, 4090 and I am able to push all the settings to the max in DCS although I have turned down shadows slightly to give even more headroom.

This looks like it could be useful in DCS. It has programmable key switches and rotary dials that you might be able to map to dials in the cockpit. A little bit pricey though. I think it emulates a keyboard and can be used with USB or wireless. https://amzn.eu/d/iSZ6g9d

People with other headsets are reporting similar experiences here:

Oh ok. I use a Quest Pro at 72Hz so have lots of headroom.

I am not experiencing this. I am not capping my frame rate and have turbo enabled. Are you using the multithreaded or single-threaded binary? I am using multithreaded.

Something I have noticed since using QVFR... no stutters! Looking on 6-9 line Caucasus over town, 72Hz no ASW, smooth! The micro stutters used to annoy me. I'm betting it's QVFR has helped rather than a DCS patch due to the performance uplift.

Ok. I doubled checked... I don't see the borders/outline of the rectangle anymore in any theatre. It may have been the bloom effect setting as I did start out with that on and disabled it a while ago.

I've been playing about. There is a contrast setting in the accessibility section of the headset settings. It is set to minimum by default it seems. If you increase it, blacks are much blacker in DCS night missions but at the same time, you lose a lot of lighting. So for me that isn't a good option. Then I thought that perhaps the gamma setting in DCS could be causing this. I've not yet tried to adjust mine. I don't believe I have ever changed it and it is currently set to 1.8. What is yours set to?

There is a huge thread on this brown/amber/orange haze here: Solved: Meta Quest Pro has a yellowish / brown haze in top... - Meta Community Forums - 994480 (atmeta.com) Oh, and it isn't solved despite meta tagging it as solved.

DCS has no control over local dimming. It is unable to turn it on or off. How are you able to tell it is working on the "PC link main screen" when that isn't a dark screen? You need an almost full dark screen to tell if local dimming is running or not. Same question with the "DCS main menu".

They are already. I do need to double-check that I am still seeing this artefact though.

Yeah, I could see it on the Persian Gulf map too. A black outline. Almost as if there is a gap in the rendering. @mbucchiaany ideas on this one? Any adjustments that we could make or is this something that needs to be addressed in the code?

Turn off turbo mode to get accurate measurements. This mode affects the performance calculations. You can turn it on again later. Set your encode bit rate back to default. Higher values cause choppiness with the audio. I use the dynamic bit rate encoder with a dynamic bitrate offset of 50. The choppiness isn't totally gone but it is much better. Do you mean you can see the outline of the rectangle? I too have seen this on NTTR but not on the Caucasus theatre. I've not flown in the NTTR map to see if it is still a problem. I may try later.