Hadeda

Is the 10-bit HEVC coupled with the new 2-pass encoding the best codec to use in DCS? I'm struggling to find much useful info about it. Oh, and to stay on topic, my Link cable also stopped being recognised by my QPro about 4 months ago so have been using Virtual Desktop ever since, and am quite happy with it.

I'm talking about warbirds and cold war jets. I don't have any issues locating and locking up bandits in the hornet or viper.

So here's how I've set up my warbird/cold-war PvP profile for DCS: - 2 pixel spotting dots - Keep super-sampling to 1.0 in DCS and one notch below 'god mode' in VD - Quad views off - DLSS off, no anti-aliasing like MSAA - lowered gamma from 2 to 1.8 in the hope it will help bring out bandits a bit more - some basic sharpening in VD but otherwise no further sharpening in DCS settings - running at 90mhz It seems to help but further testing required...

I'm trying to get into warbird and cold-war PvP but struggling to spot bandits and feel I'm at a disadvantage to those with flatscreens. What's the general consensus on optimising your ability to spot planes both far and close in VR? Is a lower resolution always better? Use quad views or not? Upscaling (DLSS) on or off? Does anti-aliasing make it better or worse? Sharpening? Lower Gamma? Using a Quest Pro with Virtual Desktop. Any thoughts on personal experience would be appreciated!

My recollection is that it's a radial from the Bullseye. I think that's clear when you get the radio message while you're in the mission (but not from the briefing). But haven't reflown the mission yet so could be wrong.

And you don't use OpenXR Toolkit either for DFR or FFR? I'm still using that as I can't load Turbo Mode on its own using QV.

I tested it the other day and got very similar results with and without QVFR (using Virtual Desktop). Biggest factor was Turbo Mode. When turned off this had a massive impact on frame times and created a lot of micro stutters.

Is there general consensus that QVFR does more harm than good in DCS? I've been using it with a 5800X3D and 4090 but do get a lot of micro-stutters when looking to the side. Is it better to turn it off (but keep turbo mode)?

My Link cable has completely stopped working, I think since the last update. Have tried another cable and another PC but no luck. The cable is charging the QPro so it is being recognised. I'm guessing it's a software issue. Meta support is looking into it. In the meantime I'm using Virtual Desktop which is working nicely.

Same, couldn't find them on my radar. It would be useful if there was an option to skip to the next trigger point in case the previous one doesn't get activated and you end up flying 'in the dark'

This was at least partly an issue with using HTCC and Slugmouse, which can be partly resolved by reducing the trigger area for these devices. Nonetheless it would be really helpful if the HMD mouse functionality can simply be turned off.

I've been using Slugmouse for a couple of months now and love it. So much more immersive. However, I have a couple of issues. 1) when going to an external view my mouse is still 'tied' to the slugmice, so the view moves around wildly even with the slightest movement of my hands. Quite nauseating! Not sure what can be done apart from re-assigning external view movement to my HOTAS but don't really have the buttons to spare 2) not sure if this is an issue with HTCC or Slugmouse or something entirely different, as I didn't have this issue until recently, but whenever I'm on a menu screen the mouse seems to suddenly link to my VR headset (Q Pro), meaning I have to move my head to the button to activate it. Far from ideal as it can be difficult to physically move my head to get the mouse pointer over the button! What's worse is that movement is in mirror, so left is right and right is left. If I glance at the button from my periphery, I can start using my normal mouse again and get to the button. It's quite a strange and convoluted process! Has anyone else experienced this? Would welcome any thoughts on how to fix these issues.

I'm having the same issue as the OP. I don't want my headset to be tied to my mouse controls but can't seem to switch that off. Very annoying as the direction is also inverted, meaning I have to look the other way to try and get my mouse pointer to move to the Fly, Launch, etc. button! This seems to be a new issue and I'm at a loss as how to fix it.

Thank you! Inverting both X and Y axis did the trick and solved my trim issues. If I could buy you a beer I would :-). Thanks again

Thanks for your response. I've tried different FFB Tune settings for Pitch and Roll, swapping Axis, inverting X and Y, but every time I press trim the stick jolts violently in a seemingly random direction. My force setting is 100 and Shake is 50 (both default). What should the correct settings be? It's not clear to me.