Phantom711

As I said, start from scratch. Reset upscaling. Only use it if you can‘t achive good quality with the regular settings. Upscaling will take a lower resolution and artificially try to increase it to a desired res. But it will never look as good as a „real“ high resolution/supersampling. Hence it might cause the blurriness. Also try without DLAA and/or DLSS first.

The resolution setting that you select there in your pic won‘t do anything for you in VR. It is only the res for 2D. You have to select your resolution for your headset in your headsets software. And usually you would want to supersample at least a bit for best quality. Alternatively you could increase the PD value in the DCS VR options or increase the res in the OXR toolkit. But I would recommend to start with your native headset‘s software. EDIT: And I recommend to start from scratch without any upscaling selected.

Try turning Turbo mode off if you have it selected in either OXRTK or QVFR. Yes, I think you got this right. What mbucchia said was about NATIVELY implementing QVFR into VD.

For me it is the other way around. Had some severe rubber banding with VD and Turbo mode, whereas it works without issues for me on QuestLink and even ASW on. One can enable local dimming in ODT and probably also OTT (haven‘t checked though).

@sze5003 So basically what you are saying is that eye-tracking isn‘t working for you with VD? Make sure to follow mbucchias instructions on how to use the QuestPro with QVFR. https://github.com/mbucchia/Quad-Views-Foveated/wiki/Meta-Quest-Pro

@VR Flight Guy in PJ Pants Chill! My comment was not aimed at you in a sense of saying you should have provided me the multipliers instead of the res numbers. But indeed I find it a bit odd, that pretty much all other apps (WMR, SteamVR, Meta) use multipliers or percentage sliders and only VD uses their own fancy „names“ for it. Yeah…not your fault…

@PatMcKrotch I suggest, next time you post a crashlog, make it some sort of word document as an attachement please. As opposed to just plain copy/pasting it into the message here.

@VR Flight Guy in PJ Pants I tend to think in multipliers rather than the actual resulting resolution. So I deduct from those numbers, that Ultra is 1.5 and godlike is 1.7.

Does anyone actually know what would be the equivalent multipliers of the VD settings like „ultra“ and „godlike“ are. I personally didn‘t feel any need to boost them any further.

@gonvise 90Hz: yes Scaling 2.0: VD doesn‘t really call out the numbers, but „ultra“ and „godlike“ are nicely supersampled. (2.0 is a VERY high setting!!!) ASW 45: yes and no. VD has it‘s own MR method which is called SSW. I find it to be not as good as ASW, but you can set it to „automatic“ or „always enabled“ which would be the effect you are asking for. bitrate 900: No. But you can select other (better) codecs then the ones that QuestLink uses. I find HVEC10 to be very good and only then tried to achieve a similar result with QuestLink and settled with 500mbps there. With 900 I get severe audio cutouts. EDIT: This is just for comparison. And to avoid any confusion: Settings in OTT are completely meaningless for VD. OXR Toolkit and QVFR: yes and yes. (However: some people report problems with the toolkit and the latest Meta software v68)

If only VDs motion reprojection was as good as Metas ASW….but other than that, I definitely see your points…

I guess it might have to do with the codecs that Meta uses vs. VD. I used HVEC10 with VD and I feel the same way. Maybe HVEC10 handles the „lesser“ pixels in the outer area differently from H.264. In your video, side by side, I would say that VD makes the outer area rather blurrier whereas OculusLink makes it kind of pixelated/grainy. The latter would certainly be more noticeable in the peripheral vision. The ghost trails: do you use DLAA or DLSS? They tend to do that.

There is nothing to be „launched“ about OpenXR. If you mean the OpenXR toolkit companion, it is active, unless you deactivate it by the respective checkmark. QuadViewsCompanion: This is only a tool to change the settings of QuadViews. You only need to open it if you want to change the settings. It doesn‘t need to run in the background. OTT: yes, this needs to be running in the background if you want it‘s settings to be applied. As far as I understand, it needs to be opened BEFORE the MetaApp is opened on the PC.

Joah…aber OpenXR ist nunmal der default in dem die MT Version von DCS läuft. Bzw. wie meinst Du das überhaupt „Du hast OXR deaktiviert“? Oh und es gab heute übrigens einen Patch…vllt liegt es daran?

@rss0900 Since you are probably not very active here and have not followed the developement, you may have borked some things there. Firstly I would recommend to run a DCS repair. Also want to let you know, that OpenXR is the default way of running DCS nowadays. You don‘t need to manipulate any files in DCS anymore like one had to back then. You should to have „OpenXR tools for WMR (Windows Mixed Reality)“ installed in order to activate the OpenXR runtime on that. In that app you might also want to dial down the resolution % and you can chose to activate motion reprojection (I would recomment AUTOMATIC) for a smoother experience at the cost of some artefacts/wobbling. Alternatively you can set SteamVR as your OpenXR runtime in the SteamVR options and run it via SteamVR. It should run better without SteamVR though. Lastly a headsup: If you are running Windows 11, support for WMR will end very soon (or has it already?). If you are on Win10, you should be fine. Also: what are the rest of your specs? (CPU)

I had similar issues a while ago abd also very violent in-game freezes. I disabled the 8th core (last P-core) on my 13700K. Haven‘t had an issue since.

@lolof1 One could use a mod manager like OVGME to switch between the regular version and the „dirty fix“ for QVFR.

Using Quad Views on a crystal light basically is a form of Fixed Foveated Rendering but uses another technique. QVFR is more efficient in relieving your GPU but also puts some more workload on your CPU than the FFR that you can chose in OXR toolkit. QVFR also already has some sharpening build in, but you can put CAS on top of it or use it instead. Just give it a try, it doesn‘t do harm.

@Glide I was referring to the post before mine which stated that he loses his wireless connection more often now. As far as I know a Crystal doesn‘t have a wireless connection yet. So I don‘t see how this would happen to you as well?!

@Michel0079 I would call it unlikely, that this is a DCS issue. Remember, that Meta also issues updates to the Meta app and the headset frequently. Could also be something else interfering with your WiFi.

Since you are using a QuestPro, this is absolutely irrelevant. Nothing you set in there has any effect for you because as the name of the app suggests, it is for Windows Mixed Reality and the respective headsets that use it (i.e. HP G2). In the settings of the Meta PC app, make sure that it is set as your OpenXR runtime (Settings>General)! I have a 13700K and for DCS I disabled the 8th core (P-core), which has solved the problem of frequent freezes for me. Disabling all E-cores had a negative effect for me and even though this was propagated by some people, I think it‘s bull<profanity>. But find whatever works for you!

@splash 2.2 is crazy high. Do you really feel that you need that? I have mine set to 1.7…and that is also with a 4090 and using Quad Views on a QuestPro. Maybe rather try the middle ground then…I have mine set to 500. The differences are very subtle and you won‘t notice a difference in all situations. I only noticed, after I tried Virtual Desktop, which simply looked better and I couldn‘t tell why until I tried increasing the bitrate on Quest Link. There is less color banding and I feel like terrain at a distance looks better.

@SgtButsy The game‘s interaction or lack thereoff with an external product like a specific vendor‘s controllers (or virtual hands) might be even more complicated to fix than an internal problem that you mention as examples. And in all fairness, Meta also had a recent record of implementing surprise changes that broke stuff in DCS.

@Hursta1 The update is not even a week old. I don‘t think it‘s a realistic expectation on your part, that this gets fixed that fast.

So wie ich das im NATOPS lese, ist das nur ein Verfahren zur Fehlerbehebung, falls der FCS RESET nicht funktioniert hat.