Latest update issues... Connect to VR server failed (301)

[SuppleTeet]

I went to demo my project today, set everything up in a new location, and when I started steam to run the room setup I noticed SteamVR updated. Now I'm getting screen flickering, audio cuts out periodically, and there's some visual noise (green dots) in certain spots. I'm getting "SteamVR failed to initialized for unknown reasons. (Error: Connect to VR server failed (301))" errors as well, even though it runs with those problems.

I can't really show like this, is there a way to roll back to the previous SteamVR? I looked online and it seems like there is not.

[bendotcom]

There are multiple betas available (look under properties). They're identified by release timestamp because one branch marked "previous" was becoming unwieldy.

[SuppleTeet]

Oh great, thanks!

[SuppleTeet]

I got it working, but I'm not sure that the SteamVR update was even the problem. I'll check again when I get home but it seems what fixed it was plugging the breakout box ac adapter straight into the wall instead of a cheap power strip that my laptop was also plugged into.

[Gerald]

The green dots might be a cable issue. I tried a different (PC) DVI to HDMI (box) cable first and had green dots too because it was too long.

[SuppleTeet]

I'm back home and trying to get everything back to normal.

While I did get it working on Saturday I wasn't actually able to get rid of the "SteamVR failed to initialized for unknown reasons. (Error: Connect to VR server failed (301))".

I can't run Room Setup anymore, not sure it's even SteamVR version that's causing it anymore.

I tried:
* New HDMI cable
* Rolling back SteamVR (Removing USB devices and rebooting between tries)
* Rolling back nvidia drivers

Anything else to try?

Is it something with windows 10?

[SuppleTeet]

Ok figured some stuff out...

The green dots/artifacts come from the HDMI cable, the breakout box -> HMD one. If I jiggle the HDMI connection to the HMD around the green dots flicker on and off. If I connect a different HDMI cable from the breakout box to the HMD I cannot reproduce. (Thanks indienerd! I only tried replacing the PC->Breakout box hdmi cable when I read your post originally)

Connect to VR server failed (301) This was a windows 10 thing. Steam needs to be set to run as administrator... which I did when I first set everything up but somehow it got turned off. Maybe a steam update? Maybe I stupidly did it myself and don't remember?

I will say though that I was actually able to run vrcompositor.exe --keepalive and then run steamvr_room_setup.exe manually and everything worked just fine outside of steam.

[JERENBOR]

I was having the same VR compositor issue today as well. Windows 10 machine, moved to new location, suddenly was getting error 301 and couldnt run room setup. Occasionally after vigorous power cycling I could enter the room setup, but despite having green/ready components in the vrmonitor, it wouldnt see them in the room setup program.

I'm excited to try your work-around tomorrow. Thanks for investigating and sharing.

[Shadow]

We have noticed some people having problems on WIn10 if everything isn't in administrator mode. People have solved this by running Steam in administrator mode (which in turn will invoke SteamVR in the same). If you are developing with Unity you will probably need to launch it in administrator mode also if you are having this issue.

Note that it isn't consistent- I'm running in normal mode fine on my win10 workstation here so we are trying to understand what is causing the issue.

[SuppleTeet]

Good to know. I'm on Windows 10 Home, are you on Windows 10 Pro? Could have different permissions by default or something.

[PuzzaBug]

I have 301 issues all over the place unless I run in admin mode. I'm on windows 10 pro x64. I also run unity and unreal (launch the editor, not the popup) in admin mode for best results.

The green spots are just a technical glitch and won't appear everywhere, and won't appear in the dk2 kits.

[Jo]

I can also confirm whilst developing for unity the "Connect to VR Server Failed (301)" persisted until I updated to the beta branch and ran both Unity and Steam in administrator mode.
I am running Windows 8 and had the 301 issue without fail, even after any kind of restart, of both Unity or SteamVR or its components. So thanks!