diego999

DLSS = better performance with ghosting. MSAA = better visuals, kills your fps. Pick your poison.

1 - Increasing RAM will help with general stability and avoid memory related stutters, nothing more. Your machine is on the edge of playability for VR, so even if you add 64GB of RAM, overall performance won't improve much. 2 - I don't know as I don't use hand tracking. For me using the head controlled pointer is way better. 3 - Yes. Oculus Desktop app has a built-in test for your cable. 4 - Absolutely. Using OpenXR Toolkit is a must, as it offers fixed foveated rendering. Couple that with Oculus Tray Tool's reduce fov option and you can change your VR experience from miserable to -at least- decent.

It works for me and apparently for the other guy too. You might have some issue there.

It doesn't waste resources as it just mirrors what you're seeing in the headset. There's a trick to reduce DCS resolution on your monitor to something very low (like 800x600, can't remember exactly) for some supposed gain. I tested it extensively, couldn't find any difference in fps or frametimes.

This is good advice. What changed it for me was a stick upgrade. While I had a normal X52, the woobly nature in the center position made it impossible to manage the small inputs you need to stay in close formation with the tanker. Since I changed it for a Thrustmaster, I can fly with a lot more precision. I'm still struggling, but now it has became doable.

The same installation can run both modes, 2D and VR. In my case with a Quest 2, if the headset is powered on and connected to the pc, DCS starts in VR mode on its own. Otherwise the game starts in "normal" 2D mode. If you want to have different graphics settings for 2D and VR, you can do that by presets in the graphic options screen. You don't need a separate install of the entire game.

Absolutely. Just don't go nuts with the settings.

My feelings exactly.

Doesn't matter. The Intel graphics "chip" is too slow compared to a real one. You could assign all your memory to it, wouldn't make a difference. Besides, your "dedicated VRAM" is just regular RAM, way slower than the real VRAM used by a discrete graphics card.

I'd suggest to wait until the new cards are announced soon. Prices will drop hopefully on the normal 4xxx cards, and if they're worth it, you can get one of the supers.

Amazing! I will try your mod tonight.

It's a pity we don't have an medium setting for ground textures. High eats up all your VRAM and low looks really ugly.

I have a Quest 2 but I'll try to help. - I think you can use multiple devices on the same account in the app, or multiple accounts with the same device. - For me cable was always the best option. Any quality USB-C cable will do, all Quest models can use the same one. Airlink in my case was inconsistent, with random stutters and loss of visual quality. VD is better than Airlink, it has more options, but is wireless only so if you want to connect by cable you can't even use VD.

Oh there are people with severe stuttering on a 13900/4090 rig. DCS always finds a way to wreck you, no matter how much hardware you throw at it.

A final trick you can try is limiting the FoV. I don't know how this works on the G2, but with the Quest 2 I play with 0.85 both horizontal and vertical. This option cuts the outermost pixels of the image, saving some GPU power by not rendering, in my case, 15% of the pixels every frame. With the Quest 2 for me that number is the limit. Any more than that and I start to see an ugly black box around the image. But at 0.85 I don't even notice the missing part and I'm saving a considerable amount of pixels that can be applied in the center where it matters. You can try reducing it a bit, say 0.95 and see if you notice it. If not, reduce it a little more. When you see the edges, that's too much.

On top of that I use OpenXR Toolkit Turbo Mode, headset configured in 72hz. I run a PD of 1.3 configured in the Oculus App (I have a Quest 2). The important thing here is to change this setting in one place only: DCS, your G2 sofware or Steam VR in case you're using that version. These settings should be an absolute low baseline for you as your rig is way better than mine (i5 10400, 3060ti). Start cranking one at a time and see how it goes. FPS killers in my experience are MSAA, SSAO, SSLR and clouds on the highest setting. With this I can mantain 72fps almost all the time, except when on the ground or above a city. In SP that is. Multiplayer has higher requirements, specially on populated servers.

No. Tried QVFR but it comes with a noticeable cpu load my old 10400 wasn't capable to bear. This should not be a problem for your 5800X3D. I use OXR Toolkit with Quality/Wide presets. You can try all combinations ingame, as you don't need to restart dcs after changing them. Will post my settings when I get home tonight.

PD is Pixel Density. It provides better visual quality by supersampling the image. IPD is the setting that changes the game scale. That is the way to go with a G2. Due to the fresnel lenses the external part of the image you see on the headset is blurry anyways, so there's no point in wasting GPU power by rendering it at full resolution. QVFR is made for headsets with eye tracking. Your G2 doesn't have that, so it will function in fixed mode. Using QVFR or OXR Toolkit is up to you. Try both and see which one works better. About antialiasing, you can try DLSS with full sharpening (1.0), or no upscaling with DLAA. TAA has very bad ghosting in VR and MSAA is a fps killer. This one is simple, so try all and see what your brain prefers. I can share my settings tonight when I get home if you want.

Forcing AI MiG-21s to not drop their fuel tanks or using afterburner can help in making them more in line with reality. It's a cheap trick really, but it's better than watching them pull sustained 9G without losing speed. For human-piloted MiG-21s, the FM is decent enough I think.

You're supposed to increase PD to compensate. I went from 1.15 to 1.4 with DLSS activated. Displays are readable and the overall performance is better. Gosthing is ugly though.

"Soon" since a month ago. Go figure.

I don't know as I change it with Oculus Tray Tool. Maybe there is something equivalent for the G2? Fixed foveated gave me around 5% increase in performance in Quality/Wide mode (from OpenXR Toolkit). It's not a lot, but is noticeable.

You can try reducing the FoV to at least 85% (something I can barely notice in my Quest 2). You'll be saving 15% of the total pixel count the GPU needs to render every frame. Another useful thing is foveated rendering. Your G2 doesn't have eye tracking, but there is a fixed mode that works very well. Like my Quest 2, your G2 is wasting GPU processing power by rendering at full resolution the exterior part of the image that you see blurry anyways due to the fresnel lenses. Those two settings changed my VR experience from barely playable to very satisfactory. With modest settings that is.

Damn I'm dumb. You will have no issues with the 2080ti / G2 combo.

I played for a year on a 2060. With modest settings, some FOV limiting and not going nuts with mission complexity, I could get a decent performance (72/36 fps with motion reprojection activated, 72 almost all the time except on the ground or flying over cities). With your 2080ti you should have no problems. Which headset are you using?