<?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[Regarding a bug with the F100 in the MFS2020 version]]></title><description><![CDATA[<p dir="auto">I have always been a fan of the Fokker series of aircraft; I’ve purchased the F100, F70, and F28 add-ons from JustFlight, but I’ve run into some issues while using the F100.</p>
<ol>
<li>When attempting to start the engines on the ground, I engaged the engine start switch and pulled it to the left to initiate the start sequence for Engine 1 (with the APU running and the bleed air system switched on). However, there was no change in the engine status indicators—neither in the bottom-left corner nor in the detailed engine display—which remained at 0%. I initially assumed I might have made an operational error, but after trying the same procedure again five minutes later, the reading remained at 0%.</li>
</ol>
<p dir="auto">2.My EFB frequently freezes—for instance, when on the OFP or Aircraft pages, it becomes impossible to exit and ends up completely locked up.<br />
I’m not sure if anyone else has encountered this issue, and I can’t tell whether it’s something I’m doing wrong or a bug in the plugin—but I still really like this plugin.</p>
]]></description><link>https://community.justflight.com/topic/11472/regarding-a-bug-with-the-f100-in-the-mfs2020-version</link><generator>RSS for Node</generator><lastBuildDate>Mon, 26 Oct 2026 03:30:27 GMT</lastBuildDate><atom:link href="https://community.justflight.com/topic/11472.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 24 Oct 2026 12:36:53 GMT</pubDate><ttl>60</ttl></channel></rss>