FSUIPC for Microsoft Flight Simulator X (incorporating WideFS 7). Now version 4.955. This version works with FSX, FSX-SE and Prepar3D. A module that allows outside. Apr 13, 2007 I'm trying to install FSX FSUIPC 4.09, it cannot find the FSX path and wants me to give it FSX.EXE location. I've tried searching with no luck. Apr 05, 2014 FSUIPC4 Problems Can't Access. I've installed FSUIPC and it says it is installed. Installer for FSUIPC4.DLL version 4.09 Looking in registry for FSX install. Dec 30, 2016 FSUIPC 4.947. Copy Contents of /crack folder in the rar into your modules folder in P3d/fsx Download. 09/04 (4) 09/04 - 09/11.

I brought FSUIPC 4.96 yesterday and installed it. You do NOT buy a specific version! Yashwant Kanetkar Books Pdf.

The current version is 4.962, not 4.96, so please go get the current version. Additionally, if/when you ARE using 4.962 I need more information, because so far yours in the only report.

The Windows crash details. You can use the Event Viewer you get this. The FSUIPC4.LOG file from the sim's Modules folder.

A list of what add-ons you are running. A note of the Windows version -- Win7, Win8 or Win10? Hi, thank you for the reply.

I uninstalled fsuipc and my sim didnt crash. I re installed it and it crashed again and again and again. Hi, thank you for the reply. I uninstalled fsuipc and my sim didnt crash.

I re installed it and it crashed again and again and again. It just keeps crashing as soon as the plane loads into the airport on free flight. Where are the crash details, please? The log is useful, and seems to indicate a corrupted weather file, but the Windows crash details are absolutely necessary. It is they that tells mev what the crash is and where. The problems with weather files (.WX files and wxstationlist.bin) is that they are binary files with no checks applied. This appears not to matter until FSUIPC starts reading the weather, one of its functions for client programs, and any corruption in the files causes SimConnect or weather.dll to crash.

The text on the website isn't updated for each sub-version, and it isn't my website so I can't easily do much about it. It will catch up. The link will be pointing to the current version, depending on when you used it.

Where are the crash details, please? The log is useful, and seems to indicate a corrupted weather file, but the Windows crash details are absolutely necessary. It is they that tells mev what the crash is and where. The problems with weather files (.WX files and wxstationlist.bin) is that they are binary files with no checks applied. This appears not to matter until FSUIPC starts reading the weather, one of its functions for client programs, and any corruption in the files causes SimConnect or weather.dll to crash. Pete HI, thank you for the reply. Windows log: Application: Administrative: Number of events: 26,190, Size: 20.00MB Security: Administrative: Number of events: 32,438, Size: 20.00MB Setup: Operational: Number of events: 2,279, Size: 1.00MB System: Administrative: Number of events: 31,886, Size: 20.00MB Forwarded Events: Operational: Number of events: 0, Size: 68KB I hope this is what you mean by the crash details.

I got them from Event Viewer--Windows Logs Many thanks Sam. I hope this is what you mean by the crash details. I got them from Event Viewer--Windows Logs No, it isn't. That looks like simple a count of reports in different sections. You have to look at the Windows Logs - Application and scroll down to find one marked Error in red and attributed to FSX. It's also the data you see in the original on-screen report when the crash occurs if you select the more info button. Here's an example of a crash report (not one for FSX - I don't have one at present).