Gauges and Extensions

SPAD.neXt generally supports ESP compatible gauges
Gauges loaded into SPAD.neXt have to match this schema: Gauge.xsd​
RPN Expressions have to be ESP RPN conform!
SPAD.neXt is generally Saitek/Logitech compatible, but it has NOT implemented Saitek Bugs:
Saitek gauges require a Non-Space-Character before a closing brace "}" e.g. in if{ statements:
if{ someexpression %} els{ someotherexpression %}

SPAD.neXt does not support this. You will need to alter the gauge accordingly and remove the %
Extensions for (RPN) Expressions
To access any other Data than Simconnect (FSX / P3D / MSFS) use the Dataref-Tag as it is used by SPAD.neXt. Those Datarefs have always the format 
RPN Expressions: (PROVIDER:DATREFNAME) or (PROVIDER:DATREFNAME,unit)
SPAD Expressions: [PROVIDER:DATREFNAME] or [PROVIDER:DATREFNAME,unit]
If the requested unit does not match the datarefs default unit, SPAD.neXt will automatically convert it to the requested unit, if such a conversion is known
To access LVAR use the prefix LVAR: (FSX/P3D/MSFS only)
(LVAR:AB_MCP_AP_ON, Number) 
To access FSUIPC Offsets use the Prefix FSUIPC:
(FSUIPC:0000:0AB2, Number)
You can copy a dataref from the data browser to you cilpboard, by selecting it and pressing CTRL-C or the OK Button.
Other examples:
PMDG (P3D):
(PMDG737:1000:010E) = Glareshield.Mode Control Panel.Altitude
ETS2
(SCS:scs/truck/fuel)

X-Plane:
(XPLANE:sim/cockpit2/annunciators/afterburner)

Local Variables access
LOCAL:VARNAME
Local var , will not be saved, will be initialized to 0 if it does not exist already

DEVICE:VARNAME
Local var, Value will be DEVICE-specific, and will be initialized to the saved value again when the gauge is loaded onto that device. (Same varibale has diffrent value son different FIP devices)
PROFILE:VARNAME 
Local var , Value will be saved to the PROFILE , and will be initialized to the saved value again when the profile is loaded

Additional Time-Variables
All time variables as shown here can also be used with the "LOCAL:"-Prefix to retrieve the local computer time as UTC/Local.
To get the local computer hour you would use
(LOCAL:LOCAL TIME,Hours)
Dynamic Images
The Image-Tag supports the following extensions for dynamically changing images:
Attribute "Dynamic"
Sub-tag "Value"
See: Example for dynamic images
Dynamic Labels
In order to show numbers on the gauge, SPAD.neXt support an additional sub element: <Label>
See: Dynamic Labels
Extended Button Configuration
To assign a function to a FIP button other than a SimConnect Control Event, you can deliver an extended button configuration together with your gauge.
Just configure the button as desired within SPAD.neXt, and then export the button configuration (copy to clipboard and save to a file) to a file BUTTONNAME.bml in the gauge main directory.
The following buttons are supported:
FIP_BUTTON_S1 - FIP_BUTTON_S6 , FIP_RIGHTDIAL, FIP_LEFTDIAL, FIP_BUTTON_PAGEUP, FIP_BUTTON_PAGEDOWN
GaugeSettings
SPAD.neXt also defines an additional tag for providing settings in a gauge:
<Gauge>
..
..
..
  <GaugeSettings .....>
  </GaugeSettings>
</Gauge>
​
SPAD.neXt GaugeSettings Sample
Event programming - Previous
Untitled
Next - Extending and API's
C# Scripting Interface
Last modified 1yr ago