John Dowson

@cchiozza Your install log looks fine. Did you not get a pop-up box when you start P3Dv5 asking if you want the FSUIPC6 add-on to be enabled? If you go to Options -> Add-ons, do you see FSUIPC6 listed there? If so, and it isn't checked/active, try activating there. I see you also installed in P3Dv4 - is it working/active in that version?

Maybe also try sending direct to FSUIPC calibration and calibrating in the calibration tab (p6 of the calibration screens).

What control are you assigning to? Which aircraft are you using? Could you activate logging for Axis controls and events, and generate a short log file (just load a plane and turn the trim wheel through its full range, then exit). Then attach your FSUIPC7.log and FSUIPC7.ini files and I'll take a look.

Just use the attached license. Save it to your FSUIPC7 installation folder. It should be valid until (and including) 01/02/2021. John FSUIPC7.key

Hi Emile, Ok, that's good to know. I'll verify this when I get a chance and update the FAQ entry accordingly. John

There are no sim variables (exposed via simconnect or otherwise) for those. I suspect there may be available via lvars (or some other type of variable, maybe k vars), but as Al has commented, there is currently no way to access lvars using FSUIPC7. I am looking in to providing such access in a future release, but no timescales yet. John

I could add to a new offset if you like. I can't really update the functionality of existing offset 0x3103, but I could add a new offset that would be read/write and accept flags 0x1 for avionics master 1 and 0x2 for avionics master 2 (and so a value of 0x3 would indicate/set both master avionics). Let me know if this is useful and I can add for you to test. John

You need to assign to the control Throttle Revers Thrust Toggle. However, this control/event seems to be broken since the last MSFS update. I have reported this to Asobo. John

As I have said, your logs show that it is MSFS that is crashing, not FSUIPC7. You are experiencing the issue previously mentioned with the MSFS SDK. You should raise a support request with Asobo, and include the event log information and the crash dump file. John

Could you attach your InstallFSUIPC6.log file please and I'll take a look. John

I don't know - it should be recognised directly if its a hid joystick type device, and programmable via lua if its any other type of hid device. I can provide you with a time-limited license to try the registered facilities if you like - let me know. John

Controls Avionics Master 1/2 Set were added for this back in October 2020 - see

Yes, thanks for the input. John

As the author says. this is calling other lua scripts and those functions are defined in Linda. Maybe the author should make it clear that those functions are used. I'm not sure if you could extract those functions and use them without Linda, as they probably reference other Linda functions. Maybe the author, @joeherwig, could either let you know if this script - only works with Linda installed, or - can be used by extracting a self-contained set of lua functions? If so, maybe this can also be added to github? John

If its now working, its not necessary to send me any more files.

It connected initially after 18 seconds: Note that WideServer is only started/enabled by FSUIPC once you have an aircraftin a ready-to-fly state. You can manually enable it earlier if you wish. WideClient cannot connect before WideServer is started. But this is a separate issue and cannot be related to your wideclient connection issue, which seems to be solved. There are currently known issues with MSFS crashing due to issues with simconnect, and so provoked by simconnect clients. Asobo are aware of the problem and are looking into it (there are various threads on this in this forum). All MSFS CTDs should really be reported to Asobo via zendesk, with relevant details (event log details + crash dump) if available.

As I said, it does look strange. But as it was produced when you were re-connecting and changing usb ports on-the-fly, I'm not going to investigate why, sorry. There's just far to much to do for me to investigate such peculiarities. If you have an issue where devices get switched or not recognised when you aren't re-connecting and swapping ports then I will take a look, but as i said, I just can't see any issue here.

Why are you worried about what is written to the ini? It does look strange but its not worth spending time on this if you don't have an issue, especially if you are now starting to plug usb2 devices into usb3 ports. That is known to cause issues with some usb2 devices, so the first thing I would recommend is to not do this an to stick to usb2 ports. John

Ok, I'll look at this, but tomorrow.

Hi Luke, There is no duplication. Your devices are there with the letters you have assigned to the device, and also with the joystick ids. FSUIPC needs both. John

Yes, I'm surprised it was working before, and I'm also surprised that an error wasn't logged now it isn't working. I will check this sometime (but not today), but first would like to know if it does work with quotes or not, as it may be something else. John

Why are you continually disconnecting and re-connecting your devices when FSUIPC is running? There is something strange in your ini (your yoke is given the name of your pedals) but its really not with investigating this as I don't know what state this was written in (i.e. what devices were connected) Connect your devices, start FSUIPC and see if they are working or not, and if not then attach your files and I'll take a look.

Try this thread: I think there are some links or dlls posted there, and was reported as working. The manual and FAQ entry are both out-of-date and need revising. It would be good if you could make some notes trying to get this work, and maybe write an updated FAQ entry for other users (solution should be valid for FSUIPC5, 6 & 7). Here's the current one, which needs updating/replacing: John

From the Advanced User Guide: John

What update? I thought it was now connected/working? Why attach two log files? Please, EVERY time you think you have an issue, we need to see your WideClinet.ini, your WideClient.log and your WideServer.log. All three, every time. And have you tried setting the ServerName and Protocol ini parameters? Or ServerAddress?