ricktoberfest

I believe the answer is no. It’s not actually installed in the specific block f16 that ours is modeled after. The buttons are there for export versions that might have it installed as an option.

That's too bad, just tried OpenXR again today after a BIOS update and the Oculus runtime runs about 10-20% faster on my computer than the OpenXR, in addition to being more stable in tracking

Oculus. I tried with openxr but it doesn’t track well or have as good performance so I forced oculus. Why no oculus option? I’m on a rift S

I agree except for 2 points 1. missing basic features like the F16 was initially on release 2. when they change a feature you’ve already learned and now you have to relearn it and get new muscle memory. I found this to be true with the AV8B and I’ve had a hard time getting back into it when they completely changed work flow for several of the systems long after release (I think it was the Tpod)

Try it. You can always delete it if it doesn’t help you.

It’s unfortunate that something like this is necessary. I actually stopped playing WW2 and early Cold War mostly because of the spotting issues when you don’t have radar to guide you. All we really want is a level playing ground and the fact that some people are saying this gives an advantage to VR, while others are saying the exact opposite shows how much of an issue this is. As a RiftS player I can tell you that spotting at any distance without this mod is almost impossible for me, even when I know roughly where to look. This has made it possible for me to enjoy multiplayer again.

It is an option, just don’t press the mapped button

Those are not enough of an upgrade to buy something at the end of its life. If HP were going to continue in the VR world then maybe I’d go that way, but I’ve already got one discontinued headset, don’t need another

I was really hoping that this would be “the one”, but turns out it isn’t. I’m also on the rift S waiting for a significant improvement before I jump to another.

Thanks. Didn’t see your reply till now. I wish I had Thea kills to help but unfortunately I don’t. It’s a great product and I only wish the best for the team who is working on it. Makes sense that people are working off-line so it might not show up on the github, appreciate it.

Exactly, except I’m on Rift S. I find the openxr implementation is more buggy than the oculus. Constantly recenterIng and seems to conflict with oculus ASW

What about oculus runtime? Is it still not default for oculus headsets? Currently running a registry hack to disable openxr but I’d like to not have to do that.

I’d hoped when the community team took over that there’d be a resurgence of interest, but I guess that was short lived. As far as discord- no thanks. Too much social media in my life already.

I’ve been regularly checking for updates on GitHub but there hasn’t seemed to be any activity now for months. The last patch was end of December and even the commits seem to have dried up. I was really hoping at least for fixing the modules that don’t seem to work with VAICOM. Apache and Mi8 are 2 that really bother me but also WW2 aircraft. is anyone still working on this or am I holding out hope for nothing?

I speak bad texting: I think he’s saying “But when will the super carrier be complete” either that or he’s asking where the bathroom is.

Or do what the Tomcat does and start the cockpit shaking like an SOB above 8-9G

I just found that if you disable openxr in the registry then you gain (or at least I did) 10-15 fps and it’s way more stable on oculus runtime. There’sa thread here about it. Here’s the thread.

Oh man, just had the opportunity to try it and it turns out that running on Oculus runtime via the registry hack gained me the FPS that I was missing from the MT version. Easily gained 10-15FPS for me and more stable in a quick test. Don't have time to try further but YaY!

I’m not at my computer so can’t check, but couldn’t you export both of those registry fields to the desktop so you can just click on one or the other to switch? A second thought, is there a way to remove or rename the openxr.DLL (or whatever file DCS uses for openxr) from the dcs folder that would make dcs ignore it?

I’ve also had this happen several times with a Rift S using the openxr runtime. The openxr just seems so much less stable for me than the oculus runtime, including many uncommanded head re-centers.

On another note: now that we are being “forced” to use openxr, has anyone compared in ST mode if there’s an improvement or change compared to oculus runtime? I’ve been on exclusively MT since the patch and did note an increase in FPS, but I’m now wondering how much of that might be a different runtime and how much is the MT. Just did a quick test myself now that I'm home again, seems like very little difference in FPS either way. The OpenXR has more settings for scaling, the Oculus runtime is less "buggy" and doesn't seem to require the scaling even at the same 1.3 Pixel Density. These were of course just quick tests using the F16 instant action dogfight and an underwhelming GPU

I have found that having the pixel density in DCS at 1.3, leaving the SS in openxr at default, and applying FSR scaling of 125% seems to give a good balance of frame rate and resolution, at least compared to previous oculus default settings of DCS at 1.4. I’ve stopped using Tray tool for now as it seemed to be conflicting a bit and will just turn off ASW with the Ctrl-1 hotkey

I very much like the A10, was my 2nd purchase after the Blackshark2. I still go back to it every couple months even after “flying” it for over a decade.

I still don’t understand what’s so amazing about a new radio for the a10 and why it’s taken so long. Even watching the video by Wags just has me thinking “so what”

Is this VR or pancake mode? I run ryzen 5600x, 32Gb 3600 ram, and a Vega64 and get 30-40 fps in VR, which translates to 90-120 in pancake. This is single player so not the cpu intensive load that multiplayer puts on it but I usually still get over 35-45 fps in various servers. 35-40 FPS is very playable in VR. It only gets choppy below 25