The newer Barons and or nacelle kits are those style.

@Voice-of-Reason contacted Microsoft and i have the 2020 version now.

I tried that via the system.cfg but there's absolutely no effect in the sim. Testwise I set hideGPS and forceRegistration to 1 and entered 75% fuel to right aux tank but starting up the sim everything is with the original settings and values.

[image: 06ca91cc-1d56-4421-9b97-ea5cb34614ab.png] [image: dada85dc-d29d-46aa-a5e9-5082d946aa3e.png]

I bought this three aircraft package to fly as near IRL as possible also considering I’m on Xbox. And yes there is loads to do and learn especially the turboprop. It is also disappointing that state saving is buggy to say the least as this so important for immersion and I do hope this gets resolved asap because in systems depth these GA aircraft are up there with the very best in the sim.

I am having problems with my 146 professional. It usually starts with wrong ZFW and Gross Weight showing high numbers on solid red background. No matter what changes I make on passenger number, cargo or fuel those numbers won't change. After a couple restarts I get the "WASM module crashed". At that point only solution is reinstalling the 146. It works well for a couple of flights before the weight issues come back. Very frustrating. I have the feeling that "Shift+C" for entering the aircraft is triggering this issue. I know it sounds weird but I can reproduce the problem by repeatedly entering and leaving the plane with Shift+C. It only happens with 146 tho. It is my favorite aircraft, so I hope a solution will be coming soon.

OK solved it.

I was wondering this as well

That makes sense, and I appreciate the reply. I'm only using the 750 or 530 versions, for reference. However, I believe the problem is something like not having all the AIRAC data properly pushed to the sim (I don't know the proper terminology for this, so...) The reason I say this is because I ran the same type of LPV RNAVs into several different locations and found no issues, went back to the airports near my home, and found issues... tried to reset the plan while in the plane, tried a simple ESC, RESTART the flight -- and suddenly it works as intended! So it seems as if some approaches simply don't populate the sim/GNSS system properly on start up, and sometimes they do. I suppose this may, or may not be something that you have any control over.

I am flying across Australia with the Baron currently so I will be testing it out more in the coming days. I departed Perth and discovered that my auto pilot had failed so I got to hand fly the Baron at lower altitudes for a couple hundred miles. It hand flys like a dream, like it should. Honestly, I didnt think of this as being a bug since there was a backup that I used for a bit while I tried to troubleshoot. I got to see the pulse oximeter and the ear discomfort in action as I dump pressure and finally when the rate knob started working correctly. I did take a couple of photos but next time if it ever happens again will get video footage. Since I was on AP at cruise and I follow ARROW, I do have both a printed out BS Baron manual (my boss would thank you for the printer friendly version if she knew I used the company printer for it) as well as I pruchased an actual B58P manual in my simpit. So I tried to trouble shoot while in cruise. I also tried to use your YouTube videos to trouble shoot it. (Crazy how great cell service is at FL190 in the Australian outback as if I had Starlink internet ). Heres some pics from the flight that shows what I saw. https://imgur.com/a/FitL40J There should be 4 pics to that link.

@jmarkows All aircraft except the Analog Series and the Velocity have this code. That's what allows me to do the gyroscope physics simulations that you may have seen in my YouTube videos.

@Black-Square Thanks for getting back to me. Even with just my keyboard connected it still does it. I've had a look round the cockpit to see if there's any other interaction and I can't see anything. Is there any more debugging I can do from my side? Thanks

@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!

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