@pequenyo sorry no, it's currently on hold. In Starship version 1.1, the GTN will not drive the autopilot in NAV or APPR modes.

@Black-Square Thanks for the answer. My concern is MSFS ending my flight, not you. If that doesn't happen, sure. I've seen reports from people saying it happened to them on their PMDG planes from TOGA overstress. So, no idea. Guess I'll see. Would be pretty annoying to lose a flight to it though cause the sim says "you ded"

@Flak Yeah it's annoying for something that compared to the other broken stuff in 2024 seems fairly trivial..Ruins screenshots of what is otherwise a beautiful model On point 3 though you can with some patience get BlackSquare's custom tail numbers working by following the workaround others have suggested of entering the customisation screen a couple of times (after renabling Nick's original code and disabling the current placeholder) Although I had to regress to SU2 as the latest beta build stopped that workaround working for me at least...So it will probably break totally soon

I’ve reported issues with Starship FMS and arrival fixes in SU3 beta here: https://community.justflight.com/topic/8521/unable-to-enter-arrival-fixes-in-latest-su3-beta-1.5.12.0 SU2 seems to work fine, but I don’t use the native ATC and don’t send the FPL from EFB to the aircraft.

you could totally go with one of the free video-sharing sites, this forum needs a bit of rep before you can upload files anyway. And even then the video might be a little too chunky to fit

@Randolf Ha ha yeah as I said if this quote is still correct then they'll never drain the battery, 5w virtual LED or 55w virtual 80s incandescent "Don't tell anyone, but the courtesy lights won't actually drain your battery in MSFS, because I am a merciful aircraft designer " I'm happy with a 99.999% accurate electrical system though same as the other guy.

Aarrrggg you're right, I was in GNS mode for the SID. Thanks

Wonderful! It was teamwork, because posting the King Air made me thing of just the right thing. I will add this to the release build for you. Let me know what kind of fantastic stories you might get from this very lucky individual. Have fun, and let me know if there is anything else I can do for you!

@ploodovic Not too surprised that it can be a bit of a rocky experience IRL as well. Still, I think that it is the case that a case of a quirky system IRL having its deficiencies further amplified by the aggressive autopilot pitching. For now I am also using VS mode (which, as people note in this thread, is also too aggressive), but I enjoy trying to make it as smooth of a ride as possible for the passengers. Also Air Hauler passengers start complaining when going to 0.7 G, which helps highlight things like this.

@MarkS said in Feature Request: EFB on the Pad: @x4569 said in Feature Request: EFB on the Pad: In addition I‘d opt in to ask to have the pad a) movable, as ist currently is for „dynamic“ sitautions, but also b) lockable on some sort of fixed mount to hold it during the flight. There is an option on the tablet, "VR Tablet Static Position" that puts it in a fixed position under the glareshield next to the left reversionary panel. While it says "VR" it works perfectly fine in pancake mode too. Agree and aware, but it still stays „floating“ in the cockpit, it should come with some sort of reasonable „mount“ to give it a more real taste

@DrZGard can give you also some pointers for FSUIPC, if you have any specific questions. I used it long time ago, before switching to AAO.

@lancealotg said in CDU "KYBD" Timeout: @John-S. Thanks for figuring this out. I didn't know about those js files. Because of this, I was able to find a js file for the checklists and customize it to my liking. Much appreciated. This sounds very interesting, where did you find it?

@Captain-Bakon But in general, yes, this is exactly the scenario I envisioned when I included it.

@Captain-Bakon It's on the configuration page a tab or two over from where your select the livery before starting a flight.

Thanks Nick! it's working again

@DDoBaGi Probably best if you contact Support in that case: Create a ticket with Just Flight Support via the following link, and our support team will be able to assist with troubleshooting this: https://www.justflight.com/support

@Marionettework As @jmarkows says. There are power setting tables in the manual. For climb you set 1600 and forget it. Use only the power levers to maintain table torque until ITT becomes limiting.

Hi thank you. I started a similar process and hit a point where the menu stopped working. Rolled back to a previous working state and the menu still didn't work! I now just have the 3 FSTraffic folders and it still doesn't work. I'm guessing some caching somewhere. Removed cache from my app/roaming folder but still no good. I have raised a ticket but willing to try anything.

Thank you all for your reactions. I completely missed the earlier discussion.I’ll wait for the dev’s further reaction. I love the depth of this simulation!

@Avionic Let me first say, that I don’t have the Starship (yet), so I’m merely spitballing here. It makes sense that you have to use a reference point not part of the flight plan, when the alternatives are point abeam and radial. That obviously can become a problem, if there are no appropriate points to reference. In your specific case, as you say, a solution could’ve been, to work out, at what radial toward MIKSI did your flight path intersect, when the distance to TNO was exactly 20 Nm, or whatever distance you’d prefer. It would require some extra preparation, for sure, but I think it could be a fun exercise nonetheless. Love these questions, where you have to use a little bit of creativity. Cheers, and good luck!