pilotclient
pilotclient copied to clipboard
swift-project
Use Flightgears PTT hotkeys for swift
Hi, According to the comment:
Separate COM volumes can now be set in the UI and can be controlled from G and XP. Available with 0.9.7.149 and 0.9.8.36 (or later).
Originally posted by @ltoenning in https://github.com/swift-project/pilotclient/issues/100#issuecomment-1016238931
Controlling the COM volume should be possible by the insim values.
And indeed, they seem to be transmitted to swift:
I did just connect my first time to VATSIM and listened to radio calls from EDDM, which worked fine. However, the incoming radio messages where always the same volume, regardless what I did set in FlightGear. Changing them in swifts gui did work.
What am I doing wrong? (or is there something broken?)
Also just as an idea; flightgear has built in PTT buttons. That could be used as PTT enabling the radios in swift, so for example simulation of the C182s' GMA340 audio panel (or other aircraft simulating complex audio panels) could be supported.
OK.... nevermind, sorry for the noise.
I had "COM integration" not enabled. Ticket that and it worked.
InSim PTT does still not work, however.
InSim PTT does still not work, however.
(I do not talk about the PTT hotkey binding in swift; which needs read access to /dev/input/event* (provided by group inputin debian 12);
but the /controls/radios/comm-ptt/ FGCom property, which contains:
/controls/radios/comm-ptt/ |
Bedeutung |
|---|---|
0 |
kein TX |
1 |
TX COM1 |
2 |
TX COM2 |
/controls/radios/comm-ptt/Bedeutung0kein TX1TX COM12TX COM2
This would indeed be an interesting feature. But it would also require internal changes to the simulator plugin interface because this feature is not implemented for any simulator so far. We'll keep it on the list :+1:
which needs read access to
/dev/input/event*(provided by groupinputin debian 12
Just as a side note: We recently updated our docs regarding this. We now recommend a different method to allow reading input from a specific device using udev rules for security reasons (see https://swift-project.org/troubleshooting/linux_hotkeys/)
