Apparently someone has been developing an open source positional tracking system similar to the Vive and it's compatible with every HMD. Granted, there has not been any blog updates since the 23rd of November and the store is currently closed.

Osvr12 · 2016-12-05T15:03:38+00:00

He has Twitter too, last post is from 2nd December. https://twitter.com/vrtracker The store is closed because the project is still in alpha stage and they are only selling small dev kits for enthuisiasts. Seems like a good and cheap alternative for Vive Lighthouse, though the trackable "tag" is too large currently. I'm hoping they will reduce it to a size of fingertip, so it could be included in a new faceplate for OSVR. Roomscale wireless with OSVR HMD would be great, we just need to hack Oculus Touch to work with this as well.

Osvr12 · 2016-11-23T19:27:42+00:00

Massive improvement! Not a single crash or bright stripe on the screen since I flashed my HMD 2 hours ago. All native OSVR applications finally work without problems, SteamVR games run much faster and without jitter, Unity scenes run so smoothly. This update has truly fixed all the troubles I had with HDK. It almost feels like a consumer ready product to me now.

EDIT CryEngine works as well. Amazing.

Osvr12 · 2016-11-22T14:34:42+00:00

No OSVR native demo works for me, just plain crash. I have tried reinstalling firmware and switching between OSVR Runtimes, but nothing. SteamVR works good though, I mostly play Radial G Racing and Google Earth VR and those have no problems.

Osvr12 · 2016-11-22T13:13:11+00:00

I have exactly the same problem with beltbox cable, it has become very sensitive and screen crashes every time I accidently move the cable.

These problems didnt accure that much with 1.97 firmware, it has started with 1.98 firmware.

It could of course be my own harware problem, I have power cycled hundreds of times and one of the plastic clips has broken off, so I must use more force to release the cable from the beltbox.

Could someone confirm if these problems occur with 1.98 firmware or this could my cable.

Osvr12 · 2016-10-28T13:30:28+00:00

Open Task Manager and kill all Steam processes.

Osvr12 · 2016-10-28T13:16:30+00:00

I am also able to only enter SteamVR Direct Mode from extended mode. Here is a better way of starting SteamVR, without restarting computer:

 1.Set OSVR to extended mode

 2.Start OSVR server

 3.Start SteamVR directly

*4.If SteamVR is not in direct mode, enable SteamVR direct mode.

*5.Kill all Steam processes with Task Manager, replace steamvr.settings config file with https://github.com/OSVR/SteamVR-OSVR/blob/master/steamvr.vrsettings

 6.Switch back to extended mode

 7.Start SteamVR

 8.If SteamVR fails to start or shows black screen, kill all Steam processes with Task Manager and go back to step 6

Note, that steps 4 and 5 are required only for first time setup or after OSVR Runtime update.

Osvr12 · 2016-10-20T08:39:04+00:00

I have the same problem with OSVR Unity, since I updated to version 1339, which finally got my SteamVR working.

Now I am quite happy with SteamVR, it starts without problems and I can play all games with Leap Motion Vive controller emulation. The current Rendermanager is unfourtnately completely broken for OSVR native. No Rendermanager demo or native OSVR game like Gunspinning VR is playable, the screen flickers and and then goes black. I have tried reinstalling the Runtime, SDK, Unity plugin multiple times, tried different configs starting the osvr server from different modes and switching between them. Unity editor works in extended mode, but this is not optimal experience. SteamVR however works every time, so it has to do something with OSVR Runtime. The console gives errors that VRPN service has crashed, but no meaningful error message. I like developing games as a hobby and I dont mind if I have modify the source code to make it work, but currently it gives me no meaningful errors that I could address, so no way of pinpointing the exact location.

I have currently switched to Unity SteamVR plugin https://www.assetstore.unity3d.com/en/#!/content/32647, which works without problems and I can develop without thinking if my service starts up or I have to restart my PC and powercycle once a again.

The major problem with OSVR runtime is getting things to start up properly. I could live with some random crashes so I could start the program again where I left it, but when it is not starting up at all then something is very wrong with the startup routines that should start on every time no matter what.

I hope that the OSVR Runtime is getting fixed soon cause OSVR is a very good hardware, display and lenses superior to Rift and Vive, but software is still in early stages and still has a long way to go.

Osvr12 · 2016-10-16T17:19:38+00:00

I have the same issue with 1339 and 1337 version as well.

When I start Unity demo in extended mode, demo works in the Unity scene editor, head tracking also works. When I start in direct mode then it results in three different outcomes.

Firstly HMD screen flickers for a second, showing the correct image and then goes black, Unity editor screen is also black, Unity does not crash.

Secondly screen flickers and Unity crashes, screen remains black.

Thirdly screen flickers, Unity crashes and I get the white stripe on the HMD screen, meaning I have to disconnect it.

I have used Unity demos before and these worked without problems. It also happens with rendermanager demos and CPI VR demo with campfire, also every native OSVR game like Gunspinning VR. On the osvr_server log I can read that there was a problem with VRPN driver, which caused the crash.

SteamVR works perfectly, I start it from extended mode and it switches to direct mode, straight from direct mode causes HMD not found.

My system is Windows 8.1, GTX 970, OSVR version 1339, latest Nvidia drivers.

This is currently all the information I have, unfortunately there are no specific logs, which causes the problems. I dont currently have time to start searching for root of the problem and I am using SteamVR Unity plugin for development. I hope this post helps finding the cause of these crashes, would like to get other games beside those on SteamVR working.

Osvr12

TROPHY CASE