'mytrackd' features

* 'mytrackd' software seems to be sufficient alternative to VRCO 'trackd'. 'mytrackd' provides about same features including comprehensive setup and calibration facilities for sensors.
* VRPN generic server (used as 'mytrackd' server side) directly supports great amount of tracking and controlling hardware currently used with VR systems including some exotic, like "Python" device. Full list of supported devices can be obtained on VRPN site. In case you device isn't supported already, VRPN provides well defined frame to develop new VRPN class as descendant of some powerful base classes
* 'mytrackd' provides very clear devices mapping model. For example, you have to specify in configuration file to which CAVE sensor particular tracker's sensor should be mapped. 'mytrackd' also rejects attempts to map few data source to same CAVE sensor, button or valuator.
* 'mytrackd' has advanced configuration solution for tracking sensors. You can instruct EACH sensor separately to get it's setup either from local file or one used by correspondent server or, finally, borrow head and wand sensors configuration from CAVELib setup files.
* 'mytrackd' uses same VRCO 'trackd' model of calibration with runtime loaded DSO. You can attach calibration filters you use with VRCO 'trackd' to 'mytrackd' without any modification, for example this free one.