SteamVR Developer Hardware

SteamVR Developer Hardware

View Stats:
Lon Sep 19, 2016 @ 8:16am
IVRDriverDirectModeComponent changes
Hello,
I've noticed that newest beta version of SteamVR utilizes IVRDriverDirectModeComponent with 002 suffix, and support for 001 was apparently dropped. Is the driver header file going to be updated on GitHub before releasing those changes on the main channel? I am aware that beta releases are subject to change but I want to make sure that I'll have enough time to update our driver, especially if 01 version is being dropped.
< >
Showing 1-5 of 5 comments
aaron.leiby  [developer] Sep 19, 2016 @ 12:51pm 
The interface has been updated, however, the old interface should continue to work. If you find that's not the case, let us know and we'll try to reproduce the issue.
Lon Sep 20, 2016 @ 6:17am 
Thanks for reply. Unfortunately, according to vrserver logs that's not the case. I've got following message:
"Tue Sep 20 2016 11:02:04.303 - device implements IVRDriverDirectModeComponent_001, but this runtime doesn't have an adapter for that version"
Is there any way to get access to the updated interface? I'm developer of Vridge and I'd like to adapt to these changes as soon as possible so we won't break compatibility for all our users.
deedhero Oct 5, 2016 @ 10:47am 
I get that error message too, i am building a driver for our own headset. Any Ideas how i can overcome this?
deedhero Oct 5, 2016 @ 10:53am 
I also get this error message in vrclient_vrmonitor.txt:
" IPCPipe(VR_Pipe): Waiting on event failed in SendMessageInternal with res 0 and error 232"
What does that mean?
deedhero Oct 6, 2016 @ 11:07am 
Alright fixed it from new Beta update! :)
< >
Showing 1-5 of 5 comments
Per page: 15 30 50

Date Posted: Sep 19, 2016 @ 8:16am
Posts: 5