[image: ad33c2aa-5443-4368-b3a0-424da1c52e76.png]

Fly the Line: Short Haul Edition is primarily focused on simulating a short-haul airline pilot's lifestyle. You can read the product description of Fly the Line: Short Haul Edition on the product page here: https://www.justflight.com/product/fly-the-line-short-haul-edition Additional features beyond the scope of the product, such as cargo airlines and bush flying, are on the developers' radar for future versions of Fly the Line, however, they aren't natively supported in Fly the Line: Short Haul Edition. When generating schedules, a message will appear on the world map as a warning if too many routes are selected. The more routes that are selected, the longer the schedule generation will take. The exact time it will take to generate schedules will also vary based on PC specs. We would recommend taking advantage of the advanced options when generating schedules and keeping the number of schedules generated to a maximum of approximately 50. One of the main aims of Fly the Line is not to restrict your choice of aircraft types. This removes the sometimes tedious grind that can often be required in other career mode products, which acts as a barrier that prevents you from flying the aircraft you want to fly. Mark - Just Flight

Do you perhaps use GSX Passengers with the RJ? If so, there was previously an issue caused by GSX Passengers that would prevent the interior models from loading. This was fixed in a recent GSX update, so we would recommend double checking that GSX is fully up to date. Other than that, it sounds like an installation issue and/or a conflict with another product. We would recommend contact Just Flight Support via the following link and one of our support team will be best suited to assisting with further troubleshooting: https://www.justflight.com/support Mark - Just Flight

The GNS430s used in our PA28s across various simulators are developed by a variety of third-party developers, such as Working Title (for MSFS) and Laminar Research (X-Plane). Therefore, we don't have any control over their feature sets of functionality. We would recommend contacting the developer of the specific GPS unit you are referring to to request feature requests or bug fixes with the GPS functionality. Mark - Just Flight

You're looking for an L:Var that triggers the light, or an L:Var that indicates when the light is illuminated? For the latter, there are instructions in the manual under the "Annunciator Lights" section that describe how to access L:Vars for most of the annunciator lights in my aircraft. In this case, it should be L:var_MD41Message_EM_readonly. For the former, no such L:Var exists to trigger the light, since the lights all have complex behavior and I haven't been expecting users to drive them with their own logic, but if this is something you really wanted to do, you could add (L:MD41_MeggageLight, bool) or to BonanzaProfessional_Base_INT.XML in the block of code containing <NODE_ID>MD41Message_EM</NODE_ID>, directly before the line, </ON_CONDITION_CODE>.

Awesome! No worries at all, thank you for the update! Best Regards, Jakob

Excellent, thank you for the quick respond.

@Norman99 Just to clarify, the Analog King Air and Analog Caravan do not have the turbine engine simulation that my later aircraft do, so this is expected for those older aircraft in my fleet.

I addressed both of these with my sound designer well before release, and we spent substantial time trying to figure out what was going on. I don't remember exactly how that conversation resolved itself, but I'll bring it up with him again before the next update.

If it's always returning to this value, I suspect this is related to the broken state saving with SU4 that you may have seen others complaining about. Unfortunately, there isn't anything I can do about this, except pressure Asobo to look into this issue for SU5. In the meantime, there is currently a discussion on the official forums about a workaround with how you exit the simulator. That might be worth a try. Also, have you tried editing the state.cfg? I think others have had luck setting any values in there as they like.

@kletzi said in Occasional aggressive pitch-down events on approach: Yesterday and today (2.1.2026) I had very aggressive pitch down in a reproducable setup on short final at ELLX runway 24. The airport is on an elevated plateu, together with the wind 25012KT this creates quite some turbulence when entering the plateu. However, with Starship this seems especially bad, causing a pitch down that I couldn't recover from (AP and handflying) at first, and finally managed to just barely catch with full elevator deflection when expecting it beforehand. I tried the approach with another aircraft and while it got violent turbulence as well, there was not nearly as much pitch down as with Starship. Speed is not the issue. With calm weather there is no issue. Is Starship especially vulnerable to this kind of turbulence? Should it be? I also had something similar happen at Rimini in the meantime, though it was higher up and gave me a chance to recover. It might be exaggerated in starship because of the methods the developer has to use to get the canard wing to properly behave and feel within the confines of the sim. I notice a few developers of planes with complex flight dynamics, specifically airliners, recommend setting the msfs turbulence from realistic or medium, all the way down to low. Low is not as fun but it might be worth the try to prevent this kind of odd behaviour.

Well the indicator seems to have resolved itself lol. Yeah I found an earlier message later yesterday talking about the oil door. Man there's a couple really weird things about the Duke - setting off a master caution for a normal operation with the oil door and no indication for cowl flap position!? Beech quirks

Thank you for the detailed write-up, this might help me narrowing down the problem I've checked some vidoes on youtube searching for people with the same issue but sadly all of the youtubers only use the standard close view when going external, so even if they had the same problem they wouldn't know My hardware is super mainstream. i5 12600k, 5060Ti 16GB, 32GB, with the newest drivers, but I would assume if this would be a problem the issue would appear more under load and less when there's less going on, but it's always at the same ranges and the debug monitor doesn't show anything special when it comes to resources used. No special settings for MSFS2024 in the NVIDIA applications. In the sim everything is set to High (other than NPC and airports traffic, but I've also checked rising them to high). As of now, I have only found one person on the MSFS forums that has reported the same issue. An exciting mystery to solve, will continue investigating

I don't know if this was clear from above, but I just wanted to confirm that this is the intended behavior, and not a bug. This is very typical in aircraft with alternators and analog voltage regulators. It's actually often one of the first things that I hear real world pilots remark about when they test my aircraft, "you even got the low voltage light correct!" In my own flying, the cabin lights dimming and pulsing at low RPM while taxiing is actually a great indicator that you forgot to return the engine to an idle RPM of 1,000-1,200, which keeps the battery charged, and the engine healthy. Always happy to answer if you have any more questions!

The Navigraph takeoff perf calc for the Avro is inaccurate. Flex coming up as 50 degrees, sometimes the TRP does not even allow me to dial such high value in. Other times I run out of runway and climb out in a 100 fpm manner or even better, the jet nosedives to achieve the desired speed. Again, this is supposed to be a Professional stuff, allegedly study level. At this price range, I expect the devs to either provide a proper calculator (tool) or at least supply perf charts so we can properly obtain the required values. Otherwise the feature (flexi) is unusable, at least in a realistic manner. Derates absolutely require tools to determine their values.

ups,fdx,dhl

thanks ill try that i already knocked a few out hard to weed thru

Agreed, same reason I only ever use the G530 and G430 combo.

ILS 17 in to Porto with both ND's showing critical nav data to the approach. [image: 61e7a1d6-5abc-42e3-94a5-5191e75c9201.jpg] [image: 802b7776-606b-4b27-a408-ab2643c98855.jpg]

Thank you, I will try to find the solution in the MSFS Forums.