slughead

Super. Thanks for the update. I’m sure that’s going to put a lot of minds at rest.

@BIGNEWY as predicted. Meta has pushed back on this despite it clearly being a change that they have made and have redirected me to Eagle Dynamics and Khronos.org! Has the team made any progress on this as I expect Meta will push this out for general release in a couple of weeks.

At least they are being upfront about it. I bet your ISP is collecting a ton of data about what websites you visit, when, how often, how long for, etc, etc, etc. Yet no one is screaming from the hilltops over that. Same with Microsoft I expect. Amazon is collecting everything you look at and buy, how you buy it, how often and so on and so on. Phone company the same. Utility companies.. the same. Satnav company... the same. Even Apple has been found to record breadcrumb trails of your movements, and what wifi you connect to. Banks... ATMs.... supermarkets.... petrol stations.... To be blunt about it..... everything you are doing digitally involves some form of data capture... about you.

Ok. It’s just that if you have both installed you should only use the turbo mode in qvfr.

Are you also using the quad view foveated rendering openxr layer?

Sure but it isn't related to DCS crashing with v^3 PTC. This is an issue with the Oculus app and your headset. So to avoid this thread going off-track, please raise a new thread. Ta.

That’s some other problem. This one is specific to v63 PTC and DCS crashing on entry to VR space. Probably better if you create a new thread or raise it on the meta support forum.

I am about to embark on building these myself. I don't know why I didn't do this sooner. Perhaps it is because I bought a Quest Pro and use HTCC for hand tracking and pinch gestures for left and right click. However, the pinch gestures I've never been too happy about. I have had a pointctrl on order for 21 months now so I'm very close to mine being available. However, most of the pointctrl system will be wasted on the Quest Pro. I saw a post on Facebook that does something similar but then found this which is a much sleeker design. So I bought a 3D printer and have all the parts on order. I thought by the time I've paid out on pointctl, I might as well buy a 3D printer and make my own! Now my only question of concern is about the plastic ring wearing out my new Thrustmaster Viper throttle paintwork and labelling. Has anyone who uses these types of ring controllers found this to be a problem? I am considering either applying some heat-shrink around the ring, some fabric or perhaps modify the design to use elastic rather than plastic for the section that attaches to the finger.

You need to opt out of the PTC in the Oculus PC app. Just that, shouldn't need to roll back the headset. I say this as I never received a v63 headset update anyway.

ED is not handling the Quest in this regard particularly well as I understand it. mbucchia added a workaround in his Quad View Foveated Rendering OpenXR layer. The fix is fairly simple and ED could incorporate it into their code should they choose. In the meantime, you could install QVFR and if you don't like it, you can disable it for DCS... but the sleep fix still works. That's what I have done.

Barely enough time to read through the change log.

I have finally been able to get Winwing to understand the issue. They say it will be implemented in a future release.

I've reported the problem to winwing but as usual with any support team, we usually understand their products more than they do plus the language barrier.... I don't have high hopes. It would help if you also reported the fault.

It's not the device you need to roll back but the Oculus PC app. You can also run DCS with SteamVR using the latest SteamVR beta or you can use Virtual Desktop.

I have tested this further. This is indeed the cause. If sharpening is set to Disabled or Normal I don't see the shudder. Only when it is set to Quality do I experience the shudder with fast moving parts of the image. Thanks for the tip off!

Has anyone got the screen backlight adjustment to work from the DCS F-16 cockpit "Data Entry Display" lighting dial (see the first image)? I can control the ICP console illumination (button text, etc) via the DCS F-16 console brightness cockpit control but not the DED screen backlight. See the second image. I have configured it correctly in Simapp Pro, and I am using the latest on the latest release of the app.

Just plug a cable in from the headset to your pc and use the oculus app to create the link. If your motherboard is capable it should power the headset but the headset will still drain but slower. Alternatively get a powered cable from Amazon.

Have you had a look at the QVFR log file for any clues? Have you read through the trouble shooting guide? Troubleshooting · mbucchia/Quad-Views-Foveated Wiki (github.com)

Easy. Fly west in the morning and east in the evening.

That’s interesting. I have been seeing a shudder much as though the system is in ASW but the frame rate is still at 72Hz so couldn’t possibly be in ASW. I noticed it turning during taxi on the Persian Gulf Ready On Ramp mission for the F-16. I’ve been trying to capture a video of it but it doesn’t show in the video. I disabled sharpening in the Oculus link yesterday and it seems to have solved it. I want to do more testing to confirm though. I had it set to quality, I need to test more with it disabled and again with it set to “low”. It’s certainly less sharp with it off but it can be compensated with in-game sharpening to a degree. I’m glad it wasn’t just me seeing things!

A new version of the Thrustmaster TARGET software is available which is now Windows 11 compatible. New Features in T.A.R.G.E.T V3.0.23.1205_rev1 - Win 11 support with new driver compatible with Memory Integrity - Increase max buttons of Thrustmaster virtual device from 32 to 120 Viper TQS Mission Pack - Thrustmaster - Technical support website

UPDATE: Support for the JF-17 added courtesy of @Tigershark2005! Please refer to the first post in the thread for instructions and download details.

Except it isn't fixed. It's a workaround. Meta will release v63 to everyone in the coming weeks and will likely have this change in it still. They forced Steam to change their VR code to comply with their changes and I expect they will expect all other vendors to follow suit. I expect ED will have little choice but to make adjustments. Hopefully, it's a minor change to make as Steam produced a fix fairly quickly.

A temporary workaround is to disable PTC in the Oculus app and hope it downgrades the software back to v62. This is only temporary though as Meta is likely to push this out to all users in the next few weeks. They forced Steam to change their VR code so I expect that they expect all VR vendors to follow suit. This is likely something ED will need to address.

That's only a temporary solution though. Meta forced Steam to change their VR code in the last couple of weeks. I expect they expect all VR companies to follow suit. It's only a matter of weeks before Meta push this change out to everyone whether or not they are on the PTC.