John Dowson

Your logs show that WideServer/FSUIPC is not receiving the response from WideClient and the connection times-out: This error is usually caused by the connection being blocked by a firewall. Are you sure that you tested with ALL firewalls turned off? Especially check the firewall(s) on your server PC (i.e. the one running MSFS/FSUIPC7). Alternatively, something else could be running on the default ports (8002 and 9002). You could try changing these (for both WideServer and WideClient) - see the WidFS Technical guide for details on the Port and Port2 ini file oprions. Note that your FSUIPC7.log is large as you have event and axis controls activated, which aren't needed. Anyway, I just wanted to check that WideServer was running, which your logs show, so no need to attach that file again. There are quite a few reports with this same error/issue over the years (Flight Sim version not really important for this issue as WideServer and WideClient will be the same), and it is always the firewall configuration (maybe caused by a windows update) that causes this issue. For example, see the following: John

@JARS I know this post is now 6 years old now, but do you remember what exception and where this is located in P3D? Or do you mean that you ticket the box in a router config page to allow P3D to send/receive external traffic?

@Javinet Why are you posting the same question again in the wrong sub-forum. I have moved your 2nd post in the FAQ sub-forum. I will not do this again - they will just be deleted. Please see my original comment and follow instructions there if you want support for this issue. John

Please exit FSUIPC7 and WideClient before attaching files (you can keep MSFS running). If its too large, compress/zip it. WideClient again looked like it connected: But there was no sign of it in your WideServer.log file though. I will check things here when I get a chance and get back to you. However, it would be useful to see all the correct files from the same session, and attached when FSUIPC7 / WideClient have closed. You also seem to be using a very old version of FSUIPC7 (including WideServer) - 7.2.11, which is from October 2021. I am very surprised that version even works... And I only support the latest version, which is 7.4.15. Can you please update to the latest version of FSUIPC, try again, and remember to exit FSUIPC7 and WideClient before attaching files. John

Your FSUIPC7.1.log is a continuation log file. Please do not do this (i.e. start a new log) - I need to see the full log file not a partial one. And your WideClient.log shows that it connected but that you closed WideClient after 7 seconds: Why was this? Can you explain what happened please, or try running WideCLient for a bit longer...

Please also attach the WideServer.log file.

First, you posted in the FAQ sub-forum where it explicitly states NOT for support requests. I have moved your post to the main support forum, Please use this forum for all issues with FSUIPC6. Then please show me/attach your InstallFSUIPC6.log file. This implies that you are trying to install under the Documents\Prepar3D v5 Add-ons folder. You should use this location for the add-on.xml file only. When you install, please choose another folder, and not under a windows protected folder (such as Documents or Program Files). Select a non-windows protected folder, such as c:\FSUIPC6 or C:\P3Dv5 Add-ons\FSUIPC6. If you still get issues when installing in a non-windows protected folder, show me/attach your InstallFSUIPC6.log file. John

@Edoradar Sorry for the delay with this -I have been rather busy with MSFS / FSUIPC7 (as usual!) and also suffering from lower back and sciatica issues which are restricting the amount of time I can remain seated and working... Anyway, please try the attached dll, beta version v6.2.1c. I have enable writing at offset 0x3402 but only for bits 0,1, 4,5,6 & 7. So, to assign to a button/key press, you need to assign to the control Offset Word Togglebits with parameters: 0x1 - to toggle pause 0x2 - to toggle slew mode 0x10 - to toggle position freeze 0x20 - to toggle attitude freeze 0x40 - to toggle altitude freeze 0x80 - to toggle lat/long freeze Please test this and let me know how you get on. Once this is tested and I have updated the documentation I will release this version. Cheers, John FSUIPC6.dll

This is very strange... again, the log files show nothing. Can you use the attached please - I have added a couple of more debug log statements to try and track down where this crash is happening. The log file will be a lot larger and may need zipping, but still al lot smaller than trace logging. layout.json FSUIPC7_WASM.wasm

Very strange...did anything change? It is in the WASM persistence storage area - from the Advanced User guide: John

@BJHawk Could you please try the attached updated WASM module please. Save the FSUIPC7_WASM.wasm file to your Community\fsuipc-lvar-module\modules folder, and the layout.json and manifest.json files to your Community\fsuipc-lvar-module folder. There is not a specific fix for this issue, but I have switched to using tagged data so this version should be more efficient. Let me know if you have any issues, and if so please attach your FSUIPC_WASM.log file. @J-Aviator If your issue is with a WASM crash, please also try this version. John manifest.json layout.json FSUIPC7_WASM.wasm

This issue is related to an FSUIPC CTD has now been reported in the following topic: For users with the issue that FSUIPC is running but not opening/displaying when instructed (e.g. on keypress Alt+F), then this is usually because the window is being sized/positioned off-screen. To rectify this, you need to exit FSUIPC and delete the Window ini parameter from the [General] section of your FSUIPC7.ini file and then restart FSUIPC7. This will reset FSUIPC to the default size and position. John

@DaveSCUSA Are you still having this issue?

No they were not - you pasted images. Please attach the following files (not paste images or contents): From your server PC: FSUIPC7.log, FSUIPC7.ini, WideServer.log From your client PC: WidweClient.log, WideClient.ini Did anything change? Please check the following: - firewalls: maybe temoprarily disable all firewalls (client and server PCs, routers) to see if its a firewall issue - check your WorkGroup names, both PCs must be in the same WorkGroup You can also try adding the ServerName and Protocol ini parameters to your WideClient.ini file. Please see the Configure your Network section of the WideFS User Guide. And see the trouble-shooting notes in the WideFS Technical guide. Also a good idea to reboot both PCs if you haven't done that already. John

Unfortunately the logs don't reveal much. I have now had MSFS running (and attached to a debugger for the WASM) for around 24hours, switching between the FBW A320 and the PMDG 777 and 737 and have not been able to get the WASM to crash/fail. I had to stop this session as I ended up getting exceptions/a CTD in MSFS. Looks like there is definitely a problem somewhere in the WASM causing this but it is going to be difficult to track down. I will keep investigating, and I do have some performance improvements I would like to implement in the WASM so maybe I will take a look at these to see if this improves things. There are some minor adjustments you can make which will hopefully make this crash less likely. Change the following in your FSUIPC_WASM.ini file (the one in your WASM persistance area, not the one under your Community folder. Set the following ini parameters: LvarScanFrequency=-5 LvarScanDelay=8 LvarScanPeriod=5 Are you sure this is the same problem, i.e. a WASM crash? To verify this, you can either try sending another preset or lvar update - if that works, the WASM hasn't crashed. Otherwise, you need to check in the devmode debug console - search for fsuipc and see if there is an exception message. If it is a WASM crash, also please try those updated settings mentioned above. If not, then I will need to see your files (FSUIPC7.log, FSUIPC7.ini and FSUIPC_WASM.log). John

Sorry, but it is confusing when you talk about 'not showing in task bar'. I think you mean that FSUIPC7 is crashing on start-up. The log files you attached are also very strange, and just show that FSUIPC stopped at different stages during start-up. Can you please download the installer again and re-install from a fresh download. If you get the same issue can you temporarily rename your FSUIPC7.ini file and try again to see if that makes a difference. Also please check the Windows Event Viewer application and see if there are any events related to FSUIPC there, and if so show that to me (they are under Windows Logs -> Application).

And the event information pease. All I can tell you is that WideClient/WideFS has been stable for around 10 years now, with no updates. If it does crash, this normally indicates an issue in your system - maybe a corrupt windows library somewhere. Such issues are notoriously difficult to track down... John

I need to see the FSUIPC_WASM.log from when it crashed. Restarting FSUIPC won't help. This is an FSUIPC WASM crash and you need to restart MSFS. Which version of the FBW A320 were you using?

I don't have the 738 and am not familiar with 'squad' - what is it? Is there a control in the Virtual Cockpit for this? If so, do you see any events in the FSUIPC7.log file when this is used? Try logging events (Log -> Events) and open the logging console (Log -> Open console) and see if anything is logged when you activate this in the VC. If nothing is logged, try listing lvars to see if any look appropriate. I can't see anything related to squad the PMDG custom controls or offsets.

Sounds good, but I wonder why it is still off by 1000 feet - it would be useful to know where/how it is deriving this altitude. This sounds strange as offsets CC00-CFFF are documented as the area to READ the weather at the requested location. The writable area is C800-CBFF. To be honest I am not sure how these offsets work - I will take a look in more detail next week, Maybe worth checking these in FSUIPC6 with P3D, or maybe with FSUIPC4 in FSX. The Active Sky files may contain some useful data, especially the current_wx_snapshot.txt file: Maybe worth taking a look at that file. I will see if I can look into this in more detail next week sometime.

Offset area 6700 - 6BFF (1632 bytes) are ok to use if not using Jean-Michael Biston ("Michael") for Airbus gauges or FS-Communicator, which is what they are reserved for. Note that your lua WILL NOT turn on the LED - it will update the offset with the status of the LED/lvar when the lvar changes. Those offsets should certainly work - I will double check them next week, but if having issues try debugging the lua script using the facilities provided (i.e. Debug/Trace Lua plugins in the Logging tab). This will tell you if the script is running and what it is doing. Also try logging the offset you are using on the right hand side of the logging tab, and make sure to check Normal log file.

How long into the flight did this happen? Those files are all from today and show no issues.

No. Can you please show me your WideClient.log file, and also any event information from the windows Event Viewer. If WideClient crashed, there should be a crash event reported with further details. Yes. Instructions are provided in Appendix 4 of the Advanced User guide (page 67). John

Are you using 7.4.15? Was it just the presets that stopped working? You can compress/zip them. If still too big, you can use one of the free file transfer services (e.g. https://filetransfer.io/). It must be there - are you sure you are looking in the correct place? It is in the WASM persistent storage area: John

There are only 4. But you can also log an offset range, although I am not sure where or if that is documented. I have never had a need to use this facility so I would need to check.