OSVR / SteamVR-OSVR

An OSVR plugin for SteamVR, providing SteamVR support for OSVR HMDs.
Apache License 2.0
138 stars 57 forks source link

OSVR HDK 1.4 cannot start STEAM VR - error 108 #127

Open Atihinen opened 7 years ago

Atihinen commented 7 years ago

Description of issue

SteamVR says cannot detect headmount (error 108) and cannot figure out how to continue. The HDK itself works e.g. with games from itch.io.

Steps to reproduce the problem

Open SteamVR.

System configuration

Please specify any relevant system configuration information.

osvr_server_config.txt vrclient_vrmonitor.txt vrclient_vrstartup.txt vrmonitor.txt vrserver.previous.txt vrserver.txt vrclient_Steam.txt

Attached files

Please attach the following files:

godbyk commented 7 years ago

The vrserver.txt log file reports: OSVRTrackedHMD::Activate(): Context startup timed out after 5 ms! A common cause of this error is if SteamVR can't communicate with osvr_server. Are you starting the OSVR server before starting SteamVR?

Atihinen commented 7 years ago

@godbyk hi,

yes I always start the osvr server before starting the application. To start OSVR server I use OSVR Central -> OSVR server

godbyk commented 7 years ago

While the OSVR server is running, can you run osvr_print_tree.exe in a terminal and post the output?

Atihinen commented 7 years ago

@godbyk osvr_print_tree.exe > print_tree.log Aug 30 00:18:03.245 info [OSVR]: Logging for D:\Program Files\OSVR\Runtime\bin\osvr_print_tree.exe Aug 30 00:18:03.246 info [OSVR: org.osvr.tools.printtree]: OSVR client context initialized for org.osvr.tools.printtree Aug 30 00:18:04.453 info [OSVR: org.osvr.tools.printtree]: Could not connect to OSVR server in the timeout period allotted of 200ms Aug 30 00:18:04.454 info [Client: org.osvr.tools.printtree]: Client context has not yet started up - waiting. Make sure the server is running. Aug 30 00:18:11.396 info [OSVR: org.osvr.tools.printtree]: Got connection to main OSVR server Aug 30 00:18:51.506 info [OSVR: org.osvr.tools.printtree]: Connected 0 of 0 unconnected paths successfully Aug 30 00:18:51.507 info [Client: org.osvr.tools.printtree]: OK, client context ready. Proceeding. Aug 30 00:18:51.509 info [OSVR: org.osvr.tools.printtree]: OSVR client context shut down for org.osvr.tools.printtree

print_tree.txt

edit: changed the print_tree.log to print_tree.txt because the github

godbyk commented 7 years ago

It looks like either the server isn't actually running or osvr_print_tree and SteamVR are unable to connect to it for some reason (e.g., a firewall).

Can you run the OSVR server from a terminal as well? It will print out a log showing any errors it encounters.

Atihinen commented 7 years ago

@godbyk

osvr_server.exe Aug 30 00:30:34.235 info [OSVR]: Logging for D:\Program Files\OSVR\Runtime\bin\osvr_server.exe Aug 30 00:30:34.237 info [OSVR Server]: Using default config file - pass a filename on the command line to use a different one. Aug 30 00:30:34.238 info [OSVR Server]: Attempting to load config file 'osvr_server_config.json'. Aug 30 00:30:34.238 info [OSVR Server]: Constructing server as configured... Aug 30 00:30:34.243 info [OSVR Server]: Loading auto-loadable plugins... Aug 30 00:30:34.253 info [OSVR Server]: Loading plugins... Aug 30 00:30:34.254 info [OSVR Server]: Instantiating configured drivers... Aug 30 00:30:34.255 info [OSVR Server]: Added device: org_osvr_filter_videoimufusion/HeadFusion Aug 30 00:30:34.256 info [OSVR: org.osvr.analysisplugin]: OSVR client context initialized for org.osvr.analysisplugin Aug 30 00:30:34.257 info [OSVR]: Z:\j\workspace\OSVR-Core-Build-Win\BIT\64\TRACING\OFF\VS\12\host\windows\src\osvr\Common\ClientInterface.cpp:38: Interface initialized for /com_osvr_Multiserver/OSVRHackerDevKitPrediction0/semantic/hmd Aug 30 00:30:34.257 info [OSVR]: Z:\j\workspace\OSVR-Core-Build-Win\BIT\64\TRACING\OFF\VS\12\host\windows\src\osvr\Common\ClientInterface.cpp:38: Interface initialized for /com_osvr_VideoBasedHMDTracker/TrackedCamera0_0/semantic/hmd/front Aug 30 00:30:34.257 info [OSVR Server]: Successes: Aug 30 00:30:34.258 info [OSVR Server]: - com_osvr_VideoBasedHMDTracker/VideoBasedHMDTracker Aug 30 00:30:34.258 info [OSVR Server]: - org_osvr_filter_videoimufusion/VideoIMUFusion Aug 30 00:30:34.258 info [OSVR Server]: Aliases found and parsed from config file. Aug 30 00:30:34.259 info [OSVR Server]: Display descriptor found and parsed from config file. Aug 30 00:30:34.260 info [OSVR Server]: RenderManager config found and parsed from the config file. Aug 30 00:30:34.260 info [OSVR Server]: Triggering automatic hardware detection... Aug 30 00:30:34.261 info [OSVR Server]: Registering shutdown handler... Aug 30 00:30:34.261 info [OSVR Server]: Starting server mainloop: OSVR Server is ready to go! Aug 30 00:30:34.261 info [OSVR Server]: Performing hardware auto-detection. Aug 30 00:31:14.349 info [OSVR Server]: Added device: com_osvr_Multiserver/OSVRHackerDevKit0 Aug 30 00:32:03.705 info [OSVR Server]: Added device: com_osvr_Multiserver/OSVRHackerDevKitPrediction0 directx_camera_server: Can't create video enumerator (no cameras?)

Video-based tracker: Could not open the tracking camera. If you intend to use it, make sure that all cables to it are plugged in firmly. Video-based tracker: Windows users may need to exit other camera-using applications or activities until after the tracking camera is turned on by this plugin. (This is the most common cause of messages regarding the 'filter graph')

Aug 30 00:32:23.778 info [OSVR]: Z:\j\workspace\OSVR-Core-Build-Win\BIT\64\TRACING\OFF\VS\12\host\windows\src\osvr\Client\AnalysisClientContext.cpp:76: Got updated path tree, processing Aug 30 00:32:24.780 info [OSVR]: Z:\j\workspace\OSVR-Core-Build-Win\BIT\64\TRACING\OFF\VS\12\host\windows\src\osvr\Client\TrackerRemoteFactory.cpp:93: Constructed a TrackerHandler for com_osvr_Multiserver/OSVRHackerDevKitPrediction0@localhost:3883 sensor 0 Aug 30 00:32:24.781 info [OSVR: org.osvr.analysisplugin]: Successfully produced handler for /com_osvr_Multiserver/OSVRHackerDevKitPrediction0/semantic/hmd Aug 30 00:32:24.782 info [OSVR: org.osvr.analysisplugin]: Could not resolve source for /com_osvr_VideoBasedHMDTracker/TrackedCamera0_0/semantic/hmd/front Aug 30 00:32:24.784 info [OSVR: org.osvr.analysisplugin]: Connected 1 of 2 unconnected paths successfully Aug 30 00:32:24.784 info [OSVR Server]: Sent path tree to clients. vrpn: Connection request received from 127.0.0.1: 127.0.0.1 54464 Aug 30 00:32:24.787 info [OSVR Server]: Performing hardware auto-detection. directx_camera_server: Can't create video enumerator (no cameras?) Aug 30 00:32:44.838 info [OSVR Server]: Sent path tree to clients. vrpn: Connection request received from 127.0.0.1: 127.0.0.1 56607 VRPN Error (20) from com_osvr_Multiserver/OSVRHackerDevKitPrediction0: No response from server for >= 10 seconds Aug 30 00:32:44.841 info [OSVR Server]: Performing hardware auto-detection. Aug 30 00:33:04.895 info [OSVR Server]: Performing hardware auto-detection. directx_camera_server: Can't create video enumerator (no cameras?) Aug 30 00:33:24.949 info [OSVR Server]: Sent path tree to clients. VRPN Error (60) from com_osvr_Multiserver/OSVRHackerDevKitPrediction0: No response from server for >= 10 seconds VRPN Error (40) from com_osvr_Multiserver/OSVRHackerDevKitPrediction0: No response from server for >= 10 seconds VRPN Error (0) from com_osvr_Multiserver/OSVRHackerDevKitPrediction0: Server connection re-established! VRPN Error (60) from com_osvr_Multiserver/OSVRHackerDevKitPrediction0: No response from server for >= 10 seconds VRPN Error (0) from com_osvr_Multiserver/OSVRHackerDevKitPrediction0: Server connection re-established!

Atihinen commented 7 years ago

Also with same osvr_server instance running I'm able to play non steamvr games or use unity to do stuff with osvr

godbyk commented 7 years ago

If you leave osvr_server.exe running on one terminal and try running osvr_print_tree.exe in another terminal, does it print out more information then? Is that works, try running SteamVR again while the osvr_server.exe terminal is still running.

Atihinen commented 7 years ago

@godbyk osvr_server: Aug 30 00:50:09.879 info [OSVR Server]: Using default config file - pass a filename on the command line to use a different one. Aug 30 00:50:09.880 info [OSVR Server]: Attempting to load config file 'osvr_server_config.json'. Aug 30 00:50:09.880 info [OSVR Server]: Constructing server as configured... Aug 30 00:50:09.885 info [OSVR Server]: Loading auto-loadable plugins... Aug 30 00:50:09.894 info [OSVR Server]: Loading plugins... Aug 30 00:50:09.895 info [OSVR Server]: Instantiating configured drivers... Aug 30 00:50:09.896 info [OSVR Server]: Added device: org_osvr_filter_videoimufusion/HeadFusion Aug 30 00:50:09.896 info [OSVR: org.osvr.analysisplugin]: OSVR client context initialized for org.osvr.analysisplugin Aug 30 00:50:09.897 info [OSVR]: Z:\j\workspace\OSVR-Core-Build-Win\BIT\64\TRACING\OFF\VS\12\host\windows\src\osvr\Common\ClientInterface.cpp:38: Interface initialized for /com_osvr_Multiserver/OSVRHackerDevKitPrediction0/semantic/hmd Aug 30 00:50:09.897 info [OSVR]: Z:\j\workspace\OSVR-Core-Build-Win\BIT\64\TRACING\OFF\VS\12\host\windows\src\osvr\Common\ClientInterface.cpp:38: Interface initialized for /com_osvr_VideoBasedHMDTracker/TrackedCamera0_0/semantic/hmd/front Aug 30 00:50:09.898 info [OSVR Server]: Successes: Aug 30 00:50:09.898 info [OSVR Server]: - com_osvr_VideoBasedHMDTracker/VideoBasedHMDTracker Aug 30 00:50:09.898 info [OSVR Server]: - org_osvr_filter_videoimufusion/VideoIMUFusion Aug 30 00:50:09.899 info [OSVR Server]: Aliases found and parsed from config file. Aug 30 00:50:09.899 info [OSVR Server]: Display descriptor found and parsed from config file. Aug 30 00:50:09.899 info [OSVR Server]: RenderManager config found and parsed from the config file. Aug 30 00:50:09.900 info [OSVR Server]: Triggering automatic hardware detection... Aug 30 00:50:09.900 info [OSVR Server]: Registering shutdown handler... Aug 30 00:50:09.900 info [OSVR Server]: Starting server mainloop: OSVR Server is ready to go! Aug 30 00:50:09.901 info [OSVR Server]: Performing hardware auto-detection. Aug 30 00:50:49.993 info [OSVR Server]: Added device: com_osvr_Multiserver/OSVRHackerDevKit0 Aug 30 00:50:49.996 info [OSVR Server]: Added device: com_osvr_Multiserver/OSVRHackerDevKitPrediction0 directx_camera_server: Can't create video enumerator (no cameras?)

Video-based tracker: Could not open the tracking camera. If you intend to use it, make sure that all cables to it are plugged in firmly. Video-based tracker: Windows users may need to exit other camera-using applications or activities until after the tracking camera is turned on by this plugin. (This is the most common cause of messages regarding the 'filter graph')

Aug 30 00:51:10.128 info [OSVR]: Z:\j\workspace\OSVR-Core-Build-Win\BIT\64\TRACING\OFF\VS\12\host\windows\src\osvr\Client\AnalysisClientContext.cpp:76: Got updated path tree, processing Aug 30 00:51:11.135 info [OSVR]: Z:\j\workspace\OSVR-Core-Build-Win\BIT\64\TRACING\OFF\VS\12\host\windows\src\osvr\Client\TrackerRemoteFactory.cpp:93: Constructed a TrackerHandler for com_osvr_Multiserver/OSVRHackerDevKitPrediction0@localhost:3883 sensor 0 Aug 30 00:51:11.137 info [OSVR: org.osvr.analysisplugin]: Successfully produced handler for /com_osvr_Multiserver/OSVRHackerDevKitPrediction0/semantic/hmd Aug 30 00:51:11.139 info [OSVR: org.osvr.analysisplugin]: Could not resolve source for /com_osvr_VideoBasedHMDTracker/TrackedCamera0_0/semantic/hmd/front Aug 30 00:51:11.141 info [OSVR: org.osvr.analysisplugin]: Connected 1 of 2 unconnected paths successfully Aug 30 00:51:11.143 info [OSVR Server]: Sent path tree to clients. vrpn: Connection request received from 127.0.0.1: 127.0.0.1 59618 Aug 30 00:51:11.151 info [OSVR Server]: Performing hardware auto-detection. directx_camera_server: Can't create video enumerator (no cameras?) Aug 30 00:51:31.222 info [OSVR Server]: Sent path tree to clients. vrpn: Connection request received from 127.0.0.1: 127.0.0.1 59755 VRPN Error (20) from com_osvr_Multiserver/OSVRHackerDevKitPrediction0: No response from server for >= 10 seconds Aug 30 00:51:31.238 info [OSVR Server]: Performing hardware auto-detection. directx_camera_server: Can't create video enumerator (no cameras?) Aug 30 01:01:47.245 info [OSVR Server]: Sent path tree to clients. vrpn: Connection request received from 127.0.0.1: 127.0.0.1 59756 VRPN Error (636) from com_osvr_Multiserver/OSVRHackerDevKitPrediction0: No response from server for >= 10 seconds Aug 30 01:01:47.251 info [OSVR Server]: Performing hardware auto-detection.

print_tree: Aug 30 00:50:36.400 info [OSVR]: Logging for C:\Program Files\OSVR\Runtime\bin\osvr_print_tree.exe Aug 30 00:50:36.401 info [OSVR: org.osvr.tools.printtree]: OSVR client context initialized for org.osvr.tools.printtree Aug 30 00:50:37.614 info [OSVR: org.osvr.tools.printtree]: Could not connect to OSVR server in the timeout period allotted of 200ms Aug 30 00:50:37.615 info [Client: org.osvr.tools.printtree]: Client context has not yet started up - waiting. Make sure the server is running. Aug 30 00:51:31.230 info [OSVR: org.osvr.tools.printtree]: Got connection to main OSVR server Aug 30 01:01:47.251 info [OSVR: org.osvr.tools.printtree]: Connected 0 of 0 unconnected paths successfully Aug 30 01:01:47.251 info [Client: org.osvr.tools.printtree]: OK, client context ready. Proceeding. Aug 30 01:01:47.253 info [OSVR: org.osvr.tools.printtree]: OSVR client context shut down for org.osvr.tools.printtree

[ StringElement] /display

[ DeviceElement] /org_osvr_filter_videoimufusion/HeadFusion

[ DeviceElement] /com_osvr_Multiserver/OSVRHackerDevKit0

edit added markup

Atihinen commented 7 years ago

Aug 30 01:18:57.610 info [OSVR Server]: Performing hardware auto-detection. directx_camera_server: Can't create video enumerator (no cameras?) Aug 30 01:19:17.665 info [OSVR Server]: Sent path tree to clients. vrpn: Connection request received from 127.0.0.1: 127.0.0.1 60064 vrpn_Endpoint::connect_tcp_to: Could not connect to machine 127.0.0.1 port 60064 Winsock error: 10061 vrpn_Endpoint::setup_new_connection: Can't write cookie. vrpn_Connection_IP::handle_connection(): Can't set up new connection! Aug 30 01:19:18.670 info [OSVR Server]: Performing hardware auto-detection.

This is what I get to osvr_server right after the osvr_print_tree.exe is finished

Atihinen commented 7 years ago

Can't see this comment which I received from email:

What does your current steamvr.vrsettings config file look like? You will find config dir in steam install root directory.

The instructions said nothing about the manifest so I haven't touched it.

driver.vrdrivermanifest.txt

godbyk commented 7 years ago

It looks like OSVR is having trouble talking to the IR tracking camera (directx_camera_server: Can't create video enumerator (no cameras?)). When you run the OSVR server, does the light on the camera turn green? If not, you might double-check the USB cable going to the camera.

The Winsock error is a little suspicious, too:

vrpn: Connection request received from 127.0.0.1: 127.0.0.1 60064
vrpn_Endpoint::connect_tcp_to: Could not connect to machine 127.0.0.1 port 60064
Winsock error: 10061

While osvr_print_tree got the tree data okay, I'm concerned there may be some communication problem with the OSVR server.

Winsock error 10061 means the connection was refused:

Connection refused. No connection could be made because the target computer actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host—that is, one with no server application running.

Atihinen commented 7 years ago

@godbyk sorry for late response. Currently I don't have the IR camera added in setup. Is it necessary to have? I have it in the box. Never used it.