John Dowson

Just checked and it is working here. However, it is extremely slow. If you hold your button(s) down (to send the control repeatedly), then you should see the elevator pitch trim indicator move. If you want larger trim increments/decrements (deltas) for each button press/release, you can assign to the trim offset 0x0BC0 using the offset sword increment/decrement controls, and give the inc/dec delta that works for you. Alternatively, if you have a spare axis, you can assign to the Axis Elevator Trim Set control. You can also duplicate your assignment lines (remembering to change the index number) to have (say) 10 controls sent upon each button press (by duplicating 10 times) and release (if you also assign the control to be sent on release as well). John

Please attach it next time - its a lot easier and there is nothing in there that can't be public. Ok, but this makes no difference to how FSUIPC behaves, only how it is started by P3D. But what I need to see is your log, with the appropriate logging activated (as asked). Can you please attach that (not via PM please!). John PS. I'll also check the trim on the Mooney here....

What error message? Do you have an FSUIPC7.log file? If so, please show it to me. If its a windows error message, see the README.txt provided. Note that there is also an issue with lvar/hvar access in v7.2.5, there is an updated version available from the following link (that I will release shortly):

No change in ipc.display(), but there is an issue with lvar/hvar access in that version. There is an updated version here (that I will release officially shorty):

@LeoSchoonbroodt Please try the attached version: FSUIPC7.exe Seems ok, but I'll do more tests and release officially tomorrow. John

Yes, I have just noticed this after updating on my flight system. Mot sure what happened...I am looking into it now... Sorry about this. John

Those assignments have everything assigned to buttons 3 and 2. Your images show buttons 8 and 9 (with the same control for each). Just do as the OP suggests, and change the button numbers to the ones you want to use, e.g. change the 2 to 8 for engine 1, and the 3 for 9 for engine 2. You should also manually remove any original assignments you have to those buttons numbers as they will be no longer needed. Note also that the FSUIPC assignments window will only show one assignment if you have multiple, and will be grayed out so it cannot be changed. You can only update by manually editing the ini - and once you do this, click the 'Reload all buttons button to reload the modified ini file. John

How is your trim assigned? Can you activate logging for buttons, Events and maybe also Axes controls, load the Mooney Bravo and then try to adjust the trim, then close down P3D and show me your FSUIPC6.log and FSUIPC6.ini files. I'm surprised at this though - could it be that the buttons that you use are outside of the 32 button limit (in FSUIPC5) and you are using lua toggle a virtual button instead? If that is the case, you will either need to re-assign your trim buttons, or add the following to the [General] section of your FSUIPC6.ini file to revert to the old 32-button limit behavior: EnableExtraButtons=No No - by doing that you will be using the default P3D assignments, which will also mean that all your other axes/buttons will/could also be assigned in P3D, which would give you dual assignments. Best to still leave controllers turned off in P3D if using FSUIPC for your assignments. John

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