Kalnon Posted December 30, 2021 Report Share Posted December 30, 2021 Hello, I have the Honeycomb Alpha flight yoke and it used to work fine but recently since I had to do a complete reinstallation of FSX:SE, it no longer sees it. I need FSUIPC to properly calibrate the axis for the ailerons. I really would appreciate any help, thank you. Link to comment Share on other sites More sharing options...
John Dowson Posted December 30, 2021 Report Share Posted December 30, 2021 Can you please show me your FSUIPC .ini and .log files. Link to comment Share on other sites More sharing options...
John Dowson Posted December 30, 2021 Report Share Posted December 30, 2021 Btw, Is FSUIPC4 installed and running ok? If not, I also need to see your installation log. Link to comment Share on other sites More sharing options...
Kalnon Posted December 30, 2021 Author Report Share Posted December 30, 2021 Where can I find those files? Link to comment Share on other sites More sharing options...
Kalnon Posted December 31, 2021 Author Report Share Posted December 31, 2021 To answer your other question, It does seem to be running fine now that I found the registration. My HOTAS it sees fine but not my yoke. My yoke seems to work fine in MSFS so I don't think it is the issue. One thing I did try is unplugging and plugging back in the yoke while I had FSX running and FSUIPC did seem to recognize it for a moment but then stopped again. If you could please point me to where I can find those log files I will provide them for you. Link to comment Share on other sites More sharing options...
John Dowson Posted December 31, 2021 Report Share Posted December 31, 2021 15 hours ago, Kalnon said: Where can I find those files? They are in your FSUIPC installation folder. For FSX, that will be under a folder called Modules, in your FSX-SE folder. Link to comment Share on other sites More sharing options...
John Dowson Posted December 31, 2021 Report Share Posted December 31, 2021 4 hours ago, Kalnon said: FSUIPC did seem to recognize it for a moment but then stopped again. Check that you have power management disabled on your USB hubs. Link to comment Share on other sites More sharing options...
Kalnon Posted December 31, 2021 Author Report Share Posted December 31, 2021 ********* FSUIPC4, Version 4.976 (15th January 2021) by Pete Dowson ********* Windows 10 Enterprise 64 Bit reported as Build 19042, Release ID: 2009 (OS 10.0) fsx.exe version = 10.0.62615.0 Reading options from "H:\SteamLibrary\steamapps\common\FSX\Modules\FSUIPC4.ini" Running inside FSX Steam Edition on Windows 10 Module base=20BD0000 User Name="Christopher Matke" User Addr="kalnon@protonmail.com" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired 0 System time = 30/12/2021 11:41:26 0 FLT path = "C:\Users\Admin\Documents\Flight Simulator X - Steam Edition Files\" 16 ------ Module Version Check ------ 16 acontain.dll: 10.0.62615.0 16 api.dll: 10.0.62615.0 16 controls.dll: 10.0.62615.0 16 fs-traffic.dll: 10.0.62615.0 16 G3D.dll: 10.0.62615.0 16 language.dll: 10.0.62615.0 16 sim1.dll: 10.0.62615.0 16 visualfx.dll: 10.0.62615.0 16 weather.dll: 10.0.62615.0 32 window.dll: 10.0.62615.0 32 ---------------------------------- 32 Trying to connect to SimConnect 10.0.62615.0 ... 32 ... Okay! Connected! 47 FS path = "H:\SteamLibrary\steamapps\common\FSX\" 110 ---------------------- Joystick Device Scan ----------------------- 110 Product= TWCS Throttle 110 Manufacturer= Thrustmaster 110 Vendor=044F, Product=B687 (Version 1.16) 110 GUIDs returned for product: VID_044F&PID_B687: 110 GUID= {8CB18220-FFE1-11EB-8002-444553540000} 110 Details: Btns=14, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U1023,V1023,X1023,Y1023,Z65535 110 Product= T.16000M 110 Manufacturer= Thrustmaster 110 Vendor=044F, Product=B10A (Version 5.0) 125 Product= Saitek Pro Flight Rudder Pedals 125 Manufacturer= Saitek 125 Vendor=06A3, Product=0763 (Version 1.1) 125 GUIDs returned for product: VID_06A3&PID_0763: 125 GUID= {26FB3E20-995D-11EB-8001-444553540000} 125 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0 141 Product= Alpha Flight Controls 141 Manufacturer= Honeycomb Aeronautical 157 Serial Number= E6012E031B163B00 157 Vendor=294B, Product=1900 (Version 3.0) 157 GUIDs returned for product: VID_294B&PID_1900: 157 GUID= {83FCF960-9AE3-11EB-8001-444553540000} 157 Details: Btns=35, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X1023,Y1023,Z0 157 Product= FANATEC CSL Elite Pedals LC 172 Manufacturer= FANATEC 172 Vendor=0EB7, Product=6204 (Version 0.1) 172 Product= Saitek Pro Flight Quadrant 188 Manufacturer= Saitek 188 Vendor=06A3, Product=0C2D (Version 2.2) 188 GUIDs returned for product: VID_06A3&PID_0C2D: 188 GUID= {72B7D780-A7A7-11EB-8001-444553540000} 188 Details: Btns=9, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255 188 ------------------------------------------------------------------- 204 Device acquired for use: 204 Joystick ID = 4 (Registry okay) 204 4=TWCS Throttle 204 4.GUID={8CB18220-FFE1-11EB-8002-444553540000} 204 Device acquired for use: 204 Joystick ID = 4 (Registry okay) 204 4=T.16000M Joystick 204 4.GUID={8CB18220-FFE1-11EB-8002-444553540000} 204 Device acquired for use: 204 Joystick ID = 1 (Registry okay) 204 1=Saitek Pro Flight Rudder Pedals 204 1.GUID={73DD7BD0-CD43-11EB-8001-444553540000} 204 Device acquired for use: 204 Joystick ID = 3 (Registry okay) 204 3=Alpha Flight Controls 204 3.GUID={26FB3E20-995D-11EB-8001-444553540000} 204 Device acquired for use: 204 Joystick ID = 2 (Registry okay) 204 2=FANATEC CSL Elite Pedals LC 204 2.GUID={35193120-FFE1-11EB-8001-444553540000} 204 Device acquired for use (as alternative possibility): 204 Joystick ID = 1 (Registry okay) 204 1=FANATEC CSL Elite Pedals LC 204 1.GUID={73DD7BD0-CD43-11EB-8001-444553540000} 204 Device acquired for use: 204 Joystick ID = 6 (Registry okay) 204 6=Saitek Pro Flight Quadrant 204 6.GUID={72B7D780-A7A7-11EB-8001-444553540000} 204 ------------------------------------------------------------------- 282 LogOptions=00000000 00000001 282 ------------------------------------------------------------------- 282 ------ Setting the hooks and direct calls into the simulator ------ 282 --- CONTROLS timer memory location obtained ok 282 --- SIM1 Frictions access gained 297 --- FS Controls Table located ok 297 --- Installed Mouse Macro hooks ok. 297 --- Wind smoothing fix is fully installed 297 --- SimConnect intercept for texts and menus option is off 297 --- All links checked okay 297 ------------------------------------------------------------------- 297 SimConnect_Open succeeded: waiting to check version okay 297 Opened separate AI Traffic client okay 1985 -------------------------------------------------------------------- 1985 ***** HID USB device reconnected: re-initialising FSUIPC connections 2000 ---------------------- Joystick Device Scan ----------------------- 2000 Product= TWCS Throttle 2000 Manufacturer= Thrustmaster 2000 Vendor=044F, Product=B687 (Version 1.16) 2000 GUIDs returned for product: VID_044F&PID_B687: 2000 GUID= {8CB18220-FFE1-11EB-8002-444553540000} 2000 Details: Btns=14, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U1023,V1023,X1023,Y1023,Z65535 2000 Product= T.16000M 2000 Manufacturer= Thrustmaster 2000 Vendor=044F, Product=B10A (Version 5.0) 2016 Product= Saitek Pro Flight Rudder Pedals 2016 Manufacturer= Saitek 2016 Vendor=06A3, Product=0763 (Version 1.1) 2016 GUIDs returned for product: VID_06A3&PID_0763: 2016 GUID= {26FB3E20-995D-11EB-8001-444553540000} 2016 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0 2032 Product= Alpha Flight Controls 2032 Manufacturer= Honeycomb Aeronautical 2047 Serial Number= E6012E031B163B00 2047 Vendor=294B, Product=1900 (Version 3.0) 2047 GUIDs returned for product: VID_294B&PID_1900: 2047 GUID= {83FCF960-9AE3-11EB-8001-444553540000} 2047 Details: Btns=35, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X1023,Y1023,Z0 2047 Product= FANATEC CSL Elite Pedals LC 2063 Manufacturer= FANATEC 2063 Vendor=0EB7, Product=6204 (Version 0.1) 2063 Product= Saitek Pro Flight Quadrant 2063 Manufacturer= Saitek 2063 Vendor=06A3, Product=0C2D (Version 2.2) 2063 GUIDs returned for product: VID_06A3&PID_0C2D: 2063 GUID= {72B7D780-A7A7-11EB-8001-444553540000} 2063 Details: Btns=9, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255 2063 ------------------------------------------------------------------- 2079 Device acquired for use: 2079 Joystick ID = 4 (Registry okay) 2079 4=TWCS Throttle 2079 4.GUID={8CB18220-FFE1-11EB-8002-444553540000} 2079 Device acquired for use: 2079 Joystick ID = 4 (Registry okay) 2079 4=T.16000M Joystick 2079 4.GUID={8CB18220-FFE1-11EB-8002-444553540000} 2079 Device acquired for use: 2079 Joystick ID = 1 (Registry okay) 2079 1=Saitek Pro Flight Rudder Pedals 2079 1.GUID={73DD7BD0-CD43-11EB-8001-444553540000} 2079 Device acquired for use: 2079 Joystick ID = 3 (Registry okay) 2094 3=Alpha Flight Controls 2094 3.GUID={26FB3E20-995D-11EB-8001-444553540000} 2094 Device acquired for use: 2094 Joystick ID = 2 (Registry okay) 2094 2=FANATEC CSL Elite Pedals LC 2094 2.GUID={35193120-FFE1-11EB-8001-444553540000} 2094 Device acquired for use (as alternative possibility): 2094 Joystick ID = 1 (Registry okay) 2094 1=FANATEC CSL Elite Pedals LC 2094 1.GUID={73DD7BD0-CD43-11EB-8001-444553540000} 2094 Device acquired for use: 2094 Joystick ID = 6 (Registry okay) 2094 6=Saitek Pro Flight Quadrant 2094 6.GUID={72B7D780-A7A7-11EB-8001-444553540000} 2094 ------------------------------------------------------------------- 2172 Running in "Microsoft Flight Simulator X", Version: 10.0.62615.0 (SimConnect: 10.0.62615.0) 2172 Initialising SimConnect data requests now 2172 FSUIPC Menu entry added 2219 H:\SteamLibrary\steamapps\common\FSX\flights\other\FLTSIM.FLT 2219 H:\SteamLibrary\steamapps\common\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.air 7110 Weather Mode now = Theme 26844 H:\SteamLibrary\steamapps\common\FSX\SimObjects\Airplanes\Carenado D18S\D18.air 46188 User Aircraft ID 1 supplied, now being used 46188 Aircraft loaded: running normally now ... 46313 System time = 30/12/2021 11:42:12, Simulator time = 14:41:33 (18:41Z) 46329 Aircraft="Carenado D18S C-GJMC" 117844 Starting everything now ... 121329 Advanced Weather Interface Enabled 144047 -------------------------------------------------------------------- 144047 ***** HID USB device reconnected: re-initialising FSUIPC connections 144047 HID: Vendor=294B, Product=1900 (Version 3.0) 144063 Manufacturer= Honeycomb Aeronautical 144063 Product= Alpha Flight Controls 144079 Serial Number= E6012E031B163B00 144079 ---------------------- Joystick Device Scan ----------------------- 144079 Product= TWCS Throttle 144094 Manufacturer= Thrustmaster 144094 Vendor=044F, Product=B687 (Version 1.16) 144094 GUIDs returned for product: VID_044F&PID_B687: 144094 GUID= {8CB18220-FFE1-11EB-8002-444553540000} 144094 Details: Btns=14, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U1023,V1023,X1023,Y1023,Z65535 144110 Product= T.16000M 144110 Manufacturer= Thrustmaster 144110 Vendor=044F, Product=B10A (Version 5.0) 144125 Product= Saitek Pro Flight Rudder Pedals 144125 Manufacturer= Saitek 144125 Vendor=06A3, Product=0763 (Version 1.1) 144125 GUIDs returned for product: VID_06A3&PID_0763: 144125 GUID= {26FB3E20-995D-11EB-8001-444553540000} 144125 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0 144141 Product= Alpha Flight Controls 144141 Manufacturer= Honeycomb Aeronautical 144157 Serial Number= E6012E031B163B00 144157 Vendor=294B, Product=1900 (Version 3.0) 144157 GUIDs returned for product: VID_294B&PID_1900: 144157 GUID= {83FCF960-9AE3-11EB-8001-444553540000} 144157 Details: Btns=35, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X1023,Y1023,Z0 144157 Product= FANATEC CSL Elite Pedals LC 144157 Manufacturer= FANATEC 144157 Vendor=0EB7, Product=6204 (Version 0.1) 144172 Product= Saitek Pro Flight Quadrant 144172 Manufacturer= Saitek 144172 Vendor=06A3, Product=0C2D (Version 2.2) 144172 GUIDs returned for product: VID_06A3&PID_0C2D: 144172 GUID= {72B7D780-A7A7-11EB-8001-444553540000} 144172 Details: Btns=9, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255 144172 ------------------------------------------------------------------- 144188 Device acquired for use: 144188 Joystick ID = 4 (Registry okay) 144188 4=TWCS Throttle 144188 4.GUID={8CB18220-FFE1-11EB-8002-444553540000} 144188 Device acquired for use: 144188 Joystick ID = 4 (Registry okay) 144188 4=T.16000M Joystick 144188 4.GUID={8CB18220-FFE1-11EB-8002-444553540000} 144204 Device acquired for use: 144204 Joystick ID = 1 (Registry okay) 144204 1=Saitek Pro Flight Rudder Pedals 144204 1.GUID={73DD7BD0-CD43-11EB-8001-444553540000} 144204 Device acquired for use: 144204 Joystick ID = 3 (Registry okay) 144204 3=Alpha Flight Controls 144204 3.GUID={26FB3E20-995D-11EB-8001-444553540000} 144204 Device acquired for use: 144204 Joystick ID = 2 (Registry okay) 144204 2=FANATEC CSL Elite Pedals LC 144204 2.GUID={35193120-FFE1-11EB-8001-444553540000} 144204 Device acquired for use (as alternative possibility): 144204 Joystick ID = 1 (Registry okay) 144204 1=FANATEC CSL Elite Pedals LC 144204 1.GUID={73DD7BD0-CD43-11EB-8001-444553540000} 144204 Device acquired for use: 144204 Joystick ID = 6 (Registry okay) 144204 6=Saitek Pro Flight Quadrant 144204 6.GUID={72B7D780-A7A7-11EB-8001-444553540000} 144204 ------------------------------------------------------------------- 160297 -------------------------------------------------------------------- 160297 ***** HID USB device reconnected: re-initialising FSUIPC connections 160297 HID: Vendor=294B, Product=1900 (Version 3.0) 160313 Manufacturer= Honeycomb Aeronautical 160313 Product= Alpha Flight Controls 160329 Serial Number= E6012E031B163B00 160329 ---------------------- Joystick Device Scan ----------------------- 160329 Product= TWCS Throttle 160329 Manufacturer= Thrustmaster 160329 Vendor=044F, Product=B687 (Version 1.16) 160329 GUIDs returned for product: VID_044F&PID_B687: 160329 GUID= {8CB18220-FFE1-11EB-8002-444553540000} 160329 Details: Btns=14, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U1023,V1023,X1023,Y1023,Z65535 160329 Product= T.16000M 160329 Manufacturer= Thrustmaster 160329 Vendor=044F, Product=B10A (Version 5.0) 160344 Product= Saitek Pro Flight Rudder Pedals 160344 Manufacturer= Saitek 160344 Vendor=06A3, Product=0763 (Version 1.1) 160344 GUIDs returned for product: VID_06A3&PID_0763: 160344 GUID= {26FB3E20-995D-11EB-8001-444553540000} 160344 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0 160360 Product= Alpha Flight Controls 160360 Manufacturer= Honeycomb Aeronautical 160375 Serial Number= E6012E031B163B00 160375 Vendor=294B, Product=1900 (Version 3.0) 160375 GUIDs returned for product: VID_294B&PID_1900: 160375 GUID= {83FCF960-9AE3-11EB-8001-444553540000} 160375 Details: Btns=35, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X1023,Y1023,Z0 160375 Product= FANATEC CSL Elite Pedals LC 160391 Manufacturer= FANATEC 160391 Vendor=0EB7, Product=6204 (Version 0.1) 160391 Product= Saitek Pro Flight Quadrant 160407 Manufacturer= Saitek 160407 Vendor=06A3, Product=0C2D (Version 2.2) 160407 GUIDs returned for product: VID_06A3&PID_0C2D: 160407 GUID= {72B7D780-A7A7-11EB-8001-444553540000} 160407 Details: Btns=9, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255 160407 ------------------------------------------------------------------- 160422 Device acquired for use: 160422 Joystick ID = 4 (Registry okay) 160422 4=TWCS Throttle 160422 4.GUID={8CB18220-FFE1-11EB-8002-444553540000} 160422 Device acquired for use: 160422 Joystick ID = 4 (Registry okay) 160422 4=T.16000M Joystick 160422 4.GUID={8CB18220-FFE1-11EB-8002-444553540000} 160422 Device acquired for use: 160422 Joystick ID = 1 (Registry okay) 160422 1=Saitek Pro Flight Rudder Pedals 160422 1.GUID={73DD7BD0-CD43-11EB-8001-444553540000} 160422 Device acquired for use: 160422 Joystick ID = 3 (Registry okay) 160422 3=Alpha Flight Controls 160422 3.GUID={26FB3E20-995D-11EB-8001-444553540000} 160422 Device acquired for use: 160422 Joystick ID = 2 (Registry okay) 160422 2=FANATEC CSL Elite Pedals LC 160422 2.GUID={35193120-FFE1-11EB-8001-444553540000} 160422 Device acquired for use (as alternative possibility): 160422 Joystick ID = 1 (Registry okay) 160422 1=FANATEC CSL Elite Pedals LC 160422 1.GUID={73DD7BD0-CD43-11EB-8001-444553540000} 160422 Device acquired for use: 160422 Joystick ID = 6 (Registry okay) 160422 6=Saitek Pro Flight Quadrant 160422 6.GUID={72B7D780-A7A7-11EB-8001-444553540000} 160422 ------------------------------------------------------------------- 174079 -------------------------------------------------------------------- 174079 ***** HID USB device reconnected: re-initialising FSUIPC connections 174079 HID: Vendor=294B, Product=1900 (Version 3.0) 174079 Manufacturer= Honeycomb Aeronautical 174094 Product= Alpha Flight Controls 174094 Serial Number= E6012E031B163B00 174110 ---------------------- Joystick Device Scan ----------------------- 174110 Product= TWCS Throttle 174110 Manufacturer= Thrustmaster 174110 Vendor=044F, Product=B687 (Version 1.16) 174110 GUIDs returned for product: VID_044F&PID_B687: 174110 GUID= {8CB18220-FFE1-11EB-8002-444553540000} 174110 Details: Btns=14, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U1023,V1023,X1023,Y1023,Z65535 174125 Product= T.16000M 174125 Manufacturer= Thrustmaster 174125 Vendor=044F, Product=B10A (Version 5.0) 174141 Product= Saitek Pro Flight Rudder Pedals 174141 Manufacturer= Saitek 174141 Vendor=06A3, Product=0763 (Version 1.1) 174141 GUIDs returned for product: VID_06A3&PID_0763: 174141 GUID= {26FB3E20-995D-11EB-8001-444553540000} 174141 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0 174157 Product= Alpha Flight Controls 174157 Manufacturer= Honeycomb Aeronautical 174172 Serial Number= E6012E031B163B00 174172 Vendor=294B, Product=1900 (Version 3.0) 174172 GUIDs returned for product: VID_294B&PID_1900: 174172 GUID= {83FCF960-9AE3-11EB-8001-444553540000} 174172 Details: Btns=35, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X1023,Y1023,Z0 174172 Product= FANATEC CSL Elite Pedals LC 174188 Manufacturer= FANATEC 174188 Vendor=0EB7, Product=6204 (Version 0.1) 174188 Product= Controller (XBOX 360 For Windows) 174188 Manufacturer= Saitek 174188 Vendor=06A3, Product=0C2D (Version 2.2) 174188 GUIDs returned for product: VID_06A3&PID_0C2D: 174188 GUID= {72B7D780-A7A7-11EB-8001-444553540000} 174188 Details: Btns=9, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255 174188 ------------------------------------------------------------------- 174204 Device acquired for use: 174204 Joystick ID = 4 (Registry okay) 174204 4=TWCS Throttle 174204 4.GUID={8CB18220-FFE1-11EB-8002-444553540000} 174204 Device acquired for use: 174204 Joystick ID = 4 (Registry okay) 174204 4=T.16000M Joystick 174204 4.GUID={8CB18220-FFE1-11EB-8002-444553540000} 174204 Device acquired for use: 174204 Joystick ID = 1 (Registry okay) 174204 1=Saitek Pro Flight Rudder Pedals 174204 1.GUID={73DD7BD0-CD43-11EB-8001-444553540000} 174219 Device acquired for use: 174219 Joystick ID = 3 (Registry okay) 174219 3=Alpha Flight Controls 174219 3.GUID={26FB3E20-995D-11EB-8001-444553540000} 174219 Device acquired for use: 174219 Joystick ID = 2 (Registry okay) 174219 2=FANATEC CSL Elite Pedals LC 174219 2.GUID={35193120-FFE1-11EB-8001-444553540000} 174219 Device acquired for use (as alternative possibility): 174219 Joystick ID = 1 (Registry okay) 174219 1=FANATEC CSL Elite Pedals LC 174219 1.GUID={73DD7BD0-CD43-11EB-8001-444553540000} 174219 Device acquired for use: 174219 Joystick ID = 6 (Registry okay) 174219 6=Saitek Pro Flight Quadrant 174219 6.GUID={72B7D780-A7A7-11EB-8001-444553540000} 174219 ------------------------------------------------------------------- 191375 -------------------------------------------------------------------- 191375 ***** HID USB device reconnected: re-initialising FSUIPC connections 191375 HID: Vendor=294B, Product=1900 (Version 3.0) 191391 Manufacturer= Honeycomb Aeronautical 191391 Product= Alpha Flight Controls 191407 Serial Number= E6012E031B163B00 191407 ---------------------- Joystick Device Scan ----------------------- 191407 Product= TWCS Throttle 191407 Manufacturer= Thrustmaster 191407 Vendor=044F, Product=B687 (Version 1.16) 191407 GUIDs returned for product: VID_044F&PID_B687: 191407 GUID= {8CB18220-FFE1-11EB-8002-444553540000} 191407 Details: Btns=14, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U1023,V1023,X1023,Y1023,Z65535 191407 Product= T.16000M 191407 Manufacturer= Thrustmaster 191407 Vendor=044F, Product=B10A (Version 5.0) 191422 Product= Saitek Pro Flight Rudder Pedals 191422 Manufacturer= Saitek 191422 Vendor=06A3, Product=0763 (Version 1.1) 191422 GUIDs returned for product: VID_06A3&PID_0763: 191422 GUID= {26FB3E20-995D-11EB-8001-444553540000} 191422 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0 191438 Product= Alpha Flight Controls 191438 Manufacturer= Honeycomb Aeronautical 191454 Serial Number= E6012E031B163B00 191454 Vendor=294B, Product=1900 (Version 3.0) 191454 GUIDs returned for product: VID_294B&PID_1900: 191454 GUID= {83FCF960-9AE3-11EB-8001-444553540000} 191454 Details: Btns=35, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X1023,Y1023,Z0 191454 Product= FANATEC CSL Elite Pedals LC 191469 Manufacturer= FANATEC 191469 Vendor=0EB7, Product=6204 (Version 0.1) 191469 Product= Saitek Pro Flight Quadrant 191485 Manufacturer= Saitek 191485 Vendor=06A3, Product=0C2D (Version 2.2) 191485 GUIDs returned for product: VID_06A3&PID_0C2D: 191485 GUID= {72B7D780-A7A7-11EB-8001-444553540000} 191485 Details: Btns=9, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255 191485 ------------------------------------------------------------------- 191485 Device acquired for use: 191485 Joystick ID = 4 (Registry okay) 191485 4=TWCS Throttle 191485 4.GUID={8CB18220-FFE1-11EB-8002-444553540000} 191500 Device acquired for use: 191500 Joystick ID = 4 (Registry okay) 191500 4=T.16000M Joystick 191500 4.GUID={8CB18220-FFE1-11EB-8002-444553540000} 191500 Device acquired for use: 191500 Joystick ID = 1 (Registry okay) 191500 1=Saitek Pro Flight Rudder Pedals 191500 1.GUID={73DD7BD0-CD43-11EB-8001-444553540000} 191500 Device acquired for use: 191500 Joystick ID = 3 (Registry okay) 191500 3=Alpha Flight Controls 191500 3.GUID={26FB3E20-995D-11EB-8001-444553540000} 191500 Device acquired for use: 191500 Joystick ID = 2 (Registry okay) 191500 2=FANATEC CSL Elite Pedals LC 191500 2.GUID={35193120-FFE1-11EB-8001-444553540000} 191500 Device acquired for use (as alternative possibility): 191500 Joystick ID = 1 (Registry okay) 191500 1=FANATEC CSL Elite Pedals LC 191500 1.GUID={73DD7BD0-CD43-11EB-8001-444553540000} 191500 Device acquired for use: 191500 Joystick ID = 6 (Registry okay) 191500 6=Saitek Pro Flight Quadrant 191500 6.GUID={72B7D780-A7A7-11EB-8001-444553540000} 191500 ------------------------------------------------------------------- 217204 === Closing session: waiting for DLLStop to be called ... 221891 === DLLStop called ... 221891 === Closing external processes we started ... 222891 === About to kill any Lua plug-ins still running ... 223047 === Closing global Lua thread 224047 === About to kill my timers ... 224235 === Restoring window procs ... 224235 === Unloading libraries ... 224235 === stopping other threads ... 224235 === ... Button scanning ... 224344 === ... Axis scanning ... 224438 === Releasing joystick devices ... 224438 === Freeing macro memory 224438 === Removing any offset overrides 224438 === Clearing any displays left 224438 === NOTE: not calling SimConnect_Close ... 224438 === AI slots deleted! 224438 === Freeing button memory ... 224438 === Closing my Windows ... 224438 === Freeing FS libraries ... 225454 === Closing devices ... 225454 === Closing the Log ... Bye Bye! ... 225454 System time = 30/12/2021 11:45:11, Simulator time = 14:42:09 (18:42Z) 225454 *** FSUIPC log file being closed Minimum frame rate was 10.7 fps, Maximum was 21.8 fps Minimum available memory recorded was 1734Mb Average frame rate for running time of 32 secs = 14.6 fps Maximum AI traffic for session was 40 aircraft Memory managed: 18 Allocs, 17 Freed ********* FSUIPC Log file closed *********** Link to comment Share on other sites More sharing options...
Kalnon Posted December 31, 2021 Author Report Share Posted December 31, 2021 [General] UpdatedByVersion=4976 History=GWIJIAF08NMPPUQJV91MR AxesWrongRange=No TCASid=Flight TCASrange=40,3 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No AxisIntercepts=No DontResetAxes=No ThreadAffinityMask=x0 LuaAffinityMask=x0 InitDelay=0 GetNearestAirports=Yes LogOptionProtect=Yes OOMcheck=Yes OOMcheckInterval=10 TimeForLuaClosing=2 WeatherReadFactor=2 WeatherRewriteSeconds=1 CustomWeatherModify=No SimConnectStallTime=1 LuaRerunDelay=66 Console=No ProvideAIdata=Yes ProvideAIairports=Yes InitDelayDevicesToo=No Annotate=Yes NewInterceptTextMenu=No UseSystemTime=No UseMidMouseBtn=Yes MouseWheelMove=No MouseWheelTrim=No MouseWheelTrimSpeed=1 JoystickTimeout=20 PollGFTQ6=Yes BlankDisplays=No FixControlAccel=No FixMachSpeedBug=No NewDeleteVehiclesForAES=No AutoScanDevices=Yes VisibilityOptions=No OneCloudLayer=No CloudTurbulence=No CloudIcing=No GenerateCirrus=No SuppressCloudTurbulence=No MaxIce=-4 MinIce=-4 UpperWindGusts=No SuppressWindTurbulence=No SuppressWindVariance=No WindTurbulence=No TurbulenceRate=1.0,5.0 TurbulenceDivisor=20,20,40,40 SuppressAllGusts=No MaxSurfaceWind=0 WindLimitLevel=200 WindDiscardLevel=400 WindAjustAltitude=No WindAjustAltitudeBy=2000 SmoothBySimTime=No WindSmoothing=No WindSmoothness=2 WindSmoothAirborneOnly=Yes PressureSmoothness=0 TemperatureSmoothness=0 DisconnTrimForAP=No ZeroElevForAPAlt=No ThrottleSyncAll=No WhiteMessages=No ShowPMcontrols=No SpoilerIncrement=512 MagicBattery=No RudderSpikeRemoval=No ElevatorSpikeRemoval=No AileronSpikeRemoval=No ReversedElevatorTrim=No ClockSync=No ClockSyncMins=5 ClearWeatherDynamics=No OwnWeatherChanges=No TimeForSelect=4 LoadFlightMenu=No LoadPlanMenu=No PauseAfterCrash=No BrakeReleaseThreshold=75 SaveDataWithFlights=No ZapSound=firework ShortAircraftNameOk=Substring UseProfiles=Yes EnableMouseLook=No DelayedMouseLookZoom=No WideLuaGlobals=Yes FSVersionUsed="Microsoft Flight Simulator X",10.0.62615.0 SimConnectUsed=10.0.62615.0 [WideServer] WideFSenabled=Yes [Traffic Limiter] AirportPreference=50 PlannedAirportsPreference=50 GroundPreference=50 NearerPreference=50 TargetFrameRate=0 TrafficLimit=0 [JoyNames] AutoAssignLetters=No 1=FANATEC CSL Elite Pedals LC 1.GUID={73DD7BD0-CD43-11EB-8001-444553540000} 2=FANATEC CSL Elite Pedals LC 2.GUID={35193120-FFE1-11EB-8001-444553540000} 4=T.16000M Joystick 4.GUID={8CB18220-FFE1-11EB-8002-444553540000} 6=Saitek Pro Flight Quadrant 6.GUID={72B7D780-A7A7-11EB-8001-444553540000} 3=Alpha Flight Controls 3.GUID={26FB3E20-995D-11EB-8001-444553540000} [Axes] PollInterval=10 RangeRepeatRate=10 [Buttons] PollInterval=25 ButtonRepeat=20,10 [AutoSave] Next=1 Interval=60 Files=10 SaveOnGround=No AutoSaveEnabled=No [GPSout] GPSoutEnabled=No [GPSout2] GPSoutEnabled=No [Sounds] Path=H:\SteamLibrary\steamapps\common\FSX\Sound\ Device1=Primary Sound Driver Device2=Speakers (Realtek(R) Audio) Device3=Realtek Digital Output (Realtek(R) Audio) Device4=5 - Optix AG32C (AMD High Definition Audio Device) Device5=Headset Earphone (HyperX Virtual Surround Sound) Device6=Headphones (Oculus Virtual Audio Device) Device7=Realtek HD Audio 2nd output (Realtek(R) Audio) Link to comment Share on other sites More sharing options...
John Dowson Posted December 31, 2021 Report Share Posted December 31, 2021 First, can you please attach files and not paste their contents. If they are too large, you can zip them. I need to see the complete FSUIPC4.ini. Also, the latest version of FSUIPC is 4.977 - can you please update. Other than that, your log shows that your devices are continually reconnecting. Are you using a (powered?) hub? Make sure that there is enough power for your devices. Maybe try switching them to different usb ports/hubs. And check that you have usb2 devices plugged into usb2 slots. Maybe also try with just one device connected, then add each device back until you notice the problem again. Also, you should change this in your FSUIPC4.ini: AutoAssignLetters=No to AutoAssignLetters=Yes This will assign letters to your devices and prevent issues if/when your Joy ids change. John Link to comment Share on other sites More sharing options...
Kalnon Posted December 31, 2021 Author Report Share Posted December 31, 2021 Here you go. Sorry I thought I did paste the entire thing. FSUIPC4.ini FSUIPC4.log Link to comment Share on other sites More sharing options...
John Dowson Posted December 31, 2021 Report Share Posted December 31, 2021 The ini file you attached shows no assignments what so ever....have you ever made any assignments in FSUIPC? Your log file again shows continual scanning of your USB devices. This is usually a sign of a bad connection, an under-powered hub, or a faulty usb port/hub. Try changing/switching usb ports/hubs for your devices, and check all your connections and cables. And check the power settings in the windows device manager - you really need to turn off power management for all your USB hubs. You also need to check this now and again, as this setting can revert on Windows updates. Ans, as I said, you are using an old version of FSUIPC4 - only the latest version is supported, so please update to 4.977 before responding further. Also, please change this in your ini, in the [JoyNames] section if your FSUIPC4.ini: AutoAssignLetters=No to this AutoAssignLetters=Yes Not an issue at the moment, but this can/will prevent problems with assignments (that you don't yet have!) if your joy ids change. There are also very mixed messages on your devices between your ini and log files, which is usually a sign of dodgy registry entries. Can you also show me your FSUIPC4.JoyScan.csv file please. 6 hours ago, John Dowson said: Other than that, your log shows that your devices are continually reconnecting. Are you using a (powered?) hub? Make sure that there is enough power for your devices. Maybe try switching them to different usb ports/hubs. And check that you have usb2 devices plugged into usb2 slots. Maybe also try with just one device connected, then add each device back until you notice the problem again. Did you try this? It does look like a faulty device, hub or cable is giving these problems.... Please revise my comments and let me know how it goes. This is my last response this year, I will be back covering support from the 3rd Jan. I wish you and your family best wishes for the New Year, John Link to comment Share on other sites More sharing options...
Kalnon Posted December 31, 2021 Author Report Share Posted December 31, 2021 Here is the file you asked for. I will check into the things you've mentioned as soon as I have the time to troubleshoot the USB issue and test and get back to you. It is plugged directly into a USB port. I did previously have it assigned but like I said I just did a complete reinstall because my FSX install went to hell. I was having issues with it crashing often and it was running much worse than it usually did to performance wise. I ran the verify files utility on Steam and it found over 8,000 files missing somehow. I did however have the yoke assigned before it did and it worked fine until recently. I was having all these issues as well as the yoke stop working at the same time. Weird thing is that in MSFS it works just fine. Happy New Years to you as well. Cheers! FSUIPC4.JoyScan.csv Link to comment Share on other sites More sharing options...
Kalnon Posted December 31, 2021 Author Report Share Posted December 31, 2021 Could you possibly tell me what to check for in the registry that may be causing the issue? I do know basic stuff about using it and how to change values and stuff, and of course, always make a backup, as I learned the hard way once 🙂 Link to comment Share on other sites More sharing options...
Kalnon Posted January 1, 2022 Author Report Share Posted January 1, 2022 Well, you were right. It seems to have been related to the particular USB port I had it plugged in to. I just simply switched USB ports and it seems to be reading the yoke just fine now. I know you said to plug it into a USB 2.0 port but that's what I was already using. Instead I plugged it into a USB 3.0 port. I'm wondering if maybe my particular yoke needs the extra power that a USB 3.0 or 3.1 port can provide. I don't know if you are familiar with my particular yoke but it does have a bunch of LED lights and the whole front panel lights up, plus it has a bunch of switches on it so maybe it just needed the extra power to run correctly, either that or I have a USB port going bad. I've added those log files again just in case you would like to go through them to make sure everything's looks good there now. Thank you for your help I greatly appreciate it. And thanks for making such an important software so that I'm able to use my new yoke and other controls properly with FSX. FSUIPC4.log FSUIPC4.ini FSUIPC4.JoyScan.csv Link to comment Share on other sites More sharing options...
John Dowson Posted January 2, 2022 Report Share Posted January 2, 2022 15 hours ago, Kalnon said: I don't know if you are familiar with my particular yoke Yes, I have the same yoke. There still seems to be an issue though - your TWCS Throttle and T.16000M Joystick both have the same joystick Id. You don't seem to have any assignments to either of those devices at the moment but you would have issues if trying to assign to those devices. To correct this, first try changing your [JoyNames] section in your FSUIPC4.ini from: Quote [JoyNames] AutoAssignLetters=No 1=FANATEC CSL Elite Pedals LC 1.GUID={73DD7BD0-CD43-11EB-8001-444553540000} 4=T.16000M Joystick 4.GUID={8CB18220-FFE1-11EB-8002-444553540000} 6=Saitek Pro Flight Quadrant 6.GUID={72B7D780-A7A7-11EB-8001-444553540000} 3=Saitek Pro Flight Rudder Pedals 3.GUID={26FB3E20-995D-11EB-8001-444553540000} to Quote [JoyNames] AutoAssignLetters=Yes 1=FANATEC CSL Elite Pedals LC 1.GUID={73DD7BD0-CD43-11EB-8001-444553540000} 2=T.16000M Joystick 2.GUID={8CB18220-FFE1-11EB-8002-444553540000} 6=Saitek Pro Flight Quadrant 6.GUID={72B7D780-A7A7-11EB-8001-444553540000} 3=Saitek Pro Flight Rudder Pedals 3.GUID={26FB3E20-995D-11EB-8001-444553540000} Do this when FSX/FSUIPC4 are not running, then start FSX and see if both of those devices are recognised as separate devices. If not, show me your update .log, .ini and .JoyScan.csv files. John Link to comment Share on other sites More sharing options...
Kalnon Posted January 3, 2022 Author Report Share Posted January 3, 2022 Ok I did what you instructed and in the FSUIPC interface it doesn't recognize the joystick at all but it does recognize the throttle. I am not too worried about this since it works fine just binding it using the regular FSX control settings, though it would be nice to have that option if I ever needed it. I don't know if there was ever an issue with it before since I haven't yet tried to bind it using FSUIPC until now. There is another issue I am having regarding my yoke that I've always had since I first started using it with FSX is that FSUIPC doesn't seem to recognize the full length of the axis for the ailerons or it thinks the axis is shorter than it is. At least from what I see the VC yoke doing. When I turn all the way to the left, the VC yoke goes almost all the way except for maybe only a quarter to a half an inch worth of the last bit of travel which is good enough to me but when I turn it all the way to the right, the VC yoke stops traveling or maxes out when I still have around 2 inches worth of travel still left on the Alpha yoke. I can still fly just fine most of the time unless I'm stunting with a yoke aircraft, which is rare. I was just wondering if that is a normal issue with this yoke or is it just me? FSUIPC4.log FSUIPC4.ini FSUIPC4.JoyScan.csv Link to comment Share on other sites More sharing options...
John Dowson Posted January 3, 2022 Report Share Posted January 3, 2022 1 hour ago, Kalnon said: Ok I did what you instructed and in the FSUIPC interface it doesn't recognize the joystick at all but it does recognize the throttle. No, the ini change didn't work. We can try cleaning the registry entries if you like - let me know and I can provide you with a .reg file to do this. 1 hour ago, Kalnon said: There is another issue I am having regarding my yoke that I've always had since I first started using it with FSX is that FSUIPC doesn't seem to recognize the full length of the axis for the ailerons or it thinks the axis is shorter than it is. At least from what I see the VC yoke doing. When I turn all the way to the left, the VC yoke goes almost all the way except for maybe only a quarter to a half an inch worth of the last bit of travel which is good enough to me but when I turn it all the way to the right, the VC yoke stops traveling or maxes out when I still have around 2 inches worth of travel still left on the Alpha yoke. I can still fly just fine most of the time unless I'm stunting with a yoke aircraft, which is rare. I was just wondering if that is a normal issue with this yoke or is it just me? No, this is not normal. However, FSUIPC cannot see your yoke at all - is it assigned in FSX? There is an assignment to your ailerons for joystick no. 5L 2=5X,256,F,65763,0,0,0 -{ TO SIM: AXIS_AILERONS_SET }- But no such joystick (i.e. your Alpha yoke) is present in either your .ini, .log or registered in your registry: Quote N, x00, x044F, xB687, TWCS Throttle, -1, 4, 0, {NULL}, {8CB18220-FFE1-11EB-8002-444553540000}, {8CB18220-FFE1-11EB-8002-444553540000}, Y, Y N, x00, x044F, xB10A, T.16000M Joystick, -1, 4, 0, {NULL}, {8CB18220-FFE1-11EB-8002-444553540000}, {8CB18220-FFE1-11EB-8002-444553540000}, Y, Y N, x00, x044F, xB10A, T.16000M Joystick, -1, 2, 0, {NULL}, {35193120-FFE1-11EB-8001-444553540000}, {NULL}, N, Y N, x00, x0EB7, x6204, FANATEC CSL Elite Pedals LC, -1, 1, 0, {NULL}, {73DD7BD0-CD43-11EB-8001-444553540000}, {73DD7BD0-CD43-11EB-8001-444553540000}, Y, Y N, x00, x06A3, x0763, Saitek Pro Flight Rudder Pedals, -1, 3, 0, {NULL}, {26FB3E20-995D-11EB-8001-444553540000}, {26FB3E20-995D-11EB-8001-444553540000}, Y, Y N, x00, x06A3, x0C2D, Saitek Pro Flight Quadrant, -1, 6, 0, {NULL}, {72B7D780-A7A7-11EB-8001-444553540000}, {72B7D780-A7A7-11EB-8001-444553540000}, Y, Y Are you sure that the yoke was connected? To a hub or direct to the PC? Maybe try switching ports. The Alpha needs to be connected to either a USB 2.0 port or USB 3.1+ - there are issues with the Alpha on USB 3.0 ports. John Link to comment Share on other sites More sharing options...
Kalnon Posted January 4, 2022 Author Report Share Posted January 4, 2022 I have all axis of the 16000M assigned directly to FSX, I never assigned it to FSUIPC at all. It is the Alpha yoke that I had assigned using FSUIPC but just the ailerons. I do however have the pitch for the Alpha assigned directly to FSX since the pitch seems to work just fine that way so I never assigned that axis to FSUIPC. I did have the Alpha unplugged when I was testing the 16000M so maybe that could be why? It's necessary for me to unplug the Alpha when I switch to the 16000M due to the limited room on my desk. I keep the 16000M and TWCS throttle always plugged in because I use it more often than the yoke since I also use it for games like IL-2 Sturmovik BOS and Star Citizen. If you think it would help, I can reconnect the yoke and then send you the log files again. Link to comment Share on other sites More sharing options...
Kalnon Posted January 4, 2022 Author Report Share Posted January 4, 2022 Here's with the yoke plugged in. FSUIPC4.ini FSUIPC4.JoyScan.csv FSUIPC4.log Link to comment Share on other sites More sharing options...
Kalnon Posted January 4, 2022 Author Report Share Posted January 4, 2022 I also switched to a USB 2.0 port (different one than origanlly) and I updated to the current version of FSUIPC. Link to comment Share on other sites More sharing options...
John Dowson Posted January 5, 2022 Report Share Posted January 5, 2022 16 hours ago, Kalnon said: If you think it would help, I can reconnect the yoke and then send you the log files again. Of course I need to see that. You stated that your issue is that FSUIPC does not recognise your yoke. How can it recognise it if its not connected? The new log and ini files you posted shows the Alpha was recognised, now it is connected: Quote JoyNames] AutoAssignLetters=Yes 1=FANATEC CSL Elite Pedals LC 1.GUID={73DD7BD0-CD43-11EB-8001-444553540000} 4=T.16000M Joystick 4.GUID={8CB18220-FFE1-11EB-8002-444553540000} 6=Saitek Pro Flight Quadrant 6.GUID={72B7D780-A7A7-11EB-8001-444553540000} A=FANATEC CSL Elite Pedals LC A.GUID={73DD7BD0-CD43-11EB-8001-444553540000} B=Saitek Pro Flight Rudder Pedals << MISSING JOYSTICK >> B.GUID={26FB3E20-995D-11EB-8001-444553540000} C=T.16000M Joystick C.GUID={8CB18220-FFE1-11EB-8002-444553540000} D=Saitek Pro Flight Quadrant D.GUID={72B7D780-A7A7-11EB-8001-444553540000} 5=Alpha Flight Controls 5.GUID={83FCF960-9AE3-11EB-8001-444553540000} E=Alpha Flight Controls E.GUID={83FCF960-9AE3-11EB-8001-444553540000} Quote 234 Device acquired for use: 234 Joystick ID = 5 (Registry okay) 234 5=Alpha Flight Controls 234 5.GUID={83FCF960-9AE3-11EB-8001-444553540000} And you have your ailerons assigned to the X axis: Quote 2=EX,1,F,65763,0,0,0 -{ TO SIM: AXIS_AILERONS_SET }- and that you have also set a very large slope on the this axis (in the calibration tab): Quote SlopeAileron=-15 Such a large slope will give very little movement unless you move the axis to its extremes (check the slope curve in the calibration tab). So, if your ailerons are working but only when moving the axis to its extremes, remove that slope. If the ailerons are not moving at all, try switching to a different aileron control such as Aileron Set, or, better still, switch to using 'Send direct to FSUIPC Calibration' (rather than 'Send to FS as normal axis' and use the Aileron or Aileron/SlewSide control, and then make sure you calibrate that axis in the FSUIPC calibration tab. John Link to comment Share on other sites More sharing options...
Kalnon Posted January 6, 2022 Author Report Share Posted January 6, 2022 Well, I think I have the yoke fixed and working properly now. The slope I had adjusted it to was causing the issue with FSUIPC not correctly reading my ailerons axis. What is strange though is for me, when the slope is set to 15, it's even less sensitive and setting it to -15 made it more sensitive which is backwards from what you just explained it's supposed to work. I believe you when you said setting it to -15 would give very little movement, after all you are the creator of FSUIPC but for some strange reason, for me it's backwards. After a little tinkering, I found that when the slope to about -7 makes it just sensitive enough to perfectly match the VC yoke the entire way and it now sees the entire axis unlike before. If you would like, I could create a little YouTube video showing what it does when I adjust slope if you would like to see, just let me know. Otherwise, my issues now seem to be solved. Thank you so much for all of your help, I greatly appreciate it. And again, thanks for making such great software that allows me to use my yoke with FSX. Without it, the yoke sensitivity is so far off, I would never be able to fly with my yoke at all. Edit: I also changed the input setting to Send direct to FSUIPC Calibration as you suggested. Link to comment Share on other sites More sharing options...
John Dowson Posted January 6, 2022 Report Share Posted January 6, 2022 56 minutes ago, Kalnon said: What is strange though is for me, when the slope is set to 15, it's even less sensitive and setting it to -15 made it more sensitive which is backwards from what you just explained it's supposed to work. Sorry, I was mistaken: -15 IS the most sensitive curve (around the centre position) and 15 the least. Glad it is now working and calibrated to your needs. John 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