http://www.fsdeveloper.com/wiki/api.php?action=feedcontributions&feedformat=atom&user=N4gixFSDeveloper Wiki - User contributions [en-gb]2026-05-20T02:14:06ZUser contributionsMediaWiki 1.41.1http://www.fsdeveloper.com/wiki/index.php?title=XML:_Macros_-_Universal_Timer&diff=9300XML: Macros - Universal Timer2014-08-19T13:09:31Z<p>N4gix: Created page with "{{Infobox-Applicable-FSVersion | P3D = true | FSXA = true | FSX = true | FS2004 = true | FS2002 = false | FS2000 = unknown | FS98 = unknown }} ''' Universal Timer Macros ''' ..."</p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| P3D = true<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = false<br />
| FS2000 = unknown<br />
| FS98 = unknown<br />
}}<br />
''' Universal Timer Macros '''<br />
<br />
Making elapsed time based on gauge update cycle is simple to code and easy to understand.<br />
<br />
Courtesy of Tom Aguilo (taguilo) in post: http://www.fsdeveloper.com/forum/threads/adding-a-timer.431123/#post-681198<br />
<br />
A group of macros, but with an universal score could be :<br />
<br />
<Macro Name="GetElapsed"><br />
(P:Absolute time,@2) (L:@1,@2) - abs<br />
</Macro><br />
<Macro Name="SetElapsed"><br />
(P:Absolute time,@2) (>L:@1,@2)<br />
</Macro><br />
<br />
And then using:<br />
@SetElapsed(name_of_var,unit)<br />
@GetElapsed(name_of_var,unit)<br />
<br />
For example (pseudocode):<br />
<Update><br />
(A:TURB ENG ITT:1, celsius) 907 ><br />
if{ @SetElapsed(MyTimer,minutes) }<br />
...<br />
...<br />
@GetElapsed(MyTimer,minutes) 5 ><br />
if{ do something }<br />
...<br />
</Update><br />
<br />
Both macros can be copied and pasted on every gauge so to have elapsed timers available for the entire code.<br />
<br />
[[category:Aircraft Design]]<br />
[[category:Panel and Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=XtoMDL&diff=9001XtoMDL2014-04-04T15:12:55Z<p>N4gix: /* XtoMDL */</p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = false<br />
| FS2002 = false<br />
| FS2000 = unknown<br />
| FS98 = unknown<br />
}}<br />
== XtoMDL ==<br />
<br />
Original Entry by Bill Leaming<br />
<br />
The new XtoMDL.exe program for FSX and Prepar3D is "command line driven," meaning that there's no fancy-schmanzy GUI to use.<br />
<br />
Did you know that you could create a shortcut on your desktop that would 'proxy' commands to another application?(1) Create a shortcut on your desktop, name it something clever like CompileAircraft and enter the following for the 'target' (fix up c:\temp to be the appropriate paths to the files):<br />
<br />
%windir%\system32\cmd.exe /K c:\temp\xtomdl.exe /DICT:c:\temp\modeldef.XML<br />
<br />
For example, my "Target:" path is -<br />
<br />
%windir%\system32\cmd.exe /K E:"\FSX_SDK\SDK\Environment Kit\Modeling SDK\3DSM7\Plugins\xtomdl.exe" /XANIM /DICT:E:"\FSX_SDK\SDK\Environment Kit\Modeling SDK\bin\modeldef.XML" > buildlog.txt<br />
<br />
My "Start in:" path is -<br />
<br />
"E:\FSX_SDK\SDK\Environment Kit\Modeling SDK\3DSM7\Plugins"<br />
<br />
You can drag and drop onto that shortcut and a new .CMD window will open and stay open so you can see your results. The redirect command "> buildlog.txt" will write a text file with the results of the command, which is useful to review if there are any error messages.<br />
<br />
=== Aircraft models ===<br />
<br />
As an "improvement" to the above(2), move or drag the shortcut to your ..\SendTo folder:<br />
<br />
'''WinXP'''<br />
C:\Documents and Settings\User Name\SendTo<br />
<br />
'''Vista - and - Win7'''<br />
C:\Users\''YourUserName''\AppData\Roaming\Microsoft\Windows\SendTo<br />
<br />
Now, in Explorer right-click '''on the .x file''' and select "CompileAircraft" from the popup menu.<br />
<br />
NOTE: The chief advantage of the "Send To" method is that you can have the .x file(s) anywhere you like to keep them, and the compiled .mdl will appear in that same location.<br />
<br />
=== Scenery models ===<br />
<br />
Creating scenery requires one additional command line switch: /XMLSAMPLE to be added to mix.<br />
<br />
Copy the existing CompileAircraft shortcut you just made, and paste it back in the \SendTo folder. Rename is something clever like - say - CompileScenery, and then edit the Target path and add /XMLSAMPLE to the end, so it looks something like this:<br />
<br />
%windir%\system32\cmd.exe /K E:"\FSX_SDK\SDK\Environment Kit\Modeling SDK\3DSM7\Plugins\xtomdl.exe" /DICT:E:"\FSX_SDK\SDK\Environment Kit\Modeling SDK\bin\modeldef.XML" /XMLSAMPLE > buildlog.txt<br />
<br />
=== Common Problems ===<br />
<br />
1. XTOMDL.EXE generates only MDL-Files with ZERO SIZE -- International windows settings must be set to US (dot used as decimal character)<br />
<br />
2. XTOMDL.EXE shows ERROR: NOT CORRECT DIRECTX OR DIRECTX NOT FOUND -- DIRECTX 9.0c Update from October 2006 is needed<br />
<br />
3. XTOMDL.EXE doesn't start because it needs the MICROSOFT .NET FRAMEWORK 2.0505 -- Download it from Microsoft<br />
<br />
=== References ===<br />
<br />
*1) Thanks to John Kane from ACES (MS Developer) for this tip!<br />
*2) Thanks to Tom Gibson for this tip!<br />
<br />
[[category:Aircraft Design]]<br />
[[category:Scenery Design]]<br />
[[Category:Tools]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=XtoMDL&diff=8885XtoMDL2013-08-18T18:19:46Z<p>N4gix: /* Aircraft models */</p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = false<br />
| FS2002 = false<br />
| FS2000 = unknown<br />
| FS98 = unknown<br />
}}<br />
== XtoMDL ==<br />
<br />
Original Entry by Bill Leaming<br />
<br />
The new XtoMDL.exe program for FSX is "command line driven," meaning that there's no fancy-schmanzy GUI to use.<br />
<br />
Did you know that you could create a shortcut on your desktop that would 'proxy' commands to another application?(1) Create a shortcut on your desktop, name it something clever like CompileAircraft and enter the following for the 'target' (fix up c:\temp to be the appropriate paths to the files):<br />
<br />
%windir%\system32\cmd.exe /K c:\temp\xtomdl.exe /DICT:c:\temp\modeldef.XML<br />
<br />
For example, my "Target:" path is -<br />
<br />
%windir%\system32\cmd.exe /K E:"\FSX_SDK\SDK\Environment Kit\Modeling SDK\3DSM7\Plugins\xtomdl.exe" /XANIM /DICT:E:"\FSX_SDK\SDK\Environment Kit\Modeling SDK\bin\modeldef.XML" > buildlog.txt<br />
<br />
My "Start in:" path is -<br />
<br />
"E:\FSX_SDK\SDK\Environment Kit\Modeling SDK\3DSM7\Plugins"<br />
<br />
You can drag and drop onto that shortcut and a new .CMD window will open and stay open so you can see your results. The redirect command "> buildlog.txt" will write a text file with the results of the command, which is useful to review if there are any error messages.<br />
<br />
=== Aircraft models ===<br />
<br />
As an "improvement" to the above(2), move or drag the shortcut to your ..\SendTo folder:<br />
<br />
'''WinXP'''<br />
C:\Documents and Settings\User Name\SendTo<br />
<br />
'''Vista - and - Win7'''<br />
C:\Users\''YourUserName''\AppData\Roaming\Microsoft\Windows\SendTo<br />
<br />
Now, in Explorer right-click '''on the .x file''' and select "CompileAircraft" from the popup menu.<br />
<br />
NOTE: The chief advantage of the "Send To" method is that you can have the .x file(s) anywhere you like to keep them, and the compiled .mdl will appear in that same location.<br />
<br />
=== Scenery models ===<br />
<br />
Creating scenery requires one additional command line switch: /XMLSAMPLE to be added to mix.<br />
<br />
Copy the existing CompileAircraft shortcut you just made, and paste it back in the \SendTo folder. Rename is something clever like - say - CompileScenery, and then edit the Target path and add /XMLSAMPLE to the end, so it looks something like this:<br />
<br />
%windir%\system32\cmd.exe /K E:"\FSX_SDK\SDK\Environment Kit\Modeling SDK\3DSM7\Plugins\xtomdl.exe" /DICT:E:"\FSX_SDK\SDK\Environment Kit\Modeling SDK\bin\modeldef.XML" /XMLSAMPLE > buildlog.txt<br />
<br />
=== Common Problems ===<br />
<br />
1. XTOMDL.EXE generates only MDL-Files with ZERO SIZE -- International windows settings must be set to US (dot used as decimal character)<br />
<br />
2. XTOMDL.EXE shows ERROR: NOT CORRECT DIRECTX OR DIRECTX NOT FOUND -- DIRECTX 9.0c Update from October 2006 is needed<br />
<br />
3. XTOMDL.EXE doesn't start because it needs the MICROSOFT .NET FRAMEWORK 2.0505 -- Download it from Microsoft<br />
<br />
=== References ===<br />
<br />
*1) Thanks to John Kane from ACES (MS Developer) for this tip!<br />
*2) Thanks to Tom Gibson for this tip!<br />
<br />
[[category:Aircraft Design]]<br />
[[category:Scenery Design]]<br />
[[Category:Tools]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=XtoMDL&diff=8884XtoMDL2013-08-18T18:18:33Z<p>N4gix: /* XtoMDL */</p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = false<br />
| FS2002 = false<br />
| FS2000 = unknown<br />
| FS98 = unknown<br />
}}<br />
== XtoMDL ==<br />
<br />
Original Entry by Bill Leaming<br />
<br />
The new XtoMDL.exe program for FSX is "command line driven," meaning that there's no fancy-schmanzy GUI to use.<br />
<br />
Did you know that you could create a shortcut on your desktop that would 'proxy' commands to another application?(1) Create a shortcut on your desktop, name it something clever like CompileAircraft and enter the following for the 'target' (fix up c:\temp to be the appropriate paths to the files):<br />
<br />
%windir%\system32\cmd.exe /K c:\temp\xtomdl.exe /DICT:c:\temp\modeldef.XML<br />
<br />
For example, my "Target:" path is -<br />
<br />
%windir%\system32\cmd.exe /K E:"\FSX_SDK\SDK\Environment Kit\Modeling SDK\3DSM7\Plugins\xtomdl.exe" /XANIM /DICT:E:"\FSX_SDK\SDK\Environment Kit\Modeling SDK\bin\modeldef.XML" > buildlog.txt<br />
<br />
My "Start in:" path is -<br />
<br />
"E:\FSX_SDK\SDK\Environment Kit\Modeling SDK\3DSM7\Plugins"<br />
<br />
You can drag and drop onto that shortcut and a new .CMD window will open and stay open so you can see your results. The redirect command "> buildlog.txt" will write a text file with the results of the command, which is useful to review if there are any error messages.<br />
<br />
=== Aircraft models ===<br />
<br />
As an "improvement" to the above(2), move or drag the shortcut to your ..\SendTo folder:<br />
<br />
'''WinXP'''<br />
C:\Documents and Settings\User Name\SendTo<br />
<br />
'''Vista - and - Win7'''<br />
C:\Users\''YourUserName''\AppData\Roaming\Microsoft\Windows\SendTo<br />
<br />
Now, in Explorer rightclick on the .x file and select "CompileAircraft" from the popup menu.<br />
<br />
NOTE: The chief advantage of the "Send To" method is that you can have the .x file(s) anywhere you like to keep them, and the compiled .mdl will appear in that same location.<br />
<br />
=== Scenery models ===<br />
<br />
Creating scenery requires one additional command line switch: /XMLSAMPLE to be added to mix.<br />
<br />
Copy the existing CompileAircraft shortcut you just made, and paste it back in the \SendTo folder. Rename is something clever like - say - CompileScenery, and then edit the Target path and add /XMLSAMPLE to the end, so it looks something like this:<br />
<br />
%windir%\system32\cmd.exe /K E:"\FSX_SDK\SDK\Environment Kit\Modeling SDK\3DSM7\Plugins\xtomdl.exe" /DICT:E:"\FSX_SDK\SDK\Environment Kit\Modeling SDK\bin\modeldef.XML" /XMLSAMPLE > buildlog.txt<br />
<br />
=== Common Problems ===<br />
<br />
1. XTOMDL.EXE generates only MDL-Files with ZERO SIZE -- International windows settings must be set to US (dot used as decimal character)<br />
<br />
2. XTOMDL.EXE shows ERROR: NOT CORRECT DIRECTX OR DIRECTX NOT FOUND -- DIRECTX 9.0c Update from October 2006 is needed<br />
<br />
3. XTOMDL.EXE doesn't start because it needs the MICROSOFT .NET FRAMEWORK 2.0505 -- Download it from Microsoft<br />
<br />
=== References ===<br />
<br />
*1) Thanks to John Kane from ACES (MS Developer) for this tip!<br />
*2) Thanks to Tom Gibson for this tip!<br />
<br />
[[category:Aircraft Design]]<br />
[[category:Scenery Design]]<br />
[[Category:Tools]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=XML:_Modulus_Operator&diff=8750XML: Modulus Operator2013-04-08T15:52:41Z<p>N4gix: /* XML: Modulus Operator */</p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = false<br />
| FS2000 = false<br />
| FS98 = false<br />
}}<br />
==XML: Modulus Operator==<br />
<br />
'''QUESTION:''' ''What does the expression "123 2 %" mean?''<br />
<br />
The modulus, or remainder, operator divides number1 by number2 and returns only the remainder as result. <br />
<br />
The sign of result is the same as the sign of number1. <br />
<br />
The value of result is between 0 and the absolute value of number2.<br />
<br />
<br />
<br />
In XML syntax, the general statement is:<br />
<br />
'''''number1 number2 %'''''<br />
<br />
<br />
For example, in the following expression, A (which is result) equals 5.6.<br />
<br />
A = 19 6.7 %<br />
<br />
This is equivalent to:<br />
<br />
19 / 6.7 = 2.8358208<br />
<br />
We throw away the fraction leaving 2 as the result<br />
<br />
Now we have:<br />
<br />
A = 19 - (6.7 * 2)<br />
<br />
Therefore A = 5.6<br />
<br />
<br />
<br />
The above is an example where the result is certainly not obvious! <br />
<br />
The "%" (or "mod") operator in computer languages is simply the remainder. <br />
<br />
For example,<br />
<br />
17 3 % = 2<br />
<br />
because<br />
<br />
17 / 3 = 5 rem 2<br />
<br />
which in turn means<br />
<br />
17 = 3 * 5 + 2<br />
<br />
<br />
<br />
There are some tricky issues when negative numbers are used, <br />
but that shouldn't ordinarily be necessary.<br />
<br />
<br />
<br />
In math (number theory), the term is used a little differently. <br />
<br />
The "modulus" is actually not the remainder, <br />
<br />
but the number you are dividing by; <br />
<br />
and "mod" is not an operator, <br />
<br />
but a label telling "in what sense two quantities are considered congruent, or equal." <br />
<br />
<br />
<br />
For example, we would say<br />
<br />
17 = 11 (mod 3)<br />
<br />
(read as "17 is congruent to 11, modulo 3"), meaning that 17 and 11 <br />
both leave the SAME remainder when divided by 3. You probably won't <br />
see this usage if you are only reading about programming, but it's <br />
worth being aware of if you look deeper into the math behind it.<br />
<br />
The expression a = b (% n) means that n is a divisor of a - b. This<br />
sentence is read, "a is congruent to b modulo n." It is something<br />
like a remainder, because if you subtract a remainder from the<br />
dividend, the divisor will go into the result evenly.<br />
<br />
Examples: 100 = 86 (% 7), because 100 - 86 = 14 has 7 as a divisor.<br />
On the other hand, if you divide 100 by 7, the quotient is 14 and<br />
remainder is 2, and 100 = 2 (% 7), too.<br />
<br />
Now, back to your original question, what would 123 2 % be?<br />
<br />
A = 123 2 %<br />
<br />
123 / 2 = 61.5, therefore:<br />
<br />
A = 123 - (61 * 2)<br />
<br />
A = 1<br />
<br />
'''NOTA BENE:'''<br />
It was pointed out by "mgh" that the "XML modulus function" '''x y %''' in C/C++ is mathematically equivalent to:<br />
<br />
(fabs(x)/x)*(fabs(x)-int(fabs(x)/fabs(y))*fabs(y))<br />
Of course, since C/C++ has a defined function, actual usage would be:<br />
fmod(x,y)<br />
<br />
#include <math.h><br />
double fmod( double x, double y)<br />
<br />
[[Category:Aircraft Design]]<br />
[[Category:Panel and Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=XML:_Modulus_Operator&diff=8749XML: Modulus Operator2013-04-08T15:44:18Z<p>N4gix: /* XML: Modulus Operator */</p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = false<br />
| FS2000 = false<br />
| FS98 = false<br />
}}<br />
==XML: Modulus Operator==<br />
<br />
'''QUESTION:''' ''What does the expression "123 2 %" mean?''<br />
<br />
The modulus, or remainder, operator divides number1 by number2 and returns only the remainder as result. <br />
<br />
The sign of result is the same as the sign of number1. <br />
<br />
The value of result is between 0 and the absolute value of number2.<br />
<br />
<br />
<br />
In XML syntax, the general statement is:<br />
<br />
'''''number1 number2 %'''''<br />
<br />
<br />
For example, in the following expression, A (which is result) equals 5.6.<br />
<br />
A = 19 6.7 %<br />
<br />
This is equivalent to:<br />
<br />
19 / 6.7 = 2.8358208<br />
<br />
We throw away the fraction leaving 2 as the result<br />
<br />
Now we have:<br />
<br />
A = 19 - (6.7 * 2)<br />
<br />
Therefore A = 5.6<br />
<br />
<br />
<br />
The above is an example where the result is certainly not obvious! <br />
<br />
The "%" (or "mod") operator in computer languages is simply the remainder. <br />
<br />
For example,<br />
<br />
17 3 % = 2<br />
<br />
because<br />
<br />
17 / 3 = 5 rem 2<br />
<br />
which in turn means<br />
<br />
17 = 3 * 5 + 2<br />
<br />
<br />
<br />
There are some tricky issues when negative numbers are used, <br />
but that shouldn't ordinarily be necessary.<br />
<br />
<br />
<br />
In math (number theory), the term is used a little differently. <br />
<br />
The "modulus" is actually not the remainder, <br />
<br />
but the number you are dividing by; <br />
<br />
and "mod" is not an operator, <br />
<br />
but a label telling "in what sense two quantities are considered congruent, or equal." <br />
<br />
<br />
<br />
For example, we would say<br />
<br />
17 = 11 (mod 3)<br />
<br />
(read as "17 is congruent to 11, modulo 3"), meaning that 17 and 11 <br />
both leave the SAME remainder when divided by 3. You probably won't <br />
see this usage if you are only reading about programming, but it's <br />
worth being aware of if you look deeper into the math behind it.<br />
<br />
The expression a = b (% n) means that n is a divisor of a - b. This<br />
sentence is read, "a is congruent to b modulo n." It is something<br />
like a remainder, because if you subtract a remainder from the<br />
dividend, the divisor will go into the result evenly.<br />
<br />
Examples: 100 = 86 (% 7), because 100 - 86 = 14 has 7 as a divisor.<br />
On the other hand, if you divide 100 by 7, the quotient is 14 and<br />
remainder is 2, and 100 = 2 (% 7), too.<br />
<br />
Now, back to your original question, what would 123 2 % be?<br />
<br />
A = 123 2 %<br />
<br />
123 / 2 = 61.5, therefore:<br />
<br />
A = 123 - (61 * 2)<br />
<br />
A = 1<br />
<br />
'''NOTA BENE:'''<br />
It was pointed out by "mgh" that the "XML modulus function" '''x y %''' in C/C++ is equivalent to:<br />
<br />
(fabs(x)/x)*(fabs(x)-int(fabs(x)/fabs(y))*fabs(y))<br />
<br />
[[Category:Aircraft Design]]<br />
[[Category:Panel and Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=XML:_Set_ADF_Frequency&diff=8747XML: Set ADF Frequency2013-03-26T16:09:44Z<p>N4gix: </p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = false<br />
| FS2000 = unknown<br />
| FS98 = unknown<br />
}}<br />
<br />
==XML: Set ADF Frequency==<br />
We need to convert the desired ADF Frequency (KHz) to BCD format. This simple @Macro will do the job painlessly for us.<br />
<br />
Note the use of lower case L in '''l0''' and '''l2''', this is [[not]] a number 1:<br />
<br />
e.g., s2 '''[[l]]'''0 10 / flr 10 % 16 * '''[[l]]'''2 +<br />
<br />
<Macro Name="SetADF"><br />
(* UPDATE ADF FREQUENCY *)<br />
@1 10000 * s0 10 %<br />
s2 l0 10 / flr 10 % 16 * l2 +<br />
s2 l0 100 / flr 10 % 256 * l2 +<br />
s2 l0 1000 / flr 10 % 4096 * l2 +<br />
s2 l0 10000 / flr 10 % 65536 * l2 +<br />
s2 l0 100000 / flr 10 % 1048576 * l2 +<br />
s2 l0 1000000 / flr 10 % 16777216 * l2 +<br />
s2 l0 10000000 / flr 10 % 268435456 * l2 +<br />
s2 (>K:ADF_COMPLETE_SET)<br />
</Macro><br />
<br />
Usage: <br />
@SetADF((L:ADF1 Frequency,Khz))<br />
<br />
[[category:Aircraft Design]]<br />
[[category:Panel and Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=XML:_Decimal_To_BCD_Macro_-_Set_Nav/Com_Freq&diff=8746XML: Decimal To BCD Macro - Set Nav/Com Freq2013-03-26T16:09:13Z<p>N4gix: </p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = false<br />
| FS2000 = unknown<br />
| FS98 = unknown<br />
}}<br />
<br />
==XML:Decimal to BCD Macro==<br />
<br />
A very simple but useful @macro to convert any decimal frequency to BCD format to allow direct SETting of COM and NAV frequencies in FS:<br />
<br />
<Macro Name="Dec2Bcd"><br />
@1 100.001 * 10000 % int<br />
d 10 % r 10 / int<br />
d 10 % r 10 / int<br />
d 10 % r 10 / int<br />
16 * +<br />
16 * +<br />
16 * +<br />
</Macro><br />
<br />
Usage is then as simple as passing the decimal frequency to the @macro the issuing the appropriate _SET key event:<br />
<br />
<Click><br />
@Dec2Bcd(112.30) (>K:NAV2_RADIO_SET)<br />
</Click><br />
<br />
You could also use a custom L:var to pass a "tuned" frequency:<br />
<br />
<Click><br />
@Dec2Bcd((L:Nav2Freq,enum)) (>K:NAV2_RADIO_SET)<br />
</Click><br />
<br />
<br />
[[Category:Aircraft Design]]<br />
[[Category:Panel and Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=XtoMDL&diff=8745XtoMDL2013-03-12T19:30:52Z<p>N4gix: /* Aircraft models */</p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = false<br />
| FS2002 = false<br />
| FS2000 = unknown<br />
| FS98 = unknown<br />
}}<br />
== XtoMDL ==<br />
<br />
Original Entry by Bill Leaming<br />
<br />
The new XtoMDL.exe program for FSX is "command line driven," meaning that there's no fancy-schmanzy GUI to use.<br />
<br />
Did you know that you could create a shortcut on your desktop that would 'proxy' commands to another application?(1) Create a shortcut on your desktop, name it something clever like CompileAircraft and enter the following for the 'target' (fix up c:\temp to be the appropriate paths to the files):<br />
<br />
%windir%\system32\cmd.exe /K c:\temp\xtomdl.exe /DICT:c:\temp\modeldef.XML<br />
<br />
For example, my "Target:" path is -<br />
<br />
%windir%\system32\cmd.exe /K E:"\FSX_SDK\SDK\Environment Kit\Modeling SDK\3DSM7\Plugins\xtomdl.exe" /XANIM /DICT:E:"\FSX_SDK\SDK\Environment Kit\Modeling SDK\bin\modeldef.XML" > buildlog.txt<br />
<br />
My "Start in:" path is -<br />
<br />
"E:\FSX_SDK\SDK\Environment Kit\Modeling SDK\3DSM7\Plugins"<br />
<br />
You can drag and drop onto that shortcut and a new .CMD window will open and stay open so you can see your results. The redirect command "> buildlog.txt" will write a text file with the results of the command, which is useful to review if there are any error messages.<br />
<br />
=== Aircraft models ===<br />
<br />
As an "improvement" to the above(2), move or drag the shortcut to your ..\SendTo folder:<br />
<br />
'''WinXP'''<br />
C:\Documents and Settings\User Name\SendTo<br />
<br />
'''Vista - and - Win7'''<br />
C:\Users\''YourUserName''\AppData\Roaming\Microsoft\Windows\SendTo<br />
<br />
Now, in Explorer rightclick on the .x file and select "CompileAircraft" from the popup menu.<br />
<br />
NOTE: The chief advantage of the "Send To" method is that you can have the .x file(s) anywhere you like to keep them, and the compiled .mdl will appear in that same location.<br />
<br />
=== Scenery models ===<br />
<br />
Creating scenery requires one additional command line switch: /XMLSAMPLE to be added to mix.<br />
<br />
Copy the existing CompileAircraft shortcut you just made, and paste it back in the \SendTo folder. Rename is something clever like - say - CompileScenery, and then edit the Target path and add /XMLSAMPLE to the end, so it looks something like this:<br />
<br />
%windir%\system32\cmd.exe /K E:"\FSX_SDK\SDK\Environment Kit\Modeling SDK\3DSM7\Plugins\xtomdl.exe" /DICT:E:"\FSX_SDK\SDK\Environment Kit\Modeling SDK\bin\modeldef.XML" /XMLSAMPLE > buildlog.txt<br />
<br />
=== Common Problems ===<br />
<br />
1. XTOMDL.EXE generates only MDL-Files with ZERO SIZE -- International windows settings must be set to US (dot used as decimal character)<br />
<br />
2. XTOMDL.EXE shows ERROR: NOT CORRECT DIRECTX OR DIRECTX NOT FOUND -- DIRECTX 9.0c Update from October 2006 is needed<br />
<br />
3. XTOMDL.EXE doesn't start because it needs the MICROSOFT .NET FRAMEWORK 2.0505 -- Download it from Microsoft<br />
<br />
=== References ===<br />
<br />
*1) Thanks to John Kane from ACES (MS Developer) for this tip!<br />
*2) Thanks to Tom Gibson for this tip!<br />
<br />
[[category:Aircraft Design]]<br />
[[category:Scenery Design]]<br />
[[Category:Tools]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=XtoMDL&diff=8744XtoMDL2013-03-12T19:23:19Z<p>N4gix: /* Aircraft models */</p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = false<br />
| FS2002 = false<br />
| FS2000 = unknown<br />
| FS98 = unknown<br />
}}<br />
== XtoMDL ==<br />
<br />
Original Entry by Bill Leaming<br />
<br />
The new XtoMDL.exe program for FSX is "command line driven," meaning that there's no fancy-schmanzy GUI to use.<br />
<br />
Did you know that you could create a shortcut on your desktop that would 'proxy' commands to another application?(1) Create a shortcut on your desktop, name it something clever like CompileAircraft and enter the following for the 'target' (fix up c:\temp to be the appropriate paths to the files):<br />
<br />
%windir%\system32\cmd.exe /K c:\temp\xtomdl.exe /DICT:c:\temp\modeldef.XML<br />
<br />
For example, my "Target:" path is -<br />
<br />
%windir%\system32\cmd.exe /K E:"\FSX_SDK\SDK\Environment Kit\Modeling SDK\3DSM7\Plugins\xtomdl.exe" /XANIM /DICT:E:"\FSX_SDK\SDK\Environment Kit\Modeling SDK\bin\modeldef.XML" > buildlog.txt<br />
<br />
My "Start in:" path is -<br />
<br />
"E:\FSX_SDK\SDK\Environment Kit\Modeling SDK\3DSM7\Plugins"<br />
<br />
You can drag and drop onto that shortcut and a new .CMD window will open and stay open so you can see your results. The redirect command "> buildlog.txt" will write a text file with the results of the command, which is useful to review if there are any error messages.<br />
<br />
=== Aircraft models ===<br />
<br />
As an "improvement" to the above(2), rename the shortcut something like "CompileAircraft" then move the shortcut to your \SendTo folder:<br />
<br />
'''WinXP'''<br />
C:\Documents and Settings\User Name\SendTo<br />
<br />
'''Vista - and - Win7'''<br />
C:\Users\''YourUserName''\AppData\Roaming\Microsoft\Windows\SendTo<br />
<br />
Now, in Explorer rightclick on the .x file and select "CompileAircraft" from the popup menu.<br />
<br />
NOTE: The chief advantage of the "Send To" method is that you can have the .x file(s) anywhere you like to keep them, and the compiled .mdl will appear in that same location.<br />
<br />
=== Scenery models ===<br />
<br />
Creating scenery requires one additional command line switch: /XMLSAMPLE to be added to mix.<br />
<br />
Copy the existing CompileAircraft shortcut you just made, and paste it back in the \SendTo folder. Rename is something clever like - say - CompileScenery, and then edit the Target path and add /XMLSAMPLE to the end, so it looks something like this:<br />
<br />
%windir%\system32\cmd.exe /K E:"\FSX_SDK\SDK\Environment Kit\Modeling SDK\3DSM7\Plugins\xtomdl.exe" /DICT:E:"\FSX_SDK\SDK\Environment Kit\Modeling SDK\bin\modeldef.XML" /XMLSAMPLE > buildlog.txt<br />
<br />
=== Common Problems ===<br />
<br />
1. XTOMDL.EXE generates only MDL-Files with ZERO SIZE -- International windows settings must be set to US (dot used as decimal character)<br />
<br />
2. XTOMDL.EXE shows ERROR: NOT CORRECT DIRECTX OR DIRECTX NOT FOUND -- DIRECTX 9.0c Update from October 2006 is needed<br />
<br />
3. XTOMDL.EXE doesn't start because it needs the MICROSOFT .NET FRAMEWORK 2.0505 -- Download it from Microsoft<br />
<br />
=== References ===<br />
<br />
*1) Thanks to John Kane from ACES (MS Developer) for this tip!<br />
*2) Thanks to Tom Gibson for this tip!<br />
<br />
[[category:Aircraft Design]]<br />
[[category:Scenery Design]]<br />
[[Category:Tools]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=XtoMDL&diff=8743XtoMDL2013-03-12T19:22:49Z<p>N4gix: /* Aircraft models */</p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = false<br />
| FS2002 = false<br />
| FS2000 = unknown<br />
| FS98 = unknown<br />
}}<br />
== XtoMDL ==<br />
<br />
Original Entry by Bill Leaming<br />
<br />
The new XtoMDL.exe program for FSX is "command line driven," meaning that there's no fancy-schmanzy GUI to use.<br />
<br />
Did you know that you could create a shortcut on your desktop that would 'proxy' commands to another application?(1) Create a shortcut on your desktop, name it something clever like CompileAircraft and enter the following for the 'target' (fix up c:\temp to be the appropriate paths to the files):<br />
<br />
%windir%\system32\cmd.exe /K c:\temp\xtomdl.exe /DICT:c:\temp\modeldef.XML<br />
<br />
For example, my "Target:" path is -<br />
<br />
%windir%\system32\cmd.exe /K E:"\FSX_SDK\SDK\Environment Kit\Modeling SDK\3DSM7\Plugins\xtomdl.exe" /XANIM /DICT:E:"\FSX_SDK\SDK\Environment Kit\Modeling SDK\bin\modeldef.XML" > buildlog.txt<br />
<br />
My "Start in:" path is -<br />
<br />
"E:\FSX_SDK\SDK\Environment Kit\Modeling SDK\3DSM7\Plugins"<br />
<br />
You can drag and drop onto that shortcut and a new .CMD window will open and stay open so you can see your results. The redirect command "> buildlog.txt" will write a text file with the results of the command, which is useful to review if there are any error messages.<br />
<br />
=== Aircraft models ===<br />
<br />
As an "improvement" to the above(2), rename the shortcut something like "CompileAircraft" then move the shortcut to your \SendTo folder:<br />
<br />
'''WinXP -'''<br />
C:\Documents and Settings\User Name\SendTo<br />
<br />
'''Vista - and Win7'''<br />
C:\Users\''YourUserName''\AppData\Roaming\Microsoft\Windows\SendTo<br />
<br />
Now, in Explorer rightclick on the .x file and select "CompileAircraft" from the popup menu.<br />
<br />
NOTE: The chief advantage of the "Send To" method is that you can have the .x file(s) anywhere you like to keep them, and the compiled .mdl will appear in that same location.<br />
<br />
=== Scenery models ===<br />
<br />
Creating scenery requires one additional command line switch: /XMLSAMPLE to be added to mix.<br />
<br />
Copy the existing CompileAircraft shortcut you just made, and paste it back in the \SendTo folder. Rename is something clever like - say - CompileScenery, and then edit the Target path and add /XMLSAMPLE to the end, so it looks something like this:<br />
<br />
%windir%\system32\cmd.exe /K E:"\FSX_SDK\SDK\Environment Kit\Modeling SDK\3DSM7\Plugins\xtomdl.exe" /DICT:E:"\FSX_SDK\SDK\Environment Kit\Modeling SDK\bin\modeldef.XML" /XMLSAMPLE > buildlog.txt<br />
<br />
=== Common Problems ===<br />
<br />
1. XTOMDL.EXE generates only MDL-Files with ZERO SIZE -- International windows settings must be set to US (dot used as decimal character)<br />
<br />
2. XTOMDL.EXE shows ERROR: NOT CORRECT DIRECTX OR DIRECTX NOT FOUND -- DIRECTX 9.0c Update from October 2006 is needed<br />
<br />
3. XTOMDL.EXE doesn't start because it needs the MICROSOFT .NET FRAMEWORK 2.0505 -- Download it from Microsoft<br />
<br />
=== References ===<br />
<br />
*1) Thanks to John Kane from ACES (MS Developer) for this tip!<br />
*2) Thanks to Tom Gibson for this tip!<br />
<br />
[[category:Aircraft Design]]<br />
[[category:Scenery Design]]<br />
[[Category:Tools]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=XtoMDL&diff=8742XtoMDL2013-03-12T19:21:56Z<p>N4gix: /* Aircraft models */</p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = false<br />
| FS2002 = false<br />
| FS2000 = unknown<br />
| FS98 = unknown<br />
}}<br />
== XtoMDL ==<br />
<br />
Original Entry by Bill Leaming<br />
<br />
The new XtoMDL.exe program for FSX is "command line driven," meaning that there's no fancy-schmanzy GUI to use.<br />
<br />
Did you know that you could create a shortcut on your desktop that would 'proxy' commands to another application?(1) Create a shortcut on your desktop, name it something clever like CompileAircraft and enter the following for the 'target' (fix up c:\temp to be the appropriate paths to the files):<br />
<br />
%windir%\system32\cmd.exe /K c:\temp\xtomdl.exe /DICT:c:\temp\modeldef.XML<br />
<br />
For example, my "Target:" path is -<br />
<br />
%windir%\system32\cmd.exe /K E:"\FSX_SDK\SDK\Environment Kit\Modeling SDK\3DSM7\Plugins\xtomdl.exe" /XANIM /DICT:E:"\FSX_SDK\SDK\Environment Kit\Modeling SDK\bin\modeldef.XML" > buildlog.txt<br />
<br />
My "Start in:" path is -<br />
<br />
"E:\FSX_SDK\SDK\Environment Kit\Modeling SDK\3DSM7\Plugins"<br />
<br />
You can drag and drop onto that shortcut and a new .CMD window will open and stay open so you can see your results. The redirect command "> buildlog.txt" will write a text file with the results of the command, which is useful to review if there are any error messages.<br />
<br />
=== Aircraft models ===<br />
<br />
As an "improvement" to the above(2), rename the shortcut something like "CompileAircraft" then move the shortcut to your \SendTo folder:<br />
<br />
'''WinXP -'''<br />
C:\Documents and Settings\User Name\SendTo<br />
<br />
'''Vista -'''<br />
C:\Users\''YourUserName''\AppData\Roaming\Microsoft\Windows\SendTo<br />
<br />
Now, in Explorer rightclick on the .x file and select "CompileAircraft" from the popup menu.<br />
<br />
NOTE: The chief advantage of the "Send To" method is that you can have the .x file(s) anywhere you like to keep them, and the compiled .mdl will appear in that same location.<br />
<br />
=== Scenery models ===<br />
<br />
Creating scenery requires one additional command line switch: /XMLSAMPLE to be added to mix.<br />
<br />
Copy the existing CompileAircraft shortcut you just made, and paste it back in the \SendTo folder. Rename is something clever like - say - CompileScenery, and then edit the Target path and add /XMLSAMPLE to the end, so it looks something like this:<br />
<br />
%windir%\system32\cmd.exe /K E:"\FSX_SDK\SDK\Environment Kit\Modeling SDK\3DSM7\Plugins\xtomdl.exe" /DICT:E:"\FSX_SDK\SDK\Environment Kit\Modeling SDK\bin\modeldef.XML" /XMLSAMPLE > buildlog.txt<br />
<br />
=== Common Problems ===<br />
<br />
1. XTOMDL.EXE generates only MDL-Files with ZERO SIZE -- International windows settings must be set to US (dot used as decimal character)<br />
<br />
2. XTOMDL.EXE shows ERROR: NOT CORRECT DIRECTX OR DIRECTX NOT FOUND -- DIRECTX 9.0c Update from October 2006 is needed<br />
<br />
3. XTOMDL.EXE doesn't start because it needs the MICROSOFT .NET FRAMEWORK 2.0505 -- Download it from Microsoft<br />
<br />
=== References ===<br />
<br />
*1) Thanks to John Kane from ACES (MS Developer) for this tip!<br />
*2) Thanks to Tom Gibson for this tip!<br />
<br />
[[category:Aircraft Design]]<br />
[[category:Scenery Design]]<br />
[[Category:Tools]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=OOM_Error&diff=8729OOM Error2013-02-26T18:13:57Z<p>N4gix: /* FINE TUNING VAS */</p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = false<br />
| FS2002 = false<br />
| FS2000 = unknown<br />
| FS98 = unknown<br />
}}<br />
<br />
<br />
== Overview ==<br />
<br />
''Virtual Memory'' is a technique of simulating additional memory for an application to use. <br />
<br />
''Application programs'' and many ''system processes'' always reference memory using ''virtual memory addresses'' which are automatically translated to ''real (RAM) addresses'' by the hardware. <br />
<br />
Virtual memory divides the virtual address space of an application program into pages; a page is a block of contiguous virtual memory addresses.<br />
<br />
The virtual memory management component of the operating system maintains the translation tables used by the hardware to provide the mapping of virtual addresses into real addresses. <br />
<br />
==OOM Error==<br />
<br />
All 32 bit operating systems (WinXP and Vista32) have 4 GBs of ''[http://en.wikipedia.org/wiki/Virtual_address_space Virtual Address Space]'', (VAS), to work with, as that is the maximum number that can be expressed with only 32bits. <br />
<br />
The VAS table is the same size whether your system physically has 512MB RAM or 4GB of RAM...<br />
<br />
By default, 2GB of VAS addresses are reserved for the operating system, with the remaining 2GB of VAS reserved for application programs. <br />
Note that every application running maintains it's own set of VAS addresses, and that the operating system will take care of shuffling both the application's address table and the data contents back and forth from the Virtual Memory on the hard drive as necessary.<br />
<br />
Obviously, everytime a running application needs to access it's VAS table and data, the OS needs to swap things around. The more application programs running at once, the more things get slowed down.<br />
<br />
When you add the /3GB switch, what you are doing is increasing the total available Virtual Address Space (VAS) for FSX to use, which in turn reduces the available VAS for the operating system.<br />
<br />
It's a case of "robbing Peter to pay Paul..."<br />
<br />
What the 3GB "tweak" accomplishes in both WinXP and Vista32 is that you essentially increase the size of the VAS table available to ALL running programs for which the "flag" for "LARGEADDRESSAWARE" has been set. The FSX.exe for both RTM, SP1 must be manually made "LARGEADDRESSAWARE", where the SP2 FSX.exe has already been marked as "LARGEADDRESSAWARE."<br />
<br />
In all cases though, the onus is on the user to tell their operating system to increase the VAS for all "enabled" application programs. The procedure for WinXP and Vista are different, but the results are identical.<br />
<br />
This next bit of information is critical to coming to a more full understanding of what is causing the "OOM Error" to occur:<br />
<br />
'''[[FSX will only use "contiguous 1MB blocks of VAS]]."'''<br />
<br />
Anytime FSX cannot find a 1MB block of VAS in which to "load stuff," it will summarily crash to desktop...<br />
<br />
Incidentally, it's also important to note that the amount of memory on a video card can actually hinder performance rather than help...<br />
<br />
...that is because the video card's memory addresses are mapped to the operating system's slice of VAS, and therefore reduces the total number of Virtual Addresses available the operating system...<br />
<br />
For example, a video card with 512MB of onboard RAM will consume 512MB of the available operating system's slice of VAS, so robbing too much from the OS's slice can cause a lot of problems. As always, this is a balancing act...<br />
<br />
<br />
== FINE TUNING VAS ==<br />
<br />
As I stated previously, since it's a case of "robbing Peter to pay Paul," it may be best to allocate LESS than a full GB of VAS to applications, which is why Phil Taylor recommends using /2560 rather than the full /3072 MB.<br />
<br />
'''NOTE: The following applies only to WinXP users:<br />
--------------------------------------------------------'''<br />
In your boot.ini file, if you have added the /3GB switch already:<br />
<br />
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect /3GB<br />
<br />
To "fine tune" the actual amount of VAS allocated, you need only add another switch to the end of the entire entry:<br />
<br />
/Userva=2560<br />
<br />
or whatever size you wish, keeping in mind the 1MB contiguous limit of FSX. In such a case, using any number that isn't a multiple of 512MB simply doesn't make much sense...<br />
<br />
'''NOTE: The following applies only to Vista32 users:<br />
--------------------------------------------------------'''<br />
BCDEDIT /set increaseuserva 2560<br />
BCDEDIT /set increaseuserva 3072<br />
<br />
'''<br />
<br />
== WARNING! ==<br />
'''<br />
<br />
It is possible to starve the operating system's slice of VAS to the point that your system will no longer boot!<br />
<br />
If this happens, you must reboot the computer into "Safe Mode" (which bypasses the /3GB switch, and then edit your boot.ini (WinXP) or use bcdecit (Vista) to reduce the size of the application slice of the VAS.<br />
<br />
[[category:General]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=XML:_RNOR_Bug!&diff=8723XML: RNOR Bug!2013-02-15T15:52:12Z<p>N4gix: </p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = true<br />
| XP10 = false <br />
| XP9 = false <br />
}}<br />
<br />
<br />
== XML: RNOR Bug! ==<br />
<br />
There is a bug in the rnor function that can be used in XML scripts (in both gauges and modeldef.xml).<br />
<br />
The expression 4.0 rnor should be 4.0, not 0.86 as FS returns. The problem is that the parsing engine is doing a mod by pi instead of 2 pi.<br />
<br />
What to do about this? I would suggest taking a number and converting to degrees (using the rddg function), then using dnor (to normalize the number of degrees to a range between 0 and 360). and then convert back to radians using dgrd. Take care to mind your d's and r's and g's, though!<br />
<br />
[[Category:Aircraft Design]]<br />
[[Category:Panel and Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=Taxi_light&diff=8696Taxi light2013-02-03T17:26:05Z<p>N4gix: </p>
<hr />
<div>[[Image:VTBStaxilightFinal.jpg]]<br />
<br />
<br />
There are variety of the methods of making Taxi Edge Light:<br />
<br />
1.Make individual light, attached with effect and place the instance many time by xml. This is good for small airport with hundred of taxi lights but not thousand in big international airport since many xml placement will cause fps drop. The difficult of this is you have to place them many times and it is time consuming method. You can have difficulties placing along the straight line to make it perfectly strait. Or even more difficult, perfectly curve along the turn<br />
<br />
2.Make the whole taxi lights in gmax and export them in one file. This will keep XML minimal just only one time placement. Then use maxscript from Nick Whittome [http://www.fsdeveloper.com/wiki/index.php?title=Apron_lighting_using_effects_and_GMax] . But the effect can cause frame rate drop dramatically. I did that and I found 50% drop[http://www.fsdeveloper.com/forum/showthread.php?t=424631].<br />
<br />
3.Make the same way as the second method but eliminate the use of effect. This will be the best from frame rate but less visibility range. You can see your light only withing a few hundred meters.[http://fsdeveloper.com/forum/showthread.php?t=259310] Please read #12.<br />
<br />
I think I found a sweet spot between visibility range that you get from effect and the ease of placement.<br />
Here is my tutorial about taxi lights.<br />
Taxi Edge Light Tutorial [http://www.fsdeveloper.com/forum/attachment.php?attachmentid=13936&d=1359701230]<br />
<br />
[[Category:Airport Design]]<br />
[[category:Scenery Design]]<br />
[[category:Effects]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=Taxi_light&diff=8695Taxi light2013-02-03T17:22:39Z<p>N4gix: </p>
<hr />
<div>[[Image:VTBStaxilightFinal.jpg]]<br />
<br />
<br />
There are variety of the methods of making Taxi Edge Light:<br />
<br />
1.Make individual light, attached with effect and place the instance many time by xml. This is good for small airport with hundred of taxi lights but not thousand in big international airport since many xml placement will cause fps drop. The difficult of this is you have to place them many times and it is time consuming method. You can have difficulties placing along the straight line to make it perfectly strait. Or even more difficult, perfectly curve along the turn<br />
<br />
2.Make the whole taxi lights in gmax and export them in one file. This will keep XML minimal just only one time placement. Then use maxscript from Nick Whittome [http://www.fsdeveloper.com/wiki/index.php?title=Apron_lighting_using_effects_and_GMax] . But the effect can cause frame rate drop dramatically. I did that and I found 50% drop[http://www.fsdeveloper.com/forum/showthread.php?t=424631].<br />
<br />
3.Make the same way as the second method but eliminate the use of effect. This will be the best from frame rate but less visibility range. You can see your light only withing a few hundred meters.[http://fsdeveloper.com/forum/showthread.php?t=259310] Please read #12.<br />
<br />
I think I found a sweet spot between visibility range that you get from effect and the ease of placement.<br />
Here is my tutorial about taxi lights.<br />
Taxi Edge Light Tutorial [http://www.fsdeveloper.com/forum/attachment.php?attachmentid=13936&d=1359701230]<br />
<br />
[[Category:Airport Design]]<br />
[[category:Scenery Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=XML:_Decimal_To_BCD_Macro_-_Set_Nav/Com_Freq&diff=8597XML: Decimal To BCD Macro - Set Nav/Com Freq2012-11-17T21:44:34Z<p>N4gix: </p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = false<br />
| FS2000 = unknown<br />
| FS98 = unknown<br />
}}<br />
<br />
==XML:Decimal to BCD Macro==<br />
<br />
A very simple but useful @macro to convert any decimal frequency to BCD format to allow direct SETting of COM and NAV frequencies in FS:<br />
<br />
<Macro Name="Dec2Bcd"><br />
100.001 * 10000 % int<br />
d 10 % r 10 / int<br />
d 10 % r 10 / int<br />
d 10 % r 10 / int<br />
16 * +<br />
16 * +<br />
16 * +<br />
</Macro><br />
<br />
Usage is then as simple as passing the decimal frequency to the @macro the issuing the appropriate _SET key event:<br />
<br />
<Click><br />
@Dec2Bcd(112.30) (>K:NAV2_RADIO_SET)<br />
</Click><br />
<br />
You could also use a custom L:var to pass a "tuned" frequency:<br />
<br />
<Click><br />
@Dec2Bcd((L:Nav2Freq,enum)) (>K:NAV2_RADIO_SET)<br />
</Click><br />
<br />
<br />
[[Category:Aircraft Design]]<br />
[[Category:Panel and Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=XML:_Decimal_To_BCD_Macro_-_Set_Nav/Com_Freq&diff=8596XML: Decimal To BCD Macro - Set Nav/Com Freq2012-11-17T15:11:52Z<p>N4gix: </p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = false<br />
| FS2000 = unknown<br />
| FS98 = unknown<br />
}}<br />
<br />
==XML:Decimal to BCD Macro==<br />
<br />
A very simple but useful @macro to convert any decimal frequency to BCD format to allow direct SETting of COM and NAV frequencies in FS:<br />
<br />
<Macro Name="Dec2Bcd"><br />
100 * 10000 % int<br />
d 10 % r 10 / int<br />
d 10 % r 10 / int<br />
d 10 % r 10 / int<br />
16 * +<br />
16 * +<br />
16 * +<br />
</Macro><br />
<br />
Usage is then as simple as passing the decimal frequency to the @macro the issuing the appropriate _SET key event:<br />
<br />
<Click><br />
@Dec2Bcd(112.30) (>K:NAV2_RADIO_SET)<br />
</Click><br />
<br />
You could also use a custom L:var to pass a "tuned" frequency:<br />
<br />
<Click><br />
@Dec2Bcd((L:Nav2Freq,enum)) (>K:NAV2_RADIO_SET)<br />
</Click><br />
<br />
<br />
[[Category:Aircraft Design]]<br />
[[Category:Panel and Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=Flight_Dynamics_Development:_FDE&diff=8554Flight Dynamics Development: FDE2012-09-21T20:40:19Z<p>N4gix: New page: {{Infobox-Applicable-FSVersion | FSXA = true | FSX = true | FS2004 = true | FS2002 = false | XP10 = false | XP9 = false }} == Flight Dymanics Development: FDE == This is an empty topi...</p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = false<br />
| XP10 = false <br />
| XP9 = false <br />
}}<br />
<br />
<br />
== Flight Dymanics Development: FDE ==<br />
<br />
This is an empty topic created by Bill Leaming to be filled out by Roy Holmes later...<br />
<br />
[[Category:Aircraft Design]]<br />
[[Category:Flight Dynamics]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=Aircraft_Fuselage_Creation:_The_Perfect_Way&diff=8551Aircraft Fuselage Creation: The Perfect Way2012-08-08T16:05:42Z<p>N4gix: New page: {{Infobox-Applicable-FSVersion | FSXA = true | FSX = true | FS2004 = true | FS2002 = true | FS2000 = false | FS98 = false }} ==Aircraft Fuselage Creation: The Perfect Way== I'm going to ...</p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = true<br />
| FS2000 = false<br />
| FS98 = false<br />
}}<br />
<br />
==Aircraft Fuselage Creation: The Perfect Way==<br />
<br />
I'm going to take the time to retype a post made by the late Master of Max/GMax Gerard van der Harst back on November 11, 2002 that I printed out and added to my '''''Design Notes''''' folder on that date.<br />
<br />
I've since built every model using this technique with perfect results every time!<br />
<br />
----<br />
<br />
There's no need to screw around with tubes people, and the "clone and downscale" method sucks because you have to indeed "plug the holes." Besides, downscaling will not give you constant thickness... and a host of other problems.<br />
<br />
Here's the (I dare say) '''THE''' way:<br />
<br />
- Build the fuselage.<br />
<br />
- Convert to editable mesh, clone the fuselage, select all polygons and extrude them inwards (negative value) along their normals (tick 'Local').<br />
<br />
- Select all polygons and hit 'Flip'.<br />
<br />
- Attach the new "inner hull" to the fuselage, select all vertices, set weld threshold to 0.001m and hit 'Weld Selected.'<br />
<br />
'''That's it: constant thickness and no holes to plug!'''<br />
<br />
[[Category:Aircraft Design]]<br />
[[Category:Modeling]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=C:_XML_Variables_in_C_Gauges&diff=8492C: XML Variables in C Gauges2012-07-11T02:25:27Z<p>N4gix: </p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = false<br />
| XP10 = false <br />
| XP9 = false <br />
}}<br />
<br />
<br />
==C: XML Variables in C Gauges==<br />
<br />
To control XML variables from a C gauge:<br />
<br />
// declare the variable and pointer ID for the variable<br />
<br />
double pitot_cover = 1 ; // this is the C variable<br />
ID pitot_cover_id; // this is the pointer address to the XML variable<br />
<br />
// Register the variable (this is the XML "name," e.g., L:PitotCover<br />
<br />
case PANEL_SERVICE_PRE_INITIALIZE:<br />
register_named_variable ( "PitotCover" );<br />
break;<br />
<br />
// now, you can use the next two statements to <br />
// (a) associate the ID with the XML variable, then <br />
// (b) set the variable to be identical to the C variable, e.g., pitot_cover<br />
<br />
case PANEL_SERVICE_PRE_UPDATE:<br />
pitot_cover_id = check_named_variable ( "PitotCover" ) ;<br />
set_named_variable_value ( pitot_cover_id, (FLOAT64)pitot_cover ) ;<br />
break;<br />
<br />
// now, in my mouse routine, I can set the value of pitot_cover, and it will <br />
//be automatically passed to the XML variable!<br />
<br />
BOOL FSAPI mouse_pitotcb( PPIXPOINT relative_point, FLAGS32 mouse_flags)<br />
{<br />
if ( pitot_cover == 0 ) { pitot_cover = 1 ; } else { pitot_cover = 0 ; }<br />
return FALSE;<br />
} <br />
<br />
// now, to use the XML variable to control the C variable, the only<br />
// difference is that you would use the get_named_variable_value command <br />
// instead, and omit the mouse code!<br />
<br />
pitot_cover_id = check_named_variable("PitotCover");<br />
pitot_cover = get_named_variable_value (pitot_cover_id); <br />
<br />
'''Alternate Method'''<br />
<br />
There is another method that may be used to communicate between C gauges and XML gauges, using the execute_calculator_code(); function. Here is the prototype for the function:<br />
<br />
execute_calculator_code(PCSTRINGZ code, FLOAT64* fvalue, SINT32* ivalue, PCSTRINGZ* svalue);<br />
<br />
"Translating" the function into more easily understood pseudo-code, we have this:<br />
<br />
execute_calculator_code(XML variable name,units, floating point var name, integer variable name, string variable name);<br />
<br />
To use the function, first determine from the "units" of the XML variable whether the returned value will be a floating point number, an integer, or a string.<br />
<br />
When constructing the function call, only ONE of the fields 2 through 4 will be used, an the unused fields filled with "NULL" value. For example, we want to fetch an ADF frequency, so we'd use something like this:<br />
<br />
FLOAT64 adf1_frequency = 0; // first declare the float C variable<br />
execute_calculator_code("(A:ADF ACTIVE FREQUENCY:1, KHz)",&adf1_frequency,NULL,NULL);<br />
<br />
If the XML variable is an integer, here is an example:<br />
<br />
SINT32 time_of_day; // first declare the integer C variable<br />
execute_calculator_code("(E:TIME OF DAY,Enum)",NULL,&time_of_day,NULL);<br />
<br />
If the XML variable is a string, here is an example:<br />
<br />
PCSTRINGZ WP_NextID; // first declare the string C variable<br />
execute_calculator_code("(A:GPS WP_NEXT ID,string)",NULL,NULL,&WP_NextID);<br />
<br />
Custom L:variables may also be obtained following the same structure shown above.<br />
<br />
''BOOLEAN:''<br />
execute_calculator_code("(L:MyCustomVariable,bool)",NULL,&my_custom_variable,NULL);<br />
<br />
''FLOAT:''<br />
execute_calculator_code("(L:MyCustomVariable,enum)",&my_custom_variable,NULL,NULL);<br />
<br />
This method is much easier to use than the method described in the previous section. <br />
<br />
To SEND a command with this method, use the following format:<br />
<br />
execute_calculator_code("(>K:SOUND_TOGGLE)", NULL, NULL, NULL);<br />
<br />
If you need to pass a value for a SET type key_event, simply use the same syntax used in an XML gauge by prefixing the command with the value (which can itself be another XML variable as shown below):<br />
<br />
execute_calculator_code("(A:Plane heading degrees gyro,degrees) (>K:HEADING_BUG_SET)", NULL, NULL, NULL);<br />
<br />
To set an L:variable, use this syntax:<br />
<br />
''Constant:''<br />
execute_calculator_code(" 120 (>L:CustomXMLvar,enum)",NULL,NULL,NULL);<br />
<br />
''C Variable:''<br />
FLOAT64 myVar = 100.00;<br />
char cTemp[60];<br />
sprintf_s(cTemp, %f%s, myVar, " (>L:MyVar,number)");<br />
PCSTRINGZ szString = cTemp;<br />
execute_calculator_code(szString,NULL,NULL,NULL);<br />
<br />
<br />
[[Category:Aircraft Design]]<br />
[[Category:Panel and Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=C:_XML_Variables_in_C_Gauges&diff=8491C: XML Variables in C Gauges2012-07-11T02:24:17Z<p>N4gix: </p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = false<br />
| XP10 = false <br />
| XP9 = false <br />
}}<br />
<br />
<br />
==C: XML Variables in C Gauges==<br />
<br />
To control XML variables from a C gauge:<br />
<br />
// declare the variable and pointer ID for the variable<br />
<br />
double pitot_cover = 1 ; // this is the C variable<br />
ID pitot_cover_id; // this is the pointer address to the XML variable<br />
<br />
// Register the variable (this is the XML "name," e.g., L:PitotCover<br />
<br />
case PANEL_SERVICE_PRE_INITIALIZE:<br />
register_named_variable ( "PitotCover" );<br />
break;<br />
<br />
// now, you can use the next two statements to <br />
// (a) associate the ID with the XML variable, then <br />
// (b) set the variable to be identical to the C variable, e.g., pitot_cover<br />
<br />
case PANEL_SERVICE_PRE_UPDATE:<br />
pitot_cover_id = check_named_variable ( "PitotCover" ) ;<br />
set_named_variable_value ( pitot_cover_id, (FLOAT64)pitot_cover ) ;<br />
break;<br />
<br />
// now, in my mouse routine, I can set the value of pitot_cover, and it will <br />
//be automatically passed to the XML variable!<br />
<br />
BOOL FSAPI mouse_pitotcb( PPIXPOINT relative_point, FLAGS32 mouse_flags)<br />
{<br />
if ( pitot_cover == 0 ) { pitot_cover = 1 ; } else { pitot_cover = 0 ; }<br />
return FALSE;<br />
} <br />
<br />
// now, to use the XML variable to control the C variable, the only<br />
// difference is that you would use the get_named_variable_value command <br />
// instead, and omit the mouse code!<br />
<br />
pitot_cover_id = check_named_variable("PitotCover");<br />
pitot_cover = get_named_variable_value (pitot_cover_id); <br />
<br />
'''Alternate Method'''<br />
<br />
There is another method that may be used to communicate between C gauges and XML gauges, using the execute_calculator_code(); function. Here is the prototype for the function:<br />
<br />
execute_calculator_code(PCSTRINGZ code, FLOAT64* fvalue, SINT32* ivalue, PCSTRINGZ* svalue);<br />
<br />
"Translating" the function into more easily understood pseudo-code, we have this:<br />
<br />
execute_calculator_code(XML variable name,units, floating point var name, integer variable name, string variable name);<br />
<br />
To use the function, first determine from the "units" of the XML variable whether the returned value will be a floating point number, an integer, or a string.<br />
<br />
When constructing the function call, only ONE of the fields 2 through 4 will be used, an the unused fields filled with "NULL" value. For example, we want to fetch an ADF frequency, so we'd use something like this:<br />
<br />
FLOAT64 adf1_frequency = 0; // first declare the float C variable<br />
execute_calculator_code("(A:ADF ACTIVE FREQUENCY:1, KHz)",&adf1_frequency,NULL,NULL);<br />
<br />
If the XML variable is an integer, here is an example:<br />
<br />
SINT32 time_of_day; // first declare the integer C variable<br />
execute_calculator_code("(E:TIME OF DAY,Enum)",NULL,&time_of_day,NULL);<br />
<br />
If the XML variable is a string, here is an example:<br />
<br />
PCSTRINGZ WP_NextID; // first declare the string C variable<br />
execute_calculator_code("(A:GPS WP_NEXT ID,string)",NULL,NULL,&WP_NextID);<br />
<br />
Custom L:variables may also be obtained following the same structure shown above.<br />
<br />
''BOOLEAN:''<br />
execute_calculator_code("(L:MyCustomVariable,bool)",NULL,&my_custom_variable,NULL);<br />
<br />
''FLOAT:''<br />
execute_calculator_code("(L:MyCustomVariable,enum)",&my_custom_variable,NULL,NULL);<br />
<br />
This method is much easier to use than the method described in the previous section. <br />
<br />
To SEND a command with this method, use the following format:<br />
<br />
execute_calculator_code("(>K:SOUND_TOGGLE)", NULL, NULL, NULL);<br />
<br />
If you need to pass a value for a SET type key_event, simply use the same syntax used in an XML gauge by prefixing the command with the value (which can itself be another XML variable as shown below):<br />
<br />
execute_calculator_code("(A:Plane heading degrees gyro,degrees) (>K:HEADING_BUG_SET)", NULL, NULL, NULL);<br />
<br />
To set an L:variable, use this syntax:<br />
<br />
''Constant:''<br />
execute_calculator_code(" 120 (>L:CustomXMLvar,enum)",NULL,NULL,NULL);<br />
<br />
''C Variable:''<br />
FLOAT64 myVar = 100.00;<br />
char cTemp[60];<br />
sprintf_s(cTemp, %f%s, myVar, " (>L:MyVar,number)");<br />
PCSTRINGZ szString = cTemp;<br />
execute_calculator_code(szString,NULL,NULL,NULL);<br />
<br />
<br />
[[Category:Aircraft Design]]<br />
[[Category:Panel and Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=C:_XML_Variables_in_C_Gauges&diff=8490C: XML Variables in C Gauges2012-07-10T16:43:19Z<p>N4gix: New page: {{Infobox-Applicable-FSVersion | FSXA = true | FSX = true | FS2004 = true | FS2002 = false | XP10 = false | XP9 = false }} ==C: XML Variables in C Gauges== To control XML variables fr...</p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = false<br />
| XP10 = false <br />
| XP9 = false <br />
}}<br />
<br />
<br />
==C: XML Variables in C Gauges==<br />
<br />
To control XML variables from a C gauge:<br />
<br />
// declare the variable and pointer ID for the variable<br />
<br />
double pitot_cover = 1 ; // this is the C variable<br />
ID pitot_cover_id; // this is the pointer address to the XML variable<br />
<br />
// Register the variable (this is the XML "name," e.g., L:PitotCover<br />
<br />
case PANEL_SERVICE_PRE_INITIALIZE:<br />
register_named_variable ( "PitotCover" );<br />
break;<br />
<br />
// now, you can use the next two statements to <br />
// (a) associate the ID with the XML variable, then <br />
// (b) set the variable to be identical to the C variable, e.g., pitot_cover<br />
<br />
case PANEL_SERVICE_PRE_UPDATE:<br />
pitot_cover_id = check_named_variable ( "PitotCover" ) ;<br />
set_named_variable_value ( pitot_cover_id, (FLOAT64)pitot_cover ) ;<br />
break;<br />
<br />
// now, in my mouse routine, I can set the value of pitot_cover, and it will <br />
//be automatically passed to the XML variable!<br />
<br />
BOOL FSAPI mouse_pitotcb( PPIXPOINT relative_point, FLAGS32 mouse_flags)<br />
{<br />
if ( pitot_cover == 0 ) { pitot_cover = 1 ; } else { pitot_cover = 0 ; }<br />
return FALSE;<br />
} <br />
<br />
// now, to use the XML variable to control the C variable, the only<br />
// difference is that you would use the get_named_variable_value command <br />
// instead, and omit the mouse code!<br />
<br />
pitot_cover_id = check_named_variable("PitotCover");<br />
pitot_cover = get_named_variable_value (pitot_cover_id); <br />
<br />
'''Alternate Method'''<br />
<br />
There is another method that may be used to communicate between C gauges and XML gauges, using the execute_calculator_code(); function. Here is the prototype for the function:<br />
<br />
execute_calculator_code(PCSTRINGZ code, FLOAT64* fvalue, SINT32* ivalue, PCSTRINGZ* svalue);<br />
<br />
"Translating" the function into more easily understood pseudo-code, we have this:<br />
<br />
execute_calculator_code(XML variable name,units, floating point var name, integer variable name, string variable name);<br />
<br />
To use the function, first determine from the "units" of the XML variable whether the returned value will be a floating point number, an integer, or a string.<br />
<br />
When constructing the function call, only ONE of the fields 2 through 4 will be used, an the unused fields filled with "NULL" value. For example, we want to fetch an ADF frequency, so we'd use something like this:<br />
<br />
FLOAT64 adf1_frequency = 0; // first declare the float C variable<br />
execute_calculator_code("(A:ADF ACTIVE FREQUENCY:1, KHz)",&adf1_frequency,NULL,NULL);<br />
<br />
If the XML variable is an integer, here is an example:<br />
<br />
SINT32 time_of_day; // first declare the integer C variable<br />
execute_calculator_code("(E:TIME OF DAY,Enum)",NULL,&time_of_day,NULL);<br />
<br />
If the XML variable is a string, here is an example:<br />
<br />
PCSTRINGZ VorIcaoCode; // first declare the string C variable<br />
execute_calculator_code("(C:fs9gps:WaypointICAO,st ring)",NULL,NULL,&VorIcaoCode);<br />
<br />
Take note that the string example also shows how we can easily fetch stuff from the GPS system using this technique!<br />
<br />
Custom L:variables may also be obtained following the same structure shown above.<br />
<br />
''BOOLEAN:''<br />
execute_calculator_code("(L:MyCustomVariable,bool)",NULL,&my_custom_variable,NULL);<br />
<br />
''FLOAT:''<br />
execute_calculator_code("(L:MyCustomVariable,enum)",&my_custom_variable,NULL,NULL);<br />
<br />
This method is much easier to use than the method described in the previous section. <br />
<br />
To SEND a command with this method, use the following format:<br />
<br />
execute_calculator_code("(>K:SOUND_TOGGLE)", NULL, NULL, NULL);<br />
<br />
If you need to pass a value for a SET type key_event, simply use the same syntax used in an XML gauge by prefixing the command with the value (which can itself be another XML variable as shown below):<br />
<br />
execute_calculator_code("(A:Plane heading degrees gyro,degrees) (>K:HEADING_BUG_SET)", NULL, NULL, NULL);<br />
<br />
To set an L:variable, use this syntax:<br />
<br />
''Constant:''<br />
execute_calculator_code(" 120 (>L:CustomXMLvar,enum)",NULL,NULL,NULL);<br />
<br />
''C Variable:''<br />
char cTemp[200];<br />
SINT32 temp_val=myCvalue;<br />
sprintf_s(cTemp,"temp_val (>L:L:CustomXMLvar,enum)");<br />
PCSTRINGZ szSetValue = cTemp;<br />
execute_calculator_code(szSetValue,NULL,NULL,NULL);<br />
<br />
[[Category:Aircraft Design]]<br />
[[Category:Panel and Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=XML:_Increment_Variable_w/Modulo_Reset&diff=8489XML: Increment Variable w/Modulo Reset2012-06-29T15:58:51Z<p>N4gix: </p>
<hr />
<div>==XML: Increment Variable w/Modulo Reset==<br />
<br />
{{Infobox-Applicable-FSVersion<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = false<br />
| XP10 = false <br />
| XP9 = false <br />
}}<br />
<br />
The following script shows how to increment the custom (L:Variable,unit) value by 1 on each "click". The number preceeding the modulo operator (%) is the reset point (highcount + 1), at which point the variable will reset back to zero!<br />
<br />
'''NOTE: this technique works for integers only. Fractional increment/decrement should use other methods.'''<br />
<br />
0 + click = 1; 1 mod 5 = 1<br />
1 + click = 2; 2 mod 5 = 2<br />
2 + click = 3; 3 mod 5 = 3<br />
3 + click = 4; 4 mod 5 = 4<br />
4 + click = 5; 5 mod 5 = 0<br />
<br />
<MouseRect><br />
<Cursor>Hand</Cursor><br />
<TooltipText>Window Left</TooltipText><br />
<CallbackCode><br />
(L:SwitchWindowLeft, enum) ++ 5 % (>L:SwitchWindowLeft, enum)<br />
</CallbackCode><br />
</MouseRect><br />
<br />
[[Category:Aircraft Design]]<br />
[[Category:Panel and Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=XML:_Increment_Variable_w/Modulo_Reset&diff=8488XML: Increment Variable w/Modulo Reset2012-06-29T15:57:00Z<p>N4gix: </p>
<hr />
<div>==XML: Increment Variable w/Modulo Reset==<br />
<br />
{{Infobox-Applicable-FSVersion<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = false<br />
| XP10 = false <br />
| XP9 = false <br />
}}<br />
<br />
The following script shows how to increment the custom (L:Variable,unit) value by 1 on each "click". The number preceeding the modulo operator (%) is the upper limit, at which point the variable will reset back to zero!<br />
<br />
'''NOTE: this technique works for integers only. Fractional increment/decrement should use other methods.'''<br />
<br />
0 + click = 1; 1 mod 5 = 1<br />
1 + click = 2; 2 mod 5 = 2<br />
2 + click = 3; 3 mod 5 = 3<br />
3 + click = 4; 4 mod 5 = 4<br />
4 + click = 5; 5 mod 5 = 0<br />
<br />
<MouseRect><br />
<Cursor>Hand</Cursor><br />
<TooltipText>Window Left</TooltipText><br />
<CallbackCode><br />
(L:SwitchWindowLeft, enum) ++ 5 % (>L:SwitchWindowLeft, enum)<br />
</CallbackCode><br />
</MouseRect><br />
<br />
[[Category:Aircraft Design]]<br />
[[Category:Panel and Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=XML:_Increment_Variable_w/Modulo_Reset&diff=8487XML: Increment Variable w/Modulo Reset2012-06-28T23:01:04Z<p>N4gix: New page: ==XML: Increment Variable w/Modulo Reset== {{Infobox-Applicable-FSVersion | FSXA = true | FSX = true | FS2004 = true | FS2002 = false | XP10 = false | XP9 = false }} The following scri...</p>
<hr />
<div>==XML: Increment Variable w/Modulo Reset==<br />
<br />
{{Infobox-Applicable-FSVersion<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = false<br />
| XP10 = false <br />
| XP9 = false <br />
}}<br />
<br />
The following script shows how to increment the custom (L:Variable,unit) value by 1 on each "click". The number preceeding the modulo operator (%) is the upper limit, at which point the variable will reset back to zero!<br />
<br />
0 + click = 1; 1 mod 5 = 1<br />
1 + click = 2; 2 mod 5 = 2<br />
2 + click = 3; 3 mod 5 = 3<br />
3 + click = 4; 4 mod 5 = 4<br />
4 + click = 5; 5 mod 5 = 0<br />
<br />
<MouseRect><br />
<Cursor>Hand</Cursor><br />
<TooltipText>Window Left</TooltipText><br />
<CallbackCode><br />
(L:SwitchWindowLeft, enum) ++ 5 % (>L:SwitchWindowLeft, enum)<br />
</CallbackCode><br />
</MouseRect><br />
<br />
[[Category:Aircraft Design]]<br />
[[Category:Panel and Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=C:_Decimal_to_BCD&diff=8486C: Decimal to BCD2012-06-13T14:43:22Z<p>N4gix: </p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = true<br />
| FS2000 = true<br />
| FS98 = true<br />
}}<br />
== C: BCD to Decimal and Decimal to BCD ==<br />
<br />
This scheme was supplied by Arne Bartels which allows BCD conversion in both directions. Add the following to the master source file:-<br />
<br />
#include <math.h><br />
#define Bcd2Dec(BcdNum) HornerScheme(BcdNum,0x10,10)<br />
#define Dec2Bcd(DecNum) HornerScheme(DecNum,10,0x10)<br />
<br />
UINT32 HornerScheme(UINT32 Num,UINT32 Divider,UINT32 Factor)<br />
{<br />
UINT32 Remainder=0,Quotient=0,Result=0;<br />
Remainder=Num%Divider;<br />
Quotient=Num/Divider;<br />
if(!(Quotient==0&&Remainder==0))<br />
Result+=HornerScheme(Quotient,Divider,Factor)*Factor+Remainder;<br />
return Result;<br />
}<br />
<br />
Then for each sub-gauge that requires a BCD conversion use the following syntax:-<br />
<br />
Bcd2Dec(bcd_number) for BCD to decimal and<br />
Dec2Bcd(dec_number) for decimal to BCD conversions.<br />
<br />
[[Category:Aircraft Design]]<br />
[[Category:Panel and Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=C:_Decimal_to_BCD&diff=8485C: Decimal to BCD2012-06-13T14:42:30Z<p>N4gix: New page: {{Infobox-Applicable-FSVersion | FSXI = false | FSXA = true | FSX = true | FS2004 = true | FS2002 = false | FS2000 = unknown | FS98 = unknown }} == C: BCD to Decimal and Decimal to BCD == ...</p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = false<br />
| FS2000 = unknown<br />
| FS98 = unknown<br />
}}<br />
== C: BCD to Decimal and Decimal to BCD ==<br />
<br />
This scheme was supplied by Arne Bartels which allows BCD conversion in both directions. Add the following to the master source file:-<br />
<br />
#include <math.h><br />
#define Bcd2Dec(BcdNum) HornerScheme(BcdNum,0x10,10)<br />
#define Dec2Bcd(DecNum) HornerScheme(DecNum,10,0x10)<br />
<br />
UINT32 HornerScheme(UINT32 Num,UINT32 Divider,UINT32 Factor)<br />
{<br />
UINT32 Remainder=0,Quotient=0,Result=0;<br />
Remainder=Num%Divider;<br />
Quotient=Num/Divider;<br />
if(!(Quotient==0&&Remainder==0))<br />
Result+=HornerScheme(Quotient,Divider,Factor)*Factor+Remainder;<br />
return Result;<br />
}<br />
<br />
Then for each sub-gauge that requires a BCD conversion use the following syntax:-<br />
<br />
Bcd2Dec(bcd_number) for BCD to decimal and<br />
Dec2Bcd(dec_number) for decimal to BCD conversions.<br />
<br />
[[Category:Aircraft Design]]<br />
[[Category:Panel and Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=XML:_Set_ADF_Frequency&diff=8329XML: Set ADF Frequency2012-04-20T17:31:10Z<p>N4gix: New page: {{Infobox-Applicable-FSVersion | FSXI = false | FSXA = true | FSX = true | FS2004 = true | FS2002 = false | FS2000 = unknown | FS98 = unknown }} ==XML: Set ADF Frequency== We need to conv...</p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = false<br />
| FS2000 = unknown<br />
| FS98 = unknown<br />
}}<br />
<br />
==XML: Set ADF Frequency==<br />
We need to convert the desired ADF Frequency (KHz) to BCD format. This simple @Macro will do the job painlessly for us.<br />
<br />
Note the use of lower case L in '''l0''' and '''l2''', this is [[not]] a number 1:<br />
<br />
e.g., s2 '''[[l]]'''0 10 / flr 10 % 16 * '''[[l]]'''2 +<br />
<br />
<Macro Name="SetADF"><br />
(* UPDATE ADF FREQUENCY *)<br />
10000 * s0 10 %<br />
s2 l0 10 / flr 10 % 16 * l2 +<br />
s2 l0 100 / flr 10 % 256 * l2 +<br />
s2 l0 1000 / flr 10 % 4096 * l2 +<br />
s2 l0 10000 / flr 10 % 65536 * l2 +<br />
s2 l0 100000 / flr 10 % 1048576 * l2 +<br />
s2 l0 1000000 / flr 10 % 16777216 * l2 +<br />
s2 l0 10000000 / flr 10 % 268435456 * l2 +<br />
s2 (>K:ADF_COMPLETE_SET)<br />
</Macro><br />
<br />
Usage: <br />
@SetADF((L:ADF1 Frequency,Khz))<br />
<br />
[[category:Aircraft Design]]<br />
[[category:Panel and Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=XML:_Decode_Flags&diff=8328XML: Decode Flags2012-04-20T15:47:27Z<p>N4gix: </p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = false<br />
| FS2000 = unknown<br />
| FS98 = unknown<br />
}}<br />
== XML Decode Macros ==<br />
<br />
There are several XML variables that are returned as "flags" in an 8bit format. In order to use them you must "decode" them. This is an easy method to use as all the script is encapsulated in a set of <Macro>s for quick and simple use. Just copy/paste these <Macro> definitions to your XML gauge script.<br />
<br />
Examples of usage are at the bottom of this entry.<br />
<br />
// DO NOT COPY THIS! It is for reference only //<br />
128 BIT7: 0 = VOR 1= Localizer <br />
64 BIT6: 1 = glideslope available <br />
32 BIT5: 1 = no localizer backcourse <br />
16 BIT4: 1 = DME transmitter at glide slope transmitter <br />
8 BIT3: 1 = no nav signal available <br />
4 BIT2: 1 = voice available <br />
2 BIT1: 1 = TACAN available <br />
1 BIT0: 1 = DME available<br />
<br />
'''MACRO Definitions for the NAV CODES variable''' <br />
<br />
<Macro Name="IsVor">(A:NAV CODES:1, flags) 128 &#38;&#97;&#109;&#112;&#59; 128 !=</Macro><br />
<Macro Name="IsLoc">(A:NAV CODES:1, flags) 128 &#38;&#97;&#109;&#112;&#59; 128 ==</Macro><br />
<Macro Name="HasGS">(A:NAV CODES:1, flags) 64 &#38;&#97;&#109;&#112;&#59; 64 ==</Macro><br />
<Macro Name="HasBCGS">(A:NAV CODES:1, flags) 32 &#38;&#97;&#109;&#112;&#59; 32 !=</Macro><br />
<Macro Name="HasDMEatGS">(A:NAV CODES:1, flags) 16 &#38;&#97;&#109;&#112;&#59; 16 ==</Macro><br />
<Macro Name="HasNAVsignal">(A:NAV CODES:1, flags) 8 &#38;&#97;&#109;&#112;&#59; 8 !=</Macro><br />
<Macro Name="HasVoice">(A:NAV CODES:1, flags) 4 &#38;&#97;&#109;&#112;&#59; 4 ==</Macro><br />
<Macro Name="IsTacan">(A:NAV CODES:1, flags) 2 &#38;&#97;&#109;&#112;&#59; 2 ==</Macro><br />
<Macro Name="HasDME">(A:NAV CODES:1, flags) 1 &#38;&#97;&#109;&#112;&#59; 1 ==</Macro><br />
<br />
// DO NOT COPY THIS! It is for reference only //<br />
1 BIT0: 1 = back course available<br />
2 BIT1: 1 = localizer tuned in<br />
4 BIT2: 1 = on course<br />
128 BIT7: 1 = station active<br />
<br />
'''MACRO Definitions for the NAV BACK COURSE FLAGS variable'''<br />
<br />
<Macro Name="IsBCavailable">(A:NAV BACK COURSE FLAGS:1, flags) 1 &#38;&#97;&#109;&#112;&#59; 1 ==</Macro><br />
<Macro Name="IsLocalizerTuned">(A:NAV BACK COURSE FLAGS:1, flags) 2 &#38;&#97;&#109;&#112;&#59; 2 ==</Macro><br />
<Macro Name="IsOnCourse">(A:NAV BACK COURSE FLAGS:1, flags) 4 &#38;&#97;&#109;&#112;&#59; 4 ==</Macro><br />
<Macro Name="IsStationActive">(A:NAV BACK COURSE FLAGS:1, flags) 128 &#38;&#97;&#109;&#112;&#59; 128 ==</Macro><br />
<br />
[[Category:Aircraft Design]]<br />
[[Category:Panel and Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=XML:_Decimal_To_BCD_Macro_-_Set_Nav/Com_Freq&diff=8324XML: Decimal To BCD Macro - Set Nav/Com Freq2012-04-19T17:28:36Z<p>N4gix: </p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = false<br />
| FS2000 = unknown<br />
| FS98 = unknown<br />
}}<br />
<br />
==XML:Decimal to BCD Macro==<br />
<br />
A very simple but useful @macro to convert any decimal frequency to BCD format to allow direct SETting of COM and NAV frequencies in FS:<br />
<br />
<Macro Name="Dec2Bcd"><br />
100 * 10000 % int<br />
d 10 % r 10 / int<br />
d 10 % r 10 / int<br />
d 10 % r 10 / int<br />
16 * +<br />
16 * +<br />
16 * +<br />
</Macro><br />
<br />
Usage is then as simple as passing the decimal frequency to the @macro the issuing the appropriate _SET key event:<br />
<br />
<Click><br />
@Dec2Bcd(112.30) (>K:NAV2_RADIO_SET)<br />
</Click><br />
<br />
You could also use a custom L:var to pass a "tuned" frequency:<br />
<br />
<Click><br />
@XPDRSet((L:XPDR_Code,number)) <br />
<br />
<br />
@Dec2Bcd((L:Nav2Freq,enum)) (>K:NAV2_RADIO_SET)<br />
</Click><br />
<br />
[[Category:Aircraft Design]]<br />
[[Category:Panel and Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=XML:_Decimal_To_BCD_Macro_-_Set_Nav/Com_Freq&diff=8323XML: Decimal To BCD Macro - Set Nav/Com Freq2012-04-19T17:21:46Z<p>N4gix: New page: {{Infobox-Applicable-FSVersion | FSXI = false | FSXA = true | FSX = true | FS2004 = true | FS2002 = false | FS2000 = unknown | FS98 = unknown }} ==XML:Decimal to BCD Macro== A very simpl...</p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = false<br />
| FS2000 = unknown<br />
| FS98 = unknown<br />
}}<br />
<br />
==XML:Decimal to BCD Macro==<br />
<br />
A very simple but useful @macro to convert any decimal frequency to BCD format to allow direct SETting of COM and NAV frequencies in FS:<br />
<br />
<Macro Name="Dec2Bcd"><br />
100 * 10000 % int<br />
d 10 % r 10 / int<br />
d 10 % r 10 / int<br />
d 10 % r 10 / int<br />
16 * +<br />
16 * +<br />
16 * +<br />
</Macro><br />
<br />
Usage is then as simple as passing the decimal frequency to the @macro the issuing the appropriate _SET key event:<br />
<br />
<Click><br />
112.30 @Dec2Bcd (>K:NAV2_RADIO_SET)<br />
</Click><br />
<br />
You could also use a custom L:var to pass a "tuned" frequency:<br />
<br />
<Click><br />
(L:Nav2Freq,enum) @Dec2Bcd (>K:NAV2_RADIO_SET)<br />
</Click><br />
<br />
[[Category:Aircraft Design]]<br />
[[Category:Panel and Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=XML:_Decode_Flags&diff=8322XML: Decode Flags2012-04-19T16:22:12Z<p>N4gix: </p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = false<br />
| FS2000 = unknown<br />
| FS98 = unknown<br />
}}<br />
== XML Decode Macros ==<br />
<br />
There are several XML variables that are returned as "flags" in an 8bit format. In order to use them you must "decode" them. This is an easy method to use as all the script is encapsulated in a set of <Macro>s for quick and simple use. Just copy/paste these <Macro> definitions to your XML gauge script.<br />
<br />
Examples of usage are at the bottom of this entry.<br />
<br />
// DO NOT COPY THIS! It is for reference only //<br />
128 BIT7: 0= VOR 1= Localizer <br />
64 BIT6: 1= glideslope available <br />
32 BIT5: 1= no localizer backcourse <br />
16 BIT4: 1= DME transmitter at glide slope transmitter <br />
8 BIT3: 1= no nav signal available <br />
4 BIT2: 1= voice available <br />
2 BIT1: 1 = TACAN available <br />
1 BIT0: 1= DME available<br />
<br />
'''MACRO Definitions for the NAV CODES variable''' <br />
<br />
<Macro Name="IsVor">(A:NAV CODES:1, flags) 128 and !</Macro><br />
<Macro Name="IsLoc">(A:NAV CODES:1, flags) 128 and</Macro><br />
<Macro Name="HasGS">(A:NAV CODES:1, flags) 64 and</Macro><br />
<Macro Name="HasBCGS">(A:NAV CODES:1, flags) 32 and !</Macro><br />
<Macro Name="HasDMEatGS">(A:NAV CODES:1, flags) 16 and</Macro><br />
<Macro Name="HasNAVsignal">(A:NAV CODES:1, flags) 8 and !</Macro><br />
<Macro Name="HasVoice">(A:NAV CODES:1, flags) 4 and</Macro><br />
<Macro Name="IsTacan">(A:NAV CODES:1, flags) 2 and</Macro><br />
<Macro Name="HasDME">(A:NAV CODES:1, flags) 1 and</Macro><br />
<br />
// DO NOT COPY THIS! It is for reference only //<br />
1 BIT0: 1=back course available<br />
2 BIT1: 1=localizer tuned in<br />
4 BIT2: 1=on course<br />
128 BIT7: 1=station active<br />
<br />
'''MACRO Definitions for the NAV BACK COURSE FLAGS variable'''<br />
<br />
<Macro Name="IsBCavailable">(A:NAV BACK COURSE FLAGS:1, flags) 1 and</Macro><br />
<Macro Name="IsLocalizerTuned">(A:NAV BACK COURSE FLAGS:1, flags) 2 and</Macro><br />
<Macro Name="IsOnCourse">(A:NAV BACK COURSE FLAGS:1, flags) 4 and</Macro><br />
<Macro Name="IsStationActive">(A:NAV BACK COURSE FLAGS:1, flags) 128 and</Macro><br />
<br />
[[Category:Aircraft Design]]<br />
[[Category:Panel and Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=GaugeSound.dll&diff=8313GaugeSound.dll2012-04-06T00:20:40Z<p>N4gix: </p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = false<br />
| FS2000 = false<br />
| FS98 = false<br />
}}<br />
<br />
If you wish to use the GaugeSound.dll in your gauge(s), the first step is to declare the following in your main gauge (.cpp) file:<br />
<br />
// Sound declarations<br />
typedef VOID (*TGaugePlaySound)(LPTSTR,LPSTR,int);<br />
typedef VOID (*TGaugeStopSound)(LPTSTR);<br />
typedef VOID (*TTerminateSounds)();<br />
TGaugePlaySound GaugePlaySound;<br />
TGaugeStopSound GaugeStopSound;<br />
TTerminateSounds TerminateSounds;<br />
HMODULE MGaugeSound;<br />
<br />
// If you need to "loop" some sounds, define the "stop loop string names"<br />
LPSTR flap = "flap";<br />
LPSTR gearhorn = "gearhorn";<br />
LPSTR overspeed = "overspeed";<br />
LPSTR firetest = "firetest";<br />
LPSTR geartest = "geartest";<br />
LPSTR speedtest = "speedtest";<br />
LPSTR warning = "warning";<br />
<br />
Next, initialize the following in the PANEL_SERVICE_PRE_INITIALIZE case:<br />
<br />
case PANEL_SERVICE_PRE_INITIALIZE:<br />
if (MGaugeSound == NULL) {MGaugeSound = LoadLibrary("GaugeSound");}<br />
GaugePlaySound = (TGaugePlaySound)GetProcAddress(MGaugeSound,"GaugePlaySound");<br />
GaugeStopSound = (TGaugeStopSound)GetProcAddress(MGaugeSound,"GaugeStopSound");<br />
TerminateSounds = (TTerminateSounds)GetProcAddress(MGaugeSound,"TerminateSounds");<br />
break;<br />
<br />
Next, add the following to the PANEL_SERVICE_PRE_UPDATE case:<br />
<br />
case PANEL_SERVICE_PRE_UPDATE:<br />
MGaugeSound = GetModuleHandle("GaugeSound");<br />
if (MGaugeSound == NULL) {MGaugeSound = LoadLibrary("GaugeSound");}<br />
GaugePlaySound = (TGaugePlaySound)GetProcAddress(MGaugeSound,"GaugePlaySound");<br />
GaugeStopSound = (TGaugeStopSound)GetProcAddress(MGaugeSound,"GaugeStopSound");<br />
TerminateSounds = (TTerminateSounds)GetProcAddress(MGaugeSound,"TerminateSounds");<br />
break;<br />
<br />
<br />
Finally, add this to the PANEL_SERVICE_PRE_KILL case:<br />
<br />
case PANEL_SERVICE_PRE_KILL:<br />
MGaugeSound = GetModuleHandle("GaugeSound");<br />
if (MGaugeSound == NULL) {MGaugeSound = LoadLibrary("GaugeSound");}<br />
GaugePlaySound = (TGaugePlaySound)GetProcAddress(MGaugeSound,"GaugePlaySound");<br />
GaugeStopSound = (TGaugeStopSound)GetProcAddress(MGaugeSound,"GaugeStopSound");<br />
TerminateSounds = (TTerminateSounds)GetProcAddress(MGaugeSound,"TerminateSounds");<br />
(TerminateSounds)();<br />
FreeLibrary(MGaugeSound);<br />
break;<br />
<br />
To play a sound, use one of the following examples in a mouse callback. Note that "PathName" is the sub-folder name in the default FS ..\Sound folder, e.g., ..\Sound\Milviz. "SoundName" is for example push.wav:<br />
<br />
'''Play once:'''<br />
<br />
(GaugePlaySound)("sound\\PathName\\SoundName.wav","",0) ; <br />
<br />
'''Loop Sound:'''<br />
<br />
Looping a sound continuously require that you specify a "stop loop string name" and set the third parameter to 1 (0 = play once, 1 = loop continuously).<br />
<br />
if ( *rotartest == 2 ) <br />
{ (GaugePlaySound)("soundesdggearhorn.wav",geartest,1) ; } <br />
else { (GaugeStopSound)(geartest); }<br />
<br />
[[category:Aircraft Design]]<br />
[[category:Panel and Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=GaugeSound.dll&diff=8312GaugeSound.dll2012-04-06T00:19:44Z<p>N4gix: New page: {{Infobox-Applicable-FSVersion | FSXI = false | FSXA = true | FSX = true | FS2004 = true | FS2002 = false | FS2000 = false | FS98 = false }} If you wish to use the GaugeSound.dll in your ...</p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = false<br />
| FS2000 = false<br />
| FS98 = false<br />
}}<br />
<br />
If you wish to use the GaugeSound.dll in your gauge(s), the first step is to declare the following in your main gauge (.cpp) file:<br />
<br />
// Sound declarations<br />
typedef VOID (*TGaugePlaySound)(LPTSTR,LPSTR,int);<br />
typedef VOID (*TGaugeStopSound)(LPTSTR);<br />
typedef VOID (*TTerminateSounds)();<br />
TGaugePlaySound GaugePlaySound;<br />
TGaugeStopSound GaugeStopSound;<br />
TTerminateSounds TerminateSounds;<br />
HMODULE MGaugeSound;<br />
<br />
// If you need to "loop" some sounds, define the "stop loop string names"<br />
LPSTR flap = "flap";<br />
LPSTR gearhorn = "gearhorn";<br />
LPSTR overspeed = "overspeed";<br />
LPSTR firetest = "firetest";<br />
LPSTR geartest = "geartest";<br />
LPSTR speedtest = "speedtest";<br />
LPSTR warning = "warning";<br />
<br />
Next, initialize the following in the PANEL_SERVICE_PRE_INITIALIZE case:<br />
<br />
case PANEL_SERVICE_PRE_INITIALIZE:<br />
rtu1_bg_element = (PELEMENT_STATIC_IMAGE)pgauge->elements_list[0];<br />
if (MGaugeSound == NULL) {MGaugeSound = LoadLibrary("GaugeSound");}<br />
GaugePlaySound = (TGaugePlaySound)GetProcAddress(MGaugeSound,"GaugePlaySound");<br />
GaugeStopSound = (TGaugeStopSound)GetProcAddress(MGaugeSound,"GaugeStopSound");<br />
TerminateSounds = (TTerminateSounds)GetProcAddress(MGaugeSound,"TerminateSounds");<br />
break;<br />
<br />
Next, add the following to the PANEL_SERVICE_PRE_UPDATE case:<br />
<br />
case PANEL_SERVICE_PRE_UPDATE:<br />
MGaugeSound = GetModuleHandle("GaugeSound");<br />
if (MGaugeSound == NULL) {MGaugeSound = LoadLibrary("GaugeSound");}<br />
GaugePlaySound = (TGaugePlaySound)GetProcAddress(MGaugeSound,"GaugePlaySound");<br />
GaugeStopSound = (TGaugeStopSound)GetProcAddress(MGaugeSound,"GaugeStopSound");<br />
TerminateSounds = (TTerminateSounds)GetProcAddress(MGaugeSound,"TerminateSounds");<br />
break;<br />
<br />
<br />
Finally, add this to the PANEL_SERVICE_PRE_KILL case:<br />
<br />
case PANEL_SERVICE_PRE_KILL:<br />
MGaugeSound = GetModuleHandle("GaugeSound");<br />
if (MGaugeSound == NULL) {MGaugeSound = LoadLibrary("GaugeSound");}<br />
GaugePlaySound = (TGaugePlaySound)GetProcAddress(MGaugeSound,"GaugePlaySound");<br />
GaugeStopSound = (TGaugeStopSound)GetProcAddress(MGaugeSound,"GaugeStopSound");<br />
TerminateSounds = (TTerminateSounds)GetProcAddress(MGaugeSound,"TerminateSounds");<br />
(TerminateSounds)();<br />
FreeLibrary(MGaugeSound);<br />
break;<br />
<br />
To play a sound, use one of the following examples in a mouse callback. Note that "PathName" is the sub-folder name in the default FS ..\Sound folder, e.g., ..\Sound\Milviz. "SoundName" is for example push.wav:<br />
<br />
'''Play once:'''<br />
<br />
(GaugePlaySound)("sound\\PathName\\SoundName.wav","",0) ; <br />
<br />
'''Loop Sound:'''<br />
<br />
Looping a sound continuously require that you specify a "stop loop string name" and set the third parameter to 1 (0 = play once, 1 = loop continuously).<br />
<br />
if ( *rotartest == 2 ) <br />
{ (GaugePlaySound)("soundesdggearhorn.wav",geartest,1) ; } <br />
else { (GaugeStopSound)(geartest); }<br />
<br />
[[category:Aircraft Design]]<br />
[[category:Panel and Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=XML:_Macros_-_Set_Xpndr_Code&diff=8205XML: Macros - Set Xpndr Code2011-09-14T20:40:45Z<p>N4gix: </p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = false<br />
| FS2002 = false<br />
| FS2000 = false<br />
| FS98 = false<br />
}}<br />
<br />
'''== Transponder Set Macro =='''<br />
<br />
<Macro id="XPDR Set" Name="XPDRSet"><br />
<MacroValue><br />
@1 s0 10 % l0 10 /<br />
int 10 % 16 * + l0 100 /<br />
int 10 % 256 * + l0 1000 /<br />
int 4096 * + (&gt;K:XPNDR_SET) <br />
</MacroValue><br />
</Macro><br />
<br />
@XPDRSet(1200)<br />
<br />
@XPDRSet((L:XPDR_Code,number))<br />
<br />
[[category:Aircraft Design]]<br />
[[category:Panel and Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=XML:_Displaying_only_part_of_a_string_-_ssub&diff=8194XML: Displaying only part of a string - ssub2011-09-04T16:40:05Z<p>N4gix: </p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = false<br />
| FS2000 = false<br />
| FS98 = false<br />
}}<br />
<br />
== XML: Displaying only part of a string ==<br />
<br />
Thanks go to Paul EGLD (AVSIM Forum,18 March 2011) for pointing out this undocumented capability of the '''ssub''' string operator:<br />
<br />
'ABCDEFGHIJK' 0 4 ssub <br />
extracts characters 0 through 4 of the string. So,<br />
<br />
'ABCDEFGHIJK' 0 4 ssub <br />
results in 'ABCDE', and<br />
'ABCDEFGHIJK' 3 6 ssub <br />
results in 'DEFG'<br />
<br />
<br />
This compliments the SDK which states only<br />
<br />
'ab' 'abcde' ssub <br />
<br />
results in 'cde'<br />
[[Category:Aircraft Design]]<br />
[[Category:Panel and Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=XML:_Loop_Using_a_Goto&diff=8167XML: Loop Using a Goto2011-09-02T17:35:40Z<p>N4gix: </p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = false<br />
| XP10 = false <br />
| XP9 = false <br />
}}<br />
<br />
==XML: Loop Using a Goto==<br />
<br />
A Loop can be easy simulated using a [[g]] (goto) command which uses :''number_label'' for its target:<br />
<br />
<Update><br />
100 sp0 (* initialize, reg.0 = loop counter, 100 cycles *)<br />
:12345 (* loop label *)<br />
<br />
(* do something *)<br />
<br />
l0 -- s0 0 > if{ g12345 } (* next *)<br />
</Update><br />
<br />
An alternative to using the stack pointer operators (and makes the script more clear!) is this form:<br />
<br />
<Update><br />
100 (>L:LoopCounter,enum) (* initialize the counter's stack, 100 cycles *)<br />
:12345 (* loop label *)<br />
<br />
(* do something *)<br />
<br />
(L:LoopCounter,enum) 1 - (>L:LoopCounter,enum) (* decrement -1 *)<br />
(L:LoopCounter,enum) 0 > if{ g12345 } (* next *)<br />
</Update><br />
<br />
Notes:<br />
1. loop label can be any unique number<br />
2. This "loop" will execute completely on [[every]] gauge cycle (18Hz), so you may wish to "slow it down" by using a master timer.<br />
--[[User:N4gix|N4gix]] 13:35, 2 September 2011 (EDT)<br />
[[Category:Aircraft Design]]<br />
[[Category:Panel and Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=XML:_Loop_Using_a_Goto&diff=8166XML: Loop Using a Goto2011-09-02T17:33:40Z<p>N4gix: </p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = false<br />
| XP10 = false <br />
| XP9 = false <br />
}}<br />
<br />
==XML: Loop Using a Goto==<br />
<br />
A Loop can be easy simulated using a [[g]] (goto) command which uses :''number_label'' for its target:<br />
<br />
<Update><br />
100 sp0 (* initialize, reg.0 = loop counter, 100 cycles *)<br />
:12345 (* loop label *)<br />
<br />
(* do something *)<br />
<br />
l0 -- s0 0 > if{ g12345 } (* next *)<br />
</Update><br />
<br />
An alternative to using the stack pointer operators (and makes the script more clear!) is this form:<br />
<br />
<Update><br />
100 (>L:LoopCounter,enum) (* initialize the counter's stack, 100 cycles *)<br />
:12345 (* loop label *)<br />
<br />
(* do something *)<br />
<br />
(L:LoopCounter,enum) 1 - (>L:LoopCounter,enum) (* decrement -1 *)<br />
(L:LoopCounter,enum) 0 > if{ g12345 } (* next *)<br />
</Update><br />
<br />
Notes:<br />
1. loop label can be any unique number<br />
2. This "loop" will execute completely on [[every]] gauge cycle (18Hz), so you may wish to "slow it down" by using a master timer.<br />
[[Category:Aircraft Design]]<br />
[[Category:Panel and Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=XML:_Loop_Using_a_Goto&diff=8165XML: Loop Using a Goto2011-09-02T17:29:19Z<p>N4gix: New page: {{Infobox-Applicable-FSVersion | FSXI = false | FSXA = true | FSX = true | FS2004 = true | FS2002 = false | XP10 = false | XP9 = false }} ==XML: Loop Using a Goto== A Loop can be easy ...</p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = false<br />
| XP10 = false <br />
| XP9 = false <br />
}}<br />
<br />
==XML: Loop Using a Goto==<br />
<br />
A Loop can be easy simulated using a g (goto) command which uses :''number_label'' for its target:<br />
<br />
<Update><br />
100 sp0 (* initialize, reg.0 = loop counter, 100 cycles *)<br />
:12345 (* loop label *)<br />
<br />
(* do something *)<br />
<br />
l0 -- s0 0 > if{ g12345 } (* next *)<br />
</Update><br />
<br />
An alternative to using the stack pointer operators (and makes the script more clear!) is this form:<br />
<br />
<Update><br />
100 (>L:LoopCounter,enum) (* initialize the counter's stack, 100 cycles *)<br />
:12345 (* loop label *)<br />
<br />
(* do something *)<br />
<br />
(L:LoopCounter,enum) 1 - (>L:LoopCounter,enum) (* decrement -1 *)<br />
(L:LoopCounter,enum) 0 > if{ g12345 } (* next *)<br />
</Update><br />
<br />
Notes:<br />
1. loop label can be any unique number<br />
2. This "loop" will execute completely on [[every]] gauge cycle (18Hz), so you may wish to "slow it down" by using a master timer.<br />
[[Category:Aircraft Design]]<br />
[[Category:Panel and Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=XML:_Macros_-_Extracting_Digits&diff=8164XML: Macros - Extracting Digits2011-08-29T20:15:16Z<p>N4gix: </p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = false<br />
| FS2000 = unknown<br />
| FS98 = unknown<br />
}}<br />
''' Extract Digits Macro '''<br />
<br />
Quite frequently it is necessary to extract the ''nth'' digit of a number for any number of reasons.<br />
This XML Macro is very handy for the purpose, as it is "universal" and does not care what the number is...<br />
<br />
<Macro Name="ExtDigit"> <br />
@1 sp0 <br />
@3 0 > <br />
if{ l0 10 @3 pow * sp0 } <br />
l0 int 10 @2 pow % 10 @2 1 - 0 max pow / int <br />
</Macro><br />
<br />
@ExtDigit((ALGVar),nDigit,nDecimals)<br />
<br />
<br />
<br />
Where: <br />
(ALGVar) is the A,L or G var from where to extract the digit <br />
nDigit is the position of the digit to extract, starting from the right. <br />
nDecimals is the number of decimals to be included in the calcs. <br />
<br />
For instance<br />
for a value of 123.456789999999 <br />
<br />
@ExtDigit(lVar,1,0) means I want to extract the right most, discarding the decimals. It returns 3 <br />
@ExtDigit(lVar,2,0) returns 2 ; <br />
@ExtDigit(lVar,3,0) returns 1 and <br />
@ExtDigit(lVar,4,0) and up returns 0 <br />
<br />
using decimals: <br />
@ExtDigit(lVar,1,2) returns 5 <br />
@ExtDigit(lVar,2,2) returns 4 <br />
@ExtDigit(lVar,3,2) returns 3 <br />
@ExtDigit(lVar,4,2) returns 2 <br />
<br />
==NOTES:==<br />
<br />
1. '''@1 sp0''' - this s(tores) the value of @1 in register 0 (zero) and p(ops) the number from the stack<br />
2. '''l0''' - this is a lower case L, and not a 1 (one)! This means l(oad) the value from the 0 (zero) register<br />
3. '''@1 @2 @3''' - this is how an @Macro passes parameters. The @1 is the first parameter passed from it, etc. Used like so:<br />
@Macro1(Param1,Param2,Param3)<br />
@1 passes Param1 <br />
@2 passes Param2<br />
@3 passes Param3<br />
<br />
[[category:Aircraft Design]]<br />
[[category:Panel and Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=XML:_RNOR_Bug!&diff=8161XML: RNOR Bug!2011-08-29T15:42:21Z<p>N4gix: New page: {{Infobox-Applicable-FSVersion | FSXI = false | FSXA = true | FSX = true | FS2004 = true | FS2002 = true | XP10 = false | XP9 = false }} == XML: RNOR Bug! == There is a bug in the rno...</p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = true<br />
| XP10 = false <br />
| XP9 = false <br />
}}<br />
<br />
<br />
== XML: RNOR Bug! ==<br />
<br />
There is a bug in the rnor function that can be used in XML scripts (in both gauges and modeldef.xml).<br />
<br />
The expression 4.0 rnor should be 4.0, not 0.86 as FS returns. The problem is that the parsing engine is doing a mod by pi instead of 2 pi.<br />
<br />
What to do about this? I would suggest taking a number and converting to degress (using the rddg function), then using dnor (to normalize the number of degrees to a range between 0 and 360). and then convert back to radians using dgrd. Take care to mind your d's and r's and g's, though!<br />
<br />
[[Category:Aircraft Design]]<br />
[[Category:Panel and Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=Gauges:_Resource_Numbering&diff=7970Gauges: Resource Numbering2011-05-08T14:10:09Z<p>N4gix: </p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = true<br />
| FS2000 = unknown<br />
| FS98 = unknown<br />
}}<br />
<br />
Original Entry: Bill Leaming<br />
<br />
One of the major shortcomings of the SDK is that absolutely no mention is made of the requirements for resource numbers, including the various auto-offsets that the panel system will look for...<br />
<br />
Every bitmap used in a C gauge's .rc file requires a resource number allocated in the gauge's .h file.<br />
<br />
Each such resource allocation actually reserves '''FOUR''' resource numbers (in FSX) although only '''TWO''' in FS9 and earlier gauges.<br />
<br />
For example (using decimal numbers), the background image for a gauge might be 1000. Therefore, the following table applies:<br />
<br />
----<br />
<br />
1000 - background image<br />
<br />
1500 - optional hi-resolution version of background image<br />
<br />
41000 - optional night version of background image (FSX+ only)<br />
<br />
41500 - optional night version of hi-res background image (FSX+ only)<br />
<br />
----<br />
<br />
So, even if we don't provide any of the "optional" bitmaps, the '''resource numbers''' are already "reserved," hence unavailable for use by any other bitmaps!<br />
<br />
Some months ago, Jean-Luc suggested one possible scheme that at least has the virtue of being guaranteed "safe," since it takes into account all of the conditions placed by the panel system on resource numbers.<br />
<br />
I've since expanded the list to take advantage of the full dynamic range of allowable numbers. Below is the complete list of "Safe Ranges:"<br />
<br />
// 0x0100-0x02F3 0x0500-0x06F3 0x0900-0x0AF3<br />
<br />
// 0x1100-0x12F3 0x1500-0x16F3 0x1900-0x1AF3<br />
<br />
// 0x2100-0x22F3 0x2500-0x26F3 0x2900-0x2AF3<br />
<br />
// 0x3100-0x32F3 0x3500-0x36F3 0x3900-0x3AF3<br />
<br />
// 0x4100-0x42F3 0x4500-0x46F3 0x4900-0x4AF3<br />
<br />
// 0x5100-0x52F3 0x5500-0x56F3 0x5900-0x6AF3<br />
<br />
// 0x6100-0x62F3<br />
<br />
''NOTE: A handy site for hex-decimal-binary conversion is:<br />
http://flor.nl/dec2hex.html''<br />
<br />
It's critical to recognize that, even though the "old system" of dual-resolution bitmaps is no longer canon for FSX gauge code, because of the necessity for "backwards compatibility" the auto-offset of 500(decimal) in resource numbers is still respected.<br />
<br />
Of course, this is only one possible scheme, but it has the advantage of being rational and consistent. As long as you allocate resources within these ranges, you will '''NEVER''' run into a problem with contention. :)<br />
<br />
The complete range of allowable resources is of course 0x0000 to 0xffff. The reason the above table stops at 0x62f3 is because in FSX, if one takes into account the 40,000 (decimal) auto-offset that the night time bitmap "swap code" looks for, then the highest possible number would be 0x63bf, which of course one could use, but it "breaks" the consistency of the tabular range scheme. ;)<br />
<br />
Aside from which, with 9,500 allowable id's, I cannot conceive of '''any''' multigauge cluster that would come close to exhausting the list of numbers provided by restricting one's choices to the table's range...<br />
<br />
...at least not one which would actually load and run efficiently!<br />
<br />
[[category:Aircraft Design]]<br />
[[category:Panel & Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=GPS:_Missing_Airspace_Options&diff=7963GPS: Missing Airspace Options2011-04-13T17:57:22Z<p>N4gix: /* '''GPS: Missing Airspace Options''' */</p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = false<br />
| FS2000 = false<br />
| FS98 = false<br />
}}<br />
<br />
==='''GPS: Missing Airspace Options'''===<br />
<br />
I highly suggest visitors to this Wiki entry to refer to this most excellent guide:<br />
<br />
'''BlackBox Website - GPS Guidebook'''[http://www.robbiemcelrath.com/blackbox/?guide]<br />
<br />
The tabular data previously listed on this entry has proven to be incomplete and or incorrect...<br />
<br />
[[Category:Aircraft Design]]<br />
[[Category:Panel & Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=GPS:_Missing_Airspace_Options&diff=7962GPS: Missing Airspace Options2011-04-13T17:56:04Z<p>N4gix: /* '''GPS: Missing Airspace Options''' */</p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = false<br />
| FS2000 = false<br />
| FS98 = false<br />
}}<br />
<br />
==='''GPS: Missing Airspace Options'''===<br />
<br />
I highly suggest visitors to this Wiki entry to refer to this most excellent guide:<br />
<br />
'''BlackBox Website - GPS Guidebook'''[http://www.robbiemcelrath.com/blackbox/?guide]<br />
[[Category:Aircraft Design]]<br />
[[Category:Panel & Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=GPS:_Missing_Airspace_Options&diff=7961GPS: Missing Airspace Options2011-04-12T17:22:21Z<p>N4gix: /* '''GPS: Missing Airspace Options''' */</p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = false<br />
| FS2000 = false<br />
| FS98 = false<br />
}}<br />
<br />
==='''GPS: Missing Airspace Options'''===<br />
<br />
I highly suggest visitors to this Wiki entry to refer to this most excellent guide:<br />
<br />
'''BlackBox Website - GPS Guidebook'''[http://www.robbiemcelrath.com/blackbox/?guide]<br />
<br />
Here is a list of known* input parameters for this token:<br />
<br />
-1 - default<br />
0 - NONE = 0<br />
8 - CENTER = 1<br />
16 - CLASS_A = 2<br />
32 - CLASS_B = 3<br />
64 - CLASS_C = 4<br />
128 - CLASS_D = 5<br />
264 - CLASS_E = 6<br />
528 - CLASS_F = 7<br />
1024 - CLASS_G = 8<br />
2048 - TOWER = 9<br />
4096 - CLEARANCE = 10<br />
8192 - GROUND = 11<br />
16384 - DEPARTURE = 12<br />
32768 - APPROACH = 13<br />
65536 - MOA = 14<br />
131072 - RESTRICTED = 15<br />
262144 - PROHIBITED = 16<br />
524288 - WARNING = 17<br />
1048576 - ALERT = 18<br />
2097152 - DANGER = 19<br />
4194304 - NATIONAL_PARK = 20<br />
8388608 - MODE_C = 21<br />
16777216 - RADAR = 22<br />
33554432 - TRAINING = 23 <br />
<br />
''* NOTA BENE: This is a work in progress and may (probably does) contain errors of ommission or commission!''<br />
<br />
You can create Macro entries for use in your gauge to display selected airspaces by summing the input parameters for each type:<br />
<br />
B, C, D, MOA, RESTRICTED, PROHIBITED, WARNING, ALERT, DANGER, MODE_C, RADAR, TRAINING<br />
8, 16,32, 64, 128, 256, 512 1024 2048 4096 8192 16384<br />
<Macro Name="DisplayedAirspaces">0xEFC038</Macro><br />
<br />
MOA, RESTRICTED, PROHIBITED, WARNING, ALERT, DANGER<br />
64 128 256 512 1024 2048<br />
<Macro Name="AlwaysDisplayedAirspaces">0x0FC000</Macro><br />
<br />
[[Category:Aircraft Design]]<br />
[[Category:Panel & Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=GPS:_Missing_Airspace_Options&diff=7960GPS: Missing Airspace Options2011-04-12T17:18:37Z<p>N4gix: /* '''GPS: Missing Airspace Options''' */</p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = false<br />
| FS2000 = false<br />
| FS98 = false<br />
}}<br />
<br />
==='''GPS: Missing Airspace Options'''===<br />
<br />
I have found a very curious OMISSION in the FSX SDK on the XML Map parameters...<br />
<br />
ObjectDetailLayerAirspaces <br />
-1 = Default<br />
0 = Draw nothing <br />
<br />
This is woefully incomplete! Here is a list of known* input parameters for this token:<br />
<br />
-1 - default<br />
0 - NONE = 0<br />
8 - CENTER = 1<br />
16 - CLASS_A = 2<br />
32 - CLASS_B = 3<br />
64 - CLASS_C = 4<br />
128 - CLASS_D = 5<br />
264 - CLASS_E = 6<br />
528 - CLASS_F = 7<br />
1024 - CLASS_G = 8<br />
2048 - TOWER = 9<br />
4096 - CLEARANCE = 10<br />
8192 - GROUND = 11<br />
16384 - DEPARTURE = 12<br />
32768 - APPROACH = 13<br />
65536 - MOA = 14<br />
131072 - RESTRICTED = 15<br />
262144 - PROHIBITED = 16<br />
524288 - WARNING = 17<br />
1048576 - ALERT = 18<br />
2097152 - DANGER = 19<br />
4194304 - NATIONAL_PARK = 20<br />
8388608 - MODE_C = 21<br />
16777216 - RADAR = 22<br />
33554432 - TRAINING = 23 <br />
<br />
''* NOTA BENE: This is a work in progress and may (probably does) contain errors of ommission or commission!''<br />
<br />
You can create Macro entries for use in your gauge to display selected airspaces by summing the input parameters for each type:<br />
<br />
B, C, D, MOA, RESTRICTED, PROHIBITED, WARNING, ALERT, DANGER, MODE_C, RADAR, TRAINING<br />
8, 16,32, 64, 128, 256, 512 1024 2048 4096 8192 16384<br />
<Macro Name="DisplayedAirspaces">0xEFC038</Macro><br />
<br />
MOA, RESTRICTED, PROHIBITED, WARNING, ALERT, DANGER<br />
64 128 256 512 1024 2048<br />
<Macro Name="AlwaysDisplayedAirspaces">0x0FC000</Macro><br />
<br />
[[Category:Aircraft Design]]<br />
[[Category:Panel & Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=GPS:_Missing_Airspace_Options&diff=7959GPS: Missing Airspace Options2011-04-12T17:17:46Z<p>N4gix: </p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = false<br />
| FS2000 = false<br />
| FS98 = false<br />
}}<br />
<br />
==='''GPS: Missing Airspace Options'''===<br />
<br />
I have found a very curious OMISSION in the FSX SDK on the XML Map parameters...<br />
<br />
ObjectDetailLayerAirspaces <br />
-1 = Default<br />
0 = Draw nothing <br />
<br />
This is woefully incomplete! Here is a list of known* input parameters for this token:<br />
<br />
-1 - default<br />
0 - NONE = 0<br />
8 - CENTER = 1<br />
16 - CLASS_A = 2<br />
32 - CLASS_B = 3<br />
64 - CLASS_C = 4<br />
128 - CLASS_D = 5<br />
264 - CLASS_E = 6<br />
528 - CLASS_F = 7<br />
1024 - CLASS_G = 8<br />
2048 - TOWER = 9<br />
4096 - CLEARANCE = 10<br />
8192 - GROUND = 11<br />
16384 - DEPARTURE = 12<br />
32768 - APPROACH = 13<br />
65536 - MOA = 14<br />
131072 - RESTRICTED = 15<br />
262144 - PROHIBITED = 16<br />
524288 - WARNING = 17<br />
1048576 - ALERT = 18<br />
2097152 - DANGER = 19<br />
4194304 - NATIONAL_PARK = 20<br />
8388608 - MODE_C = 21<br />
16777216 - RADAR = 22<br />
33554432 - TRAINING = 23 <br />
<br />
''* NOTA BENE: This is a work in progress and may (probably does) contain errors of ommission or commission!''<br />
You can create Macro entries for use in your gauge to display selected airspaces by summing the input parameters for each type:<br />
<br />
B, C, D, MOA, RESTRICTED, PROHIBITED, WARNING, ALERT, DANGER, MODE_C, RADAR, TRAINING<br />
8, 16,32, 64, 128, 256, 512 1024 2048 4096 8192 16384<br />
<Macro Name="DisplayedAirspaces">0xEFC038</Macro><br />
<br />
MOA, RESTRICTED, PROHIBITED, WARNING, ALERT, DANGER<br />
64 128 256 512 1024 2048<br />
<Macro Name="AlwaysDisplayedAirspaces">0x0FC000</Macro><br />
<br />
[[Category:Aircraft Design]]<br />
[[Category:Panel & Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=GPS:_Missing_Airspace_Options&diff=7958GPS: Missing Airspace Options2011-04-12T17:00:07Z<p>N4gix: /* '''GPS: Missing Airspace Options''' */</p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = false<br />
| FS2000 = false<br />
| FS98 = false<br />
}}<br />
<br />
==='''GPS: Missing Airspace Options'''===<br />
<br />
I have found a very curious OMISSION in the FSX SDK on the XML Map parameters...<br />
<br />
ObjectDetailLayerAirspaces <br />
-1 = Default<br />
0 = Draw nothing <br />
<br />
This is woefully incomplete! Here is a list of known input parameters for this token:<br />
<br />
-1 - default<br />
0 - Draw Nothing<br />
8 - Class B<br />
16 - Class C<br />
32 - Class D<br />
64 - MOA<br />
128 - Restricted<br />
256 - Prohibited<br />
512 - Warning<br />
1024 - Alert<br />
2048 - Danger<br />
4096 - Mode C<br />
8192 - Radar<br />
16384 - Training<br />
<br />
You can create Macro entries for use in your gauge to display selected airspaces by summing the input parameters for each type:<br />
<br />
B, C, D, MOA, RESTRICTED, PROHIBITED, WARNING, ALERT, DANGER, MODE_C, RADAR, TRAINING<br />
8, 16,32, 64, 128, 256, 512 1024 2048 4096 8192 16384<br />
<Macro Name="DisplayedAirspaces">0xEFC038</Macro><br />
<br />
MOA, RESTRICTED, PROHIBITED, WARNING, ALERT, DANGER<br />
64 128 256 512 1024 2048<br />
<Macro Name="AlwaysDisplayedAirspaces">0x0FC000</Macro><br />
<br />
[[Category:Aircraft Design]]<br />
[[Category:Panel & Gauge Design]]</div>N4gixhttp://www.fsdeveloper.com/wiki/index.php?title=GPS:_Missing_Airspace_Options&diff=7957GPS: Missing Airspace Options2011-04-12T16:33:00Z<p>N4gix: </p>
<hr />
<div>{{Infobox-Applicable-FSVersion<br />
| FSXI = false<br />
| FSXA = true<br />
| FSX = true<br />
| FS2004 = true<br />
| FS2002 = false<br />
| FS2000 = false<br />
| FS98 = false<br />
}}<br />
<br />
==='''GPS: Missing Airspace Options'''===<br />
<br />
I have found a very curious OMISSION in the FSX SDK on the XML Map parameters...<br />
<br />
ObjectDetailLayerAirspaces <br />
-1 = Default<br />
0 = Draw nothing <br />
<br />
This is woefully incomplete! Here is a list of known input parameters for this token:<br />
<br />
-1 - default<br />
0 - Draw Nothing<br />
8 - Class B<br />
16 - Class C<br />
32 - Class D<br />
64 - MOA<br />
128 - Restricted<br />
256 - Prohibited<br />
512 - Warning<br />
1024 - Alert<br />
2048 - Danger<br />
4096 - Mode C<br />
8192 - Radar<br />
16384 - Training<br />
<br />
You can create Macro entries for use in your gauge to display selected airspaces by summing the input parameters for each type:<br />
<br />
B, C, D, MOA, RESTRICTED, PROHIBITED, WARNING, ALERT, DANGER, MODE_C, RADAR, TRAINING<br />
8, 16,32, 64, 128, 256, 512 1024 2048 4096 8192 16384<br />
<Macro Name="DisplayedAirspaces">0x7FF800</Macro><br />
<br />
MOA, RESTRICTED, PROHIBITED, WARNING, ALERT, DANGER<br />
64 128 256 512 1024 2048<br />
<Macro Name="AlwaysDisplayedAirspaces">0x0FC000</Macro><br />
<br />
[[Category:Aircraft Design]]<br />
[[Category:Panel & Gauge Design]]</div>N4gix