abdelsa Posted February 2, 2017 Report Share Posted February 2, 2017 Hi, I've updated today P3D to the 3.4.22.19868 (following the proper Updating Client, Content and Scenery procedure). Also updated FSUIPC module, and everything was ok, but every time I restart P3D I got this fatal error:Faulting application name: Prepar3D.exe, version: 3.4.22.19868, time stamp: 0x588f7cbf Faulting module name: FSUIPC4.dll, version: 4.9.6.1, time stamp: 0x5891a779 Exception code: 0xc0000005 Fault offset: 0x0001f145 Faulting process id: 0x213c Faulting application start time: 0x01d27d477981c87d Faulting application path: C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe Faulting module path: C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\FSUIPC4.dll Report Id: bd517a86-e93a-11e6-aa5d-a4badbfeb155 Faulting package full name: Faulting package-relative application ID: ---------------------------------------------------------------------------------------------------------------------------------------------- Fault bucket 108719371654, type 1 Event Name: APPCRASH Response: Not available Cab Id: 0Problem signature: P1: Prepar3D.exe P2: 3.4.22.19868 P3: 588f7cbf P4: FSUIPC4.dll P5: 4.9.6.1 P6: 5891a779 P7: c0000005 P8: 0001f145 P9: P10: Attached files: \\?\C:\Users\ARSotolongo\AppData\Roaming\Lockheed Martin\Prepar3D v3\Prepar3D.cfg.txt \\?\C:\Users\ARSotolongo\AppData\Roaming\Lockheed Martin\Prepar3D v3\dxdiag.txt \\?\C:\Users\ARSotolongo\AppData\Roaming\Lockheed Martin\Prepar3D v3\fdr.dat \\?\C:\Users\ARSotolongo\AppData\Roaming\Lockheed Martin\Prepar3D v3\DLL.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDB34.tmp.WERInternalMetadata.xml \\?\C:\Users\ARSotolongo\AppData\Local\Temp\WERE70C.tmp.appcompat.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE78A.tmp.mdmp These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_1b24b766a54862c5b4ab9bba9a7e49c41d794_00000000_327bf6ca Analysis symbol: Rechecking for solution: 0 Report Id: c45c8d56-e942-11e6-aa5e-a4badbfeb155 Report Status: 4104 Hashed bucket: a537bf03c6ddea3d6e94c44d9bba9731 ---------------------------------------------------------------------------------------------------------------------------------------------- Faulting application name: Prepar3D.exe, version: 3.4.22.19868, time stamp: 0x588f7cbf Faulting module name: FSUIPC4.dll, version: 4.9.6.1, time stamp: 0x5891a779 Exception code: 0xc0000005 Fault offset: 0x0001f145 Faulting process id: 0x2e8c Faulting application start time: 0x01d27d4f7fb08f34 Faulting application path: C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe Faulting module path: C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\FSUIPC4.dll Report Id: c45c8d56-e942-11e6-aa5e-a4badbfeb155 Faulting package full name: Faulting package-relative application ID: If I reinstall the FSUIPC module, It works, and P3D starts, but everytime p3d it's restarted, then the problem happend again. And never got an error before. thanks in advance. AR Sotolongo Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 2, 2017 Report Share Posted February 2, 2017 34 minutes ago, abdelsa said: I've updated today P3D to the 3.4.22.19868 (following the proper Updating Client, Content and Scenery procedure). Also updated FSUIPC module, and everything was ok, but every time I restart P3D I got this fatal error:Faulting application name: Prepar3D.exe, version: 3.4.22.19868, time stamp: 0x588f7cbf Faulting module name: FSUIPC4.dll, version: 4.9.6.1, time stamp: 0x5891a779 Exception code: 0xc0000005 Fault offset: 0x0001f145 That is the same error which was occurring with 4.959, and which was fixed by the 4.96 release (and a couple of interim test releases beforehand), and also fixes to LINDA, which was involved. The crash on P3D reload is actually right at the entry point of FSUIPC (offset 1F145), so it isn't FSUIPC which is crashing, but SimConnect which appears to be trying to call it before it is loaded properly. The problem is caused by P3D crashing on a previous sesion when you exit the simulator. Please check the FSUIPC4.LOG file in your Modules folder -- you'll probably find it terminates incorrectly, with no closing. Show it too me, then use the Windows Event Viewer to find details of the P3D crash on Exit, which will be different from the above one (probably in NTDLL). If you are using LINDA see if it is okay without. And make sure you have updated LINDA -- it was changed to fix some problems which were instrumental in making this failure occur. Otherwise I need a list of the other things you are running -- add-ons, Lua plug-ins, etc. Pete Link to comment Share on other sites More sharing options...
abdelsa Posted February 2, 2017 Author Report Share Posted February 2, 2017 (edited) Hi, Thanks for your answer. I'm not using LINDA, so that's not the problem. I've been reinstalled (not just updated) FSUIPC and I have deleted previous .ini file, but the error happen again. ---------------------------------------------------------------------------------------------------------------------------------------------- Here is my FSUIPC log: ********* FSUIPC4, Version 4.960a (1st February 2017) by Pete Dowson ********* Windows 10 Pro 64 Bit reported as Build 14393, Release ID: 1607 (OS 10.0) Prepar3D.exe version = 3.4.22.19868 Reading options from "C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\FSUIPC4.ini" Running inside Prepar3D v3 on Windows 10 Module base=250F0000 User Name="Abdel R. Sotolongo Abella" User Addr="abdelsa@msn.com" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired 1672 System time = 02/02/2017 14:39:55 1672 FLT path = "C:\Users\ARSotolongo\Documents\Prepar3D v3 Files\" 1672 ------ Module Version Check ------ 1672 acontain.dll: 3.4.22.19868 1672 api.dll: 3.4.22.19868 1672 controls.dll: 3.4.22.19868 1672 fs-traffic.dll: 3.4.22.19868 1672 G3D.dll: 3.4.22.19868 1672 language.dll: 3.4.22.19868 1672 sim1.dll: 3.4.22.19868 1672 visualfx.dll: 3.4.22.19868 1672 weather.dll: 3.4.22.19868 1672 window.dll: 3.4.22.19868 1672 ---------------------------------- 1672 Trying C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D3.dll 1672 Found it: trying to connect 1687 FS path = "C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\" 2328 ---------------------- Joystick Device Scan ----------------------- 2328 Product= Control Manager ID #00 2328 Manufacturer= Control Manager ID #00 2328 Vendor=068E, Product=C0F2 (Version 0.0) 2328 Serial Number= Control Manager ID #00 2328 Product= Control Manager ID #00 2328 Manufacturer= Control Manager ID #00 2328 Vendor=068E, Product=C0FF (Version 0.0) 2328 Serial Number= Control Manager ID #00 2328 Product= Control Manager ID #00 2328 Manufacturer= Control Manager ID #00 2328 Vendor=068E, Product=C0FA (Version 0.0) 2328 Serial Number= Control Manager ID #00 2328 ------------------------------------------------------------------- 2344 LogOptions=00000000 00000001 2344 ------------------------------------------------------------------- 2344 ------ Setting the hooks and direct calls into the simulator ------ 2344 --- CONTROLS timer memory location obtained ok 2344 --- SIM1 Frictions access gained 2344 --- FS Controls Table located ok 2344 --- Installed Mouse Macro hooks ok. 2344 --- Wind smoothing fix is installed 2344 --- SimConnect intercept for texts and menus option is off 2344 --- All links okay (except older global weather setting method) 2344 ------------------------------------------------------------------- 2344 SimConnect_Open succeeded: waiting to check version okay 2344 Trying to use SimConnect Prepar3D 2344 Opened separate AI Traffic client okay 73422 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.4.22.19868 (SimConnect: 3.4.0.0) 73422 Initialising SimConnect data requests now 73422 FSUIPC Menu entry added 73437 C:\Users\ARSotolongo\AppData\Local\Lockheed Martin\Prepar3D v3\Prepar3D_Default.fxml 73437 C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air 104484 C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\SimObjects\Airplanes\PMDG 747-400\B747-400_GE.air 176500 User Aircraft ID 2 supplied, now being used 177422 System time = 02/02/2017 14:42:50, Simulator time = 14:41:06 (14:41Z) 177422 Aircraft="PMDG 747-428 Virgin Atlantic Airways (G-VROM | 2016)" 183406 Starting everything now ... 183484 ASN active function link set 183484 Ready for ASN WX radar 183578 Weather Mode now = Theme 196437 Sim stopped: average frame rate for last 20 secs = 25.2 fps 196437 Max AI traffic was 0 aircraft 199828 Advanced Weather Interface Enabled 281203 Sim stopped: average frame rate for last 82 secs = 22.6 fps 281203 Max AI traffic was 0 aircraft 312672 === Calling SimConnect_Close ... 312875 === SimConnect_Close done! 313875 System time = 02/02/2017 14:45:07, Simulator time = 14:42:27 (14:42Z) 313875 *** FSUIPC log file being closed Minimum frame rate was 14.0 fps, Maximum was 43.4 fps Minimum available memory recorded was 1186Mb Average frame rate for running time of 102 secs = 23.1 fps Maximum AI traffic for session was 0 aircraft Memory managed: 43 Allocs, 42 Freed ********* FSUIPC Log file closed *********** ---------------------------------------------------------------------------------------------------------------------------------------------- Here is the report when P3D has been closed (last time it worked): Fault bucket 116325781745, type 5 Event Name: BEX Response: Not available Cab Id: 0 Problem signature: P1: Prepar3D.exe P2: 3.4.22.19868 P3: 588f7cbf P4: FSUIPC4.dll_unloaded P5: 4.9.6.1 P6: 5891a779 P7: 00020f10 P8: c0000005 P9: 00000008 P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE8A5.tmp.WERInternalMetadata.xml \\?\C:\Users\ARSotolongo\AppData\Local\Temp\WEREFE9.tmp.appcompat.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF132.tmp.dmp \\?\C:\Users\ARSotolongo\AppData\Local\Temp\WERF8D4.tmp.WERDataCollectionFailure.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_bde090dc745d6ff32d134d1721f3cf70aad015d_d937b49f_1ea7f910 Analysis symbol: Rechecking for solution: 0 Report Id: 1ebb1a06-38e4-49bc-9245-93f7f0f7d538 Report Status: 4104 Hashed bucket: 304cf213fc68495fd173d7d97a6fcdb4 ---------------------------------------------------------------------------------------------------------------------------------------------- And the last one with the fatal error again: Fault bucket 108719371654, type 1 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: Prepar3D.exe P2: 3.4.22.19868 P3: 588f7cbf P4: FSUIPC4.dll P5: 4.9.6.1 P6: 5891a779 P7: c0000005 P8: 0001f145 P9: P10: Attached files: \\?\C:\Users\ARSotolongo\AppData\Roaming\Lockheed Martin\Prepar3D v3\Prepar3D.cfg.txt \\?\C:\Users\ARSotolongo\AppData\Roaming\Lockheed Martin\Prepar3D v3\dxdiag.txt \\?\C:\Users\ARSotolongo\AppData\Roaming\Lockheed Martin\Prepar3D v3\fdr.dat \\?\C:\Users\ARSotolongo\AppData\Roaming\Lockheed Martin\Prepar3D v3\DLL.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2777.tmp.WERInternalMetadata.xml \\?\C:\Users\ARSotolongo\AppData\Local\Temp\WER313C.tmp.appcompat.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_1b24b766a54862c5b4ab9bba9a7e49c41d794_00000000_2d3d31f6 Analysis symbol: Rechecking for solution: 0 Report Id: 79ff1a29-e94e-11e6-aa5f-a4badbfeb155 Report Status: 1 Hashed bucket: a537bf03c6ddea3d6e94c44d9bba9731 ---------------------------------------------------------------------------------------------------------------------------------------------- My addon list: All aerosoft, fsdreamteam, flytampa, taxi2gate sceneries for P3D. FS2Crew for 777, and RAASPRO... now let me show you something: Activation context generation failed for "C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\RAASPRO\RAASPRO.dll". Dependent Assembly Microsoft.FlightSimulator.SimConnect ,processorArchitecture="x86",publicKeyToken="67c7c14424d61b5b",type="win32",version="10.0.61242.0" could not be found. Please use sxstrace.exe for detailed diagnosis Activation context generation failed for "C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\RAASPRO\RAASPRO.dll". Dependent Assembly Microsoft.FlightSimulator.SimConnect ,processorArchitecture="x86",publicKeyToken="67c7c14424d61b5b",type="win32",version="10.0.60905.0" could not be found. Please use sxstrace.exe for detailed diagnosis. Maybe is a problem with RAASPRO? If you need something alse please let me know. And thank you again. Edited February 2, 2017 by abdelsa Link to comment Share on other sites More sharing options...
abdelsa Posted February 2, 2017 Author Report Share Posted February 2, 2017 (edited) Ok, I uninstalled RAASPRO and the problem it's still there: Fault bucket 108719371654, type 1 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: Prepar3D.exe P2: 3.4.22.19868 P3: 588f7cbf P4: FSUIPC4.dll P5: 4.9.6.1 P6: 5891a779 P7: c0000005 P8: 0001f145 P9: P10: Attached files: \\?\C:\Users\ARSotolongo\AppData\Roaming\Lockheed Martin\Prepar3D v3\Prepar3D.cfg.txt \\?\C:\Users\ARSotolongo\AppData\Roaming\Lockheed Martin\Prepar3D v3\dxdiag.txt \\?\C:\Users\ARSotolongo\AppData\Roaming\Lockheed Martin\Prepar3D v3\fdr.dat \\?\C:\Users\ARSotolongo\AppData\Roaming\Lockheed Martin\Prepar3D v3\DLL.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2D57.tmp.WERInternalMetadata.xml \\?\C:\Users\ARSotolongo\AppData\Local\Temp\WER372C.tmp.appcompat.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_1b24b766a54862c5b4ab9bba9a7e49c41d794_00000000_2deb37d6 Analysis symbol: Rechecking for solution: 0 Report Id: 572326b6-e951-11e6-aa60-a4badbfeb155 Report Status: 1 Hashed bucket: a537bf03c6ddea3d6e94c44d9bba9731 Edited February 2, 2017 by abdelsa Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 2, 2017 Report Share Posted February 2, 2017 5 minutes ago, abdelsa said: Here is my FSUIPC log Hmm. That shows the previous good session closed properly, as least there was no crash caused by FSUIPC. So the fact that FSUIPC can't even run on your next load certainly implies something wrong elsewhere. With the previous errors of the same type, FSUIPC not being entered, the cause was always traced back to a previous crash on exit. No one could explain why crashing on exit made the next load fail -- it was even happening after a system re-boot. Whilst i managed, with LINDA, to finally reproduce the crash on exit I could never reproduce the crashes on the next load -- and nor could my colleague Thomas. It is extra mysterious why an FSUIPC reinstall, with no actual changes being made to anything in so doing (only the timestanp on the DLL.XML file would be affected) seems to make it okay for one more load. Note that one person with the problem often found it was okay on several subsequent reloads. It was unpredictable. It definitely still points to SimConnect, as it is that which calls the "DLLStart" function, which is the one at the offset of the crash. I notice that the FSUIPC log announces the FSUIPC4 version as 4.960a, which was corrected afterwards, though I appear to have uploaded the build just before. I don't think there was any other change, but just in case can you download the separate FSUIPC 4.961 (not the installer) from the Download Links subforum, and use that. i don't think it'll make any difference. Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 2, 2017 Report Share Posted February 2, 2017 14 minutes ago, abdelsa said: Ok, I uninstalled RAASPRO and the problem it's still there: Is that your only other add-on? No more DLLs or EXE's running? No Lua plug-ins running? From the crash results you are getting, none are from withing any FSUIPC code, so I can't really do anything. We need L-M on this. Pete Link to comment Share on other sites More sharing options...
abdelsa Posted February 2, 2017 Author Report Share Posted February 2, 2017 Hi, I'm using the 4.961 from Download Links. I reinstalled FSUIPC again and the problem was fixed, like all the times before. Now I'm testing without FS2Crew RAASPRO and so far so good, keep you in the loop. Thanks. Link to comment Share on other sites More sharing options...
abdelsa Posted February 2, 2017 Author Report Share Posted February 2, 2017 10 minutes ago, Pete Dowson said: Is that your only other add-on? No more DLLs or EXE's running? No Lua plug-ins running? From the crash results you are getting, none are from withing any FSUIPC code, so I can't really do anything. We need L-M on this. Pete Active Sky 2016, but the error become with and without it (AS16 is updated to the currently today's version by the way). CH Products (Yoke, Throttle Quadrant and Pedals). No more dll's or exe's and no Lua plug-ins. Link to comment Share on other sites More sharing options...
abdelsa Posted February 2, 2017 Author Report Share Posted February 2, 2017 ok, with RAASPRO uninstalled I can't reproduce the error, so I think that was the problem. Maybe as you suggested a program (RAAS Pro in this case) appears to be trying to call FSUIPC before it is loaded properly, wich provoque a Fatal Error at P3D start up. I'm gonna keep trying to reproduce the error, but I think it's solved. Thanks for your help, and thank you for your awesome work with FSUIPC. Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 2, 2017 Report Share Posted February 2, 2017 25 minutes ago, abdelsa said: ok, with RAASPRO uninstalled I can't reproduce the error, so I think that was the problem. Maybe as you suggested a program (RAAS Pro in this case) appears to be trying to call FSUIPC before it is loaded properly, wich provoque a Fatal Error at P3D start up. No. I am pretty sure RAAS doesn't use FSUIPC at all. I think RAAS pro is causing some error or strange state on the previous (otherwise good) session, and it is that state, the one we have no theory for at all, which then causes SimConnect to do strange things on the next load. This is probably why you posted this contradiction earlier: 1 hour ago, abdelsa said: Ok, I uninstalled RAASPRO and the problem it's still there: It is misleading when the crash on load is caused by a problem in the previous session. That is still something no one has any theories about. It makes no sense, especially when merely reinstalling FSUIPC "fixes" it. In one of the earlier reports some one found running a different installer, GSX I think it was, also "fixed" it, temporarily. I suspect any re-install of any P3D add-in (i.e. one affecting the DLL loading) would "fix" it. Though we did check that the DLL.XML file was idenntical before ad after, apart from the timestamp. Have you looked to see if there's an update to RAASPRO for P3D3.4 HF3? Pete Link to comment Share on other sites More sharing options...
Vashq8 Posted February 2, 2017 Report Share Posted February 2, 2017 I Have the same issue with latest P3D and FSUIPC4 versions. After some testing, I found the problem maybe is laying in "Previous Flight.wx" and "Previous Flight.fxml". After exiting the simulator I simply delete both files and P3D would start fine. If I leave the files P3D would crash again. Link to comment Share on other sites More sharing options...
abdelsa Posted February 2, 2017 Author Report Share Posted February 2, 2017 Hi, the problem was still there with RAAS uninstalled because was loading the previous session. When reinstalled FSUIPC without RAAS on the system, the problem was fixed. I couldn't reproduced the fatal error again after that. So it is solved now. I've opened a post on fs2crew forum with this, maybe they've to fix RAAS for the new P3D hotfix. thanks again. Link to comment Share on other sites More sharing options...
abdelsa Posted February 2, 2017 Author Report Share Posted February 2, 2017 I've installed the latest RAAS Pro (2.6.10.2) and the problem is still there. When exit P3D I got this error: Application: Prepar3D.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: exception code c0000005, exception address 23DB0F10 Then, when P3D started again, got this one: Activation context generation failed for "C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\RAASPRO\RAASPRO.dll". Dependent Assembly Microsoft.FlightSimulator.SimConnect ,processorArchitecture="x86",publicKeyToken="67c7c14424d61b5b",type="win32",version="10.0.61242.0" could not be found. Please use sxstrace.exe for detailed diagnosis. Maybe something related with framework, I don't know. Hope you can help me here. Thanks. Link to comment Share on other sites More sharing options...
Thomas Richter Posted February 2, 2017 Report Share Posted February 2, 2017 1 hour ago, abdelsa said: I've installed the latest RAAS Pro (2.6.10.2) and the problem is still there. When exit P3D I got this error: Application: Prepar3D.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: exception code c0000005, exception address 23DB0F10 Then, when P3D started again, got this one: Activation context generation failed for "C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\RAASPRO\RAASPRO.dll". Dependent Assembly Microsoft.FlightSimulator.SimConnect ,processorArchitecture="x86",publicKeyToken="67c7c14424d61b5b",type="win32",version="10.0.61242.0" could not be found. Please use sxstrace.exe for detailed diagnosis. Hi, that is definitely not related to FSUIPC because it doesn't use .Net Framework at all. SimConnect version 10.0.61242.0 is FSX SP1, very strange that that is still used or RAAS is looking for? Thomas Link to comment Share on other sites More sharing options...
abdelsa Posted February 3, 2017 Author Report Share Posted February 3, 2017 10 hours ago, Thomas Richter said: Hi, that is definitely not related to FSUIPC because it doesn't use .Net Framework at all. SimConnect version 10.0.61242.0 is FSX SP1, very strange that that is still used or RAAS is looking for? Thomas Hi, Thank you for making me realize that the system was using an older version of Simconnect. After a full re-installation of simconnect 10.0.61259 the problem with RAAS is gone. Thanks. Bests, Link to comment Share on other sites More sharing options...
Sumits81 Posted February 3, 2017 Report Share Posted February 3, 2017 12 hours ago, abdelsa said: Hi, Thank you for making me realize that the system was using an older version of Simconnect. After a full re-installation of simconnect 10.0.61259 the problem with RAAS is gone. Thanks. Bests, Hi, where is the simconnect installer found please? Link to comment Share on other sites More sharing options...
Thomas Richter Posted February 3, 2017 Report Share Posted February 3, 2017 Hi, for i.e. Prepar3D v3 in YourDriveAndPath\Prepar3D v3\redist\Interface\ Thomas Link to comment Share on other sites More sharing options...
Sumits81 Posted February 3, 2017 Report Share Posted February 3, 2017 15 minutes ago, Thomas Richter said: Hi, for i.e. Prepar3D v3 in YourDriveAndPath\Prepar3D v3\redist\Interface\ Thomas Thanks Thomas. Found it in the p3d folder, installed but not much seems to have changed. Link to comment Share on other sites More sharing options...
qqwertz Posted February 3, 2017 Report Share Posted February 3, 2017 On 2/2/2017 at 1:24 PM, Vashq8 said: After some testing, I found the problem maybe is laying in "Previous Flight.wx" and "Previous Flight.fxml". After exiting the simulator I simply delete both files and P3D would start fine. If I leave the files P3D would crash again. Same problem here. With FSUIPC enabled, P3D 3.4 HF3 hangs (the startup window closes but the program is still running in the task manager and consuming CPU resources). With FSUIPC disabled iP3D starts just fine. I have installed the most recent versions of FSUIPC, P3D and Simconnect. I don't use RAAS and I didn't find "Previous Flight.wx" and "Previous Flight.fxml" anywhere (except very old ones in my FSX folders). Sometimes the Windows Event Viewer shows an error message, sometimes it shows nothing. Peter Link to comment Share on other sites More sharing options...
Sumits81 Posted February 3, 2017 Report Share Posted February 3, 2017 29 minutes ago, qqwertz said: Same problem here. With FSUIPC enabled, P3D 3.4 HF3 hangs (the startup window closes but the program is still running in the task manager and consuming CPU resources). With FSUIPC disabled iP3D starts just fine. I have installed the most recent versions of FSUIPC, P3D and Simconnect. I don't use RAAS and I didn't find "Previous Flight.wx" and "Previous Flight.fxml" anywhere (except very old ones in my FSX folders). Sometimes the Windows Event Viewer shows an error message, sometimes it shows nothing. Peter Hi, You can find them under C:\Users\username\Documents\Prepar3D v3 Files\ I've tried deleting both but P3D still CTD. Doesn't really help at the moment. Cheers Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 4, 2017 Report Share Posted February 4, 2017 1 hour ago, qqwertz said: I have installed the most recent versions of FSUIPC, P3D and Simconnect. I don't use RAAS and I didn't find "Previous Flight.wx" and "Previous Flight.fxml" anywhere (except very old ones in my FSX folders). Sometimes the Windows Event Viewer shows an error message, sometimes it shows nothing. It won't be a crash on start up, but the aftermath of a crash when you closed the previous (or a previous) session. ou need to get the details for that, and try to eliminate it by a process of elimination. Please see a lot of the previous messages here which expain things further about what is happening. Pete Link to comment Share on other sites More sharing options...
qqwertz Posted February 4, 2017 Report Share Posted February 4, 2017 Hello Pete, sorry, I forgot to mention that; I have read the posts about restarting P3D and tried to eliminate this possibility. - I restarted my computer and did nothing but starting P3D, but even then I get the same problem. -I do not have the files "Previous Flight.wx" and "Previous Flight.fxml" in C:\Users\username\Documents\Prepar3D v3 Files\ (and that directory is the one used by P3D for the error log), nor anywhere else, possibly because I am using AS16. I also tried to delete the AS16 weather files (activeflightplanwx.txt, current_wx_snapshot.txt, LastDownloaded.Wx), but it had no effect. - I always launch P3D with the default airplane (F35) at the default airport, with the start-up screen enabled. - I am using the registered version of FSUIPC under Win 10. Thanks for looking into this, Peter Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 4, 2017 Report Share Posted February 4, 2017 1 minute ago, qqwertz said: I do not have the files "Previous Flight.wx" and "Previous Flight.fxml" in C:\Users\username\Documents\Prepar3D v3 Files\ It would be the last thing that FSUIPC requests of SimConnect before it closes. Those files would have the same timestamp as the LOG file when FSUIPC closes. If the last FSUIPC log shows that FSUIPC did close, then the requests to save those files has actually gone to SimConnect. So either something else has crashed before SimConnect performs that function, or it is the attempt to save those files which is crashing, maybe because you have more sophisticated add-on aircraft, like the PMDG ones, which try to detect those save operations and save their own data too. Maybe that conflicts with their attempt to close down as they've been asked to by then. To test if this latter is the problem try setting SavePreviousFlight=No in the [General] section of the FSUIPC4.INI file. Pete Link to comment Share on other sites More sharing options...
qqwertz Posted February 4, 2017 Report Share Posted February 4, 2017 Hello Pete, It looks like you are on the right track regarding PMDG planes. I was able to resolve the problem doing the following. - I uninstalled the new PMDG 747. This didn't change anything at first - I disabled all dll modules in dll.xml . P3D then started normally - I re-enabled first FSUIPC and then subsequently all other modules. P3D was able to get to the start-up screen after each change. - I then launched the default flight with success. Except that the FSUIPC menu and functionalities were gone (with the module being enabled) -I re-installed FSUIPC. After that it was working fine again. - I re-installed the 747. When I only started a flight with it there were no problems after restarting, but after I initialized the plane to cold & dark and restarted P3D, the problem reappeared. - After that, I set SavePreviousFlight=No in FSUIPC.ini, but it didn't help. By the way, RAAS remained disabled during these procedures. - Re-installing FSUIPC fixed the problem. This long list is simply an accountof my trial and error session. I would guess the essential elements are to re-install FSUIPC and to add SavePreviousFlight=No in FSUIPC.ini . I will let you know if the issue occurs again. Thanks and best regards, Peter Link to comment Share on other sites More sharing options...
qqwertz Posted February 4, 2017 Report Share Posted February 4, 2017 I should have made one more test :) P3D didn't start again, but did so after reinstalling FSUIPC. It seems that for now I have to reinstall it every time before launching P3D Peter Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now