Oculus SDK 0.8 + Horizons 64bit + Win 7 64bit + SteamVR = Formula for success finally!

Hello guys,

first of thanks Thorvald for the tutorial. I couldn't get the DK2 running on Win 10 without your guide.

I'm using a R9 Nano, which is a smaller Version of the ATI Fury card. The Nano gives me wonderful performance in regular gameplay without the DK2. But it seems too weak for VR, since i can barely play on lowest settings without studder in stations and near to planet surfaces. I set my monitor and the ingame settings to 1024x768 and 75Hz.

My question is, what performance can I expect of a Nvidia 980Ti OC with the DK2? Would I be able to use 1,5 or even 2 times supersampling, and could I switch to high/ultra settings without studder in stations and on planets?

Edit: CPU is i7 6700K and 16 GB of 2400 MHz ram. OS is Win10 64 bit.

I would say yes. I just have a ge force 980 I OC'd some and that works well even on surface although you will get some frame drops on the surface
 
Is there any reason to use sdk .8 over .6?

I'm asking because I'm using .6 and recently, for some reason, direct mode has begun to work for me. I could never get it to work before but now it suddenly does. I"m wondering if there's any reason for me to risk changing my setup to sdk .8.
 
Is anyone successfully getting Reshade/Sweetfx working with Steamvr+win7+.8+horizons64?

Crashes for me

Code:
11/01/2016 19:26:38:843 [09732] | INFO  | > Found 360 match(es). Installing ...
11/01/2016 19:26:42:075 [09732] | INFO  | > Installed 360 hook(s).
11/01/2016 19:26:42:470 [03464] | INFO  | Redirecting 'CreateDXGIFactory2(0, {50C7F8E9-A63F-4035-9801-B96E733347DE}, 000000004DF0AF10)' ...
11/01/2016 19:26:42:470 [03464] | ERROR | Unable to resolve hook for '0x000007FEE8A32D20'

This might be one reason to revert to .6 apparently sweetfx makes the view in the Oculus substantially better. :\

https://forums.frontier.co.uk/showthread.php?t=117345
 
Is there any reason to use sdk .8 over .6?

I'm asking because I'm using .6 and recently, for some reason, direct mode has begun to work for me. I could never get it to work before but now it suddenly does. I"m wondering if there's any reason for me to risk changing my setup to sdk .8.

To be honest, if it's working great with .6 and you don't play any other VR games, stick with .6 and enjoy. Unless you like mental anguish like the rest of us in the thread messing around with SteamVR and SDK 0.8 lol.


The primary reason I went to 0.8 was I wanted to play other VR games. While ED has stayed back with .5/.6, most others have moved on and support later SDK's or even require them. I could not get Project Cars to run at all unless I installed SDK 0.8. So I wanted to find a way (short of the SDK switcher util) to get ED running under 0.8 and other other helpful threads were a start but no one had consolidated "all the steps" into a single post that I could follow like a checklist.... so after wasting a good night chasing down all the threads on Reddit, here and other places, I made my own "nearly complete" list for others to follow.

Cheers!
 
Last edited:
great work Thorvald

No matter what I did I could not get SteamVR working with Oculus runtime v0.8. So I decided maybe I should do a full clean up and remove all Oculus relevant data from my computer.
Well the full clean did it, SteamVR, Oculus runtime 0.8 and ED all playing together now.
if it helps anyone the steps below are what I did to clean my computer of Oculus data.
Note: these steps will remove your Oculus user settings, meaning you will need to run the Oculus config setups again

Full clean up steps:
1. uninstall all Oculus runtime SDK
2. uninstall SteamVR
3. reboot PC
4. remove any Oculus folders under "\Program Files (x86)" and "\Program Files"
5. remove Oculus folder under %AppData%\Local
6. remove all %SystemRoot%\System32\LibOVRRT*.dll
7. remove all %SystemRoot%\SysWOW64\LibOVRRT*.dll
8. remove OculusConfigUtil.lnk under %PROGRAMDATA%\Microsoft\Windows\Start Menu\Programs\StartUp"
9. in Windows Registry (using regedit) remove [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Oculus VR, LLC\Oculus Runtime]
10. reboot PC
11. install Oculus runtime SDK 0.8.0.0 under "Program Files", NOT "Program Files (x86)"
12. reboot PC
13. reconfigure Oculus
14. install SteamVR
15. after SteamVR installed - select "beta - SteamVR Beta Update", and wait for update to complete
16. reboot PC
17. start SteamVR and run room setup wizard
18. with SteamVR running start ED and configure ED graphics as per what Thorvald posted on the 1st page of this post
19. done!
 
First of all, thanks for the details on how to make it work.

Second: How the hell is it possible that Frontier tells us to use an extremely outdated version of the SDK because they can not figure out how to make it run and they don't even know if they will ever support the final Rift.
At the same time DK2 works fine when having steam VR, it's like a secret thing users had to find out.

What the heck is going on ?
 
First of all, thanks for the details on how to make it work.

Second: How the hell is it possible that Frontier tells us to use an extremely outdated version of the SDK because they can not figure out how to make it run and they don't even know if they will ever support the final Rift.
At the same time DK2 works fine when having steam VR, it's like a secret thing users had to find out.

What the heck is going on ?

Hahahaha Nice question, but Frontier has the excuse. No Comment!!!!

indie Developers made their Support for SDK0.8 at home, Frontier with their HUGE TEAM they cannot do nothing!!!

For Now(I Hope) They don't care about this section! STOP

[Long Breath]
 
First of all, thanks for the details on how to make it work.

Second: How the hell is it possible that Frontier tells us to use an extremely outdated version of the SDK because they can not figure out how to make it run and they don't even know if they will ever support the final Rift.
At the same time DK2 works fine when having steam VR, it's like a secret thing users had to find out.

What the heck is going on ?

They don't have time to work on this. Don't get too carried away with your own sense of entitlement.
 
THIS IS MY 3DMARK RESULT. Download the benchmark, run it. If your result are higher you won't have any problems, above 10000 in that test is a good playing RIG.
Bare in mind that now we are all trying configurations to bypass the fact that elite doesn't support the recent SDK0.8. if you install SDK0.5 you will be flying around without any issue, but then you might loose the possibility to Play 90% of the demos available.
SDK0.8 is Muuuuuuch more performing than the SDK0.5, if Elite will switch to 0.8 I think everything will be butter smooth!
Highest of 3 runs for me was 12400ish on 2x gtx670 /i7 3820. I can do 1.5 ss on med/low settings on planets with minimal SLi latency on ORT 0.6.
 
Last edited:
Right clicking on "Elite Dangerous: Horizons" in my Steam library.

I can't rep you any more, but wow that makes a difference.

For all that aren't running a through steam downloaded version of Horizons and aren't satisfied with the performance, do it! That's a whole new world!
I was able to switch to medium and high settings with 1.5 supersampling activated in most situations.

Thanks to all of you for this wonderful thread,
Cheers!
 
For those of us still having issues with monitor refresh rates locking the ones on the Rift, simple solution:

Change your monitor display ratio to any 16/10 resolutions - Ex 1680/1050

Problem solved.

Longer answer: The SteamVR wrapper somehow carries the monitor refresh rate when the monitor is in a 16/9 display ratio. Setting it to a different display ratio solves the problem.
 
Ok I finally got it working, don't know if this will help anyone but what I was doing differently is I install things in their own directory on separate SSDs, I don't install in default directories. When I installed the Oculus runtime in the default directory it worked.

Now I've got judder when there are other ships in the area (low settings) but I'm waiting for my 980Ti to come back from RMA.
 
I can't rep you any more, but wow that makes a difference.

For all that aren't running a through steam downloaded version of Horizons and aren't satisfied with the performance, do it! That's a whole new world!
I was able to switch to medium and high settings with 1.5 supersampling activated in most situations.

Thanks to all of you for this wonderful thread,
Cheers!

What hardware and drivers are you using to be able to enable supersampling? I get good results with my standalone installation but cannot enable supersampling without judder.

If I am already running horizons standalone, with rift 0.8 drivers and utilising SteamVR (without actually launching steam), are you saying that I will see an improvement if I migrate Horizons fully into steam?
 
Last edited:
Another issue I'm finding ... when resetting the centre position in game (F12) it works for few times, but doing it again the screen will go a pail colour and the Rift loses sync with the camera. Anyone know why this is occurring and / or how to fix it?

The only way I can solve this is to exit the game and launcher and reset the Rift via configuration.
 
Last edited:
Firstly thanks to the OP, this has been hugely useful. I'm currently developing a vr game using runtime 8 so not having to change runtimes to play ED is really helpful. Its running really well via steam on windows 10 now!

The only problem I now have is the black smearing is back as I cant alter nvidia colour settings for the rift in direct mode. Is there any work around to alter colour settings? Will reshade or sweetfx work? Or will it just effect the monitor window?
 
Scratch that.... everything is very smooth, except planet surfaces which are now utterly unplayable :( Guess I'll head back to runtime switching.
 
Back
Top Bottom