<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[AP Value Variables]]></title><description><![CDATA[<p dir="auto">Firstly, great to finally get my hands on this!  Starting to work out some of the differences in flying this compared to others but it's challenging in a good way!</p>
<p dir="auto">However, for us home cockpit hardware users, some of what's been done in terms of variables is a nightmare.  To output the selected altitude needs variables to hide some values where the altitude is 4 figures or less, and to display them requires reading multiple values and stitching them together (e.g. variables AFCAS_HD_Window_1, AFCAS_HD_Window_2 and AFCAS_HD_Window_3 just to display the heading selected!).</p>
<p dir="auto">Could we please request that the following be combined into singular variables for output to hardware:</p>
<ul>
<li>Altitude</li>
<li>Heading</li>
<li>IAS/Mach</li>
<li>Vertical Speed</li>
</ul>
<p dir="auto">Additionally, looking in Developer Mode, the ILS CRS value should be getting output in ILS_KNOB_CRS.  However, if turning this in the cockpit itself, not via hardware) at a reasonable pace (due to course being nearer South from it's load in value of 000), then the value output in that variable does not match that in the cockpit.</p>
<p dir="auto">Thanks!</p>
]]></description><link>https://community.justflight.com/topic/10802/ap-value-variables</link><generator>RSS for Node</generator><lastBuildDate>Mon, 29 Jun 2026 10:37:47 GMT</lastBuildDate><atom:link href="https://community.justflight.com/topic/10802.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 28 Jun 2026 21:19:28 GMT</pubDate><ttl>60</ttl></channel></rss>