CaptSwan

According to the "Simulation Variables" chart for the Flight Simulator X SDK, the aircraft variabiable you need to find is (A:PITOT HEAT, bool), specifying that it's an aircraft variable A:, the pitot heat variable: PITOT HEAT, and that the variable type is boolean, only having two states known as 0, off, or false and 1, on, or true. Setting G: or L: (Gauge or Local) variables to put the current (A:PITOT HEAT, bool) value in is up to you as to what you call them. Hope that helps.

Hello. I am a legally blind one-eyed partially deaf flightsimmer who is trying to create in essence a "talking aircraft" to call out airspeeds, altitudes, and other instrument readouts as I cannot see the instrument displays while in the sitting up "flying" position. Only way I can look at the displays beyond a very brief glance is to put the "aircraft" on "autopilot" and then kneel and get "nose to nose" with the displays so I can see them. I have been studying 2 different xml files -- one associated with an A320 GPWS altitude callouts application and the other associated with a V-Speeds Callout application. Both of these make use of the dsd_fsx_xml_sound guage application by Doug Dawson. The GPWS altitude callouts uses the following approach for it's sound "triggers" with regard to each of the callout altitudes: The first line says "If aircraft is in the Target Altitude's trigger range and Target_Altitude_Played is 0 (false) then put 1 in Target_Altitude trigger": 2500 2480 @Altitude rng (L:Target_Altitude_Played, bool) ! andif{ 1 (>L:Target_Altitude, number) } The second line says "If Target_Altitude_Trigger is 1 then put 1 (true) in Target_Altitude_Played": (L:Target_Altitude, number) 1 == if{ 1 (>L:Target_Altitude_Played,bool) } The third line says "If aircraft is outside the 200-foot range surrounding the Target_Altitude and if Target_Altitude_Played is 1 (true) then set Target_Altitude_Played to 0 (false): 2400 2600 @Altitude rng ! (L:Target_Altitude_Played, bool) andif{ 0 (>L:Target_Altitude_Played, bool) } XML operates in "Reverse Polish Notation. The "@Altitude" involes an "Altitude" macro whose macro value is setto both A:RADIO HEIGHT, feet and A:STATIC CG TO GROUND, feet. My first approach was to try to apply the GPWS callouts author's approach to detect certain airspeeds and to call them out. When I first tried the app for the first time after doing the basic syntax debugging of it, my "1000 AGL. Set Climb Power. Flaps 1" callout kept playing over and over again nonstop even the "aircraft" was still sitting at the "gate". My "V2+15" callout did the same thing starting shortly after liftoff from the runway. So I had to deactivate the language for these callouts and none of the other triggers are working. The "aircraft" is accelerating right through the v-speed callouts without their "triggers" being "tripped" and the calls are not working. Thinking that maybe the two files running the samd dsd_fsx_xml_sound guage at the same time was resulting in the original GPWS file working okay but my IASCalls_Control file not working at all -- I thought maybe the first one is preventing the second from running. So I "commented out" the invocation of thw 2nd one and tried putting only the VR callout in the original GPWS file. That hasn't worked either. When I tried tapping into the A:TOTAL VELOCITY variable instead of the A:AIRSPEED INDICATED variable, that caused the Vr callout to play over and over again nonstop. So I switched back to the A:AIRSPEED INDICATED and added to the IASpeed macro value the A:AIRPEED SELECT INDICATED OR TRUE variable to the A:AIRSPEED INDICATED variable already in the macro value. So then I tried the other approach -- the one used by the VSpeed Callouts author: <Element> <Element><Select> 160 (&gt;G:Var3) </Select></Element> </Element> <Element> <Element><Select> (A:AIRSPEED INDICATED, knots) &gt;(G:Var3) if{ 1 (&gt;L:IASCall_VR, enum) (This line puts 1 in the IASCall_VR trigger variable) 4 (&gt;G:Sound_Played) (This number replaces the 3 with 4 to prevent the 3rd sound VR from playing twice) } </Select></Element> </Element> The "aircraft" is still going through each takeoff roll and sailing right past the VR speed 160 knots without playing the sound at all. So -- I've tried two different approaches to this problem. Why is neither approafch working? Thank you.