Steam Gauge Overhaul

@altack: Hmmm, I turn out that I can not move completely out of the cockpit, so I still have parts of the cockpit visible to the right of my seat But another strange thing I have seen: I am using BSQ King Air in MSFS2024, done by copying the files to the Community folder in 2024. I tried to do the old trick to comment the Interior = AnalogKingAir.xml, but after I did that none of the controls in my physical cockpit worked Strange, because I think it works in Msfs2020. Do anybody have experience with this?

@reiler Wow, this is amazing! I wish I had the space for a home cockpit. It'd be tough to decide what to build, but a King Air would definitely be in the top 5, if not the top 3.

Dive in https://www.justflight.com/product/black-square-baron-and-bonanza-professional-bundle

At last I got it to work None of the vars for Mixture will work, but after a lot of frustration, I ended up with this (the values are for my potientometers, might need to be changed in other setups): @ 341 < if{ (>B:FUEL_1_Condition_Lever_Cut_Off) quit } // < 341 → Cut Off 341 682 @ rng if{ (>B:FUEL_1_Condition_Lever_Low_Idle) quit } // 341..682 → Low Idle @ 682 > if{ (>B:FUEL_1_Condition_Lever_High_Idle) } // > 682 → High Idle

https://community.justflight.com/topic/8289/product-support?_=1759821363499

Problem solved, I had the KA version from Marketplace, and it got detected when I installed MSFS2024, I later bought KA from Justflight because it was not possible to copy the Marketplace version to 2024. Even though I deleted the Marketplace version in 2020, it did not work until I reinstalled 2024. But after deleting the Marketplace version in 2020 and reinstall of 2024, it seems to work.

Thank you @altack and @Black-Square I originally bought the King Air from Marketplace, and it did not contain the AnalogKingAir.xml file. Now I have (also) bought it from Just flight, also because I want to move to MSFS2024, and I could not get it to work with the Marketplace version (lesson learned...) But now I have the file, my chances are much better Thanks for your help.

Hi Guys, I get the same problem (from time to time) using MSFS popout Manager and my.... G1000 King Air homecockpit (but with the great Black Square Analog King Air as a backbone). So any help on that matter would be appreciated. Regards, Francois

Worth trying a reinstall?

@Outermarker One has to get the balance right between keeping customers well informed and avoiding too much AWNTY* for the development teams. I am quite sure there will be some more news in due course, but I think it is fair to say that most development date projections are a target first and foremost.

@Jafajones Glad you got it working Mike!

It will be a separate purchase, but there will be a discount of unspecified size if you own the overhaul version.

Is there the potential to give the users the ability to customise avionics outside of the simulator by choosing just one for that aircraft, just like the possibility to create a turbocharged, non-tip tanks entry by copying a folder and modifying a textual parameter?

I manged to get it working somehow reliably two times. I disabled my VPN as I've read in another forum that State Saving is actually saved onto Microsoft's servers (truly horrible choice), so I figured NordVPN might be a problem. The same post also told about the importance of choosing the same livery, as SS is tied to that also. This is not on the manual. I noticed that sometimes the livery is pre-selected, some other times it reverts back to the default one. In the first case, I've found it's good to actually select another livery, then select the previous one manually, and some of the variables are recalled: engine health, active failures, fuel on board, windowed open, cabin thermometer. The rest is always reset (including the radios).

Thank you very much to all.

This happens so much with so many different things (not just imported BSQ aircraft for what it's worth) in 2024 I just leave collision off. The common denominator for me was "various 3rd party scenery": in my case most often it would happen turning off of runway 35 at twy A at Tacoma Narrows (TIW). I have the Orbx scenery for it and there is just some seam or misalignment in various parts of the field that cause this, whatever it is is invisible to me. I've also seen it at Anacortes taking off south, multiple planes, same thing: you crashed! I also have a 3rd party scenery there, too. I thought I was doing something wrong til I disabled collision and magically everything is fine. No random bumps in the physics, just smooth sailing. If I had to guess, that may be your issue: if you haven't, try another field with just the basic 2024 scenery and maybe as flat a runway as you can find. Failing that, disable collision, though I can understand not wanting to.

I didn’t see any warning lights on either the glare shield or the pedestal, although it’s possible my view of that pedestal light was blocked by the throttles.