Pat

Please help, thanks

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.

ich bin ganz neu in diesem Forum und hoffe auf Hilfe von euch. Leider nur in Deutsch. 

Ich nutze noch den alten fs9 und das noch sehr gerne

Ich möchte 2 Variablen addieren und einer neuen Variablen zuweisen. Hier mein erster Versuch der leider als Ergebnis 0 anzeigt. Wo liegt der Fehler

<Gauge Name="fuel_Test" Version="1.0">
<Element>
<Image Name="fuel.bmp" ImageSizes="370,160,370,160"/>
 
 <!--  Summe der MAINTANKS -->
               <Element>
                    <Select>
                    <Value>          
    (L:AUX,Gallons)==(A:FUEL TANK RIGHT AUX QUANTITY, gallons) (A:FUEL TANK LEFT AUX QUANTITY, gallons)  +  
     
                    </Value>
                    </Select>
               </Element>

 <!--  Main and Center Quantity -->
            <Element>
             
               <Element>
                <Position X="200" Y="64"/>
                <Text X="86" Y="25" Bright="Yes" Length="5" Font="Arial" Color="%('red' 'Orange' (L:low fuel left,bool) ?)" Adjust="Right" VerticalAdjust="Center" Multiline="No">
            <String>%((L:AUX, gallons))  %!3d!</String>
                    </Text>
               </Element>              
            </Element>
 </Element>
</Gauge>

Auf Antworten freut sich Wolfgang near EDDS

Normal lights:

Problem lights at CARGO modification:

many years ago when the A340 Airbus was designed I noticed that British Airways had no A340's.

At the time I was running Windows XP and later Windows 7 and now running Windows 10

So I enquired whether anybody was able to do a Repaint of the A340 In british Airways livery and 

hey presto somebody, these names from the A340 file created for me:- 

(Designer: Herve Maxime DONGMO - Member: SIMUBUILD FREEWARE GROUP
Livery Artist: XUDEVA IRRIBARRA  Cockpit Design: SIMUBUILD FREEWARE GROUP FLIGHTDECK ENGINEERING DEPARMTNET).

Iv'e had many Years flying this great Aircraft, not so good with Landings, although they say any Landing is a good one. 

However, with the Increasing upgrades of Microsoft Flight Simulator through 98 2002, 2004 FS9and FSX and many changes 
since. 

Having come back to Flight Simulator recently I find I cannot fly this A340-600 anymore because the Gauges/Cockpit have 
lots of things missing.

Can somebody please possibly advise me what to do to get this A340 working again please.

Have a nice Christmas everybody!

Paul.

default_vertical_speed= say 600, (gives the "default" setting) while something like....

max_vertical_speed=  say 3000 (gives the MAXIMUM and MINIMUM settings).

I have not been able to come up with a way of using XML coding to limit the maximum vertical speed.

Is it possible??

Manuel.

The MSFS20 SDK indicates that templated panels can be created for use as mouse interactive gauges, which is what I need. I would like to have a small rectangular panel that contains the basic knobs and buttons for the MFD ( HDG, ALT and Range in/out knob and 5 AP buttons as a minimum) , all interactive to MFD events and where the panel can be dragged (like the ATC window etc) onto the 10" monitor and positioned above or below the MFD pop-up panel.  My question is simply...  Can this type of gauge be created using the templated system and if so, can the end result then be dragged to a 2nd monitor or not, or is it restricted to being within the primary window.?

I am running a circa 2011 Flyit version of the B206 with a hardware replica of the collective and instrument panel. No mixture control naturally with the turbine but a fuel valve as per the real B206. If the fuel valve is turned on, the engine N2 and Nr will start without pressing the start button and the throttle at cutoff. When the start button is pressed and held, the N1 (Gas Producer) accelerates to peak at 20% and even with the throttle opened to the flight idle detent, the engine will not run until the fuel valve is then turned on.

The correct start sequence should be;

Throttle at idle cutoff, fuel valve on, fuel pumps on, press and hold start button and at 15% N1 open the throttle to the flight idle detent. At this point the engine ignites and accelerates to where the starter is released at 58% N1. Then engine now being at self sustaining speed will increase to a N1 flight idle speed of around 61-63%.

The correct shutdown procedure should be;

Throttle reduced to the flight idle detent, to shut the engine down the detent button is pressed and the throttle rolled off to the cutoff position where both the N1 and N2 (and to a slower extent the Nr) slowly return to zero.

The fuel valve in the real aircraft plays no part in controlling the start except that it opens the fuel supply to the engine's fuel control unit (FCU) which will then meter the fuel to the engine by the throttle during starting and shutdown, and by the power turbine governor (PTG) during engine running.

As this is now 2023, is there a Bell 206 aircraft.cfg or .air that more accurately mimics the correct start/shutdown sequences?

Thanks

Geoff

Rhys 

I guess my issue with it is, I am not sure I am fully "installed" correctly, to the point I have tried almost everything I know, to make it an "Add-On" in all forms like DLL.XML etc., and still nothing.

As I look at the TrafficRadarXML code, it seems that C:fs9Traffic... is not working at all.  Sure, the TrafficRadar.DLL is in my \Modules folder and if I add a display like  GPH fuel rate (digital display) to the screen, it's there but all I have is a "range" of zero, no control at all, no traffic displays.   It's a blank screen with the grid and 0.0 nm, that's all.

This is a very simple, but effective traffic "fish-finder" as the local pilot's call it on VHF, I'd like to have one in my General Aviation aircraft.

Does anyone know if there is more to my installation to make C:fs9Traffic routines run on FSX?   

I feel I have missed something in my FSX SP2 system that makes it happy to run fs9 anything more than C:fs9GPS...

ThankYou,  N3BXL

0, 0, 1, 1, how will that appear visually in the cockpit?

Is that actually an invisible gauge?

I have the full suite of 727 Captain variants (Base Pack and the 3 expansion packs that complement it), all with the latest version of the 727 Captain released which is 2.7. All are installed within FSX Accelerator.

My problem, is only with all of the 200 variants (both passenger and Freighter, the 100 variants are working just fine).

The issue I have is that as soon as I start to taxi on the ground or even use the FSX pushback option at any airport with any of the 200 variants, the aircraft starts to bounce and jump about quite dramatically, even turning vertical in the air and as a result the aircraft is totally unusable. 

I have worked with reducing the scenery mesh complexity, right down to the minimum, however the same thing happens, but as I say only with the 727-200 variant.

Has anyone on this forum any suggestions as to why this may be happening and how I can fix this issue?

Any help what so ever would be appreciated as the captain sim forum has not responded to my posts relating to this issue and I can’t understand why.

Kind Regards

I can do basic wiring and electronics, so if there are some kits or instructions on how to do this, please let me know

I am a FSX user and fly only the B737-800 default, no 3rd party aircraft. So I build myself a MCP based specific on the B737-800 default MCP (auto pilot panel) and use FSUIPC to configure it via Mobiflight. All is working fine. But on the default B737-800 MCP there is button VOR LOC. When hover with the mouse over VOR LOC button the help tip says "Nav Hold switch"

So I am looking for FSUIPC Event ID or Offset. I did search through FSUIPC documentation but could not find anything not anywhere web wise. 

I would love to have this upgrade. I do not know it it is illegal in this case to ask if somebody could help me with a copy of the highest resolution blue panels . The reason I want this is to ease my old eyes with better readable labels on the panels.  If not possible, is there a way I can "overhaul"  them myself  ? I have done this a few times in Xplane but I am rather new in P3D and files seem to be scattered all over the  filesystem. 

This plane is sold for use in P3DV4, but I use the plane in P3DV5.3 and at least upto now it seems to work perfect. This amazing plane has so much features that it will take a while before I tried them all. Together with the PMDG DC-6 and A2A Connie my most used plane.