Black Square Baron and Bonanza Professional releasing soon

This information is based on data and real world tests. What is written in the poh are suggestions and guidelines, not what is allowed.

What is widely known today with all the data collected from modern engine monitors is that running ROP is worse in most ways for the engine. Backed up by data from Savvy and gami. Also backed up by boroscope inspections where engines operated LOP look a lot cleaner.

Spending more time in the climb, with lower airspeeds and higher CHTs is of course worse as well.

This is just me who likes to nerd about engines in my spare time. It’s a sim, fly any way you want and have fun! for me this stuff is fun that’s why i like simulating it as if i was the owner/operator.

1 Like

I am absolutely open to learn and adept. My main source of ā€œknowledgeā€ are just POHĀ“. I came across a few articles about the leaning controversy allready but never really engaged to deep into that matter, because for me it is not that important yet. So just because I am not convinced yet, that doesnĀ“t mean I would not be open to change my mind, if I would read more about it. Same for Climb Power etc..

But I am more the type of simmer, that is satisfied with a very basic knowledge about the operation of aircraft in the context of the simulation.

Your insights are definetively very interesting and I will keep them in my mind for future discussions.

3 Likes

(post deleted by author)

Great planes! Anyone know whether the overspeed warning in the turbo Bonanza (180 kts) can be disabled? Asking for a friend! :sweat_smile:

If you’re comfortable editing files, you can edit (in my example, for the turbine Bonanza)

community folder \bksq-aircraft-bonanzapro\SimObjects\Airplanes\bksq-aircraft-bonanzaproturbine\sound\sound.xml

At around line 340, you’ll find a code block for the overspeed sound. There you can change the ā€œLowerBoundā€ section.

For example, I changed it to 374.h knots:

<Sound WwiseData="true" WwiseEvent="overspeed" SimVar="AIRSPEED INDICATED" Index="0" Units="knots">
      <Range LowerBound="374.5" />
      <Requires SimVar="CIRCUIT ON" Index="26" Units="Bool" >
              <Range LowerBound="1" />
      </Requires>
</Sound>

This means you’ll still get the warning light but not hear the sound.

EDIT: Changed font formating to meet community standards…I think?

Oh wow perfect, thanks for the quick reply!

No problem! I just happened to be sitting at my FS computer when I saw your post.

Now if someone could pay it forward, I’d like to know if it’s possible (and if so, where) to set the default radio config.

Thanks to a post above I changed the XPDR default to off in apron.FLT.

I’m hoping that while we wait for state saving to work, I can at least have the plane default to how I want it config’d

So after a fair few flights, I’ve actually got mixed feelings on the Baron. I’ve been flying the NA Baron exclusively so far. It does all the things that I expect a BKSQ plane to do and it’s amazing for that. My problem is that the envelope didn’t get pushed at all with this release in terms of doing a little more with the persistent state, wear and tear and use of the walk around.

The TBM, Dukes, Starships and now the Baron/Bonanza are all great for the reasons we’ve come to know and expect from BKSQ but how come we still don’t have oil consumption and the need to check it? Is my battery wearing out or does it just take a beating every start and is brand new the next flight? I’m missing the next level here.

Don’t get me wrong, I appreciate how great they are but it just doesn’t feel as alive as some other planes. I really hope BKSQ digs a little deeper in this area on the next few releases. I’m dying for the AC690 and even though I know BKSQ will nail the TPE331 simulation and that alone will be worth the price of admission, I still hope there’s more persistence beyond my engine being what ever %.

1 Like

It’s been a LONG time since I did this, but I remember it working.

Basically, you have to load a flight in the same state you want to change. So, load a flight that will use apron.flt.

Change whatever cockpit elements you want to configure, then do a ā€œSave Flightā€. This should drop a new set of files, with a *.flt name.

Find the one that corresponds to the default apron.flt. Compare the 2 (original and newly saved) and only bring over to the items that relate to the NAV info you want to set. Save and replace the original apron.flt (make a backup of the original) and test. May take a few edits, sometimes you need more than one line item to make something work properly in the cockpit.

I agree. I was thinking the same. I love the Baron. It is all I am flying right now. It would be nice though to have the next level as you say. Tire wear, oil, dirt and bug accumulation that is now in 24, is it just resetting every flight in terms of wear… More accusim level of ownership. But I am happy with it, it is overall very good, and very realistic. Flies very nice too.

1 Like

Interesting…but I don’t see in apron.flt where you can set the GNS530 instead of the GTN750, for example.

That’s what I meant about ā€œradio configā€ā€¦I think your method would save things like frequencies and such?

Or maybe I’m misunderstanding something - I’ll experiment later on, thanks for the pointers.

Sorry I’m not more help. If you get really stuck I can try to recreate the steps. I don’t have these planes (yet) though. Dang payday!

That’s not stored in the .flt. Set that in the tablet and it should remember that once you set it.

1 Like

Yeah, I know that it should remember (and I know that it isn’t in apron.flt), but up-thread there’s reasons why state saving currently doesn’t work in 2024 and I was hoping there’s a shortcut for folks who are OK with editing files.