crazypilot
09-06-2001, 03:41 AM
Hi all.
Thank you very much for your help with the problem I had with SCASM and the
Monitor3D/Tr commands.
After several days of experiments and 'digging' into other APIs that I have
I managed to program what I want but not with the use of any regular position
monitoring command!
I write you here my concusions so that all will benefit.
1. Monitor3D. Stuck in the 360 True heading no matter what. Works ok, but
cannot be rotated or transformed in FS2000.
2. MonitorTr. Exactly the same as Monitor3D. No practical difference.
3. VectorJump. The a option to monitor a polygon on the ground did not work.
It seems to work fine when testing position in relation to vertical planes,
but not with horizontal planes/surfaces.
The p option gives totally wrong results for what I wanted to do (AGNIS).
Also, VectorJump takes as a/c position the Viewing position.
4. AreaSense/BorderSense. Simply ignored by FS2000!
5. CrashBox. Also seems to be ignored, but I still need to confirm this.
So, what's the best way to test the position of the aircraft in respect of the
reference point? What I used, and worked, is a simple IfVarRange3() command!
I just check the Aircraft Delta X, Z and Y with this command and it worked!
It also works fine rotated! The only dissadvandage is that it also considers
the viewing position as the a/c position (like VectorJump) but I can live with
it!
For ease here's the checking :
IfVarRange3( :NotInBox 37E minX maxX 382 minZ maxZ 386 minY maxY )
If ALL 3 variables are NOT within the limits defined the execution will jump
to the label defined. Make sure that the minimum values are LESS than the
maximum otherwise FS will crash.
37E = Aircraft/View Position Delta X from RefPoint
382 = Aircraft/View Position Delta Z from RefPoint
386 = Aircraft/View Position Delta Y from RefPoint
Hope this will help others with problem similar to mine.
Thanks again for your great help
George Dorkofikis
Athens, Hellas
Thank you very much for your help with the problem I had with SCASM and the
Monitor3D/Tr commands.
After several days of experiments and 'digging' into other APIs that I have
I managed to program what I want but not with the use of any regular position
monitoring command!
I write you here my concusions so that all will benefit.
1. Monitor3D. Stuck in the 360 True heading no matter what. Works ok, but
cannot be rotated or transformed in FS2000.
2. MonitorTr. Exactly the same as Monitor3D. No practical difference.
3. VectorJump. The a option to monitor a polygon on the ground did not work.
It seems to work fine when testing position in relation to vertical planes,
but not with horizontal planes/surfaces.
The p option gives totally wrong results for what I wanted to do (AGNIS).
Also, VectorJump takes as a/c position the Viewing position.
4. AreaSense/BorderSense. Simply ignored by FS2000!
5. CrashBox. Also seems to be ignored, but I still need to confirm this.
So, what's the best way to test the position of the aircraft in respect of the
reference point? What I used, and worked, is a simple IfVarRange3() command!
I just check the Aircraft Delta X, Z and Y with this command and it worked!
It also works fine rotated! The only dissadvandage is that it also considers
the viewing position as the a/c position (like VectorJump) but I can live with
it!
For ease here's the checking :
IfVarRange3( :NotInBox 37E minX maxX 382 minZ maxZ 386 minY maxY )
If ALL 3 variables are NOT within the limits defined the execution will jump
to the label defined. Make sure that the minimum values are LESS than the
maximum otherwise FS will crash.
37E = Aircraft/View Position Delta X from RefPoint
382 = Aircraft/View Position Delta Z from RefPoint
386 = Aircraft/View Position Delta Y from RefPoint
Hope this will help others with problem similar to mine.
Thanks again for your great help
George Dorkofikis
Athens, Hellas