Search All Oculus Rift Setup Tool Drivers. Driver Update Utility. Updates PC Drivers Automatically. Identifies & Fixes Unknown Devices. Supports Windows 10, 8, 7, Vista, XP.
I've just got my DK2, I couldn't make it work either. I tried the Runtime 0.8, it didn't work, so I took the 0.7, and it didn't work either. I'm on a laptop with WIndows 10 (config: Intel core i3 + Nvidia GeForce 820M). And before you say anything: it's not because of my configuration. Indeed: I've made it work!
So, here is an advice for those who can't run the DK2 on Windows 10: take the Oculus Runtime 0.4. It works perfectly. And maybe the 0.6 also works, I haven't tried yet (after hours spent trying to make it work, I just want to play now, enough crash-testing for me!). Also, I'd like to report this to the devs: the problem clearly comes from the Runtimes. So, maybe it's a bug?
Maybe not, still it's kind of weird: the only Runtimes that don't work on Windows 10 are the ones that should be working on it! I understand, still so many people had problems playing the Rift on Windows 10 with the latest Runtimes. Flash Drive Driver Windows 10 there. So, if they can't use those, I'd still advice them to use previous Runtimes, so that they can enjoy the Rift without problems. But I don't really get it: why are they not working, concretely? I mean, what makes those Runtimes different from the previous ones? And why were those changes necessary? Isn't there a way to make those changes with a less power-hungry software such as the previous Runtimes?
Since the goal of Oculus is to make VR popular, it's a shame to have reduced the number of potential players. So many people could play with their weak laptops/PCs, if it weren't for those Runtimes! In order to optimize for the best experience on the consumer Rift, choices were made to use new features only available in newer GPUs. However, the laptop issue is a problematic for many reasons, and just won't work well.
Comments are closed.