John Dowson

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?

Hi Hans, There is no change in this are between v7.0.3 and v7.0.4. You do not need to uninstall before installing a new version. If you do this, the default installation location will be C:\FSUIPC7 rather than your previous installation location. Therefore, it may be running with a default/newly created ini file rather than the one with your RUNIFs. Just run the installer, and it will then prompt you to uninstall before re-installing. So run the installer again, and make sure that you select the correct installation location. Please check this, and if thats not the issue, please attach your FSUIPC7.log and FSUIPC7.ini files. John

That can be safely ignored. WideClient always runs an Initial.lua file on start-up, if found in the WideClient.exe folder. See the WideFS User manual, section Lua plug-in facilities. One thing to note though is that you are running WideClient from a desktop folder. Did you mean to do this? Anyway, I'm happy that its now connecting. Such issues usually are caused by the network/sharing/firewall configuration. John

You should read this thread that you posted in, and also check the referenced threads, i,e,this one: I think you should be okay with the batteries, you can do quite a bit with the APU but I'm not sure about the full start-up sequence, fuels valves look ok but not sure about the pumps - you would need to try/test. I'm sure there are quite a few A320Neo (both with and without the FBW mod) dlvers that also use FSUIPC7, so maybe they can help. I could also give you a time-limited license for FSUIPC7 if you wanted to try for yourself - let me know. For Stream Deck, there is also an FSUIPC plugin available from a user contribution: John

Its not really a crash/CTD though is it? Looks like its hanging when exiting, or does it actually CTD as well? If its a CTD, is there any crash event in the windows Event Viewer logs? Your FSUIPC log shows that FSUIPC is waiting for P3D to call DLLStop to exit, so it looks like its closing down correctly. There's nothing in your log that shows anything that could prevent a correct and orderly shut-down. Does the same thing occur without FSUIPC running? If this only occurs in that one Orbx region, maybe try asking over on the Orbx forums to see if any one else is experiencing this issue. John

There is currently a known issue that is causing CTDs in MSFS when using SimConnect clients. There are various threads on this issue (both here and on the Asobo forums). Asobo are aware of this and its under investigation. The trigger seems to be related to the amount of data going through simconnect, and FSUIPC is a pretty heavy user.Some people have had success by disabling the reception of AI data in FSUIPC, by adding the following to the [General] section of your FSUIPC7.ini file: ProvideAIdata=No As FSUIPC7 is now a separate application (rather than an embedded dll), it should not cause MSFS to crash, and any MSFS CTDs should be reported to Asobo, with the windows event viewer details attached as well as the crash dump, if available. John

Re-run the installer and do not install the Auto-Start FSUIPC7 with MSFS component. If you do not see this component in the selection panel, you need to download the latest installer. You should be ok with that but you will have to manually start FSUIPC7. Once installed, please send me your InstallFSUIPC7.log file and I'll take a look. Are you using an MS Store install for MSFS or a Steam one? John