Connect to VR server failed (301)

[godbyk]

When I run Steam VR, the control panel reports that it couldn't connect to the VR server (error 301) and therefore it couldn't find an HMD. (This appears to be a step backward from a couple versions where it would detect the HMD but complained that it wasn't receiving pose updates.)

I've attached some log files as well. In the vrserver.txt file, you can see where the OSVR driver reports having an available HMD. (The messages prefixed by osvr' are emitted by my driver.)

The vrclient_vrmonitor.txt log file shows the following two messages at the end:

    Timeout while waiting for message of type 101
    Invalid response to connect message. Connect failed

Per Joe of Valve Software:

When an instance of vrclient (i.e. an app) connects to vrserver it sends message 100 (Connect) and expects message 101 (ConnectReponse) in response. In this case the connect is taking a long time to get back and the client will only wait 5 seconds. According to the vrserver log, though the whole startup process is taking less than a second so there’s something fishy going on.

vrserver.txt

Wed Jul 08 02:59:18 2015 - ================================================================================================
Wed Jul 08 02:59:18 2015 - ================================================================================================
Wed Jul 08 02:59:18 2015 - VR server (v1435962534) starting up with config=C:\Program Files (x86)\Steam\config
Wed Jul 08 02:59:18 2015 - Load Config from C:\Program Files (x86)\Steam\config\steamvr.cfg
Wed Jul 08 02:59:18 2015 - lighthouse: Attached HID Devices:
Wed Jul 08 02:59:18 2015 - lighthouse:     46D, C52B: s/n 㮷炿䂐0: Cordless Receiver
Wed Jul 08 02:59:18 2015 - lighthouse:     46D, C52B: s/n Cordless Receiver: Cordless Receiver
Wed Jul 08 02:59:18 2015 - lighthouse:     1532, 300: s/n \\?\hid#vid_1532&pid_0300&mi_00#7&221ec141&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}: Razer Hydra
Wed Jul 08 02:59:18 2015 - lighthouse:     764, 501: s/n \\?\hid#vid_0764&pid_0501#6&3b240b79&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}:  CP 1350C
Wed Jul 08 02:59:18 2015 - lighthouse:     46D, C221: s/n \\?\hid#vid_046d&pid_c221&mi_01&col01#8&31e94e87&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}: Gaming Keyboard
Wed Jul 08 02:59:18 2015 - lighthouse:     46D, C221: s/n \\?\hid#vid_046d&pid_c221&mi_01&col02#8&31e94e87&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}: Gaming Keyboard
Wed Jul 08 02:59:18 2015 - lighthouse:     46D, C222: s/n \\?\hid#vid_046d&pid_c222&col02#7&25bd4246&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}: G15 Keyboard
Wed Jul 08 02:59:18 2015 - lighthouse:     46D, C52B: s/n \\?\hid#vid_046d&pid_c52b&mi_01&col02#8&7184af4&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}: USB Receiver
Wed Jul 08 02:59:18 2015 - lighthouse:     46D, C52B: s/n \\?\hid#vid_046d&pid_c52b&mi_01&col03#8&7184af4&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}: USB Receiver
Wed Jul 08 02:59:18 2015 - lighthouse:     572, 1410: s/n 00000000: RAZER USB AUDIO
Wed Jul 08 02:59:18 2015 - lighthouse:     46D, C52B: s/n \\?\hid#vid_046d&pid_c52b&mi_01&col04#8&7184af4&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}: USB Receiver
Wed Jul 08 02:59:18 2015 - Driver lighthouse has no HMDs. Skipping
Wed Jul 08 02:59:18 2015 - oculus: Found 0 Oculus devices
Wed Jul 08 02:59:18 2015 - Driver oculus has no HMDs. Skipping
Wed Jul 08 02:59:18 2015 - osvr: ServerDriver_OSVR::Init() called.
Wed Jul 08 02:59:18 2015 - osvr: ServerDriver_OSVR::GetTrackedDeviceCount(): Detected 1 tracked devices.
Wed Jul 08 02:59:18 2015 - osvr: ServerDriver_OSVR::GetTrackedDeviceCount(): Detected 1 tracked devices.
Wed Jul 08 02:59:18 2015 - osvr: ServerDriver_OSVR::GetTrackedDeviceDriver(): Returning tracked device 0.
Wed Jul 08 02:59:18 2015 - osvr: ServerDriver_OSVR::GetTrackedDeviceCount(): Detected 1 tracked devices.
Wed Jul 08 02:59:18 2015 - osvr: ServerDriver_OSVR::GetTrackedDeviceDriver(): Returning tracked device 0.
Wed Jul 08 02:59:18 2015 - osvr: ServerDriver_OSVR::GetTrackedDeviceCount(): Detected 1 tracked devices.
Wed Jul 08 02:59:18 2015 - Active HMD set to osvr.OSVR HMD

vrmonitor.txt

Wed Jul 08 02:59:17 2015 - ================================================================================================
Wed Jul 08 02:59:17 2015 - ================================================================================================
Wed Jul 08 02:59:17 2015 - vrmonitor starting up with config=C:\Program Files (x86)\Steam\config
Wed Jul 08 02:59:17 2015 - Runtime: C:\Program Files (x86)\Steam\steamapps\common\SteamVR
Wed Jul 08 02:59:17 2015 - Load Config from C:\Program Files (x86)\Steam\config\steamvr.cfg
Wed Jul 08 02:59:17 2015 - Tools Path: C:\Program Files (x86)\Steam\steamapps\common\SteamVR\tools exists.
Wed Jul 08 02:59:17 2015 - Demo Path: C:\Program Files (x86)\Steam\steamapps\common\SteamVR\demo exists.
Wed Jul 08 02:59:23 2015 - Unable to get shared openGL context when initializing overlay bridgeWed Jul 08 02:59:43 2015 - Open URL vrmonitor://open/statusreport
Wed Jul 08 03:01:42 2015 - Open URL vrmonitor://open/statusreport

vrclient_vrmonitor.txt

Wed Jul 08 02:59:17 2015 - vrclient startup with PID=6532, config=C:\Program Files (x86)\Steam\config
Wed Jul 08 02:59:17 2015 - Load Config from C:\Program Files (x86)\Steam\config\steamvr.cfg
Wed Jul 08 02:59:17 2015 - Starting vrserver process: C:\Program Files (x86)\Steam\steamapps\common\SteamVR\bin\win32\vrserver.exe
Wed Jul 08 02:59:23 2015 - Timeout while waiting for message of type 101 
Wed Jul 08 02:59:23 2015 - Invalid response to connect message. Connect failed

[antcodd]

Found the reason for this. Infinite loop in vrserver due to a typo in a nested loop:

vr::HmdMatrix34_t OSVRTrackedDevice::GetHeadFromEyePose(vr::Hmd_Eye eye) (osvr_tracked_device.h:388)

vr::HmdMatrix34_t OSVRTrackedDevice::GetHeadFromEyePose(vr::Hmd_Eye eye)
{
    vr::HmdMatrix34_t matrix;
    // TODO

    // Return an identity matrix for now
    for (int i = 0; i < 3; ++i) {
        for (int j = 0; j < 4; ++i) {
            matrix.m[i][j] = (i == j ? 1.f : 0.f);
        }
    }

    return matrix;
}

Edit: There is another identical infinite loop on line 628 in vr::HmdMatrix34_t OSVRTrackedDevice::GetMatrix34TrackedDeviceProperty(vr::TrackedDeviceProperty prop, vr::TrackedPropertyError* error)

Now connects but get no head pose. Not sure if this function needs to be implemented properly first?
Note: I have no headset and haven't really explored the code base. My intention is to try and get SteamVR connected to Cardboard.

PS: Why does this header file have so much implementation in it?

[rpavlik]

Thanks for noticing this! I've pushed changes that resolve that loop issue and all similar ones (by using an object/expression-based method of converting math types, as well as the Eigen math library).

[d235j]

I have not experienced this issue; can someone else test and close if fixed?

[pavlo1031]

you can play steamVR game using osvr hmd now? these 2 are interacting normally for you?

[d235j]

@pavlo1031: I was able to, at least up until a recent build which seems to have changed the SteamVR driver API (without updating the "OpenVR" headers), so I'm stuck until this is resolved. Try previous versions in the betas tab for SteamVR, but be warned — the steamvr server may not start automatically if you're on Mac OS or Linux.

[pavlo1031]

i'm using the driver "Windows alpha binaries: Download Windows Alpha", still trying and the issue is still there, which has the only directory "drivers" in it.

do i have to rebuild this project for my own driver on my computer?

[d235j]

@pavlo1031: what issue are you experiencing exactly? You shouldn't have to rebuild it. What you may have to do is downgrade the SteamVR software in Steam (on the Betas tab in SteamVR properties).
Are you following the instructions at https://github.com/OSVR/SteamVR-OSVR#binary-usage-instructions?

[pavlo1031]

i downgraded steamVR and it does not crash now but still shows warning messagebox that says "VR_Init failed with Unable to initialize necessory OpenVR interfaces."

Then i ran Team Fortress 2. Screen direction was changed by hovering the mouse right & left, but i don't know if the osvr HMD is really interacting with steam.

What does it look like when they interacts normally? rotating the hmd by an angle can change screen direction in the game? (for now it cannot)

Could you please tell me how to know if steam and osvr hmd are interacting normally?

[Someguysname]

I'm also unable to get SteamVR working properly with my hmd. I'm using v1448479831 of SteamVR but I'm getting a timeout on the VR_Pipe instead.
vrclient_hellovr_sdl.txt

[zhengjiezxxy]

@pavlo1031 how to downgrade steamvr? Steam will update the software automatically.

[d235j]

I'm having a hard time getting this to work with any current version of SteamVR. I'm sorry there isn't more progress, but it's not in my hands at this point.

[pavlo1031]

Finally, my elder colleague sort of solved it
steam apps now can co-work with osvr hmd now.

1). Please upgrade/downgrade SteamVR to the version "v1444268063".
[!] right-click on steamvr item, open the "properties" window, go to "BETAS" tab
you'll see a drop-down list, and select the version you wanna use, and re-downloading
and re-installation will start then.

2). Before you run steam app (hellovr_sdl.exe or other steam games), please confirm your pc's resolution is set to exactly 1920x1080.
(if your computer does not support such a high resolution, your can use other monitor, like TV)

3). Start SteamVR.

4). Start the game.

5). After entering the game (for example, Team Fortress 2), open the "option" window, enable Virtual Reality mode, and go back to TF2's homescreen, you'll see a button
"Activate virtual Reality Mode" or sth like that, click on it, and the screen will become side-by-side.

P.S. If the button "Activate virtual Reality Mode" doesn't show, set launch parameter "-vr"
(not including the double-quote) to the steam app or game that you're going to run.
[!] HOW-TO: Same way open the "properties" window, you may see something about launch
parameter, set it to -vr and start the game.

After doing all of these everything works fine, hope it helps :) !!

[typhoidcoma]

Just got the files to build on Win 10, no longer getting a crash with latest SteamVR beta and latest Core, but now Its back to not reconizing the HMD. Progress :-)

[fatalnickle]

What core version Tyhpoid? Im pretty sure I have the latest.. SteamVR doesnt crash anymore, but still isnt detecting my osvr.

[zhengjiezxxy]

version "v1444268063" doesn't work for me(latest driver). The error is not recognizing the HDM. But v1448479831 works.

[fatalnickle]

Nice. Kind of half way working. Still says Not Ready, and my left and right's seem to be backwards. even though when i look at the screen under the lenses its not. I put it on and theyre backwards. its weird. Keeps telling me Compositor is not fullscreen as well, when it is.

[fatalnickle]

[typhoidcoma]

Yup, looks pretty typical as of late.

[fatalnickle]

When I look at my screen under the lenses it looks just like that. But when I put it on I can see the left side in my right eye and the right side in my left eye... So confusing.

[zhengjiezxxy]

@pavlo1031 which versions of core and plugin do you use?

[typhoidcoma]

Downloaded v0.6-740-g0195020 and updated to the latest SteamVR beta on Win 10. Works like a friggin charm. Having some camera height calibration issues, but I think I can work through that with the config file. Also using latest core snapshot.

[zhengjiezxxy]

@typhoidcoma Also using latest core snapshot. do you mean the latest plugin?

[typhoidcoma]

Yes latest plugin as well.
https://bintray.com/osvr/SteamVR-OSVR/SteamVR-OSVR-Win/v0.1-35-g8a0724b-core-v0.6-740-g0195020/view

On Mon, Jan 11, 2016 at 12:04 AM zhengjiezxxy notifications@github.com
wrote:

@typhoidcoma https://github.com/typhoidcoma Also using latest core
snapshot. do you mean the latest plugin?

—
Reply to this email directly or view it on GitHub
#5 (comment).

[zhengjiezxxy]

@typhoidcoma Thanks. It work on me(windows7), I can run the demo(hellovr_sdl.exe ), but when I play Team Fortress 2, I cannot find "Virtual Reality" mode, and there is a message box that says " Init failed with unable to initialize necessary OpenVR interface.

[toxicFork]

Is your HMD / HDK display on portrait or landscape, and is it to the left
or right of your other displays, and what is its resolution? Can you take a
screenshot of your monitor arrangement window please? I think it may be
related to another issue.

On Mon, 11 Jan 2016 09:12 zhengjiezxxy notifications@github.com wrote:

@typhoidcoma https://github.com/typhoidcoma Thanks. It work on
me(windows7), I can run the demo(hellovr_sdl.exe ), but when I play Team
Fortress 2, I cannot find "Virtual Reality" mode, and there is a message
box that says " Init failed with unable to initialize necessary OpenVR
interface.

—
Reply to this email directly or view it on GitHub
#5 (comment).

[zhengjiezxxy]

This is my display settings.

[toxicFork]

Hmm... I think it's because your main window is not 1920 pixels wide... Can
you try setting it to 1920 wide please? May be related to #23.

On Mon, 11 Jan 2016 09:20 zhengjiezxxy notifications@github.com wrote:

This is my display settings.

[image: display1]
https://cloud.githubusercontent.com/assets/5151510/12229964/832a3be0-b887-11e5-905d-802f39a00082.PNG

[image: display2]
https://cloud.githubusercontent.com/assets/5151510/12229971/9b2440d8-b887-11e5-9bcc-13f53ec7b6ad.PNG

—
Reply to this email directly or view it on GitHub
#5 (comment).

[fieldy1]

Ok all, u can get this working by doing the following -
Steamvr = latest version
Osvr-steam driver = SteamVR-OSVR-Win-Build-v0.1-35-g8a0724b-core-v0.6-743-g790672e.7z

This works for me and I can run hl2, I'm testing more this week

[godbyk]

We've just released an updated SteamVR-OSVR driver that should work with the current release of SteamVR. Please give it a try and report back if you encounter any problems.

[godbyk]

I'm closing this isssue due to a lack of information. If you are the original filer of this issue and still encounter this problem, feel free to reopen this issue. If you're not the original filer of this issue, please open a new issue instead.