2025 VR benchmark

TL: DR what I have learned.​

  • My local benchmark table cannot be copied over to the forum in one click :,-(
  • Flatscreen resolution does not seem to affect performance (when in VR)
  • SteamVR resolution and HMD quality in-game have comparatively the same effect on performance
  • Other SteamVR options did not influence performance but can affect comfort (motion smoothing, auto throttle)
  • Default VR graphic profiles in ED are not necessarily “optimal” depending on your headset. They are used to get the same baseline if other CMDRs want to add their results.
  • There is a bigger decrease in performance between VR medium and high
  • Large station landing pads are the most demanding of the scenarios tested

Introduction​

I wanted to see if my VR experience is similar to the average.
With many different hardware combinations (computer and VR headset) as well as a lack of real VR benchmark, I went on to establish some protocol to get repeatable measurements.
Having a SteamVR native headset already put me on a specific use case but I think comparing with other compositers (hopefully that is the right word) can still be useful.

My configuration (using a mix of system info and HWiNFO)​

  • Intel i5 12600K @3.7 Ghz
  • 32 GB RAM DDR4 3200 16CL
  • Geforce RTX 4070 (GV-N4070WF3OC-12GD)
  • XPG GAMMIX S70 BLADE NVMe 1TB
  • Bigscreen Beyond VR headset, 3560x3560 100% SteamVR resolution 75 Hz refresh rate

Test protocol​

  • This is what I used and should ideally be followed to ensure consistent results across tests.
  • Put your VR headset on something stable and levelled so that all UI elements are visible in the VR view, this will ensure the viewed scene is consistent across tests.
    This will also make it much easier to alt-tab and note your results after each scenario. You will NOT wear your headset at any time.
  • SteamVR: Click the three horizontal parallel lines on the mini SteamVR UI, enable Display Performance Graph. You should now see your frame time in the mini UI.
    For example mine is at 2.0 of 13.3 ms (75 Hz) when there are no game launched and the Steam home is NOT launched.
  • Game version started on 4.1.0.2 (Odyssey) and will be indicated if different.
  • Use the various training scenarios to help with consistence, those are available at any time from the play menu, under training.
  • Get the frame time after counting 10 seconds from the start of the scenario (after the loading screen).
  • Surface Operation (on-foot tutorial) has two values, flatscreen and VR using the default external camera facing your Commander.
  • Advanced SRV/SLF does NOT benchmark SRV or SLF performance, just the initial situation.
  • "SRV pratice" scenario test SRV performance.
  • Ideally, re-run a few scenarios to see if you get the same results. A complete test loop of all the scenarios took me between 15-20 minutes.
  • In-game time when the tests were run has been indicated. I am not sure how much this can impact the performance in the various systems used in tutorials
  • SteamVR specific
    • Motion smoothing off
    • Throttling behavior fixed 90 FPS, 0 ms additional prediction

Conclusion​

  • A Geforce RTX 4070 is not enough to run ED with the Bigscreen Beyond at its native resolution but an “acceptable” experience can be found by lowering resolution and graphic settings
  • The benchmark scenarios, while diverse, lack specific game scenarios (neutron star, repeatable multi-ship flight/combat, etc)
  • Hopefully people can contribute with their own benchmarks and we can compare results
  • It’s definitely not a perfect protocol, I am happy to take constructive feedback, o7
 
Last edited:
Scenarios(Numbers are in ms)Basic FlightDocking and Travel
(a bit unstable)
CombatMiningAdvanced - CombatAdvanced - SRVAdvanced - SLF (before ship arrive)Challenges
Skirmish
Challenges Wolfpack TacticsChallenges Pirate DefenceChallenges Docking PracticeChallenges SRV PracticeChallenges Intro to VR(a bit unstable)Challenges Surface Operation(Flatscreen and free cam)
3560x3560@75Hz
VR Low 3840x2160@60Hz flatscreen
(02:40 UTC)
Version 4.1.2.000
Windows Game Mode Off
18.0-18.223.9-24.015-3-15.415.9-16.0
3560x3560@75Hz
VR Low 3840x2160@60Hz flatscreen
(19:40 UTC)
Version 4.1.2.000
19.0-19.124.3-24.416.0-16.116.2-16.315.3-15.420.5-20.615.5-15.614.2-14.316.2-16.314.9-1518-18.121.8-2225.8-263.7-.8
19.9-20
3560x3560@75Hz
VR Low 3840x2160@60Hz flatscreen
(05:56 UTC)
Version 4.1.2.000
18.5-18.624-24.315.415.6-15.714.7-14.820-20.215.1-15.214-14.116-16.114.6-14.718.1-18.221-21.226.53.5 (flatscreen)
20.4 external view facing CMDR
3560x3560@75Hz
VR Low 800x600@60Hz flatscreen
(00:00 UTC)
version 4.1.0.2
(all tests below)
19.7-20.024.5-25.015.7-16.016.7-17.016.0-16.221.7-22.015.4-15.615.3-15.418.0-18.216.0-16.218.4-18.622.0-22.227.7-28.04 (flatscreen) / 20.8-21.0 (external view facing CMDR)
VR Medium
(00:30 UTC)
20.2-20.425.8-26.017.2-17.417.8-1816.8-17.023.8-24.016.6-16.816.0-16.218.5-18.716.6-16.819.4-19.622.8-23.028.6-28.84.0-4.2 / 22.4-22.6
VR High
(01:00 UTC)
35.2-35.445.2-45.431.8-32.032.0-32.430.8-31.241.8-42.231.8-32.230.0-30.434.0-34.431.8-32.035.6-36.041.6-42.047.0-48.05.0-5.2 / 39.8-40.0
VR Ultra
(01:30 UTC)
37.8-38.047.8-48.033.0-33.434.033.0-33.244.8-45.033.8-34.032.0-32.435.4-35.633.6-33.838.6-39.043.0-43.250.0-52.05.6 / 44.6
2516x2516@75Hz
50% SteamVR
VR Low
(02:00 UTC)
7.5-7.610.2-10.46.6-6.86.8-7.06.2-6.68.2-8.46.2-6.36.1-6.27.0-7.16.1-6.27.2-7.49.0-9.111.4-11.64 / 8.9-9.0
3560x3560@75Hz
VR Low
HMD Qual 0.75
Effectively 2670x2670
8.6-8.711.8-12.07.2-7.37.1-7.26.7-6.8
2664x2664@75Hz
VR Low
(01:30 UTC)
8.5-8.611.8-12.27.1-7.27.5-7.66.6-6.7
3560x3560@75Hz
VR Low
3840x2160@60Hz flatscreen
(00:30 UTC)
19.5-19.724.6-25.016.4-16.617.2-17.415.8-16.0
2516x2516@75Hz
50% SteamVR
VR Low
3840x2160@60Hz flatscreen
(01:00 UTC)
7.5-7.610.0-10.56.3-6.46.4-6.56.0-6.1
 
Last edited:
Sorry I cannot go into that much detail
I'm old!
But I'll do my best.
Atm and it's working without stuttering or video lag (not talking about elites current micro stuttering that's another issue.)

Amd 7800x3d
Rtx 5080
Pimax crystal light
2tb nvme ( western digital)
64 gig ddr5 ram
Windows 11 24h2
1200w corsair psu

Steam vr resolution 4312x5100 (100%) @ 120hz
I get 60fps according to VRfps which displays it at the bottom of my headsets screens (it's floating)
At planetary ports it drops to between 45 to 50fps.
Doesn't drop at all in space, in fact it goes up to 70+fps.
In orbitals it's a constant 60fps.
Cpu temp is at a constant 60 to 65°.
GPU temp is between 70 to 75°.

If I try to raise steams vr resolution the framerate plummets so l leave it at 100%.
Gpu load according to VRfps is 88 to 98%.
Cpu load is 12 to 18%
VRAM (16gb) it's anything from 12gb to 14.5gb.
PC is hot!
And l have fans running to keep the ambient temp of my bedroom as cool as possible. (Window open as well).
Oh forgot elites settings ingame.
All ultra or ultra+ or high if they don't go further. Basically maxed. Like my eye candy.
Windows I've set power to max performance.
Pimax i have all the bells on inc local dimming. Foveated rendering etc on.
also l use steam vr advanced supersampling. But that other one off. Motion smoother.
The geforce panel is default.


Hope this helps!

o7
 
Last edited:
Sorry I cannot go into that much detail
Thanks for sharing your experience CMDR!
If you have a chance to activate your in-HMD performance indicator (under developer VR settings) from Steam and run a few of those scenarios, we will be able to compare apples to apples.
 
Last edited:
I have updated the testing protocol to be much faster and practical by just leaving the VR headset on a stable surface and reading the frame time from the SteamVR mini UI.
Hopefully non-SteamVR CMDRs have something equivalent to track frame time.

I also changed some wording to improve readability.

With version 4.1.2.000, it seems the frame time might be slightly better on the two batches of test I ran.
I don't get the exact same numbers for each run so it's hard to tell for sure.
 
Last edited:
Time is tight, but here's a quick data point. Generally my settings relate to sub 11.1 ms performance. If there's any downtime for more rigorous data gathering, I'll post again.
 

Attachments

  • Screenshot 2025-05-06 125314.png
    Screenshot 2025-05-06 125314.png
    1.7 MB · Views: 17
Back
Top Bottom