There is enough information on the internet so that I can pierce together a mapping for the Rift, but for other devices like the Windows Mixed Reality headsets some inputs may not work.Īlso I can only map a button to another button for which an input component already exists.
I own only a Vive, so I can only know it for sure for this device. To be able to remap buttons I now need to know to what button a specific input component is mapped, which I cannot for all devices. Runtime tells application that button 2 has been pressedon device 4.Driver tells runtime that input component "/input/grip/click" (that you need to register first at startup) on device 4 has been set to true.The new API now basically works as follows: Runtime tells application that button 2 has been pressed on device 4.įor button remapping i only needed to change some numbers, and everything directly translated to the application side.Driver tells runtime that button 2 has been pressed on device 4.The previous API basically worked as follows: Therefore the code may (and most probably will) still contain bugs, and some things don't work as expected. There are some MASSIVE changes to the driver API which required me to completely overhaul the hooking mechanisms and significantly change the inner working of Input Emulator. Finally got Input Emulator working with the new OpenVR driver API.
0 kommentar(er)
