eziocin

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

Thanks Pete for your reply. I think I have solved the mistery: I have three profiles in the FSUIPC.ini, corresponding to Aerosoft Airbus, PMDG 777 and PMDG NGX. The buttons/key assignments are pretty much the same for the three profiles. I have FS2Crew installed on all the three aircraft. Now, for the T7 and NGX FS2crew I have the option to assign the FS2crew soft mute action to the CTRL key in the FS2crew config section (and I have not selected this option as I am soft muting FS2crew via the same PTT button I use to talk to online ATC), whilst for the Airbus this is the default option and cannot be changed. The 17=H1,0,K238,8 line is only present on the Airbus profile and not on the PMDG ones, so I believe this must be relevant to the action of soft muting Fs2crew microphone while holding the CTRL key. So I must assume that FS2crew can modify the FSUIPC.ini file in this way. Does it make sense ? I can't check what FSUIPC displays in the button assignment tab when pressing that button as that button has a total of three assignments and I don't know how to display the three of them (maybe I am missing something in the manual). Regards Ezio

Hi, today, while editing the Buttons section of Fsuipc.ini, to add two new assignments for a button on a particular profile, I noticed that such section contains all the assignment I had previousy made for this button on this profile plus an additional line that I thought I hadn't seen before: 17=H1,0,K238,8 So I looked for the key 238 in the manual to understand what is was referring to but I wasn't able to find a key corresponding to 238. Apologise in advance if I am missing something obvious and this is a very silly question, but can someone clarify which key is corresponding to 238 ? Thanks Regards Ezio

Thanks Pete.....excellent support as usual... Regards

Update. I noticed that in the P3D modules folder there was no FSUIPC Key file, so I just copied and pasted into that folder the same file included in the FSX Modules folder and now everything is ok. So it seems it is sorted out. Just one question: is there any problem in doing it that way, i.e.copying the key file from FSX to P3D ? Thanks

Pete, I have just performed a P3D v2.5 fresh install and I have installed FSUIPC 4.939j (this is side by side installation with FSX). I have entered the registration key both for FSUIPC and WideFS 7 and apparently the installation went fine. However, when I start P3D and enter the FSUIPC menu, it tells me that this is an unregistered copy. The thing which is confusing me is that the installer log shows a successful registration (on the parallel FSX install everything works fine: __________ Installer for FSUIPC4.DLL version 4.939j Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" ... >>> OK! FOUND FSX! <<< ... SetupPath=I:\Flight Simulator X\ Looking in registry for FSX-SE install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0 Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0 Parameter"AppPath" ... NOT found! ... Looking in registry for Prepar3D v1 install path: HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D Parameter"AppPath" ... NOT found! ... Looking in registry for Prepar3D v2 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2 Parameter"SetupPath" ... >>> OK! FOUND Prepar3D v2! <<< ... SetupPath=I:\Lockheed Martin\Prepar3D v2\ =========================================================== INSTALLATION FOR FSX: SetupPath="I:\Flight Simulator X\" Checking version of the FSX EXE: ... Version 10.0.61472.0 (Need at least 10.0.60905.0) Checking compatibility with installed SimConnect: Found SimConnect build 60905 (Original) Found SimConnect build 61242 (SP1 May07) Found SimConnect build 61259 (Acc/SP2 Oct07) Checking if there's already a version of FSUIPC4 installed in: I:\Flight Simulator X\Modules\FSUIPC4.DLL ... Version 4.939j found. FSX Modules folder already exists. Okay -- installed FSUIPC4 into "I:\Flight Simulator X\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\EZIO-P3D\AppData\Roaming" Now finding \Microsoft\FSX\FSX.CFG for all users, including this one Looking in "C:\Users\All Users\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Default\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Default User\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\EZIO-P3D\AppData\Roaming" Found FSX.CFG in "C:\Users\EZIO-P3D\AppData\Roaming\Microsoft\FSX\FSX.CFG" Now checking DLL.XML ... ... There is a previous DLL.XML, checking for FSUIPC4 section. ... FSUIPC4 section already exists but will be replaced. (for FSUIPC4, without Loader) ... FSUIPC4 section of DLL.XML written okay Now checking for a SimConnect.XML file ... ... There is a SimConnect.XML, checking for "local" section. ... "local" section already exists, file not modified. Looking in "C:\Users\Public\AppData\Roaming" ... No FSX.CFG there "Modules\FSUIPC Documents" folder already exists. Now installing additional files into the "Modules\FSUIPC Documents" folder: Installed "FSUIPC4 User Guide.pdf" okay Installed "FSUIPC4 for Advanced Users.pdf" okay Installed "FSUIPC4 History.pdf" okay Installed "List of FSX and P3D controls.pdf" okay Installed "FSUIPC Lua Library.pdf" okay Installed "FSUIPC Lua Plug-Ins.pdf" okay Installed "Lua License.pdf" okay Installed "Lua Plugins for VRInsight Devices.pdf" okay Installed "LuaFileSystem.pdf" okay Installed "Example LUA plugins.zip" okay Installed "ASN WX Radar facilities in FSUIPC4.pdf" okay Installed "Offset Mapping for PMDG 737NGX.pdf" okay Installed "FSUIPC4 Offsets Status.pdf" okay Installed "Profiles in Separate Files.pdf" okay =========================================================== INSTALLATION FOR Prepar3D v2: SetupPath="I:\Lockheed Martin\Prepar3D v2\" Checking version of the Prepar3D v2 EXE: ... Version 2.5.12942.0 (Need at least 1.0.677.0) Checking compatibility with installed SimConnect: Checking if there's already a version of FSUIPC4 installed in: I:\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL ... Version 4.939j found. Prepar3D v2 Modules folder already exists. Okay -- installed FSUIPC4 into "I:\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\EZIO-P3D\AppData\Roaming" Now finding \Lockheed Martin\Prepar3D v2\Prepar3D.CFG for all users, including this one Looking in "C:\Users\All Users\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Default\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Default User\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\EZIO-P3D\AppData\Roaming" Found Prepar3D.CFG in "C:\Users\EZIO-P3D\AppData\Roaming\Lockheed Martin\Prepar3D v2\Prepar3D.CFG" Now checking DLL.XML ... ... There is a previous DLL.XML, checking for FSUIPC4 section. ... FSUIPC4 section already exists but will be replaced. (for FSUIPC4, without Loader) ... FSUIPC4 section of DLL.XML written okay Now checking for a SimConnect.XML file ... ... No SimConnect.XML file found. This is okay. Looking in "C:\Users\Public\AppData\Roaming" ... No Prepar3D.CFG there "Modules\FSUIPC Documents" folder already exists. Now installing the Prepar3D SimConnect interface for FSUIPC4 into the "Modules" folder: Installed "SimConnectP3D2.dll" okay Now installing additional files into the "Modules\FSUIPC Documents" folder: Installed "FSUIPC4 User Guide.pdf" okay Installed "FSUIPC4 for Advanced Users.pdf" okay Installed "FSUIPC4 History.pdf" okay Installed "List of FSX and P3D controls.pdf" okay Installed "FSUIPC Lua Library.pdf" okay Installed "FSUIPC Lua Plug-Ins.pdf" okay Installed "Lua License.pdf" okay Installed "Lua Plugins for VRInsight Devices.pdf" okay Installed "LuaFileSystem.pdf" okay Installed "Example LUA plugins.zip" okay Installed "ASN WX Radar facilities in FSUIPC4.pdf" okay Installed "Offset Mapping for PMDG 737NGX.pdf" okay Installed "FSUIPC4 Offsets Status.pdf" okay Installed "Profiles in Separate Files.pdf" okay =========================================================== All installer tasks completed. Registration check for FSUIPC4 and WideFS was successful! (result code 00) *************** End of Install Log *************** Looking at the FSUIPC log in the P3D Modules folder it looks like it cannot read my user details: ********* FSUIPC4, Version 4.939j by Pete Dowson ********* Reading options from "I:\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.ini" Running inside Prepar3D v2 on Windows 7 Module base=5CB50000 User Name="" User Addr="" FSUIPC4 not user registered WIDEFS7 not user registered, or expired 0 System time = 03/04/2015 00:55:12 0 FLT path = "C:\Users\EZIO-P3D\Documents\Prepar3D v2 Files\" 0 Trying I:\Lockheed Martin\Prepar3D v2\Modules\SimConnectP3D2.dll 0 Found it: trying to connect 16 FS path = "I:\Lockheed Martin\Prepar3D v2\" 265 LogOptions=00000000 00000001 265 --- CONTROLS timer memory location obtained ok 265 --- SIM1 Frictions access gained 265 --- FS Controls Table located ok 265 --- Installed Mouse Macro hooks ok. 265 --- Wind smoothing fix is fully installed 265 SimConnect_Open succeeded: waiting to check version okay 265 Trying to use SimConnect Prepar3D 1560 Running in "Lockheed Martin® Prepar3D® v2", Version: 2.5.12942.0 (SimConnect: 2.5.0.0) 1560 Initialising SimConnect data requests now 1560 FSUIPC Menu entry added 1576 C:\Users\EZIO-P3D\AppData\Local\Lockheed Martin\Prepar3D v2\Prepar3D_Default.fxml 1576 I:\Lockheed Martin\Prepar3D v2\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air 19828 System time = 03/04/2015 00:55:32, Simulator time = 15:56:46 (19:56Z) 20826 Starting everything now ... 21856 ASN active function link set 21856 Ready for ASN WX radar 22152 Advanced Weather Interface Enabled 50716 System time = 03/04/2015 00:56:03, Simulator time = 15:57:02 (19:57Z) 50716 *** FSUIPC log file being closed Minimum frame rate was 76.8 fps, Maximum was 83.2 fps Minimum available memory recorded was 2359Mb Average frame rate for running time of 15 secs = 78.3 fps Memory managed: 11 Allocs, 11 Freed ********* FSUIPC Log file closed *********** I have repeated the installation a couple of times but nothing has changed. I would really appreciate some indication on how to proceed. Thanks in advance for your help Regards Ezio

Many thanks.....have a nice day... Regards

Pete, I guess I missed the point when I read your first post on the delay before zooming. Now I got it, and, yes, you are right "... the only likely time you'd move it unintentionally ... when you initially pressed it. If you don't continually move it, then the modification I have made will ignore the initial movement..." In this case I think it would really make the difference I am looking for....sorry for misunderstanding you and quickly jumping to the wrong conclusion. I would like to try this option. Thank you Bye

Pete, thank you for you replies....based on your statements above I will leave everything as is....I don't think that a delay before zooming starts would really make the difference. Thank you for your time anyway... Regards

OK, let me clarify better as I have not been accurate enough in my original post. Pete, you are right, I am talking about mouse look. I don't have Ezdok, as I use Opus for camera views but as far as I am aware of Opus hasn't got a mouse wheel zoom feature embedded. The only option I have enabled on mouse wheel is mouse look via FSUIPC. You are also right that it is not so simple to rotate the wheel when you depress it for VC panning. My problem is that in those rare occasions when I inadvertently rotate the mouse wheel while it is also depressed, the zoom level changes and there is no way to reset it at the original value (ok, the obyious way is to rotate the wheel in the opposite direction, but it is not accurate). So, my question could be put differently: is there a way to reset the zoom level to the original level once it has been changed via a mouse wheel rotation ? Thanks Regards

Is there a way to completely disable the zoom function associated with the mouse wheel ? It may seem a silly question, but I can't find it anywhere. I know many people find it useful but I find very annoying that when panning around in the cockpit using the mouse wheel depressed, it may eventually cause a zoomed view. Thanks Regards

Pete, just to let you know....after several unsuccessful trials I finally managed to make it work well again just selecting "run as administrator" in the Wideclient.exe compatibility window. I honestly don't know what is the rationale behind it, but it is simple as that: now PTT works well even if WideFs is not the active window. Do you have an explanation for this ? Thanks Bye

Yes, this is what I have... However, looking also at last paragraph of your reply it has just come to my mind that the day before the crash I had to reset the home network router for various reasons, so it might be worth having a look at the homegroup settings to see if they have been somehow affected by this reset. I'll see and report back...... Thanks for your answer anyway. Ciao

Peter, I am having a strange issue on WideFS and Teamspeak. I use a networked configuration when I fly online, with Ivap and Teamspeak installed on the client, and use WideFs to activate PTT on Teamspeak from a yoke button. Everything has been running quite flawlessly for more than two years, but yesterday I had a WideFs crash (first time ever since I use WideFS), and after that event what happens is that in order to have PTT working I need to have WideFs as the active window on the client PC. In the client I have other programs running, that are Ivap and ASN, and if one of them is the active window, PTT simply doesn't work....as soon as I click on the WideFs window then PTT comes back to life. I have been using WideFs as a "launch and forget" software for years and everything has alwasy been fine quite fine. I have tried to remove the entire WideFs folder and replace with the most updated version but nothing changed. Any idea what might have happened ? Thanks and have a good day... Ciao