peroht
commented
5 years ago Yes, you are not alone :)
This is a problem with applications written in Unreal. The implementation of openvr in Unreal is lagging behind. I am not an Unreal developer but from what I see there is no support for other controller types than this, (I have not accessed the source code, only looking at the api docs on the homepage):
http://api.unrealengine.com/INT/API/Plugins/SteamVR/ESteamVRTrackedDeviceType/index.html
enum ESteamVRTrackedDeviceType { Controller, TrackingReference, Other, Invalid, }
while openvr defines these classes and types:
enum ETrackedDeviceClass { TrackedDeviceClass_Invalid = 0, // the ID was not valid. TrackedDeviceClass_HMD = 1, // Head-Mounted Displays TrackedDeviceClass_Controller = 2, // Tracked controllers TrackedDeviceClass_GenericTracker = 3, // Generic trackers, similar to controllers TrackedDeviceClass_TrackingReference = 4, // Camera and base stations that serve as tracking reference points TrackedDeviceClass_DisplayRedirect = 5, // Accessories that aren't necessarily tracked themselves, but may redirect video output from other tracked devices TrackedDeviceClass_Max };
/* Describes what specific role associated with a tracked device / enum ETrackedControllerRole { TrackedControllerRole_Invalid = 0, // Invalid value for controller type TrackedControllerRole_LeftHand = 1, // Tracked device associated with the left hand TrackedControllerRole_RightHand = 2, // Tracked device associated with the right hand TrackedControllerRole_OptOut = 3, // Tracked device is opting out of left/right hand selection TrackedControllerRole_Treadmill = 4, // Tracked device is a treadmill TrackedControllerRole_Max = 4 };
From my experiences many Unreal games filter out controllers based on index - just like you say. The problem here is that since the treadmill driver is of the type "controller" internally there is no way to distinguish between the hand controller and the treadmill controller - unless the game developer has used some logic to filter out on e.g. device manufacturing strings. Thus your treadmill device driver might get an index of 1 and then the game belives that the device with an index 1 should be the hand controller - and then you have the problem you describe. Sadly.
If you follow some earlier threads you'll find that it was possible to overwrite values on one device from another devices. But the official way forward is to do exactly as you do; write a device driver and the the user use the SteamVR Input UI to remap controllers/buttons as they want.
From my experiments the Vive pucks correspond to the class TrackedDeviceClass_GenericTracker while a treadmill device is of the class TrackedDeviceClass_Controller (same as the hand controllers). Related to the ETrackedControllerRole I see no such corresponding definition in Unreal.
Maybe you have more knowledge and access to the source code and can dig deeper?
kaplat
CybershoesVR
nickos64252
andreaskern
Hello,
I am working on a custom driver for a treadmill device and my driver is working fine for a bunch of games.
In PavlovVR I have a problem though. In my opinion the game assigns the first two devices that are of type vr::TrackedDeviceClass_Controller to the left and right hand. This is a problem for my driver, as my treadmill (vr::TrackedDeviceClass_Controller with treadmill role) always registers before the vive controllers and therefore the treadmill is assigned to one of the hands. Now my questions:
1) Is my binding of the treadmill false? 2) I use alwaysActive=true and that is why my treadmill is always assigned before the controllers. Is there a way to activate the treadmill after the controllers? Is there a way to activate the treadmill without using alwaysActive=true at all? 3) Has anybody else had this problem and can point me in the right direction to fix it? Or is it a game problem?
Thanks in advance for all answers. I would really appreciate the help.