Craig Deitch Posted November 20, 2019 at 05:13 AM Posted November 20, 2019 at 05:13 AM I’ve noticed two datarefs: xpilot/ptt and xpilot/version. I can’t work out what ptt does although it would be great if it indicated when the ptt was activated because I could put that in a VR window. Is that what it’s supposed to do? Version indicates a value of ‘1.0.1.1’ which may be out of date unless it relates to the plugin. I am using xpilot v1.1.5.0. Cheers, Craig. Link to comment Share on other sites More sharing options...
Justin Shannon Posted November 20, 2019 at 08:21 PM Posted November 20, 2019 at 08:21 PM Hi Craig, The "xpilot/ptt" dataref indicates whether the PTT is actively pressed (1=Active, 0=Inactive). The "xpilot/version" dataref has no use for endusers; it's used only by the UI client to determine the plugin version. Additionally, I introduced a command binding in 1.1.4.0 which allows you to bind a PTT key or button within X-Plane instead of through the xPilot Client. This should be helpful for those that use VR. Controller (C3), Los Angeles ARTCC Developer: xPilot, vATIS Link to comment Share on other sites More sharing options...
Craig Deitch Posted November 21, 2019 at 07:33 AM Author Posted November 21, 2019 at 07:33 AM Can you please confirm that the ptt dataref is working in the current version? I don’t see any change when I look at it with Datareftool. Link to comment Share on other sites More sharing options...
Justin Shannon Posted November 28, 2019 at 06:24 PM Posted November 28, 2019 at 06:24 PM I have confirmed that I forgot to add an event to toggle the "xpilot/ptt" dataref value if the PTT (set within the xPilot UI) is pressed. However, if you bind your PTT within X-Plane, the "xpilot/ptt" dataref value will change accordingly. I will fix this in the next release. Controller (C3), Los Angeles ARTCC Developer: xPilot, vATIS Link to comment Share on other sites More sharing options...
Recommended Posts