[Wolf_Rider]

A third? 2/3DoF was 2 or 3 Degrees of Freedom - as distinct from full 6DoF. And actually there is a reason - some games have BLOCKED OUT the methods that you mentioned, for controlling in-game head pose, which is the ONLY reason behind this thread's existence.

Thanks and my bad... I did leave out the word 'party' where your question mark is. NP took the time and the effort to create their system (interface and tracker module), when there was no other product around... why can't others go and do the same?
TrackIR in games only came about because of few people who saw what handicapped people were using (that being SmartNav) and thought to themselves; "this is a damned good idea, can it be adapted to a gaming environment?"

This is an odd thing to be asked, 18 pages into the thread about exactly this topic. The "rhetoric" continues because it simply isn't possible in some games, or isn't possible with 6DoF, which is equally unacceptable. I created this thread to try to get 1C to state their stance - whether or not they would restrict non-NP trackers, which would negate the use of PPJoy etc.


I guess some games only recognise one joystick... one input? which goes back to my earlier comments regarding approaching developers for a patch. Have any actually been approached in a civilsed manner?


Because you didn't actually answer the question, and have avoided it previously. The topic of this thread, and my "yes or no" question, was about BoB 'listening' for head positions on standard interfaces - not tracking software using standard interfaces (which is, or easily can be, a given). Do you understand the difference? If TIR, or freetrack, or any other tracker sent head position as normal joystick axes, many games would ignore it - and I'm wondering if BoB will too. But either a 1C rep didn't read the first post of this thread, or they won't comment.



"YES or NO, Wolf_Rider: Should "BoB accept generic axis inputs for head angle and position"? Note that the question is independent of freetrack and it's developers practises. The outcome of 1C's decision will affect non-NP, non-freetrack trackers. How about it, yes or no?"

the above is your original question...

I've already said several times, what happens with third parties seeking inclusion in developer's product is between the developer and the third party. I've also already said, there should be no problem with any third party software accessing simconnect, devicelink, joystick api, or similar. The problem lies with a third party infringing another company's copyright.
Why do people keep on "forgetting" what was said earlier?