Steam Gauge Overhaul

@kityatyi, the MSFS/FSX/P3D version will be adequate to get you started. There is a 14 day free trial so you can try it out before spending the money for a license.

There is no built-in method to do this, but I can offer you an easy solution to implement in the code yourself. First, you must locate the appropriate behaviors XML file for the aircraft you're interested in, such as "AnalogBaron.XML". Search for for "Gma340Location" and "Kma24Location" within the file. If you want the GMA340 to always be visible, and never show the KMA24, then replace the two blocks of code you found above with the following: <Component ID="Gma340Location" Node="Gma340Location"> <UseTemplate Name="ASOBO_GT_Visibility_Code"> <VISIBILITY_CODE> 1 </VISIBILITY_CODE> </UseTemplate> </Component> <Component ID="Kma24Location" Node="Kma24Location"> <UseTemplate Name="ASOBO_GT_Visibility_Code"> <VISIBILITY_CODE> 0 </VISIBILITY_CODE> </UseTemplate> </Component>

That worked like a charm, thanks!

Oh, my bad, thought it was an error that had stayed over from my mapping effort. Probably decimals I sat while reading that tutorial, and forgot about it, as I never mapped that function to the Radio Control Panel. Thanks for the insight.

@meh195, knowing this is an older topic, were ever able to find this: [SWITCH_ENGINE (Device)] in spad? I am trying to get the avionics switch assigned to my Honeycomb Alpha and not having success so far.

Works perfectly in both the Baron and Bonanza. Did not touch the code I posted above.

I came to the conclusion I was advancing my throttle too fast. when I slowly advance it, the engine starts as it should

Did you make the change to the GNS530 javascript file that is described above? I did finally receive confirmation from Working Title that this will be fixed permanently in Sim Update 15. If you made that change, and you are still having difficulties, it's like the result of a GPS addon incompatibility or outdated file in your community folder. The good news is that JF tech support has not encountered any GPS or Autopilot issue in my aircraft that they have not been able to solve. The first step is usually just trying the aircraft with a completely clean community folder to rule out as many potential conflicts as possible. As for the Go-Around button, it's up to Working Title to implement this correctly, and I do not believe that have yet. I will add this to my list for them to consider in a reply today. Please let me know how this goes for you, because there is no reason that we cannot get you a perfectly functioning Baron and Bonanza to enjoy, asap.

@Black-Square said in Bonanza Autopilot - occasional issues: Some of the switches will just "spam" their command 10 times per second, which tends to break things. It sounds like something similar was happening with the autopilot disconnect. That certainly is the one and only thing I don’t care for about the otherwise excellent Honeycomb controllers. Perhaps at some point I’ll look into SPAD or FSUIPC to make my own filtering for those controls, but I’m not of a mind to tackle that task just yet. The comments in the manual only speak to the virtual buttons inside the cockpit, not to physical hardware controls. Oh! That’s a thought which had not occurred to me - I always assumed the manual was referring to sim control bindings, and hence hardware controllers. Now I’ll reread the manuals with a fresh insight. Thanks again for describing your problem so thoroughly! No problem at all! My biggest problem is usually going into too much detail, rather than the inverse. And thanks again for your help.

Yes, you are correct on all accounts. Thanks for bringing this up again. I just put a note in the FAQ for the Duke so that people can hopefully avoid this issue. Your reply is very kind! I just hope you're enjoying the aircraft. I've built them as I always wished addon aircraft were, and I figured at least some people out there will have the same taste as me. Let me know if you have any more questions! Always happy to help.

Any thoughts on this?

Okay, much appreciated.

@Black-Square Thanks. A restart of the sim always works to fix this. I might make it my SOP to fly Black Square Analogs only after a fresh sim start to make sure all the states are correct. Thanks, love my all my BKSQ aircraft (five and counting!).

Hey Fellas, I have an update on this one. I had another report of this via tech support yesterday, so I spent several hours looking into the problem. As best I can tell, the flight plan is not synchronized with the GNS 530 when the GPS is hot-swapped in by my code, which can sometimes happen right after the aircraft is loaded. Clearly, other GPS units do not have this problem, so it should be something fixable in the GNS 530's code. I spent way too long trying to find a solution last night, so today I will write to some of my GPS developer friends for advice. Hopefully we can have a solution for you soon, and I can encourage Working Title to include that in SU15, before the release of my Dukes.

Engine alarms also working. This is starting to become everything I dreamed of in MSFS, when I bought these controllers. Analog Baron cross-country with throttles, radio and a nice yoke. Looking forward to go through your RNAV tutorial one of the days!

Use a drift meter. https://flightsim.to/file/19402/simple-driftmeter-for-msfs

I was not able to reproduce that bug today, so now the single profile for both planes, also with the the turbocharged versions works perfectly. Again, thank you very much for the superb support!