Bonanza Professional

@Black-Square I can tell you tomorrow. Wife insisted on some we time.

I've made this same mistake in the starship clicking through the cover of the circuit breakers. Maybe a hidden click spot to lock the breakers?

I had no idea about that as a setting. I’ll take a look and turn it off if it’s on by default. Thanks for the tip.

@jmarkows You are correct, an open storm window wont cause a plane to crash. Incidentally, at higher speeds its almost impossible to open the storm window (at least in a Cherokee). Once its open you don't notice it all that much, unless you get a piece of paper close to the open window- then its literally gone in a blink of an eye lol. Now when you board an airliner, before you tell them of your PMDG experience, hold up a fuel strainer and ask if they have already sumped the tanks. We LOVE that

I'm a 'dyed in the wool' Dynamic Registration hater. There! I've said it. All I want to see is the registration that the painter has worked on not to be covered by a white sticking plaster! How do I achieve that. Two painters have produced repaints with two options. One for real reg and on for vanity regs. I simply delete the vanity ones, refresh the layout.json and Bob's your uncle! The default skins are bare of registrations. Can I get the assigned numbers to show. Let me guess, it's on page one one of the manual.

@Black-Square said in Manipulating Cabin Air Vents via LVars: I once had someone tell me that L:Vars had no units, and that adding them made no difference. Those words echo in my head almost every day when I have problems, haha. Unfortunately, the FSUIPC documentation is rather poor on how some of these features work. How to implement them in FSUIPC, yes, but what you're actually doing, not so much. This has mainly been me trying to parse how the large library of pre-made bindings and functions from years of community contributions from all flavors of MSFS. The example I was looking at for the cowl flaps was from A2A's Comanche cowl flaps, as well as finding the RECIP ENG COWL FLAP POSITION:1 variable in online MSFS SDK where it was defined as a percent. In the manual, you listed 0-100, and it started working once I put the all-important A: in front of the var name. It was only because I have also seen "number" used in that field, as well as "enum," that I thought to try it. As I said, I don't have any documentation with a list of what it could possibly be. For the various air levers, while percent seemed to work for the levers, it did not for the valves they control. Do you, from a programming standpoint, have any inkling as to what might have been happening under the hood when the input was... typecast(?) as a percent instead of a number? This is purely me asking for a glimpse of how it works under the hood.

@Black-Square Fantastic! I'm very much looking forward to this change. Thank you very much for all the time and effort in this project! The Barron and Bo are my favorite addon. The time and attention to detail really show.

My sound designer and I listened to your clip, but try as we might, we can't hear anything out of the ordinary. For the sake of experimentation, would you try moving your camera to the right seat and telling us if the sound is now biased to your left ear? Everything we heard panning in stereo as you moved your head seemed to be as expected over here.

@Black-Square Thanks! As I say, I'd be happy for you to use this. Very cool that this is modelled BTW. Haven't tried it yet, but someday soon I'll have to pull the mixture overhead a nice big runway...

Yeah, clearly. I'll confirm my table interpolated number later. Probably in the neighborhood of 199kts and 1,078nm. Thanks for pointing it out.

Solved! It is a stock simulator variable, so it is looking for the A: in front of it. The full variable for interacting with is A:RECIP ENG COWL FLAP POSITION:1. Figuring that out, plus making my math actually do what I wanted it to do fixed it right up. Next update pass, Nick, would you mind including the A: prefixes for all base sim variables? After a quick look through the Bonanza manual, I think that's the only one, but I haven't checked your other products.

Yes, I saw your post elsewhere. This should be a relatively easy fix in just two places. Expect it for 1.1 very soon. Thank you!

As I've explained elsewhere, there are two different issues at play here. The "Load With Covers" setting is being saved, but the way aircraft are loaded in MSFS 2024 is preventing them from remaining deployed (the camera zooming in from outer space causes the aircraft to move around a lot, which removes the chocks). @turkintheus The other issue is Asobo's cloud state saving. If you are also not seeing the Hobbs state save, then the issue lies either with your system, or with Asobo, because I have exactly nothing to do with saving the Hobbs time.

@Black-Square This is why you deserve every single dollar you make, you CARE and you listen, some of the smallest things that really wont matter to much people you take the time (hours) to perfect it for the people that want it. There are large scale dev teams that wouldn't even think to do something like this. You are a solo class act. Thanks as always for your hard work and appreciation for your customers. Legend!