Ok. Thank you.

That's fantastic, thanks @Black-Square! I really appreciate you taking the time to look at this for my derpy little Stream Deck dial I've had a go at addressing that using the same change-detection already used for lastVs, lastVsAdjustMode etc. Added lastAltAlert and lastArmActive tracking properties to the constructor, initialised to -1 so the first frame always fires and correctly initialises the L-Vars Both SetSimVarValue calls are now gated behind a comparison against the previous value, so they only fire when the state actually changes The diffAndSetText calls for the screen annunciators are unaffected and still update every frame as before New file is here if it's helpful: https://pastebin.com/9ptzAmjk I've given it a quick blast in the Bonanza and the Baron professionals this morning (what else is there to do when you cant sleep at 5am on a Saturday? The light over the south of England was beautiful!) and all seems well Obviously feel free to make whatever changes you like/need. I just wanted to have a stab so that my version doesn't suck my already-sometimes-sucky frames. The dial is complete! [image: 14773582-2f35-4c63-9b43-e5eac50ab374.png] [image: f5c78b3c-23c3-49a5-9829-4f44803d8547.png]

I have the same question myself. In the flight_model.cfg file this damaging speed 190 is under the "flaps" section, which makes sense since the max flaps extended speed is 180. Should this really apply to the landing gear as well?

@Rhinozherous thank you!!! ... Just checked it out - perfect!!

I just checked this, and everything appears to be working correctly on my end. Do you have the latest version of the Baron? I had to do some work in this area after the initial release. If you still think there is an issue, can you describe the circumstances of your screenshot a little more? The P-Baron should have winglets by default, so your screenshot depicts the "normal" lights, while toggling the tablet option should remove the winglets.

@Subsonic said in A list of Squawks as a 10+ year TBM Maintainer: The engine is slow to spool on the starter. I looked into this today, and unfortunately found that there appears to be a bug in the simulator, as the parameter that's supposed to adjust this has no effect. Apparently, this was a known issue for turbojet aircraft years ago, but it was not fixed for turboprop aircraft. I'll see if I can convince Asobo to make the fix for turboprops too.

Thanks for sending them another reminder to fix this issue, asobo should be ashamed of themselves for doing nothing to fix it on their end its unacceptable I'm very disappointed in them.

This came up a few months ago, and the poster tested the same key bindings with several other aircraft and determined that it was a simulator bug. Let me know if you have a chance to try the same test and find different results.

Pakistan, what are you doing, ahaha, stop! [image: 8839149d-78b4-4af5-886b-666315ddbc30.png] I honestly gave Bonanza a chance, and I love it, but it's just not Baron enough, if you know what I mean. This bird took me from Essen all the way to Turbat, known as the hottest place in the Gulf. And I didn't stop there - landed in Ahmedabad just a minute ago, almost 5.000 NM behind my back and I just can't have enough of Baron. Two engines, twice as much headache, and it's just so awesome! I love Bo, I really do. Bo with its fancy view out of cockpit makes a journey feel relaxed. A nice shot of the landscape made from between Baron's roaring engines makes a trip feel deserved and every good landing - well-earned. Will see how it conquers Nepal, wish me luck! [image: 12723915-a350-4e4a-8715-30dc65fc0d72.png]

Have the same issue with bonanza and baron

Figured that was still the case. Landing lights workaround is fine until they do. From your comment it sounds like SU5 did not tackle this, maybe SU6.

@Black-Square Thanks for the clarification. I guess I'll have to live with it showing up on shadows cast on the ground as well while sitting inside the plane. Other than this, it is a great plane, and has already provided me with hours and hours of entertainment. I thank you for that!

@Black-Square There seem to be some issues with the "A:IS USER SIM", more info might be here https://devsupport.flightsimulator.com/t/is-user-sim-is-not-returning-correct-values-for-multiplayer-aircraft/16920 For the Caravan is seems to work fine (as far as I could test it)

@Chicobello I checked the files as soon as I saw (I'm assuming your) post on the Official Forums, and all four flight models are identical in this respect. Let me know if you have had a chance to examine this.

The code appears to be correct. I can check this later, though. The code come from several of my other aircraft, where I assume this would have been reported if it was not working. If you want to see if this is something on your end, the events are: (>K:COM1_VOLUME_INC) (>K:COM1_VOLUME_DEC) (>K:COM2_VOLUME_INC) (>K:COM2_VOLUME_DEC) And to monitor: (A:COM VOLUME:1, percent) (A:COM VOLUME:2, percent)

Sorry for the delay. I was traveling to record sounds for my upcoming aircraft. No MSFS 2024 features here, just the code I have in each of my aircraft to make things more realistic. If you only want the speed to be divided by two, then you should be able to change (L:bksq_VisualPropRpm, RPM) 8 * to (L:bksq_VisualPropRpm, RPM) 4 *. If you also want to delay the transition to the blurred propeller disk, then change the first line to (A:PROP RPM:1, RPM) 286 > Let me know if that gets you what you're looking for. Always happy to help!