Why is the support on issues so bad?

[OptoCloud]

Not being able to get a solution to a problem you cannot solve yourself is super frustrating.

This makes SteamVR (in my experience) the worst API I've ever had to work with.

The developers hide their code even though its "OpenVR" and then ignores the majority of the issues?

Valve is such a huge corporation as well... There must be able to get someone to resolve some of these?

My issue still remains open after more than a year: https://github.com/ValveSoftware/openvr/issues/1429

All of this makes SteamVR extremely non developer friendly and infuriating, please fix this :c

[okawo80085]

I understand your frustration, however i also understand why Valve don't want to make SteamVR public

OpenVR is an SDK for SteamVR, not SteamVR itself, which does not make it easier to work with i admit And this is a serious problem with OpenVR and SteamVR right now, partially because there is no way to submit SteamVR (windows) specific issues and partially because it can be hard to distinguish between OpenVR and SteamVR issues

Whats the difference? Simple, OpenVR is what you use to build your app/driver, SteamVR is the runtime for it (which is closed source)

I don't need to explain why they wouldn't want to make SteamVR open source right?

Which brings me to this question for @JoeLudwig (because he's the last one from Valve i've seen active in this repository): Why is there no input from Valve on practically any of the recent issues in this repository? Both minor and major issues are literally ignored for almost 8 months now!

---

@OptoCloud Thank you for bringing attention to your issue and the general problem with issues in this repository

Regarding your issue however, i personally wont be of much help because i work with and interested in drivers, not the app side of OpenVR

[Rectus]

Valve has had an extremely limited team working on the SteamVR software for years now. They currently seem to be fully focused on implementing OpenXR support, which also is lagging far behind their competitors.

Valve doesn't have a traditional corporate structure and their employees have more chose on what projects they work on, so guessing there are less people willing to work on less glamorous projects like maintaining existing software.

[TheDeveloperGuy]

I think many people confuse this with a developer support forum, which it is not. I've had many issues addressed and fixed, so I don't believe they are ignored. What you do need to do is have an actual bug in SteamVR (not a difference in opinion over how something should be implemented), and a clear explanation of what it is and how to reproduce it. And be lucky. The OP's issue report is in the form of a question, and so belongs on a developer support forum. I believe the SteamVR community forums would probably be a better place for that. Moaning about the "Open" in OpenVR is pointless (apparently it refers to the API, and is not shorthand for Open Source VR - OSVR is that). My 0.02.

[OptoCloud]

Ok I know the thing about this not being a support forum. The issue i made a year ago was because I had tried to make it do something and I had worked on it for two mo ths and viewed a dozen other repositories and talked with lots of other devs about how to solve this. Most people use Unity and lets Unity act as a wrapper, but outside of that noone has done it. And looking at the Api docs OpenVR should allow for the behaviour im looking for. But OpenVR misbehaves and blocks input to other applications, it also has major issues with the framebuffer api and resizing the overlay (doing it the way the Qt example does it). My plans was making a Qt wrapper for OpenVR to make it easier for others to make stuff without struggling with this API. Im starting to think this is a bug and not actually me doing it wrong. Concerning the "Open"VR... Sure. But they could at least make some attempt to tell peaople to go to steam support and close issues so actual important issues dont get drowned.

[danwillm]

I think extensions in documentation and examples could help a lot, I certainly struggled getting started with OpenVR (especially with skeletal input as there isn't really much on it) and have seen many issues opened here and on the steam support forum that are rather simple questions about OpenVR, but I'm sure are confusing to new developers.

To help this, perhaps Valve could open the wiki up to the community to edit (I've seen some attempts of vandalism in the past on the wiki so maybe this isn't ideal), or include some examples of open source drivers and apps for references? Happy to include a couple of examples that we've written.