eziocin

John, thank you. I modified the FSUIPC.ini file to add the CONNECTED (Spad.next) and READY (Vpilot) on the RUN instructions, and to adjust the DetectToConnectDelayAuto as per the link you provided (the value now set for me is 86). Now everything is working well. Thanks a lot for your help Ezio

Hi John, as promised here I am with the FSUIPC and WideClient Log files. You will find attached three files: FSUIPC7@3Mar_Start1.log this is the log following the initial FSUIPC start with MSFS which in turn started also vPilot and Spad.next FSUIPC7@3Mar_Restart.log this is the log relevant to the manual restart of FSUIPC after I shut it down keeping MSFS2020 running (before I shut FSUIPC down Spad.next had shut down without any action on my side, and vPilot was still working) Wideclient.log this the log relevant to WideClient on the networked laptop. Note that I did not shut it down when I restarted FSUIPC, and upon the FSUIPC restart the connection was immediately found. I am running the 24H2 Win11 build but this issue had started before 24H2 was released and installed on my PC Thanks for your help Ciao Ezio WideClient.log FSUIPC7@3Mar_Start1.log FSUIPC7@3Mar_restart.log

Thanks John for the quick answer. Yes, your point is correct..it doesn't hang..it is waiting for a connection...I usually shut down Wideclient before restarting FSUIPC and then restart WideClient after I restart FSUIPC, but I will check if leaving it running it reconnects automatically. I will send you the log files as soon as I am back home.. that is Sunday late evening ... 🙂 have a nice week end Ezio

Hi, after many years of successful use of WideFs and FSUIPC, all of a sudden, in the last few weeks I am not able to connect Widefs unless I restart FSUIPC. This is what happens: I launch MSFS2020 and at some point FSUIPC also starts. Then once I have loaded the flight and the aircraft is at the departure gate, I run Widefs Client on the networked laptop, but it hangs with the message "Waiting for a connection". In order to establish the connection I need to shut down and restart FSUIPC (no need to restart MSFS as well) , and then I can connect Widefs without any issue. I don't know if this is part of the same problem, but I have Spad.next and vPilot launched automatically by FSUIPC, and although they both start and load correctly they shut down as soon as I load the flight. The only reason I am mentioning this is because this issue has come out concurrently with the WideFs issue...never had problems like these in many years of flawless use of FSUIPC, Spad and vPilot. Running MSFS on Win11, latest build, and FSUIPC latest version Any indication on how to solve this issue would be greatly appreciated. Thanks a lot in advance Ezio

Hi, is there a possibility to assign an action to a button while double clicking the button ? In particular I have the Elev Trim Up action assigned to a Joystick button (hold), and I would like to assign at that same button the Custom Camera 1 view, without having the view change everytime I use the elevator trim. So assigning the Custom Camera 1 view to that button, but triggered by a double click of the button, could be the solution. Or maybe there is another solution which I cannot see... Thanks Ezio

The command line is: DelayedMouseLookZoom=Yes and it is reported in General section of FSUIPC.ini Ezio

Hi, in the FSX/P3D versions of FSUIPC, there is an option in FSUIPC.ini to delay the action of zooming in the VC while scrolling the wheel. This is particularly useful to avoid unintentional zooming in when the mouse wheel is being used for rotating knobs. I have not seen this option in the .ini file of the MSFS version. Is there any chance to have this feature implemented ? Thanks Ezio

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

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

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

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

OMG..! How could I miss that....!! File path adjusted...now working perfectly.... Pete, apologise for the useless question.... Jumpmonkey, thanks for pointing it out....! Ezio

Flightsim is my user name, yes... vPilot user guide reccomends to install it in the default location and considering that it works flawlessly (apart from the topic subject) I am not keen to move it..in the end it is not a big issue but I found strange that I could not start it via FSUIPC as I have several other programs (Opus FSI, EFB, etc..) that I normally start via FSUIPC and I never had a problem with this FSIPC feature.. Ezio

Pete, thanks for your quick reply. AppData folder is the default install location of the program and I have checked and rechecked many times the correct definition of the path. The strange thing is that when I had Windows 7 it started as expected, with the same command in FSUIPC and the same location in AppData...now with Windows 10 (fresh install) I have this problem ... I suspect it might be something related to permissions...but it is a strange issue. Regards Ezio

Hi, I am trying to autostart vPilot client via FSUIPC and I have added the following line to FSUIPC.cfg: [Programs] Run1=KILL,C:\Users\FlightSim\AppData\Local\vPilot.exe However when I launch P3D (V3.4) vPilot will not start and I have the following warning in FSUIPC log: FSUIPC couldn't run: "C:\Users\FlightSim\AppData\Local\vPilot.exe" [Error=2] Both vPilot and P3D are set to run as administrators Any ideas ? Thanks Ezio