Fsx Fsuipc 4 09 Itunes
Apr 07, 2007 The latest ver of FSUIPC is causing my FSX to crash without successfully loading. I was running fine before I downloaded ver 4.09. I had to delete it from my modules. 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. Hi, I brought FSUIPC 4.96 yesterday and installed it. Every time I load into a free flight on FSX: SE, it crashes to desktop every time. This must be an e.
In addition to what James said above, FSUIPC allows you to set some parameters for aircraft/sim in ways different from what you can do in FS, including setting calibration values for many of your controls. It's been worth it to me. To clarify a bit, though, it's the paid for version that allows all the extra flexibility. The free version is strictly for the interface between the sim and certain software, allowing that software to control things that otherwise are difficult or impossible. There shouldn't be any side effects. HR Larry N.
I brought FSUIPC 4.96 yesterday and installed it. You do NOT buy a specific version! 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.
Fsuipc 4 Freeware
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).
My red highhlighting. Faulting application name: StandardCollector.Service.exe, version: 14.0.25123.0, time stamp: 0x56f2261c Faulting module name: ntdll.dll, version: 6.1.7601.23572, time stamp: 0x57fd0651 Exception code: 0xc000000d Fault offset: 0x0689f2 Faulting process id: 0x2274 Faulting application start time: 0x01d28233e15aa4b9 Faulting application path: C: Program Files (x86) Microsoft Visual Studio 14.0 Team Tools DiagnosticsHub Collector StandardCollector.Service.exe Faulting module path: C: Windows SYSTEM32 ntdll.dll Report Id: 75652d29-ee2b-11e6-ae61-74d435ed54d3 The important lines are those in red. Hi, I found the error report. I coppied twoof the crash details for better detail. I found the error report. I coppied twoof the crash details for better detail.
Sorry, but neither of those crash reports actually identify FSUIPC as the cause. The only reason your sim crashes with FSUIPC and not without is very probably because FSUIPC is actively using parts of your sim which are corrupted. So, I think you have a problem with corruption in one or more of your FSX-SE files. The most likely is the weather being loaded. Find the.WX files in your FSX-SE Documents folder (where the flights are, and delete them - or at least move them out of that folder, as a test. Also delete the 'wxstationlist.bin' file, which you'll find in your Users AppData Roaming Microsoft Flight Simulator folder, near your FSX.CFG file. The sim will make a new one when you load it.
The first crash you list looks like a bad AI Traffic File, so also try turning all traffic off. If that fixes it, you'd need to reinstall your traffic program, or if you are using only default traffic, repairing the FSX-SE files.