Oculus Rifts Running Maxed Settings, please add your hardware here

[tommywright]

Hey guys,
I keep reading of people running OR with everything maxed out. I would love to hear what hardware you guys are running that on. Now when I say maxed, I'm talking every setting on High or Ultra with supersampling at 2560x1440. I consider that truely "maxed out".

Can you take a screenshot from GeForce Experience like this or write this stuff here if you are one of these lucky people?



It will really help me figure out what I should build for my next rig. Thanks so much!

 

[rich_hard1]

I'm running maxed out, but on AMD

Wish I had NVidia cards. They run most VR stuff maxxed plus supersampled.

 

[tommywright]

Oh I should mention that I'm talking about running in Multiplayer rather than SP or a tutorial. I get very different results in a tutorial for some reason.

 

[Adam Lusardi]

Oh I should mention that I'm talking about running in Multiplayer rather than SP or a tutorial. I get very different results in a tutorial for some reason.

Is that Multiplayer with other players in your instance! lucky you.

 

[tommywright]

Is that Multiplayer with other players in your instance! lucky you.

Do you not see other players?

 

[Logical Viking]

Everything maxed out in extended mode (direct worked just as good too). No supersampling because AMD doesn't make it easy until the Omega drivers release this week. FPS is over 200 so I think I'll have the headroom to supersample once it becomes available. I still get an ever so slight judder in stations but it's not down to FPS dropping below 75, thats for sure so it must be something in the DK2 drivers or the games handling of head tracking.

R9 290x No OC
AMD FX-8350 OC'd to 4.5ghz
16gb RAM
Win 8.1
Smasung SSD

 

[Deaks]

Running maxed out in extended mode so I can use supersampling at 75Hz (Direct mode is restricted to 1080 at 60Hz)

Intel i7 4Ghz
Nvidia 980
16 Gigs RAM
win 8.1
SSD / HDD

 

[KING5TON]

Running it maxed out is one thing. Anyone can "run" it maxed out.
Running it maxed out and always getting >75fps in VR in all instances is another thing entirely.
Unless people are using dual or triple GPUs then they're augmenting the truth that they are running it maxed out, they might have all the settings dialed up but they're probably getting judder.
I personally run the game on low at 1080p, you can see my rig below and it's no slouch. It's the only way I can get smooth >75fps gameplay 80% of the time, still get a little bit of judder in stations and rings. Had hoped that FD would improve the performance of the game but I guess that will come after release (ha!).

 

[777Driver]

Running it maxed out is one thing. Anyone can "run" it maxed out.
Running it maxed out and always getting >75fps in VR in all instances is another thing entirely.
Unless people are using dual or triple GPUs then they're augmenting the truth that they are running it maxed out, they might have all the settings dialed up but they're probably getting judder.
I personally run the game on low at 1080p, you can see my rig below and it's no slouch. It's the only way I can get smooth >75fps gameplay 80% of the time, still get a little bit of judder in stations and rings. Had hoped that FD would improve the performance of the game but I guess that will come after release (ha!).

Maxed - No Judder, and SMAA is switched on. Only thing off is Ambient oclusion (What does that do?) Blur is OFF & Bloom is on Low.

I5 2600K Overclocked to 5.1ghz
780TI
Machine only runs ED, no background processes or junk going on. Networked laptop for internet, route planners, forums etc.

 

[KING5TON]

Maxed - No Judder, and SMAA is switched on. Only thing off is Ambient oclusion (What does that do?) Blur is OFF & Bloom is on Low.

I5 2600K Overclocked to 5.1ghz
780TI
Machine only runs ED, no background processes or junk going on. Networked laptop for internet, route planners, forums etc.

I don't believe you.
Take a screenshot in the rift in a station and show you are getting 75fps+

 

[777Driver]

I don't believe you.
Take a screenshot in the rift in a station and show you are getting 75fps+

Well yes, in stations I do feel a decrease in performance, but nothing major, flight feels smooth on approach. My specs are not huge, but my machine is overclocked and background stufff is at a minimum. I could decrease settings, but theirs no point IMHO, I am in dock for 5 minutes to drop of my rare goods after a 150LY trip.

Don't know why the screenshots look blurry, it looks fine in the rift.

In station, pretty much the max strain on my PC, defintely not 75FPS, but smooth enough me at the moment

-

In flight, where I spend 99% om time hauling rare items. It seems I hit 75FPS

 

[SlackR]

My new rig comes in two days...
i7- 5960x (OC'd)
Asus rampage V extreme
GTC 980's in SLI
I bought it with the sole intention of running the DK2 at maxed out settings with supersampling.
If I dont hit 75fps at 1440 I think I will actually cry!

 

[CATPAIN KIRK]

Maxed - No Judder, and SMAA is switched on. Only thing off is Ambient oclusion (What does that do?)

Afaik it doesn't do anything for you atm because it's forced off in the current nvidia ED Profile.

Anyway - running it maxed (1080p blur off UI effects off no AA, Vsync forced adaptive on), but I get framedrops below 75 FPS - especially in some of the posh stations and when running the second window dev hack. It doesn't affect me enough to bother setting the quality lower, though. I7 3930 k @ 4.2 Ghz, dual GTX 680 in SLI.

Spoiler

Edit:
Some Benchmarks (measured at the release of beta 2 when they added SLI support, using fraps, undocking and redocking in the tutorial mission, but that station seems to be optimized - I do worse in stations usually):

2014-10-01 18:56:34 - EliteDangerous32
Frames: 4501 - Time: 60000ms - Avg: 75.017 - Min: 73 - Max: 78

With the 78 being contributed to fraps miscounting due to Vsync issues/rounding error.

Testing on a HD 120 Hz screen, I get this:

2014-10-02 19:09:01 - EliteDangerous32
Frames: 7193 - Time: 60000ms - Avg: 119.883 - Min: 115 - Max: 124

Capping at the screens refresh rate due to vsync.

 

[KING5TON]

Well yes, in stations I do feel a decrease in performance, but nothing major, flight feels smooth on approach. My specs are not huge, but my machine is overclocked and background stufff is at a minimum. I could decrease settings, but theirs no point IMHO, I am in dock for 5 minutes to drop of my rare goods after a 150LY trip.

Don't know why the screenshots look blurry, it looks fine in the rift.

In station, pretty much the max strain on my PC, defintely not 75FPS, but smooth enough me at the moment

I wasn't questioning that you could get 75fps+ in space. I believed that.
When people say "I can run it maxed out and it's 75fps+ all the time" they mean "I can run it maxed out (kinda) and it's 75fps+ except in stations, ring systems and certain other situations".
So my point is true, you can't run it maxed out (which is everything on including AO and bloom) on a single GPU and have 75fps+ all the time.
If you want 75fps+ all the time you have to run it on low @1080p. Even then you might get occasional dips below 75fps.

SLI/Xfire I can believe are able to get 75fps+ all the time with maxed out settings @1080p. I don't believe that even SLI/Xfire can get 75fps+ all the time maxed settings at 1440p or 4k downscaling.

 

[777Driver]

Fair enough mate, but I wasn't saying I could get 75+FPS all the time, I wasn't even aware you could see the FPS counter while in the rift. I just look for general smoothness and enjoyable game play. Hopefully by the time the CV1 is released, I'll have an upgraded CPU and two beast cards running in SLI

 

[onesungmirror]

Judder and fps are not connected directly. You can have high fps and still have judder, which comes from tracking. I have satisfying fps but a lot of stutter and tracking dropouts, orientation and positional. All the quality settings don't make a significant difference. So I think effectivesness of the computing of the tracking is crucial. It may well be that the xeon handles this better despite the "low" frequency. Also raising computing power by overclocking may result in less stuttering independently from the fps.
Also low fps (30 -40) can look very smotth if you have no stutter from tracking.

 

[Obsidian Ant]

The Oculus Image Quality slider makes a massive difference to performance, try dropping it by 2 or 3 steps...

 

[[VR] Mad Mike]

Judder and fps are not connected directly. You can have high fps and still have judder, which comes from tracking. I have satisfying fps but a lot of stutter and tracking dropouts, orientation and positional. All the quality settings don't make a significant difference. So I think effectivesness of the computing of the tracking is crucial. It may well be that the xeon handles this better despite the "low" frequency. Also raising computing power by overclocking may result in less stuttering independently from the fps.
Also low fps (30 -40) can look very smotth if you have no stutter from tracking.

indeed, I really hope that once the preditctive tracking & timewarp oculus are working from is implemented a lot of our stutter issues will simply vanish (AFAIK they are not in yet but correct me if i am wrong)

edit @ granite if you can help it at all, imo it is better to lower any setting you need to in VR but NOT the oculus quality slider.

 

[KING5TON]

Judder and fps are not connected directly. You can have high fps and still have judder, which comes from tracking. I have satisfying fps but a lot of stutter and tracking dropouts, orientation and positional. All the quality settings don't make a significant difference. So I think effectivesness of the computing of the tracking is crucial. It may well be that the xeon handles this better despite the "low" frequency. Also raising computing power by overclocking may result in less stuttering independently from the fps.
Also low fps (30 -40) can look very smotth if you have no stutter from tracking.

Sorry but they are directly connected.
You can have judder issues that aren't related to FPS but in the main when people report judder what they are reporting is that their frame rate has dropped below 75fps.

If you have any judder check your FPS. If it is lower than 75fps then that is the issue. Soon as you resolve that issue the judder will in the main go away. If it doesn't then yes it's another issue relating to tracking or vsync etc.. .

You cannot have smooth VR at 30 to 40 fps that's not correct. 60fps on the DK1 didn't have judder it had smearing. Low persistence fixed the smearing but if you don't hit the target FPS (75) you get judder.

 

[onesungmirror]

Sorry but they are directly connected.
You can have judder issues that aren't related to FPS but in the main when people report judder what they are reporting is that their frame rate has dropped below 75fps.

If you have any judder check your FPS. If it is lower than 75fps then that is the issue. Soon as you resolve that issue the judder will in the main go away. If it doesn't then yes it's another issue relating to tracking or vsync etc.. .

You cannot have smooth VR at 30 to 40 fps that's not correct. 60fps on the DK1 didn't have judder it had smearing. Low persistence fixed the smearing but if you don't hit the target FPS (75) you get judder.

What I'm trying to say is: It is very hard to know what comes from what.
I believe the connection between judder (from tracking) and fps are only connected in the way that a system (CPU & GPU) that doesn't rech high framerates is very likely to have tracking problems too and vice versa. If you restrict elite to one core you will see a massive performance drop in framerate and tracking which is I guess because elite also doesn't run solely on the GPU. Most quality setting however are render related which almost completely is done on the GPU.
There is also a problems with the terms stutter, judder, microjudder, dropouts and so on.
For example: I can have a very constant low framerate which of course will result in the visibility of single frames when I move my head fast, but without tracking dropouts which usually are not regular or happen just every 3rd frame or so (just an example) the whole experience can feel much smoother to some than high framerates with constant tracking stutter (meaning the camera rotation is not updated fast enough).
It all depends on individual perception or to put it like this: what's bugging you most.
I am of course no expert. I'm just trying to say at this moment where the "flaws" come from and what you can do about it. Still collecting as much info as possible is a good idea allthough it may be outdated very soon