Pete Dowson

Apart from LINDA, you could do all that yourself with a Lua plug-in, assuming that you have appropriate (accessible) interfaces to that device. Pete

I think they are the same, just alternative names. Just checked them in the C172 and both work. The AP button in the aircraft itself uses the AP ALT HOLD event. I've not tested these in MSFS, but they certainly used to be different. If there's an MCP altitude display, or, for GA, probably an adjustable speed bug on the speed tape/dial then they operated differently. The "AP PANEL ALTITUDE HOLD" says to hold at the display or bug-set altitude, whereas "AP ALT HOLD" says to hold at the current altitude. Pete

In my case, with an MS Store install, it was the LocalCache folder, next door to the LocalState one. Pete

It's John who has made it available and who is doing almost all the work. i'm officially retied -- just doing whatever minimal WideFs and FSUIPC4 support is occasionally still needed. Pete

Also, I'm not sure in the complex MSFS installatiion where you'd create a "modules" folder. I just made a folder called "FSUIPC7" on different drive, and put it in there along with the other files it needs. Pete

0x0B80 and 0xAF4 are OFFSET values -- i.e the addresses in FSUIPC which contain the data. They are not the data themselves but fixed numbers, in hexadecimal. In other words you need to read the values from those offsets -- making three values you need to read to calculate what you want. The fuel level provided is in terms of the percentage of tank full, so is based on tank capacity. All versions of Flight Sim, including the new MSFS, provide the capacities of each tank and the current level as a proportion. They also supply the current weight per gallon so that the current total weight of fuel can be calculated. I think you'll find that GA prop aircraft have analog fuel gauges which show capacity and current level, much the same as in motor vehicles. I'm pretty sure that in glass cockpit airliners, and the like, the calculation is done for you -- by software. There was that famous case where and airliner had the fuel loaded in US Gallons and the pilot had thought it was in Imperial Gallons (20% more), and they ended up crash landing on vapour. Pete

Try enabling the auto-close option in FSUIPC7, and closing MSFS first instead of FSUIPC. It is probably some timing problems with interaction with the VRI devices. This sort of thing has happened before on FSX and P3D. I'm pretty convinced it is to do with the serial port usage made by those devices, not terminating properly. When we've managed to actually get details, the thread which isn't terminating has actually hung in one of the Windows serial port driver functions. outside FSUIPC direct control. LINDA's treatment of VRI devices seems to fare better. Pete

It might be worth posting this on the User Contributions subforum, as a worthwhile reference. You'd need to amend the title to indicate MSFS specifically though, for clarity! Thanks! Pete

You can disable axes in the PFCcom driver (untick the "enable" checkbox for each on the PFCcom calibration screen) if you'd prefer FSUIPC calibration, but I've always found the built-in calibration good enough. Pete

What is "JeeHell"? Is that software which handles EHID? If so, are you running it okay with MSFS? I thought 2Mobiflight" was the software for EHID and cockpitsonic devices? You need some sort of EHID driver. FSUIPC doesn't support EHID itself. Pete

My forward overhead is mostly Cockpitsonic. I think it came with an EHID driver, but I wrote my own instead -- specifically aimed originally at Project Magenta but then revised to work with ProSim737. The interface it uses is 100% via private offsets declared to ProSim. There's no direct link to the simulator itself. I've forgotten most of the details of the interface CockpitSonic provides. The overhead is a collection of over 8 different HID devices, but not type 'Joystick'. The protocol and encoding used withing the HID packets are specific to that hardware, much as GoFlight and Saitek panels use their own HID protocols. I don't really remember any detailed information about the EHID driver, though I have the specfications here somewhere. I never had any EHID-driven hardware actually working directly with the Flight Sim, only via systems programs such as Project Magenta and ProSim. PM already works with MSFS, ProSim will no doubt follow at some time in the future. So the question really comes back to: How are these two devices seen / registered in your sim and FSUIPC at present? Which sim / FSUIPC version are you using? Pete

FSUIPC's support for Lua is for plug-ins -- i.e. Lua programs being executed by FSUIPC and using libraries provided by FSUIPC. That's exactly the same in FSUIPC7.EXE as it is in FSUIPC6.DLL. The fact that FSUIPC7 is an EXE instead of a DLL doesn't affect this at all. If you want to use the Lua language separately, nothing to do with FSUIPC, then of course you can do -- you'd need the Lua compiler or interpreter (see lua.org). Pete

Of course -- different versions of flight sim have needed different versions of FSUIPC. To expand on Thomas's list: FSUIPC7 is for MSFS FSUIPC6 is for P3D4 or P3D5 FSUIPC5 is for P3D4 (but no longer supplied) FSUIPC4 is for FSX and P3D1-3 FSUIPC3 was for FS2004 and possibly before (no longer sold) FSUIPC2 was for FS2002 but now defunct FSUIPC1 was for FS98 and FS2000 also now defunct. Pete

FSUIPC7 is John's work. I'm just assisting occasionally. Pete

Two points here: 1. "offsets" are data repositories. "Buttons" don't have "offsets". An offset is the address of a piece of data, like airspeed, position, etc. "Buttons" cause actions (if assigned and implemented) via controls or events. 2. Many of the events MS have listed in their SDK and which we have faithfully listed for you to assign (in hope) appear not yet to do anything. The idea of releasing FSUIPC7 as a Beta was to collect information on all this for feedback to MS/Asobo. Regarding the G1000, questions have already been asked about these and apparently they are not yet hooked up to the events. So, like many of the switches, dials and buttons on the cockpits, you'll have to resort to using the mouse for the time being. Think of MSFS as being in Beta development still, which it is really. Then you'll always be looking forward to the next update, as are we! Pete

John got it saving flights okay, using the SimConnect facility for this, but the Flights SimConnect saves don't appear to be reloadable at present. They seem type be missing too much and are simply shunned by the load option. Mind you, this was the case last time i tested. Best to test again -- which I will do, but probably after not till the expected update (this week?). Pete

Good. Glad it was so easy! You might now want to check whether that UK2000 Prestwick scenery (and the Common Libraries) are installed okay, and if not trying again with those. Pete

Well, these two entries at the beginning are wrong, they shouldn't be there: [UK2000 Common Library] Active=FALSE [UK2000 Prestwick Xtreme] Active=FALSE I've no idea where they came from. Probably an installer going wrong. Try deleting those first. If still no go, it might be a corrupted Add-Ons xml or cfg file which is clobbering the Lorby program. To check whether this is the case there are two further tests you can do: 1. Temporarily remove the Scenery Export program, then run MakeRwys. That should make files just from those sceneries in the Scenery.CFG file -- none of those using the AddOns methods. 2. Download the freeware Lorby program "AddOnOrganizer" from the Lorby website, and run that. If that manages to list all of your sceneries correctly then that Scenery Export program should do likewise -- it's basically a subset of that program. The Organizer might tell you what is wrong if something still is. Pete

That log unfortunately doesn't show some vital details, such as the version of P3D4 or 5 you are running or the precise Identity of the aircraft. You pressed the "New Log" button, so starting a new log and leaving the old one renamed in the folder. Please don't do that unless asked to. Anyway, let's see: Event 69929 is not a default event or control. The highest number used even by the latest P3D5 is 68120. You appear to be using custom controls specific to the aircraft, much like those provided by the PMDG Boeings. Furthermore, though the Log was intended to show me this, there is no occurrence of control number 69929 in the log!! There are 66917's, with parameters 16777217 (0x01000001) and 16777216 (0x01000000). Not how simple the numbers are in hexadecimal. They appear to be flags so I suspect these are mouse codes. I'm afraid that unless the makers of your aircraft have provided some indication for you to use, or a separate control to simply toggle the switch, you will probably have to find a different way, such as perhaps using two buttons or a latching switch. Pete

I think you’d better show the Log itself, please, so I can make sense of this. You really need to test with a default aircraft because many addons do their own thing but the offset data is sim data, not addon (except for the special cases of the three PMDG Boeing’s) Pete

There is not always a direct relationship between the data values provided in offsets to the events or controls used to handle the aircraft. You need to search by function and be ready to interpret alternative terms for the same things. For a toggle condiition (i.e. one which is either on or off), it might be based on some value, or it may only be represented by a single bit in an array of bits. If you can't locate the values you need, ask specifically and i'll see if I can help. There's no general method. Pete

The problem is with the actual SimConnect code -- the real stuff that does things inside MSFS. The SimConnect.DLL is just the interface to MSFS, and this is still used. It is just that the code for that interface is now compiled into FSUIPC to save you having to find and position another module. Pete

Looks like something is screwed up in your scenery.cfg file. Find that file in your AppData folder for P3D4 and let us see it -- or at least the first 50 lines or so. Pete

Just a quick clarification here/. The PMDG offsets provide DATA for you to display on your hardware, should younkow how to program it. They are not the "controls" you use to program buttons. Control numbers are not the same as offset addresses -- the latter are like mailslots where you find data relating to that address. Pete

These symptoms are all the result of duplicate assignments. I don't know what you've been doing to the INI file, but to make things clearer i've sorted the button assignments list into order of button, with all the "Press" ones before all the "Release" ones. I've highlit all those which are duplicated: 150= PA,0,K192,8 -{Key press: '@key}- 282= PA,0,K192,8 -{Key press: '@key}- 152= PA,14,CM1:4,0 -{Macro PMDG737NGX: Toga}- 111= PA,14,CM1:4,0 -{Macro PMDG737NGX: Toga}- 110= PA,15,CM1:1,0 -{Macro PMDG737NGX: Parkingbrake}- 151= PA,15,CM1:1,0 -{Macro PMDG737NGX: Parkingbrake}- 108= PA,16,CM1:78,0 -{Macro PMDG737NGX: ENG1_MASTER}- 153= PA,16,CM1:78,0 -{Macro PMDG737NGX: ENG1_MASTER}- 113= PA,17,CM1:3,0 -{Macro PMDG737NGX: Transponderdec}- 156= PA,17,CM1:3,0 -{Macro PMDG737NGX: Transponderdec}- 109= PA,18,CM1:79,0 -{Macro PMDG737NGX: ENG2_MASTER}- 154= PA,18,CM1:79,0 -{Macro PMDG737NGX: ENG2_MASTER}- 112= PA,19,CM1:2,0 -{Macro PMDG737NGX: Transponderinc}- 155= PA,19,CM1:2,0 -{Macro PMDG737NGX: Transponderinc}- 157= PC,0,CM1:14,0 -{Macro PMDG737NGX: WHEEL_WELL_LIGHT}- 159= PC,1,CM1:15,0 -{Macro PMDG737NGX: WING_LIGHT}- 176= PC,10,CM1:25,0 -{Macro PMDG737NGX: ENG1_IGN_INC}- 177= PC,11,CM1:24,0 -{Macro PMDG737NGX: ENG1_IGN_DEC}- 179= PC,12,CM1:27,0 -{Macro PMDG737NGX: APU_MASTER_DEC}- 181= PC,13,CM1:26,0 -{Macro PMDG737NGX: APU_MASTER_INC}- 182= PC,14,CM1:28,0 -{Macro PMDG737NGX: TAXI_LIGHT}- 184= PC,15,CM1:29,0 -{Macro PMDG737NGX: R_TURNOFF_LIGHT}- 186= PC,16,CM1:30,0 -{Macro PMDG737NGX: L_TURNOFF_LIGHT}- 188= PC,17,CM1:31,0 -{Macro PMDG737NGX: R_LAND_LIGHT}- 190= PC,18,CM1:32,0 -{Macro PMDG737NGX: L_LAND_LIGHT}- 192= PC,19,CM1:81,0 -{Macro PMDG737NGX: R_LANDRETR_INC}- 161= PC,2,CM1:16,0 -{Macro PMDG737NGX: ANTI_COLL_LIGHT}- 198= PC,20,CM1:80,0 -{Macro PMDG737NGX: R_LANDRETR_DEC}- 196= PC,21,CM1:35,0 -{Macro PMDG737NGX: LEFT_LANDRETR_IN}- 194= PC,22,CM1:36,0 -{Macro PMDG737NGX: LEFT_LANDRETR_DE}- 206= PC,23,CM1:9,0 -{Macro PMDG737NGX: R_Aft_Fuelpump}- 204= PC,24,CM1:8,0 -{Macro PMDG737NGX: R_Fwd_Fuelpump}- 202= PC,25,CM1:7,0 -{Macro PMDG737NGX: L_Fwd_Fuelpump}- 200= PC,26,CM1:6,0 -{Macro PMDG737NGX: L_Aft_Fuelpump}- 210= PC,27,CM1:11,0 -{Macro PMDG737NGX: R_Ctr_Fuelpump}- 208= PC,28,CM1:10,0 -{Macro PMDG737NGX: L_Ctr_Fuelpump}- 213= PC,29,CM1:53,0 -{Macro PMDG737NGX: GRD_CALL}- 165= PC,3,CM1:17,0 -{Macro PMDG737NGX: POS_LIGHT_DEC}- 212= PC,30,CM1:52,0 -{Macro PMDG737NGX: ATTEND}- 163= PC,4,CM1:18,0 -{Macro PMDG737NGX: POS_LIGHT_INC}- 167= PC,5,CM1:19,0 -{Macro PMDG737NGX: LOGO_LIGHT}- 169= PC,6,CM1:20,0 -{Macro PMDG737NGX: ENG2_EGN_INC}- 170= PC,7,CM1:21,0 -{Macro PMDG737NGX: ENG2_IGN_DEC}- 172= PC,8,CM1:23,0 -{Macro PMDG737NGX: IGN_SELECT_INC}- 174= PC,9,CM1:22,0 -{Macro PMDG737NGX: IGN_SELECT_DEC}- 238= PD,0,CM1:54,0 -{Macro PMDG737NGX: L_SIDE_HEAT}- 240= PD,1,CM1:55,0 -{Macro PMDG737NGX: L_FWD_HEAT}- 232= PD,10,CM1:41,0 -{Macro PMDG737NGX: GALLEY}- 234= PD,14,CM1:45,0 -{Macro PMDG737NGX: SUPPLY_EQUIP_COO}- 236= PD,15,CM1:46,0 -{Macro PMDG737NGX: EXHAUST_EQUIP_CO}- 221= PD,16,CM1:47,0 -{Macro PMDG737NGX: EMER_LIGHTS_INC}- 220= PD,17,CM1:48,0 -{Macro PMDG737NGX: EMER_LIGHTS_DEC}- 214= PD,18,CM1:49,0 -{Macro PMDG737NGX: CHIME}- 218= PD,19,CM1:50,0 -{Macro PMDG737NGX: BELTS_INC}- 242= PD,2,CM1:56,0 -{Macro PMDG737NGX: R_FWD_HEAT}- 216= PD,20,CM1:51,0 -{Macro PMDG737NGX: BELTS_DEC}- 114= PD,21,CM1:63,0 -{Macro PMDG737NGX: ENG1_HYD}- 116= PD,22,CM1:66,0 -{Macro PMDG737NGX: ENG2_HYD}- 118= PD,23,CM1:65,0 -{Macro PMDG737NGX: ELEC1}- 256= PD,23,CM1:65,0 -{Macro PMDG737NGX: ELEC1}- 258= PD,24,CM1:64,0 -{Macro PMDG737NGX: ELEC2}- 120= PD,24,CM1:64,0 -{Macro PMDG737NGX: ELEC2}- 246= PD,25,CM1:60,0 -{Macro PMDG737NGX: WING_ANTIICE}- 102= PD,25,CM1:60,0 -{Macro PMDG737NGX: WING_ANTIICE}- 104= PD,26,CM1:61,0 -{Macro PMDG737NGX: ENG1_ANTIICE}- 248= PD,26,CM1:61,0 -{Macro PMDG737NGX: ENG1_ANTIICE}- 250= PD,27,CM1:62,0 -{Macro PMDG737NGX: ENG2_ANTIICE}- 106= PD,27,CM1:62,0 -{Macro PMDG737NGX: ENG2_ANTIICE}- 244= PD,3,CM1:57,0 -{Macro PMDG737NGX: R_SIDE_HEAT}- 252= PD,4,CM1:58,0 -{Macro PMDG737NGX: PROBE1_HEAT}- 254= PD,5,CM1:59,0 -{Macro PMDG737NGX: PROBE2_HEAT}- 100= PD,5,CM1:59,0 -{Macro PMDG737NGX: PROBE2_HEAT}- 122= PD,6,CM1:37,0 -{Macro PMDG737NGX: YAW_DAMPER}- 224= PD,6,CM1:37,0 -{Macro PMDG737NGX: YAW_DAMPER}- 226= PD,7,CM1:38,0 -{Macro PMDG737NGX: ALTERNATE_FL_INC}- 126= PD,7,CM1:38,0 -{Macro PMDG737NGX: ALTERNATE_FL_INC}- 228= PD,8,CM1:39,0 -{Macro PMDG737NGX: ALTERNATE_FL_DEC}- 124= PD,8,CM1:39,0 -{Macro PMDG737NGX: ALTERNATE_FL_DEC}- 230= PD,9,CM1:40,0 -{Macro PMDG737NGX: BATTERY_MASTER}- 146= PE,0,CM1:67,0 -{Macro PMDG737NGX: L_RECIRC_FAN}- 278= PE,0,CM1:67,0 -{Macro PMDG737NGX: L_RECIRC_FAN}- 280= PE,1,CM1:68,0 -{Macro PMDG737NGX: R_RECIRC_FAN}- 148= PE,1,CM1:68,0 -{Macro PMDG737NGX: R_RECIRC_FAN}- 264= PE,10,CM1:77,0 -{Macro PMDG737NGX: ENG2_BLEED}- 132= PE,10,CM1:77,0 -{Macro PMDG737NGX: ENG2_BLEED}- 266= PE,2,CM1:69,0 -{Macro PMDG737NGX: L_PACK_INC}- 134= PE,2,CM1:69,0 -{Macro PMDG737NGX: L_PACK_INC}- 268= PE,3,CM1:70,0 -{Macro PMDG737NGX: L_PACK_DEC}- 136= PE,3,CM1:70,0 -{Macro PMDG737NGX: L_PACK_DEC}- 138= PE,4,CM1:71,0 -{Macro PMDG737NGX: ISOVALVE_INC}- 270= PE,4,CM1:71,0 -{Macro PMDG737NGX: ISOVALVE_INC}- 140= PE,5,CM1:72,0 -{Macro PMDG737NGX: ISOVALVE_DEC}- 272= PE,5,CM1:72,0 -{Macro PMDG737NGX: ISOVALVE_DEC}- 142= PE,6,CM1:73,0 -{Macro PMDG737NGX: R_PACK_INC}- 276= PE,6,CM1:73,0 -{Macro PMDG737NGX: R_PACK_INC}- 274= PE,7,CM1:74,0 -{Macro PMDG737NGX: R_PACK_DEC}- 144= PE,7,CM1:74,0 -{Macro PMDG737NGX: R_PACK_DEC}- 128= PE,8,CM1:75,0 -{Macro PMDG737NGX: ENG1_BLEED}- 260= PE,8,CM1:75,0 -{Macro PMDG737NGX: ENG1_BLEED}- 130= PE,9,CM1:76,0 -{Macro PMDG737NGX: APU_BLEED}- 262= PE,9,CM1:76,0 -{Macro PMDG737NGX: APU_BLEED}- 158= UC,0,CM1:14,0 -{Macro PMDG737NGX: WHEEL_WELL_LIGHT}- 160= UC,1,CM1:15,0 -{Macro PMDG737NGX: WING_LIGHT}- 178= UC,11,CM1:25,0 -{Macro PMDG737NGX: ENG1_IGN_INC}- 180= UC,12,CM1:26,0 -{Macro PMDG737NGX: APU_MASTER_INC}- 183= UC,14,CM1:28,0 -{Macro PMDG737NGX: TAXI_LIGHT}- 185= UC,15,CM1:29,0 -{Macro PMDG737NGX: R_TURNOFF_LIGHT}- 187= UC,16,CM1:30,0 -{Macro PMDG737NGX: L_TURNOFF_LIGHT}- 189= UC,17,CM1:31,0 -{Macro PMDG737NGX: R_LAND_LIGHT}- 191= UC,18,CM1:32,0 -{Macro PMDG737NGX: L_LAND_LIGHT}- 193= UC,19,CM1:80,0 -{Macro PMDG737NGX: R_LANDRETR_DEC}- 162= UC,2,CM1:16,0 -{Macro PMDG737NGX: ANTI_COLL_LIGHT}- 199= UC,20,CM1:81,0 -{Macro PMDG737NGX: R_LANDRETR_INC}- 197= UC,21,CM1:36,0 -{Macro PMDG737NGX: LEFT_LANDRETR_DE}- 195= UC,22,CM1:35,0 -{Macro PMDG737NGX: LEFT_LANDRETR_IN}- 207= UC,23,CM1:9,0 -{Macro PMDG737NGX: R_Aft_Fuelpump}- 205= UC,24,CM1:8,0 -{Macro PMDG737NGX: R_Fwd_Fuelpump}- 203= UC,25,CM1:7,0 -{Macro PMDG737NGX: L_Fwd_Fuelpump}- 201= UC,26,CM1:6,0 -{Macro PMDG737NGX: L_Aft_Fuelpump}- 211= UC,27,CM1:11,0 -{Macro PMDG737NGX: R_Ctr_Fuelpump}- 209= UC,28,CM1:10,0 -{Macro PMDG737NGX: L_Ctr_Fuelpump}- 166= UC,3,CM1:18,0 -{Macro PMDG737NGX: POS_LIGHT_INC}- 164= UC,4,CM1:17,0 -{Macro PMDG737NGX: POS_LIGHT_DEC}- 168= UC,5,CM1:19,0 -{Macro PMDG737NGX: LOGO_LIGHT}- 171= UC,7,CM1:20,0 -{Macro PMDG737NGX: ENG2_EGN_INC}- 173= UC,8,CM1:22,0 -{Macro PMDG737NGX: IGN_SELECT_DEC}- 175= UC,9,CM1:23,0 -{Macro PMDG737NGX: IGN_SELECT_INC}- 239= UD,0,CM1:54,0 -{Macro PMDG737NGX: L_SIDE_HEAT}- 241= UD,1,CM1:55,0 -{Macro PMDG737NGX: L_FWD_HEAT}- 233= UD,10,CM1:41,0 -{Macro PMDG737NGX: GALLEY}- 235= UD,14,CM1:45,0 -{Macro PMDG737NGX: SUPPLY_EQUIP_COO}- 237= UD,15,CM1:46,0 -{Macro PMDG737NGX: EXHAUST_EQUIP_CO}- 222= UD,16,CM1:48,0 -{Macro PMDG737NGX: EMER_LIGHTS_DEC}- 223= UD,17,CM1:47,0 -{Macro PMDG737NGX: EMER_LIGHTS_INC}- 215= UD,18,CM1:49,0 -{Macro PMDG737NGX: CHIME}- 219= UD,19,CM1:51,0 -{Macro PMDG737NGX: BELTS_DEC}- 243= UD,2,CM1:56,0 -{Macro PMDG737NGX: R_FWD_HEAT}- 217= UD,20,CM1:50,0 -{Macro PMDG737NGX: BELTS_INC}- 115= UD,21,CM1:63,0 -{Macro PMDG737NGX: ENG1_HYD}- 117= UD,22,CM1:66,0 -{Macro PMDG737NGX: ENG2_HYD}- 119= UD,23,CM1:65,0 -{Macro PMDG737NGX: ELEC1}- 257= UD,23,CM1:65,0 -{Macro PMDG737NGX: ELEC1}- 121= UD,24,CM1:64,0 -{Macro PMDG737NGX: ELEC2}- 259= UD,24,CM1:64,0 -{Macro PMDG737NGX: ELEC2}- 247= UD,25,CM1:60,0 -{Macro PMDG737NGX: WING_ANTIICE}- 103= UD,25,CM1:60,0 -{Macro PMDG737NGX: WING_ANTIICE}- 105= UD,26,CM1:61,0 -{Macro PMDG737NGX: ENG1_ANTIICE}- 249= UD,26,CM1:61,0 -{Macro PMDG737NGX: ENG1_ANTIICE}- 107= UD,27,CM1:62,0 -{Macro PMDG737NGX: ENG2_ANTIICE}- 251= UD,27,CM1:62,0 -{Macro PMDG737NGX: ENG2_ANTIICE}- 245= UD,3,CM1:57,0 -{Macro PMDG737NGX: R_SIDE_HEAT}- 253= UD,4,CM1:58,0 -{Macro PMDG737NGX: PROBE1_HEAT}- 101= UD,5,CM1:59,0 -{Macro PMDG737NGX: PROBE2_HEAT}- 255= UD,5,CM1:59,0 -{Macro PMDG737NGX: PROBE2_HEAT}- 225= UD,6,CM1:37,0 -{Macro PMDG737NGX: YAW_DAMPER}- 123= UD,6,CM1:37,0 -{Macro PMDG737NGX: YAW_DAMPER}- 127= UD,7,CM1:39,0 -{Macro PMDG737NGX: ALTERNATE_FL_DEC}- 227= UD,7,CM1:39,0 -{Macro PMDG737NGX: ALTERNATE_FL_DEC}- 229= UD,8,CM1:38,0 -{Macro PMDG737NGX: ALTERNATE_FL_INC}- 125= UD,8,CM1:38,0 -{Macro PMDG737NGX: ALTERNATE_FL_INC}- 231= UD,9,CM1:40,0 -{Macro PMDG737NGX: BATTERY_MASTER}- 147= UE,0,CM1:67,0 -{Macro PMDG737NGX: L_RECIRC_FAN}- 279= UE,0,CM1:67,0 -{Macro PMDG737NGX: L_RECIRC_FAN}- 281= UE,1,CM1:68,0 -{Macro PMDG737NGX: R_RECIRC_FAN}- 149= UE,1,CM1:68,0 -{Macro PMDG737NGX: R_RECIRC_FAN}- 265= UE,10,CM1:77,0 -{Macro PMDG737NGX: ENG2_BLEED}- 133= UE,10,CM1:77,0 -{Macro PMDG737NGX: ENG2_BLEED}- 135= UE,2,CM1:70,0 -{Macro PMDG737NGX: L_PACK_DEC}- 267= UE,2,CM1:70,0 -{Macro PMDG737NGX: L_PACK_DEC}- 269= UE,3,CM1:69,0 -{Macro PMDG737NGX: L_PACK_INC}- 137= UE,3,CM1:69,0 -{Macro PMDG737NGX: L_PACK_INC}- 139= UE,4,CM1:72,0 -{Macro PMDG737NGX: ISOVALVE_DEC}- 271= UE,4,CM1:72,0 -{Macro PMDG737NGX: ISOVALVE_DEC}- 273= UE,5,CM1:71,0 -{Macro PMDG737NGX: ISOVALVE_INC}- 141= UE,5,CM1:71,0 -{Macro PMDG737NGX: ISOVALVE_INC}- 277= UE,6,CM1:74,0 -{Macro PMDG737NGX: R_PACK_DEC}- 143= UE,6,CM1:74,0 -{Macro PMDG737NGX: R_PACK_DEC}- 145= UE,7,CM1:73,0 -{Macro PMDG737NGX: R_PACK_INC}- 275= UE,7,CM1:73,0 -{Macro PMDG737NGX: R_PACK_INC}- 261= UE,8,CM1:75,0 -{Macro PMDG737NGX: ENG1_BLEED}- 129= UE,8,CM1:75,0 -{Macro PMDG737NGX: ENG1_BLEED}- 131= UE,9,CM1:76,0 -{Macro PMDG737NGX: APU_BLEED}- 263= UE,9,CM1:76,0 -{Macro PMDG737NGX: APU_BLEED}- 7= PC,0,CM1:14,0 -{Macro PMDG737NGX: WHEEL_WELL_LIGHT}- 9= PC,1,CM1:15,0 -{Macro PMDG737NGX: WING_LIGHT}- 29= PC,11,CM1:24,0 -{Macro PMDG737NGX: ENG1_IGN_DEC}- 32= PC,12,CM1:27,0 -{Macro PMDG737NGX: APU_MASTER_DEC}- 31= PC,13,CM1:26,0 -{Macro PMDG737NGX: APU_MASTER_INC}- 34= PC,14,CM1:28,0 -{Macro PMDG737NGX: TAXI_LIGHT}- 36= PC,15,CM1:29,0 -{Macro PMDG737NGX: R_TURNOFF_LIGHT}- 38= PC,16,CM1:30,0 -{Macro PMDG737NGX: L_TURNOFF_LIGHT}- 40= PC,17,CM1:31,0 -{Macro PMDG737NGX: R_LAND_LIGHT}- 42= PC,18,CM1:32,0 -{Macro PMDG737NGX: L_LAND_LIGHT}- 44= PC,19,CM1:33,0 -{Macro PMDG737NGX: R_RETRLAND_INC}- 11= PC,2,CM1:16,0 -{Macro PMDG737NGX: ANTI_COLL_LIGHT}- 46= PC,20,CM1:34,0 -{Macro PMDG737NGX: L_RETRLAND_DEC}- 48= PC,21,CM1:35,0 -{Macro PMDG737NGX: LEFT_LANDRETR_IN}- 50= PC,22,CM1:36,0 -{Macro PMDG737NGX: LEFT_LANDRETR_DE}- 52= PC,23,CM1:9,0 -{Macro PMDG737NGX: R_Aft_Fuelpump}- 54= PC,24,CM1:8,0 -{Macro PMDG737NGX: R_Fwd_Fuelpump}- 56= PC,25,CM1:7,0 -{Macro PMDG737NGX: L_Fwd_Fuelpump}- 58= PC,26,CM1:6,0 -{Macro PMDG737NGX: L_Aft_Fuelpump}- 60= PC,27,CM1:11,0 -{Macro PMDG737NGX: R_Ctr_Fuelpump}- 62= PC,28,CM1:10,0 -{Macro PMDG737NGX: L_Ctr_Fuelpump}- 65= PC,29,CM1:53,0 -{Macro PMDG737NGX: GRD_CALL}- 13= PC,3,CM1:17,0 -{Macro PMDG737NGX: POS_LIGHT_DEC}- 64= PC,30,CM1:52,0 -{Macro PMDG737NGX: ATTEND}- 15= PC,4,CM1:18,0 -{Macro PMDG737NGX: POS_LIGHT_INC}- 17= PC,5,CM1:19,0 -{Macro PMDG737NGX: LOGO_LIGHT}- 19= PC,6,CM1:20,0 -{Macro PMDG737NGX: ENG2_EGN_INC}- 21= PC,7,CM1:21,0 -{Macro PMDG737NGX: ENG2_IGN_DEC}- 25= PC,8,CM1:23,0 -{Macro PMDG737NGX: IGN_SELECT_INC}- 23= PC,9,CM1:22,0 -{Macro PMDG737NGX: IGN_SELECT_DEC}- 80= PD,0,CM1:54,0 -{Macro PMDG737NGX: L_SIDE_HEAT}- 82= PD,1,CM1:55,0 -{Macro PMDG737NGX: L_FWD_HEAT}- 90= PD,10,CM1:41,0 -{Macro PMDG737NGX: GALLEY}- 94= PD,11,CM1:43,0 -{Macro PMDG737NGX: DISCONNECT_1_PWR}- 92= PD,12,CM1:42,0 -{Macro PMDG737NGX: STBY_POWER}- 76= PD,14,CM1:45,0 -{Macro PMDG737NGX: SUPPLY_EQUIP_COO}- 78= PD,15,CM1:46,0 -{Macro PMDG737NGX: EXHAUST_EQUIP_CO}- 72= PD,16,CM1:47,0 -{Macro PMDG737NGX: EMER_LIGHTS_INC}- 74= PD,17,CM1:48,0 -{Macro PMDG737NGX: EMER_LIGHTS_DEC}- 66= PD,18,CM1:49,0 -{Macro PMDG737NGX: CHIME}- 68= PD,19,CM1:50,0 -{Macro PMDG737NGX: BELTS_INC}- 84= PD,2,CM1:56,0 -{Macro PMDG737NGX: R_FWD_HEAT}- 70= PD,20,CM1:51,0 -{Macro PMDG737NGX: BELTS_DEC}- 86= PD,3,CM1:57,0 -{Macro PMDG737NGX: R_SIDE_HEAT}- 98= PD,4,CM1:58,0 -{Macro PMDG737NGX: PROBE1_HEAT}- 88= PD,9,CM1:40,0 -{Macro PMDG737NGX: BATTERY_MASTER}- 27= RC,10,CM1:25,0 -{Macro PMDG737NGX: ENG1_IGN_INC}- 8= UC,0,CM1:14,0 -{Macro PMDG737NGX: WHEEL_WELL_LIGHT}- 10= UC,1,CM1:15,0 -{Macro PMDG737NGX: WING_LIGHT}- 30= UC,11,CM1:25,0 -{Macro PMDG737NGX: ENG1_IGN_INC}- 33= UC,12,CM1:26,0 -{Macro PMDG737NGX: APU_MASTER_INC}- 35= UC,14,CM1:28,0 -{Macro PMDG737NGX: TAXI_LIGHT}- 37= UC,15,CM1:29,0 -{Macro PMDG737NGX: R_TURNOFF_LIGHT}- 39= UC,16,CM1:30,0 -{Macro PMDG737NGX: L_TURNOFF_LIGHT}- 41= UC,17,CM1:31,0 -{Macro PMDG737NGX: R_LAND_LIGHT}- 43= UC,18,CM1:32,0 -{Macro PMDG737NGX: L_LAND_LIGHT}- 45= UC,19,CM1:34,0 -{Macro PMDG737NGX: L_RETRLAND_DEC}- 12= UC,2,CM1:16,0 -{Macro PMDG737NGX: ANTI_COLL_LIGHT}- 47= UC,20,CM1:33,0 -{Macro PMDG737NGX: R_RETRLAND_INC}- 49= UC,21,CM1:36,0 -{Macro PMDG737NGX: LEFT_LANDRETR_DE}- 51= UC,22,CM1:35,0 -{Macro PMDG737NGX: LEFT_LANDRETR_IN}- 53= UC,23,CM1:9,0 -{Macro PMDG737NGX: R_Aft_Fuelpump}- 55= UC,24,CM1:8,0 -{Macro PMDG737NGX: R_Fwd_Fuelpump}- 57= UC,25,CM1:7,0 -{Macro PMDG737NGX: L_Fwd_Fuelpump}- 59= UC,26,CM1:6,0 -{Macro PMDG737NGX: L_Aft_Fuelpump}- 61= UC,27,CM1:11,0 -{Macro PMDG737NGX: R_Ctr_Fuelpump}- 63= UC,28,CM1:10,0 -{Macro PMDG737NGX: L_Ctr_Fuelpump}- 14= UC,3,CM1:18,0 -{Macro PMDG737NGX: POS_LIGHT_INC}- 16= UC,4,CM1:17,0 -{Macro PMDG737NGX: POS_LIGHT_DEC}- 18= UC,5,CM1:19,0 -{Macro PMDG737NGX: LOGO_LIGHT}- 22= UC,7,CM1:20,0 -{Macro PMDG737NGX: ENG2_EGN_INC}- 26= UC,8,CM1:22,0 -{Macro PMDG737NGX: IGN_SELECT_DEC}- 24= UC,9,CM1:23,0 -{Macro PMDG737NGX: IGN_SELECT_INC}- 81= UD,0,CM1:54,0 -{Macro PMDG737NGX: L_SIDE_HEAT}- 83= UD,1,CM1:55,0 -{Macro PMDG737NGX: L_FWD_HEAT}- 91= UD,10,CM1:41,0 -{Macro PMDG737NGX: GALLEY}- 93= UD,12,CM1:42,0 -{Macro PMDG737NGX: STBY_POWER}- 97= UD,13,CM1:44,0 -{Macro PMDG737NGX: DISCONNECT_2_PWR}- 77= UD,14,CM1:45,0 -{Macro PMDG737NGX: SUPPLY_EQUIP_COO}- 79= UD,15,CM1:46,0 -{Macro PMDG737NGX: EXHAUST_EQUIP_CO}- 73= UD,16,CM1:48,0 -{Macro PMDG737NGX: EMER_LIGHTS_DEC}- 75= UD,17,CM1:47,0 -{Macro PMDG737NGX: EMER_LIGHTS_INC}- 67= UD,18,CM1:49,0 -{Macro PMDG737NGX: CHIME}- 69= UD,19,CM1:51,0 -{Macro PMDG737NGX: BELTS_DEC}- 85= UD,2,CM1:56,0 -{Macro PMDG737NGX: R_FWD_HEAT}- 71= UD,20,CM1:50,0 -{Macro PMDG737NGX: BELTS_INC}- 87= UD,3,CM1:57,0 -{Macro PMDG737NGX: R_SIDE_HEAT}- 99= UD,4,CM1:58,0 -{Macro PMDG737NGX: PROBE1_HEAT}- 89= UD,9,CM1:40,0 -{Macro PMDG737NGX: BATTERY_MASTER}- I suggest you start off by deleting one copy of each duplicate. You can edit or change multiple assignments to the same button or switch in the Options dialogues. I also have a question. You seem to be using an very large number of Macros. I wonder why? There are <custom controls> for every switch in a PMDG aircraft. I don't know if your macros are using those, but if so why the indirect method via macros? Is it just so you have a recognisable name instead of a number? And, if you aren't using the controls supplied by PMDG, why not? Pete