Opentrack relative translation
-
Is relative translation behave differently from TrackIR’s TrueView?
What is the best setting regarding relative translation for BMS?
-
TrueView keeps a movement history. After:
- move forward
- rotate 90 deg left
- more forward (physically toward screen)
will result in moving forward then left.
In opentrack, it’ll result in moving left twice since it doesn’t keep a “memory” of the path the user took.
-
This probably why TrackIR sometime has trouble returning to center with Trueview on. Those movement history algorithm must complicated things.
-
Actually there’s a simple solution for trueview – get closer to the origin, closer the user gets to the centered position.
I’m not too convinced about ripping off trackir’s features. There are some “political matters” that are better left how they are. Were things different, I’d implement it. Let’s see how the market looks like in a few years. For now, I see no new “trackir enhanced” games and likely market shift toward true VR. If they become even less of a threat, I can rip off the feature.
While I said that I’d defend opentrack to the last legal recourse, and that holds as before – I’m not inviting legal drama intentionally. For now, we have all “trackir enhanced” and otherwise, games, supported by the NPClient protocol. This is already a big blow, given freetrack never did that. Look up the legal threats toward the freetrack team in 2008. That was the reason the project got abandoned.
I’d expect properly-set-up opentrack to work indistinguishably the same or even better than trackir (in terms of basic usage). That is, right filter settings, correct model, 640x480@60Hz.
TL;DR if naturalpoint becomes even more irrelevant with time, they won’t risk another incident like the freetrack legal threat. Then a rip-off feature is possible.
-
… I could swear that I’ve missed the word ‘monopoly’ somewhere above … but its just me I guess…