Search the Community

Hello! When I start P3D i am able to load into the aircraft, but after a few seconds it crashes to desktop without any warnings or error messages. I looked at Event viewer and found that FSUIPC is crashing the sim. This is what the event viewer says: Faulting application name: Prepar3D.exe, version: 5.2.22.27615, time stamp: 0x60db69bf Faulting module name: FSUIPC6.dll, version: 6.1.0.5, time stamp: 0x613a4dfa Exception code: 0xc0000409 Fault offset: 0x00000000000ebad4 Faulting process id: 0x5330 Faulting application start time: 0x01d7cff1edf656bb Faulting application path: G:\Lockheed Martin\Prepar3D v5\Prepar3D.exe Faulting module path: C:\Users\Klaus\Documents\Prepar3D v5 Add-ons\FSUIPC6\FSUIPC6.dll Report Id: b0111cf0-8c93-4b7f-9a7b-262540866702 Faulting package full name: Faulting package-relative application ID: In the FAQ I found the part about the wxstations.bin file - I tried it with the "NoWeatherAtAll=Yes" in the [General] section of the FSUIPC4.INI file - without success. (Removed after trying) I found that I had no wxstations.bin file at all in the "APPDATA/ROAMING/LOCKHEED MARTIN/PREPAR3D" folder. I never deleted anything from there. Also after restarting the file was not created. I tried to copy it over from the "LOCKHEED MARTIN/PREPAR3D/WEATHER" folder - without success. What can I do now? Thank you very much! EDIT - I attached the log and ini file. FSUIPC6.log FSUIPC6.ini

Hello, I unfortunately suffered an FSX CTD at 1,500 feet on my approach and I'd like to figure out what the issue was and if it was related to FSUIPC at all. Everything was going normally until the simulator locked up around 1,500 feet, froze for a minute or two, and then closed. This was on VATSIM in a busy airspace, though my sim will usually just stutter in such instances without crashing. The Windows crash details indicate FSRecorder as the faulting module, though it seems to always throw up the same .dll as the faulting module after a CTD. I was not using FSRecorder at the time, nor had I used it at all during this particular flight. Here's the report anyway: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: RecorderFSX.dll_unloaded, version: 1.3.0.0, time stamp: 0x4772d03d Exception code: 0xc0000005 Fault offset: 0x0000cf30 Faulting process id: 0x4b0 Faulting application start time: 0x01d6e2202b6bcb94 Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe Faulting module path: RecorderFSX.dll Report Id: 50e32fd4-f1f9-45a1-9845-d7b065db7543 Faulting package full name: Faulting package-relative application ID: Here's another one from less than a minute later. Looks almost identical. Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: RecorderFSX.dll_unloaded, version: 1.3.0.0, time stamp: 0x4772d03d Exception code: 0xc000041d Fault offset: 0x0000cf30 Faulting process id: 0x4b0 Faulting application start time: 0x01d6e2202b6bcb94 Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe Faulting module path: RecorderFSX.dll Report Id: a2d2cafe-1c8a-4005-93b0-43fc01b60d80 Faulting package full name: Faulting package-relative application ID: Here's a final one from 13 minutes later, perhaps when I tried to relaunch FSX. This one lists ai_player.dll as the faulting module. Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: ai_player.dll, version: 10.0.61637.0, time stamp: 0x46fadb57 Exception code: 0xc0000005 Fault offset: 0x00037399 Faulting process id: 0xfe4 Faulting application start time: 0x01d6e23a68099c7d Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ai_player.dll Report Id: 810a2d1a-9dbc-4473-b32d-9b30b28fc566 Faulting package full name: Faulting package-relative application ID: I've attached the FSUIPC4.log file to the post. This is an unregistered copy of FSUIPC and I just updated it the other day through DVA ACARS. I was flying an addon 717 (can look up developer later if needed). Addons I was using were ASN, DVA ACARS, projectFly, vPilot, and Self Loading Cargo. I had also used FS Real Time early in the flight but was not at the time. I know it doesn't look like FSUIPC was at fault, so I'm just trying to get to the bottom of what happened. Self Loading Cargo users have been reporting issues with a recent version of FSUIPC, but it may be for MSFS, I'm not sure, or if that's related to my issue. Any help would be appreciated. Thanks in advance. FSUIPC4.log

Hey, I recently reinstalled FSUIPC since I had some troubles with my sim and thought it could be related to FSUIPC. Now FSUIPC isn't working at all. So basically what's happening is that I click "fly now" in FSX-SE so it loads in, after it successfully loaded in, it crashes to desktop after a couple of seconds (about 5 secs). PS: Thanks for any help in advance (FSUIPC log is attached) FSUIPC4.log

Hi, I've got a crash to desktop. Below you will find the event viewer report . I'm running Prepar3D v4.1.7 and FSUIPC5 5.122a. Any advice to avoid more of this? Thanks, Jose --------------------------- Nombre de la aplicación con errores: Prepar3D.exe, versión: 4.1.7.22841, marca de tiempo: 0x59d67e95 Nombre del módulo con errores: FSUIPC5.dll, versión: 5.1.2.201, marca de tiempo: 0x5a19470e Código de excepción: 0xc0000005 Desplazamiento de errores: 0x0000000000046423 Identificador del proceso con errores: 0x250c Hora de inicio de la aplicación con errores: 0x01d3913987749a4a Ruta de acceso de la aplicación con errores: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe Ruta de acceso del módulo con errores: C:\Program Files\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.dll Identificador del informe: abf2714a-abc6-48d7-915c-ebcd3db87be9 Nombre completo del paquete con errores: Identificador de aplicación relativa del paquete con errores:

Hello, I have bought a Saitek X52 Pro (replacing a Thrustmaster 4 HOTAS) and thinking that it will work flawlessly, I plugged it into USB slot, then installed the related software and the FSX-P3D and Xp11 plugins required from the manufacturer's website, which later I found out was a mistake. As the title suggests now P3Dv4.1 crashes to desktop while loading the main scenario screen. If I disconnect the controller, the application starts fine. I followed some steps that I found here in this forums, like uninstalling the software, removing the device and the drivers from Device Manager but it still doesn't work. Also interesting is that I can't even find the device listed in Device Manager although it is connected and visible under "Devices and Printers" I am attaching the relevant files and any help is appreciated. Thanks. event viewer.txt FSUIPC5.log FSUIPC5.JoyScan.csv

Hi there, well after fresh install of p3d.3.4 and all addons, there is time for testing. 3 tests without problem (average 7h duration, on PMDG738), then tongiht, 4th trial and baam - CTD. Checked the error log and that's what was there: Faulting application name: Prepar3D.exe, version: 3.4.9.18400, time stamp: 0x57d9b14e Faulting module name: SimConnectP3D3.dll_unloaded, version: 0.0.0.0, time stamp: 0x571e4e28 Exception code: 0xc0000005 Fault offset: 0x13d41eb0 Faulting process id: 0x21e4 Faulting application start time: 0x01d22fd9dc19f48f Faulting application path: E:\Program Files\Lockheed Martin\Prepar3D.exe Faulting module path: SimConnectP3D3.dll Report Id: 117c0380-9c01-11e6-9f34-74d435e2a771 Now, what could cause that? I've the latest FSUIPC and fresh installs of next addons/programs: AS16+softclouds, ORBX base+vector, ezdok, accufeel, rwy bumping effect, fscaptain, ivap and acars. The error occured after 7 hours of flight with PMDG738 on holding above LEPA (added aerosoft's airport). So, what to do? Thanks for help..

I purchased the Eaglesoft Cessna Citation X recently and was advised to purchase a registered version of FSUIPC along to have a fully functional fadec. I followed the advise and purchased a registered FSUIPC 4 and set up the joystick and throttle. Both are working fine with a throttle idle of 24% N1. I applied the axeswrongrange = yes, as advised in some online fora. My problem is that with the ES Cessna aircraft, FSX crashes to desktop randomly. Recently the crashes have become too frequent and happen right on the ground while setting up FMS. I have read some posts about this issue and understand it is related to corrupt weather files. So I deleted the .WX files from document folder as well as the waether. bin file from appdata\roaming folder as advised. However this did not solve the problem and FSX crashed at the very next flight on ground. I am producing below excerpts from the log file for the events that happened during the crash. Please help me with this issue so that I have a good return on the investments I made on these two apparently top class softwares related to flight sim. Pls do not keep me waiting at moderation and I request a response at the earliest. Regards, Samik ********* FSUIPC4, Version 4.949p by Pete Dowson ********* fsx.exe version = 10.0.61637.0 Reading options from "C:\FSX\Modules\FSUIPC4.ini" Running inside FSX on Windows 7 Module base=616E0000 User Name="samik gupta" User Addr="samik66@yahoo.com" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired 1125 System time = 21/05/2016 18:12:11 1125 FLT path = "C:\Users\samik\Documents\Flight Simulator X Files\" 1141 ------ Module Version Check ------ 1141 acontain.dll: 10.0.61637.0 1141 api.dll: 10.0.61637.0 1141 controls.dll: 10.0.61637.0 1141 fs-traffic.dll: 10.0.61637.0 1141 G3D.dll: 10.0.61637.0 1141 language.dll: 10.0.61637.0 1141 sim1.dll: 10.0.61637.0 1141 visualfx.dll: 10.0.61637.0 1141 weather.dll: 10.0.61637.0 1141 window.dll: 10.0.61637.0 1141 ---------------------------------- 1547 Trying to connect to SimConnect Acc/SP2 Oct07 ... 1563 FS path = "C:\FSX\" 2031 ---------------------- Joystick Device Scan ----------------------- 2047 Product= MetalStrik 3D 2047 Manufacturer= MetalStrik 3D 2047 Vendor=0583, Product=B011 (Version 1.0) 2047 Serial Number= MetalStrik 3D 2047 Product= Wireless Device 2047 Manufacturer= Lite-On Technology Corp. 2047 Vendor=04CA, Product=006F (Version 0.53) 2047 Serial Number= Lite-On Technology Corp. 2047 ------------------------------------------------------------------- 2078 LogOptions=F0000000 0000001F 2078 ------------------------------------------------------------------- 2078 ------ Setting the hooks and direct calls into the simulator ------ 2078 --- CONTROLS timer memory location obtained ok 2094 --- SIM1 Frictions access gained 2110 --- FS Controls Table located ok 2110 --- Installed Mouse Macro hooks ok. 2110 --- Wind smoothing fix is fully installed 2110 --- G3D.DLL fix attempt installed ok 2110 --- All links checked okay 2110 ------------------------------------------------------------------- 2110 SimConnect_Open succeeded: waiting to check version okay 2110 Trying to use SimConnect Acc/SP2 Oct07 14219 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 14219 Initialising SimConnect data requests now 14219 FSUIPC Menu entry added 14297 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y 14297 *** EVENT: Cntrl= 66078 (0x0001021e), Param= 2016 (0x000007e0) ZULU_YEAR_SET 14297 *** EVENT: Cntrl= 66077 (0x0001021d), Param= 142 (0x0000008e) ZULU_DAY_SET 14297 *** EVENT: Cntrl= 66075 (0x0001021b), Param= 12 (0x0000000c) ZULU_HOURS_SET 14297 *** EVENT: Cntrl= 66076 (0x0001021c), Param= 42 (0x0000002a) ZULU_MINUTES_SET 14297 C:\FSX\FLIGHTS\OTHER\FLTSIM.FLT 14297 C:\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR 14969 READ1[6792] 3304, 4 bytes: 10 00 49 49 ..II 14969 READ1[6792] 3308, 4 bytes: 08 00 DE FA .... 14969 Memory in use: 754Mb, Avail=3342Mb 15453 READ1[6792] 290C, 4 bytes: 38 00 00 00 8... 15453 READ1[6792] 320C, 4 bytes: 38 00 00 00 8... 15563 READ1[6792] 8320, 1 bytes: 02 . 15563 READ1[6792] 0B63, 1 bytes: 00 . 15563 READ1[6792] 3306, 2 bytes: 49 49 II 15563 READ1[6792] 0238, 10 bytes: 00 00 00 00 00 00 00 00 00 00 .......... 15563 READ1[6792] 3C00, 256 bytes: 43 3A 5C 46 53 58 5C 53 69 6D 4F 62 6A 65 63 74 C:\FSX\SimObject 15563 73 5C 41 69 72 70 6C 61 6E 65 73 5C 41 69 72 63 s\Airplanes\Airc 15563 72 65 61 74 69 6F 6E 5F 35 38 32 53 4C 5C 41 69 reation_582SL\Ai 15563 72 63 72 65 61 74 69 6F 6E 5F 35 38 32 53 4C 2E rcreation_582SL. 15563 41 49 52 00 00 00 00 00 00 00 00 00 00 00 00 00 AIR............. 15563 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ ******************************************************************************************************************************************************** 588735 READ1[6792] 3500, 24 bytes: 43 37 35 30 00 00 00 00 00 00 00 00 00 00 00 00 C750............ 588735 00 00 00 00 00 00 00 00 ........ 588735 READ1[6792] 3D00, 256 bytes: 45 61 67 6C 65 73 6F 66 74 20 43 69 74 61 74 69 Eaglesoft Citati 588735 6F 6E 20 58 20 32 2E 30 20 4E 38 30 30 45 53 00 on X 2.0 N800ES. 588735 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 588735 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 588735 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 588735 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 588735 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 588735 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 588735 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 588735 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 588735 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 588735 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 588735 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 588735 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 588735 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 588735 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 588735 READ1[6792] 3148, 24 bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 588735 00 00 00 00 00 00 00 00 ........ 588735 READ1[6792] 3130, 12 bytes: 00 00 00 00 00 00 00 00 00 00 00 00 ............ 588735 READ1[6792] 313C, 12 bytes: 4E 38 30 30 45 53 00 00 00 00 00 00 N800ES...... 588735 READ1[6792] 0240, 2 bytes: E0 07 .. 588735 READ1[6792] 023E, 2 bytes: 8E 00 .. 588735 READ1[6792] 023B, 1 bytes: 0C . 588735 READ1[6792] 023C, 1 bytes: 33 3 588735 READ1[6792] 0238, 1 bytes: 0E . 588735 READ1[6792] 0239, 1 bytes: 33 3 588735 READ1[6792] 023A, 1 bytes: 39 9 588735 READ1[6792] 0248, 2 bytes: 01 00 .. 588735 READ1[6792] 0D70, 40 bytes: 4C 75 61 20 46 53 50 53 00 00 00 00 00 00 00 00 Lua FSPS........ 588735 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 588735 00 00 00 00 00 00 00 00 ........ 588735 READ1[6792] 0D6C, 4 bytes: 00 00 00 00 .... 588735 Exception 15 "WEATHER_UNABLE_TO_GET_OBSERVATION", Ref 6133, Index param -1 on Weather request type 5 588735 WX Error: Exception 15, WX request type 5, Lat=48.9958, Lon=2.5544, Alt=0.0m 588735 WRITE0[6792] 310A, 2 bytes: 08 00 .. 588735 READ0[6792] 332E, 2 bytes: 00 00 .. 588735 READ0[6792] 3330, 2 bytes: 00 00 .. 588735 READ0[6792] 3332, 2 bytes: 00 00 .. 588735 WRITE0[6792] 088C, 2 bytes: 01 00 .. 588735 WRITE0[6792] 0924, 2 bytes: 01 00 .. 588735 READ0[6792] 7B92, 1 bytes: 00 . 588735 WRITE0[6792] 7B92, 1 bytes: 00 . 588735 READ0[6792] 7B9B, 1 bytes: 00 . 604563 Weather Read request (At Aircrft) to area 4: Lat=49.00, Lon=2.55, Alt=121.0, Req=2 604563 Weather Read request (Nr Station) to area 5: Lat=49.00, Lon=2.55, Alt=0.0, Req=1 606063 System time = 21/05/2016 18:22:15, Simulator time = 14:51:58 (12:51Z) 606063 *** FSUIPC log file being closed Minimum frame rate was 3.5 fps, Maximum was 4.3 fps Minimum available memory recorded was 1669Mb Average frame rate for running time of 244 secs = 3.8 fps G3D fix: Passes 17626, Null pointers 0, Bad pointers 0, Separate instances 0 Maximum AI traffic for session was 87 aircraft Memory managed: 59 Allocs, 59 Freed ********* FSUIPC Log file closed ***********

Hello. Sorry my poor English. I'm setting my joystick axis on FSUIPC Axis Assignment. (My joystick is Thrustmaster HOTAS Warthog and Saitek Pro Rudder Pedals) Setting Axis is here: http://imgur.com/TCPhs0N http://imgur.com/Gq3G4VD http://imgur.com/a8UWn5Q http://imgur.com/ECbj6lD http://imgur.com/Sr9s0NK http://imgur.com/BH6nQB9 http://imgur.com/ZSDcRSx http://imgur.com/681P5nA After setting few minutes, Prepar3D v3 is crashed. Eventlog code is here: Faulting application name: Prepar3D.exe, version: 3.0.10.14945, time stamp: 0x560b4abe Faulting module name: DINPUT8.dll, version: 6.1.7600.16385, time stamp: 0x4a5bd9c1 Exception code: 0xc0000005 Fault offset: 0x000069e8 Faulting process id: 0x1404 Faulting application start time: 0x01d0ff746a2e3650 Faulting application path: I:\P3D\Prepar3D v3\Prepar3D.exe Faulting module path: C:\Windows\system32\DINPUT8.dll Report Id: 3c9875d8-6b68-11e5-aacd-3085a990bff7 I have another simulator installed FSUIPC. (FSX package, FSX Steam, Prepar3D v2) Try to the same settings this simulators. FSX Package : no crash FSX Steam : no crash Prepar3D v2 : same crash FSUIPC version is 4.946 (All simulators) Try to the one joystick only setting (HOTAS WH or Saitek Rudder). But occurred same crash both joystick. When all Axis setting delete, not occurred crash. Have knowledge of cause this crash ? Thanks. Tomoya.

Hi, I loaded FSUIPC latest version 4.938d for testing the FSFlyingSchool 2015 Demo. My Sim was working very well with FTX Global, Vector, OpenLC Europe and FS Global Ultimate. When I load a flight at daytime all is fine. But: When I load a flight at nighttime P3D says: FATAL ERROR and crashes to desktop. Removing the modules folder or just removing the FSUIPC_Loader.dll helps to prevent CTD --> it's an issue of FSUIPC. Windows event log doesn't help as there is no helpful information listed... Anyone who can please help me? A lot of Add Ons will use FSUIPC and I need also to fly @ night. Thanks a lot in advance. Denny