fxsttcb

Try this, Rob B is right, I had to nest text elements in a few gauges so they would work. <Element> <Position X="8" Y="8" /> <Select> <Value>(L:Valt, number)</Value> <Case Value="0"> <Image Name="none.bmp" /> </Case> <Case Value="1"> <Image Name="nav1.bmp" /> </Case> </Select> <Element> <Position X="8" Y="8" /> <Visible>(L:Valt, number) 2 == </Visible> <Text X="42" Y="12" Bright="Yes" Length="5" Font="Arial" Color="#00FF00" Adjust="Right" VerticalAdjust="Center" Multiline="No" Fixed="No"> <String>NAV 2</String> </Text> </Element> </Element> I have plenty of text gauges without Font size being declared. They self adjust to the x, y, length descriptors...Don

I created an extra element(more if I want needles and digits lit differently) for each gauge.The Element calls a bitmap that has only the areas I want lit only when a specific "switch" is on.Tag it Luminous=yes Bright=yes.The panel.cfg Luminous line controls the color of the light. [Color]Day=255,255,255Night=225,225,225Luminous=200,75,75 With custom switches(L:var) and visibility statements the sky is truly the limit.The SDK has most of the L:var info. Look at other gauges for visibility examples...Don

I think the only way to easily accomplish the same gauge with 2 different color schemes is to copy and rename the original.Edit the "new" gauge's bitmaps.You will now have 2 identical gauges with diff colors.Use the new gauge name in the panel.cfg. Might be worth a try..Don

Though the following isn't a copy/paste, the element is from a working gauge I made, <Element> <Position X="30" Y="44" /> <Visible>(A:FUEL TOTAL QUANTITY, gallons) 175 < (A:CIRCUIT GENERAL PANEL ON, bool) and</Visible> <Text X="96" Y="30" Bright="yes" Length="8" Font="quartz" Color="0xFFA06B" Adjust="Center" VerticalAdjust="Center" Fixed="no"> <String>LOW_FUEL</String> </Text> </Element> It is a "Total" fuel warning, you will have to change the variable and the string to what you want.You will also have to position it for your background, and designate the level, in gallons, in place of "175" above.Change the font and color also, to your preference.The SDK lists the variables available and you can also change to a "percent" variable to make it universal. ..Don

I think Ed/Ted Cook has had success using keyboard input to .xml gaugesI found this snip in my archives and a note to myself to find "Strobe Switch" in the Avsim forum for his actual usage. Unfortunately I didn't save a link to the thread. <Keys><On Key="Keyboard Key">(>K:Variable Event) </On></Keys> I haven't tried it, so don't know if it works.Along with the snip was a partial list of key numbers compiled by Rob Barendregt and this note: A list of all Windows key codes can be found in Peter Dowson's FSUIPC zipped package in the FSUIPC for Advanced Users.doc, available from http://www.schiratti.com/dowson.html ...Don

I think you are looking for windows priority. Initially they are drawn in the order they are listed if "visible=1":[Window Titles]window00=Main PanelWindow01=Radio PanelWindow02=GPSwindow03=Throttle Quadrantetc., etc. You can also specify their priority according to zorder=xx by including it in the window description: [Window00]file_1024=bombardier_CRJ700_panel_background.bmpfile_1024_night=bombardier_CRJ700_panel_background_night.bmpsize_mm=1024position=7visible=1ident=MAIN_PANELzorder=00 The zorder=00 is the lowest priority and successive numbers will remain "On Top" of any lower number.To reply without quoting use the reply button at the bottom of the thread, not the one with the balloon attached...Don

Sorry I wasn't much help. It takes a lot of changing things around and testing. If its worth it to you, put the PMDG in and Fly it and Look at it. Spend some time examining the flight dynamics in all phases of flight. Make note of everything that is wrong, lights, contact Points, flight handling, everything. Now that you have changed the flaps and the autopilot sections a few times, you know how do the same thing with the contact points, lights etc. Don't be afraid to experiment! You can always change it back. I make a copy of every change that worked and name it in order, aircraft1A, aircraft1B etc, if it doesn't work I can go back to the last one, even years later. I also make a list of changes that didn't work, so I don't make the same mistakes twice. It can get really tedious, be patient. Let me know how it goes...Good Luck...Don

When you put the PMDG aircraft.cfg in the plane it messed up the contact points etc, but the AP worked.I think the PMDG AP is embedded in [AFDSAuth].Replace all of the POSKY [autopilot] section with this:[autopilot]autopilot_available = 0autothrottle_available = 0default_pitch_mode=0default_bank_mode=0[AFDSAuth]---BEGIN SHA1---036904E3202DA70E950ECD29714706B66084BC23A7AD0E6840A79704D01EBE667B3A06A29E8CE223CC8E0E0E00717C0D7D2EC4E37C4AC61B1189982389660B4C70302304529E1DEE7D67D618CE8C91239234051C80E46202BD0E93847B42D65EA1887523---END SHA1---Put the flaps back to POSKYchange in sections [flaps.0] and [flaps.1] "only"from: flaps-position.6 = 30 // degreesto: flaps-position.6 = 33 // degreesWe'll get there sooner or later!...Don

Lets do the Flaps First. Open the POSKY aircraft.cfg (the one you are going to use)REMOVE THIS:[flaps.0]type = 1 // 1 - tail, 2 - leadspan-outboard = 0.8 // 0.0 .. 1.0extending-time = 25 // secondsflaps-position.0 = 0 // degreesflaps-position.1 = 5 // degreesflaps-position.2 = 10 // degreesflaps-position.3 = 15 // degreesflaps-position.4 = 20 // degreesflaps-position.5 = 25 // degreesflaps-position.6 = 30 // degreesdamaging-speed = 200 // KIASblowout-speed = 250 // KIASlift_scalar = 0.28drag_scalar = 0.40pitch_scalar= 0.40system_type = 1 //Hydraulic[flaps.1]type = 1 // 1 - tail, 2 - leadspan-outboard = 0.2 // 0.0 .. 1.0extending-time = 25 // secondsflaps-position.0 = 0 // degreesflaps-position.1 = 5 // degreesflaps-position.2 = 10 // degreesflaps-position.3 = 15 // degreesflaps-position.4 = 20 // degreesflaps-position.5 = 25 // degreesflaps-position.6 = 30 // degreesdamaging-speed = 200 // KIASblowout-speed = 250 // KIASlift_scalar = 0.28drag_scalar = 0.40pitch_scalar= 0.40system_type = 1 //Hydraulic[flaps.2]type = 2 // 1 - tail, 2 - leadspan-outboard = 0.8 // 0.0 .. 1.0extending-time = 12 // secondsflaps-position.0 = 0 // degreesflaps-position.1 = 20.0 // degreesdamaging-speed = 250 // KIASblowout-speed = 300 // KIASlift_scalar = 0.28drag_scalar = 0.40pitch_scalar= 0.40system_type = 1 //Hydraulic[flaps.3]type = 2 // 1 - tail, 2 - leadspan-outboard = 0.5 // 0.0 .. 1.0extending-time = 12 // secondsflaps-position.0 = 0 // degreesflaps-position.1 = 20 // degreesdamaging-speed = 250 // KIASblowout-speed = 300 // KIASlift_scalar = 0.28drag_scalar = 0.40pitch_scalar= 0.40system_type = 1 //Hydraulic[flaps.4]type = 2 // 1 - tail, 2 - leadspan-outboard = 0.2 // 0.0 .. 1.0extending-time = 12 // secondsflaps-position.0 = 0 // degreesflaps-position.1 = 10 // degreesflaps-position.2 = 20.0 // degreesdamaging-speed = 250 // KIASblowout-speed = 300 // KIASlift_scalar = 0.28drag_scalar = 0.40pitch_scalar= 0.40system_type = 1 //HydraulicPASTE THIS in its place:[flaps.0]type = 1 // Trailing edgespan-outboard = 0.7 // 0.0 .. 1.0extending-time = 60 // secondsflaps-position.0 = 0 // pseudo-degreesflaps-position.1 = 0.00,280 // 1 - no TEflaps-position.2 = 25.0,260 // 5flaps-position.3 = 27.5,240 // 10flaps-position.4 = 30.0,230 // 20flaps-position.5 = 31.5,205 // 25flaps-position.6 = 33.0,180 // 30lift_scalar = 1.0drag_scalar = 0.1pitch_scalar= 1.0system_type = 1 //Hydraulic[flaps.1]type = 2 // Inboard/midboard leading edgespan-outboard = 0.53333 // 0.0 .. 1.0extending-time = 12 // secondsflaps-position.0 = 0 // pseudo-degreesflaps-position.1 = 1.0 // 1damaging-speed = 275 // KIASblowout-speed = 280 // KIASlift_scalar = 0.88drag_scalar = 1.54pitch_scalar= 1.0system_type = 1 //Hydraulic[flaps.2]type = 2 // Outboard leading edgespan-outboard = 0.2666 // 0.0 .. 1.0extending-time = 10 // secondsflaps-position.0 = 0 // pseudo-degreesflaps-position.1 = 0.0 // 1 - no effectflaps-position.2 = 5.0 // 5damaging-speed = 255 // KIASblowout-speed = 260 // KIASlift_scalar = 1.0drag_scalar = 1.0pitch_scalar= 1.0system_type = 1 //Hydraulic[flaps.3]type = 2 // Correct 5-30 / TE LIFTspan-outboard = 0.7 // 0.0 .. 1.0extending-time = 50 // secondsflaps-position.0 = 0 // pseudo-degreesflaps-position.1 = 0.00flaps-position.2 = 25.0flaps-position.3 = 21.0flaps-position.4 = 16.1flaps-position.5 = 8.7flaps-position.6 = 4.7lift_scalar = -1.22drag_scalar = 0.00pitch_scalar = -0.12system_type = 1 //Hydraulic[flaps.4]type = 2 // Correct 10 / TE DRAGspan-outboard = 0.7 // 0.0 .. 1.0extending-time = 60 // secondsflaps-position.0 = 0 // pseudo-degreesflaps-position.1 = 0.0flaps-position.2 = 0.0flaps-position.3 = 1.0flaps-position.4 = 0.1flaps-position.5 = 3.0lift_scalar = 0.00drag_scalar = -1.00pitch_scalar = 0.00system_type = 1 //Hydraulic[flaps.5]type = 2 // Correct 30 / TE DRAGspan-outboard = 0.7 // 0.0 .. 1.0extending-time = 60 // secondsflaps-position.0 = 0 // pseudo-degreesflaps-position.1 = 0.0flaps-position.2 = 0.0flaps-position.3 = 0.0flaps-position.4 = 0.0flaps-position.5 = 0.0flaps-position.6 = 6.5lift_scalar = 0.00drag_scalar = 1.00pitch_scalar = 0.00system_type = 1 //Hydraulic[flaps.6]type = 1 // Modelspan-outboard = 0.7extending-time = 60 flaps-position.0 = 0.0flaps-position.1 = 1.0flaps-position.2 = 5.0flaps-position.3 = 10.0flaps-position.4 = 20.0flaps-position.5 = 25.0flaps-position.6 = 30.0lift_scalar = 0.0drag_scalar = 0.0pitch_scalar= 0.0system_type = 1Test it and get back to me...Don

I'm just learning a little bit about "C" so I can use the principles in xml gauges.It looks to me like the ASI c file FLOAT64 FSAPI mach_string_cb( PELEMENT_STRING pelement ) section has 0.20 Mach set as minimum to display: FLOAT64 val = pelement->source_var[0].var_value.n; if (val < 0.20) val = 0.20; else val=val; //wsprintf(pelement->string, "%3d", (UINT32)val); I'm interpreting that as: "if Mach is less than 0.20, Display 0.20, otherwise display Mach"...Don

You could try using all of the PMDG [flaps.0]-[flaps.6] but the lift/drag scalings are a lot different. The simplest way to make the flaps gauge line up is to change [flaps.0] and [flaps.1] flaps-position.6 = 30 // degrees to: flaps-position.6 = 33 // degrees. Make the change, verify the gauge now works correctly, and test fly to check full flaps doesn't mess up flight dynamics.As for the autopilot it looks like the PMDG AP is embedded in the FMC. You can try replacing the POSKY [autopilot] with the PMDG and add what looks like Automated Flight Director System. I don't know what it does, but thought it might be worth a try.CHANGE THIS:[autopilot]autopilot_available = 0autothrottle_available = 0default_pitch_mode=0default_bank_mode=0ADD THIS://Do Not Alter the following line or your 747-400 may cease operating.[AFDSAuth]---BEGIN SHA1---036904E3202DA70E950ECD29714706B66084BC23A7AD0E6840A79704D01EBE667B3A06A29E8CE223CC8E0E0E00717C0D7D2EC4E37C4AC61B1189982389660B4C70302304529E1DEE7D67D618CE8C91239234051C80E46202BD0E93847B42D65EA1887523---END SHA1---// Do Not Alter the above lines.If all else fails you may have to add a default autopilot gauge to a new panel window or blank area of an existing panel...Don

OK! Ha-Ha, I didn't need the whole thing :( but I'll put it my archives. It looks like the PMDG didn't have an AP configured in the file and as I suspected, the flaps are very detailed. Post just the [autopilot] and [flaps.0]-[flaps.?] sections of the POSKY. Maybe I can fix those...Don

Do you have a copy of the PMDG aircraft.cfg?

I don't have either aircraft, but have merged a few. As far as the flaps go, did you change the POSKY cfg flaps sect. to the same as the PMDG? They may have different reference/points/angles. I've had to change/test until I got it right before. Is the PMDG AP a custom Gauge by PMDG? I can't imagine the model interfering with arming it. It may have certain pre-conditions such as avionics switch etc that have to be met before it will engage. I've read that you really have to be on top of procedures with the PMDG birds. I'm sure that applies to the panel...Good Luck...Don

This is what xml I got to work this AM. Just a quick test was OK. <?xml version="1.0" encoding="utf-8"?><Gauge Name="Pitch Hold Toggle" Version="1.0"> <Element> <Select> <Value>(L:PitchHoldDCB, number)</Value> <Case Value="0"> <Image Name="F4_AFCS_Switch_Off.bmp" Luminous="no" ImageSizes="22,34" /> </Case> <Case Value="1"> <Image Name="F4_AFCS_Switch_On.bmp" Luminous="no" ImageSizes="22,34" /> </Case> </Select> </Element> <Mouse> <Tooltip>%Pitch Hold</Tooltip> <Area Left="0" Right="22" Top="0" Bottom="10"> <Cursor Type="Hand" /> <Click>1 (>L:PitchHoldDCB, number) (>K:AUTOPILOT_ON) (>K:SYNC_FLIGHT_DIRECTOR_PITCH) (>K:AP_PITCH_REF_SELECT) </Click> </Area> <Area Left="0" Right="22" Top="10" Bottom="20"> <Cursor Type="Hand" /> <Click>0 (>L:PitchHoldDCB, number) (>K:AUTOPILOT_OFF)</Click> </Area> <Area Left="0" Right="11" Top="20" Bottom="34"> <Cursor Type="DownArrow" /> <Click Event="AP_PITCH_REF_INC_DN" /> </Area> <Area Left="12" Right="22" Top="20" Bottom="34"> <Cursor Type="UpArrow" /> <Click Event="AP_PITCH_REF_INC_UP" /> </Area> </Mouse></Gauge> I had to fool around with the AP on/off for stand alone gauge, but if you engage AP Alt Hold it switches off. I still need to work on the visible switch change so it turns off with AP and Alt hold also...DonBTW thanks to all for their ideas/input

Thanks!! I never would have found that. I thought the AP_PITCH_REF_INC u/d were for reference on the Attitude gauge!...Don

I looked for a solution a while back. I couldn't find any in xml, but did find two discussions with possible ideas;http://forums1.avsim.net/index.php?showtop...p;hl=pitch+holdhttp://forums.flightsim.com/vbfs/showthread.php?t=211296If you find a solution would you post it, please? F-4Js only had Pitch/Roll/Yaw in their AFCS...Don

Hey, Bee, I've used Carsten's plans for RC scale to model in FS98. The caveat is that you have to scale again for the software you are using. There are a lot of scale modeling sites that may have what you're looking for. I generally google; airframename "scale drawing" I've had some luck, but not always. Some aircraft history sites also have data or links. If you are modeling an older plane, restorers are also a good source...Good Luck...Don

Thanks OPA, I was just about to open a new thread to discover what happened to the link! ...Don

From what I could find, the reverse polish notation was originally developed for early calculators. Something about moving results from the top of the "stack", but I am not sure with the reasoning...Don

The SDK has an entire list of operators and the syntax used.In your example the "!" is basically "not" and is only true (1) if the prop is not still.The mathematics are arranged in a form of "Reverse Polish Notation"ie; (A:Indicated Altitude, feet) 100 < , is only true (1) when the altitude is less than 100ft(A:Indicated Altitude, feet) 1000 / is altitude divided by 1000IMO the SDK could be better at explaining the usage, and it references some variables that don't work. I'd suggest reading the SDK first to get the jist of it, then start reading posts others have made to see how it can be used. Thats pretty much how I learned the basics...Don

I got the same access denied!The SDK gives the variables and key/mouse events and basic tutorial examples.I don't know about "versions". I use XML Notepad 2007, but I believe any text editor that can save in UTF-8 format will work...Hope this helps...Don

The animation code is embedded in the model, sorry, unless you are designing it or have access to the uncompiled model.def you can't add or modify it...Don

Hi pve, Thanks for the quick reply. I'm finding that I may have to decide if I want it AC oriented or have Mouse Adjustable Range rings. I thought about using code like yours and selecting different Ring sizes depending on the Range/Zoom factor. I've already got a lot of repetitive code as it is!

:( It isn't often that I laugh out loud while reading a thread! :( Thanks, Roman, I needed that...Don