AhSoul

When I first took the 4080S out of the box I had a minor panic attack that it wasn't going to fit I'm now eyeing up 7950X3D builds. But I'd need mobo and ram, so instead of a £380 purchase for the 14700, it'll be like £1250. Eeeeek!

I went for the 4080 Super as I could get a Founders Edition at MSRP and could spend the difference on other upgrades. Then when the 5090 comes out, I'd go full bore at that point

Hmm I was trying to avoid having to go down the route of replacing everything. A 14700 would drop right in. But if that's going to make little difference....

Thanks to all the above! Bit of an update...... I've recently bought a 4080 Super. This has let me do the following: Shift VD to AV1 10-bit (at 200mbps) Move from DLSS back to MSAA 4x Up ground textures from Low to High Bump up visibility distance a notch Turn off ASW DCS looks really good. In my 'reference' mission (F-16 Caucasus Free-flight) a lot of the time I'm nicely at 72FPS. Occasionally I drop into the 60s. When it does, both the DCS and OpenXR Toolkit overlays say CPU bound. I then tried free-flight on Marianas. At the start (before you hit spacebar I'm down at around 45fps). To see if perhaps I'm GPU bound I swapped back to DLSS, but it stays around 45. So is my 12600KF just not up to the task now? I noticed it was using all 4 e-cores so I've used Process Lasso to shift DCS to only p-cores, but that didn't seem to make much difference.

@Qcumber Well apart from the Apache I seem to be fine with MSAA 4x if using 45 ASW and QVFR. I was using DLAA before - DLSS looked too blurry. I think it depends on what I want to change next. Do I want to try and turn off ASW and hit a locked 72FPS, or do I just want to up some other details like render distance to see what happens.

Ok will have a tinker. Seems a bit odd that XRT is showing pretty much 100% headroom the whole time now I'm using QVF. I can't believe that's the case as if I remove ASW I can only get 60-70FPS. On the plus side it's let me go back to MSAA 4x instead of DLAA, and I think the image looks better as a result.

So i just gave this a go - with pretty interesting results. Not changed any of its default configuration and it's definitely a lot more noticeable than the one from XR Toolkit - looking through my HUD I can't just glance down to read the MFDs as they are now blurry. I have to consciously look at them. I assume I can tweak where it kicks in etc.? However seems to be a big performance boost. My GPU is now saying 100% headroom, but it's saying that the whole time which feels a bit odd? Very occasionally I drop below 45fps and XRT says I'm CPU bound then it comes back. Using this lets me fly the F-15 fine now. Though I still can't fly the Apache - still cpu bound and around 30-35FPS.

Pretty good! There's some ghosting, and almost like really small streamers coming off other aircraft in the air at times - most noticeable when the aircraft is against a light background like the sky. I wonder if I should turn off lens effects and maybe bloom (if I've got it on). Not sure if that's encoding/decoding artifacts, or ASW related. But it's very playable and I can read the MFDs etc. If I pick the F-16 Caucasus Free Flight instant action I've generally got 10-15% GPU headroom. When the ground units start getting blown up that can drop to 5%. Will try that QVF tool to see if that gets me some more GPU headroom vs XR toolkil FFV. That would let me turn some other options up again perhaps. Also found https://gitlab.com/NobiWan/xrnecksafer which seems to work pretty well and allows me to see over my shoulder a lot better.

Oh very interesting, thanks! XR Toolkit is saying I've got a reasonable amount of CPU headroom so worth trying. I tried Godlike and 1.0 PD in DCS. Looked pretty much the same as High and 1.3 PD. Performance seemed to stay about the same too.

I then need to figure out how to get the Apache and F-15 to run well. They seem to really struggle vs my other modules (F-16, F-18 etc).

Oh right. I saw 4090 next to Godlike and just assumed I shouldn't pick it! Will see how it goes. I've turned on Fixed Foveated Rendering in XR Toolkit - set to Performance/Wide I think (the defaults?). Seemed to get me maybe 5 FPS when I wasn't using ASW. Is Quad Views FV different?

Oh right. Why does it matter which way round you do it?

Yeah but doesn't it then look a bit crap? I want to play in VR, but not if it looks awful ASW seems to be the way to go if you don't have a 4090 or something. I'm hitting a locked 45 FPS and the headset is running at 90Hz. I'm using High mode in Virtual Desktop, and a 1.3 PD in DCS. DLAA on and a mix of other settings. Running the headset at 90Hz also seems to make things like using the mouse to interact with the cockpit much smoother.

So weirdly I get smoother video over VD wireless than I do over link cable. With the cable I get these pretty regular little spikes in the frame graph, and the image looks like it's 'shifting' or something. I don't get that at all with VD. So with 90Hz ASW to 45, I can put on DLAA and still have GPU headroom with quite a few aircraft. However I can't meet the 45 target with new modules like the Apache or the F-15. Still, this is a significant improvement from where I was earlier!

Not getting the artifacting in VD now. In fact the image feels 'smoother' in VD than it does over link..... I'm now using 90Hz mode, with ASW forced on to lock at 45. Seems to work well. I'll give DLAA a go and see if I can tell the difference. I might also try upping VD to Ultra (I'm on High atm).

I haven't touched that (it has always showed "Oculus is not set as the default OpenXr runtime") and just now with Link Cable I did get the XR menu in game. The only difference was that I ran DCS by double clicking the exe in the bin-mt folder, rather than launching from a pinned icon on the Taskbar (which I created from the bin-mt folder), so bit weird. Running ASW 45 over link cable I could turn off DLSS and turn on 4x MSAA, and the overlay was saying 75% CPU headroom and 0-10% GPU headroom. It looked pretty good! So if I assume I'm going to have to used ASW 45 I guess I now need to tinker again with PD, which aliasing to use etc etc until I get some combination I'm happy with. It looked pretty good in VD with ASW 45 too, though there I would get some rainbow artifacting.

Yes OpenXR Toolkit Companion installed and I get the menu when using Virtual Desktop. Just not when using Link Cable.

I'm trying via Link Cable instead now to see how that goes, and I can't tell if it's using OpenXr or not. The shortcut to bring up the OpenXR ingame menu isn't working which makes me think it isnt?

Tried with the link cable and ASW 45 (with the headset on 90). Definitely felt smoother, though the graphics looks muddier compared to VD, so I assume I need to play about with the Oculus App and Debug settings. Weirdly it doesn't seem to be running OpenXR like it does with VD though. I've used the OpenComposite tool to make OpenXR the default, and in the Oculus app it says the Oculus Runtime isn't the default, and Steam VR isn't running, but I don't get the OpenXR overlays. So I assume it's using Oculus?

Yeah I'm probably getting confused - so many tools to mess with....

But he's setting his FOV Multiplier to 0.65, so must be cropping a massive chunk of the view???

This guy also has a 3080ti, and isn't using DLSS or ASW, and his game seems to be on higher settings than mine with no visible stutter and a solid 72fps. ok his CPU is and i9900 and he has 64Gb of ram though....

Also should I use ASW in Oculus Tray Tool or OpenXR?

I tried ASW at 72 (so halved to 36) and got weird artifacts and stuff. I'm sure when I tried VR ages ago with my Quest 2 ASW gave me crazy ghosting e.g. aircraft or buildings to the side of me. Would things be different at 45/90?

How much VRAM do we need???