May 12, 20188 yr I have a CH Flight Sim USB Yoke. I can't set any button as the PTT. It stays with the 0. A keyboard PTT key set works as does the PTT button in the app. Bob Zolto
May 12, 20188 yr Commercial Member The Buttons in P2A are zero based, so 0 is a valid button number. My MadCatz joystick PTT and my Saitek Yoke PTT button are both numbered 0.
May 13, 20188 yr Author That's fine, but what if I want to change it to Button 9? he CH yoke doesn't have a button 0. Edited May 13, 20188 yr by Bob_Z Bob Zolto
May 13, 20188 yr Commercial Member Select the joystick or yoke from the dropdown list. Press the button you want to use. DONE. Don't try and enter a number. Dave
May 13, 20188 yr Author Not Done. No matter what I try, the 0 will not go away and nothing will replace it. Can'T program a Say-It button to yoke either. Edited May 13, 20188 yr by Bob_Z Bob Zolto
May 13, 20188 yr Commercial Member Can you click in the Button Number text box and then press a different button to see what happens? It's possible the CH Yoke is not being recognized properly, although I'm pretty sure many other users have that Yoke and it works for them. Dave
May 13, 20188 yr Author No buttons work. It is a pretty common yoke. Is there a way to have it recognized? Bob Zolto
May 13, 20188 yr Commercial Member Is it showing up in the drop-down to be selected? If so, it is recognized. Are you running Pilot2ATC as administrator? (Right-click the icon or exe file and select Run as Adminstrator from the dropdown.)It's possible there is an access issue of some sort.
May 13, 20188 yr Commercial Member No. The trial is only time limited. It is the same exact program. I don't think the log would have anything in it on this, but please send me the P2A log file so I can check. Log files are located in: C:\Users\<UserName>\AppData\Roaming\P2A_200\Logs where <UserName> is your PC user name. Portions of the path may be hidden by default, so be sure Windows Explorer has Show Hidden Items checked in the View tab. A new one is created each time you start Pilot2ATC, so if you take the most recent one when you have the error, you should have the correct one. Thanks, Dave
May 13, 20188 yr Author Here's the log Program StartedPilot 2 ATC (P2A) - version 2.5.0.2_x64 05/13/2018 14:06:05 Application frmP2AMain starting 05/13/2018 14:06:36 Loading Form Main form opened: Pilot2ATC 2018 v. 2.5.0.2_x64 Navigraph - AIRAC cycle: 1805 Loading Joystick Devices - 05/13/2018 14:06:41 Joystick Device: Mouse - Mouse Joystick Device: Keyboard - Keyboard Joystick Device: CH PRO PEDALS USB - Joystick Joystick Device: CH FLIGHT SIM YOKE USB - Joystick Loading Joystick Devices - 05/13/2018 14:06:41 Joystick Device: Mouse - Mouse Joystick Device: Keyboard - Keyboard Joystick Device: CH PRO PEDALS USB - Joystick Joystick Device: CH FLIGHT SIM YOKE USB - Joystick Loading Joystick Devices - 05/13/2018 14:06:41 Joystick Device: Mouse - Mouse Joystick Device: Keyboard - Keyboard Joystick Device: CH PRO PEDALS USB - Joystick Joystick Device: CH FLIGHT SIM YOKE USB - Joystick Loading Joystick Devices - 05/13/2018 14:06:41 Joystick Device: Mouse - Mouse Joystick Device: Keyboard - Keyboard Joystick Device: CH PRO PEDALS USB - Joystick Joystick Device: CH FLIGHT SIM YOKE USB - Joystick Loading Map Control LoadMapControl: panel 1 Creating ucMap1 SQLiteVersion: 3.8.11.1 | 2015-07-29 20:00:57 cf538e2783e468bbc25e7cb2a9ee64d3e0e80b2f | INTEROP_CODEC INTEROP_EXTENSION_FUNCTIONS INTEROP_VIRTUAL_TABLE NET_40 PRELOAD_NATIVE_LIBRARY THROW_ON_DISPOSED TRACE TRACE_PRELOAD TRACE_SHARED TRACE_WARNING USE_PREPARE_V2 WINDOWS ucMap1 Created ucMap DockFill set. Setting Map Mode Done Loading Map Control Loading FPL Control FPL Control Loaded ATCAssignsSTARs Changed to: True - 05/13/2018 14:06:50 ATCAssignsAPPRs Changed to: True - 05/13/2018 14:06:50 Loading Joystick Devices - 05/13/2018 14:06:57 Joystick Device: Mouse - Mouse Joystick Device: Keyboard - Keyboard Joystick Device: CH PRO PEDALS USB - Joystick Joystick Device: CH FLIGHT SIM YOKE USB - Joystick Loading Joystick Devices - 05/13/2018 14:07:19 Joystick Device: Mouse - Mouse Joystick Device: Keyboard - Keyboard Joystick Device: CH PRO PEDALS USB - Joystick Joystick Device: CH FLIGHT SIM YOKE USB - Joystick Application frmP2AMain ended normally 05/13/2018 14:07:31 Object of type SlimDX.DirectInput.Joystick was not disposed. Stack trace of object creation: Object of type SlimDX.DirectInput.Joystick was not disposed. Stack trace of object creation: Total of 2 objects still alive. Bob Zolto
May 13, 20188 yr Commercial Member Bob, It looks like it's being detected, based on the log file. Somehow the button-press is not getting to the program. Do you have any other software running that might be getting or trapping the button presses? Are the buttons set to do something in the SIM or something similar? The only other things I can think of is to try finding another Joystick or Gamepad to see if their button presses are recognized. Dave
May 14, 20188 yr Author All of the other buttons on the yoke work in the sim. I can program the button I want to use as the PTT in the sim. Keyboard selections work. I'll try a gamepad. Bob Zolto
May 14, 20188 yr I thought I had this issue initially with the same Yoke as I could never get anything other than 0 but it turned out I was not actually selecting the Yoke when assigning the button but rather the mouse. Even though it shows the Yoke selected in the drop down list there was another checkbox or click that I was missing - once I figured that out I was able to move the PTT to button 9 and all worked as expected. I suspect there is 1 small part of the assignment process that, like me, you have not quite done right - check both the left and right hand side of the screen to make sure you haven't missed a step.
May 14, 20188 yr Just to add, having read through the manual again and looked at the screen shots to see if I remembered what the issue was for me - make sure the enabled box is checked and then hit set which brings up the second smaller window where you select the controller from the drop down and push a button to confirm the assignment (may have to click in the button window, honestly I can't remember) but for a long time I thought there was an issue with the hardware because I only got button 0 which did not work but it was me.
Archived
This topic is now archived and is closed to further replies.