slughead

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.

@BIGNEWY I think this is still worth DCS looking at in case Meta has decided to make a permanent change. Considering that they forced Steam to change their VR code in the last couple of weeks, I expect they will also expect ED to follow suit as well.

Update: rolling back just the Oculus app solves the problem (i.e. opting out of PTC on the app and not the headset). Using the PTC, the Oculus app was updated to v63 whilst the headset remained v62. I have raised the issue on the atmeta support forum: PTC v62: Oculus app updated to v63 headset update ... - Meta Community Forums - 1152703 (atmeta.com)

That's normal as the second column of 5 LEDs have no function.

Ok. I don't get a GPU driver crash prompt. I don't see DCS screen in the headset - the new PTC has changed this. It now shows all your recently run apps and displays a swirling circle on the ones that are loading. DCS does not remain in the task manager - it is killed automatically or by itself so there is no hung process to terminate that I could see. It would seem that the behaviour for you is a bit different to mine. Maybe because you are using AMD and I am using NVidia. I'll test again later today to see if I can get anymore information out of the system/process.

@SkateZillaI can't work out what you are trying to demonstrate or what you expect the outcome to be as you've not stated what you expect it to be. For sure, I expect Meta's change to affect many applications. For example, they recently made a change that broke SteamVR which was subsequently fixed in a SteamVR beta build.

Are you sure it's not VR only? The latest Oculus PTC is causing DCS to crash just after the splash screen.

I've stopped using QVFR with my 4090. I found it is causing more CPU load than without it and reducing performance. @piolin23000VD sets render resolution for you depending on your choice, e.g. god mode etc. With the Oculus link, you must set it yourself via the slider in the Oculus settings or via the PD setting in DCS. I prefer to set the PD setting to 1.4x and leave the render resolution to 1.0x in the Oculus config. Changing the render resolution in the Oculus setting sets it for all applications using the link whereas setting it in DCS sets it only for DCS. That way I can adjust it per app as needed.

@Flappie no zip files produced. Let me know if there is anything else I can do to help.

Same thing happened with SteamVR and Oculus v62. Steam had to fix it on their end. Looks like we are going to need a DCS side fix before Meta make this a general release. Probably best not to mark this as solved… as it is going to come back when Meta push this out to all users.

I have had this today and thought it was due to an Oculus update. I reverted back from the PTC to normal release of v62 and DCS loaded fine. I haven’t tried again with the PTC version of v62 however my DCS log ended exactly the same as yours has. I raised the error in VR bugs section. 2D worked ok though.