Bonanza Professional

You're looking for an L:Var that triggers the light, or an L:Var that indicates when the light is illuminated? For the latter, there are instructions in the manual under the "Annunciator Lights" section that describe how to access L:Vars for most of the annunciator lights in my aircraft. In this case, it should be L:var_MD41Message_EM_readonly. For the former, no such L:Var exists to trigger the light, since the lights all have complex behavior and I haven't been expecting users to drive them with their own logic, but if this is something you really wanted to do, you could add (L:MD41_MeggageLight, bool) or to BonanzaProfessional_Base_INT.XML in the block of code containing <NODE_ID>MD41Message_EM</NODE_ID>, directly before the line, </ON_CONDITION_CODE>.

@smokey01170 I’m feeling Thursday, considering what was said above, with regards to testing needed and staff away for the holidays. But I wouldn’t mind being wrong.

If it's always returning to this value, I suspect this is related to the broken state saving with SU4 that you may have seen others complaining about. Unfortunately, there isn't anything I can do about this, except pressure Asobo to look into this issue for SU5. In the meantime, there is currently a discussion on the official forums about a workaround with how you exit the simulator. That might be worth a try. Also, have you tried editing the state.cfg? I think others have had luck setting any values in there as they like.

@SadBucket said in A36TC POH: @Buzz No worries, my reply may have come out more accusatory than I meant... Just trying to help too. *Also, as far as I am aware, FAA does not require an engine or induction-system STC to provide any replacement of the manufacturer’s performance section so long as performance is not degraded... Maybe someone has done it, but it is not required to be in the POH. The STC only has to provide compliance with engine limitations and safe operating procedures in the AFMS. Please correct me if I misinterpreted this... The FAA DRS is your friend. Item 8. Apparently this STC requires the included supplement to be in the AFM/POH. https://drs.faa.gov/browse/excelExternalWindow/DRSDOCID128380987620240925140721.0001

Already discussed here

@SkipperMacz I actually stopped participating in betas back with 2020 because half the issues reported with them were never fixed before the SU was released in full. Sometimes I wonder what they're actually doing over there.

Glad you're enjoying it Happy New Year!!

After a bit of experimentation, I think it's the engine noise. I suppose the noise cancelling headphone simulation works by reducing the higher frequency components, making the rumble more noticeable.

@Black-Square: I hope you had a good Christmas and nice holidays. Is there any news on the update timeline?

@Black-Square thanks

Brightness looks absolutely fine to me... the manual offset should work on the backlight page under utilities. You should just have to hold it down for a while to see a difference.

Cheers all good now.

God, you have to love the knowledge this forum has...

KI-256 SPECIFICATIONS Size: 3.55"W x 3.37"H x 7.31"L

@TedStriker If you read my message above, you will see that this was a very time consuming workaround that I implemented myself, not something that Asobo fixed. I included this in the v1.1 update for the Baron and Bonanza, but I have not released these changes to the Dukes yet. I'm glad to hear that you're looking forward to it, though!

Here's some info on changing the panels from the Baron: https://community.justflight.com/topic/9472/swap-panels-on-liveries/12

Thanks. Good idea. I'll change the bindings. I was able to use the ignition panel this morning but I had to hold it in the start position and use the mouse to keep it from springing back.

and it's look like speed is faster about 10kts, they changed something