<?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[Suggestions for a possible v1.4]]></title><description><![CDATA[<p dir="auto">I've had a little time with v1.3 and overall I'm really pleased with the changes so far. A great plane is now even better.</p>
<p dir="auto">I'm sure a few things will come to light so thought we could collate suggestions here, should the Duke receive any future updates. Realistically, I appreciate it may well not receive any more (except emergency bug fixes if Asobo move the goalposts) and that's fine. There's no expectation, only boundless enthusiasm!</p>
<p dir="auto">A couple I am sure I have mentioned before but didn't make it:</p>
<ul>
<li>
<p dir="auto">I would love for the <strong>walkaround items to be independent of each other</strong>, i.e. the left engine plugs shoudn't also remove the right engine plugs. Removing the pitot covers near the nose shouldn't also remove the static port covers near the tail. Left chocks &amp; right chocks too. I appreciate that complicates matters with the toggle switches in the tablet, but it would make the walkaround more meaningful - and the cost of forgetting one more consequential.</p>
</li>
<li>
<p dir="auto">Unfortunately, there's still a typo (missing 'T' in 'limitations') on the label in the nose compartment (sorry)<br />
<img src="https://communityuploads.justflight.com/files/9299/4826794f-e81c-47f7-baa3-c5d4f4f3cc6b.png" alt="d2c693b8-0c70-461b-84f4-479741648924-image.png" class=" img-fluid img-markdown" /></p>
</li>
<li>
<p dir="auto">Prior to starting the piston Duke, positive fuel flow is obtained with mixture rich and pump on, even with the throttle at idle. I assume that's a deliberate and accurate change, but thought it worth a sense-check because it's unusual in my experience.</p>
</li>
<li>
<p dir="auto">I'd love if the <strong>piston Duke and Grand Duke were treated separately for state saving</strong>. They are presented separately in the aircraft selection screen after all. I fly the Grand Duke "for real" and use the regular Duke for "experimentation" sometimes, but state saving is shared between them. Ask me how I know! Per livery or tail number is even better, but I appreciate it might be a lot more complexity and not really worth it.</p>
</li>
<li>
<p dir="auto">With the changes in the piston engine modelling, it <strong>seems that the props can only ever stop in one position</strong>, with one blade in the 12 o'clock position. This might be correct to the real aircraft (and many photos seem to show it like this, though not all), but... I preferred when the props stopped in a less rigid position. I don't have tons of time on v1.3 yet, so stand to be corrected. But if it's accurate, I'll take it <img src="https://community.justflight.com/assets/plugins/nodebb-plugin-emoji/emoji/emoji-one/1f601.png?v=75b85052940" class="not-responsive emoji emoji-emoji-one emoji--beaming_face_with_smiling_eyes" style="height:23px;width:auto;vertical-align:middle" title=":beaming_face_with_smiling_eyes:" alt="😁" /><br />
<em>Side note: I've always preferred the look of a static 3-bladed prop when there's a blade near the 6 o'clock position rather than 12 o'clock. I just find it more aesthetically pleasing. Is it just me?</em></p>
</li>
</ul>
<p dir="auto">As ever, I don't mean to detract from the great release that v1.3 is, and I'm more than happy with what I already have.</p>
]]></description><link>https://community.justflight.com/topic/11555/suggestions-for-a-possible-v1.4</link><generator>RSS for Node</generator><lastBuildDate>Sat, 21 Nov 2026 00:15:12 GMT</lastBuildDate><atom:link href="https://community.justflight.com/topic/11555.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 20 Nov 2026 22:27:58 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Suggestions for a possible v1.4 on Sat, 21 Nov 2026 00:02:19 GMT]]></title><description><![CDATA[<p dir="auto">Watch the engine page on the tablet and you will see why the props stop where they do.</p>
]]></description><link>https://community.justflight.com/post/55711</link><guid isPermaLink="true">https://community.justflight.com/post/55711</guid><dc:creator><![CDATA[jmarkows]]></dc:creator><pubDate>Sat, 21 Nov 2026 00:02:19 GMT</pubDate></item></channel></rss>