Starship

You can, at least, tap the standby instruments just like the other aircraft.

Yeah, that adds up, I also have the feeling that the legs must be far enough apart to cause it. Thanks a lot Correction: I also see it closer to a fix.

I guess I'll see what happens when I go back later. I hit End Flight a few times to jump between liveries to no effect. Hopefully Asobo finally get the registration stuff squared away soon. I like how 24 feels and it runs so much better, but some of these issues are just bonkers.

You're the best!

Thank you for the hint. That was my fault

Need a Black Square shirt...Trying to support Nick's work , so I've purchased every one of his products. I just bought a taxiway sign for Taxiway Bravo (Also bought other letters from the airport to have my initials, i'm not insane) (I promise)

Oh yes I see it now.

Thanks Nick!

I found that, with the navigation_graph.pilot.cfg I posted earlier in this thread, for some reason, both the pilot and copilot were being automatically filled to their maxmass of 300 pounds. I found that removing the MassSections altogether and relying on default values eliminated this problem, and seems to be OK. (The Black Square tablet still uses a 300 pound limit per seat; the 2024 EFB becomes a 200 pound limit but I think we can just ignore that since we're not supposed to use it anyway.) BUT MORE IMPORANTLY: Somehow, removing the mass sections fixes the Starship's ability to properly restore weights on load in, and also fixes the problem of the weights from the EFB overwriting the tablet weights when exiting and re-entering the plane! Including for passengers, which shouldn't even be affected by the pilot navigation graph??? I'm referring to the 2 topics mentioned in this thread: https://community.justflight.com/topic/8258/payload-pax-reset-on-walkaround-mode/10?_=1751621648887 Both of these work as desired if masssections aren't used in navigation_graph_pilot.cfg

Hello! I would assume that if you created the files without breaking any rules to get it, then it seems ok to share as anyone with the same knowledge would anyway do it. This plane is really great!

I actually also like using the SDU for this purpose, but the more intended method is to use set the Preset Nav Source to VOR1/2 on the CDU, so you can monitor the CDI on the ND. Then, use the "CRS XFER" line select key on the Nav Source CDU page to instantaneously transfer over to your chosen localizer course and source.

@Sunake said in Crew Notes on MFD: I think operators can type some stuff in text files or word document or something on a computer, and put it on the floppy and upload it to starship, then they'll be displayed on that MFD page. I'm oversimplifying it but I think that's the idea. This was my thought, as well. As it is I use it as a good reference for things I should also look at. I don't fly IRL and thus tend to treat the weather as a surprise

Last time this came up, I was unsure of how the CDU interpreted frequency entries, but I now have the answer. It will be adjusted for the next update. All frequencies entered will be assumed to carry a decimal place, so 3675 will be interpreted as 367.5, and 15050 will be required to enter 1505.0.

Ooooooh woooow okay cool thanks for the explanation. And thanks for looking into the click spot

Thought it might be something like that. Thanks for looking into Simbrief injection.

Additionally here is what is con the BAT BUS from 122-590013-13B. 24-33-00 P2 [image: b119e897-1213-440f-98c5-d52fb2683871.png]

@SinkRate Would you be willing to share your form. This is the one I made for XPlane, the CL650 specifically based on an operator: https://forums.x-pilot.com/files/file/1359-aircraft-trip-log/