PTT Issues

[David Cross]

1st off, thank you for the continued work on this platform. I know you all work for free to provide this service.  The only problem I'm running into regarding the PTT is prior to this version we were able to just assign a key / button. Now we're being forced to use an xplane command drafted by the installer "xPilot: Radio Push-To-Talk (PTT)" The problem with this is for those of us who pay for the Pilotedge service we are forced to use the standard xplane command "Contact ATC" which makes more sense anyway. So before, i could use the same key/button to talk to controllers both on Vatsim and PE. Now I'm having to go into settings every time i want to fly on a different network and change the command. Is it possible to edit a file somewhere to allow me the use of the default Contact ATC command?. I tried using two keys, one for PE and one for xPilot but it got to confusing, that its just easier in the long run to enter settings for every flight. Any help would be appreciated.  Thanks

Dave.

[Justin Shannon]

Hi Dave,

There is an option in the xPilot settings in X-Plane that should take care of this for you. See the first bullet point under Advanced Options: https://beta.xpilot-project.org/#/xplane?id=advanced-options

[David Cross]

1 hour ago, Justin Shannon said:

Hi Dave,

There is an option in the xPilot settings in X-Plane that should take care of this for you. See the first bullet point under Advanced Options: https://beta.xpilot-project.org/#/xplane?id=advanced-options

Ok those advanced settings state

"Override "Contact ATC" Command
If this option is enabled, xPilot will ignore the "Contact ATC" X-Plane command. This is generally only useful for users who also fly on PilotEdge."

But this is only useful if one chooses to use a different key for xPilot right?. Where as if you assign the xpilot xPilot: Radio Push-To-Talk (PTT) command to a different key and accidentally push the key I'm use to pressing for PE , being the contact atc button. Then i guess the default pop up atc window may be blocked with that option checked, but it still forces me to use either two different buttons or i have to manually swap between The two commands depending on which network i want to fly to use the same button on the yoke.

If the advanced xPilot settings would allow xPilot to overide IT'S command for for it's ptt and in fact use the xp default setting of "Contact atc" AND at the same time do block the popup atc window like the PE software does and your earlier build did, that would be great. Your advanced setting as far as i understand this still forces two different keys to be entered for the service you want to use.

If there is a work around file i could use to allow the contact atc xp command to use as the xPilot PTT command that would be great. Or have the option checked to use it would be best.

Thanks for the prompt help. Sorry if I'm not understanding this.

Dave

[David Cross]

I figured this may help explain my issue further.

I copied this directly from the PilotEdge client setup page. So you'll see we are forced to use the Contact ATC command, thus making it necessary to switch this command depending on which network we want to fly on if we want to use the same button, which obviously that would be our preference.

How to transmit on the radio

PilotEdge uses the CONTACT ATC function in X-Plane to toggle the Push to Talk. By default, this is the ENTER key (not to be confused with numpad enter). You can map a joystick/yoke button to be your PTT button by simply mapping it to the CONTACT ATC function.

To speak on the radio:

1. tune the appropriate COM radio (see the next section for transmitting on COM1 vs COM2),
2. hold down the joystick button or key that you have mapped to the CONTACT ATC command, speak into the microphone, then release the PTT button/key.

Dave

[David Cross]

Good talk

[Ned Torbin]

I agree, the new xPilot does not follow its own setting to Override Contact ATC command (as set in attached picture). I even restarted the software and simulator, and I just ran the update to v2.0.0 beta 22.

However, it did work in v1.xxx.  

Please fix this.

Thank you!

 

[Justin Shannon]

I see what the issue/confusion is now. X-Plane doesn't allow the same button to be binded to more than one command. I will remove the "Override Contact ATC Command" option in the next version to avoid confusion. This option was only useful when the PTT could be binded within the client, which isn't the case any more.

As a workaround, you could create two separate joystick profiles, one for VATSIM and one for PilotEdge and set your PTT binding accordingly.

[Justin Snapp]

@Justin Shannon Your proposed idea of creating two separate profiles is exactly what users are looking to avoid.    There is no reason you can't just registered a command handler for the Contact ATC command (sim/operation/contact_atc) and if the user has selected to override it (or just always if connected to vatsim), intercept this command and block it from the sim and handle that by then calling your own custom command.

I would submit there is actually zero reason that you should need to create a custom command here for the above reason.   The preferred design idiom within X-Plane and the XPLM is always to intercept existing stock commands and give them custom action wherever possible. 

Cheers,

Another Justin

[David Cross]

On 2/10/2022 at 11:19 PM, Justin Shannon said:

As a workaround, you could create two separate joystick profiles, one for VATSIM and one for PilotEdge and set your PTT binding accordingly.

I do appreciate the tip, however,  I did think of that, but it's just as easy to swap out the command. Either way you have to go to settings. I really didn't want to double my profiles for the ac i use the most. So I'm sticking to a single profile And I'll just swap out the command for now. Hopefully you can come up with a better solution. Maybe implement something like JS II suggested : ).

Thanks for the input.

Dave.

[Stephan Buchmann]

Fixed! Assigning 2 PTT buttons - FO and Captain: 

Fixed!  Double assigned in X-Plane (2 buttons same feature; wasn´t aware that´s working) 


(( Didn´t we assign in the previous versions one button in XPilot and one via X-Plane? Did I oversee it (it was late last night)? Or do we have FO and Captain in X-Plane? Will check that later . ))

Thanks for the great work ! 
Stephan 

Edited February 12, 2022 at 09:48 AM by Stephan Buchmann
solution found

[Justin Shannon]

On 2/11/2022 at 11:08 AM, Justin Snapp said:

@Justin Shannon Your proposed idea of creating two separate profiles is exactly what users are looking to avoid.    There is no reason you can't just registered a command handler for the Contact ATC command (sim/operation/contact_atc) and if the user has selected to override it (or just always if connected to vatsim), intercept this command and block it from the sim and handle that by then calling your own custom command.

I would submit there is actually zero reason that you should need to create a custom command here for the above reason.   The preferred design idiom within X-Plane and the XPLM is always to intercept existing stock commands and give them custom action wherever possible. 

Cheers,

Another Justin

The latest beta (b23) addresses this. If the override option is enabled, it will intercept the Contact ATC command and activate the xPilot PTT.

[David Cross]

17 hours ago, Justin Shannon said:

The latest beta (b23) addresses this. If the override option is enabled, it will intercept the Contact ATC command and activate the xPilot PTT.

Great news! Thank you.

Dave.