SteamVR Developer Hardware

SteamVR Developer Hardware

View Stats:
Wevr 16 Jun, 2015 @ 10:53am
No compositor, Error 303
Hey all,

Our VIVE setup has been purring along happily until this morning when I got a redlight in our Steam VR toolbar. Taking a look at the logs, we have this error:

Tue Jun 16 17:36:49 2015 UTC - RuntimePath : C:/Program Files (x86)/Steam/steamapps/common/SteamVR
Tue Jun 16 17:36:49 2015 UTC - ERROR: Tue Jun 16 17:36:49 2015 UTC - Invalid adapter specified!Tue Jun 16 17:36:49 2015 UTC -
Tue Jun 16 17:36:49 2015 UTC - Failed to initialize compositor
Tue Jun 16 17:36:49 2015 UTC - Failed to start compositor with error 303

I'm guessing that "Invalid Adapter specified" is at the root of our troubles. At last startup, USB gave us some trouble about not being able to install the drivers for the Spanner. The USB2 Hub driver installs fine, then it tries to install something else and fails out.

Any thoughts? Reboots don't seem to be helping.


EDIT: FIXED! Officially the silliest mistake yet. If you right click on the Windows desktop and select "Screen Resolution", we needed the Vive monitor to be on the RIGHT, not the left and to be monitor "1".

That fixed it. All the USB stuff was a separate, coincidental incident.
Last edited by Wevr; 16 Jun, 2015 @ 1:04pm
< >
Showing 1-13 of 13 comments
Wevr 16 Jun, 2015 @ 11:19am 
Just uninstalled the device with usbdevview. It reinstalled (And took a minute or two?), but I'm still getting the same error. I'm not getting the USB "couldn't install driver" error anymore, but still getting the 303 from Compositor.

Via USBdevview, it seems to think that the spanner is a USB3.0 Camera- Is this standard?
Last edited by Wevr; 16 Jun, 2015 @ 11:22am
Wevr 16 Jun, 2015 @ 11:50am 
More updates! So, we lost SteamVR and the headset for a bit. We got rid of every clearly non-essential USB device and forced a reinstall of the headset drivers. 4/5 of the drivers installed fine, one did not and gave an "Unknown USB Device" error. Steam VR and HMD are now green, Compositor is still red.

The "Unknown Device" seemed to the HDMI/video bit of the spanner. There's no video in the headset and the PC isn't recognizing the headset as a second monitor. Drilling down, it looks like the issue is the "STM32 Virtual Comport in SF Mode" USB device.
Last edited by Wevr; 16 Jun, 2015 @ 11:56am
Wevr 16 Jun, 2015 @ 12:10pm 
Final update as we've kind of hit a wall here- Walked through a fresh re-install again, it failed the STM32 Virtual ComPort in FS Mode driver installs again. Same issues. I'm guessing this is whats causing the Compositor to flunk out. Any thoughts?

EDIT: Managed to manually install the STM32 drivers and the devices installed fine via Windows. Still getting the 303/301 errors
Last edited by Wevr; 16 Jun, 2015 @ 12:42pm
Wevr 16 Jun, 2015 @ 12:41pm 
Interestingly, even though the error I get in the Compositor log file is a 303, the error its showing in the System Report is a 301 (Connect to VR Server failed). I'm guessing the 303 derives from the 301.
Tammeka Games 18 Jun, 2015 @ 8:44am 
We're getting the same error having just setup the dev kit on a different PC. Tried the simple solution of making sure the HMD is set to display 1 on the right hand side, no joy.
Programmer Joe  [developer] 18 Jun, 2015 @ 6:59pm 
Unfortunately Error 303 is returned for a bunch of different causes. Can you post the log files now that the HMD is the rightmost monitor? I'd like to see some contents from vrcompositor.txt, vrclient_vrcompositor.txt, and vrserver.txt.
Not sure if you are trying this on a machine with multiple displays, but just in case, we saw this suggestion in another topic and it helped us:

http://steamcommunity.com/app/358720/discussions/0/613956964585890398/#c613956964585976620

If we plug in the Vive or reboot while both of our monitors are connected, nothing shows up in the headset and we get the red status bar lights on Steam VR and Compositor.

Trick seems to be unplugging our secondary display before plugging in the Vive. After the Vive is detected and we see the desktop background in the headset, we're fine to plug in our secondary monitor again and everything seems to work as it should. As others have mentioned, the Vive must also be set to the far right monitor position.
aaron.leiby  [developer] 19 Jun, 2015 @ 1:45pm 
Originally posted by Holden@TButt:
Trick seems to be unplugging our secondary display before plugging in the Vive. After the Vive is detected and we see the desktop background in the headset, we're fine to plug in our secondary monitor again and everything seems to work as it should. As others have mentioned, the Vive must also be set to the far right monitor position.

Which version of Windows are you seeing this happen?
Originally posted by aaron.leiby:
Which version of Windows are you seeing this happen?

Windows 7 Pro x64, with a GeForce 780.
Programmer Joe  [developer] 20 Jun, 2015 @ 10:39am 
Can you post a screenshot of your display settings before and after plugging in the second display?
Sure thing. Top image is before plugging in second display, bottom image is after:
http://imgur.com/Eci5u8Y
layla.mah 1 Jul, 2015 @ 6:09pm 
I'm running into the same issue (again) after a fresh OS install :(

I had overcome it in the past, though I don't recall how... but with the fresh install of 8.1, the issues are back.

I've installed the Microsoft C++ 2010 Runtimes (x86 and x64), and also tried ensuring that vrcompositor/vrserver are both not blocked by Windows Firewall. All of my USB devices are showing up correctly after some tweaking in USBDevView and removing/re-inserting..

I'm a bit stumped :/
Jason 28 Nov, 2016 @ 7:11pm 
A few things, doing it from memory, not sure if anything will help, maybe too basic. Vive needs to be on the right AND I think it also needs to be monitor number 2. Check resolution on vive, should be at it's highest setting. You can try to setup first by turning off direct to vive in steam vr settings and making sure that you have windows set to extend these displays. I may have had some issues when I switched HDMI ports or usb ports. Also, I went into my device manger to USB devices and deleted everything, with no harm done, just plugged it in again. Thought I was very scared to do so and not sure I would recommend it.
< >
Showing 1-13 of 13 comments
Per page: 15 30 50

Date Posted: 16 Jun, 2015 @ 10:53am
Posts: 13