Oculus Rift & Windows 10 Thread

[spameroo]

I'm using a 290X, but the only significant architectural difference is the internal "Crossfire" so I'm fairly sure our Catalyst-Win10-E-Oculus compatibility situations are the same. I had the same experience after upgrading to Windows 10; I'd been using a ~1.5x supersample by using regedit to force ED to recognize the resolution options, with the in-game SS left at 1x and the Oculus Image Quality slider somewhere below half.

After I upgraded Windows I also couldn't get that method to work (it wasn't all that easy to get the Rift and Elite to work at all...), so I decided to play around with the in-game SS and Oculus Quality settings. I'm glad now that it DIDN'T work the same, because it turned out I was able to maintain a stable frame rate with 1.5x supersampling (in-game setting), 2x MSAA (in-game setting, not thru CCC) and the Oculus slider up all the way, even with all other graphics options nearly maxxed. And that looks 10 times better than it ever did with the previous (regedit) method. You'll probably be able to go even farther, possibly to 2x SS and/or 4x AA. I have my 290X running at a 5% overclock, but your card should be able to use these settings without overclocking.

Hope this helps! You'll need to play around I'm sure, but IMO start by setting Oculus Quality all the way to the right, because the difference it makes is HUGE.

 

[z4StormShadow]

Great Tips! I'll try this now! I wish they would put out a crossfire profile and fix this supercruze problem.

 

[[VR] Mad Mike]

I'm curious about why people use the power button on the rift itself? I never touched it (errgg, possibly once the day I received the dk2). my DK2 is always plugged, I don't feel the need to turn it off or on as it work as soon as I need it. The device is kept in Direct Mode (so led is orange) and I set it as extended for ED (so it turn blue) Is it for saving some power? do I miss something here?

extended mode does not turn off, and indeed the opposite, it comes on by itsself. once direct is the only mode, i will probably do similar, until then (and i aint upgrading till Elite does) i feel it is good habit to be in to turn it off each time i power on my pc, if i am not using VR.

 

[drkaii]

I'm curious about why people use the power button on the rift itself? I never touched it (errgg, possibly once the day I received the dk2). my DK2 is always plugged, I don't feel the need to turn it off or on as it work as soon as I need it. The device is kept in Direct Mode (so led is orange) and I set it as extended for ED (so it turn blue) Is it for saving some power? do I miss something here?

Yes burnout is bad, don't leave the screens on

 

[[VR] Mad Mike]

To the people upstairs...

Use the 32bit version OVRServer_x86.exe with Windows 10.

Runtime 0.6.0.1 and driver Nvidia 356.04

Works with Elite and iRacing.

i am not computer illiterate... but my mind is fried.

all these guides, do they work for clean, brand new virgin windows 10 installs, or are they based on an upgrade?

is there a guide which walks through it on a brand new machine? looking around there seem to be so many threads and they are all different. thanks

 

[potskomtar]

i am not computer illiterate... but my mind is fried.

all these guides, do they work for clean, brand new virgin windows 10 installs, or are they based on an upgrade?

is there a guide which walks through it on a brand new machine? looking around there seem to be so many threads and they are all different. thanks

This is on my machine , no bibles for computers , every one works diferent.

 

[Karnath]

i am not computer illiterate... but my mind is fried.

all these guides, do they work for clean, brand new virgin windows 10 installs, or are they based on an upgrade?

is there a guide which walks through it on a brand new machine? looking around there seem to be so many threads and they are all different. thanks

I used this method

https://www.reddit.com/r/oculus/comments/3paivl/rtu_package_to_switch_between_oculus_07_and_05/

very easy to follow and works on a clean win 10 install

But before I started I downloaded 0.8 from the Oculus site and installed that first, then followed the switcher instructions

Edit:

I should of stated the simple instructions

Install runtime 0.8 for win 10

1: Download the switch from MEGA
2: Extract the ZIP file to where you keep your Oculus stuff for safe keeping.
3: Copy the "Oculus_500" folder and set the copy into C:\Program Files (x86)
4: Copy the LibOVRRT64_0_5.dll file and paste it into C:\Windows\System32
5: Copy the other LibOVRRT64_0_5.dll file and paste it into C:\Windows\SysWOW64
6: Right click the SDK05 file and run as administrator.

 

[[VR] Mad Mike]

cant rep again but thanks so much (to all of you guys)

that is my sunday mapped out for me now anyway, building a new pc and getting ED running on it

do i need to worry about which nvidia drivers to use or windwos updates?

i have an iso file of the most recent windows 10 build downloaded from microsoft a few days ago.

thanks again

 

[Karnath]

I had to use an older driver to get it to recognise the DK2, I forget which one at the min (still at work will confirm later tonight when I get home)

 

[callezetter]

I used this method

https://www.reddit.com/r/oculus/comments/3paivl/rtu_package_to_switch_between_oculus_07_and_05/

very easy to follow and works on a clean win 10 install

But before I started I downloaded 0.8 from the Oculus site and installed that first, then followed the switcher instructions

Edit:

I should of stated the simple instructions

Install runtime 0.8 for win 10

1: Download the switch from MEGA
2: Extract the ZIP file to where you keep your Oculus stuff for safe keeping.
3: Copy the "Oculus_500" folder and set the copy into C:\Program Files (x86)
4: Copy the LibOVRRT64_0_5.dll file and paste it into C:\Windows\System32
5: Copy the other LibOVRRT64_0_5.dll file and paste it into C:\Windows\SysWOW64
6: Right click the SDK05 file and run as administrator.

Yeah this work great on a clean Win 10 install. On the other hand if you have an install that you have
changed a lot of runtimes and driver stuff in, chances are that the above wont work.

 

[Karnath]

I had to use an older driver to get it to recognise the DK2, I forget which one at the min (still at work will confirm later tonight when I get home)

Just to confirm driver 358.50 is what I had to use, although it's not supported for 0.8 runtime but it was the only one i could get ED to recognize the DK2 in the display options (obviously maybe different for others)

 

[[VR] Mad Mike]

Cool thanks. So its a choice ED or games using sdk .8.

No decision there then. ED

 

[Karnath]

Exactly I just used 8 as the initial installer for the DK2, however when I completed my new build the newest driver available at the time was 358.87 which is what is required for 0.8 so I had already this installed.
But when I installed the switcher program and switched to 0.5 ED couldn't find the DK2

So I rolled back a driver (358.50) and it worked, since everything is spot on and running the best it's ever run (beta 1.5) I have not tried updating drivers to the very latest so 358.91 or 359.00 may work

 

[callezetter]

Yeah finally got 0.5 and 0.7 working with the switcher again after the TH2 (nov) win10 update.
Dont really know why it suddently worked now. Been installing/resetting/deleting regedit keys for a week now.

Basicly uninstalled all oculus software, deleted all OVR0003 keys in the registry, swicthed place on my montor/dks hmdi connectors, reinstalled 0.5 and then installed 0.7.
Now works perfectly with the swicher V3 (https://goo.gl/9tYR84)

I use a 290x and the 15.9 driver. Dont feel brave enough to test the crimon yet. Or my dual switch goes down the DK2 win 10 grave again

 

[[VR] Mad Mike]

I used this method

https://www.reddit.com/r/oculus/comments/3paivl/rtu_package_to_switch_between_oculus_07_and_05/

very easy to follow and works on a clean win 10 install

But before I started I downloaded 0.8 from the Oculus site and installed that first, then followed the switcher instructions

Edit:

I should of stated the simple instructions

Install runtime 0.8 for win 10

1: Download the switch from MEGA
2: Extract the ZIP file to where you keep your Oculus stuff for safe keeping.
3: Copy the "Oculus_500" folder and set the copy into C:\Program Files (x86)
4: Copy the LibOVRRT64_0_5.dll file and paste it into C:\Windows\System32
5: Copy the other LibOVRRT64_0_5.dll file and paste it into C:\Windows\SysWOW64
6: Right click the SDK05 file and run as administrator.

hi

I did all of this however no joy. I have 358.50 drivers and followed to the letter.

on switching I get no hmd detected, tracker connected.

any ideas......

thanks

 

[Karnath]

Morning Mike,

Before right clicking on the runtime 5 and selecting run as admin make sure the DK2 is turned off.
Right click on the runtime 5 select run as admin, Then turn the DK2 on it should automatically be in extended mode.

When you did your fresh install did win 10 update itself to threshold 2 ?

https://forums.frontier.co.uk/showthread.php?t=200475

Edit

If Windows has downloaded and installed all the latest updates,I found this which may help

https://forums.frontier.co.uk/showthread.php?t=202726&p=3141204&viewfull=1#post3141204

 

[[VR] Mad Mike]

I am having a total mare. I think perhaps it is something to do with my m2 SSD.

As soon as I install anything to do with sdk0.5 my pc dies on reboot. 3 installs due to this and time to give up on that route.

So I dug out windows 7 install and a spare hdd. It seems on booting with that my pc is no longer able to boot from my see at all. Going back to win 10 I can't even repair it says cant install gpt format do i had to delete al partitions and rebuild and reformat.

Win7 does not support my ssd. Now even tho I was not going to install on this I am thinking win7 did something to it. Windows 8.1 does. Maybe I can dual boot with win 8.1 but not sure I can face doing it all again

edit.

it won, I lost. I suck the rift on ebay, it sold in 10 mins (I deliberately undercut everyone for quick sale). Still, net cost after ebay fees and postage (£17.33 P&P!) it still means I had 16 months of the best videogame experience I have ever had, at a net cost of £17

at least it means I can catch up on other games for a while

 

[Karnath]

I am having a total mare. I think perhaps it is something to do with my m2 SSD.

As soon as I install anything to do with sdk0.5 my pc dies on reboot.

No-way how frustrating, I'm sure that was the initial problem people were having when windows 10 first launched. As this is the reason why I waited so long to adopt win 10 until this switcher method became available

I do hope you get it sorted soon

 

[rohirm]

If boot hangs after installing the SDK the reason is RiftEnabler.sys. You have to boot (Windows 10) while holding down the shift key and go to the command prompt. Then delete c:\windows\system32\drivers\RiftEnabler.sys. After that it will boot normally.

 

[[VR] Mad Mike]

If boot hangs after installing the SDK the reason is RiftEnabler.sys. You have to boot (Windows 10) while holding down the shift key and go to the command prompt. Then delete c:\windows\system32\drivers\RiftEnabler.sys. After that it will boot normally.

An hr ago I would have tried it. Too late now

Thanks for the info tho and hopefully will help someone else