Maddaawg

So that video is the first time I have heard of the Pimax MR front plate. Have they said anything about hand tracking with it? I'm starting to think that the Super may need a 5090 because of the 50 ppd, that may cause me to change my mind and get a Light.

I wish they had more information on the 12k, some specs about the panels and lenses. It looks like it will be about as heavy as the Crystal since it has batteries too. I like that it has hand tracking and pass through which I wish were going to be on the Super. At 50ppd, the Super is already going to being needing a top tier PC.

That was my original plan, to upgrade the GPU. It's an interesting concept that you upgrade the GPU and become GPU bound where as you would think that would make you even more CPU when your showing CPU bound. I've heard the in-game DCS monitor isn't trusted. I think the best way is going to have to be observing my own CPU use vs GPU use. Ultimately, I'm upgrading both anyway and since AMD is bring out new processors, soon I may get a really good deal on this generation or if justified in the reviews go for a 9000x3d when they come out. The 7800x3D is really proven right now though. Which your your HMD's are you using for DCS?

My confusion is from a lack of sleep and coffee. I am 7.5 miles or 6.5NM in front of the Park Fire in California. Our property has been evacuated but I am already in Seattle waiting for a lung transplant. I sleep from 2am to 7am to monitor the fire all day and night and stress 24/7 between it and my lungs. I get some relief from browsing DCS stuff but I haven't really played since the fire started. So I really have no idea if this or that is fixed or what is or will be broken, I'm just trying to engage in other things in between scouring the internet for the Park Fire.

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.