Lange_666

You might be running the ST version thinking it's MT. To be sure just check the bottom right of the menu screen. If there is just the version number (2.9.0.46801 in this case) you're running ST. The MT version has Multi Thread Preview in front of the version number. Then you should be able to select DLAA under the Anti-Aliasing options. Not needed, i'm still running 516.94 and have all the options available (BTW, latest nVidia driver 545.xx causes a bit of stutter in my setup).

Are you aware that DCS itself is limited to 180 FPS by default in its graphics.lua (maxfps = 180)?

Home tab:

Sidenote: Actually the photo was taken from a 2de hand website where you can sell your unused stuff. Demanding price for the card: 1€. Bid offerings accepted from 0.01€

I'm still running 516.94 and i have all options available (tried 545.xx but that one gives stutters).

No it's not because of the Q3. I have the same with my Rift-S. When i change the Turbo setting in MT, ON or OFF doesn't matter, 8/10 it freezes and then DCS crashes. But there is a workaround to set it to ON. Just set it to on in ST. Since the toolkit settings are shared between ST and MT, next time you run MT Turbo will be on and it will not crash.

Do you run OpenXR Toolkit? In it, setting Turbo Mode to ON removed my stutters in MT. Comes with a bit of a drawback because there's a bit if "small" black banding flickering on the edge of the FOV when moving your head quickly (Rift-S, not a Q3).

If you only see Version 2.9.0.46801 then you are running the ST version. MT version can be run if you use the DCS.exe from the bin-MT (in your DCS install directory) instead of the one in then bin directory.

From the link: NEW: Added support for Nvidia DLSS. Using upscaling, Deep Learning Super Sampling (DLSS) can dramatically improve game performance if you are Graphics Processor Unit (GPU) limited. Multi-Threading must be enabled to enable DLSS. Please note that if your CPU is limited, DLSS will have little to no performance effect. Owners of Nvidia 20-, 30-, and 40-series graphics card will most benefit from this. With DLSS selected as the Upscaling option, you can further refine quality versus performance with Quality, Balance, Performance, and Ultra Performance presets.

Ah well, i'm one of those guys then that "never" reads the news there. I just read it here on the forums.

From the above link: NEW: Added support for Nvidia DLSS. Using upscaling, Deep Learning Super Sampling (DLSS) can dramatically improve game performance if you are Graphics Processor Unit (GPU) limited. Multi-Threading must be enabled to enable DLSS. Please note that if your CPU is limited, DLSS will have little to no performance effect. Owners of Nvidia 20-, 30-, and 40-series graphics card will most benefit from this. With DLSS selected as the Upscaling option, you can further refine quality versus performance with Quality, Balance, Performance, and Ultra Performance presets. WIP

Problem is that i lack the connection box on the left...

game launcher..?

It's best not to have it enabled to avoid issues when entering a mission. It can start with the values of the previous flight until you touch any of the controls. Only then they sync to your current mission. Also, your controls setup is shared between ST and MT. If you set "sync with HOTAS at mission start" in ST it will also be set in MT and vice versa.

Some extra info: https://www.reddit.com/r/PicoXR/comments/11tyvxb/how_to_play_pico_4_with_usb/ and

Out of my head because i don't have my Pico anymore: For VD I needed to set up a wifi connection first and then switch to a link cable (and then you get a 1200Mhz stable connection). Starting from scratch directly with a link cable didn't work somehow. But once setup, you don't need to repeat this process unless VD loses the link configuration somehow on startup (did happen now and then, never figured out why). There are various video's on how to set it up on Youtube. PS: I don't own a Pico anymore because of the need of running at it's native refresh rate to overcome visual artifacts and that was not possible on my system "all the time in each and every scenario". ASW as a trade off didn't work as good as with the Oculus Rift-S, way to much artifacts compared to the clean Rift-S image. So i send it back.

VD should work fine with both cable link and wifi on the Pico 4.

I saw the tittle of the post, read it and thought... let's have a go. For me there is no difference in take-off distance between 2D or VR both ST and MT (tried the A-10C first, then a few others). (latest OB version)

I don't think it's a DCS issue but a standalone headset issue (no matter what brand) when not running on max FPS setting on the selected refresh freq.

Because the search function only searches in the selected controls profile. For me (personal opinion) a lot of module controls should be offloaded to the General profile instead of being repeated in each module like the view or camera controls. I wonder how many people set up their zoom controls "differently" for each aircraft/module? VR zoom is common for each module, so why not other stuff that is generally common on each module? Same goes for the names used for certain controls which are different on some modules but act or do exact the same thing.

You can find it under the UI Layer in the controls section. Toggle VR Spyglass Zoom Toggle VR Zoom

C:\Users\*Your Name*\Saved Games\DCS Updater Utility

Having the same problem with my HS 70 Pro Wireless, also on the inside of the headband. Used a wired Sennheiser before the HS70 which didn't had that problem at all. Also, Corsairs iCUE software needs to be running and open and the headset needs to be selected to see the battery level. However, iCUE is not needed to use the headset. Wireless connection sometimes is instant, sometimes it takes up to 20 secs before the connection is established. I'm not impressed.

I have version 56.0.0.109.155 running at the moment but i guess the update i'm blocking is the one you have right now.

Works fine (Rift-S) in both ST and MT OpenBeta versions. Must say that i'm not on the latest Meta software, i'm still on 56.xxx and i block the update until i know there are no issues with it. Blocking the Meta update: Simply browse to C:\Program Files\Oculus (or your Oculus install path) Create a new file called Staging (with no extension) Create a new file called tmp (also, no extension) rename folder \Staging to bak.Staging rename folder \tmp to bak.tmp