<?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[Sliding door issue - F100]]></title><description><![CDATA[<p dir="auto">For some reason the clickspots aren't responding on the L1 door.   The galley door responds-as does other interactive features.  The only way to open the L1 sliding door seems to be via the EFB.</p>
]]></description><link>https://community.justflight.com/topic/10843/sliding-door-issue-f100</link><generator>RSS for Node</generator><lastBuildDate>Wed, 01 Jul 2026 20:21:47 GMT</lastBuildDate><atom:link href="https://community.justflight.com/topic/10843.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 01 Jul 2026 08:31:05 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Sliding door issue - F100 on Wed, 01 Jul 2026 09:23:10 GMT]]></title><description><![CDATA[<p dir="auto">We are aware of some door interaction issues with third-party liveries that looks to stem from livery artists using a different format in the Title= entry of the aircraft.cfg compared to our own liveries. If the Title= line does not include the door variant, then the correct door logic will not load in the simulator.</p>
<p dir="auto">We're investigating this on our side to see if there's anything else we can do to detect which variant it loaded in the simulator, but for now, the quickest solution would be for livery artists to update the aircraft.cfg Title= entry so that it is in the format of:</p>
<p dir="auto">[Aircraft Type] | [Pax Door Type] | [Cargo Door Type] | [Airline]</p>
<p dir="auto">Mark - Just Flight</p>
]]></description><link>https://community.justflight.com/post/51700</link><guid isPermaLink="true">https://community.justflight.com/post/51700</guid><dc:creator><![CDATA[Mark]]></dc:creator><pubDate>Wed, 01 Jul 2026 09:23:10 GMT</pubDate></item></channel></rss>