Starship

Thank you for trying! The default 430 is the only flaw on this otherwise awesome aircraft.

I tested it with a mouse to rule out that issue already in 2024. I’ve not started 2020 since about a week after 2024 was released, so I’m not aware of the difference there. I’m using 1.1 which was downloaded before its advertised release via email.

Also, the area where the decal can be positioned on the engines is very small, any chance it could be extended forward/backward so that we can get creative with tail art?

@mxqn it took me a while to figure it out but what worked for me was to move all of the autopilot rotary knob functions into SPAD and make sure there were no duplicate binds in MSFS. In addition to setting up binds for clockwise and counterclockwise for each of the 5 selections (ALT, VS, HDG, CRS, IAS) I also added event triggers for knob push for VS (button 20), HDG (button 19), CRS (button 18), and IAS (button 17) and that prevents the issue where using the rotary knob for anything other than altitude would still change the altitude along with say heading or vertical speed. If I could attach a pic I would. I am glad I finally figured it out, was about to give up on SPAD and not buy a license but now that I understand it I plan to keep it - so maybe I can publish a profile or snippet next week.

Thanks for mini-FCU profile!!!! I'm. Unfortunately stuck at work at the moment, but hopefully there's a decent Starship turnout for the FSExpo VATSIM activities tonight!

I agree. It seems cheesy - but I would love the bar/commisary to be modelled as well one day!

It's fine, just the trend vector. Open that JS file with notepad and paste the new string of text over the old one. Ot wait until a new patch. It worked for me on both 2020 and 2024. I can't say I've seen anything else, but I've only done one flight in each. https://community.justflight.com/topic/8428/airspeed-trend-line-missing-in-version-1.1

I've never seen that. I use the TM Boeing yoke and assign a trim assignment through MSFS, not a 3rd party app.

Hey again For what it's worth, there's another typo in the RTU events: Rtu_TransponderStandbyButton_L should be Rtu_TransponderStandbyButton_1

Oh, turns out neither of my workarounds will work. As far as I can tell livery artists are completely unable to make a livery with ANY form of registration at the moment, which is a shame. We can't paint the livery in the texture because STARSHIP_EXTERIOR3_ALBD.PNG is mirrored. While this is good for texture efficiency, it is limiting for livery artists. We can't add a model attachment with the static tail reg on a mesh, because the model needs to animate with the engine nacelles when the wing flexes. I don't think this is possible to do by adding model attachments to the Starship model, although someone may (hopefully!) prove me wrong. We can't use the dynamic reg, because it simply doesn't work in MSFS 2024. It's a bit disappointing, we can't really do any paints for the Starship - although I still absolutely love flying it!

Strangely this has stopped working for me now, i'm not sure if I am entering things differently now or what but even when GNS as a source is on I cannot get it to follow the PMS GTN750 route anymore. This is a ball ache as it takes ages to type a route in even with the keyboard entry system, that keyboard system should not time out it should stay on until you press enter rather than having to ptess enter in the fms.

@SebAvi Probably because no Starship has been equipped with that.

@jmarkows thank you, i will try again. Actually it works. It's only a not correct idle position but dont affect too much. Ciao

All registrations. I assume he draws the stock ones in the same way, that way they can be overridden by a custom one.

@Randolf The standby/transfer pumps are on the battery bus. They will function with battery only.