Oculus Rift 0.7.0 SDK

callezetter

C
- - Updated - - -

alexjbrandt said:
Anyone have suggestions on how to get Elite Dangerous to show up on the Rift now that the extended display option has been removed? Or do I have to wait for the developers to make a direct to rift display ability?

Any help would be greatly appreciated.

Running Windows 10.
Click to expand...

0.5.0.1 works fine on Win 10 for ED.
 
Last edited:

Apec Valorian

Apec Valorian
seanwasere said:
I don't understand FD's issue here, Euro Truck Simulator 2 works with 0.7 and it is faultless.
Click to expand...

I wouldn't be surprised if FD was secretly sick and tired of Oculus re-inventing their API over and over again, to the point that they decided to hold off trying to keep up with the changes, until it is absolutely positively clear that Direct Driver Mode will indeed be the real deal.
 

doma

D
I wonder if they are just waiting for 1.0 or whats up.

I am still using 0.6 and Elite is the only reason for that. Would so like to upgrade to 0.7

Come on FD!
 

djbordie

D
someone needs to invent a quick runtime switcher, as opposed to uninstalling/reinstalling/rebooting.

i have way too much content for each runtime and just find myself playing mgsV instead of runtime hassles...
 

callezetter

C
There are already quick runtime switchers between 0.5 and 0.7. I use a simple click to swicth runtimes just for ED.
Working on win10, ED, DK2, 290x.

I have two .cmd files I run. Its abit of a hassle to set up, and could be done so much easier if someone will the skills did
a simple ui/program for just this.
 
Last edited:

callezetter

C
I do a dual 0.7/0.5 install like this from a fresh windows 10 system (without any oculus software installed),
and switch between then with two .cmd files.

1. Install 0.5.0.1 runtime (ignore erros)
2. Copy the whole folder "C:\program files (x86)\Oculus" to your desktop
3. Install 0.7 runtime
4. Make two text files 005.txt and 007.txt
5. Edit 005.txt so it look like this (change the "yourusername" to you own):

net stop OVRService
"C:\program files (x86)\Oculus\Tools\DirectDisplayConfig.exe" off
taskkill /f /im OculusConfigUtil
start "" "C:\Users\yourusername\Desktop\Oculus\Service\OVRServer_x64.exe"
start "" "C:\Users\yourusername\Desktop\Oculus\Tools\OculusConfigUtil.exe"

6. Save and rename the file to 005.cmd
7. Edit 007.txt so it looks like this:

taskkill /f /im OculusConfigUtil.exe
taskkill /f /im OVRServer_x64.exe
"C:\program files (x86)\Oculus2\Tools\DirectDisplayConfig.exe" on
net start OVRService
start "" "C:\program files (x86)\Oculus\Tools\OculusConfigUtil.exe"

8. Save and rename the file 007.cmd.
9. Since you just installed the 0.7 runtime (in step 3) you should already have it working. Test the demoscene to make sure.
10. You should also have the oculus folder and the two .cmd files on your desktop.
11. To switch to the 0.5 runtime, first close the oculus configwindow, and make sure you exit it in the taskbar too.
12. Right click the 005.cmd and run as administrator.
13. A command windows pops up and the config windows opens and show that DK2 is ready. Do not close the command window. It needs to be open as long as you run 0.5.
14. Test the 0.5 demoscene to make sure it works. (ignore errors). Test ED :)
15. To switch back to 0.7, first close the command window.
16. Close the config window, and make sure you exit it in the taskbar too.
17. Right click the 007.cmd file and run as administrator.
18. Oculus config windows opens and shows a working 0.7. Test the demoscene to make sure.

To get it working on my AMD R9 290x I have to use the latest 15.9.1 beta drivers

Thats it! Good luck :)
 
Last edited:

callezetter

C
Yeah, its the source of it all. :) And the added taskkill and run "" commands mean you dont have to install a 3rd party program.
 
Last edited:

Nightbringerx

N
When you install runtime 0.5, do you restart?
Or just install 0.5, copy the files to desktop and install 0.7
THEN restart?
 
Last edited:

grammatonfeather

grammatonfeather
Apec Valorian said:
I wouldn't be surprised if FD was secretly sick and tired of Oculus re-inventing their API over and over again, to the point that they decided to hold off trying to keep up with the changes, until it is absolutely positively clear that Direct Driver Mode will indeed be the real deal.
Click to expand...

Given that dk2 is a development kit oculus are perfectly entitled to make numerous changes and updates. Many small VR developers have updated their games and demos for 0,7 so there is no real excuse.
 

Dirtmuncher

D
grammatonfeather said:
Given that dk2 is a development kit oculus are perfectly entitled to make numerous changes and updates. Many small VR developers have updated their games and demos for 0,7 so there is no real excuse.
Click to expand...

I dont know small VR developers are very dependent on their game working on the oculus, elite not so much. Waiting for the release version of the sdk would be great.
I hope they add launch in vr from the launcher menu, because extended mode etc is not so elegant.
 

grammatonfeather

grammatonfeather
Dirtmuncher said:
I dont know small VR developers are very dependent on their game working on the oculus, elite not so much. Waiting for the release version of the sdk would be great.
I hope they add launch in vr from the launcher menu, because extended mode etc is not so elegant.
Click to expand...

Agree. I'm guessing this forthcoming planetary landings won't bring any runtime compatibility upgrade.

I have the 0.7 runtime installed and just run the 0500 cmd (from the reddit runtime switcher v3) to switch immediately to 501 runtime for Elite.
 

Gluksi

G
THX Works for me fine .. i copy the to folders (Windows to windows and the other in program Filesx86) and it works fine. the first time in win 10 and no judder or lagging..
I use sdk 0.8
GF 980 TI @ 358.70 Driver
I7 4790K @4,6
32GB Ram

Sorry for my Englisch :)
 
You must log in or register to reply here.
Back
Top Bottom