I don't think that to be the case grunch and you know it, else you would be whinging that you couldn't use ATI drivers/ control panel on an nVidia card and visa versa, or any driver with similar product those drivers were developed for, or any joystick programmer with any joystick, interswap Intel and AMD cpus, etc..... you've made allegations without proof, admit to having no proof and agree that developers/ publishers shouldn't have to cater to hackers.

Yeah, but I also understand the principle of reasonable doubt. I don't see how your link supports your allegations about the Freetrack developers, either. How could a bunch of free software developers "intimidate" a game developer? I thought you were going to bring up something more substantial than people bitching in a forum thread. I thought game developers had thicker skins than that.
I understand enough about the way that joystick devices work to know that there was no need to create the proprietary interface. They could have even kept their software as it is, all they had to do is pass the output to a virtual joystick instead of via an encrypted datastream as it is most recently. They wouldn't even have to make the virtual joystick device themselves, they could just use the freely available PPJoy, although they would likely be wise to make their own solution to avoid infringing copyright themselves.
The other benefit to this is that developers wouldn't even have to code in support for TrackIR specifically, they would just have to make view position accessible to a joystick device, so it would even make developers' lives easier.
Incidentally, I didn't know that NP broke older TrackIR hardware in newer games just to break Freetrack, so that at least was informative. I wonder if my TrackIR 3 would work with Arma II?

EDIT: In fact, it seems like the cause of the controversy in that thread was the developers' insistence on ignoring the fact that Freetrack has its own API that developers are free to use.

Round and round we go...

Tesll us what it is that you think NP have intellectual property rights over. Is it:

(A) Any device that measures head movement and uses that to interface with a computer.

(B) Any device that measures head movement and uses that to interface with a computer using the particular protocol they developed.

(C) something else entirely.

If it is (A) they were not original. If it is (B) then anyone can develop an alternative - or use the existing standards.

If it is (C) then for god's sake tell us what it is.

NP are just protecting their code and the product's good name in quality.

I've basically said before there is nothing wrong with someone developing their own interface, its just when the hack into someone else's that there is a problem. So why all your hoo har?

for your edit... perhaps the developers have never been approached to include the api via a patch. You've already said earlier that the first was BIS and you've agreed that developer/ publishers shouldn't have to cater to hackers.



yes well tell us about it, you've been running a right merry-go-round.

what is it exactly, you don't understand now?

You'd understand why it's possible if you understood a bit more about computer hardware. ATI and NVidia make their own proprietary drivers because their drivers are a direct interface between hardware and software, their drivers communicate directly with the card. TrackIR's software communicates with the TrackIR device via USB, which first of all does a lot of the interfacing itself, and secondly is too slow a protocol for the speeds required by a 3D engine. It's then passed to the game via their encrypted datastream. The TrackIR software can recognise the head position on its own, so it would be quite possible to pass that information from the TrackIR software to a virtual joystick instead of encrypting it and sending it to the game. In fact, the TrackIR software has to be running for the device to work anyway so I don't see how that could ever be a problem.

which means?

That there was no good reason to create the interface in the first place except to cause other implementations difficulty once theirs was in use. It made developers' lives harder as well since they had to add TrackIR support specifically.

As to BIS, given what's written in that thread it seems like the Freetrack developers were tearing their hair out about showing their API to BIS and BIS saying that they couldn't implement it because it used the NP API. Which it didn't. Sounds like a misunderstanding, but it looks like it got pretty out of hand.

EDIT: Anyway, I'm off out, talk to you guys later.

err did sim connect or devicelink exist when TIR first came out?

Following your "logic" why couldn't other people interested in headtracking write their own and approach developers for inclusion, or take advanatge of what was available? its what I've said before.. its between the developer and the particular tracker people... nothing to do with NP

Why hammer NP?

The BIS biz didn't read like you were suggesting at all... they say quite clearly; no-one approached them about inclusion... quite clearly the FT does use the TIR side of things (if nothing else is available) and that goes against NP licensing and copyright.

Perhaps FT should just get rid of anything NP, in any form and go about taking an honest approach?

BIS set a precedent by supporting both TrackIR and Freetrack so it is clear there is no license problem or legal issue with Freetrack. The only unclear thing is your motivation for spending a 14 page thread slandering Freetrack.

I don't believe anyone has said there is any issue with FT (or any other) and TIR running side by side Sigur... where did this come from?
Also pointed out were the means of having a camera run as tracker, without having to hack into NP software.