SteamVR-OSVR icon indicating copy to clipboard operation
SteamVR-OSVR copied to clipboard

SteamVR-OSVR fails if OSVR server isn't already running

Open 0x1100 opened this issue 8 years ago • 1 comments

Description of issue

It seems that if the server isn't already running then OSVRTrackedDevice::activate() simply returns VRInitError_Driver_Failed right away. SteamVR-OSVR hence needs the OSVR server to be started before SteamVR.

On the other hand, everything will work correctly if you restart the OSVR server after a correct initialization.

Steps to reproduce the problem

Start SteamVR. Start the OSVR server. See that the status doesn't get to ready.

0x1100 avatar Apr 20 '17 07:04 0x1100

You are describing expected behaviour..

Start OSVR Start steamvr Start steamvr app from steamvr dashboard or steam desktop client.

Think of osvr server needing started first as being how steamvr knows to use the steam-osvr drivers.

What we need is better integration to steamvr and steam runtimes of the steamvr-osvr driver so that we just need to connect hardware and click on play in steam. Seeing steamvr-osvr drivers compiled for steam would mean folks simply install them from steam store, plug in hardware and then jump into vr by starting steamvr .

This is described in first post in https://github.com/OSVR/SteamVR-OSVR/issues/18 and is what is needed for

Connect and power on hardware Click play on any steamvr app

to be all that is needed after initial setup of steamvr-osvr drivers better optimised for steam and SteamVR runtimes.

The vive hmd and vive controllers start steamvr by one click of a power button.

Balderick avatar Dec 11 '17 23:12 Balderick