Cedric Gautier (gce++at++syseca.fr)
Fri, 14 Apr 95 11:05:04 +0200
here is the app part of the code ...
pfDPoolLock(stvPoolMem);
stvPoolPtr= stvPoolMem;
stvCoord1xyz[0]= *stvPoolPtr++;
stvCoord1xyz[1]= *stvPoolPtr++;
stvCoord1xyz[2]= *stvPoolPtr++;
stvCoord1hpr[0]= (*stvPoolPtr++)-90.0f;
stvCoord1hpr[1]= -(*stvPoolPtr++);
stvCoord1hpr[2]= *stvPoolPtr++;
stvCoord2xyz[0]= *stvPoolPtr++;
stvCoord2xyz[1]= *stvPoolPtr++;
stvCoord2xyz[2]= *stvPoolPtr++;
stvCoord2hpr[0]= (*stvPoolPtr++)-90.0f;
stvCoord2hpr[1]= -(*stvPoolPtr++);
stvCoord2hpr[2]= *stvPoolPtr++;
pfDPoolUnlock(stvPoolMem);
Well I think that's all ... I am using only a quarter of the usable half
sphere processed by the fastrak cause of strange sign chnage in xyz which I
did not solve for now ... sign changes are artefacts (may be one per 100)
providing uncorrect view behaviour sometimes ! ...
I forgot also to tell you that depending on your app you may have to
calibrate the fastrak using the alignment command name 'A' with several
parameters if you want to match a reel reference for instance ! ...
(the code for that is in progress !) ...
See you ...
Cedric
Thomson Group
email: gce++at++syseca.fr
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:51:17 PDT