XML Qs 2

[Guest bartels]

Is there anything left that should go in the FAQ? Place questions in this thread.Arne Bartels

[Guest InBetween]

Greetings,I have made an XML "invisible" gauge to control the smokesystemin my Dynamic Jet Smoke effects. The gauge is supposed to turnon the smoke at a specific N1 percent, but not above 29900 ft alt.The gauge works, but has "side-effects": in AC with more than one"exit" only the "main" exit will operate, and some users reporthaving trouble with the autopilot settings being limited to largeincrements.The gauge: (A:ENG1 N1 RPM,percent) 70 > (A:INDICATED ALTITUDE,feet) 29900 < && if{ (>K:SMOKE_ON) } els{ (>K:SMOKE_OFF) } The question is whether this gauge itself causes the anomalies, oris it just the presence of any "invisible" gauge in the VCockpit?Thanks,JR

[Guest bartels]

I haven't tried it it but to check, if it is problem of invisible gauges, you can insert the invisible part of the <Value> line simply in a visible gauge and retry.E.g. <Value>(A:ENG1 N1 RPM,percent) 70 > (A:INDICATED ALTITUDE,feet) 29900 < && if{ (>K:SMOKE_ON) } els{ (>K:SMOKE_OFF) } (A:ENG1 N1 RPM,percent)</Value>For a RPM gauge. You can simply make any kind of visible gauge and insert (A:ENG1 N1 RPM,percent) 70 > (A:INDICATED ALTITUDE,feet) 29900 < && if{ (>K:SMOKE_ON) } els{ (>K:SMOKE_OFF) } just before the value that is really displayed. The "trick" with the invisible gauge is not really necessary, you can "hide" it before any other displayed value.Arne Bartels

[Guest InBetween]

Thanks Arne,I will give it a whirl and report back...JR

[spokes2112 179]

Arne,This little trick is in a response to you saying the "M functions are not explored much." ( http://ftp.avsim.com/cgi-bin/dcforum/dcboa...orum=DCForumID9 )With the "M" function you can make a variable click area. For instance, set the "M" function to monitor the Y axis. Where after giving limits ( in this case 1-10 ) clicking the bottom of will increase/decrease by a factor of 1 and dragging the click upwards will increase/decrease up to a factor 10.Below is a snippet used for setting speed bugs. (G:Var1) (M:Y) 1 max 10 min (G:Var1) + 0 max (>G:Var1)(M:Y) 1 max 10 min (G:Var1) + 450 min (>G:Var1)Other possible uses if they can be directly "set" could be A/P settings, Radio freqs.( Using maybe the "near" function ) , Change the "M" to monitor the X axis to make a horizontal slider etc.... Regards,Roman

[phjvh 0]

Roman, you wrote something about frequency's with M function.If you have time could you show a "snippet" of frequency's to set automatically for the NAV1?I have this one with help from Arne, but it is not working so properly.Busy making an xml-fmc.-----(A:HSI TF flags, enum) 1 == (A:NAV1 HAS NAV,bool) 1 == && if{ (A:NAV1 radial, degrees) 180 + (>K:HEADING_BUG_SET) (A:NAV1 radial, degrees) 180 + (>K:VOR1_SET) } (A:HSI TF flags, enum) 2 == (A:NAV1 HAS NAV,bool) 1 == && if{ (>K:HEADING_BUG_SET) }(A:HSI TF flags, enum) 2 == if{ (L:NAV,number) ++ (>L:NAV,number) 117.10 116.80 113.20 112.60 114.10 110.80 6 (L:NAV,number) case 100 * 10000 % int d 10 % r 10 / int d 10 % r 10 / int d 10 % r 10 / int 16 * + 16 * + 16 * + (>K:NAV1_RADIO_SET) 1 (>K:TOGGLE_AFTERBURNER2) }----Thanks and a good sundayJanhttp://community.webshots.com/sym/image4/2...75aouncN_ph.jpg