Disregard. Restarting it didn’t fix it, but pulling the CB and resetting the CB did.

"site not found"

I did have fps degradation issues, but they disappeared after a NVIDIA driver update for my VC.

https://support.justflight.com/support/solutions/articles/17000131086-why-am-i-seeing-a-lot-of-white-aircraft-at-my-local-airport-

@plhought You need to get into train sims.... BR Class 86

@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

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 eagerly await the new version of the Cessna Caravan for MSFS2024.

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

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

I will do so. thx. It seems that the crahses when fsuipc is running. without fsuipc all works fine. regards Dieter