Patch for Vive Trackers support

[YuriNK]

@mordentral

Better to keep the global inputs but with a “tracked device ID” attached to it and the capability of setting input events tied to a specific id.

Is it possible now?

@mordentral

Regardless 12 trackers all adding button inputs is a use case that isn’t ever going to be needed except by extreme outliers, who can re-factor input themselves to accommodate for it.

Idea to prodive a full support for some input devices and incomplete support for absolutely similar devices is werid.

@mordentral

Even if you move input into the controllers, how are you going to keep it from bloating there too? You’ll have it easier in device by device events, but now you still have to support Oculus specific inputs and Knuckles capacitive inputs and other manufacturer input events. It still ends up being a platform by platform configuration, except with less flexibility since you don’t have re-binding and have the un-used events sitting in there.

VR-plugins could be responsible for binding their custom button events to unified keys.

ed. To be clear: For me it’s more or less theoretical discussion, I don’t have any plans like this. But I do think that tons of events - wrong solution.