John Dowson

Are you referring to what you see in the event viewer? So there is nothing there related to FSUIPC? It is very difficult for me to determining what is happening on your system without you responding to my questions. What actually happens when you run the FSUIPC7.exe file? Did you try pressing Alt + F to show the main window? If you start the Task manager, can you see the process running or not (labeled 'IPC Interface and More, for MSFS')?

These don't seem to work in the King Air either, sorry.

There is one other thing that you can try.... Check to see if any of the controls in MSFS itself work. The default key for Landing Lights Right is shift + Ctrl + Num6, and for left is shift + ctrl + num4. If they work, you can assign your buttons to the MSFS assigned key presses. John

No I am not 100% sure, and I did not try this. You should always try/test lvars/hvars/calculator code before using, as I said in my first post: Did you not do this? Have you installed the FSUIPC WASM module (that provides access to lvars/hvars)? Did you activate the WAPI? This needs to be done just the once if you want to use lvars/hvars. Then I suggest you keep the manuals open and check things before asking for support. For example, you said: which is obviously the wrong syntax which even a brief check against the documentation would have told you.... Well, obviously. But from your questions it seems to me that you are not even looking at the manual. I gave both the syntax and an example on the manuals, and you seem to have missed both... Anyway, I just checked those lvars in the King Air, which you should have done as suggested, and they are settable but have no affect. Even stranger, some of the standard landing light controls (Landing Lights Set, Landing Light Right, etc) get logged as completely different controls when sent to this a/c. Very strange. There is also no MobiFlight preset for the King Air landing (or any other) lights, just presets for the AutoPilot (see https://hubhop.mobiflight.com/#/list). So, in summary, I do not think this is currently possible. You could see if there is a mod available where this has been fixed, maybe try this one: https://uwajimaya.github.io/FS2020/ John

If this is the case, then did you not see this: ? And why isn't this clear from the example I give in the documentation: ? I am sorry but I fail to understand why you are asking these questions when it should be clear from the documentation.... So, your lvaroffsets section should look like this (for example - you can use any offsets that are free for general use): What that says is 'assign the lvar L:LIGHTING_LANDING_1 to offset 0xA000 as an unsigned byte, and also lvar L:LIGHTING_LANDING_2 to offset 0xA001 also as an unsigned byte. An then assign one button to the control Offset Byte Togglebits, giving A000 as the offset and 1 (or x1) as the parameter, and the other button to the same control, giving A001 as the offset and 1 (or x1) as the parameter. Exactly as the example given, except you are using 2 lvars and 2 offsets. Why is this not clear from the Advanced user guide and the example given? Maybe, if/when the penny finally drops, you can create a FAQ entry (or User Contribution) explaining how to do this in language you understand, that may help others who have difficulty understanding the manuals. John

Hi Peter, Good! Ah, ok, understood. Ok. Take a look at the examples provided - they should be in a zip file in your FSUIPC7 Documents folder. There are also several documents got using lua with FSUIPC7, but for general lua information you should consult google. Remember that a lua program needs to be started - if its event based, then you would usually start the lua from your [Auto] (or profile [Auto.xxx]) ini section. John

Why are you sending me log files? Please answer my question: What FSUIPC7 clients are you using? Error 13 IS NOT an error message from FSUIPC as far as I can tell... Your 'previous' log file shows that FSUIPC7 exited after about 4 minutes as MSFS was no longer running. The second log file shows FSUIPC7 still running (i.e. not closed down) after 2 minutes. Can you please answer my question and explain what your issue actually is (no pictures please!). i.e. what happens when you acknowledge the message? Is FSUIPC7 still running? If not, are there any events visible in the Windows Event Viewer? John

Try first without using the luas. Just assign your throttle to the FS controls Throttle1 Axis Set Ex1 and Throttle2 Axis Set Ex1, and try reversing the axes by manually editing your ini and adding ,*-1 to the axes assignment lines - see the section Additional parameters to scale input axis values on the Advanced User guide (P39). The Ex1 axes controls cannot be calibrated using FSUIPC's calibration facilities. You need to use the axis input values scaling for these axes. Try that first before using the luas. Any issues, let me know. But if you do decide to use the luas instead, make sure that the lua is being started, usually you want to do this via your [Auto] or profile [Auto.xxx] ini file sections. If it still doesn't work, try activating debug logging for luas to see what is happening in the script (you can post your log file here if you want me to take a look). John

Ok, thanks - sounds good...what changes did you make? John

As I said, please read the Advanced User guide. P43 and P44. I provide these manuals so that I do not have to explain the same thing for every user. Look at the example I give in the documentation: i.e. you have to give the type of the variable (in this case, UB, an unsigned byte) and the offset address to store the value (in this case, 0xA000). They don't appear there. You need to assign your button to Offset Byte Togglebits, giving the offset you are using together with 1 (or x1) as the parameter. As it says in the documentation... Also note that, as lvars are aircraft specific, it is also better to add lvars to offsets in a LvarOffsets profile section really, but you can continue to use the general section for the time being, if you are not using profiles yet. John John

Check under Windows Logs -> Application to see if there is ant event logged for FSUIPC7 and if so show it to me. If FSUIPC7 crashed, there will be an associated event there. What actually happens when you run the FSUIPC7.exe file? Did you try pressing Alt + F to show the main window? If you start the Task manager, can you see the process running or not? I am still trying to determine if FSUIPC7 is still running or not. If not, and it is actually crashing, you need to update/re-install your VC++ redistributables, as advised. John

You said " I used the axes assignment panel for it and... it's getting worse : 3 to 4s lag instead of 2 to 3 !" but the FSUIPC4.ini file you attached shows no assignments to the Pan View control on an axis, but shows your POV buttons assigned as buttons to the separate Pan Up/Down/Left/Right. This tells me that you either DID NOT assign to the Pan View axis, or you attached an FSUIPC4.ini file that you weren't using. I already said this several times now and quoted your assignments to show you this... So, you are either confused as to what an assignment to an axis is, or you are showing me the wrong FSUIPC4.ini file. Once assigned, it will look something like this on your [Axes] section: So, either show me your updated FSUIPC4.ini file so that I can see the assignments or tell me what you do not understand about assigning your POV to the Pan View axis. Also, please double-check that you have the Enable Controller(s) tick-box unchecked in your settings. I recommend that you also initial start with a simple/stock aircraft before moving on to more complex aircraft. Try setting up all your primary axes and standard buttons (POV, Parking brake, lights, ...) in the general (i.e. no profile selected) sections first, before you start using profiles for specific aircraft. John

Which version did you update from? What do you mean by 'broken'? No, only the latest version is available and supported. We need to determine what is causing your issue. Can you please explain what your issue is, and show me your .ini and .log files. John

Yes. 4294967 seconds - just short of 50 days....a lot higher than you would ever really want! John

I said "select an installation location that IS NOT a windows protected folder, such as Program Files or Documents." So why did you install it in Program Files? PLEASE try installing in another folder, e.g. C:\FSUIPC6, as I suggested. The key file is automatically generated and saved in your FSUIPC installation folder. If you have installed under Program Files, it seems that this file cannot be created for some users. You can manually create your key file, but if this is an issue it is better to install elsewhere as you can have issues further down the line with your assignments, as they are also saved in the installation folder. John

I disagree, but you are entitled to your opinion. You say you have read the manual, but you do not evenseem to be reading mu comments. Take your hat/panning assignments. You ay you assigned this as an axis but that is obviously not true - you have the 4 hat buttons assigned as individual buttons, and you say you have set "Control to repeat while held", which is an option for buttons only - there is no such option for axes assignments. Your 'Connie' profile is only assigned to one aircraft: So that will only be used with an aircraft that has that substring in its title. The throttle calibration is also wrong for that profile: Throttle=-16380,0 You need to calibrate properly. And the only profile in which you have any rudder assigned is in your A320 profile Which is only used for the following aircraft: If the aircraft loaded has a livery that doesn't match any of those aircraft, the profile will not be used. I suggest that you change that to use substrings, e.g. If you do that, the profile will be used for all aircraft that contain the string 'A320'. I have no idea why you think your rudder was working for those aircraft when it isn't assigned, unless you had it assigned in FSX. Maybe re-read it and try again. Try starting with the section The Easy Step-by-Step Way to Calibrate Your Controls John

But you have no axis assigned to Pan View. You only have buttons assigned to Pan Left, Pan Right, Pan Up and Pan Down: You do not need these assignments. Assign to the Pan View control in the Axes assignments dialog, as I have said. John

The installer always goes to the registration page, if it didn't, then it must have crashed. You need to select an installation location that IS NOT a windows protected folder, such as Program Files or Documents. Please select another location. If you continue to get issues, you may need to install/update your VC++ redistributables. Instructions for this are in the provided README.txt. John

That happens when you click the 'New Log' button - that will close the current log file and start a new one. Just don't do that! I see Pete has also just replied.... As well as what Pete has said, your A320 throttle calibration is also very strange: Throttle=-16380,0/16 Try calibrating your throttle or change that to: Throttle=-16380,16380 As Pete said, you should read the User guide before trying to assign and calibrate. John

Just re-run the installer - it will then first uninstall from your current location. When installing, select the installation location outside if your Documents folder, e.g. C:\FSUIPC6. John

Can you not see the AutoSave/GPSOut tab? If not, then you are using an unregistered version. Do you have an FSUIPC6.key file in your FSUIPC6 installation folder? Where have you installed FSUIPC6? Make sure it isn't installed in a windows protected folder, such as Program Files or under your Documents folder. John

I have just tested running and closing/killing various programs, some using symlinks and some directly, without any issues. Could you show me your FSUIPC6.log file - there should be an error logged there if a started process fails to terminate. John

I have no idea.... What did you do? Do you have controllers disabled in FSX? Could your controller ids have changed? I really can't help if you are not showing me any files - please attach your FSUIPC4.log and FSUIPC5.ini files. Load the Baron, activate logging for axes controls in FSUIPC, try moving your rudder through its full range, then shutdown FSX and show me those files. John

How have you assigned this? To assign the hat switch to Pan View, you assign in the Axes Assignment panel, not the button assignments panel. Assign to the FS Pan View control there - there is no option "Control to repeat while held" for axes assignments, so you must be assigning in the wrong place. John

I have now installed Pilot2ATC to check this and cannot reproduce your issue. As I previously said, 3rd part apps cannot connect to FSUIPC if they are not ran at the same privilege level as FSUIPC. Could it be that FSUIPC7 is being ran at a different privilege level (elevated) when auto-started by MSFS? To check this, try running Pilot2ATC with admin rights, to see if it can then connect.