John Dowson

Checked this and it is invalid - its only 11 characters when it should be 12....! Not sure how that happened, but I will generate a new key for you, check it an send it to you via a PM. However, this will have to be tomorrow now as my win7/keygen system is currently not available. Sorry about this. I will look into what happened. John

I will move this post to that forum and update the title....

I don't have or know much about the ProSim A320 so I can't help much with this unfortunately. I suggest you either ask on the prosim forums, or create a new topic in the main FSUIPC support forum (https://forum.simflight.com/forum/30-fsuipc-support-pete-dowson-modules/) with an appropriate title to attract other ProSim A320/FSUIPC6 users. Well, they are available in the FBW A320.... Cheers, John

Only parking lights working on the annunciator panel, and only the HDG and VS buttons light up on the AP. Not sure why yet.

I only checked gear and parking lights, will check the others later. Ah, sorry - you mean the AP/FCU button lights...I don't think I ever had those working, but I will check as well... John

There is also Nav Lights Set, which you can use with a parameter of 1 or 0 for on and off respectfully.

Yes, its a known problem with some virus scanners. It will be a false positive - add an exception or disable while you install. John

Sorry, but I'm not sure I understand. Can you explain exactly what you are doing? You need to press/click the Set button, then press the keys that you wish to assign to that button (jpystick#0 button #21). Which keys are you trying to assign? Which version of FSUIPC5 or FSUIPC6 are you using? Make sure that it is the latest version (available from www.fsuipc.com) of the product you are using, as I can only support the latest versions. John

So the gear light isn't working? Seems ok for me - which a/c are you using? There aren't any IAS or ALT lights on the bravo - or are you talking about the buttons? If so, I need to see how you have those assigned. If using a lua script for those, then you need to contact the script provider - i.e. comment on the post where you got it from. I can't support 3rd party scripts. John

I'm sorry, but how is that misleading? It means the forum is not for support requests....how can I make that more understandable? And/or? I'm sorry, but they are very different and will (most probably) need different configurations.... An offset for what? All offsets are documented in the offset status document. For what you call FS11, and I (and most people) refer to as MSFS2020, then please see the addtional offset spreadsheet included in the downloadable zip. There are some specific offets for the A320 in FSUIPC7, but not related to ADIRS. If talking about FSUIPC7, then yes, they are available via the FSUIPC7 WASM module, with the WAPI enabled. Please see the user guides provided (or the many support forum questions). I can answer specific questions if you let me know the FSUIPC version, FS version and aircraft that you are using...or try to... Note I do not have the FS LABs A320, or any PMDG aircraft. But I still support these if using FSUIPC, but I need to know the details, i.e. which FSUIPC version, which FS, which aircraft. And please consult the manuals and search the support forum for similar questions before posting. And, when you post, please give as much info as possible. For example, for ADIRS knobs in the FBWE A320, I see these LVARS/Valculator code are available: Input L A32NX_ADIRS_KNOB_1 0 OFF ADIRS 1 KNOB - OFF INCORRECT INTERNAL VARIABLE. Right one is (>L:A32NX_OVHD_ADIRS_IR_1_MODE_SELECTOR_KNOB) Input L A32NX_ADIRS_KNOB_1 1 NAV ADIRS 1 KNOB - NAV INCORRECT INTERNAL VARIABLE. Right one is (>L:A32NX_OVHD_ADIRS_IR_1_MODE_SELECTOR_KNOB) Input L A32NX_ADIRS_KNOB_1 2 ATT ADIRS 1 KNOB - ATT INCORRECT INTERNAL VARIABLE. Right one is (>L:A32NX_OVHD_ADIRS_IR_1_MODE_SELECTOR_KNOB) Input L A32NX_ADIRS_KNOB_2 0 OFF ADIRS 2 KNOB - OFF INCORRECT INTERNAL VARIABLE. Right one is (>L:A32NX_OVHD_ADIRS_IR_2_MODE_SELECTOR_KNOB) Input L A32NX_ADIRS_KNOB_2 1 NAV ADIRS 2 KNOB - NAV INCORRECT INTERNAL VARIABLE. Right one is (>L:A32NX_OVHD_ADIRS_IR_2_MODE_SELECTOR_KNOB) Input L A32NX_ADIRS_KNOB_2 2 ATT ADIRS 2 KNOB - ATT INCORRECT INTERNAL VARIABLE. Right one is (>L:A32NX_OVHD_ADIRS_IR_2_MODE_SELECTOR_KNOB) Input L A32NX_ADIRS_KNOB_3 0 OFF ADIRS 3 KNOB - OFF INCORRECT INTERNAL VARIABLE. Right one is (>L:A32NX_OVHD_ADIRS_IR_3_MODE_SELECTOR_KNOB) Input L A32NX_ADIRS_KNOB_3 1 NAV ADIRS 3 KNOB - NAV INCORRECT INTERNAL VARIABLE. Right one is (>L:A32NX_OVHD_ADIRS_IR_3_MODE_SELECTOR_KNOB) Input L A32NX_ADIRS_KNOB_3 2 ATT ADIRS 3 KNOB - ATT INCORRECT INTERNAL VARIABLE. Right one is (>L:A32NX_OVHD_ADIRS_IR_3_MODE_SELECTOR_KNOB) Thats from the MobiFlight spreadsheet - see https://docs.google.com/spreadsheets/d/1jTXlcHaJWx0B7TB63Pmma7bKwpxsxXJO6EJ3ECt7zpc/edit#gid=172455454 John

The BravoLeds.lua version I am using seems to be working as expected (but only checked parking and gear lights, but others should be ok...). Not sure what BravoButtons lua you are using (or why you need it!), but the bravo rotaries script I am using also seems to be working as expected. Can you check your luas are actually running? I can post the ones I use if interested - probably the same as the ones available (the leds one) except maybe for additional logging that I have added (so that I can see in the log when it starts/stops). John

No. You can check the User Contributions section for various lua throttle scripts, but I'm not sure if those will be of any help. Best to just try setting it up yourself initially. But why use the inc/dec controls rather than the axes controls? Or are you assigning the inc/dec to buttons? For the FSL A320, also see John

First, you posted in the User Contributions sub-forum. That is not the place for support requests - I have moved your post for you. Please take care to post in the correct forum for support for future requests - here for FSUIPC7 or the main support forum for all other FSUIPC products. Which version of FSUIPC are you using? What A3XX? Is this a stock aircraft or an add-on or mod? Have you checked available Lvars? And also hvars, if using FSUIPC7.

Just noticed this on the Asobo forums, so may be a problem with the SU5 update: https://forums.flightsimulator.com/t/altimeter-problems-altitude-hold-and-atc-altitude/433209 https://forums.flightsimulator.com/t/help-with-incorrect-high-altitude-altimeter-setting/429439/4 John

You can still use LINDA with FSUIPC5 and P3Dv4.5. You can upgrade to FSUIPC6 if you like, but it is not needed. However, you should at least upgrade to the latest version of FSUIPC5, which is 5.157. If you decide to upgrade to FSUIPC6, you will automatically get a discount on checkout as you already have an FSUIPC5 license, John

Still downloading/installing the latest update on my flight system, so I'll check this later. In the mean time, you could try the latest version rebuilt using the latest SDK (0.14.0.0) which is available here: John

Your macro file is not correct. You are missing the initial line that must contain: [Macros] And your macro lines do not contain the Set command (see P36 Macros to activate Hvars). Try the attached macro file. John Fairing.mcro

I don't know where IVAO and VATSIM take the altitude information. FSUIPC holds the altitude in various offsets, e.g. 0x0570 - Plane Altitude 0x3324 - Indicated Altitude (Altemeter reading) I have not had any reports of these offsets being incorrect, but I'll check them. I'm currently having some issues downloading/installing the latest update, but I'll check once resolved. John

As well as what Pete has said, I think for the FBW A320 you need to initially set-up the throttle via the flypad/EFB. See, for example, For the DC6, you should try the *_EX1 throttle controls, i.e. THROTTLE_AXIS_SET_EX1, or THROTTLE1_AXIS_SET_EX1 THROTTLE2_AXIS_SET_EX1 ...etc You can also try activating logging for Events and Axis Controls, then move the throttle in the UI to see what events/controls are logged, and then use those. For a full list of the controls/events, see the Controls List for MSFS Build 999.txt document which is generated when you run FSUIPC7 and located under your Documents folder in an FSUIPC7 folder, with the rest of the FSUIPC7 documentation. John

Please try the attached version, v7.2.5a. This version has been updated to SDK 0.14.0.0, and offset 0x3124 can be used to determine the connection status - it will contain 0 when disconnected and 110 (currently) when connected. I have also added some new events from the legacy gauges.h, but I still need to revise/update to the latest SimEvent status documentation. John FSUIPC7.exe

Offset 0x3124 (FS version) is set (to 110) when connected to the sim. I will i[date this offset to show the correct version and also reset this to 0 when disconnected, so that it can be used to monitor the connection state. SDK 0.14.0.0 has just been released, so I'll include this once I have updated to the latest SDK. I will update and release in the next few days.

@thomasl123 Also, please do not hijack unrelated threads. This thread was for an issue with the [Programs] section which is now resolved. I will now lock this thread.

That looks like a fault in FSUIPC7 as MSFS has crashed. Check your FSUIPC7.log file and it will probably have exited normally when MSFS crashed. A fault is generated as the simconnect connection is no longer available. If you look for other events, there will most probably be an MSFS CTD event before the FSUIPC7 one. If you don't think that is the case, please show me your FSUIPC7.log file.

BUS LOOKUP INDEX is read-only. This value changes when other controls are used, e.g. ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE. I added this to see if it could be used to control the batteries in the A320 as described in this post: However, it seems that these simvars are read-only Presumably you are trying to control the batteries in the FBW A320, no? If so, you can try the calculator code specified in the MF spreadsheet for A32NX_OH_ELEC_BAT1_TOG 10 6 (>K:2:ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE) 10 (>A:BUS LOOKUP INDEX, Number) (A:BUS CONNECTION ON:6, Bool) ! if{ 0 } els{ 1 } (>L:A32NX_OVHD_ELEC_BAT_10_PB_IS_AUTO) (L:XMLVAR_Momentary_PUSH_OVHD_ELEC_BAT1_Pressed) ! (>L:XMLVAR_Momentary_PUSH_OVHD_ELEC_BAT1_Pressed) A32NX_OH_ELEC_BAT2_TOG 11 6 (>K:2:ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE) 11 (>A:BUS LOOKUP INDEX, Number) (A:BUS CONNECTION ON:6, Bool) ! if{ 0 } els{ 1 } (>L:A32NX_OVHD_ELEC_BAT_11_PB_IS_AUTO) (L:XMLVAR_Momentary_PUSH_OVHD_ELEC_BAT2_Pressed) ! (>L:XMLVAR_Momentary_PUSH_OVHD_ELEC_BAT2_Pressed) (see https://docs.google.com/spreadsheets/d/1jTXlcHaJWx0B7TB63Pmma7bKwpxsxXJO6EJ3ECt7zpc/edit#gid=172455454) My MSFS is updating at the moment (and still 30GB to go....) so can't test this, will check it later. John

Is there an FSUIPC4.log file in your FSUIPC4 installation folder, i.e. under C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules ? If so, can you please show it to us? Thanks, John