I should add that I just thought of something else, I have RiftCat so I used that and the kinect, with nothing else plugged in (my usb devices are key/mouse, wifi card, and kinect only, and it STILL dropped to 0 mid-calibration.
(as well as complaining that my HMD wasnt tracking which was expected behaviour)
I notice that it happens frequently in two occasions:
– controllers out of KinectV1 range (i got the big POI balls so it’s better 🙂
– fast movements (i guess it exceeds the 30Hz tracking)
Sometimes, it even stay stuck at some position(longer than arms length) until i physically move the controller back to it or Driver4vr frozen and cannot be terminated (Driver4vr fps 0).
Is it possible to improve how Driver4vr error handles *tracking loss or cpu overload)? Crash recovery, restart, etc…
PS: I have to be so far away because of the narrow fov of KinectV1 (to be able to grab objects on the ground and wave my arms in the air). That means my controllers are even further down range when facing slightly away from sensor (~3m to 4m).
This reply was modified 1 year, 11 months ago by Xcalibur.