<?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[GNS430 RNG buttons inoperable and FMS &#x2F; progress fuel not synchronised &#x2F; AP alt set knob]]></title><description><![CDATA[<ol>
<li>
<p dir="auto">XBOX X Fs24, GNS430 range buttons do nothing only 5nm is available. Any clue?<br />
edit: VLOC input seems to be broken as well I cannot input ILS frequency.</p>
</li>
<li>
<p dir="auto">Supposedly it is my mistake but my FMS progress is counting down from the full tanks range and endurance instead of real quantities.</p>
</li>
<li>
<p dir="auto">AP Altitude SET knob key bindings ( decrease/increase autopilot reference altitude) dont change reference alt - instead plane just try to pitch up or pitch down after using these keys.</p>
</li>
</ol>
<p dir="auto">Thanks in advance.</p>
]]></description><link>https://community.justflight.com/topic/11383/gns430-rng-buttons-inoperable-and-fms-progress-fuel-not-synchronised-ap-alt-set-knob</link><generator>RSS for Node</generator><lastBuildDate>Mon, 21 Sep 2026 23:16:50 GMT</lastBuildDate><atom:link href="https://community.justflight.com/topic/11383.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 21 Sep 2026 12:11:42 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to GNS430 RNG buttons inoperable and FMS &#x2F; progress fuel not synchronised &#x2F; AP alt set knob on Mon, 21 Sep 2026 21:05:50 GMT]]></title><description><![CDATA[<ol>
<li>
<p dir="auto">I've heard a few complaints about this recently in many aircraft, including default ones.  I think Asobo messed up some interaction code in their last update.  Since I believe this is squarely on their side of things, I haven't gone looking for a solution yet, as these things often clear up quickly once they are reported.</p>
</li>
<li>
<p dir="auto">Since you say it's supposedly your mistake, would you mind sharing what that mistake supposedly is?  Perhaps I can confirm whether that's the intended behavior.</p>
</li>
<li>
<p dir="auto">Here is the relevant FAQ from the manual:</p>
</li>
</ol>
<blockquote>
<p dir="auto">Why is the autopilot behaving strangely with hardware inputs?<br />
In order to implement altitude &amp; VS preselect and more advanced features in the easiest way for cockpit builders to access, external hardware must use the HTML events described in the<br />
“Instrument Events” section of this manual and NOT the native autopilot events.</p>
</blockquote>
<p dir="auto">Let me know if there is anything else I can do for you!</p>
]]></description><link>https://community.justflight.com/post/54818</link><guid isPermaLink="true">https://community.justflight.com/post/54818</guid><dc:creator><![CDATA[Black Square]]></dc:creator><pubDate>Mon, 21 Sep 2026 21:05:50 GMT</pubDate></item></channel></rss>