Thomas Richter

Hi Trev, that are errors in MSFA/Asobo flight models/ avionics. Some AC sending constant those or other controls. Not related or controlled by FSUIPC. Btw- P3Dv5 has in some AC the same error. Thomas

Hi, if it starts it will create a FSUIPC7.ini file and a FSUIPC7.log file, both located in the folder where you run FSUIPC7. Copy and paste those files or its content to your message. Thomas

Hi, as the manual clearly describes the both commands are only used when FSUIPC starts and at what state they will start the containing Lua files. To Run / Stop Lua files you use the respective Lua controls. Please check the FSUIPC Lua Plug-Ins.pdf and FSUIPC Lua Library.pdf from one of the other FSUIPC installation Documents, FSUIPC4 / 5/ 6. Thomas

Hi, it might be that when you installed FSUIPC6 for P3Dv5 that you selected install for both, P3Dv4 and P3Dv5. But good you are sorted. Thomas

Hi, you can but most likely there is nothing that can be done as long the SDK doesn't support those functions. We report those things we find and are not related to FSUIPC direct to MSFS/ Asobo support. Thomas

👍👍

Hi, Toggle Pushback control will only toggle Pushback ON or OFF, the value has no effect. To send Left(1), Right (2), Straight(0) or OFF(3) you need to send the value to the Offset 31F4. Instead of selecting Toggle Pushback you choose Offset Dword Set, see pic. This would need 4 buttons or you use instead for Straight and Off the Toggle Pushback control but that would then switch from Left or Right to OFF and needs another press. Thomas

Hi, make sure you have an actual folder created and not starting FSUIPC7 direct in the ZIP file. Thomas

Hi, I requested, as we always ask for, the content of your FSUIPC6.ini file unaltered (the complete file/ content). Flaps UP / 1 /2 / 5 / 10 / 15 / 25 / 30 / 40 = 9 detents. -16384 to 16384 = 38768, 38768 / 9=4096. FSUIPC knows the number of detents from the current AC and the spaces are always even in-between. As you didn't calibrate the flaps lever nor set detents it depends on your controller and PMDJ only. PMDJ might interpret the lever position different. Here you can define the positions and detent spaces Thomas

Hi, this is neither a famous message nor a dummy message. It is an info that it seems there is a second installation of FSUIPC that starts. As you say AFVACARS wanted to update FSUIPC it is more likely that it did a second installation of just the DLL in some entry instead of using the FSUIPC installer. As it is possible to have more than one copy of FSUIPC running, you would see two menu entries in P3D, do you? Also on FSUIPC Logging tab on the center bottom you can press Open Folder to open the FSUIPC installation folder. Thomas

Hi, those controllers are vJoy - Virtual Joystick, not physical devices. Maybe multiple installations have been done by mistake? Thomas

Hi, since FSUIPC5 this option doesn't exist anymore as it was a problem with older FS versions and I think as well with P3Dv1-v3. Thomas

Hi, why posting this in two different threads, that is confusing for no reason ?? As I said already, you might first fix the controller problem in your registry. 109 System time = 20/09/2020 17:22:28 109 FLT path = "C:\Users\janos\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\" 188 ------------------------------------------------------------------- 203 Registered HotKey 'InvokeFSUIPCOptionsKey' (key=0x46, modifier=0x1) 297 FS path = "C:\Users\janos\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\" 313 ---------------------- Joystick Device Scan ----------------------- 313 Product= vJoy - Virtual Joystick 313 Manufacturer= Shaul Eizikovich 313 Serial Number= 2.1.9 313 Vendor=1234, Product=BEAD (Version 2.25) 328 GUIDs returned for product: VID_1234&PID_BEAD: 328 GUID= {675FFD60-DD8E-11EA-8004-444553540000} 328 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767 328 GUID= {67604B80-DD8E-11EA-800A-444553540000} 328 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767 328 GUID= {67602470-DD8E-11EA-8006-444553540000} 328 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767 328 GUID= {67602470-DD8E-11EA-8008-444553540000} 328 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767 328 GUID= {67607290-DD8E-11EA-800C-444553540000} 328 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767 328 GUID= {675FD650-DD8E-11EA-8002-444553540000} 328 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767 328 Product= vJoy - Virtual Joystick 328 Manufacturer= Shaul Eizikovich 328 Serial Number= 2.1.9 328 Vendor=1234, Product=BEAD (Version 2.25) 328 Product= vJoy - Virtual Joystick 328 Manufacturer= Shaul Eizikovich 328 Serial Number= 2.1.9 328 Vendor=1234, Product=BEAD (Version 2.25) 328 Product= VirtualFly - RUDDO+ 328 Manufacturer= 328 Vendor=16D0, Product=0DA3 (Version 0.2) 328 GUIDs returned for product: VID_16D0&PID_0DA3: 328 GUID= {225074A0-E19B-11EA-8001-444553540000} 328 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U4096,V4096,X4096,Y0,Z0 328 Product= VirtualFly - YOKO+ 328 Manufacturer= 328 Vendor=16D0, Product=0DA0 (Version 0.2) 328 GUIDs returned for product: VID_16D0&PID_0DA0: 328 GUID= {25CD3F50-E19B-11EA-8002-444553540000} 328 Details: Btns=7, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X4096,Y4096,Z0 328 Product= vJoy - Virtual Joystick 328 Manufacturer= Shaul Eizikovich 328 Serial Number= 2.1.9 328 Vendor=1234, Product=BEAD (Version 2.25) 328 Product= vJoy - Virtual Joystick 328 Manufacturer= Shaul Eizikovich 328 Serial Number= 2.1.9 328 Vendor=1234, Product=BEAD (Version 2.25) 328 Product= vJoy - Virtual Joystick 328 Manufacturer= Shaul Eizikovich 328 Serial Number= 2.1.9 328 Vendor=1234, Product=BEAD (Version 2.25) . . . 344 ------------------------------------------------------------------- 344 WARNING: Joystick ID 6 is duplicated in Registry 359 WARNING: Joystick ID 7 is duplicated in Registry 375 WARNING: Joystick ID 8 is duplicated in Registry 484 WARNING: Joystick ID 10 is duplicated in Registry 484 WARNING: Joystick ID 11 is duplicated in Registry 500 Device acquired for use: 500 Joystick ID = 3 (Registry okay) 500 3=vJoy Device 500 3.GUID={675FFD60-DD8E-11EA-8004-444553540000} 500 Device acquired for use: 500 Joystick ID = 4 (Registry okay) 500 4=vJoy Device 500 4.GUID={67604B80-DD8E-11EA-800A-444553540000} 500 Device acquired for use: 500 Joystick ID = 5 (Registry okay) 500 5=vJoy Device 500 5.GUID={67602470-DD8E-11EA-8006-444553540000} 500 Device acquired for use: 500 Joystick ID = 6 (Registry okay) 500 6=vJoy Device 500 6.GUID={67602470-DD8E-11EA-8008-444553540000} 500 Device acquired for use: 500 Joystick ID = 7 (Registry okay) 500 7=vJoy Device 500 7.GUID={67607290-DD8E-11EA-800C-444553540000} 500 Device acquired for use: 500 Joystick ID = 8 (Registry okay) 500 8=vJoy Device 500 8.GUID={675FD650-DD8E-11EA-8002-444553540000} 500 Device acquired for use: 500 Joystick ID = 2 (Registry okay) 500 2=VirtualFly - RUDDO+ 500 2.GUID={225074A0-E19B-11EA-8001-444553540000} 500 Device acquired for use: 500 Joystick ID = 10 (Registry okay) 500 10=VirtualFly - YOKO+ 500 10.GUID={25CD3F50-E19B-11EA-8002-444553540000} 500 Device acquired for use: 500 Joystick ID = 11 (Registry okay) 500 11=VirtualFly - TQ6+ 500 11.GUID={F2A26C20-E19C-11EA-8003-444553540000} Thomas

Hi, why posting this in two different threads, that is confusing for no reason ?? you might first fix the controller problem in your registry. 109 System time = 20/09/2020 17:22:28 109 FLT path = "C:\Users\janos\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\" 188 ------------------------------------------------------------------- 203 Registered HotKey 'InvokeFSUIPCOptionsKey' (key=0x46, modifier=0x1) 297 FS path = "C:\Users\janos\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\" 313 ---------------------- Joystick Device Scan ----------------------- 313 Product= vJoy - Virtual Joystick 313 Manufacturer= Shaul Eizikovich 313 Serial Number= 2.1.9 313 Vendor=1234, Product=BEAD (Version 2.25) 328 GUIDs returned for product: VID_1234&PID_BEAD: 328 GUID= {675FFD60-DD8E-11EA-8004-444553540000} 328 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767 328 GUID= {67604B80-DD8E-11EA-800A-444553540000} 328 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767 328 GUID= {67602470-DD8E-11EA-8006-444553540000} 328 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767 328 GUID= {67602470-DD8E-11EA-8008-444553540000} 328 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767 328 GUID= {67607290-DD8E-11EA-800C-444553540000} 328 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767 328 GUID= {675FD650-DD8E-11EA-8002-444553540000} 328 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767 328 Product= vJoy - Virtual Joystick 328 Manufacturer= Shaul Eizikovich 328 Serial Number= 2.1.9 328 Vendor=1234, Product=BEAD (Version 2.25) 328 Product= vJoy - Virtual Joystick 328 Manufacturer= Shaul Eizikovich 328 Serial Number= 2.1.9 328 Vendor=1234, Product=BEAD (Version 2.25) 328 Product= VirtualFly - RUDDO+ 328 Manufacturer= 328 Vendor=16D0, Product=0DA3 (Version 0.2) 328 GUIDs returned for product: VID_16D0&PID_0DA3: 328 GUID= {225074A0-E19B-11EA-8001-444553540000} 328 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U4096,V4096,X4096,Y0,Z0 328 Product= VirtualFly - YOKO+ 328 Manufacturer= 328 Vendor=16D0, Product=0DA0 (Version 0.2) 328 GUIDs returned for product: VID_16D0&PID_0DA0: 328 GUID= {25CD3F50-E19B-11EA-8002-444553540000} 328 Details: Btns=7, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X4096,Y4096,Z0 328 Product= vJoy - Virtual Joystick 328 Manufacturer= Shaul Eizikovich 328 Serial Number= 2.1.9 328 Vendor=1234, Product=BEAD (Version 2.25) 328 Product= vJoy - Virtual Joystick 328 Manufacturer= Shaul Eizikovich 328 Serial Number= 2.1.9 328 Vendor=1234, Product=BEAD (Version 2.25) 328 Product= vJoy - Virtual Joystick 328 Manufacturer= Shaul Eizikovich 328 Serial Number= 2.1.9 328 Vendor=1234, Product=BEAD (Version 2.25) . . . 344 ------------------------------------------------------------------- 344 WARNING: Joystick ID 6 is duplicated in Registry 359 WARNING: Joystick ID 7 is duplicated in Registry 375 WARNING: Joystick ID 8 is duplicated in Registry 484 WARNING: Joystick ID 10 is duplicated in Registry 484 WARNING: Joystick ID 11 is duplicated in Registry 500 Device acquired for use: 500 Joystick ID = 3 (Registry okay) 500 3=vJoy Device 500 3.GUID={675FFD60-DD8E-11EA-8004-444553540000} 500 Device acquired for use: 500 Joystick ID = 4 (Registry okay) 500 4=vJoy Device 500 4.GUID={67604B80-DD8E-11EA-800A-444553540000} 500 Device acquired for use: 500 Joystick ID = 5 (Registry okay) 500 5=vJoy Device 500 5.GUID={67602470-DD8E-11EA-8006-444553540000} 500 Device acquired for use: 500 Joystick ID = 6 (Registry okay) 500 6=vJoy Device 500 6.GUID={67602470-DD8E-11EA-8008-444553540000} 500 Device acquired for use: 500 Joystick ID = 7 (Registry okay) 500 7=vJoy Device 500 7.GUID={67607290-DD8E-11EA-800C-444553540000} 500 Device acquired for use: 500 Joystick ID = 8 (Registry okay) 500 8=vJoy Device 500 8.GUID={675FD650-DD8E-11EA-8002-444553540000} 500 Device acquired for use: 500 Joystick ID = 2 (Registry okay) 500 2=VirtualFly - RUDDO+ 500 2.GUID={225074A0-E19B-11EA-8001-444553540000} 500 Device acquired for use: 500 Joystick ID = 10 (Registry okay) 500 10=VirtualFly - YOKO+ 500 10.GUID={25CD3F50-E19B-11EA-8002-444553540000} 500 Device acquired for use: 500 Joystick ID = 11 (Registry okay) 500 11=VirtualFly - TQ6+ 500 11.GUID={F2A26C20-E19C-11EA-8003-444553540000} Thomas

Hi, when you already calibrate in FSUIPC you define the space in-between the detents. Maybe you attach or copy and paste the content of your FSUIPC6.ini file unaltered to your message. Thomas

Hi, when you start FSUIPC first and then MSFS and the axes don't work, close FSUIPC and copy the FSUIPC7.log file before you restart to see what's in the file please. Please also update to latest FSUIPC7. Thomas

Hi, Btw- did you check with FSUIPC logging IPC read/write? As PMDG doesn't use FSUIPC itself the logging doesn't get hammered. It might give an idea what read requests are there. Thomas

Hi, check those are set to Auto or Yes, at least for the PMDG model you use. Those are in FSUIPC INI file within the [General] section. Thomas

Hi, MSFS doesn't have that option to "Disable" controllers. Any function, axes and/ or buttons, that is defined in MSFS and you want to define via FSUIPC needs to be removed manually in MSFS. Hopefully they will add the option sometime. Thomas

Hi, MSFS would have to start FSUIPC7 but there is no facility, yet. Toggle Avionics Master doesn't work, Asobo needs to fix those things, long list, in SimConnect. But have a look here to fix your problem by using Avionics Master Set. Thomas

Hi, please check with this version (16th), a link is in the post included. Thomas

Hi, that question should go to Asobo/MS as it is a problem in MSFS, the text function is not proper implemented and supported. Hopefully one of the coming updates will have changes to SimConnect. Thomas

Hi, this will answer your question. Best to post in questions in relation to FSUIPC and supported programs by Pete or John Dowson in the sub-forum "FSUIPC7-Beta for MSFS" Thomas

Hi, WideFS is build into FSUIPC and FSUIPC7, I guess you mean WideClient? Make sure you use latest WideClient version. When setting up a new problem most likely your problems are related to your network settings. When downloading WideClient ZIP file it contains WideFS User Guide.pdf file that very well describes the important settings for the network. Please check and follow that manual. Latest WideClient 7.157, WideClient 7.157 Thomas

Hi, those controls are all listed in FSUIPC selection, make sure you use latest FSUIPC7 Thomas