ThomasAH

No

I sent an email to PC Aviator and got a positive reply 1.5h ago:

See http://polytoximania.blogspot.de/2014/04/experimental-pfpx-aircraft-config-for-x.html Which points to a file linked at https://gist.github.com/mblauth/11345188 Changes I made in my local copy: - correct ATCDesignator=MU2 - PaxCapacity=7 for Flysimware's variant - added [DEFAULT_DATA_KG] section (converted from DEFAULT_DATA_LB): [DEFAULT_DATA_KG] DOW=3470 MZFW=4103 MTOW=5250 MRW=5273 MLW=5001 FuelCapacity=1170 TaxiFuelPerMinute=1.5 APUBurnPerHour=0

Not sure, but maybe a problem with your flight simulator's default flight?

Not exactly trouble, but I assume it is still multiple hours work per model: Coordination with Milviz, implementation, tests, bug fixes, updating documentation, packaging, coordination with the stores, dealing with additional support requests after upgrade problems, ...

I'm interested in such an update, too. Meanwhile you can use the semi-integration found in my two posts in another thread: http://www.avsim.com/topic/491822-cessna-441-and-milviz-wx-weather-radar/?p=3454864

Default airports or additional scenery?

The OP wrote that it has not enough automation. But I just noticed that the Aerosoft Twin Otter Extended has a GNS530, too, which can follow the GPS flight plan. I think the original, non-Extended Twin Otter did not have this. But maybe this one needs more engine management than he likes to do?

Autopilots following your flight plan via GPS are already available in the GNS530 implementations of Carenado and others, e.g. Flysimware, so not having support for a GTN750 should not be a big problem. Or just use it as a popup. I really like the Carenado C337. It has a much lower cruise altitude (though you could pretend having a pressurized version and fly it at FL190 B)) and a bit less performance than the Duke, but visibility is great! If you want to go a bit faster and a bit higher, I would recommend Flysimware's C441, which still has good cockpit visibility (better than their MU-2B).

Glitch in the matrix? Make sure to exit the flight simulator completely before switching from a complex aircraft, like the Lear, otherwise some settings might carry over to the next aircraft you load.

You should consider 9/27 runways, too. I practice at EDWO. Not really remote and a bit longer than you say, not completely flat, but flat enough nice visual reference points, e.g. the autobahn junction A30/A1. Regarding your original request, I used the program "awk" to parse runways.csv (generated by FSUIPC's MakeRwys.exe), search for runways with exactly 360 degrees (i.e. not 359 or 1), with runway length >=1500 and <=2000, and to ensure the "flatness" with an elevation of <20: awk -F, '$6 == 360 && $7 >= 1500 && $7 <= 2000 && $5 < 20 {print $0}' runways.csv 35ME,0360,43.868546,-68.895157,15,360,1700,0 3VA4,0370,37.855511,-76.736198,10,360,2000,0 5VA9,0360,37.689930,-76.317673,7,360,2000,0 FA24,0360,27.090870,-80.612030,9,360,1800,0 FD57,0360,27.471535,-80.416489,18,360,1900,0 MS99,0360,30.253008,-89.541885,14,360,2000,0 SC74,0360,32.459530,-80.600746,12,360,1700,0

I only have the Switch Panel, not the Multi Panel, but with that my setup is e.g.: SPAD/Default.ini: [SwitchPanel1] SwitchSELSTARTOn=VButton,64,5 SwitchSELSTARTOff=None SwitchSELOFFOn=VButton,64,1 SwitchSELROn=VButton,64,2 SwitchSELLOn=VButton,64,3 SwitchSELALLOn=VButton,64,4 SwitchSELOFFOff=None SwitchSELROff=None SwitchSELLOff=None SwitchSELALLOff=None SPAD/C337.ini: [SwitchPanel1] SwitchSELSTARTOn=VButton,64,5 SwitchSELSTARTOff=None SwitchSELOFFOn=VButton,64,1 SwitchSELROn=VButton,64,2 SwitchSELLOn=VButton,64,3 SwitchSELALLOn=VButton,64,4 SwitchSELOFFOff=None SwitchSELROff=None SwitchSELLOff=None SwitchSELALLOff=None SwitchDEICEOn=VButton,64,6 SwitchDEICEOff=VButton,64,7 SwitchPANELOn=VButton,64,8 SwitchPANELOff=VButton,64,9 I'll take the global Magneto selector switch and the = C337-specific panel light switch as an example, in FSUIPC4 I have configured: FSX/Modules/FSUIPC4.ini: [Buttons] ...other buttons... 42=P64,4,C66027,0 -{MAGNETO_START}- 43=P64,3,C66026,0 -{MAGNETO_BOTH}- 44=P64,2,C66025,0 -{MAGNETO_LEFT}- 45=P64,1,C66024,0 -{MAGNETO_RIGHT}- 46=P64,0,C66023,0 -{MAGNETO_OFF}- FSX/Modules/Profiles/C337.ini: [Buttons] ...other buttons... 13=P64,7,Cx06000D0C,x0220 ; Panel+Cabin Light -{offset word setbits, offset 0D0C}- -{offset word setbits, offset 0D0C}- 14=P64,8,Cx0A000D0C,x0220 ; Panep+Cabin Light -{offset word clrbits, offset 0D0C}- -{offset word clrbits, offset 0D0C}- Beware that the button numbers in SPAD's ini files are 1...n, while in FSUIPC they are 0...n-1, but I think SPAD's GUI interface already shows these identical to FSUIPC. Now you have to find out, which FSX controls, which FSX offsets, or which L-vars are used in the Lear to control the auto pilot. The folder FSX/Modules/FSUIPC Documents/ might contain the corresponding information in the files "List of FSX and P3D controls.pdf" and "FSUIPC4 Offsets Status.pdf". Using controls would be the best, here are all controls with "AP PANEL": 65798 AP PANEL HEADING HOLD 65799 AP PANEL ALTITUDE HOLD 65890 AP PANEL VS HOLD 65891 AP PANEL SPEED HOLD 65915 AP PANEL MACH HOLD 66103 AP PANEL ALTITUDE ON 66104 AP PANEL ALTITUDE OFF 66105 AP PANEL ALTITUDE SET 66106 AP PANEL HEADING ON 66107 AP PANEL HEADING OFF 66108 AP PANEL HEADING SET 66109 AP PANEL MACH ON 66110 AP PANEL MACH OFF 66111 AP PANEL MACH SET 66112 AP PANEL SPEED ON 66113 AP PANEL SPEED OFF 66114 AP PANEL SPEED SET 66115 AP PANEL VS ON 66116 AP PANEL VS OFF 66117 AP PANEL VS SET 66353 AP PANEL SPEED HOLD TOGGLE 66354 AP PANEL SPEED ACQ TOGGLE 66356 AP PANEL MACH HOLD TOGGLE 66357 AP PANEL MAX SPEED TOGGLE 66358 AP PANEL CRUISE SPEED TOGGLE But I would assume that SPAD (or SPAD:Next, if you want to use that) already maps most (or if you are lucky, all) of them correctly, unlike the default Saitek drivers, which I recommend disabling in exe.xml (just change "<Disabled>False</Disabled>" to "<Disabled>True</Disabled>", or remove the block), or alternatively uninstalling from your system. Edit: I just remembered this thread: Replacing Lear35A Mouse Clicks with Keys or Buttons So the regular controls do not work, but you can map ark's lua scripts to the virtual joystick buttons.

Do you use SPAD and have a registered version of FSUIPC? With that you can map the panel buttons to virtual joystick buttons and assign anything to them via FSUIPC.