eziocin Posted February 25, 2017 Report Share Posted February 25, 2017 Hello, I am having a strange issue on P3D that I never experienced before: a few minutes after launching the flight (it may be 2 minutes or 10-15 minutes) all the controllers stop working (I have the controllers disabled in P3D menu and I control all axes via FSUIPC on three controllers..Joke, Pedals and Throttle quadrant), and it is no longer possible to open FSUIPC from the addon drop down menu. A few information: 1) I am using P3D 3.4 (Hotfix3...fresh install), and FSUIPC 4.963. 2) it is NOT aircraft related, as it happens on different aircraft 3) I have also Chase Plane installed and when the issue occur also the mouse panning function and the camera switching via the CP onscreen menu stops working This is the FSUIPC Log after the last event: ********* FSUIPC4, Version 4.963 (23rd February 2017) by Pete Dowson ********* Windows 10 Home 64 Bit reported as Build 14393, Release ID: 1607 (OS 10.0) Prepar3D.exe version = 3.4.22.19868 Reading options from "C:\Prepar3D\Modules\FSUIPC4.ini" Running inside Prepar3D v3 on Windows 10 Module base=5A400000 User Name="xxxxx" User Addr="xxxxx" FSUIPC4 Key is provided WideFS7 Key is provided 0 System time = 26/02/2017 00:00:21 0 FLT UNC path = "\\LMPREPAR3D\Users\FlightSim\Documents\Prepar3D v3 Files\" 0 ------ Module Version Check ------ 0 acontain.dll: 3.4.22.19868 0 api.dll: 3.4.22.19868 0 controls.dll: 3.4.22.19868 0 fs-traffic.dll: 3.4.22.19868 0 G3D.dll: 3.4.22.19868 0 language.dll: 3.4.22.19868 0 sim1.dll: 3.4.22.19868 0 visualfx.dll: 3.4.22.19868 0 weather.dll: 3.4.22.19868 0 window.dll: 3.4.22.19868 0 ---------------------------------- 0 Trying C:\Prepar3D\Modules\SimConnectP3D3.dll 0 Found it: trying to connect 0 FS UNC path = "\\LMPREPAR3D\Prepar3D\" 266 ---------------------- Joystick Device Scan ----------------------- 266 Product= Saitek Pro Flight Rudder Pedals 266 Manufacturer= Saitek 266 Vendor=06A3, Product=0763 (Version 1.0) 266 Serial Number= 266 Product= Saitek Pro Flight Yoke 266 Manufacturer= Saitek 266 Vendor=06A3, Product=0BAC (Version 3.3) 266 Serial Number= 266 Product= T.16000M 266 Manufacturer= Thrustmaster 266 Vendor=044F, Product=B10A (Version 5.0) 266 Serial Number= 266 ------------------------------------------------------------------- 282 Run: "C:\Users\FlightSim\AppData\Local\vPilot\vPilot.exe -host" 344 LogOptions=00000000 00000001 344 ------------------------------------------------------------------- 344 ------ Setting the hooks and direct calls into the simulator ------ 344 --- CONTROLS timer memory location obtained ok 344 --- SIM1 Frictions access gained 344 --- FS Controls Table located ok 344 --- Installed Mouse Macro hooks ok. 344 --- Wind smoothing fix is installed 344 --- SimConnect intercept for texts and menus option is off 344 --- All links okay (except older global weather setting method) 344 ------------------------------------------------------------------- 344 SimConnect_Open succeeded: waiting to check version okay 344 Trying to use SimConnect Prepar3D 344 Opened separate AI Traffic client okay 4828 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.4.22.19868 (SimConnect: 3.4.0.0) 4828 Initialising SimConnect data requests now 4828 FSUIPC Menu entry added 4860 \\LMPREPAR3D\Users\FlightSim\Documents\Prepar3D v3 Files\defaultCD.fxml 4860 \\LMPREPAR3D\Prepar3D\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air 45375 \\LMPREPAR3D\Prepar3D\SimObjects\Airplanes\FSLabs A320 IAE\A320.air 82953 User Aircraft ID 1 supplied, now being used 84032 System time = 26/02/2017 00:01:45, Simulator time = 12:28:47 (12:28Z) 84032 Aircraft="FSLabs A320-X British Airways (G-EUUE)" 90188 Weather Mode now = Theme 119407 Sim stopped: average frame rate for last 36 secs = 29.0 fps 119407 Max AI traffic was 0 aircraft 132875 Starting everything now ... 132891 ASN active function link set 132891 Ready for ASN WX radar 136047 Advanced Weather Interface Enabled 213782 Sim stopped: average frame rate for last 94 secs = 30.0 fps 213782 Max AI traffic was 0 aircraft 1402438 Sim stopped: average frame rate for last 1177 secs = 30.0 fps 1402438 Max AI traffic was 0 aircraft 1438797 === DLLStop called ... 1438797 === Closing external processes we started ... 1438797 About to KILL process "\Device\HarddiskVolume2\Users\FlightSim\AppData\Local\vPilot\vPilot.exe" 1439797 === About to kill any Lua plug-ins still running ... 1439953 === Closing global Lua thread 1440953 === About to kill my timers ... 1441157 === Restoring window procs ... 1441157 === Unloading libraries ... 1441157 === stopping other threads ... 1441157 === ... Button scanning ... 1441250 === ... Axis scanning ... 1441360 === Releasing joystick devices ... 1441360 === Freeing macro memory 1441360 === Removing any offset overrides 1441360 === Closing all WideFS threads 1450282 === Clearing any displays left 1450282 === Calling SimConnect_Close ... 1450891 === SimConnect_Close done! 1450891 === AI slots deleted! 1450891 === Freeing button memory ... 1450891 === Closing my Windows ... 1450891 === Freeing FS libraries ... 1451891 === Closing devices ... 1451891 === Closing the Log ... Bye Bye! ... 1451891 System time = 26/02/2017 00:24:33, Simulator time = 12:49:58 (12:49Z) 1451891 *** FSUIPC log file being closed Minimum frame rate was 24.9 fps, Maximum was 37.0 fps Minimum available memory recorded was 1180Mb Average frame rate for running time of 1307 secs = 30.0 fps Maximum AI traffic for session was 0 aircraft Memory managed: 332 Allocs, 331 Freed ********* FSUIPC Log file closed *********** Any suggestion ? Thanks Ezio Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 26, 2017 Report Share Posted February 26, 2017 32 minutes ago, hookipa said: I am having a strange issue on P3D that I never experienced before: a few minutes after launching the flight (it may be 2 minutes or 10-15 minutes) all the controllers stop working (I have the controllers disabled in P3D menu and I control all axes via FSUIPC on three controllers..Joke, Pedals and Throttle quadrant), and it is no longer possible to open FSUIPC from the addon drop down menu. Does the AddOn menu contain any other entries? 32 minutes ago, hookipa said: This is the FSUIPC Log after the last event: That shows a perfectly good session with FSUIPC normally closing after a session lasting about 24 minutes, Why do you suspect it as an FSUIPC issue? That doesn't make sense. I do see you are running vPilot. Someone else here has also reported a problem when using that. It doesn't use FSUIPC as far as I know, but folks always choose FSUIPC as the potential culprit initially. Try without vPilot. If it is all then okay I suggest you visit their support forum and see what they say. Pete Link to comment Share on other sites More sharing options...
eziocin Posted February 26, 2017 Author Report Share Posted February 26, 2017 29 minutes ago, Pete Dowson said: Does the AddOn menu contain any other entries? That shows a perfectly good session with FSUIPC normally closing after a session lasting about 24 minutes, Why do you suspect it as an FSUIPC issue? That doesn't make sense. I do see you are running vPilot. Someone else here has also reported a problem when using that. It doesn't use FSUIPC as far as I know, but folks always choose FSUIPC as the potential culprit initially. Try without vPilot. If it is all then okay I suggest you visit their support forum and see what they say. Pete Pete, thanks for your quick reply. I am not pointing fingers at FSUIPC, but the fact is that FSUIPC is the only entry in the Addon Menu that cannot be opened when this issue occurs...all the other entries are ok....and, all the controllers are managed by FSUIPC, and one moment they are all working perfectly and I can open FSUIPC in the addon menu, one moment later all controllers stop working and I can no longer open FSUIPC..... ...and ..yes, I have tried also without vPilot and the problem is still there... I am quite puzzled and I haven't got a clue of what's happening.. regards Ezio Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 26, 2017 Report Share Posted February 26, 2017 7 hours ago, hookipa said: but the fact is that FSUIPC is the only entry in the Addon Menu that cannot be opened when this issue occurs. This used to happen to FSUIPC with another addon too,. It seems to do something in SimConnect which allows FSUIPC to requests "DialogMode" (as it needs to to display the options dialog), but then SimConnect never enters that mode. It think that was a version of "copilot.dll", which was eventually fixed. There was one time when certain video drivers were messing it up too, but I've not heard of that happening for a long time. However, just in case try in both full screen and Windowed mode. The fact you've eliminated vPilot as a culprit is a useful start, but please list all of your SimConnect using add-ons. I think it will be a process of elimination to determine the culprit. So, are there other DLLs and EXEs being loaded or running on the same PC and using SimConnect? Pete Link to comment Share on other sites More sharing options...
eziocin Posted February 27, 2017 Author Report Share Posted February 27, 2017 Pete, just to let you know the problem was caused by ChasePlane. I selectively excluded one by one all the addons, and the problem remained until I removed CP. However, upon reinstall of CP the problem reappeared. What I did was to remove again CP, delete the file Cameras.cfg, restarted P3D to rebuild it before reinstalling CP. Then I reinstalled CP and everything came back normal (so far). Thanks anyway for your quick (as usual) replies. Ciao Ezio Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 27, 2017 Report Share Posted February 27, 2017 1 hour ago, hookipa said: just to let you know the problem was caused by ChasePlane. I selectively excluded one by one all the addons, and the problem remained until I removed CP. However, upon reinstall of CP the problem reappeared. What I did was to remove again CP, delete the file Cameras.cfg, restarted P3D to rebuild it before reinstalling CP. Then I reinstalled CP and everything came back normal (so far). Interesting. I don't know ChasePlane. I wonder how it manages to defeat a simply SimConnect menu mechanism? Anyway, glad you solved it! Pete Link to comment Share on other sites More sharing options...
eziocin Posted February 27, 2017 Author Report Share Posted February 27, 2017 Well, I was probably too optimistic...the problem reappeared (and it is still there) and using Appcrashview I have found that everyime I have this issue I also have a Couatl.exe crash (Couatl.exe is the file introduced by the FSDT addons).... I don't know if this is the cause or the effect...... The crazy thing is that if I remove the FSDT products (and Couatl.exe) but ChasePlane is installed I have the problem..while if I keep Couatl installed and remove Chase Plane the problem disappears...a compatibility issue of some sort maybe ? Anyway I wanted to let you know that it is not FSUIPC fault...:-) Ciao Ezio Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 27, 2017 Report Share Posted February 27, 2017 38 minutes ago, hookipa said: I have found that everyime I have this issue I also have a Couatl.exe crash (Couatl.exe is the file introduced by the FSDT addons). Ah, it'll be COUATL. I use GSX and find I get problems with COUATL or BGLMANX regularly. The secret is always to download the latest AddOn Manager for the Virtuali / DreamTeam site and run that. It will make sure all those bits, and SODE too (another problem one) are correct and up to date. I've never quite got the same problem as you, mind, but doing this has always solved things for me. Pete 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