I have added the armin GNS530 to my AeroWorx Kingair. MY problem is when I click on it the popup is like a 2nd Gauge. In other words when I make a change to the popup and then unclick it the changes don't show up in the GNS in the panel. I have to do it twice. So say I want the terrian on I have to click terr on the panel gauge then open the popup and click terrian again. I have included below the two entries to my panel config. Any Ideas. Thanks.[Window10]file=WS_pic_vfr_tcas_ver1.BMP size_mm=1680,1050window_size_ratio=1.000 position=7visible=1ident=1window_size= 1.000, 1.000window_pos= 0.000, 0.000gauge00=awx.b20!EADI, 268,591,219,212,picvfrgauge01=awx.b20!EHSI, 268,805,219,217,picvfrgauge02=awb2001!awb200_pic_vfr_ifr_toggle, 282,448,256,65,picvfrgauge03=awb2001!awb200_pic_cp_vfr_toggle, 924,432,296,70,picvfrgauge04=awb2002!awb200_airspeed, 117,614,136,136,picvfrgauge05=awb2002!awb200_turnslip_pic, 1,723,88,88,picvfrgauge06=awb2002!awb200_rmi_pic, 110,770,151,149,picvfrgauge07=awb2002!awb200_altimeter_pic, 497,613,154,147,picvfrgauge08=awb2002!awb200_dme_pic, 498,938,146,60,picvfrgauge09=awb2002!awb200_left_itt, 694,510,99,99,picvfrgauge10=awb2002!awb200_right_itt, 802,510,99,99,picvfrgauge11=awb2002!awb200_left_torque, 694,615,99,99,picvfrgauge12=awb2002!awb200_right_torque, 803,613,99,99,picvfrgauge13=awb2002!awb200_left_prop_rpm, 693,718,99,99,picvfrgauge14=awb2002!awb200_right_prop_rpm, 803, 717 ,99,99,picvfrgauge15=awb2002!awb200_left_n1, 694,821,99,99,picvfrgauge16=awb2002!awb200_right_n1, 802,820,99,99,picvfrgauge17=awb2002!awb200_left_fuelflow, 694,923,99,99,picvfrgauge18=awb2002!awb200_right_fuelflow, 803,920,99,99,picvfrgauge19=awx.b20!altalert, 1137,641,162,82,picvfrgauge20=awb2002!awb200_fast_erect_vfr, 44,650,51,50,picvfrgauge21=awb2001!awb200_simicons_h, 0,0,334,28,picvfrgauge22=awb2002!awb200_MasterWarn, 305,395,41,30,picvfrgauge23=awb2002!awb200_MaterCaution, 366,390,41,30,picvfrgauge24=awb2002!awb200_top_annunciator, 919,307,290,86,picvfrgauge25=awb2002!awb200_top_annunciator_test, 1223,337,34,31,picvfrgauge26=awb2002!awb200_gyro_slave, 0,838,91,91,picvfrgauge27=awb2005!awb200_comm1, 926,689,119,130,picvfrgauge28=awb2005!awb200_nav1, 926,832,119,130,picvfrgauge29=awb2002!awb200_whiskey, 1023,4,88,54,picvfrgauge30=awb2002!awb200_commch_switch_vfr, 951,566,63,78,picvfrgauge31=awx.honeywell!VSI, 491,773,167,156,picvfrgauge32=awb2005!awb200_xpdr, 927,976,119,130,picvfrgauge33=awx.b20!eadi_dim, 132,955,46,51,picvfrgauge34=awb200_reg!regnum, 439,548,91,34,picvfrgauge35=awx.b20!hdgcrs_popup_click, 3,975,99,69,picvfrgauge36=awb2002!eng_toggle, 650,442,248,69,picvfrgauge37=awb2001!awb200_pi, 1024,141,2,2,picvfrgauge38=awb2001!awb200_ap_vc_toggle, 648,349,265,64,picvfrgauge39=awb2002!awb200_airspeed, 1555,589,136,136gauge40=awb2002!awb200_rmi_pic, 1541,745,147,155gauge41=awb2005!awb200_tug, 1199,577,38,38,picifrgauge42=awb20010!awxkln90b, 1065,955,306,94gauge43=awb2005!awb200_comm2, 1388,691,119,130gauge44=awb2005!awb200_nav2, 1387,832,119,130gauge45=awb2005!awb200_adf, 1386,976,119,130gauge46=awb2004!awb200_dme_cp, 1551,913,146,61gauge47=awb2001!awb200_kln90b_popup, 1140,960,154,67,picvfrgauge48=B200!Caution Annun_popup, 5,492,128,96,picifrgauge49=FS9Garmin!GNS530, 1052,729,334,223[Window22]size_mm=446,275window_size_ratio=1.000 position=5visible=0ident=42sizeable=0window_size= 0.348, 0.344window_pos= 0.550, 0.497gauge00=FS9Garmin!GNS530, 0,0,446,275,nd

Hi,It probably depends on how they coded it. Some variables will transfer between gauges, others won't.

The GPS system uses a lot of (G:variables) which are local only to the specific instance loaded. In other words, they aren't shared globally with the rest of the system.As a result, many operations (but not all!) will affect only the single instance of a gauge, and not the others......which is why synchronizing the 2d, popup and virtual cockpit instances of the GPS impossible. :(

Some may ask why they didn't make them all the "right" type of variables (they are called L: variables) - they probably have a larger effect on the frame rate, is my guess...

Some may ask why they didn't make them all the "right" type of variables (they are called L: variables) - they probably have a larger effect on the frame rate, is my guess...

Oddly enough though, simply globally changing G:vars to L:vars WON'T WORK! :(

Hi again,That's true if they assumed they would act locally, and not globally, I agree. But an L: variable usually can be substituted along with changes in the code, right?

Normally, yes. I suspect that the reason they can't be substituted in anything sending a query to the fs9gps.dll is that multiple requests would be sent simultaneously by each instance of a GPS that had focus, and it would confuse the hell out of fs9gps.dll! :(