Jump to content

Recommended Posts

Posted
3 hours ago, markturner1960 said:

I ONLY use the resolution multiplier in the main oculus software, nowhere else, PD at 1 in DCS. Use DFR to bump up image quality in the middle if you can. 72 hz with ASW forced works very well for me.

Do you notice any difference between using oculus res multiplier and additional multiplier with QVFR? For example with QP oculus res of x1.5 would give you the same as QVFR centre res of 1.5. Is it better to set OTT to 1.5 and QVFR to 1.0 or vice versa; or a mixture? I have tried a variety of options and can't really see any difference. It seems cleaner though to keep the multiplication in one place only. 

PC specs: 9800x3d - rtx5080 FE - 64GB RAM 6000MHz - 2Tb NVME - (for posts before March 2025: 5800x3d - rtx 4070) - VR headsets Quest Pro (Jan 2024-present; Pico 4 March 2023 - March 2024; Rift s June 2020- present). Maps Afghanistan – Channel – Cold War Germany - Kola - Normandy 2 – Persian Gulf - Sinai - Syria - South Atlantic. Modules BF-109 - FW-190 A8 - F4U - F4E - F5 - F14 - F16 - F86 - I16 - Mig 15 - Mig 21 - Mosquito - P47 - P51 - Spitfire.

IMG_0114.jpeg

 

Posted (edited)

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.

Edited by AhSoul

[sIGPIC][/sIGPIC]

Soul's pit thread

Posted (edited)
On 2/7/2024 at 2:56 PM, Qcumber said:

Do you notice any difference between using oculus res multiplier and additional multiplier with QVFR? For example with QP oculus res of x1.5 would give you the same as QVFR centre res of 1.5. Is it better to set OTT to 1.5 and QVFR to 1.0 or vice versa; or a mixture? I have tried a variety of options and can't really see any difference. It seems cleaner though to keep the multiplication in one place only. 

Cant say I have done any comparisons....but have always tried to keep it simple. Too many people sampling up and down in 3 different places,, how can you tell what is doing what? Accepted wisdom is leave DCS PD at 1.0, set the overall resolution in the Oculus software ( I dont use OTT ) for me, this is as far right as the slider goes @72Hz. Then just use QVFR to supersample the image you look at, thats it. Works for me, looks very good and I have no performance issues at all. 

@ahsoul: mostly I am CPU bound. Currently DCS runs better with AMD chips than Nvidia, the X3D series is teh chip to get for DCS. Apparently it simply does not utlise the thgreads very well, so no point in having 16 super fast threads, its better to have more cache 

Edited by markturner1960

System specs: PC1 :Scan 3XS Ryzen 5900X, 64GB Corsair veng DDR4 3600, EVGA GTX 3090 Win 10, Quest Pro, Samsung Odyssey G9 Neo monitor.

CVW-17 Profile Background VFA-34.png

Posted
1 minute ago, markturner1960 said:

Then just use QVFR to supersample the image you look at, thats it. Works for me, looks very good and I have no performance issues at all. 

That's part of my point. QVFR sets the resolution in the same way as using oculus tray tool. Is it not better to use OTT at 1.5 then leave everything else (including QVFR centre) at 100%/1.0? 

PC specs: 9800x3d - rtx5080 FE - 64GB RAM 6000MHz - 2Tb NVME - (for posts before March 2025: 5800x3d - rtx 4070) - VR headsets Quest Pro (Jan 2024-present; Pico 4 March 2023 - March 2024; Rift s June 2020- present). Maps Afghanistan – Channel – Cold War Germany - Kola - Normandy 2 – Persian Gulf - Sinai - Syria - South Atlantic. Modules BF-109 - FW-190 A8 - F4U - F4E - F5 - F14 - F16 - F86 - I16 - Mig 15 - Mig 21 - Mosquito - P47 - P51 - Spitfire.

IMG_0114.jpeg

 

Posted (edited)

No because OTT will supersample the whole rendered scene, QVFR only renders a small part at the increased rate, so giving performance gains. You could possible gain even more by ONLY using QVFR if you needed the extra headroom. 

Edited by markturner1960

System specs: PC1 :Scan 3XS Ryzen 5900X, 64GB Corsair veng DDR4 3600, EVGA GTX 3090 Win 10, Quest Pro, Samsung Odyssey G9 Neo monitor.

CVW-17 Profile Background VFA-34.png

Posted
35 minutes ago, markturner1960 said:

No because OTT will supersample the whole rendered scene, QVFR only renders a small part at the increased rate, so giving performance gains. You could possible gain even more by ONLY using QVFR if you needed the extra headroom. 

 

Yes, but QVFR also reduces the sampling in the periphery. Therefore, if you increase in OTT you are then decreasing in QVFR. The QVFR discord (RIP) advised not sampling above 1.1 in the centre and using OTT (or similar) to SS. However, I found that I get the same results by using QVFR to SS just the centre region. So SS in one place would then suggest leaving OTT at 1 and SS with just QVFR in the centre only.  

PC specs: 9800x3d - rtx5080 FE - 64GB RAM 6000MHz - 2Tb NVME - (for posts before March 2025: 5800x3d - rtx 4070) - VR headsets Quest Pro (Jan 2024-present; Pico 4 March 2023 - March 2024; Rift s June 2020- present). Maps Afghanistan – Channel – Cold War Germany - Kola - Normandy 2 – Persian Gulf - Sinai - Syria - South Atlantic. Modules BF-109 - FW-190 A8 - F4U - F4E - F5 - F14 - F16 - F86 - I16 - Mig 15 - Mig 21 - Mosquito - P47 - P51 - Spitfire.

IMG_0114.jpeg

 

Posted
54 minutes ago, markturner1960 said:

@ahsoul: mostly I am CPU bound. Currently DCS runs better with AMD chips than Nvidia, the X3D series is teh chip to get for DCS. Apparently it simply does not utlise the thgreads very well, so no point in having 16 super fast threads, its better to have more cache 

 

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....

[sIGPIC][/sIGPIC]

Soul's pit thread

Posted (edited)
On 1/15/2024 at 4:49 PM, AhSoul said:

I'm wondering about the 4080 Super about to come out. It's like 1/2 the price of the 4090 and I guess can't be thaaaaaat far off in terms of power?

Big difference in both price and performance. 

image.png

Edited by MIghtymoo
  • Like 1

Intel i9 13900K | RTX4090 | 64 Gb DDR4 3600 CL18 | 2Tb PCIe4.0 | Varjo Aero | Pico 4 on WIFI6e | Virtual Desktop running VDXR

Posted (edited)
2 minutes ago, MIghtymoo said:

Big difference in both price and performance. 

null

image.png

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

Edited by AhSoul
  • Like 1

[sIGPIC][/sIGPIC]

Soul's pit thread

Posted
1 minute ago, AhSoul said:

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

 

Congrats 😀

Sure it will serve you well. This VR hobby can be crazy expensive.

  • Like 1

Intel i9 13900K | RTX4090 | 64 Gb DDR4 3600 CL18 | 2Tb PCIe4.0 | Varjo Aero | Pico 4 on WIFI6e | Virtual Desktop running VDXR

Posted
4 minutes ago, AhSoul said:

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

 

Make sure you also include the cost of a new case in that budget

Screenshot_20240209-103047.png

Modules: Wright Flyer, Spruce Goose, Voyager 1

Posted
45 minutes ago, unlikely_spider said:

Make sure you also include the cost of a new case in that budget

Screenshot_20240209-103047.png

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!

  • Like 1

[sIGPIC][/sIGPIC]

Soul's pit thread

Posted

Next update - swapped my 12600KF i5 out for a 14700KF i7. My 3DMark scores have gone up, but doesn't seem to have made much of a difference in DCS.

Have turned QVF and gone back to the FVF in OpenXR Toolkit - it feels like it performs better like that (though I wasn't using the default QVF settings so could go back to those and see).

If I want to fly more complex modules like the Apache at the graphics setting I want to make the game look decent, I have to either use ASW 45/90 (which actually looks really bad in the Apache with the rotor blades and shadow) or use DLAA and target 72FPS. DLSS gives a lot more headroom but looks too blurry for me.

Honestly feels like everything is a compromise, unless you're running a 4090 and an 7950X3D. I guess I'll stick with how things are now until the 5090 comes out, then build a new system at that point.

[sIGPIC][/sIGPIC]

Soul's pit thread

Posted
14 minutes ago, AhSoul said:

Honestly feels like everything is a compromise, unless you're running a 4090 and an 7950X3D. I guess I'll stick with how things are now until the 5090 comes out, then build a new system at that point.

Unfortunately that is DCS VR at the moment but it has improved since I started a year ago and there is the potential for further improvements. 

PC specs: 9800x3d - rtx5080 FE - 64GB RAM 6000MHz - 2Tb NVME - (for posts before March 2025: 5800x3d - rtx 4070) - VR headsets Quest Pro (Jan 2024-present; Pico 4 March 2023 - March 2024; Rift s June 2020- present). Maps Afghanistan – Channel – Cold War Germany - Kola - Normandy 2 – Persian Gulf - Sinai - Syria - South Atlantic. Modules BF-109 - FW-190 A8 - F4U - F4E - F5 - F14 - F16 - F86 - I16 - Mig 15 - Mig 21 - Mosquito - P47 - P51 - Spitfire.

IMG_0114.jpeg

 

Posted

Yeah hopefully Vulkan etc. will help this year. Part of the issue is simply how many combinations of things there are to tweak. Trying to find the right combination is a fair bit of effort 🙂

  • Like 1

[sIGPIC][/sIGPIC]

Soul's pit thread

  • 3 months later...
Posted (edited)
On 2/12/2024 at 11:20 AM, AhSoul said:

Honestly feels like everything is a compromise, unless you're running a 4090 and an 7950X3D. I guess I'll stick with how things are now until the 5090 comes out, then build a new system at that point.

Maybe you can check 7800X3D instead. I think is cheaper and it performs as well as 7950X3D as far as I have seen in reviews.

Edited by eric.gh22
Posted
3 minutes ago, eric.gh22 said:

Maybe you can check 7800X3D instead. I think is cheaper and it performs as well as 7950X3D as far as I have seen in reviews.

 

I'd have to change motherboard and ram to switch architecture though. I've found at set of settings that keeps me at 72FPS+ with MSAA 2x. I'm having to compromise on visibility (set to High) and some other things, but it's ok.

[sIGPIC][/sIGPIC]

Soul's pit thread

Posted

The 7800X3D is typically faster in games, since the 7950X3D has a hybrid design with X3D-cache only on one chiplet, with a high risk of running the wrong threads on the wrong core.

The 7950X3D is more for if you have a mixed use case and even then you may need to do extra configuration to make things work the best.

  • 1 month later...
Posted
7 hours ago, beacon said:

what is QVF? i have Quest  2 and openxr toolkit and i hve VD can i use QVF? or is it someting for Pico users?

Yes. You can use quad view foveated rendering but only in fixed mode. I've used it with rift s, Pico 4 and Quest Pro. 

It works best with VD so you are already half way there. 

https://github.com/mbucchia/Quad-Views-Foveated

PC specs: 9800x3d - rtx5080 FE - 64GB RAM 6000MHz - 2Tb NVME - (for posts before March 2025: 5800x3d - rtx 4070) - VR headsets Quest Pro (Jan 2024-present; Pico 4 March 2023 - March 2024; Rift s June 2020- present). Maps Afghanistan – Channel – Cold War Germany - Kola - Normandy 2 – Persian Gulf - Sinai - Syria - South Atlantic. Modules BF-109 - FW-190 A8 - F4U - F4E - F5 - F14 - F16 - F86 - I16 - Mig 15 - Mig 21 - Mosquito - P47 - P51 - Spitfire.

IMG_0114.jpeg

 

Posted
5 minutes ago, Qcumber said:

Yes. You can use quad view foveated rendering but only in fixed mode. I've used it with rift s, Pico 4 and Quest Pro. 

It works best with VD so you are already half way there. 

https://github.com/mbucchia/Quad-Views-Foveated

I've tried to use it but it tanked my CPU and I am already CPU bound. But maybe the standard setting are too high?

Meta Quest 3, AMD 9800x3D, EVGA 3080Ti FTW3, Corsair 2x32GB DDR5 6000, ASUS ROG Strix X870E-E Gaming, Samsung 990 Pro 2TB M2 NVME Windows 11 Drive, Samsung 970 EVO Plus 2TB M2 NVME Game Drive

Posted
9 minutes ago, Maddaawg said:

I've tried to use it but it tanked my CPU and I am already CPU bound. But maybe the standard setting are too high?

It does hit your CPU hard. Have you tried foveated rendering in OXRTK?

PC specs: 9800x3d - rtx5080 FE - 64GB RAM 6000MHz - 2Tb NVME - (for posts before March 2025: 5800x3d - rtx 4070) - VR headsets Quest Pro (Jan 2024-present; Pico 4 March 2023 - March 2024; Rift s June 2020- present). Maps Afghanistan – Channel – Cold War Germany - Kola - Normandy 2 – Persian Gulf - Sinai - Syria - South Atlantic. Modules BF-109 - FW-190 A8 - F4U - F4E - F5 - F14 - F16 - F86 - I16 - Mig 15 - Mig 21 - Mosquito - P47 - P51 - Spitfire.

IMG_0114.jpeg

 

Posted

I did, and I thought it wasn't even working. I didn't see any improvement, though I was on Link so I may give it another try today on VD. Though I am mostly happy with VD and it will take a better PC for me to really improve my settings.

Meta Quest 3, AMD 9800x3D, EVGA 3080Ti FTW3, Corsair 2x32GB DDR5 6000, ASUS ROG Strix X870E-E Gaming, Samsung 990 Pro 2TB M2 NVME Windows 11 Drive, Samsung 970 EVO Plus 2TB M2 NVME Game Drive

Posted
1 hour ago, Maddaawg said:

I did, and I thought it wasn't even working. I didn't see any improvement, though I was on Link so I may give it another try today on VD. Though I am mostly happy with VD and it will take a better PC for me to really improve my settings.

I would have thought your i9 10th gen would have enough room for QVFR. According to CPU benchmark it's comparable with my 5800x3d.

What QVFR settings have you used? 

PC specs: 9800x3d - rtx5080 FE - 64GB RAM 6000MHz - 2Tb NVME - (for posts before March 2025: 5800x3d - rtx 4070) - VR headsets Quest Pro (Jan 2024-present; Pico 4 March 2023 - March 2024; Rift s June 2020- present). Maps Afghanistan – Channel – Cold War Germany - Kola - Normandy 2 – Persian Gulf - Sinai - Syria - South Atlantic. Modules BF-109 - FW-190 A8 - F4U - F4E - F5 - F14 - F16 - F86 - I16 - Mig 15 - Mig 21 - Mosquito - P47 - P51 - Spitfire.

IMG_0114.jpeg

 

Posted
23 minutes ago, Qcumber said:

I would have thought your i9 10th gen would have enough room for QVFR. According to CPU benchmark it's comparable with my 5800x3d.

What QVFR settings have you used? 

I think default though I only tried it briefly and was watching the DCS overlay and went solid CPU bound and dropping frames. Do you have any starting suggestions for the settings? I'll give it another try tonight.

Meta Quest 3, AMD 9800x3D, EVGA 3080Ti FTW3, Corsair 2x32GB DDR5 6000, ASUS ROG Strix X870E-E Gaming, Samsung 990 Pro 2TB M2 NVME Windows 11 Drive, Samsung 970 EVO Plus 2TB M2 NVME Game Drive

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...