Maddaawg

I had already edited my post, what I mean is either ED or Meta:

Yep, I did mix up the two players that are causing OXR tools to have issues, just another reason to go with VD. PTC v68 is on Meta and may or may not break several tools in the final version, and QuadViews is currently broken from ED but has a dll fix that @mbucchia would prefer we don't use but rather complain to ED. I'm happy with VD and getting rid of all the headaches of OpenXR compliance. Is the reason VDxR not an issue because VD dev's patch it to circumvent what ED does to OXR? I just re-read this, so even if ED or Meta breaks OXR it won't matter in regard to HTCC?

For HTCC, your referring to while using VDxR, because earlier in this thread @mbucchia said v68 could break it and other OXR tools. I think this is due to ED mishandling OXR and so VD should be safe with VDxR?

It should be pinned.

@slughead What's are your PC specs again? Are you using the Quest Pro too? With a i9-10900k I am CPU bound and if I try and run QVFR I get lots stuttering with my CPU tanked. I stopped trying to us OXRTK or for that matter any of the tools as DCS and Meta are in a competition to see who can break them the fastest and most. With HTCC being OXR reliant is also a little worrying too, so I hope that keeps working in VD. One quirk with HTCC and VD though is the Dev said to disable hand tracking in VD otherwise it might cause strange issues. But for me, it won't work at all unless I enable hand tracking.

Yep, and it's those hoops that have me on VD. Sick and tired of Meta Link software and updates that break it and needing to use old tools or 3rd party tools that are no longer supported. So if you take it off your head it crashes?

I never tried it, just went by this information but now he may have changed his mind on that.

My understanding is that ASW is disabled when using turbo mode in OXRTK. Never mind, following bad advice.

FWIW when I run Quadviews my FPS drops and I get stuttering. It takes a hit on the CPU and I am already CPU bound with a i9-10900k. I also have some settings higher so that may just be it too.

The settings can be really confusing. Here are my settings, start there and tweak.

Thanks, I'll do that if or when I return to using Quest Link. Trying out VD for a while.

I never knew that, thanks as it is a bit annoying when working the throttles back and forth on a carrier landing. I'll remove it today.

Thanks

I think that's good advice, I'm just really not liking the Quest 3 for DCS. For other games it works really well, but that may also be because ED hasn't put very much effort into DCS optimization, let alone DCS in VR. I would probably only pull the trigger with good reviews and availability of a 5090. My first upgrade anyway is CPU/MB/Memory when AMD 9000 is out, and then probably wait for the x3d version.

It's really quiet in here, I put my $1.08 deposit down.

Do the IRL FA-18C have a center detent for the throttles? Just wondering where my center detent should be on an Orion 2. So let say in general at bar 29.92 sitting on the carrier. A fuel flow of 50%?

I've been getting a minor stutter when I wake them up, I'll check to see if this is set correctly.

Ok thanks but the error is in OTT. I am currently back to VD though as I could not get Quest Link to stop with ASW. I tried both ODT and OTT and ctrl+numpad 1. If I open the OTT menu in game, then I can get it to turn off ASW but I still can't get the bit rate set as seen in my screen grab. ODT will not shut off ASW either, its says its off but its not though I can cut/paste the bitrate there.

When I try and set my bit rate to anything, I get a registry error.

I've been thinking about my future PC and VR headset upgrade. For VR, I've been look at the Pimax Super QLED and Micro-OLED. There also the option to get both in one package. I just watched an update from Pimax on YouTube and they said the QLED will be available first with a 50ppd lens while they also talked about a 57ppd lens being developed. I'm assuming that the 57ppd is for the OLED. Which do you think would look better in DCS? YouTube Pimax Crystal Super Update

Need your system and VR settings. How are you connecting VD, Steam, Quest Link wifi or cable? Settings in those connection methods too. Post upgrade? Using MT? Start with a repair.

I would like to know how your connecting the Q3, VD, Steam, WiFi with Meta Link or USB with Meta Link? Are you running bin-mt\dcs.exe bin\dcs.exe? Your specs are similar to mine. I have mine connected through USB on Quest Link. I run MT and set the Quest resolution to 72hz and PD of 1.3. My PD in DCS is still 1.0 and I run MSAA at 2x. I had a very smooth run in an FA-18 cold Start in Afghanistan. I used that and it's pre determined way points to test multiple settings and connection methods. VD use to be my go-to, but that did not work in Afghanistan. Also, I am using no ASW and I was getting 36 40 fps. I'm not sure this would hold up in MP though. When I get home I'll screen shot my settings. Oh, gages are clear. Edir: I had disabled ASW in OTT and the Quest is ignoring the setting. Dev notes on his site there may be issues with Win 11. ODT also doesn't work and neither did ctrl + numpad 1.

Unfortunately you and I are at a dead-end with intel. I'm looking at AMD since upgrade support is longer. I'm waiting for the new AMD.

I have the same CPU and here is what I noticed. Without any foviated rendering prior to the update in the caucasus I was CPU bound(red). After the update I became GPU bound(green). When I put QVFR on to use for FFR my system tanked. CPU bound and dropping frames so much it was not usable. QVFR and OXRTK's FR are CPU intensive. I was going to upgrade my GPU from 3080ti to 4000 series but now I see my CPU needs to be upgraded first. I can't run FR without using the lowest graphics possible.

The dev for OXRTK has recommended you remove the tool, he is no longer supporting it. I only use it for displaying FPS and CPU/GPU usage. From his Github: DCS and Quad-Views are also currently having issues.