@Outermarker Yes, I didn't mention it, but I do indeed fulfill both of these conditions. One question: for this test, do we only use the cabin altitude Upper scale? When I perform a flight, I have to set the cruising altitude + 1000 ft on the AFCT (Inner scale of the ring) before takeoff? I'll try again to see if the test works.

Agree! I would totally like options like this. An Aspen PFD would be awesome, but if properly done could be an addon in itself.. and the standard G5 was Garbage.

@SebAvi Hi Seb. Thanks for applying your keen observation to my newest aircraft. I hope you don't mind if I reply in list form, since I've been receiving so much feedback lately. There should be a substantial impact on cranking performance, as it uses the same code from the Dukes. The increased friction, oil viscosity, and battery internal resistance should all play a roll. Engine performance should reflect the density altitude, but my sound designer and I have not made an attempt to capture a rough running engine during the warmup phase. I've received a lot of notes about this. This is one of the few features which I haven't taken complete control away from the simulator yet in my aircraft. I'm looking for a safe solution that I can roll out across my fleet. The easiest way to induce spark plug fouling is to leave the mixture at full rich at low RPM and low CHT. I have seen this effect many times in these aircraft, since I often have the simulator running in the background while I troubleshoot code. Thanks again! All your suggestions always make my aircraft better, so I'm always happy to listen!

Would you mind supplying some screenshots of what you're looking at?

or there's a sensor system like the Starship to control them.

Yeah, there is a post somewhere in this forum where someone had posted a 'fix' by editing a cfg file that displayed the copilot. Nic replied to it stating that Asobo's copilot avatar was too large when it was designed, that it clipped, other devs in the industry had the same problem and that noone could change it. Which is why he disabled it. Perhaps you made that edit and forgot about it.

Check the engine health on the tablet, please

@nrcrate said in Some Bonanza Feedback/Ideas: Since the last update, I can hear what seems to be the nose gear touchdown sound while taxiing occasionally, like the nose gear is skipping when it really isn't. I did not hear this before the last update I 2nd this

@Black-Square said in Squarish block on winglets?: Please forgive the copy-paste, but I have written about this many times since release, including just a couple hours ago. I hope you're enjoying the aircraft otherwise! That's a result of dynamic registrations being bugged in MSFS 2024. All dynamic registration issues are fixed in SU4 Beta. You don't see them everywhere else on the aircraft because I was able to make them invisible, but when you combine too many layers of visibility code, they get confused, apparently. No worries at all! And sorry, I did look around but didn’t have luck. Glad to hear it’s just a sim issue that’s due to be fixed soon. Really loving the aircraft! Thanks so much for making it.

Hmmm, time to find that breaker...

The ASI on the copilot's side also indicates the lower value of the normally aspirated Baron.

You should always set take-off power as 100% on the thrust indicators. Changing the thrust index changes what the indicators regard as 100% thrust, but that's the indicator you always want to hit. The lower the thrust index, the lower the LP and HP rpm indication at 100% thrust indication - you can see this if you set different thrust indexes on each engine or hold the aircraft on the brakes, set 100% on the indicators, then change the thrust index. As you noted, the information needed to do a proper FTTO (runway length vs. aircraft weight) isn't available. So what you can accurately do is a full rated thrust takeoff, setting the maximum thrust index for the given elevation and temperature. This is what the Thrust Index tables in the JF manual and on the in-cockpit paper checklists let you set, and what will be automatically set when you click the a square on the speed reference card, along with the relevant bug speeds. With a full rated thrust takeoff, if you've calculated the thrust index accurately, you should reach 100% thrust on the indicators with the throttles in the detent. In a FTTO, you would advance the throttles until you registered 100% indicated thrust, which may be before the detent is reached, because you are setting the thrust index for a temperature that's much higher than reality. The main purpose of the detent is to provide a clear throttle setting for the minimum throttle setting needing for the engines to produce rated power and the aircraft to achieve its certified performance. With the throttles in the detent and pitch matching the profile commanded by the flight director in Speed Control mode (not modelled in the JF F28), the aircraft is guaranteed to meet the requirements for obstacle avoidance etc. even on one engine. With the throttles below the detent, this isn't guaranteed, which is why the manual says you have to advance the detent OR beyond to achieve 100% thrust when you need full rated power. A Flexible TO is foregoing this guarantee when you have a lot of runway to spare, so you don't need to hit the detent. But if you had an engine failure after V1 you'd advance the throttle of the good engine to full thrust. The detent also indicates/activates other things like the automatic speed brake/lift dumper retract function, and the TTC system, but it's mostly there to indicate the max rated thrust position.

His posts were entertaining though and would make good training to teach AI how to self destruct.

@CoolGunS There are cases where the path length can cause issues that prevent installation in the Community folder. In such situations, using the BROWSE option is a great workaround. Additionally, when troubleshooting, the Addon Linker makes it easy to add or remove add-ons from the Community folder—it's much faster and more organized than manually copying and pasting files

@Black-Square said in Feature Request: Ability to hide throttle/prop/mixture levers: Try setting these two in addition to L:XMLVAR_AllThrottlesHidden: L:XMLVAR_LeverThrottleHidden1 L:XMLVAR_LeverPropellerHidden1 and two more in addition (for the second engine) L:XMLVAR_LeverThrottleHidden2 L:XMLVAR_LeverPropellerHidden2 works!

Thanks for the reply. Will have to experiment more.

UPDATE: I turned off state saving and did a Cold and Dark from the tablet, and now the problem seems to be fixed. I'll guess some state value got corrupted, perhaps related to my SPAD tinkering. I'll report back if this recurs.

Ive had this happen too, both in up and down directions. I turned off "realistic turbulence" after that, thinking it was some kind of crazy misinterpreted data causing an insane up or down draft. Recently I turned "realistic turbulence" back on, because medium seemed to really mean 0 turbulence. Hoping it doesn't happen again. Also I think that was before the most recent Starship patch had come out.

@bjratchf said in How do I tune HF radios?: Tuning 40000 gave me some german "achtung achtung - sieben drei eins null eins null).... didn't understand what the purpose of the numbers were. Someone crying for help? Just tried this one out, set to MAN UV and 4.0000, yep I am hearing the same thing lol. So cool.

I use custom tail reg regularly, and my hobbs and state saving has always worked.