John Dowson

No, this is not possible. It is MSFS that starts FSUIPC7, via the EXE.xml. Why do you want to do this? It shouldn't matter when FSUIPC7 is started... If you really want to do this, it should be relatively easy to implement yourself. You can change the auto-start entry in the EXE.xml that starts FSUIPC7 to start your own batch script, and in that script you can add a delay and then start FSUIPC7. I am puzzled as to why you would want to do this though. John

What were you asking for then? You certainly weren't providing an entry for the FAQ section....! The FAQ section is where you (but usually me!) can post answers to frequently asked questions and problems, not a place to ask questions., frequent or not! Cheers, John

There is no uninstall for FSUIPC4 - to uninstall you can just delete it. As this is just for testing, you can just rename the FSUIPC4.dll, to something like FSUIPC4.dll.unused. You can then just rename again when you want to use. John

License sent.

I have moved our post from the FAQ sub-forum, where it explicitly states NOT for support requests, to the main support forum. Please take care to post for support in the correct place. John

Can you show me your FSUIPC4.ini file please. If the lua file appears in the drop down for assignment, then it is available for use, and must be installed. You would normally have this lua file auto-started - please see the Advanced User guide on how to do this. You also need to edit the file to specify the joystick (Vendor and Product) and rotary button numbers (Rotaries) that you wish to use it with. So open it in an editor and take a look and make the necessary changes. John

Please see the provided documentation for such questions - in page 13 of the User guidel John

Yes, there are two ways to do this. The easiest way is to assign one to be started on the button press, and the second on the button release. If you want them both assigned on the button press, assign the first one and click ok. Then, open the button assignments panel again, and open your FSUIPC7.ini file in a text editor. Find the line for the assignment you just made to start the first lua, and comment this out by placing a semi-colon after the equals sign. Then, in the button assignments panel, click the 'Reload all buttons' button. You can then assign the button to start the second lua, and click Ok. Open the button assignments panel again, then go back to the editor, reload the updated FSUIPC7.ini file and remove the semi-colon you previously added and save the file. Finally, in the button assignments panel, click 'Reload all buttons' again. You now have multiple assignments to that button. You can no longer edit/change these via the UI, and only one assignment will be shown greyed-out. You can have as many assignments as you want on a button or keystroke using this method. John

Your installation log shows that this location was taken from the registry and was used as this was where it was previously installed. You could try uninstalling first before running the installer - you can do this from the windows app management panel, or running the uninstaller manually. This will clear the registry first and you can then do a fresh install. If that doesn't fix it, it means that this registry string is wrong: [HKCU] SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders Personal That is where the documents location is taken from. You will need to correct that, or just manually move the Documents folder to the correct location. John

I'll PM you.

The name/email doesn't really matter - they are not used for anything apart from validating the key. So there is really no need to change this. As your license purchase states for 15 users, you can just go-ahead and install this for up to 15 (distinct) users. If you have 15 seats but a rotating user base, you would need 15 commercial seat licenses, not the standard user license. As I said, commercial licenses depend upon use. It would be helpful to me if you could clarify your use for these 15 licenses. John

Installing FSX and/or FSUIPC4 should in no way affect your P3Dv4 / FSUIPC5/6 installation. You should raise a separate support request for this, giving the issue details and attach your FSUIPC ini and log files. John

You have purchased 15 licenses, so you can use that license in up to 15 installations, for 15 distinct users, None-commercial license are user based, so one license is valid for one user (in multiple installations). I am not sure what your use is - maybe you require commercial licenses? Commercial licenses are per seat, with unlimited users per seat. For commercial licenses, you need to contact me and specify your requirements as the price varies depending upon actual use. You currently have 15 user licenses, so valid for 15 distinct (and fixed/named) users. John

I am confused by your issues....there seem to be 2 issues. 1. Connectivity issue. You say: You have shown no proof of this - if there is an issue in FSUIPC, it will be in the FSUIPC4.log file. The error message "FSUIPC Error #12 FSUIPC_ERR_SENDMSG" ETC." is NOT from FSUIPC as far as I can tell, if it was it would be in your FSUIPC4.log file. And if you have seen other threads with this issue, please provide a reference so that I can understand what this problem is. 2. FSX CTD and/or FSUIPC exiting Then this sounds like it could be a weather issue, although I would still like to see a log file for the crash. You can try without weather by adding 'NoWeatherAtAll=Yes' to the [General] section of your FSUIPC4.ini - but you have to add this, it is not present by default. I am not interested in seeing FSX dump files, so please do not attach them. Do you always get this crash/exit at the same location? Have you tried without FSUIPC4 running (you can just temporarily rename the FSUIPC4.dll file to prevent it being loaded)? If FSUIPC is exiting, not crashing, then something must be telling it to exit. We can add some more logging to see what is happening, but first I would like to understand if it is crashing or just exiting.

I have PM'ed you your license details. John

How have you assigned them? If your rotary has two buttons in each direction, you can assign the "slow" button to the standard controls and the "fast" button to the fast controls., If your rotaries only have one button in each direction, you can simulate fast/slow buttons by using the provided Rotaries.lua script (in the lua examples under your FSUIPC4 documents folder). For the ADF: and you would assign the "slow" button to the frac controls, and the "fast" button to the whole controls. Alternatively, For the VOR OBI, specific "fast" controls are provided: Faster control can also be achieved by: 1. Using an offset: if there is a writeable offset that holds the value you are trying to adjust, you can assign to the appropriate offset inc/dec function with a user defined delta. 2. By overloading your assignments, i.e. you can have the control sent 2 or more times for the "fast" button by duplicating the assignment line (making sure that the index number to the assignments are unique).

Yes - you can have different versions installed in different simulators without a problem.

The download link, as well as your license details, will be in your receipt email, and also available in your SimMarket account. You can download from fsuipc.com, or here : Its late now, but tomorrow I can PM you a license/key file if you cannot find your license details (but check your account!). Regards, John

Where is this from? From your simcars program? If so, try running without that. If its fine without that, it is the simcars program that is causing this issue, and you need to contact them for support. John

Your FSUIPC4.log file shows that FSUIPC4 exited as the sim had stopped, not crashed. Are you sure that that is a log file from when it crashed? All it shows is that FSUIPC exited after 1m49s, as FSX exited.

I have removed whatever that was you included at the end of your post. Please attach your FSUIPC4.log file, and also check the windows event viewer and post any crash information that you see there. Such crashes are usually due to a corrupt weather file, although I need to see your files and crash log to confirm. This type of crash has been reported hundreds of times, and the solution to first try is well known (delete your used wxstationlist.bin file, and possibly other weather files, and let that get rebuilt). Check other posts on this issue for further information. If that doesn't work, show me your FSUIPC4.log file and windows crash event information. John

The specified size/position for ext/wnd windows is only used the first time the window is created - the position/size is then stored in your FSUIPC ini file, under the [ExtWindow] section, and this overrides any position/size specified when the window is created. If you want the new size/position to be used, delete the entry for this window under [ExtWindow]. It is implemented this way so that users can move and resize any such window to their preferred position. You can move and resize such windows by using the arrow keys to move, and ctrl + arrow keys to resize, when the window has the focus. The new size/position is then remembered for the next session. So the size/position coordinates in the creation are only ever used the very first time the window is created. Hope that makes sense. John

Ok, that's good then. If you want to get the visual working, you would have to look at the code that is associated to the pull/push button operation (using the MSFS developer mode behaviors window) and see what is used to control the animation, Detailed instructions can be found here: https://www.badcasserole.com/uncovering-input-events-using-the-msfs2020-model-behavior-dialog/. However, if this was easy to do (e.g. was using a h:var) then this would already be in the preset. I suspect it will be using a B-type variable, which are (currently) only controllable using a hack - for an example if this (controlling a b-var using a user-defined lvar), see

License sent.

Does it have the desired affect, i.e. switch between managed and selected mode? It could be that just the visuals are not working, Looking at the altitude push, it just decrements the value of the lvar L:S_FCU_ALTITUDE: (L:S_FCU_ALTITUDE) -- (>L:S_FCU_ALTITUDE) You could also try listing the lvar values to confirm that the code is being sent and is working, As I don't have the Fenix I cannot really help much further if FSUIPC is sending the code for the preset as it is defined. You can try the MobiFlight discord server, who drive the community effort for this - use the MSFS2020 channel.