Bonanza Professional

No worries at all! Just thought I'd ask!

Isn't the 0-100 for the given K event?

More info: It seems, that it is also partially persistent. When i wrote the initial mail i was flying in the normal A36. At some point i could change to the TP or TC models and there i had normal behaviour. Going back to the normal A36 i had the big increments from the get go. Great, i thought, something reproduceable. Unfortunately after flying the TP for the last hours it somehow reset on the normal model. Now the course knob behaves there as usual as well ... And again thx, had so much fun today flying from the smaller VFR airports in the Bretangne, trying to fly VOR approaches manually, going along the coast clockwise. I have no idea what is realistic but i like the new sounds. Yesterday, while flying the Baron i suddenly had some tapping noise, first i thought i had a failure but i only had inadvertendly clicked on the keys ... ... so open baggage door ... nice touch.

low_rpm_shake_scalar = 0 didnt do anything. I then tried these in the flight model: min_castering_angle = 0 ground_new_contact_model_up_to_speed_lateral = 0 ground_new_contact_model_up_to_speed_lateral_steering = 0 (added) enable_high_accuracy_integration = 0 _lateral seemed to help the most.. now the high accel's go away with even very slow movements, but when you brake to a stop there's a jolt and continued hard lateral accelerations. also shutting the engine off while stopped brings accel to 0 [image: dca889de-cb4e-4576-854a-dc74f57c5ada.png]

I was able to patch one file to have L-variables for all buttons and rotaries of the KLN90B. May I send these to BlackSquare as an Idea for the update? If yes: which way? @Black-Square

Thanks. Missed holding it down for three seconds. Works as advertised.

It is in 2024, yes. It does look like it sweeps across the screen like a weather scan or test pattern, then remains white.

In MSFS2024 You need to load passengers and crew via the ATC Ground menu. First You need to load the Co-pilot and Passengers in the MSFS2024 EFB Payload menu, then call "Ground" and ask for boarding. Look here: Youtube Video

I've done some tests on this, and also looked at the tables more closely. Interestingly, the only table in which there's a significant discrepancy in fuel flows between the normally aspirated (NA) and the turbonormalized (TN) variant (at altitudes where the NA variant can still achieve the same MAP as the TN variant) is the 55% power table. For example, at 6,000 feet, 55% power, the fuel flow for the NA variant is 56 PPH, whereas the fuel flow for the TN variant is 70 PPH. At 65% power, on the other hand, the fuel flow given for both variants is exactly the same: 87 PPH. I did some testing in the sim. It looks to me as if, in the 55% power table, the fuel flow for the NA variant corresponds to a 100 LOP lean, whereas the fuel flow for the TN variant corresponds to a 50 ROP lean. The fuel flow in the 65% power table (which, as noted is the same for both variants) seems to correspond to a 50 ROP lean. So there does seem to be a difference in leaning strategies, but only for the 55% power table, where the NA variant uses LOP, whereas everything else seems to be ROP.

The math comes out to 4.977hrs with four 170lb people at 15,000ft. With 190lb people, this will be 4.453hrs.

I wish I had a better answer for you on that one. Brake efficacy is not something I have control over in MSFS. I suppose if any real pilot encountered the same problem, he/she would just do their best to ensure the correct operation of the aircraft's systems at whatever power setting they could maintain.

@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.