LKL

I MUST BE MISSING SOMETHING, BUT(Condition 1) if{ (DoThis 1) } <==SATISFIED FOR FIRST if{ els{ (Condition 2) <==NOT SATISFIED UNTIL LATER if{ (DoThis 2) } <==SATISFIED FOR SECOND if{ els{ (DoThis 3) } <==SATISFIED FOR SECOND els{ } <==SATISFIES THE FIRST els{ } <== WHAT IS THIS ONE FOR? QUOTE: There should always be an even number of { and } braces in any XML expression, since they are always paired with one another. I COUNT 4 EACH { .....AND 5 EACH } ??

IT MUST BE ALL -MAGIC-...?? .I JUST NOW WAS ABLE TO REPLY TO 2 POSTS THAT I HAVE TRIED NUMEROUS TIMES WITH THE SAME ERROR, AND EVERY THING WORKED TODAY. I EVEN SAVED MY RESPONSES IN A TEXT FILE SO THAT I COULD CUT AND PASTE MY REPLIES, SO THAT I WOULD NOT HAVE TO TYPE IT IN AGAIN.I'M SATISFIED.

IS THE LAST } NECESSARY? NOTE, I USE ALL CAPS. SEE ABOVETHANKS FOR THE SUGGESTION ABOUT USING NOTEPAD++ I HAVE HAD IT FOR YEARS AND KEEP IT UP TO DATE BUT HAVE BEEN USING NOTE TAB LIGHT FOR SO LONG, I WAS HESITANT TO CHANGE. BUT, I WILL 'NOW' WHEN EDITING XML FILES. THE { & } CHARACTERS HAVE GIVEN ME MORE F$I!G PROBLEMS THEN I CARE TO MENTION HA!....ANYWAY, SOME PEOPLE I KNOW WILL NOT ACCEPT CHANGE....I'M NOT ONE OF THEM.I FINALLY INCORPORATED THE 4 SOUNDS IN AN ALREADY AUTOLAND GAUGE THAT I HAVE MODIFIED OVER THE YEARS. I WAS AT FIRST TRYING TO MAKE A SEPARATE GAUGE THAT WOULD BE CALLABLE FROM ANY OTHER GAUGE. I THINK WITH THE GOOD SUGGESTIONS THAT YOU GUYS HAVE GIVEN ME, I WILL GO BACK AND FINISH THE GAUGE THAT I STARTED.THANKS

JUST A THOUGHT: DOES IT HAVE ANYTHING TO DO WITH THE { } CHARACTERS IN THE POST THAT I AM REPLYING TO?IF THAT IS TRUE THEN ANYONE REPLYING TO THIS POST SHOULD GET THE SAME ERROR.

I ONLY HAVE ONE ARM AO

NOTE: I USE ALL CAPS BECAUSE OF MY KEYBOARD SETUP, UNLESS I CAN CUT AND PASTE.I KEEP GETTING THIS ERROR WHEN TRYING TO POST A REPLY. WHAT DOES IT MEAN?An error occurredThe number of opening quote tags does not match the number of closing quote tags.THANKS

JAN:FIRST OFF I USE ALL CAPS BECAUSE OF HOW MY KEY BOARD IS SET UP. MY JOY STICKS ARE IN FRONT OF MY FIRST MONITOR AND THE KEY BOARD IS AT AN ANGLE OF ABOUT 75 DEGREES IN FRONT THE SECOND RIGHT MONITOR. THEREFORE I 'HAVE' TO 1 FINGER TYPE. SORRY IF ANYBODY TAKES OFFENSE, BUT THAT'S JUST THE WAY IT IS.I SAW THE FEB 18 POST AND RESPONDED WITH 'COULD YOU INCLUDE THE ACTUAL EVENTS' BECAUSE I DID NOT UNDERSTAND SOME OF THE STATEMENTS.I JUST STARTED TO TAKE AN INTEREST IN PANEL AND GAUGE DESIGN, AND STILL GETTING UP TO SPEED. IT'S MY FAVORITE AREA IN FSX.SO FAR I TAKE SOMEONE'S GAUGE AND MODIFY IT TO MY OWN PERSONAL USE. I THINK I HAVE SOME NICE ONES. (FOR ME THAT IS)THANKS

Thanks I will try it. I was actually trying to create a standalone gauge (containing the 4 items) that I described in my original post, but have decided to just use it in my Autoland gauge that I have been messing with for years. I got it working the other day using the sounds, and it was easier then trying to make it a separate gauge.How do you close this post? or can you.Thank to everyone for their help. I have learned a lot.LKL

Anthony:Thanks for your help. I tried your gauge but could not make it work. I think it has some to do with the placement of the { and } operators. What is the rule? (opens/closes a statement ??) It appears to be that if the { is used it must be followed with a } somewhere in the file and it looks like you can have extra ones on the end. I found the Expression operators, after re-installing the SDK. Have not looked at it in years because I just recently got interested in gauge creation. It must have got corrupted somehow. Here is what I tried.<Element> <Select> <Value> L:ILS_State,number) 1 ==<!-- GlideSlope Active --> if{ (A:HSI CDI NEEDLE VALID,bool) if{ (L:GS_Sound_Triggered,bool) ! if{ 1 (> L:snd1_1, enum) 1 (>L:GS_Sound_Triggered,bool) }} els{ 0 (>L:GS_Sound_Triggered,bool) } } </Value> </Select></Element> I could move the } around and got sound but it would continuously repeat.

ROB:It WORKED just as designed. I Thank you guys very much.I feel like "OPA'' who passed away recently. THIS FLIGHT SIMMING CAN BECOME ADDICTIVE.I helped Doug test his latest gauge last year that was having a problem that me and another guy was having. His latest revision became 4.1.8 (164 KB) but I don't know if he ever released it yet.For comparison purposes, what events would YOU use to detect the 4 gauges==> GlideSlope Active, Localizer Alive, GlideSlope Alive and GlideSlope Engaged.An example like (A:HSI GSI NEEDLE,number) -20 > would be welcomed. LKL

JAN:I'm just now getting up to speed on xml gauge programming, and need an example of the gauge using your suggesting with the following.f{(A:HSI CDI NEEDLE VALID,bool)if{ 1 (> L:snd1_1, enum) } }In the meantime I will look into the other 2 replies to my post.

From a post by:n4gix, on 17 February 2012 - 02:52 PM, said:I'll just mention that there's a forum just down a few levels dedicated to such questions about aircraft, panel and gauge designexperience of the community in building an extensive catalog of missions for FSX.I assume NOW that he was referring to this:MSFS Aircraft and Panel Design ForumDesigning panels or aircraft for the MSFS series? Want to learn? Here THE place to get together with your fellow designers or to ask questions.I don't see the word "GAUGE" in the forum. I just see==>'MSFS Aircraft and Panel Design Forum'Maybe the sub paragraph should read as==> Designing Panels,Gauges and Aircraft for the MSFS series? Want to learn? Here's THE place to get together with your fellow designers or to ask questions.This might keep people from posting gauge problems in the "MS FSX Forum"I also had to "Google" several times in order to find out how to EDIT my profile. I noticed there were a lot of entries in Google for this same item.It's one of those things that Once you know, it's easy' I know there is a 'sub' Help Topics, but it should be a UNIQUE tab at the top of the page.Just a few suggestions.LKL

I could not get in to EDIT my post, so I will add it here.The "Repeat of the above, but with a trigger to satisfy the event" should read as"Repeat of the above, but with an event to satisfy the sound trigger"LKL

RE-POSTED IN THE PANELS FORUM

Your post above:I don't see the word "GAUGE" in the forum. I just see==>'MSFS Aircraft and Panel Design Forum'Maybe it should read as==> Designing panels and gauges for aircraft in the MSFS series?Just a suggestion.I did re-post it in that forum with hopefully a better explanation on what I was trying to accomplish ThanksLKL

Re-posted here, as per: Fr. Bill - MSFS Tips and Tricks ModeratorCould someone/anybody, post a gauge to do the following 4 sound triggers as suggested below:I use an AutoLand gauge that I modified for my own personal internal use years ago, but wanted to add 4 additional sounds.I have an Instrument rating, I just don't know how to design gauges....HA! Is there any literature that explains what the following characters do in a .XML gauge file? Examples { } || == ! / > < etc.I looked into the SDK but did not find anything. Some of the characters are self explanatory.Assuming a typical ILS Approach into KSFO 28R:Maintaining proper speeds and an altitude of about 3000 ft AGL, at an angle to intercept the Localizer until the Glide Slope is Captured.This is NOT to be interpreted as a tutorial, just for illustration purposes ONLY.<Comment> GlideSlope Active= The LOC (CDI) is detected -Not intercepted- and is visual on the HSI, Aircraft is about 27-28 miles out. DME1 will show this. Localizer Alive= The LOC is intercepted and GS (GSI) is visual on the HSI. Meaning, BOTH needles have been detected, Aircraft is about 22 miles out. APR HOLD should now be activated.GlideSlope Alive= The GS is intercepted and (GSI) is starting to move. Aircraft is about 14 miles out. Wait for Capture (Engaged).GlideSlope Engaged= The (GSI) is centered on the HSI, Aircraft is about 11 miles out. ALT HOLD will be deactivated IF, it was being used to intercept the GlideSlope System. </Comment><!-- SUGGESTED BARE BONES GAUGE --><!-- GlideSlope Active --><Element> <Select> <Value> (L:ILS_State,enum) 1 == if{ (A:HSI CDI NEEDLE VALID,bool) if{ 1 (> L:snd1_1, enum) } } <==I tried this but, even with excellent help I could not keep the sound from repeating. </Value> </Select></Element><!-- Localizer Alive --><Element> <Select> <Value> (L:ILS_State,enum) 2 == if{ Repeat of the above, but with a trigger to satisfy the event if{ 1 (> L:snd1_2, enum) } } </Value> </Select></Element><!-- GlideSlope Alive -->(<Element> <Select> <Value> (L:ILS_State,enum)3 == if{ Repeat of the above, but with a trigger to satisfy the event if{ 1 (> L:snd1_3, enum) } } </Value> </Select></Element><!-- GlideSlope Engaged --> <Element> <Select> <Value> (L:ILS_State,enum) 4 == if{ Repeat of the above, but with a trigger to satisfy the event if{ 1 (> L:snd1_4, enum) } } </Value> </Select></Element></Gauge>Thanks in AdvanceLKL

I tried your suggestion but (L:snd_2,enum) 1 == if{ 0 (>L:snd_2,enum) } will not produce any sound. I have to use as shown below in order to have sound. Here is part of my code<Element><Select> <Value> (L:GAState,number) 2 == I come into this gauge from another gauge and snd1_86 is my actual sound in my sounds.ini file if{ (A:HSI CDI NEEDLE VALID,bool) if{ 1 (>L:snd1_86,enum -or- 1 (>L:snd1_86,enum (==> will give constant repeats of the sound until the condition goes away. I tried every condition using your example but still no fix. Tried to use wothanfja16 suggestion but with no sucess. I will keep trying) </Value> </Select></Element>SUMMARY: I don't get any sounds, unless I use the 2 above and preceeded with the following==> if{ 1 (>L or 1 (>L:Thanks

I have a gauge to detect the events, but I need to know how to play the sound -ONLY- ONE time. The event stays up for a while, so it keeps repeating the sound.For instance using part of my gauge below to detect when the Glideslope Becomes active, usually about 24 miles from touchdown when it detects the NAV1 (ILS) frequency.--if{(A:HSI CDI NEEDLE VALID,bool)if{1 (>L:snd_2,enum)Big picture is I'm just trying to play sounds for (GLIDESLOPE ACTIVE), (LOCALIZER ALIVE), (GLIDESLOPE ALIVE), and (GLIDESLOPE CAPTURED) and for them to play just one time.Thanks in advanceLKL

I have a gauge to detect the events, but I need to know how to play the sound -ONLY- ONE time. The event stays up for a while, so it keeps repeating the sound.For instance using part of my gauge below to detect when the Glideslope Becomes active, usually about 24 miles from touchdown when it detects the NAV1 (ILS) frequency.--if{ (A:HSI CDI NEEDLE VALID,bool) if{ 1 (>L:snd_2,enum)Big picture is I'm just trying to play sounds for (GLIDESLOPE ACTIVE), (LOCALIZER ALIVE), (GLIDESLOPE ALIVE), and (GLIDESLOPE CAPTURED) and for them to play just one time.Thanks in advanceLKL