John Dowson

Yes of course! Deselecting the auto-start component implies that FSUIPC will not be auto-started with the FS (the MSFS EXE.xml file will not be updated). You can then just start FSUIPC7 manually when you want to use it. Alternatively, as described above, you can edit the MSFS.bat file to uncomment the startup of MSFS, then the MSFS desktop link (created by the FSUIPC7 installer) can be used if you want to start both MSFS and FSUIPC7, or you can start the FS from the start menu to run without FSUIPC7. John

Maybe try the *_EX1 throttle controls. See this post: John

No problem - glad its now working! Cheers, John

The double colons (comment delimiters) are currently always there - they need to be removed if you want to use the old method of starting MSFS from the .bat file. I am not going to update the installation process (at the moment at least) to allow different start-up methods to be used - I think it would complicate the installation process too much for most users. I am thinking about removing the uninstallation step from the install process at some point, or making this optional, as its not really needed for FSUIPC7 and is a hangover from the FSUIPC6 installation process. Not sure when I will get around to looking at this though.... Cheers, John

You don't normally need/want this checked for on/off light assignments.... John

@wahid I have PM'ed you a new key (and .key file) to use. John

You mean the acars programs are not connecting to FSUIPC.... Did you get MSFS in a ready-to-fly state, i.e. with an aircraft selected, loaded and ready-to-fly? Please try the latest beta, to be released shortly, but currently available here: There seem to be various issues since update SU5 but I haven't had time to look into these yet. Will start tomorrow. Yes, your FSUIPC7.log file, located under your FSUIPC7 installation folder. John

Yes, I know - me too! Unfortunately I haven't had time to look into things properly yet, I will start checking things tomorrow... Do they start once you are 'ready-to-fly', or not at all? I made some changes in the latest versions to start luas later, when ready-to-fly, as this is needed if they access lvars. This may also imply that the run programs start later, but I'm not sure. I will check in the next few days and get back to you/ Btw, also try the latest FSUIPC7 version that has been rebuilt against the latest SDK, 0.14.0.0, available here at the moment: I will release this in a full official release shortly, hopefully tomorrow. John

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