Saturday, August 29, 2015

Getting Vivid Vision beta to work

During my Skype with James, the issue of stability of the Vivid Vision beta came up.  I told James that the program would crash quite a lot, and that I'd have to reopen the game quite frequently.  He said it was a result of the problematic Oculus SDK.  But recently I've got things set up so that Vivid Vision is now very stable.  Since I've had this configuration I've not had a single crash.  Because the release of the commercial Oculus Rift is still potentially eight freaking months away, that means it makes sense to get the DK2 to go as far as it will go.  That's another eight potential months of vision therapy on the DK2.  Without further ado, here are the details of my setup.

Operating system: Windows 10 Professional (x64)
CPU: Intel Core i7-4770 Haswell Quad-Core 3.4GHz LGA 1150 84W BX80646I74770 Desktop Processor Intel HD Graphics
GPU: EVGA GeForce GTX 780 Ti Superclocked w/ACX Cooler 3GB GDDR5 384bit Dual-Link DVI-I DVI-D HDMI DP SLI Graphics Cards 03G-P4-2884-KR
Motherboard: Z87-GD65 GAMING (MS-7845) 1.0
Memory: G.SKILL Ripjaws X Series 16GB (2 x 8GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model F3-1600C9D-16GXM
Oculus runtime: oculus_runtime_sdk_0.6.0.1_win
Vivid Vision: VividVision-v0.72-Win
nVidia drivers: 355.60-desktop-win10-64bit-international-whql

When it came time to upgrade to Windows 10, everyone in the VR community collectively crapped their pants because Oculus didn't have a ready compatible runtime.  Luckily there was a workaround. When you try to install the, the installer says it fails.  But it works.  Just create a shortcut of OVRServer_x64 (in Program Files\Oculus\Service). On that shortcut, click properties, go to the compatibility tab, and check Windows 8 compatibility, and also check 'run as administrator'. Then turn off the Oculus Rift. Then run the shortcut that you created, then turn the Oculus Rift on, and then run Vivid Vision.  What a pain in the ass.   But it runs like a champ now.   I'm sure that the new runtime works great (, and that's probably the way to go.  But right now everything's working awesome for me in my current setup.  So that's where I'm going to stay for a while until some driver upgrade breaks something, and then I have to mess with the thing again.  Sigh... the joy of being an early adopter.

Here's the post that gave me the instructions on how to get the Oculus Rift to work with Windows 10.

No comments:

Post a Comment