Terence Pang Posted June 28, 2017 Report Share Posted June 28, 2017 MOVED FROM FAQ SUBFORUM!!! HELP!!! I mainly use FSUIPC 5 for autosave. In P3D v4, it works fine when I launch the scenario. In the menu bar I can find FSUIPC as usual. But after taking off some time, maybe 45 min(?), then I press the Alt key and check the menu bar, the FSUIPC tap just disappears!! In every flight!!!!! Appreciate any help! Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 28, 2017 Report Share Posted June 28, 2017 Please ALWAYS use the Support Forum, not one of the Subforums, when requesting help. First please make sure you are using version 5.103, the currently supported version. Then, as always for Support Requests, the FSUIPC5.LOG file is needed. That will show what is going on. Close P3D4 down before retrieving the Log file (it'll be in the P3D4 Modules folder). Pete Link to comment Share on other sites More sharing options...
Terence Pang Posted June 29, 2017 Author Report Share Posted June 29, 2017 13 hours ago, Pete Dowson said: Please ALWAYS use the Support Forum, not one of the Subforums, when requesting help. First please make sure you are using version 5.103, the currently supported version. Then, as always for Support Requests, the FSUIPC5.LOG file is needed. That will show what is going on. Close P3D4 down before retrieving the Log file (it'll be in the P3D4 Modules folder). Pete Thanks. But may I know how to check my current version of FSUIPC? If an update is needed, may I know where to download the new version? Bought from simmarket. Thanks. Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 29, 2017 Report Share Posted June 29, 2017 1 hour ago, Terence Pang said: But may I know how to check my current version of FSUIPC? Oh dear. :-( How do you tell for ANY program? 1. The version number is displayed clearly in the main About tab in the FSUIPC Options in the SIM. 2. The version number is clearly stated by the Installer when you installed it. 3. The version number i shown in the first line of the FSUIPC5.LOG file in you P3D Modules folder. 4. The version number is shown in the "UpdatedBy" parameter in your settings file, FSUIPC5.INI 5. The version number, as for any prtogram, is shown in the Properties of rthe DLL itself, when you right-cick on it. 6. The version number is shown in the Updates document supplied, or in its absece in the Gistory document installed alongside all the other documentation and goodies you were told to read by the Installation document. 1 hour ago, Terence Pang said: If an update is needed, may I know where to download the new version? Same place as you got the original, or, for better choices and lots of other goodies, the obscurely named (?) "Download Links" subforum above. In fact that is where asll the links point to in any case. 1 hour ago, Terence Pang said: Bought from simmarket. SimMarket only sell the registration keys, they don't supply the program. They provide a link back to the Download Links subforum here which hosts all my files. Pete Link to comment Share on other sites More sharing options...
Terence Pang Posted June 29, 2017 Author Report Share Posted June 29, 2017 3 hours ago, Pete Dowson said: Oh dear. :-( How do you tell for ANY program? 1. The version number is displayed clearly in the main About tab in the FSUIPC Options in the SIM. 2. The version number is clearly stated by the Installer when you installed it. 3. The version number i shown in the first line of the FSUIPC5.LOG file in you P3D Modules folder. 4. The version number is shown in the "UpdatedBy" parameter in your settings file, FSUIPC5.INI 5. The version number, as for any prtogram, is shown in the Properties of rthe DLL itself, when you right-cick on it. 6. The version number is shown in the Updates document supplied, or in its absece in the Gistory document installed alongside all the other documentation and goodies you were told to read by the Installation document. Same place as you got the original, or, for better choices and lots of other goodies, the obscurely named (?) "Download Links" subforum above. In fact that is where asll the links point to in any case. SimMarket only sell the registration keys, they don't supply the program. They provide a link back to the Download Links subforum here which hosts all my files. Pete Thanks. Just flew with the new version of FSUIPC. Same problem. Here is the log file. ********* FSUIPC5, Version 5.103 (26th June 2017) by Pete Dowson ********* Running inside Prepar3D v4 Module base=7FFCC55C0000 Windows 10 Home 64 Bit reported as Build 15063, Release ID: 1703 (OS 10.0) Prepar3D.exe version = 4.0.23.21468 Checking the Registrations now ... User Name="Terence Pang" User Addr="pangkinglim@yahoo.com.hk" FSUIPC5 Key is provided WIDEFS7 not user registered, or expired 16 System time = 29/06/2017 16:58:21 16 FLT path = "D:\User Data\Documents\Prepar3D v4 Files\" 16 ------ Module Version Check ------ 16 acontain.dll: 4.0.23.21468 16 api.dll: 4.0.23.21468 16 controls.dll: 4.0.23.21468 16 fs-traffic.dll: 4.0.23.21468 16 G3D.dll: 4.0.23.21468 16 language.dll: 4.0.23.21468 16 sim1.dll: 4.0.23.21468 16 visualfx.dll: 4.0.23.21468 16 weather.dll: 4.0.23.21468 16 window.dll: 4.0.23.21468 16 ---------------------------------- 31 FS path = "D:\Lockheed Martin\Prepar3D v4\" 141 ---------------------- Joystick Device Scan ----------------------- 141 Product= Controller (XBOX 360 For Windows) 141 Vendor=045E, Product=028E (Version 0.0) 141 GUIDs returned for product: VID_045E&PID_028E: 141 GUID= {AF0E9740-898A-11E6-8001-444553540000} 141 Details: Btns=10, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U65535,V65535,X65535,Y65535,Z65535 141 GUID= {6A73D430-C93E-11E6-8001-444553540000} 141 Details: Btns=10, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U65535,V65535,X65535,Y65535,Z65535 141 Product= CH PRO PEDALS USB 156 Manufacturer= CH PRODUCTS 156 Vendor=068E, Product=00F2 (Version 0.0) 156 GUIDs returned for product: VID_068E&PID_00F2: 156 GUID= {250E34B0-8CEB-11E6-8001-444553540000} 156 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255 156 Product= Controller (XBOX 360 For Windows) 156 Vendor=045E, Product=028E (Version 0.0) 156 Product= T.Flight Hotas 4 156 Manufacturer= Thrustmaster 156 Vendor=044F, Product=B67C (Version 1.16) 156 GUIDs returned for product: VID_044F&PID_B67C: 156 GUID= {650D7A10-E66B-11E6-8001-444553540000} 156 Details: Btns=12, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U255,V255,X1023,Y1023,Z255 156 Product= CH FLIGHT SIM YOKE USB 156 Manufacturer= CH PRODUCTS 156 Vendor=068E, Product=00FF (Version 0.0) 156 GUIDs returned for product: VID_068E&PID_00FF: 156 GUID= {2512EFA0-8CEB-11E6-8003-444553540000} 156 Details: Btns=12, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U255,V255,X255,Y255,Z255 156 ------------------------------------------------------------------- 156 Device acquired for use: 156 Joystick ID = 1 (Registry okay) 156 1=Controller (XBOX 360 For Windows) 156 1.GUID={AF0E9740-898A-11E6-8001-444553540000} 156 Device acquired for use: 156 Joystick ID = 2 (Registry okay) 156 2=Controller (XBOX 360 For Windows) 156 2.GUID={6A73D430-C93E-11E6-8001-444553540000} 156 Device acquired for use: 156 Joystick ID = 0 (Registry okay) 156 0=CH PRO PEDALS USB 156 0.GUID={250E34B0-8CEB-11E6-8001-444553540000} 156 Device acquired for use: 156 Joystick ID = 4 (Registry okay) 156 4=T.Flight Hotas 4 156 4.GUID={650D7A10-E66B-11E6-8001-444553540000} 156 Device acquired for use: 156 Joystick ID = 3 (Registry okay) 156 3=CH FLIGHT SIM YOKE USB 156 3.GUID={2512EFA0-8CEB-11E6-8003-444553540000} 156 ------------------------------------------------------------------- 234 LogOptions=00000000 00000001 250 SimConnect_Open succeeded: waiting to check version okay 250 Opened separate AI Traffic client okay 36906 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0) 36906 Initialising SimConnect data requests now 36906 FSUIPC Menu entry added 36906 ... Using Prepar3D with Professional Plus License 36937 C:\Users\User\AppData\Local\Lockheed Martin\Prepar3D v4\Prepar3D_Default.fxml 36937 D:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air 47172 Weather Mode now = Theme 148000 D:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\PMDG 777-200LR\B777-200LR.air 268141 User Aircraft ID 4 supplied, now being used 268156 Aircraft loaded: running normally now ... 269016 System time = 29/06/2017 17:02:50, Simulator time = 16:00:10 (08:00Z) 269031 Aircraft="PMDG 777-267LR Cathay Pacific Airways (Fictional)" 328969 **** Restarting traffic scanning due to non-reception **** 329594 Starting everything now ... 329609 ASN active function link set 329609 Ready for ASN WX radar 330656 Advanced Weather Interface Enabled 376594 Sim stopped: average frame rate for last 57 secs = 33.8 fps 376594 Max AI traffic was 37 aircraft (Deleted 0) 568547 **** No SimConnect events or states being received! Re-connecting now ... **** 568891 SimConnect_Open succeeded: waiting to check version okay 568891 Opened separate AI Traffic client okay 568906 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0) 568906 Initialising SimConnect data requests now 568906 FSUIPC Menu entry added 568906 ... Using Prepar3D with Professional Plus License 568906 User Aircraft ID 4 supplied, now being used 568906 D:\User Data\Documents\Prepar3D v4 Files\AutoSave Thu 170742.fxml 568953 System time = 29/06/2017 17:07:50, Simulator time = 16:03:41 (08:03Z) 927969 **** No SimConnect events or states being received! Re-connecting now ... **** 928328 SimConnect_Open succeeded: waiting to check version okay 928328 Opened separate AI Traffic client okay 928328 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0) 928328 Initialising SimConnect data requests now 928328 FSUIPC Menu entry added 928328 ... Using Prepar3D with Professional Plus License 928328 User Aircraft ID 4 supplied, now being used 928328 D:\User Data\Documents\Prepar3D v4 Files\AutoSave Thu 171341.fxml 928656 System time = 29/06/2017 17:13:49, Simulator time = 16:09:33 (08:09Z) 1286625 **** No SimConnect events or states being received! Re-connecting now ... **** 1286984 SimConnect_Open succeeded: waiting to check version okay 1286984 Opened separate AI Traffic client okay 1286984 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0) 1286984 Initialising SimConnect data requests now 1286984 FSUIPC Menu entry added 1286984 ... Using Prepar3D with Professional Plus License 1286984 User Aircraft ID 4 supplied, now being used 1286984 D:\User Data\Documents\Prepar3D v4 Files\AutoSave Thu 171940.fxml 1287234 System time = 29/06/2017 17:19:48, Simulator time = 16:14:11 (08:14Z) 1466906 **** No SimConnect events or states being received! Re-connecting now ... **** 1467250 SimConnect_Open succeeded: waiting to check version okay 1467250 Opened separate AI Traffic client okay 1467250 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0) 1467250 Initialising SimConnect data requests now 1467250 FSUIPC Menu entry added 1467266 ... Using Prepar3D with Professional Plus License 1467266 User Aircraft ID 4 supplied, now being used 1467266 D:\User Data\Documents\Prepar3D v4 Files\AutoSave Thu 172240.fxml 1467531 System time = 29/06/2017 17:22:48, Simulator time = 16:17:03 (08:17Z) 1645625 **** No SimConnect events or states being received! Re-connecting now ... **** 1645969 SimConnect_Open succeeded: waiting to check version okay 1645969 Opened separate AI Traffic client okay 1645969 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0) 1645969 Initialising SimConnect data requests now 1645969 FSUIPC Menu entry added 1645984 ... Using Prepar3D with Professional Plus License 1645984 User Aircraft ID 4 supplied, now being used 1645984 D:\User Data\Documents\Prepar3D v4 Files\AutoSave Thu 172539.fxml 1646031 System time = 29/06/2017 17:25:47, Simulator time = 16:19:54 (08:19Z) 1825125 **** No SimConnect events or states being received! Re-connecting now ... **** 1825484 SimConnect_Open succeeded: waiting to check version okay 1825484 Opened separate AI Traffic client okay 1825484 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0) 1825484 Initialising SimConnect data requests now 1825484 FSUIPC Menu entry added 1825484 ... Using Prepar3D with Professional Plus License 1825484 User Aircraft ID 4 supplied, now being used 1825500 D:\User Data\Documents\Prepar3D v4 Files\AutoSave Thu 172839.fxml 1825703 System time = 29/06/2017 17:28:46, Simulator time = 16:22:34 (08:22Z) 2004766 **** No SimConnect events or states being received! Re-connecting now ... **** 2005109 SimConnect_Open succeeded: waiting to check version okay 2005109 Opened separate AI Traffic client okay 2005109 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0) 2005109 Initialising SimConnect data requests now 2005109 FSUIPC Menu entry added 2005125 ... Using Prepar3D with Professional Plus License 2005125 User Aircraft ID 4 supplied, now being used 2005125 D:\User Data\Documents\Prepar3D v4 Files\AutoSave Thu 173138.fxml 2005172 System time = 29/06/2017 17:31:46, Simulator time = 16:25:26 (08:25Z) 2184297 **** No SimConnect events or states being received! Re-connecting now ... **** 2184656 SimConnect_Open succeeded: waiting to check version okay 2184656 Opened separate AI Traffic client okay 2184656 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0) 2184656 Initialising SimConnect data requests now 2184656 FSUIPC Menu entry added 2184656 ... Using Prepar3D with Professional Plus License 2184656 User Aircraft ID 4 supplied, now being used 2184672 D:\User Data\Documents\Prepar3D v4 Files\AutoSave Thu 173438.fxml 2185516 System time = 29/06/2017 17:34:46, Simulator time = 16:28:19 (08:28Z) 2365125 **** No SimConnect events or states being received! Re-connecting now ... **** 2365484 SimConnect_Open succeeded: waiting to check version okay 2365484 Opened separate AI Traffic client okay 2365484 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0) 2365484 Initialising SimConnect data requests now 2365484 FSUIPC Menu entry added 2365500 ... Using Prepar3D with Professional Plus License 2365500 User Aircraft ID 4 supplied, now being used 2365500 D:\User Data\Documents\Prepar3D v4 Files\AutoSave Thu 173737.fxml 2365547 System time = 29/06/2017 17:37:46, Simulator time = 16:31:11 (08:31Z) 2542937 **** No SimConnect events or states being received! Re-connecting now ... **** 2543281 SimConnect_Open succeeded: waiting to check version okay 2543281 Opened separate AI Traffic client okay 2543281 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0) 2543281 Initialising SimConnect data requests now 2543281 FSUIPC Menu entry added 2543297 ... Using Prepar3D with Professional Plus License 2543297 User Aircraft ID 4 supplied, now being used 2543297 D:\User Data\Documents\Prepar3D v4 Files\AutoSave Thu 174037.fxml 2543594 System time = 29/06/2017 17:40:44, Simulator time = 16:34:02 (08:34Z) 2722734 **** No SimConnect events or states being received! Re-connecting now ... **** 2723078 SimConnect_Open succeeded: waiting to check version okay 2723078 Opened separate AI Traffic client okay 2723094 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0) 2723094 Initialising SimConnect data requests now 2723094 FSUIPC Menu entry added 2723094 ... Using Prepar3D with Professional Plus License 2723094 User Aircraft ID 4 supplied, now being used 2723094 D:\User Data\Documents\Prepar3D v4 Files\AutoSave Thu 174336.fxml 2724078 System time = 29/06/2017 17:43:45, Simulator time = 16:36:55 (08:36Z) 2902312 **** No SimConnect events or states being received! Re-connecting now ... **** 2902656 SimConnect_Open succeeded: waiting to check version okay 2902656 Opened separate AI Traffic client okay 2902672 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0) 2902672 Initialising SimConnect data requests now 2902672 FSUIPC Menu entry added 2902672 ... Using Prepar3D with Professional Plus License 2902672 User Aircraft ID 4 supplied, now being used 2902672 D:\User Data\Documents\Prepar3D v4 Files\AutoSave Thu 174636.fxml 2903656 System time = 29/06/2017 17:46:44, Simulator time = 16:39:47 (08:39Z) 3081625 **** No SimConnect events or states being received! Re-connecting now ... **** 3081984 SimConnect_Open succeeded: waiting to check version okay 3081984 Opened separate AI Traffic client okay 3081984 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0) 3081984 Initialising SimConnect data requests now 3081984 FSUIPC Menu entry added 3081984 ... Using Prepar3D with Professional Plus License 3081984 User Aircraft ID 4 supplied, now being used 3081984 D:\User Data\Documents\Prepar3D v4 Files\AutoSave Thu 174935.fxml 3082047 System time = 29/06/2017 17:49:43, Simulator time = 16:42:38 (08:42Z) 3261000 **** No SimConnect events or states being received! Re-connecting now ... **** 3261359 SimConnect_Open succeeded: waiting to check version okay 3261359 Opened separate AI Traffic client okay 3261359 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0) 3261359 Initialising SimConnect data requests now 3261359 FSUIPC Menu entry added 3261359 ... Using Prepar3D with Professional Plus License 3261359 User Aircraft ID 4 supplied, now being used 3261359 D:\User Data\Documents\Prepar3D v4 Files\AutoSave Thu 175235.fxml 3261828 System time = 29/06/2017 17:52:43, Simulator time = 16:45:31 (08:45Z) 3441828 **** No SimConnect events or states being received! Re-connecting now ... **** 3442172 SimConnect_Open succeeded: waiting to check version okay 3442172 Opened separate AI Traffic client okay 3442187 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0) 3442187 Initialising SimConnect data requests now 3442187 FSUIPC Menu entry added 3442187 ... Using Prepar3D with Professional Plus License 3442187 User Aircraft ID 4 supplied, now being used 3442203 D:\User Data\Documents\Prepar3D v4 Files\AutoSave Thu 175534.fxml 3442359 System time = 29/06/2017 17:55:43, Simulator time = 15:48:23 (08:48Z) 3620641 **** No SimConnect events or states being received! Re-connecting now ... **** 3620984 SimConnect_Open succeeded: waiting to check version okay 3620984 Opened separate AI Traffic client okay 3620984 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0) 3620984 Initialising SimConnect data requests now 3620984 FSUIPC Menu entry added 3621000 ... Using Prepar3D with Professional Plus License 3621000 User Aircraft ID 4 supplied, now being used 3621000 D:\User Data\Documents\Prepar3D v4 Files\AutoSave Thu 175834.fxml 3621172 System time = 29/06/2017 17:58:42, Simulator time = 15:51:14 (08:51Z) 3800984 **** No SimConnect events or states being received! Re-connecting now ... **** 3801344 SimConnect_Open succeeded: waiting to check version okay 3801344 Opened separate AI Traffic client okay 3801359 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0) 3801359 Initialising SimConnect data requests now 3801359 FSUIPC Menu entry added 3801375 ... Using Prepar3D with Professional Plus License 3801375 User Aircraft ID 4 supplied, now being used 3801375 D:\User Data\Documents\Prepar3D v4 Files\AutoSave Thu 180133.fxml 3801875 System time = 29/06/2017 18:01:43, Simulator time = 15:54:06 (08:54Z) 3979891 **** No SimConnect events or states being received! Re-connecting now ... **** 3980234 SimConnect_Open succeeded: waiting to check version okay 3980234 Opened separate AI Traffic client okay 3980250 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0) 3980250 Initialising SimConnect data requests now 3980250 FSUIPC Menu entry added 3980250 ... Using Prepar3D with Professional Plus License 3980250 User Aircraft ID 4 supplied, now being used 3980266 D:\User Data\Documents\Prepar3D v4 Files\AutoSave Thu 180433.fxml 3980953 System time = 29/06/2017 18:04:42, Simulator time = 15:56:57 (08:56Z) 4159297 **** No SimConnect events or states being received! Re-connecting now ... **** 4159656 SimConnect_Open succeeded: waiting to check version okay 4159656 Opened separate AI Traffic client okay 4159656 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0) 4159656 Initialising SimConnect data requests now 4159656 FSUIPC Menu entry added 4159656 ... Using Prepar3D with Professional Plus License 4159656 User Aircraft ID 4 supplied, now being used 4159672 D:\User Data\Documents\Prepar3D v4 Files\AutoSave Thu 180732.fxml 4159953 System time = 29/06/2017 18:07:41, Simulator time = 15:59:48 (08:59Z) 4338516 **** No SimConnect events or states being received! Re-connecting now ... **** 4338859 SimConnect_Open succeeded: waiting to check version okay 4338859 Opened separate AI Traffic client okay 4338859 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0) 4338859 Initialising SimConnect data requests now 4338859 FSUIPC Menu entry added 4338875 ... Using Prepar3D with Professional Plus License 4338875 User Aircraft ID 4 supplied, now being used 4338875 D:\User Data\Documents\Prepar3D v4 Files\AutoSave Thu 181032.fxml 4339250 System time = 29/06/2017 18:10:40, Simulator time = 16:02:40 (09:02Z) 4518016 **** No SimConnect events or states being received! Re-connecting now ... **** 4518375 SimConnect_Open succeeded: waiting to check version okay 4518375 Opened separate AI Traffic client okay 4528078 **** No SimConnect events or states being received! Re-connecting now ... **** 4528422 SimConnect_Open succeeded: waiting to check version okay 4528422 Opened separate AI Traffic client okay 4538125 **** No SimConnect events or states being received! Re-connecting now ... **** 4538484 SimConnect_Open succeeded: waiting to check version okay 4538484 Opened separate AI Traffic client okay 4548125 **** No SimConnect events or states being received! Re-connecting now ... **** 4548484 SimConnect_Open succeeded: waiting to check version okay 4548484 Opened separate AI Traffic client okay 4593812 **** No SimConnect events or states being received! Re-connecting now ... **** 4594156 SimConnect_Open succeeded: waiting to check version okay 4607562 Failed on SimConnect_Open for AI Traffic Client, return = 0x80004005 4666375 **** No SimConnect events or states being received! Re-connecting now ... **** 4666734 SimConnect_Open succeeded: waiting to check version okay 4728234 **** No SimConnect events or states being received! Re-connecting now ... **** 4742000 Failed on SimConnect_Open, return = 0x80004005: FSUIPC5 cannot operate! 4742000 ... Now trying to connect to another version of SimConnect ... 4755406 Failed on SimConnect_Open, return = 0x80004005: FSUIPC5 cannot operate! 4755406 ... Now trying to connect to another version of SimConnect ... 4768812 Failed on SimConnect_Open, return = 0x80004005: FSUIPC5 cannot operate! 4768812 ... Now trying to connect to another version of SimConnect ... 4782219 Failed on SimConnect_Open, return = 0x80004005: FSUIPC5 cannot operate! 7784453 === Closing session: waiting for DLLStop to be called ... 7805641 === DLLStop called ... 7805641 === Closing external processes we started ... 7806641 === About to kill any Lua plug-ins still running ... 7806781 === Closing global Lua thread 7807781 === About to kill my timers ... 7807984 === Restoring window procs ... 7807984 === Unloading libraries ... 7807984 === stopping other threads ... 7807984 === ... Button scanning ... 7808094 === ... Axis scanning ... 7808187 === Releasing joystick devices ... 7808187 === Freeing macro memory 7808187 === Removing any offset overrides 7808187 === Clearing any displays left 7808187 === AI slots deleted! 7808187 === Freeing button memory ... 7808187 === Closing my Windows ... 7808187 === Freeing FS libraries ... 7809203 === Closing devices ... 7809203 === Closing the Log ... Bye Bye! ... 7809203 System time = 29/06/2017 19:08:30, Simulator time = 16:05:31 (09:05Z) 7809203 *** FSUIPC log file being closed Minimum frame rate was 23.8 fps, Maximum was 63.7 fps Average frame rate for running time of 4037 secs = 42.3 fps Maximum AI traffic for session was 41 aircraft Memory managed: 1902 Allocs, 1901 Freed ********* FSUIPC Log file closed *********** Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 29, 2017 Report Share Posted June 29, 2017 14 minutes ago, Terence Pang said: Just flew with the new version of FSUIPC. Same problem. I didn't expect it to change anything, but the log would be more appropriate. It shows: 15 minutes ago, Terence Pang said: 4159672 D:\User Data\Documents\Prepar3D v4 Files\AutoSave Thu 180732.fxml 4159953 System time = 29/06/2017 18:07:41, Simulator time = 15:59:48 (08:59Z) 4338516 **** No SimConnect events or states being received! Re-connecting now ... **** which means the sim was frozen for so long that SimConnect stopped sending data to FSUIPC. The reason is that you are using a complex PMDG aircraft and you've enabled AutoSave in FSUIPC. You'll need to disable that. The PMDG aircraft are designed to save every detail of their state whenever they see a flight being saved. They actually freeze the whole Sim whilst they do this. It is that which causes the SimConnect disconnection. (They could simply freeze the aircraft and let the rest carry on, but they don't, which is a shame). There is a parameter in FSUIPC which controls how long FSUIPC will tolerate between data updates. You could increase that but I think not by enough. Anyway, even if this stopped FSUIPC getting the data, you'd experience long pauses every time a flight is autosaved, ruining your enjoyment. So disable Autosave (it does default off), and just do a manual autosave before any critical operation. Pete Link to comment Share on other sites More sharing options...
Terence Pang Posted June 29, 2017 Author Report Share Posted June 29, 2017 27 minutes ago, Pete Dowson said: I didn't expect it to change anything, but the log would be more appropriate. It shows: which means the sim was frozen for so long that SimConnect stopped sending data to FSUIPC. The reason is that you are using a complex PMDG aircraft and you've enabled AutoSave in FSUIPC. You'll need to disable that. The PMDG aircraft are designed to save every detail of their state whenever they see a flight being saved. They actually freeze the whole Sim whilst they do this. It is that which causes the SimConnect disconnection. (They could simply freeze the aircraft and let the rest carry on, but they don't, which is a shame). There is a parameter in FSUIPC which controls how long FSUIPC will tolerate between data updates. You could increase that but I think not by enough. Anyway, even if this stopped FSUIPC getting the data, you'd experience long pauses every time a flight is autosaved, ruining your enjoyment. So disable Autosave (it does default off), and just do a manual autosave before any critical operation. Pete Thanks. What a pity that I cannot use the autosave function. Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 29, 2017 Report Share Posted June 29, 2017 It's a pity PMDG don't simply freeze the aircraft operations themselves rather than the whole sim. Perhaps they haven't found a way. Mind you, you'd still get pauses whilst flying. Maybe they should just make memory copies rather than create files. Pete Link to comment Share on other sites More sharing options...
RandyD59 Posted July 5, 2017 Report Share Posted July 5, 2017 Pete, It seems a few of us in our VA are having the same issue with auto save. But we do have one person that is not having this problem. cant figure that one. Since the primary reason we all bought this was for the auto save feature it stands that we should be working through this. Additionally, when FSUIPC fails it stops SmartCars from recording as well. Even if the flight makes it we can log it. I dont know of any one who has any issues with the auto save in V3, so the problem is new to V4. I have attached log files for SmartCars and FSUIPC for your reading pleasure just in case it is some other issue. Above you mentioned that we could extend the time FSUIPC will wait for the save. How exactly is that done? I dont mind the sim pausing every 20 minutes for 15 seconds if it save a 14 hour flight. Awaiting your words. Randy Error logs.rar Link to comment Share on other sites More sharing options...
Thomas Richter Posted July 5, 2017 Report Share Posted July 5, 2017 Hi, as your FSUIPC log file shows you use PMDG add-on aircraft and it is here and also in the FSUIPC manual very clear described to DON'T use AutoSave facility in FSUIPC because PMDG forces FS/P3D to freeze for the time of saving and because PMDG saves a big bunch of data that forces SimConnect to stall. The SimConnect stall will result in a disconnection of all SimConnect related programs. 108890 E:\P3D v4\SimObjects\Airplanes\PMDG 777-200LR\B777-200LR.air There is NO workaround that other than don't use AutoSave. What you could do instead is assigning a key in FSUIPC or FS/P3D to save the flight, then any time you want. Thomas Link to comment Share on other sites More sharing options...
Luke Kolin Posted July 5, 2017 Report Share Posted July 5, 2017 4 hours ago, Thomas Richter said: There is NO workaround that other than don't use AutoSave. What you could do instead is assigning a key in FSUIPC or FS/P3D to save the flight, then any time you want. Thomas/Pete - I think the situation is more complicated than that. I built an autosave feature into Delta/Air France Virtual's ACARS software because I believe strongly in the feature and it's tied into the actual flight recording - I won't persist the data on my end until the flight has been saved on the client. One thing that I do a little differently is that I apply a different ratio to the autosave interval depending on the payware aircraft in use. As an example, I save flights on the PMDG777 every 9 minutes and don't do so when within 30-40 miles of either airport. I can regularly do 8+ hour flights without running into issues with SimConnect disconnecting. I wonder whether there isn't something in the PMDG flight saving code that leaks memory or does something that makes each save incrementally longer? My guess is that the problem is exacerbated by the number of saves, and each save is getting slower and slower. I expect someone with a PMDG777X could test this by turning on autosave and setting the interval to something low like 5 seconds and see when things kicked in. And Randy, FWIW I have seen numerous reports of this problem in P3Dv3 and FSX. It's not new to P3Dv4. Cheers! Luke Link to comment Share on other sites More sharing options...
Luke Kolin Posted July 5, 2017 Report Share Posted July 5, 2017 ********* FSUIPC5, Version 5.103e (3rd July 2017) by Pete Dowson ********* Running inside Prepar3D v4 Module base=7FED2D00000 Windows 7 Ultimate 64 Bit with SP 1.0 reported as Build 7601 (OS 6.1) Prepar3D.exe version = 4.0.28.21686 Checking the Registrations now ... User Name="Luke Kolin" User Addr="luke@kolin.org" FSUIPC5 Key is provided WIDEFS7 not user registered, or expired 0 System time = 04/07/2017 15:13:32 0 FLT path = "C:\Users\luke.POLARIS\Documents\Prepar3D v4 Files\" 15 ------ Module Version Check ------ 15 acontain.dll: 4.0.28.21686 15 api.dll: 4.0.28.21686 15 controls.dll: 4.0.28.21686 15 fs-traffic.dll: 4.0.28.21686 15 G3D.dll: 4.0.28.21686 15 language.dll: 4.0.28.21686 15 sim1.dll: 4.0.28.21686 15 visualfx.dll: 4.0.28.21686 15 weather.dll: 4.0.28.21686 15 window.dll: 4.0.28.21686 15 ---------------------------------- 15 FS path = "D:\Program Files\Prepar3D v4\" 140 ---------------------- Joystick Device Scan ----------------------- 140 Product= CH PRO THROTTLE USB 140 Manufacturer= CH PRODUCTS 140 Vendor=068E, Product=00F1 (Version 0.0) 140 GUIDs returned for product: VID_068E&PID_00F1: 140 GUID= {8AC6B6E0-DEC1-11E3-8001-444553540000} 140 Details: Btns=19, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X245,Y242,Z228 140 Product= CH PRO PEDALS USB 140 Manufacturer= CH PRODUCTS 156 Vendor=068E, Product=00F2 (Version 0.0) 156 GUIDs returned for product: VID_068E&PID_00F2: 156 GUID= {8AC6B6E0-DEC1-11E3-8002-444553540000} 156 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z254 156 Product= CH FLIGHT SIM YOKE USB 156 Manufacturer= CH PRODUCTS 156 Vendor=068E, Product=00FF (Version 0.0) 156 GUIDs returned for product: VID_068E&PID_00FF: 156 GUID= {907D8530-E044-11E3-8001-444553540000} 156 Details: Btns=12, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U255,V255,X255,Y255,Z255 156 ------------------------------------------------------------------- 156 Device acquired for use: 156 Joystick ID = 2 (Registry okay) 156 2=CH PRO THROTTLE USB 156 2.GUID={8AC6B6E0-DEC1-11E3-8001-444553540000} 156 Device acquired for use: 156 Joystick ID = 1 (Registry okay) 156 1=CH PRO PEDALS USB 156 1.GUID={8AC6B6E0-DEC1-11E3-8002-444553540000} 156 Device acquired for use: 156 Joystick ID = 0 (Registry okay) 156 0=CH FLIGHT SIM YOKE USB 156 0.GUID={907D8530-E044-11E3-8001-444553540000} 156 ------------------------------------------------------------------- 156 LogOptions=00000000 00000001 156 SimConnect_Open succeeded: waiting to check version okay 156 Opened separate AI Traffic client okay 2839 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.28.21686 (SimConnect: 4.0.0.0) 2839 Initialising SimConnect data requests now 2839 FSUIPC Menu entry added 2839 ... Using Prepar3D with Academic License 2855 C:\Users\luke.POLARIS\AppData\Local\Lockheed Martin\Prepar3D v4\Prepar3D_Default.fxml 2855 D:\Program Files\Prepar3D v4\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air 39562 D:\Program Files\Prepar3D v4\SimObjects\Airplanes\PMDG 777-200LR\B777-200LR.air 68515 Aircraft loaded: running normally now ... 68515 User Aircraft ID 1 supplied, now being used 69030 System time = 04/07/2017 15:14:41, Simulator time = 10:12:36 (08:12Z) 69030 Aircraft="PMDG 777-206LR KLM Royal Dutch Airlines (Fictional)" 75972 Starting everything now ... 76066 ASN active function link set 76066 Ready for ASN WX radar 76393 Weather Mode now = Theme 77314 Advanced Weather Interface Enabled 688916 Sim stopped: average frame rate for last 620 secs = 14.5 fps 688916 Max AI traffic was 10 aircraft (Deleted 0) 4662526 **** Restarting traffic scanning due to non-reception **** 31179998 Sim stopped: average frame rate for last 30450 secs = 27.7 fps 31179998 Max AI traffic was 16 aircraft (Deleted 0) 31884405 Sim stopped: average frame rate for last 553 secs = 16.9 fps 31884405 Max AI traffic was 16 aircraft (Deleted 0) 31885653 === Closing session: waiting for DLLStop to be called ... 31901783 === DLLStop called ... 31901783 === Closing external processes we started ... 31902781 === About to kill any Lua plug-ins still running ... 31902922 === Closing global Lua thread 31903936 === About to kill my timers ... 31904139 === Restoring window procs ... 31904139 === Unloading libraries ... 31904139 === stopping other threads ... 31904139 === ... Button scanning ... 31904232 === ... Axis scanning ... 31904326 === Releasing joystick devices ... 31904326 === Freeing macro memory 31904326 === Removing any offset overrides 31904326 === Clearing any displays left 31904326 === Calling SimConnect_Close ... 31905043 === SimConnect_Close done! 31905043 === AI slots deleted! 31905043 === Freeing button memory ... 31905043 === Closing my Windows ... 31905043 === Freeing FS libraries ... 31906073 === Closing devices ... 31906073 === Closing the Log ... Bye Bye! ... 31906073 System time = 05/07/2017 00:05:18, Simulator time = 12:27:01 (16:27Z) 31906073 *** FSUIPC log file being closed Minimum frame rate was 8.8 fps, Maximum was 31.8 fps Average frame rate for running time of 31635 secs = 27.3 fps Maximum AI traffic for session was 16 aircraft Memory managed: 13238 Allocs, 13237 Freed ********* FSUIPC Log file closed *********** Link to comment Share on other sites More sharing options...
Pete Dowson Posted July 5, 2017 Report Share Posted July 5, 2017 5 hours ago, RandyD59 said: I dont know of any one who has any issues with the auto save in V3, so the problem is new to V4. No, there has always been many reports of problems with V3 as well, on all PMDG ircraft. You can try increasing the timeout (SimconnectStallTime) in the [General] section of the FSUIPC5.INI file. Max is 20 (secs) Default is 1 or 2. A longer time would possibly stop FSUIPC re-initialising its connection with SimConnect which would make things worse. There will stil be an effective freeze whilst PMDG's saves do their thing. Whether they are still too long for your applications I wouldn't know, but if so the only solution, apart from not using Autosave, is to make the programs more tolerant. Incidentally, I've already implemented the longer timeout which is automatically applied IF FSUIPC detects a FlightSave occurring. That's in 5.10e already released as an Interim update in the Download Links subforum. The only doubts I've got about that is whether, by the time SimConnect tries to notify FSUIPC the freeze is already underway. Of course if that is the case I could deal with it for FSUIPC's own AutoSave (since it is the instigator) but it wouldn't work for the other autosave facilities which are available. However, I will add it into FSUIPC for the next update. 22 minutes ago, Luke Kolin said: Cheers! Hi Luke: whatwas the purpose of the Log you sent, separately? Pete Link to comment Share on other sites More sharing options...
Luke Kolin Posted July 6, 2017 Report Share Posted July 6, 2017 Sorry, just to show that there wasn't anything untoward going on. I need to step out for a bit; I'll fire up the PMDG777 and set the autosave interval to something short and see what happens when I get back. Cheers! Link to comment Share on other sites More sharing options...
RandyD59 Posted July 6, 2017 Report Share Posted July 6, 2017 Thanks for looking into the save issue! I hoping we wont need this option at all in the future. With V4 the OOM problems are gone (for now anyway), but many are having CDTs. The latest issue for me is with SODE. SODE installed = CDT on longer flights. One thing I have noticed in V4 is when saving manually the save is much smoother than using auto save. Is that because the sim in being paused for the save operation? I'll download the latest FSUIPC and up the save time and see how that works and will let you know how it pans out. Regards, Randy Link to comment Share on other sites More sharing options...
Pete Dowson Posted July 6, 2017 Report Share Posted July 6, 2017 3 hours ago, RandyD59 said: One thing I have noticed in V4 is when saving manually the save is much smoother than using auto save. Is that because the sim in being paused for the save operation? No idea. I don't even understand what you could possibly mean by a "smoother" save". Is the autosave jerky in somne way? How? How can you tell? It's effectively paused in any case when PMDG take over. The call FSUIPc makes into P3D is identical to that made when you save manually. The only thing that's different is that FSIOPC provides the filename. Pete Link to comment Share on other sites More sharing options...
RandyD59 Posted July 6, 2017 Report Share Posted July 6, 2017 Yes. When it was auto saving the sim would stick for a few seconds (did this in V3) then seemed to do a jitter or two before returning to normal operation. After doing this for 1-5 hours FSUIPC would stop working and disappear from the addon dropdown. On a brighter side I have installed the 5.103e patch and have been flying for several hours and all is working as it was in V3. I'll pass this info to my VA members having troubles as I think it will solve their problems as well. I'l continue flights that will challenge the module and see if this is a dead issue. Thanks for your support! Randy Link to comment Share on other sites More sharing options...
RandyD59 Posted July 14, 2017 Report Share Posted July 14, 2017 Just a quick follow up note on the auto save issues: I have flown all the V4 PMDG aircraft (A2A and AS Twin Otter as well) on several flights now, my sim runs day and night, and have had zero problems since installing the 5.103e patch. Thank your so much for all you do with FSUIPC! 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