Oculus Rift & Windows 10 Thread
- Thread starter tinimark
- Start date
Been running Windows 10 for a several weeks worked fine for me with Elite. Now running the latest build (10041) had a few graphics issues. Seemed to be resolved but I had to install the Beta AMD Catalyst Drive 15.3, 64Bit Win8. The only issue I have now is the game after I push play will just exit completely but on the second try it seems to load and work fine.
W10TP is pretty stable, but it looks absolutely horrible and still sends all your keystrokes and web history to MS for "review".
Don't type any sensitive details into it like usernames and passwords for game clients, copy and paste them, and even that doesn't guarantee that MS isn't slurping all your details up.
As a technical preview, 10 is great. As a day-to-day operating system, it's a huge redacted.
Don't type any sensitive details into it like usernames and passwords for game clients, copy and paste them, and even that doesn't guarantee that MS isn't slurping all your details up.
As a technical preview, 10 is great. As a day-to-day operating system, it's a huge redacted.
Have you read this in the judder thread about Windows 8.1?
https://forums.frontier.co.uk/showthread.php?t=83616&page=30
If you try windows 10, can you tell me if its any better?
Thanks for the advice . It wasn't really a judder problem I was having. In fact, I think it's more related to USB and my hotas setup which was causing windows to not boot.
win 10 is unfortunately a no go, hit a stumbling block in that vjoy and UJR don't seem to work and I need them for mapping my pedals to rudder. Whilst I did get the game to run, it looks like sweetfx wasn't going to play nicely either and this is even before installing rift.
Back to win7 for me then.
win 10 is unfortunately a no go, hit a stumbling block in that vjoy and UJR don't seem to work and I need them for mapping my pedals to rudder. Whilst I did get the game to run, it looks like sweetfx wasn't going to play nicely either and this is even before installing rift.
Back to win7 for me then.
Just as a reminder for anyone trying...
Do yourself a favor and install the preview to another drive/partition…
at some point I ran into issues and DK2 IR Tracker now won't track on High FPS(or GPU Load?) anymore on build 10041. - now even rollback to previous build and reinstall of everything didn't seem to help while still working on my win 8.1 partition..
Strange stuff will happen…so again, do NOT use your existing/working Oculus Rift setup.
Do yourself a favor and install the preview to another drive/partition…
at some point I ran into issues and DK2 IR Tracker now won't track on High FPS(or GPU Load?) anymore on build 10041. - now even rollback to previous build and reinstall of everything didn't seem to help while still working on my win 8.1 partition..
Strange stuff will happen…so again, do NOT use your existing/working Oculus Rift setup.
Last edited:
Windows 10 (10074), nVidia 352.63 BETA - ISSUES
Hey everyone, had my DK2 for a couple of weeks now and after tweaking a bit it's been running very well.
Upgraded to the latest win10 release (10074) and update my nVidia drivers to the new 352.63 beta release. Should have done the smart thing and checked everything worked between each step but felt a little gung-ho so here we are.
Current issue is the game launches fine and I can see the splash screen on the rift, however it keeps dropping back to desktop (almost like fullscreen doesn't stick). I can alt tab back into the game but it only stays in for a couple of seconds before dropping back to desktop. I managed to get the display to "stick" once and everything ran fine and was playable, have not been able to reproduce how I managed this though.
Any thoughts or tips would greatly be appreciated.
Hey everyone, had my DK2 for a couple of weeks now and after tweaking a bit it's been running very well.
Upgraded to the latest win10 release (10074) and update my nVidia drivers to the new 352.63 beta release. Should have done the smart thing and checked everything worked between each step but felt a little gung-ho so here we are.
Current issue is the game launches fine and I can see the splash screen on the rift, however it keeps dropping back to desktop (almost like fullscreen doesn't stick). I can alt tab back into the game but it only stays in for a couple of seconds before dropping back to desktop. I managed to get the display to "stick" once and everything ran fine and was playable, have not been able to reproduce how I managed this though.
Any thoughts or tips would greatly be appreciated.
I have the same issue. If you find a fix let me know.
It's a custom resolution problem. If like me you followed the guide on these forums you're likely running a custom resolution to act as an anti-aliasing solution. My system doesn't work on any resolution other than 1920 x 1080. I now use that with 1.5 supersampling in game for the same effect. Can't confirm if DSR works as my system is SLI.
You can change the resolution by hand in the DisplaySettings.xml file. This should get you into the game and let you configure as you want.
Hope that helps, took my 2 days to figure out
You can change the resolution by hand in the DisplaySettings.xml file. This should get you into the game and let you configure as you want.
Hope that helps, took my 2 days to figure out
It's a custom resolution problem. If like me you followed the guide on these forums you're likely running a custom resolution to act as an anti-aliasing solution. My system doesn't work on any resolution other than 1920 x 1080. I now use that with 1.5 supersampling in game for the same effect. Can't confirm if DSR works as my system is SLI.
You can change the resolution by hand in the DisplaySettings.xml file. This should get you into the game and let you configure as you want.
Hope that helps, took my 2 days to figure out
Thanks, that worked
Windows 10 + ED + DK2 + X52 + Xifi Xtreme Gamer = Working?
Hi VR Guys and Girls,
Unless you live in a cave you should know Windows 10 is coming and I saw it's already downloaded on my hard-disk, ready to be installed for free from my Windows 7 64bits home edition.
Now as title said, I'm wondering if I will meet problems using this new OS. So does somebody already jumped in Win 10 and can confirm all work fine?
I saw from Oculus forum that it seems the OVR service seems not really ready for Win 10, but people seems able to workaround and make it work.
For ED I'm using the Saitek drivers, the DK2 and also an old Xifi Xtreme Gamer audio card.
I saw that, after Win 10 installation, we have 30 days to be sure and we can go back to previous OS, so it's not a one way stuff...
In any case if somebody already tested such combination I'll be glad to read your thoughts.
Thanks!
Hi VR Guys and Girls,
Unless you live in a cave you should know Windows 10 is coming and I saw it's already downloaded on my hard-disk, ready to be installed for free from my Windows 7 64bits home edition.
Now as title said, I'm wondering if I will meet problems using this new OS. So does somebody already jumped in Win 10 and can confirm all work fine?
I saw from Oculus forum that it seems the OVR service seems not really ready for Win 10, but people seems able to workaround and make it work.
For ED I'm using the Saitek drivers, the DK2 and also an old Xifi Xtreme Gamer audio card.
I saw that, after Win 10 installation, we have 30 days to be sure and we can go back to previous OS, so it's not a one way stuff...
In any case if somebody already tested such combination I'll be glad to read your thoughts.
Thanks!
Last edited:
There wasn't a windows 9, M$ jumped straight to 10 to distance themselves from the POS that is Win 8/8.1
Possible reasons why Microsoft missed out Windows 9..
- Like you say, to make Windows 8 look like a thing of the past
- They wanted it to have the same number as Apple's OS
- Because as every Microsoft Suit knows, Windows 10 is "one better" than Windows 9
- The police were disposing of a large heap of Cannabis by burning it right next door to the executives taking the decision
- They thought people might confuse it with Windows 95 or 98
- And here's my personal choice.. They didn't want people who know a bit of German making fun of it.
Last edited:
The official reason is that with Win10 they're moving to a service-based model and the idea is that Win10 is sort of the 'last' Windows since from here on out updates will be constant and automatic, rather than discretely packaged products. Since, all going to plan, there won't be any more version numbers (at least for a while), they wanted to end on something a bit more 'road-markery' than Windows 9.
As you can probably guess from my username, I'm of the opinion they could well have stopped at 9, since 9 is an awesome number.
As you can probably guess from my username, I'm of the opinion they could well have stopped at 9, since 9 is an awesome number.
