Forum Replies Created
-
Posts
-
A better option may be using something like katvr pucks (or maybe a single real waist tracker) and combining that with a single connect, or multiple connects, as it at least provides rotation information that can be relied on somewhat.
Guys, settle down 🙂
I know we would all like this, but stop and think for a moment about the complexity of using 2 connect devices. How would you even know which one is accurate at any given time? The skeleton fed to the software by the device only supports facing, and when it doesn’t know, it pretty much makes it up.
Sit back, breath, and realise that doing this may not be even possible, and if it is possible, it won’t be easy. I think some people are misreading what greg said earlier in experiments. Promising probably simply means he can make 2 connects work with 2 different feeds, but combining them in a meaninful way, and without needing a supercomputer to temporally process previous sheleton positions to guess the current bones from previous movements using AI, well that may be another thing totally.
From a coding point of view, I can completely understand why he would choose to do PSVR first. It’s useless to me, but I can completely understand.
For anyone here with a kat loco, through a bunch of experimenting I have managed to get them to show up as normal trackers (so the mocap mode will be available to software other than vrchat).
Extract kat_tracker_actual_tracker7.7z into <Steam Folder>\steamapps\common\SteamVR\drivers.
I have also hacked together some better looking render models for them that actually look somewhat like the kat loco trackers and are about the right size in vr.
Extract kat_tracker_better_rendermodel.7z into <Steam Folder>\steamapps\common\SteamVR\drivers
I would still like to see driver4vr take control of the trackers as maybe it can fix the silly pendulum movement of the loco drivers, but this at least gets them working for stuff.
Enjoy.
Actually it would be nice if it could simply take the kat trackers when in mocap mode from steamvr and emulate vive trackers so they are actually detected by software without kat support added.
Long term though, i could see them being useful as a secondary source of rotation data to combine with driver4vr’s virtual skeleton. Maybe could fill in some blank spots like when too close to kinect for it to see the whole body, etc.