Oculus Rift & Windows 10 Thread

I upgraded to Windows 10 yesterday. Since the upgrade, OR works fine, but I've noticed that there is a pronounced 'stutter' that simply wasn't there when I was using Windows 7. What I mean by this is not framerate- I am getting great frames. Rather, when I move my head quickly from left to right, the Rift stops ever so slightly about five or six times for a noticeable (and frustrating) interruption to gameplay.
|
I am running GTX 980's in SLI, and, like I mention above, did not have this problem in Windows 7.
|
I've searched this thread exhaustively, and while reference to 'stutter' is made, it does not seem to be the same type of stutter I am encountering. Is stutter the right thing to call it? I differentiate stutter from judder in that I perceive judder to be more consistent and more akin to framerate issues. Sutter, in my estimation, is a relatively irregular, but pronounced 'stop' and then resumption of what are otherwise great framerates.
|
Has anyone else had anything like this happen to them?
 
Got to agree here - on W10 and DK2 super cruise is so stuttery it's painful. Otherwise it works fine, but frame rate seems to be much lower than 8.1 on the same hardware, but different drivers.
 
Got to agree here - on W10 and DK2 super cruise is so stuttery it's painful. Otherwise it works fine, but frame rate seems to be much lower than 8.1 on the same hardware, but different drivers.
For me, Supercruise isn't the issue (it might be bad mind you; haven't tried it yet), but rather the primary issue for me is in stations. Just intermittent, unpredicable stutter/jitter.
 
For me, Supercruise isn't the issue (it might be bad mind you; haven't tried it yet), but rather the primary issue for me is in stations. Just intermittent, unpredicable stutter/jitter.

Have you tried disabling SLI? I found there to be too much lag for it to be tolerable (high frametimes) so turned it off, I think performance is actually better with it off.
 
I'll give it a try, but I'm worried that if that solves the problem of stutter, it'll create a new one of poor(er) frame rates.

If that's my choice, then I think it's a little bit of a gip considering I was rocking it with Windows 7 just fine on SLI (with improved SLI performance). Going back to a single 980 just to eliminate stutter means I've now got approx. C$600 worth of unutilized assets sitting in my case collecting dust (I rarely play anything other than Elite and the odd World if Warships, which Incidentally also does not support SLI 😐
 
Honestly if MS caves and walks DX12 back to Win 7 compatibility (or if a good hack comes out of the woodwork) I don't see much reason to go to Win 10. I'll take the SLI, DX12 threading and a stripped out, quiet operating system any day of the week.
 
So what some of you guys are saying is that you upgraded to Windows 10 and are able to play ED in extended mode using the v5/v6 runtime? With or without the extended mode hack?

ED's inability to run in DM is the only reason i'm not running Windows 10.
 
Last edited:
So what some of you guys are saying is that you upgraded to Windows 10 and are able to play ED in extended mode using the v5/v6 runtime? With or without the extended mode hack?

ED's inability to run in DM is the only reason i'm not running Windows 10.

I had v5 runtime on my Win8, did a seemless upgrade and haven't had to do anything with the runtime. It just works like it did before, better in fact. And yes, in extended mode.
 
Fantastic. I'll give that a go today.

EDIT - Didn't work for me. Maybe 'cause I have a 980Ti and can't use v5/v6 compatible older drivers. In any case, I have plenty of other DK2 DM compatible games and I'll wait for Frontier to join the rest of the devs in supporting the SDKs whenever that might be.
 
Last edited:
Fantastic. I'll give that a go today.

EDIT - Didn't work for me. Maybe 'cause I have a 980Ti and can't use v5/v6 compatible older drivers. In any case, I have plenty of other DK2 DM compatible games and I'll wait for Frontier to join the rest of the devs in supporting the SDKs whenever that might be.

I have a gtx980 with 5.0.1 oculus runtime, 353.82 nvidia drivers, and x55 profiler all working in Windows 10. I didn't upgrade my nvidia drivers but I just got the latest Win10 build 10532 (still a preview member). Elite works great with almost everything turned all the way up. I did upgrade to the latest oculus build when it came out but after reading about it not working with Elite I did an uninstall, rebooted, installed 5.0.1 and then rebooted again. After that it was working again. Oh, almost forgot, I did perform an upgrade to Windows 10 from 8.1 prior to win 10 release.
 
Windows 10 Oculus Rift DK2 work-around tutorial

Greetings Commanders,

There has been a lot of information about the so called "hack" to get the rift working with windows 10 and E:D.
I wanted to post the solution that worked for me that I aggregated from several different posts on the forums into one thread.
First though I'll start by saying that this MAY not work for everyone. This fix is for NVIDIA users specifically.
If anyone can find an AMD driver that works with this I will gladly add it to the OP but since I have an Nvidia card I have no way of testing.

You need two things to get started:

1. Oculus runtime version 5.0.1 (https://developer.oculus.com/downloads/pc/0.5.0.1-beta/Oculus_Runtime_for_Windows/)

2. Nvidia driver version 355.60 (http://www.nvidia.com/download/driverResults.aspx/89124/en-us)
Note: other drivers may work but this is the one that I found worked for me.

Step by step (after downloading the above files):
1. Remove your current version of the oculus rift runtime by following the same steps as step 2 but instead looking for Oculus Runtime
2. Remove your current video driver by right clicking the start menu clicking on programs and features. Scroll down to NVIDIA graphics driver and uninstall it.
3. restart your computer
4. Once booted again run the Nvidia driver you downloaded earlier and install it.
5. Run the Oculus Runtime v 5.0.1 file you downloaded earlier and install it. NOTE: It will warn you that it is not compatable with your version of windows
Ignore this warning and just click ok (it will still install it even though it says it wont... weird)
6. Another restart may help if it doesn't work right off the bat.

The deed is now done.

Some things to note: This will only work in extended mode! You cannot use Direct mode with this work-around. Also you cannot change the eye relief sliders or other options
inside the oculus config utility and you cannot launch the test environment.

My specs:
Windows 10
Intel core i7 4770
Asus Nvidia GTX 780ti
 
Last edited:
Went ahead and did it today. Went smooth as silk except for having to increase the size of the partition. First glance I really like it. It is pretty much what everybody has been saying a cross between 7 and 8 plus ED runs better than I have seen in some time. Now if we just get the support for SDK 7 and implementation of DX12 this is good. Seems like everything runs faster. Thanks you brave souls who tried it first.
 
Last edited:
I just installed Windows 10, runtime 5.0.1 beta and Nvidia 355.83 (latest) drivers. Now, I have not played ED in a long time (since 1.2), so there may be other optimizations that I'm not aware of. But ED has never run smoother. With my GTX970 I cranked everything up to full (no SSAA) and it was smooth as silk. Even got it running very well with 1.5 SSAA by turning down the OR quality slider a few notches and setting shadows to medium.

Anyway, just thought I'd let you know that it works extremely well for me with the latest NVidia drivers.
 
I am running exactly the same as above post with a single 980 and mine has never looked or run better than this. 10 seems pretty stable and love the alt-tab to switch screen.
 
Didn't really know where to put this for us guys but I'm sure some of you will of been waiting for this

Saitek / Madcatz just released beta drivers for windows 10 support for their flight sticks

http://madcatz.kayako.com/Knowledge...aitek-hotas-beta-drivers-and-software-release

Thanks for pointing that out. It's definitely "beta" though. The Smart Technology app is massively broken -- if you try to assign a keypress to a controller button, it acts as if that button is always pressed. (On an X52 Pro at least.)

It's really a shame that Windows 10 just materialized out of the blue. If only there had been previews for them to test with in the months prior to launch, they could have had their drivers ready to go... :p
 
Back
Top Bottom