![]() |
|
|
|
#1
|
|||
|
|||
|
Applying for a 'Patent' is extremely complex due to the definitions and restrictions as to what is considered 'intellectual property' and 'inventions'. The technology and software was already well established in terms of 'optical tracking' and thus 'headtracking' is an 'adaptation' rather than an 'invention'. Optical tracking has been used in manufacturing for many years, Nintendo WI remote is an optical tracker as is an optical mouse. NP can of course protect their products and registered trademarks from being used by 'another' and, quite rightly, have done exactly that.
The replies to the thread indicate that not every one feels that 'headtracking' is needed and some even dislike it. If nothing else, Freetrack gave me as an 'undecided and curious simmer' an opportunity to delve into 'headtracking' on the 'cheap'! Headtracking is now an accessory that I consider 'essential' and I owe a big thanks to FT. Would I buy TrackIR if that was my only option in a future SIM?.........probably yes! There in lies the problem and why NP will give incentives for developers to use their API. |
|
#2
|
|||
|
|||
|
I don't know the exact details, but the way i see it is this.
1) If Freetrack uses its own API, independent from NaturalPoint's API, but NP goes around to game developers and tells them to use only the NP API, then NP is clearly limiting the choices of users. Game developers should realize that and allow access to other head tracking APIs along the NP one, so that their customers are satisfied and not forced into a monopoly situation. 2) If Freetrack uses the NaturalPoint API and NP decides to encrypt it, then tough sh*t. It's NP's API and they do what they want with it. In that case, it's Freetrack itself that limits Freetrack by not coming up with a complete solution of their own, not NP who are marketing their software as they see fit. I don't know the exact circumstances, but i'd be surprised if both sides weren't a bit right and a bit wrong at the same time as usually happens That sums it up for me. |
|
#3
|
|||
|
|||
|
Quote:
|
|
#4
|
|||
|
|||
|
I bet.
Bohemia Interactive - producer of ArmAII - decided to give support to FreeTrack API after consumers request. If 1C didn't do the same, will be really a shame and a disrespect with their customers who uses FreeTrack as head tracking solution. And we aren't just a few, by the way - look at Bohemia Interactive forums... |
|
#5
|
|||
|
|||
|
Quote:
DCS allows TIR and generic head axis inputs. I use freetrack and PPJoy. Just check the PPJoy box in freetrack, assign the axes in DCS, and it's done. Unless FT's developers have lobbied for game devs to use the FT API, you can't complain about it not being used. It's when a game only uses the TIR interface, excluding all others, that I see it as unacceptable. But at the core of the issue - with 6DoF head tracking, it makes NO sense to have a proprietary API. It's more work for everyone (especially the game devs), and hurts the consumer. |
|
#6
|
|||
|
|||
|
I think the best solution would be a widely accepted standard of a single API to be used by game developers, so that they could cut down on development time. Then the people who make head tracking software would have to come up with someting that complies to this standard, or make sure their own API can interface with or "plug into" the game developer's implementation.
This not only makes it easier and faster for developers to code stuff, it also streamlines production of further titles and makes sure that everyone who wants to develop a head-tracking solution has a chance at making something work. Some will say that NP will lobby against this and it could be true, but the bottom line is they couldn't roll it back if it started. Just imagine it, SoW, DCS A-10, the next ArmA title all come out with the same head-tracking API and demand the developers of head-tracking software and devices to conform with it, instead of vice versa where the developer has to do the work. If NP doesn't do it, they'll have a whole lot of angry customers, so they will be forced to |
|
#7
|
|||
|
|||
|
Absolutely. Except that the API is pretty much already present, by use of the usual analog axis inputs.
Like TIR 1,2,3 owners who can't use TIR in new titles due to the "enhanced" NP interface! |
|
#8
|
|||
|
|||
|
you can make Tir 1,2,3, work with FT software.
|
|
#9
|
|||
|
|||
|
Quote:
Forgive me, but nothing I have read at any time convinces me I need anything else. Personally I would say only a bigger field of view (more monitors) will improve my SA, and would much rather spend money there than buy an overpriced web cam. |
|
#10
|
|||
|
|||
|
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|