The next major update for Fly the Line is currently available as Early Access on the Fly the Line Discord server, with a full release scheduled in the not too distant future. Latest changelog of the upcoming update: https://community.justflight.com/topic/8860/fly-the-line-changelog-v1.0.454-early-access-updated-08-07-26 Fly the Line Discord server: https://community.justflight.com/topic/8876/fly-the-line-discord-server-early-access-builds Mark - Just Flight

We are aware that it is not currently possible to add any additional checklists to the interactive paper checklists in our PA-28s. This is something we have logged on our internal tracker, and we will look into it ahead of the updates to our PA-28s. As a workaround until the next updates, it should be possible to replace the existing 8 checklists with your own custom documents. As long as the existing documents are replaced and the total number of checklists remains less than or equal to 8, then the documents should display in the simulator. As a reminder, any changes to the package contents will require you to update the package's layout.json. For that, we would recommend using the free MSFSLayoutGenerator tool: https://tapeapp.com/just-flight/record/170946294 Mark - Just Flight

Sadly I don't have any experience with the software you are using, so I wouldn't be able to comment on the specifics of what is required. The LVARs for the FMP controls and displays should all have "AFCAS_" prefixes. For example, the IAS/M control and window all have "AFCAS_SPD_" prefixes: AFCAS_SPD_SrcSel AFCAS_SPD_SelLight AFCAS_SPD_KNOB_ROTATE AFCAS_SPD_KNOB_INC AFCAS_SPD_KNOB_DEC AFCAS_SPD_SrcSel_INC AFCAS_SPD_SrcSel_DEC AFCAS_SPD_PUSHPULL AFCAS_SPD_Window_1 AFCAS_SPD_Window_2 AFCAS_SPD_Window_3 AFCAS_SPD_Mach AFCAS_SPD_DP AFCAS_SPD_Knob AFCAS_Spd_Sel The ILS and ADF controls/displays should all follow a similar naming scheme, with the former have "ILS_" prefixes, and the latter have "ADF_" prefixes. Hope that helps. Mark - Just Flight

Thanks for the feedback. We've logged this on our internal tracker for our development team to look into further. Mark - Just Flight

Thank you for the feedback. We'll log this feedback for our development team to look into for a future update to the F70 & F100 Professional. Mark - Just Flight

The EFIS warning on the LH MFDU typically indicates that one of the EFIS displays has its brightness set to the lower position (OFF). I would recommend double-checking that the PFD/ND knobs on both EFIS Control Panels are all rotated above their minimum positions. Mark - Just Flight

Thank you all for the feedback. For any AFCAS/ATS related feedback, could I kindly ask you to raise a support ticket with Just Flight Support at the following link: https://www.justflight.com/support The F70 & F100 Professional are complex products, so in order to give our support team the best chance at offering speedy assistance, and for any potential bugs to get properly logged and addressed, could you please include any screenshots/videos of the behaviour with your ticket, as well as attaching the log file generated by the product. Instructions for locating the log file can be found here: https://support.justflight.com/en/support/solutions/articles/17000152594-where-to-find-the-log-file-s- Mark - Just Flight

Hi Mark...doh..yes contrails, my apologies. I must be flying in every warm area known to man lol not seen a single contrail yet and have been upto 34,000ft. Will continue to watch for them and thank you for the kind response. Tony

@Mark_Hazeldine said in Hardware support: As for Mobiflight/Spad.next, that's all great, but it is a pain to set up, and I would rather it just work out of the box. It's enough work learning how to fly the plane without having to figure out all that extra setup too. Unless WinCtrl creates a profile in SimApp Pro for this plane, which is very unlikely, you'll have to use programs like Spad Next, Mobiflight, etc. I think the only thing that Just Flight would need to open up is access to the MCDU. You can control the plane's autopilot and everything else using WinCtrl hardware now. I already have two snippets for this plane in Spad Next. One for the FCU+Left EFIS (snippet 17282) and the other for the TCAS (snippet 17363)

Hey Nick! Looking forward to the Turbo Commanders! In the latest update you released yesterday I couldn't see it in the photos but is the bottom triple flash beacon light going to be modelled if not already? Would loveeeee to have that! [image: 040a50ae-3a3a-46b0-ba8c-385757f10c22.jpg] [image: 490d2bce-701b-4cf0-9f22-87d943e2ac66.jpg]

Almost all of the indicator lamps in my aircraft output their state to a variable, which is explained in the "Annunciator Lights" section of the manual (~Page 159). You should be able to access the state of these lights via: (L:var_HANDLING_Light_Flaps_1_readonly, bool) (L:var_HANDLING_Light_Flaps_2_readonly, bool) (L:var_HANDLING_Light_Flaps_3_readonly, bool) Let me know if that works for you, and if you have any more questions! Always happy to help.

@Mark Hi Mark, Thanks for the reply and for taking the time to explain. I completely understand that the current PA-38 is based on G-BNKH. I just wanted to add that there is a genuine demand for a more modern Tomahawk configuration, especially here in New Zealand where the PA-38 is still one of the main training aircraft used by many flying schools. A lot of student pilots, including myself, fly these aircraft in real life and would love to train in a version that more closely matches what we fly every day. Even if it wasn't a completely new aircraft, small optional upgrades like a modern antenna configuration, Garmin avionics option, and a few updated cockpit variations would go a long way. Having these as optional configurations would keep everyone happy while making the aircraft more appealing to a wider audience. It's also been around a year since the last update, and I think an update like this would generate a lot of interest. Many current owners would be excited to revisit the aircraft, and it could also attract new customers who train on the PA-38 in countries like New Zealand, Australia, and the UK. There aren't many high-quality Tomahawks available in MSFS, so it feels like a great opportunity. Thanks again for listening and for continuing to support the aircraft. I'd love to see the Tomahawk get some attention in the future.

What I do is use the vertical nav button on the CDU and set the altitudes for the STAR and approach waypoints and then shoot for a 2000 fpm descent. It'll give you a needed descent rate and you can watch that count up as you get closer. [image: 3efdfa4b-9b51-4526-bfa4-608a0ed6efab.jpg]

@alanfernandes Yes you are correct but a lot of 3rd party devs have added in other features that aren’t included with the base working title avionics. Like for the G3000/G5000 Skyward developed a whole Datalink functionality with it and it has some protections built in. Especially now that we know that the King Airs are gonna be the 300 and the 1900D both of them could get garmins. The 1900D has a slightly specialized one called the G950nxi and the 300 has the regular G1000nxi.

@Matchstick To my knowledge all 1900D’s were EFIS-85 from the factory. I hope he doesn’t keep the 2 Tubes exclusive to the 1900 though. I hope be make is an option for the Super King Air 300 as well. Unfortunately I would assume they are pretty early in development though, we haven’t got any screenshots of them and just now found out it was a Model 300 and a 1900D. I personally was wanting the F90 but thinking about it I’m glad he went with the 300 and 1900D. There is Avionics galore for them and upgrades. The 1900D has its own specialized version of the G1000nxi called the G950nxi built exclusively that type of work

@Voice-of-Reason still some gremlin about; some FS Expo (?) photos showing for me.

Thanks, that makes sense. I'd only seen the default Caravan at 65 and assumed a sim update had changed it. Appreciate the explanation.

@martijn Hello! I understad, but over the Atlantic (and desert) I ended up far way from the point too. I red when the CDU doens't capture automatically (in bottom screen) the nearests VOR's (150NM...200NM signals) because is far from them, the accuracy, in a long leg tend to decrease, the IRS system makes kind of a triagulation with those VOR's. Not sure with IFR points... But when I asked "Am I right?" was for the specialists to awnser. The airplane doesn't have GPS as you know. Don't know if the "problem" worsne more with latitude or longitude. I belive, anyway, someone can explain you much better than me. Best!

Cool, thanks!