amit24075844 Posted March 6, 2016 Report Posted March 6, 2016 hi,I have a problem, my fsuipc stops working after about 3-4 hours in the air (in the sim) and I know that because I cant open it via the addons tap in the menubar at the top of my P3DV3.1 and also it makes problems with my aircrafts. in my airbus x v1.31 my speedbrake not working after this period of time for drag or for landing and at the start of the flight they are working because I am checking them. also my PMDG 777 latest version have problems. it stops functioning- the autopilot is on but the aircraft won't follow the VNAV and LNAV paths and also the autothrottles are on but not changing the engine rotation, manually it is working and also I cant control the aircraft manually - when I move my joystick I can see the control surfaces of the aircraft moving and also the 777 yoke is moving but the aircraft is not and than I fly till it crashes on land or at sea, what can I do? (I reinstalled fsuipc(4.949) sereval times and also the aircrafts)
Pete Dowson Posted March 6, 2016 Report Posted March 6, 2016 I have a problem, my fsuipc stops working after about 3-4 hours in the air (in the sim) and I know that because I cant open it via the addons tap in the menubar at the top of my P3DV3.1 Check the FSUIPC log. It sounds like your system is overloaded and SimConnect is stalling. and also it makes problems with my aircrafts. in my airbus x v1.31 my speedbrake not working after this period of time for drag or for landing and at the start of the flight they are working because I am checking them. also my PMDG 777 latest version have problems. Those aircraft have nothing at all in common with FSUIPC and are not related. They are also probably suffering from the overload where SimConnect is simply not responding quickly enough and eventually stalls. I cannot support other add-ons which have nothing to do with FSUIPC. Pete
amit24075844 Posted March 6, 2016 Author Report Posted March 6, 2016 93 System time = 06/03/2016 17:30:01 93 FLT UNC path = "\\AMIT-PC\Users\amits\Documents\Prepar3D v3 Files\" 93 ------ Module Version Check ------ 93 acontain.dll: 3.1.2.15831 93 api.dll: 3.1.2.15831 93 controls.dll: 3.1.2.15831 93 fs-traffic.dll: 3.1.2.15831 93 G3D.dll: 3.1.2.15831 125 language.dll: 3.1.2.15831 125 sim1.dll: 3.1.2.15831 125 visualfx.dll: 3.1.2.15831 125 weather.dll: 3.1.2.15831 125 window.dll: 3.1.2.15831 125 ---------------------------------- 125 Trying C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D2.dll 125 !!! Error 126: The specified module could not be found. 1421 Trying to connect to SimConnect Acc/SP2 Oct07 ... 1500 FS UNC path = "C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\" 1828 ---------------------- Joystick Device Scan ----------------------- 1843 Product= Logitech Extreme 3D 1843 Manufacturer= Logitech 1843 Vendor=046D, Product=C215 (Version 2.4) 1843 Serial Number= Logitech 1843 ------------------------------------------------------------------- 1890 LogOptions=00000000 00000001 1890 ------------------------------------------------------------------- 1890 ------ Setting the hooks and direct calls into the simulator ------ 1890 --- CONTROLS timer memory location obtained ok 1890 --- SIM1 Frictions access gained 1890 --- FS Controls Table located ok 1890 --- Installed Mouse Macro hooks ok. 1890 --- Wind smoothing fix is installed 1890 --- All links okay (except older global weather setting method) 1890 ------------------------------------------------------------------- 1890 SimConnect_Open succeeded: waiting to check version okay 1890 Trying to use SimConnect Acc/SP2 Oct07 149500 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.1.3.1 (SimConnect: 3.1.0.0) 149500 Initialising SimConnect data requests now 149500 FSUIPC Menu entry added 149531 \\AMIT-PC\Users\amits\AppData\Local\Lockheed Martin\Prepar3D v3\Prepar3D_Default.fxml 149531 C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air 230937 C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\SimObjects\Airplanes\PMDG 737-800NGX WL\B737-800WL.air 310906 System time = 06/03/2016 17:35:12, Simulator time = 17:33:28 (15:33Z) 311031 Aircraft="Boeing 737-8Q8NGX El Al Israel Airlines (4X-EKP) Winglets" 312375 Weather Mode now = Theme 316921 Starting everything now ... 316921 ASN active function link set 316921 Ready for ASN WX radar 371296 Sim stopped: average frame rate for last 61 secs = 24.0 fps 378937 Advanced Weather Interface Enabled 1310296 Sim stopped: average frame rate for last 919 secs = 37.4 fps 8624437 Sim stopped: average frame rate for last 7314 secs = 39.6 fps 9273140 Sim stopped: average frame rate for last 641 secs = 40.0 fps 10181562 Sim stopped: average frame rate for last 907 secs = 40.3 fps 13475281 Sim stopped: average frame rate for last 3292 secs = 41.5 fps 13503859 === NOTE: not calling SimConnect_Close ... 13504859 System time = 06/03/2016 21:15:05, Simulator time = 20:14:40 (19:14Z) 13504859 *** FSUIPC log file being closedMinimum frame rate was 9.9 fps, Maximum was 62.9 fpsMinimum available memory recorded was 1642MbAverage frame rate for running time of 13151 secs = 39.9 fpsMemory managed: 2997 Allocs, 2997 Freed********* FSUIPC Log file closed *********** this is my log
Pete Dowson Posted March 7, 2016 Report Posted March 7, 2016 this is my log What happened to the first lines? They are important too. Please don't remove things and make the Logging less useful. Logs would being something like this: ********* FSUIPC4, Version 4.949f by Pete Dowson ********* Prepar3D.exe version = .... Reading options from "E:\Prepar3D v3\Modules\FSUIPC4.ini" Running inside Prepar3D v3 on Windows 7 Module base=12EA0000 User Name=... User Addr=... FSUIPC4 Key is provided WideFS7 Key is provided Anyway, there's no sign of any SimConnect problems there at all, and as far as FSUIPC knew the menu entry added here: 149500 FSUIPC Menu entry added stayed there. If FSUIPC became disconnected from SimConnect so that the menu entry disappeared, it would perform a complete reconnection, which is what I assumed was happening regularly from your description. So, something else was going on. I can only suggest that you go though a process of elimination to see which add-on may be responsible -- assuming of course that it isn't a P3Dv3 bug. There do seem to be quite a few still, so it might be worth reporting on the L-M forum too. Pete
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