John Dowson

Looks like you have registry issues, but could you please also show me your FSUIPC6.log file. Also, you aren't using the 'JoyLetters' facility. You should really activate this to prevent problems when windows re-assigns your ids. Please see the FSUIPC User guide for details, or simply change AutoAssignLetters=No to AutoAssignLetters=Yes in the [JoyNames] section of your FSUIPC6.ini file and run P3D.

There are many buttons/switches that can't be programmed at the moment either due to lack of controls or controls not working, especially for AP systems (G1000 etc). Also. it seems that, depending on the aircraft and the AP system used, you may have to switch authority from the FCU to enable, and this may also apply to the MCP. I am referring to this post: See this topic for further details:

Nor have I - assignments look good. Try activating logging for Buttons & Switched and Lua plugins to see if that tells you anything. You can post your log file here. Try without LINDA running as well to see if that's interfering.

I'm not sure about the Saitek X56, but its possible with the mode switch on the saitek yoke. When you change the mode switch, does FSUIPC see this in the buttons and switches assignment dialog? If so, it should be straightforward to use in FSUIPC. If not, some folks had to remove/rename a file called SaiD0BAC.PRO (in C:\Windows\System32) to get the mode switch of the yoke recognised. Maybe there is something similar for the X56? Also, note that FSUIPC only sees the first 32 buttons (0-31), so if the button number of the mode switch is higher than that it won't be recognisd in the assignments panel and you would have to resort to lua to program the button. You can check in the windows game controllers utility to see if your mode switch is recognised there (and what number it has). Finally, make sure that you have not installed the saitek software or drivers and just use the standard windows drivers.

@Thomas Richter Those assignments are fine. He's just overloading the previous button press (adding '10' to the entry number, and using offset conditions. These are the ones that should be removed as they are assigned to controls that no longer exist: For the actual problem, I'm still not sure if the TrransmitClientEvent failures are due to MSFS or FSUIPC7. However, when this occurs FSUIPC7 should be able to disconnect and reconnect successfully without crashing. This looks to be a threading issue which I'll look into. Btw, could you also activate 'Extras' logging. This will add a but more information (namely the thread id of the thread logging the message) which may be helpful. Thanks,

Yes, but its pretty much the same in FSX/P3D, although not quite so bad. However, previous versions of FSUIPC had the mouse macro functionality that enabled you to assign to UI components that weren't controllable via standard SimConnect events or variables. I think we have to wait for something similar to be implemented in MSFS, rather than expecting ASOBO to implement SimConnect events to control all buttons/switches for all aircraft.

Starting/stopping luas are controls added by FSUIPC, as Thomas has shown you.

As Pete said earlier, just run it again and it will kill the previous incarnation. Or to just kill it, you can also use the provided control.

You run WideFS on a client PC. If you want to run it on the same PC as FSUIPC/P3D, you have to change the class name - see the provided documentation for details. But, do you really need WideFS? This is really only needed to run FSUIPC clients on a different machine to P3D o/FSUIPC. You should not use that just to use the lua display library. You can use ipc.display instead for luas running in FSUIPC. For example, try the attached lua: FPS_Monitor.lua

Hi Stephan, first, I have moved your post to the dedicated FSUIPC7/MSFS sub-forum. Please use this sub-forum for question on FSUIPC7/MSFS. Yes, you can - but only if your device is recognised as a standard windows HID device. In FSUIPC, you can add 'curves' to adjust the sensitivity. I suggest that you just download and try FSUIPC7-beta. It currently comes with a time-limited license so you can try the assignments. See John

No, sorry.

There is now an installer ready that includes the WebSocket server + integration into FSUIPC7 (via an Add-ons menu entry). You can download from here: http://fsuipc.simflight.com/beta/Install_FSUIPC7.zip http://www.fsuipc.com/download/Install_FSUIPC7.zip There is an issue if the WebServer is already running when FSUIPC7 is started as it currently doesn't check for this. I may add this at a later date. Also, there is currently no indication if the WebSocket server is running or not (apart from entries in the log). I think I'll update the FSUIPC7 title bar to include this information at some point. Let me know if you have any issues or suggestions. John

Hi Joshua, as described in the Announcement and in the provided README.txt file: John

How are you running the lua? On a button press or from the [Auto] section? Maybe you can attach your FSUIPC6.ini file and I'll take a look. Otherwise, you could try activating debugging of Lua plugins to see what that tells you.

Yes. Lua functionality is only available in the registered version of FSUIPC.

Sorry, but it is still not clear what you issue is. Is it the loss of controls, or with Pilot2ATC? For loss of controls, check that you have power management disabled on your usb devices/hubs. You can also try activating logging for Axes Control in FSUIPC7. Monitor the console log (i.e. Log -> Open Console) and see what is logged, if anything, when you experience the loss of control. However, as you say that you lose control of your mouse, it sounds more like an MSFS issue as FSUIPC7 does nothing with the mouse. You could also check to see if any keyboard shorcuts have any affect when this occurs. For issues with Pilot2ATC, you really need their support forum.

Where the documentation uses the term 'Modules folder', it refers to your FSUIPC installation folder. Previous to FSUIPC version 6, FSUIPC was, by default, installed in a folder called Modules, located under the main P3D folder. So its the folder that you select to install FSUIPC6 into. if you don't know where this is, there is also an 'Open Folder' button in the FSUIPC6 logging tab that will open Windows Explorer on this folder. Sure. No, you need to restart the lua. i.e. kill it (if its running) and start it again. The file will be re-compiled each time it is ran. No, it isn't But as I said, you just need to stop the lua running and then restart it.

Still waiting. This has already been asked many times, e.g.

After you have installed FSUIPC6 and you start P3Dv5, you should have seen a pop-up dialog asking if ok to enable the add-on: didn't you see this and give permission? So when you tick the option, select 'Ok', then close and restart P3Dv5, you still don't see the Add-ons menu option with FSUIPC... menu option? Your installation log looks fine, so I'm not sure what is going on. I suggest that you uninstall the FSUIPC6 installation in P3Dv5 by running the uninstaller (located in your installation folder: C:\Users\onebo\Documents\Prepar3D v5 Add-ons\FSUIPC6\uninstallFSUIPC6.exe). Then re-run the installer and try again. I would also suggest that you choose a folder outside of your Documents folder for the installation. This is just a default and is where the add-on.xml will be created, but it is better to actually install FSUIPC6 in a different folder (e.g. C:\FSUIPC6).

There is no change with this functionality in the latest build, and I just tested in the Lomgitude and its working as expected. You can try logging Events and Axis Controls. Before you activate the toggle, you should see the THROTTLEn_SET controls with a positive Param: When the assigned button is pressed, you should see the toggle control: and after this, the Param for the THROTTLEn_SET controls should be negative: Are you using the same FSUIPC7.ini file? You could attach that and I'll check it for you.

Hi André, I don't think this is currently possible as there are no assignable controls/events for this. However, this is already on the 'wishlist': https://forums.flightsimulator.com/t/mappable-controls-to-toggle-labels-aircraft-airport-poi-etc/153732 A zendesk issue has also been raised: https://forums.flightsimulator.com/t/suggestion-keyboard-shortcut-to-toggle-traffic-labels/116033/3 I also though i'd seen a mod that implements this a while back on the MSFS forums, but couldn't find this with a quick search....

I'm not that familiar with the c# library, but I doubt it very much. I think lvar access is a lot simpler via lua, and you would probably have to implement your own 'event' type mechanism. But check the documentation, or you can ask in the client dll for .net sub-forum: https://forum.simflight.com/forum/167-fsuipc-client-dll-for-net/

Sorry, but I can't support ProSim, especially v1. @Pete Dowsonuses ProSim, so maybe he can advise...

Looks like you are running from a fresh install (i.e. no FSUIPC7.ini) as the ini you posted is completely empty. As the ini shows that you do not have 'event' logging activated - please activate that if you want to see the events logged. If you have previously configured FSUIPC7, you need to copy the latest FSUIPC7.exe file to the folder that you previously used to install/run FSUIPC7. Or, alternatively, copy your previous FSUIPC7.ini file to the new folder for FSUIPC7. FSUIPC7 uses the FSUIPC7.ini file (containing all your assignments and logging configuration) located in the same folder as the FSUIPC7.exe file that you are running.

Presume that you mean the initial call of the function, but no, this cannot be prevented. However, you can handle in your function by returning straight away if its on the first/initial call. You can determine this by using a global variable, and checking/changing the initial value in the function, exiting if it is the first call. For most use cases, this initial call is needed to initialise/sync the offset value in the script with the actual offset value.