Christopher-Marcel Esser

I love the idea of having a high-level one in VRTK, so I vote for your second point above.

Guys. If there is any you'll see it because this issue is updated. You could also do it yourself, PRs welcome!

Any implementation should definitely just be about abstracting overlays. The target shouldn't be a specific use case. With v4 work going on it will be a while until I can...

Actual OpenVR property key name is found [here](https://github.com/ValveSoftware/openvr/blob/5d0574bf6473130d25dd296ad30206ccd148590b/headers/openvr_api.cs#L3314). If Oculus doesn't provide an event for changes I vote to find a place we already run per-frame logic in already and...

You can only assign members of the repo AFAIK. A good workaround would be to just some labels and add one like `already taken | WIP` or something 😄

The only related functionality I can find is that Squirrel will be removing the `.xml` file that comes along with a `.dll`: https://github.com/Squirrel/Squirrel.Windows/blob/250fe4ce09035a682d90836f8c89097760638f66/src/Squirrel/ReleasePackage.cs#L264-L271 I can't see Squirrel removing any other...

Haha I'm just a user as you guys are, maybe @paulcbetts can chime in. I do think Squirrel having an opinion on a lot of things and pushing best practices...

I already provided you with the source code and instructions to change it. Fork + clone + edit + compile isn't that hard 😉

>we need to refresh this info when bindings are updated Either https://github.com/ValveSoftware/openvr/blob/64fc05966a109543a1e191a45e1ab3a25a651211/headers/openvr.h#L663 or https://github.com/ValveSoftware/openvr/blob/64fc05966a109543a1e191a45e1ab3a25a651211/headers/openvr.h#L786 I think. >bring up the binding UI https://github.com/ValveSoftware/openvr/blob/64fc05966a109543a1e191a45e1ab3a25a651211/headers/openvr.h#L4350-L4354 These are actually documented at the end in...

SteamVR beta 1.9.7: >Fixed some memory leaks when VR_Init is called repeatedly in long-running applications. >https://steamcommunity.com/games/250820/announcements/detail/1714113379461314416 This sadly does _not_ solve the issue. The repo snipped in the first post...