Gtx 1080 ti Elite Dangerous

NVIDIA 1080 ti Founders Edition - Think of it in terms of using similar settings as a 1080 - then imagine it owning it like a buttery pixel cannon! No it won't do 2 HMD quality - but that's up against the resolution of the headset anyway, diminishing returns. But 90 fps at stations and planet surfaces at around 1.7 with shadows on ultra gives so much presence! Settings to follow.
 
Last edited:
Think of it in terms of using similar settings as a 1080 - then imagine it owning it like a buttery pixel cannon! No it won't do 2 HMD quality - but that's up against the resolution of the headset anyway, diminishing returns. But 90 fps at stations and planet surfaces at around 1.7 with shadows on ultra gives so much presence! Settings to follow.

YOU EVIL PERSON!

My credit card does not need me to know this...
 
Settings:

xSXzWrN.jpg


- - - Updated - - -

M91wx4o.jpg


i7 4790 k oveclocked at 4600 MHz
16 Gb Hyper X RAM
Z97 PC mate motherboard
500 GB SSD

Rift CV1 touch, sensors etc

Using these settings it's near 90 fps most of the time - as you drop into a station it's wander into the 80's (ASW off) and then back to 90 in a few seconds.
 
Last edited:
I assume it's the founders edition?
How is the fan noise on it?

Last time I had one of those blower cards it got seriously loud.
But then again that was a 6 year old or more AMD, with nominal running temp of 90c..

Ps: what's the rest of the build ?
 
Last edited:
So the spec:

i7 4790 k
16 Gb Hyper X RAM
Z97 PC mate motherboard
500 GB SSD

Rift CV1 touch, sensors etc

Using these I'm getting 90 in the station and on planets, everything's totally clear!

- - - Updated - - -

Yeah it's the FE and yeah the fan noise is loud compared to an aftermarket 1080 - but not with the headset on ofc :)
 
Last edited:
May i ask, do you need the Oculus de-bug tool now that the HMD setting is in the game settings?

If so do you just download it, set the setting of 1.5 to the Pixels, then start the game from the launcher and leave the debug tool running? do you have to start up the de-bug tool then every time you run ED in the future?

Thanks.
 
May i ask, do you need the Oculus de-bug tool now that the HMD setting is in the game settings?

If so do you just download it, set the setting of 1.5 to the Pixels, then start the game from the launcher and leave the debug tool running? do you have to start up the de-bug tool then every time you run ED in the future?

Thanks.

You don't need it per se but i read in the https://forums.frontier.co.uk/showthread.php/121355-Getting-the-Best-DK2-CV1-Vive-VR-Experience-Guide-Compendium thread that the debug tool does it better than the in game setting so I tried that - there's so many variables!

You have to launch the debug before the game.
 
Last edited:
Can I ask how the supersampling interacts?

So you have 1.25 in ED and 1.5 in Oculus.

Is this effectively the same as a 1.875 supersampling?

Just trying to figure how how it equates for Vive.
 
Generally I have found the game gets smoother once the servers settle. Even on Max settings (inc. FX) I get just 45 mostly and 30 at RES & Stations. It does not really feel bad at all. I disable ASW but wonder if its my XEON bottleneck or ASW still has some influence unless totally hacked in registry.

Surely Debug does nothing now and in-game overrides.
 
Last edited:
NVIDIA 1080 ti Founders Edition - Think of it in terms of using similar settings as a 1080 - then imagine it owning it like a buttery pixel cannon! No it won't do 2 HMD quality - but that's up against the resolution of the headset anyway, diminishing returns. But 90 fps at stations and planet surfaces at around 1.7 with shadows on ultra gives so much presence! Settings to follow.

Nice! I'm curious to see when the TI's start making it into the top 50 on 3dmark-- those that waited for TI's were far smarter than I was :)
 
Can I ask how the supersampling interacts?

So you have 1.25 in ED and 1.5 in Oculus.

Is this effectively the same as a 1.875 supersampling?

Just trying to figure how how it equates for Vive.

I'd love to know this too. The Oculus Tray Tool also allows setting Oculus SS values. No idea how these things combine or whether one just one overrides all the others.
 
Last edited:
I have had a nightmare with changing from GTX970 to GTX1080. It worked smooth at first and then inferred with Rift when the last Windows came out last Tuesday. All it needed last time was to RESTART OCULUS but now this has no affect. It no longer switches ASW totally off so it jitters horribly. Once I get the new drivers installed again after wiping them, Gefore Experience just keeps getting lost upon a reboot as the driver does not load. I've now removed Oculus and hoping to get it sorted again once it settles in. I've even had to disconnect the Rift USBs to allow the driver to even install itself again. Any restore history attempts now fail but they do bring back loading the driver and Experience oddly enough. It's not a system I wish to wipe and reinstall as it will take 1 full week of solid work to do.
It really should be easy as Nvidia suggest by simply removing your old card and putting in the new one. It isn't like this. It gave me blank screens straight away as the Rift was still connected. They should try out their advice before dishing it out!
 
Wasp0 said:
May i ask, do you need the Oculus de-bug tool now that the HMD setting is in the game settings?
I can tell you why I need it - I have a tenkeyless keyboard and the de-bug tool is the only way I know to turn off ASW.

X-Terminator said:
Surely Debug does nothing now and in-game overrides.
This is my experience - just tested yesterday.

a.) SS at 1.5 and HMD at 1.0 = looks relatively bad
b.) SS at 1.0 and HMD at 1.5 = looks pretty good
c.) SS at 1.0, HMD at 1.0, and PPD at 1.5 = looks same as b to me, but I also get improved image in Oculus Home and other games (not that I actually play anything else). And as mentioned above, I need to run the tool anyway to disable the horrible ASW.

Note: I tried HMD at 1.5 and PPD at 1.5, just because, and the FPS tanked, but I really couldn't tell much of an image quality difference between that and b or c.
 
First things first.
Why on gods green earth do you buy a keyboard without numpad.

The rest i agree with.
And as has been said by many, and counterclaimed by the less informed, supersampling on vr headsets doesn't really do much for the experience past 1.3 and past 1.5 not really noticeable.
It can't go past panel resolution.

What I suspect happens if you run upsampling of 1.5 in both hmd setting and debug.
The debug tells the game native resolution is 150 for every 100 native pixels.
the hmd resolution setting then takes that and add another 50% to it.
Result is something like compound interest and you could then see an actual upsampling rate closer to 2.25 rather 1.5.

I don't really think it matters to much about where you set it in elite, I just recommend setting it in only one place.
 
Last edited:
Back
Top Bottom