vorpX 0.9 Slight Delay

[WolfTwo]

I seem to be having trouble getting that setup to work Nip. I’ve done everything you’ve said, step by step, and it still doesn’t seem to want to boot to extended mode.

Any further suggestions?

[NipOc]

You could try the following:

1. Did you make and start the .bat? If not, do so.
2. You may have to add four spaces before each line in the .bat or windows might not recognize it as code. (I think the spaces were deleted when I first posted the commands)

    net stop OVRService
    C:\Treiber\Oculus\Runtime\Tools\DirectDisplayConfig.exe off
    C:\Treiber\Oculus\Runtime\Service\OVRServer_x86.exe

3. Is C:\program files (x86)\Oculus the installation folder of your runtime?
If not, change the paths in the .bat accordingly.
4. Run the .bat as administrator.
5. Stop the runtime manually in the Oculus program and execute the .bat again.
6. Try to run the commands (from the .bat) in cmd (as administrator).

I hope this helps.

[hellfrost3]

I know VorpX is working really well on the DK2, but will there be VropX support for CV1?

[Ralf]

There are no plans to stop work on vorpX. If technically possible, which almost certainly will be the case, vorpX will work with the Rift consumer version.

[WolfTwo]

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!

[Ralf]

Following the procedure suggested by NipOc earlier in this thread you should be able to use 0.7 and 0.5/0.6 side by side without too much hassle until the next vorpX version is released.

[WolfTwo]

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?

[WolfTwo]

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.

[NipOc]

Try to kill the Oculus Config Utility (OculusConfigUtil.exe) in the Taskmanager or add Taskkill /IM OculusConfigUtil.exe to the .bat.

[WolfTwo]

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 successfully

And VorpX won’t give me the time of day.

[NipOc]

I don’t know why vorpx doesn’t detect the headset, maybe you could try another demo or game with it to look if that works.
If it does, it’s probably something with vorpx and you have to wait for the next version.

One game that definitely works, because it doesn’t rely on the oculus runtime (it just needs extend mode) is Alien Isolation.
So if you haven’t played it, you could do so until the next version of Vorpx is released, it was by far the most impressive oculus game/demo I played so far.

[Ralf]

post removed, the procedure proposed here originally can lead to problems

[NipOc]

I would be cautious with that, after I installed the 0.6 runtime (in windows 8 compatibility mode) on windows 10, I was stuck in a boot loop and neither uninstalling the oculus driver nor reinstalling the graphics drivers helped, so I had to completely reinstall the system.
(Maybe I should have used an old display driver or so)

[WolfTwo]

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.

[Ralf]

Thanks for the heads up both of you. I removed my recommendation above to make sure no one falls into this trap.

[Author]

Posts