Forum Replies Created
-
Posts
-
Yeah that was what I initially tried. Ended up in an infinite boot loop that was even crashing my bios (MSI Gaming 5) somehow. I was eventually able to get into safe mode, and then restore back to where I was before installing Oculus.
Anyways, I’ll install Alien Isolation and give it a shot in stereo mode on extended while I wait for 0.9.
I am curious though if the secret to the equation might be rolling my video drivers back, but I really don’t want to test it and end up in another loop.
There is progress. It looks like the version error stops appearing. However, VorpX still doesn’t detect the HMD and will not start. Here is the dialogue from the X86 window.
OVR::DeviceManager – initialized.
OVR::DeviceManagerThread – running (ThreadId=0xBAC).
CameraFactory starts
[TrackingManager] Entering tracking thread
OVR::Win32::HIDDevice – Opened ‘\\?\hid#vid_2833&pid_0021#7&e632a6f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}’
Manufacturer:’Oculus VR, Inc.’ Product:’Rift DK2′ Serial#:’H1DE4CC6NHC4KM00Y100′ Version:’212′
OVR::SensorDevice – Closed ‘\\?\hid#vid_2833&pid_0021#7&e632a6f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}’
OVR::Win32::HIDDevice – Closed ‘\\?\hid#vid_2833&pid_0021#7&e632a6f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}’
[TrackingManager] Broadcasting new HMD count = 0
CameraFactory::inspectCamera starts
OVR::Win32::HIDDevice – Opened ‘\\?\hid#vid_2833&pid_0021#7&e632a6f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}’
Manufacturer:’Oculus VR, Inc.’ Product:’Rift DK2′ Serial#:’H1DE4CC6NHC4KM00Y100′ Version:’212′
CameraDK2::Initialize starts
Repeated 2 IMU samples: 2000 2 0
Lost 2 IMU samples: 5004 2 4
Lost 3 IMU samples: 4002 2 5
CameraDK2::Initialize: sending GET_CUR
IOCTL_OCUSBVID_EXECUTE_VIDEO_STREAMING_REQUEST probe GET_CUR succeeded
Device reported frame index 1, format index 1, frame interval 166666
video frame size 0x58200, payload transfer size 3000
PROBE SET_CUR to fmt 1 frm 1 int 166666 frmsiz 360960 xfersize 3000
IOCTL_OCUSBVID_EXECUTE_VIDEO_STREAMING_REQUEST probe SET_CUR succeeded
COMMIT SET_CUR to fmt 1 frm 1 int 166666 frmsiz 360960 xfersize 3000
IOCTL_OCUSBVID_EXECUTE_VIDEO_STREAMING_REQUEST commit SET_CUR succeeded
Lost 2 IMU samples: 3002 2 4
Lost 2 IMU samples: 3002 2 4
Lost 2 IMU samples: 2001 2 4
Lost 4 IMU samples: 2002 2 6
[TrackingManager] Broadcasting new HMD count = 1
CameraFactory::inspectCamera ends successfullyAnd VorpX won’t give me the time of day.
The OVRServer_X86 just keeps saying REJECTED: Rift application is using an incompatible version 1.7.0, feature version 26297 (my version=1.3.0, feature version 0) over and over again.
The issue seems to be that although I am able to get the Oculus into extended mode, VorpX tells me that no device is detected and doesn’t seem to function. The only way I can get VorpX to notice my rift is by going back to direct mode.. at which point the rift tells me that VorpX is out of date and won’t function.
Is there something I am missing here?
Totally refreshing this forum every 2 hours in anticipation of the release. I bought VorpX on Monday without researching the fact that it wasn’t 0.7 runtime ready just yet. Excited to get into some games!