Baron Professional

I have same post on reddit about lack of glass cockpit options in MSFS in general. Seems like it requires a lot of work from developers so I doubt that we see anything in near future. However one dude said that he is working on Aspen avionics as an addon and provided couple of screenshots.

Thank you for your reply. I'm familiar with AAO, but unfortunately, it doesn't recognize my hardware, at least not the panels. That's okay, though, so I'm using Spadnext instead Exactly, I found similar variables, but when I set them to 19, 20, or 0, naturally for each page, nothing happens. My guess is that perhaps a "sent" command or some other instruction is missing. As I said, this is purely speculative. Maybe someone else has an idea, or perhaps the team does? Best regards and many thanks, Dennis

Hi, thank you for your reply - it is really interesting how MSFS provides the data differently. I found a way to get the name easily, cause I am also using Simhaptic with a Buttkicker - and this software is more...let's say intelligent than the Moza Cockpit. This detects automatically which aircraft gets loaded (on MSFS, X-Plane or DCS) and it shows the internal name. For your aircrafts those are: bksq-aircraft-baron bksq-aircraft-baronpress bksq-aircraft-baronturbo bksq-aircraft-turbineduke And those names work as well for the Moza presets.

There is also a free tool you can download from Flightsim.to called PushbackHelper. You can use it with all airplanes but it allows to push or pull the plane.

said in Excessive turbulence at low altitude: @Black-Square from my understanding talking to A2A, they use their own flight model and the turbulence is somehow interpolated by them before effecting the aircraft. It has come to my attention that I may be wrong about this... I'm now noticing an absence of turbulance other than the occasional bumps they inject in. Kind of a huge let down if that's the case.

@Black-Square Thanks Nick. I'm probably the only one who has ever tested it, so don't lose sleep over it. Just the fact that you have acknowledged it is good for the time being. I'm sure in due time you will get around to fixing it. Cheers

I agree it would be great to remove the KNS81... I get your point, but in reality no one I could think of would keep a KNS81 when fitting e.g. a GTN750. Also, you can easily check your navigation with your Navigation Software like Navigraph. That all being said, could you maybe explain how to remove the KNS "with the gap"? I figured with my avionics layout it wouldn't hurt too much. Also, is it possible to remove the MD41-328? Not that helpful with a GTN xD Kind Regards, Jannik S.

Thank you for your willingness to resolve any issues we report to you.

I suspect it’s a problem in Wwise where the position is set wrong for certain objects which Windows spatial doesn't use.

Update, it now doesn't start at 0% but not sure if it's because of your suggestion or me uninstalling chase plane. I uninstalled chase plane because it disables the pilot being visible in outside views which bugged me a lot. Will wait till it gets fixed, I did your suggestion the same time of the uninstallation. Either way thanks for the tip again.

Just a quick bump because I'm seeing this in the Bonanza still. I think that's correct, v1.1 was the latest and this fix was made in a yet to be released version, yes? If so, I'm guessing we'll see a rash of BS aircraft updates around when the Caravan drops.

@Torcsen for what its worth, for me the spot has moved to a tiny spot on the metal shaft. The tablet is no longer clickable which is a bigger issue and the simconnect action to toggle it doesn't work either. Will have to wait it out, they tweaked the VR click depths in the beta.

@DeeKay Exactly how I always envisioned that would look for my users! I'm glad I was able to give you a quick solution. Enjoy!

@Black-Square Thanks for the reply. I managed to run some tests and noticed that the engines only cut out at idle if there is a tailwind. It seems the airflow must always be hitting the engine intakes directly. While not entirely unrealistic, I think the effect is a bit exaggerated causing the engines to die like that. Thank you very much, I’ll be looking forward to the next update!

@Buzz Thanks much, Buzz, will take a deeper dive into the topic indeed.

The procedure to save the status of aircraft solved the issue of hobbs timer, radio frequencies of 750, but not the transponder operational status of GTX 327 when the aircraft is powered on.

Interesting. I'll keep that in mind for my development, and I'll test that behavior through the debugger to see if that's the intended behavior. Thanks for letting me know.

Your explanations are always complete and thorough. Thank you every time you provide them. I have already replicated this behavior with SPAD.neXt. Regards.