I can't seem to get the AP to work (in FSX) and I'm wondering if I can change the lines in the panel file to make the AP work. I know I would have to place the gauges in the panel also to make it work.I know not to change the values, ie Tornado_Gauges!AP_IAS Hold, 42,334,19,19, but just the gauge itself Tornado_Gauges!AP_IAS Hold, 42,334,19,19Below is the panel file[Window02]file=torn_elecauto.bmp file_1024=torn_elecauto.bmp size_mm=194window_size_ratio=1.000 position=0visible=0ident=90window_size= 0.150, 0.600window_pos= 0.860, 0.000gauge00=Tornado_Gauges!Panel Lights Switch, 129,44,18,18gauge01=Tornado_Gauges!Landing Light Switch, 90,44,18,18gauge02=Tornado_Gauges!Navigation Lights Switch, 59,44,18,18gauge03=Tornado_Gauges!Avionics Switch, 23,92,18,18gauge04=Tornado_Gauges!Battery Switch, 61,92,18,18gauge05=Tornado_Gauges!AP_DISP_Heading Lock, 99,405,60,10gauge06=Tornado_Gauges!AP_DISP_Altitude Lock, 99,305,60,10gauge07=Tornado_Gauges!AP_DISP_Speed Lock, 100,338,58,10gauge08=Tornado_Gauges!AP_DISP_Mach Lock, 100,372,59,10gauge09=Tornado_Gauges!AP_DISP_VS Lock, 101,442,60,10gauge10=Tornado_Gauges!AP ALT Dec, 77,296,15,27gauge11=Tornado_Gauges!AP ALT Inc, 65,297,12,27gauge12=Tornado_Gauges!AP_IAS Hold, 42,334,19,19gauge13=Tornado_Gauges!AP_Mach Hold, 43,370,17,17gauge14=Tornado_Gauges!AP_Heading Hold, 43, 405 ,17,17gauge15=Tornado_Gauges!AP_Alt Hold, 42,302,18,20gauge16=Tornado_Gauges!AP Button Master, 41,508,18,17gauge17=Tornado_Gauges!Approach Hold, 108,507,19,17gauge18=Tornado_Gauges!AP_BackCourse Hold, 143,507,18,17gauge19=Tornado_Gauges!Fuel Cutoff 1, 96,187,18,18gauge20=Tornado_Gauges!Fuel Cutoff 2, 133,187,18,18gauge21=Tornado_Gauges!Strobe Lights Switch, 24,44,18,18gauge22=Tornado_Gauges!AP IAS Dec, 79,331,15,27gauge23=Tornado_Gauges!AP IAS Inc, 64,331,15,27gauge24=Tornado_Gauges!AP HDG Inc, 64,401,15,27gauge25=Tornado_Gauges!AP HDG Dec, 78,401,15,27gauge26=Tornado_Gauges!AP VS Inc, 65,437,15,27gauge27=Tornado_Gauges!AP VS Dec, 80,436,15,27gauge28=Tornado_Gauges!AP Mach Inc, 63,365,15,27gauge29=Tornado_Gauges!AP Mach Dec, 78,365,15,27gauge30=Tornado_Gauges!Pitot Heat, 62,187,18,18gauge31=Tornado_Gauges!L Generator, 91,91,18,18gauge32=Tornado_Gauges!R Generator, 130,90,18,18Is this possible to do?Thanks for any help or input.CheersAri

Hi,It's certainly possible, but differences in the way the gauges are laid out may make this approach problematic. Sometimes it works, sometimes it doesn't...

Which version are you using? I have IRIS Tornado GR4(google IrisTornado_X.zip) updated by Danny Garnier for FSX. It comes with a bunch of gauge .cabs that you might be able to use for replacements...Don

I've tried both of those...and the Autopilot stack inside the VC still wouldn't work. The problem I see is that there are to many gauges I believe, or should I say double gauge work. Notice how there are 2 gauges performing the task of what should be 1 gauge. Maybe I'm reading it wrong.gauge00=Tornado_Gauges!Panel Lights Switch, 129,44,18,18gauge01=Tornado_Gauges!Landing Light Switch, 90,44,18,18gauge02=Tornado_Gauges!Navigation Lights Switch, 59,44,18,18gauge03=Tornado_Gauges!Avionics Switch, 23,92,18,18gauge04=Tornado_Gauges!Battery Switch, 61,92,18,18gauge05=Tornado_Gauges!AP_DISP_Heading Lock, 99,405,60,10gauge06=Tornado_Gauges!AP_DISP_Altitude Lock, 99,305,60,10gauge07=Tornado_Gauges!AP_DISP_Speed Lock, 100,338,58,10gauge08=Tornado_Gauges!AP_DISP_Mach Lock, 100,372,59,10gauge09=Tornado_Gauges!AP_DISP_VS Lock, 101,442,60,10gauge10=Tornado_Gauges!AP ALT Dec, 77,296,15,27gauge11=Tornado_Gauges!AP ALT Inc, 65,297,12,27gauge12=Tornado_Gauges!AP_IAS Hold, 42,334,19,19gauge13=Tornado_Gauges!AP_Mach Hold, 43,370,17,17gauge14=Tornado_Gauges!AP_Heading Hold, 43, 405 ,17,17gauge15=Tornado_Gauges!AP_Alt Hold, 42,302,18,20gauge16=Tornado_Gauges!AP Button Master, 41,508,18,17gauge17=Tornado_Gauges!Approach Hold, 108,507,19,17gauge18=Tornado_Gauges!AP_BackCourse Hold, 143,507,18,17gauge19=Tornado_Gauges!Fuel Cutoff 1, 96,187,18,18gauge20=Tornado_Gauges!Fuel Cutoff 2, 133,187,18,18gauge21=Tornado_Gauges!Strobe Lights Switch, 24,44,18,18gauge22=Tornado_Gauges!AP IAS Dec, 79,331,15,27gauge23=Tornado_Gauges!AP IAS Inc, 64,331,15,27gauge24=Tornado_Gauges!AP HDG Inc, 64,401,15,27gauge25=Tornado_Gauges!AP HDG Dec, 78,401,15,27gauge26=Tornado_Gauges!AP VS Inc, 65,437,15,27gauge27=Tornado_Gauges!AP VS Dec, 80,436,15,27gauge28=Tornado_Gauges!AP Mach Inc, 63,365,15,27gauge29=Tornado_Gauges!AP Mach Dec, 78,365,15,27gauge30=Tornado_Gauges!Pitot Heat, 62,187,18,18gauge31=Tornado_Gauges!L Generator, 91,91,18,18gauge32=Tornado_Gauges!R Generator, 130,90,18,18The other problem I see, is that if the gauge was replaced by 1 stand alone gauge it might not show up in the right location " I think" because of the first set of location numbers. I know that in the VC on the Autopilot stack all the the images or readouts for the gauge is there, but there's nothing working, as in nothing to click or set for the Autopilot to acutally work. It's a great little plane and with the config update flys really well. But without the Autopilot working, it's a lot of work to fly longer distances. If I could just get the AP master on/off, ALT hold and NAV-GPS buttons to work the throttle setting wouldn't be that big of a deal, as I could set thoses manually.Ari

Those are NOT "duplicate" gauges. Note that each is a "pair" of gauges, one for INCREASE and the other for DECREASE.I've no idea why Iris chose to do it that way, but they must have had their reasons.Have you checked the aircraft.cfg to ensure that the options marked in red below are present?[autopilot]autopilot_available= 1flight_director_available= 1default_vertical_speed= 1800.0autothrottle_available= 1autothrottle_arming_required= 0autothrottle_max_rpm = 90autothrottle_takeoff_ga= 0

I can't seem to get the AP to work (in FSX) and I'm wondering if I can change the lines in the panel file to make the AP work. I know I would have to place the gauges in the panel also to make it work.I know not to change the values, ie Tornado_Gauges!AP_IAS Hold, 42,334,19,19, but just the gauge itself Tornado_Gauges!AP_IAS Hold, 42,334,19,19Below is the panel file[Window02]file=torn_elecauto.bmp file_1024=torn_elecauto.bmp size_mm=194window_size_ratio=1.000 position=0visible=0ident=90window_size= 0.150, 0.600window_pos= 0.860, 0.000gauge00=Tornado_Gauges!Panel Lights Switch, 129,44,18,18gauge01=Tornado_Gauges!Landing Light Switch, 90,44,18,18gauge02=Tornado_Gauges!Navigation Lights Switch, 59,44,18,18gauge03=Tornado_Gauges!Avionics Switch, 23,92,18,18gauge04=Tornado_Gauges!Battery Switch, 61,92,18,18gauge05=Tornado_Gauges!AP_DISP_Heading Lock, 99,405,60,10gauge06=Tornado_Gauges!AP_DISP_Altitude Lock, 99,305,60,10gauge07=Tornado_Gauges!AP_DISP_Speed Lock, 100,338,58,10gauge08=Tornado_Gauges!AP_DISP_Mach Lock, 100,372,59,10gauge09=Tornado_Gauges!AP_DISP_VS Lock, 101,442,60,10gauge10=Tornado_Gauges!AP ALT Dec, 77,296,15,27gauge11=Tornado_Gauges!AP ALT Inc, 65,297,12,27gauge12=Tornado_Gauges!AP_IAS Hold, 42,334,19,19gauge13=Tornado_Gauges!AP_Mach Hold, 43,370,17,17gauge14=Tornado_Gauges!AP_Heading Hold, 43, 405 ,17,17gauge15=Tornado_Gauges!AP_Alt Hold, 42,302,18,20gauge16=Tornado_Gauges!AP Button Master, 41,508,18,17gauge17=Tornado_Gauges!Approach Hold, 108,507,19,17gauge18=Tornado_Gauges!AP_BackCourse Hold, 143,507,18,17gauge19=Tornado_Gauges!Fuel Cutoff 1, 96,187,18,18gauge20=Tornado_Gauges!Fuel Cutoff 2, 133,187,18,18gauge21=Tornado_Gauges!Strobe Lights Switch, 24,44,18,18gauge22=Tornado_Gauges!AP IAS Dec, 79,331,15,27gauge23=Tornado_Gauges!AP IAS Inc, 64,331,15,27gauge24=Tornado_Gauges!AP HDG Inc, 64,401,15,27gauge25=Tornado_Gauges!AP HDG Dec, 78,401,15,27gauge26=Tornado_Gauges!AP VS Inc, 65,437,15,27gauge27=Tornado_Gauges!AP VS Dec, 80,436,15,27gauge28=Tornado_Gauges!AP Mach Inc, 63,365,15,27gauge29=Tornado_Gauges!AP Mach Dec, 78,365,15,27gauge30=Tornado_Gauges!Pitot Heat, 62,187,18,18gauge31=Tornado_Gauges!L Generator, 91,91,18,18gauge32=Tornado_Gauges!R Generator, 130,90,18,18Is this possible to do?Thanks for any help or input.CheersAri

I have the AP working in FSX for the F3. The AP in the VC does not work as most of the gauges are missing from the VC section of the panel.cfg. The Autopilot Master, AP-Heading Hold, AP-Alt Hold, etc.) To get the IAS hold working I had to make the changes noted by Fr. Bill in his post. I have no idea how to place the right gauges in the VC as VC gauge placement is beyond me. Regards, Bob.

Those are NOT "duplicate" gauges. Note that each is a "pair" of gauges, one for INCREASE and the other for DECREASE.I've no idea why Iris chose to do it that way, but they must have had their reasons.Have you checked the aircraft.cfg to ensure that the options marked in red below are present?[autopilot]autopilot_available= 1flight_director_available= 1default_vertical_speed= 1800.0autothrottle_available= 1autothrottle_arming_required= 0autothrottle_max_rpm = 90autothrottle_takeoff_ga= 0

Checked the file and it differs a little but it is there...autopilot_available=1flight_director_available=1default_vertical_speed=1700.000autothrottle_available=1autothrottle_arming_required=0autothrottle_takeoff_ga=0autothrottle_max_rpm=105.000Those are NOT "duplicate" gauges. Note that each is a "pair" of gauges, one for INCREASE and the other for DECREASE.I understand they are in pairs but what I was trying to point out is that they used 2 different gauges to the work of one. I haven't noticed any of my other aircraft using that many gauges. What I generally see in most of my other freeware aircraft panels are something like this...gauge05=General!AP_AltSelector, 904,341,21,21gauge06=General!AP_Course_Selector, 573,341,19,20gauge07=General!AP_FDSwitch, 608,300,14,29gauge08=General!AP_course_Window, 572,304,23,13gauge09=General!AP_AltWindow, 883,307,39,13gauge10=General!AP_HdgSelector, 750,340,20,19gauge11=General!AP_IASMachSelector, 661,340,22,20gauge12=General!AP_HdgWindow, 747,307,23,13gauge13=General!AP_IASMachWindow, 657,305,28,13gauge14=General!AP_VSSelector, 814, 331 ,10,33gauge15=General!AP_VSWindow, 786,308,35,13What I'm used to seeing the most of in my panels is something like this..gauge18=Boeing777-300!Autopilot,255,182That one gauge controls everthing I guess...and if I believe correctly this is writing in xml code correct? Which is way above my head.Ari