slughead

There’s another major thread about stuttering and parked cores. You might want to check that one out.

I get some stutters. I don't think we can completely get rid of them. Are you using QVFR? That has turbo mode on by default which eliminates most microstutters. Have you tried the virtual desktop app instead of Oculus Link? The encoders in that might solve the problem but I have yet to get it to perform satisfactorily. To be fair, I'm a bit tired of messing around with changes and just try to get on with flying now. I'll try it again but fairly sure I was still getting them.

I've always said that the default settings are optimal. Alas, I too have not found a solution to the audio glitches. 960mbps actually makes it worse. I expect some are using alternative headphones.

There is a separate thread for foveated rendering. Would you use that, please? Maybe you will find the answer to your question there.

@VirusAM thanks. It's a pointer in a direction at least for me to get started.

Hi. Old thread revival but would you mind sharing your target script, please? I'd like to do a similar thing with the new Thrustmaster Viper TQS to configure the LEDs according to DCS state. Did you ever solve your anti-cheat problem?

This is normal and is nothing to be concerned about. It sounds like you are launching it from within the Oculus Virtual Desktop inside Oculus Link. It also sounds like you haven't enabled VR in DCS. You can launch it from the Oculus Link virtual desktop if you like, but that means you have to use Oculus VR controllers when there is a simpler way. The method below enables you to start DCS without launching the virtual desktop or using the Oculus controllers. First ensure DCS is configured to run in VR mode. You must either select "Enable Virtual Reality Headset" within the DCS Options > VR tab or add --force_enable_VR to the command line in the shortcut that you use to launch DCS. For example, create a shortcut to the DCS.exe, edit the shortcut properties and modify the "target" field to add the command line options to the end of the line as shown below: I prefer not to enable the VR option in the DCS options and instead have two shortcuts for DCS. One for VR and one for 2D so that I can run DCS in 2D to test things such as new releases or to just rebuild the shader and texture caches when a new release is installed without having to put on the headset. Now that DCS is VR-ready, put the headset on and start the Oculus Link from within the headset Settings. The Oculus PC app that forms the PC side of the link should start automatically. Once the link is established, you are presented with a "staging" room. A sort of empty infinity space with a tiled floor and ceiling (see image below). There is no need to interact with this staging room at all. Instead, launch DCS from the VR-enabled shortcut on your PC desktop or Start Menu using your mouse. You will need to peek from under your headset to do this. DCS will then start and the initial login and splash screens will be shown on your monitor. You won't see anything in VR until DCS begins to load the home screen. You should then see that DCS is starting from within the staging room and shortly afterwards the DCS blue sky loading screen and then the DCS home screen should appear inside a hanger in VR.

Have you installed any mods such as quad view foveated rendering, openXR toolkit?

@tonisteam or stand-alone version?

Yeah. I was thinking that as well.

Turn the HUD overlay on in Oculus Link mode. It will tell you what encoder is being used. The Oculus Link HUD overlay is showing H264 for me with everything set to default in the debug tool. I'm running V59 headset and Oculus PC app. So it doesn't appear to be the case for me at least that default is H.265. Where did you hear that it had changed?

Hmm. No, I hadn't noticed. Perhaps that is the cause of increased audio glitches. I shall change it back and see if it improves.

I expect it is self-calibrating.

I'm sticking with Oculus Link.

This is visible to me too on my quest pro using virtual desktop mostly. Not so much in link cable or air link. Yes, I have only seen this using virtual desktop. I thought I'd try VD, it's pants. I'm back on Oculus Link.

My replacement has arrived and works as it should out of the box.

Thrustmaster overrides the Windows facility with their own for the TPR and the Viper TQS. They didn't for the Warthog. When you clock properties for the Thrustmaster devices, the screenshots below show you what is provided. My replacement arrives today! nullnull Recording 2023-10-28 212531.mp4

My unit has been returned to the supplier. They've agreed it is faulty and should be sending out a replacement shortly.

No, because Thrustmaster replaced the default game controller tool with their own.

It's possible that it has an auto-calibration facility. Either way, it's broken and has been returned for replacement. I have seen a couple of other reports of exactly the same fault.

Not as yet.

They both do the same thing. The tray tool will over write the Oculus app. This is why we suggest changing one thing in one place only. Yes. No. Just use the ODT. I just leave it on auto. You'll find leaving most of the Oculus settings on default is sufficient. Don't over think it.

You still need a developer account for the eye tracking to be exported over PCVR link. Follow the instructions on the wiki page for the QVFR app. There's not a lot to it.

Does it have a calibration facility? My effing TQS throttle has just (minutes ago) lost its calibration! 80% throttle at just a nudge from idle and 100% at half travel. Plus button 19 comes on shortly when coming out of idle. I have a feeling it's going to be returned. Not even 2 weeks old!

Exactly. I actually find leaving it on default settings does the job. More is not always better.