VR Performance Upgrade Question

[C3PO]

Hi - but what margin of improvement could I expect the following upgrades when using VR in DCS compared to my current 5800X system with the 3090 FTW3 Ultra card etc..:

Option 1: The same 5800X system as per my sig but upgrading the GPU to an RTX 4090

Option 2. Intel Core i9 14900K, 32GB DDR5, 24GB NVIDIA RTX 4090, 64GB DDR 5 5600MHz

Clearly option 2 will be much faster, but by how much and by what compared to Option 1?

[jurinko]

There is plenty of troubles with Intel CPUs. I went from 3070 to 4080 (on 5600x) and the improvement had been great.

[Nedum]

The 4090 alone will give you an 80% boost with lower temps over your current 3090.

The CPU switch would be something around a 5% - 10% FPS boost. The 14900 is overrated. Stay as long as you can with your 5800X and if you want to switch, go for the 7800X3D. This CPU will beat the 14900 in most games, is a way less expensive and does need only a half of the power.

If you mostly play and mostly Sims, do not go for Intel.

 

[C3PO]

In 95% of lower fps situations, I am GPU bound in VR, so maybe the 4090 is the way to go.

[Gyster]

I'm running an i9-13900k @5.6, 64GB DDR5 @6000, Asus TUF OC 4090 (despite the ridiculous price tag), Samsung Pro 990 2 TB SSD, and with a Pimax 8kx I get about 75 fps as long as I stay above 2km.  For some reason, flying low with the sun at my back, especially over cityscapes, fps drops to 40s.  I have the XRToolkit overlay on but it rarely shows any value above 0.0 for GPU and CPU is usually less than 6ms.  Not sure what to do, but I'll keep tweaking settings.

[Qcumber]

4 hours ago, Gyster said:

  I have the XRToolkit overlay on but it rarely shows any value above 0.0 for GPU and CPU is usually less than 6ms.  Not sure what to do, but I'll keep tweaking settings.

If you have turbo enabled it won't show the correct reading for GPU. 

[Gyster]

7 hours ago, Qcumber said:

If you have turbo enabled it won't show the correct reading for GPU. 

I did, but someone told me about that and turned it off, but still the appGPU hovers around 0.0 to 0.1 ms.  Not sure why as there's no way that's accurate.