Wimma Posted June 11, 2017 Report Share Posted June 11, 2017 Hello Pete, I have a pretty weird problem with the licensed FSUIPC 5 and v4. after an hour or so, sometimes a bit more than that, FSUIPC crashes randomly and disapperars out of the in sim addon list in the menu bar. After restarting the sim it is their again until it crashes again one hour later. The sim does not crash during this procedure. Well at least not everytime. it sometimes does. Because of the fact that autosave is working its not really toooo much of a problem. at least when im at home. but it is still annoying as hell. I tried reinstalling FSUIPC but it did not work. hopefully you know a solution for this problem. Greetings, Michael! Link to comment Share on other sites More sharing options...
Thomas Richter Posted June 11, 2017 Report Share Posted June 11, 2017 Hi, please copy and paste the full content of the FSUIPC5.log file after the session has been closed, ideally of course a session when the 'crash' happend. Thomas Link to comment Share on other sites More sharing options...
Wimma Posted June 11, 2017 Author Report Share Posted June 11, 2017 (edited) Hi Thomas, First of all a big thank you for the ver fast response!!! I am kind of a noob when it comes to finding stuff. would u mind telling me where i can find this log file? Thank you for you help. Michael Edited June 11, 2017 by Wimma Link to comment Share on other sites More sharing options...
Thomas Richter Posted June 11, 2017 Report Share Posted June 11, 2017 Hi, all FSUIPC stuff included the module (DLL) itself is located in ..\Prepar3D v4\Modules\ So just find your FS (P3Dv4) installation folder and check in subfolder Modules Thomas Link to comment Share on other sites More sharing options...
Wimma Posted June 11, 2017 Author Report Share Posted June 11, 2017 (edited) I have been here before when i searched for it but i could not find the .log file in here. in the Modules folder is only: FSUIPC5 Install FSUIPC5 .DLL FSUIPC5 FSUIPC5.joyscan FSUIPC5.key FSUIPC5 Michael Edited June 11, 2017 by Wimma Link to comment Share on other sites More sharing options...
Wimma Posted June 11, 2017 Author Report Share Posted June 11, 2017 Well I think it is this one. it just doesnt say .log its a text document for me. hope i got the right one. ********* FSUIPC5, Version 5.10 (1st June 2017) by Pete Dowson ********* Windows 10 Pro 64 Bit reported as Build 14393, Release ID: 1607 (OS 10.0) FSUIPC5.dll version = 5.1.0.0 Reading options from "Y:\Flightsim\P3Dv4\Modules\FSUIPC5.ini" Running inside Prepar3D v4 on Windows 10 Module base=7FFB4E400000 User Name="Michael Wimmer" User Addr="michael.wimmer98@gmx.at" FSUIPC5 Key is provided WIDEFS7 not user registered, or expired 0 System time = 11/06/2017 16:36:13 0 FLT path = "C:\Users\Michael\Documents\Prepar3D v4 Files\" 0 ------ Module Version Check ------ 0 acontain.dll: 4.0.23.21468 0 api.dll: 4.0.23.21468 0 controls.dll: 4.0.23.21468 0 fs-traffic.dll: 4.0.23.21468 0 G3D.dll: 4.0.23.21468 0 language.dll: 4.0.23.21468 0 sim1.dll: 4.0.23.21468 0 visualfx.dll: 4.0.23.21468 0 weather.dll: 4.0.23.21468 0 window.dll: 4.0.23.21468 0 ---------------------------------- 15 FS path = "Y:\Flightsim\P3Dv4\" 109 ---------------------- Joystick Device Scan ----------------------- 109 Product= Saitek X52 Flight Control System 109 Manufacturer= Saitek 109 Vendor=06A3, Product=075C (Version 1.16) 109 GUIDs returned for product: VID_06A3&PID_075C: 109 GUID= {8963A7E0-211C-11E7-8001-444553540000} 109 Details: Btns=34, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U255,V255,X2047,Y2047,Z255 109 ------------------------------------------------------------------- 125 Device acquired for use: 125 Joystick ID = 1 (Registry okay) 125 1=Saitek X52 Flight Control System 125 1.GUID={8963A7E0-211C-11E7-8001-444553540000} 125 ------------------------------------------------------------------- 140 LogOptions=00000000 00000001 140 ------------------------------------------------------------------- 140 SimConnect_Open succeeded: waiting to check version okay 140 Opened separate AI Traffic client okay 2656 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0) 2656 Initialising SimConnect data requests now 2656 FSUIPC Menu entry added 2656 ... Using Prepar3D with Academic License 2671 C:\Users\Michael\AppData\Local\Lockheed Martin\Prepar3D v4\Prepar3D_Default.fxml 2671 Y:\Flightsim\P3Dv4\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air 15718 Weather Mode now = Theme 16500 Y:\Flightsim\P3Dv4\SimObjects\Airplanes\PMDG 777-200LR\B777-200LR.air 16500 C:\Users\Michael\Documents\Prepar3D v4 Files\AutoSave Sun 163406.fxml 17203 !!! ICAO1 from AI traffic incorrect! 17203 !!! ICAO2 from AI traffic incorrect! 35250 User Aircraft ID 2 supplied, now being used 35265 Aircraft loaded: running normally now ... 36156 System time = 11/06/2017 16:36:49, Simulator time = 15:30:41 (14:30Z) 36156 Aircraft="Boeing 777-21H/LR Emirates A6-EWB" 41406 **** Restarting traffic scanning due to non-reception **** 42656 Starting everything now ... 43828 Advanced Weather Interface Enabled 100250 Sim stopped: average frame rate for last 65 secs = 45.0 fps 100250 Max AI traffic was 0 aircraft 309453 **** No SimConnect events or states being received! Re-connecting now ... **** 309796 SimConnect_Open succeeded: waiting to check version okay 309796 Opened separate AI Traffic client okay 309796 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0) 309796 Initialising SimConnect data requests now 309796 FSUIPC Menu entry added 309812 ... Using Prepar3D with Academic License 309812 User Aircraft ID 2 supplied, now being used 309812 C:\Users\Michael\Documents\Prepar3D v4 Files\AutoSave Sun 164115.fxml 310609 System time = 11/06/2017 16:41:23, Simulator time = 15:34:33 (14:34Z) 608687 **** No SimConnect events or states being received! Re-connecting now ... **** 609031 SimConnect_Open succeeded: waiting to check version okay 609031 Opened separate AI Traffic client okay 609031 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0) 609031 Initialising SimConnect data requests now 609031 FSUIPC Menu entry added 609046 ... Using Prepar3D with Academic License 609046 User Aircraft ID 2 supplied, now being used 609046 C:\Users\Michael\Documents\Prepar3D v4 Files\AutoSave Sun 164615.fxml 609437 System time = 11/06/2017 16:46:22, Simulator time = 16:39:25 (14:39Z) 908468 **** No SimConnect events or states being received! Re-connecting now ... **** 908812 SimConnect_Open succeeded: waiting to check version okay 908812 Opened separate AI Traffic client okay 908812 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0) 908812 Initialising SimConnect data requests now 908812 FSUIPC Menu entry added 908812 ... Using Prepar3D with Academic License 908812 User Aircraft ID 2 supplied, now being used 908812 C:\Users\Michael\Documents\Prepar3D v4 Files\AutoSave Sun 165114.fxml 909531 System time = 11/06/2017 16:51:22, Simulator time = 16:44:18 (14:44Z) 1208000 **** No SimConnect events or states being received! Re-connecting now ... **** 1208343 SimConnect_Open succeeded: waiting to check version okay 1208343 Opened separate AI Traffic client okay 1208343 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0) 1208343 Initialising SimConnect data requests now 1208343 FSUIPC Menu entry added 1208359 ... Using Prepar3D with Academic License 1208359 User Aircraft ID 2 supplied, now being used 1208359 C:\Users\Michael\Documents\Prepar3D v4 Files\AutoSave Sun 165614.fxml 1208578 System time = 11/06/2017 16:56:21, Simulator time = 16:49:10 (14:49Z) 1508953 **** No SimConnect events or states being received! Re-connecting now ... **** 1509296 SimConnect_Open succeeded: waiting to check version okay 1509296 Opened separate AI Traffic client okay 1509296 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0) 1509296 Initialising SimConnect data requests now 1509296 FSUIPC Menu entry added 1509312 ... Using Prepar3D with Academic License 1509312 User Aircraft ID 2 supplied, now being used 1509312 C:\Users\Michael\Documents\Prepar3D v4 Files\AutoSave Sun 170113.fxml 1510109 System time = 11/06/2017 17:01:23, Simulator time = 16:54:03 (14:54Z) 1808281 **** No SimConnect events or states being received! Re-connecting now ... **** 1808625 SimConnect_Open succeeded: waiting to check version okay 1808625 Opened separate AI Traffic client okay 1808640 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0) 1808640 Initialising SimConnect data requests now 1808640 FSUIPC Menu entry added 1808640 ... Using Prepar3D with Academic License 1808640 User Aircraft ID 2 supplied, now being used 1808640 C:\Users\Michael\Documents\Prepar3D v4 Files\AutoSave Sun 170613.fxml 1809515 System time = 11/06/2017 17:06:22, Simulator time = 16:58:54 (14:58Z) 2108046 **** No SimConnect events or states being received! Re-connecting now ... **** 2108406 SimConnect_Open succeeded: waiting to check version okay 2108406 Opened separate AI Traffic client okay 2108406 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0) 2108406 Initialising SimConnect data requests now 2108406 FSUIPC Menu entry added 2108406 ... Using Prepar3D with Academic License 2108406 User Aircraft ID 2 supplied, now being used 2108406 C:\Users\Michael\Documents\Prepar3D v4 Files\AutoSave Sun 171112.fxml 2109062 System time = 11/06/2017 17:11:22, Simulator time = 17:03:45 (15:03Z) 2405609 **** No SimConnect events or states being received! Re-connecting now ... **** 2405953 SimConnect_Open succeeded: waiting to check version okay 2405953 Opened separate AI Traffic client okay 2405953 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0) 2405953 Initialising SimConnect data requests now 2405953 FSUIPC Menu entry added 2405953 ... Using Prepar3D with Academic License 2405953 User Aircraft ID 2 supplied, now being used 2405968 C:\Users\Michael\Documents\Prepar3D v4 Files\AutoSave Sun 171612.fxml 2406671 System time = 11/06/2017 17:16:19, Simulator time = 17:08:36 (15:08Z) 2706953 **** No SimConnect events or states being received! Re-connecting now ... **** 2707296 SimConnect_Open succeeded: waiting to check version okay 2707296 Opened separate AI Traffic client okay 2707296 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0) 2707296 Initialising SimConnect data requests now 2707296 FSUIPC Menu entry added 2707312 ... Using Prepar3D with Academic License 2707312 User Aircraft ID 2 supplied, now being used 2707312 C:\Users\Michael\Documents\Prepar3D v4 Files\AutoSave Sun 172111.fxml 2708140 System time = 11/06/2017 17:21:21, Simulator time = 17:13:29 (15:13Z) 3005000 **** No SimConnect events or states being received! Re-connecting now ... **** 3005343 SimConnect_Open succeeded: waiting to check version okay 3005343 Opened separate AI Traffic client okay 3005359 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0) 3005359 Initialising SimConnect data requests now 3005359 FSUIPC Menu entry added 3005359 ... Using Prepar3D with Academic License 3005359 User Aircraft ID 2 supplied, now being used 3005359 C:\Users\Michael\Documents\Prepar3D v4 Files\AutoSave Sun 172611.fxml 3006140 System time = 11/06/2017 17:26:19, Simulator time = 17:18:20 (15:18Z) Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 11, 2017 Report Share Posted June 11, 2017 13 minutes ago, Wimma said: in the Modules folder is only: FSUIPC5 Install FSUIPC5 .DLL FSUIPC5 FSUIPC5.joyscan FSUIPC5.key FSUIPC5 Oh dear. If you followed the User Guide inbstructions to tell Windows to stop hiding the file types from you, it would be obvious! The "FSUIPC5 Install" is actually "FSUIPC Install.log". One of the "FSUIPC5" files is "FSUIPC5.log" and the other "FSUIPC5.ini" (the latter contains all your FSUIPC settings). The "FSUIPC5.JoyScan" file is "FSUIPC5.JoyScan.csv". Unless you turn off that stupidly annoying Windows folder option yo will have continuing difficulties finding needed files. Pete Link to comment Share on other sites More sharing options...
Wimma Posted June 11, 2017 Author Report Share Posted June 11, 2017 I am terribly sorry for making those mistakes. I really am. So it is this one then. Michael FSUIPC5.log Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 11, 2017 Report Share Posted June 11, 2017 11 minutes ago, Wimma said: Well I think it is this one. it just doesnt say .log its a text document for me. hope i got the right one. See my previous reply. I think your prtoblem is to do with using the PMDG 777 plus FSUIPC's AutoSave. When a flight is saved the PMDG complex aircraft effectivrely freeze the computer for seconds whilst they gather cockpit information to save. You either need to stop using AutoSave in FSUIPC with PMDG aircraft, or possibly (and this isn't guaranteed to work) extend the "SimConnectStallTime" in the FSUIPC5.INI fie. The number there is in seconds, ranging 1 to 20. Since Autosaving when using such aircraft will create disjointed flights (bad hesitations), I would recommend you just stop using Autosave -- do flight saving manually before any crucial stages of flight, like approach. Incidentally, you are still using the original version of FSUIPC5. It has been updated many times since then. You should update to 5.101m, available in the Download Links subforum. Pete Link to comment Share on other sites More sharing options...
Wimma Posted June 11, 2017 Author Report Share Posted June 11, 2017 Ok. well as I said I am sorry for that mistake i made. I have to say you support is spot on and extremely fast, you guys are doing a fantastic job. I will turn autosave of and save manually as suggested. Thanks for everything. Greeting to both of you from Austria, Michael Link to comment Share on other sites More sharing options...
biloo Posted June 25, 2017 Report Share Posted June 25, 2017 On 6/11/2017 at 11:42 AM, Wimma said: Ok. well as I said I am sorry for that mistake i made. I have to say you support is spot on and extremely fast, you guys are doing a fantastic job. I will turn autosave of and save manually as suggested. Thanks for everything. Greeting to both of you from Austria, Michael Hi, I am just curious with the updated FSUIPC5 are you still having issues with autosave feature with PMDG T7 aircraft in P3D V4 or is the manual saving works best ? Link to comment Share on other sites More sharing options...
Thomas Richter Posted June 25, 2017 Report Share Posted June 25, 2017 Hi, Quote I am just curious with the updated FSUIPC5 are you still having issues with autosave feature with PMDG T7 aircraft in P3D V4 or is the manual saving works best ? you got that very wrong here. There is neither a problem with AutoSave function in FSUIPC4 nor in FSUIPC5, both work perfect correct. The problem is using FSUIPC's AutoSave function when having an PMDG aircraft selected, maybe other Add-on aircrafts are effected as well but PMDG's are best known for that, then a big amount of data is saved by PMDG that might take up to 10 seconds and freezes for that time the FS/P3D completely. The amount of data and which date is controlled by PMDG only and the function that saves it is build into FS/P3D, where FSUIPC4 / FSUIPC5 just calls that function to execute. FSUIPC is NOT involved in what data is saved and can also not change that. You can call that function manually yourself in FS/P3D direct defined, i.e. in P3Dv4 Save Scenario, to a key or button. You will find that you get the same effect, FS/P3D freezes for 5 to seconds completely. Because of that 'Saving Problem', the big amount of date that is saved, you shouldn't use the FSUIPC AutoSave function when flying a i.e. a PMDG aircraft. For any other aircraft, default or Add-on, that doesn't save that big amount of date the AutoSave function doesn't effect the joy of flying at all because the saving takes only a fraction of a second. This is well described in the FSUIPC manuals, located in folder ..\Modules\Documents\ Thomas 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