If you didn't have any failures, then I suppose the only operations are operator error, MSFS glitches, or some corner case in my code that nobody else has experienced yet. I'm trying to think of a debugging procedure I could give you, but perhaps video or screenshots might be the most helpful. Sorry that I don't have any quick fix. It just seems there are a lot of moving parts to this one.

@eracer1111 said in I'm confused about some of the BKSQ variables.: I own 13 Black Square aircraft I'm glad someone is keeping count Thanks again, and let me know if there is ever anything else I can do for you!

@Niko Many other developers have reported that state saving is almost completely broken in SU4, so you are not alone. I'm afraid there isn't anything I can do about it except add my voice to those asking for a fix in SU5. I'm glad you're enjoying the aircraft! Sorry to hear that you're having problems with the aircraft selection menu too... I'm also not sure there is anything I can do about that either. I haven't had any reports of this from PC users, so I suspect it's something Xbox related. If we can have more reports here with some more details, I can raise the issue with Asobo (I must say those words at least once per day). In the meantime, let me know if you have any more questions! You know where to find me!

You're correct, but I also see why I didn't do that in the code originally. MSFS only offers a single failure for the whole system, but I have since created my own vacuum/air simulation that should allow me to do something better. I will still leave the complete failure in the list as well, but I will make it much less likely. Thanks for letting me know.

I'm glad to hear you're enjoying the aircraft! Starship will always be my favorite, so it brings me much joy to share it with all of you! The state saving has been discussed at great length since SU4. It appears that Asobo introduced a bug that destroyed state saving for any aircraft that uses the recommended technique that you've found above. I know that several developers have brought this to their attention so far, so hopefully it will be fixed for SU5. I'll check the MS position text next time I have the simulator running. It's possible something like that can arise from text formatting errors (like rounding to nearest instead of rounding down). Thanks for letting me know, and always feel free to ask any other questions you might have

Thanks for the video. I think you have a good guess with the ground contact simulation, but I don't really recognize the sound. At the beginning, it sounds more like a cockpit interaction sound. Have you tried unplugging any hardware that might be spamming inputs?

Hi Kapa, thanks for the reply. The problem os that they never worked since last Friday when I got the Plane. Is not an issue that happens sometime during the flight. I can't simply not toggle the switchs since the begin when I load the sim.

Many thanks for the update. I’ll be glad to get my affected JF planes back.

Controller profiles are something that is handled entirely by the simulator, and we don't have any influence over. MSFS 2024 allows you to have separate control schemes for each aircraft, which may cause the difference in controller profiles you're seeing. I believe there is also an option to "Apply to all aircraft" when creating a controller profile, which will apply the same profile to all aircraft, like how MSFS 2020 handles it. Mark - Just Flight

Thank you for the kind words. For future reference, you may be interested to know that there are tools within MSFS Developer Mode that can help you find LVARs for any control in any aircraft. With Developer Mode enabled, if you move your mouse to the menu bar at the top of the screen, and navigate to: Windows > Behaviours > Local Variables. Entering instrument names or abbreviations into the ‘Filter’ field will vastly speed up the process of finding LVARs. For example, if you are trying to find the LVARs used for the transponder, you can search for ‘XPDR' and you will find the following LVARs: "PED_AFT_XPDR_MODE". With the Behaviour debug menu open, it is also possible to automatically populate the "Filter" field with the LVAR name of a specific control. With the Behaviour debug menu open, move your cursor over any control in the cockpit and then press [CTRL]+[G], to populate the "Filter" field with the LVAR name. Hope that can be of some use. Mark - Just Flight

We provided an insight into the latest progress being made with FS Traffic in Day One of our End Of Year Round Up 2025: https://www.justflight.com/articles/end-of-year-round-up-2025-part-one Mark - Just Flight

If anybody is wondering. The problem went away when switching from TAA to DLSS (both the old and the new version). Not sure if I will stay with DLSS, but for now that's what I'm using either way, so it's fine.

Enroute to Eagle CO with a setting sun. There just is no bad angle to take a pic of the Starship. [image: 9c8aed1c-3a42-4a13-9da6-4952e7a7bc8f.jpg] [image: 31496acf-8423-41d8-b33f-1d9fc9640bc1.jpg] [image: af4c6d16-f5de-4d08-b6be-50c80a64c826.jpg] [image: 60834b36-8759-45e4-b760-d0d77e16a2ed.jpg] [image: 8db7bc74-80a6-4a65-8d6b-7e2082571e2f.jpg] [image: afbb3a97-fbe1-44bf-9b10-ba1e28dd0605.jpg] [image: 6281c7b0-61b9-401e-bef2-04caf1c97092.jpg] [image: 0c447610-1afb-4b04-bf96-9a1e34e0afa3.jpg]

It certainly does sound like a control binding problem. Since the Velocity is a relatively simple aircraft, I would expect the virtual switch position to match the hardware position, but anything is possible with software. Have you tried disconnecting all hardware to see if everything works correctly when triggered from the cockpit?

Any updates?