Motion controller device ID about three.vrcontroller HOT 1 CLOSED

Hi Lewis—thanks for investigating this and providing so much info! I see what you mean about the Gamepad id string. I’ve just updated my code to find the appropriate support object using startsWith() instead of a direct object property access. Do you think in the future the Gamepad API might support multiple properties for this? Like a main ID, then subversion strings? Make, model, year, version number... That sort of thing?

As for preferring to call these “Windows motion controllers” I see what you mean there. But the “style” string that I assign is meant to be an extreme shorthand to make distinguishing between supported controllers more convenient. For example one might write if( controller.style === 'microsoft' )... Brevity and clarity. (As second-generation VR rigs hit the market I may have to expand upon this, but I’ll wait to see what the landscape is before adding additional bits.)

I’ll take a closer look at the pointing pose—that’s an interesting distinction I hadn’t considered. Perhaps even worth making a new issue out of; I could revisit the pointing poses of all supported controllers.

from three.vrcontroller.