Ok, had to delve in deeper and managed to code electric trim up and down using that code, thanks. So only works when correct power on. I guess the button animation is not possible due to the var type used?

Thanks for the heads-up directing me to the DME functionality of the RNAV, indeed this would make it a good reason to keep it in IRL. Meanwhile I found that it's pretty useful for reporting points in combination with the KLN90, which does not have them. SO right now, only a more modern transponder would be cool, something simple, but not yet simulated maybe.. TQ TTX2, or a Trig TT31, or [insert whatever option here].

I pretty much always start on the ramp. I have tested - hot swapping to a TDS 750 and setting the transponder on there to ALT - hot swapping back to normal radios - set the transponder unit to SBY. Exit and reload aircraft it is back on ALT.

Ok, thanks Nick. So it's a simulationwise limitation? I can live with it without a problem. One can fly RNAV with setting the heading bug manual or use RNAV as reference system. Just trying to understand the backgrounds.

@comanche163 You can either select the textures you want from another livery, or you can point the new livery to one of the interior texture folders. Take a look at texture.cfg in one of my default liveries, and I think you will be able to copy it and figure out what to do. Let me know if I can help!

@Black-Square I was reading this topic and I wanted to provide some feedback. As other users are saying, I personally would love to see the Walkaround elements to be independently removed: each Pitot Cover, each Static Port Cover, etc. Brings more realism and immersion to the Walkaround, specially in airplanes with multiple of these elements, like the Dukes where 1 click removes 4 Pitot and Static Covers. I also highly support the clicksposts for entering and exiting the aircrafts. Have a good day!

I tried to make this pretty quick based off the PA24... Not sure how well it will work. AC11 Simbrief

Did you read this from the FAQ in the manual? Why does the mixture behave strangely in the turbocharged version, and I cannot bind it to hardware controls? Microsoft Flight Simulator’s turbocharger simulation has been significantly flawed for several generations. This aircraft has a custom turbocharger that fixes nearly all of these issues, and is much more realistic, as a result. To make these changes, the new “Input Event” system is used to intercept hardware and key-bindings for the mixture control axis. Please make sure that your hardware bindings are using the Key Events, such as “K:MIXTURE1_DECR_SMALL”, or “K:MIXTURE1_SET” to set the mixture, and NOT setting either “A:GENERAL ENG MIXTURE LEVER POSITION:1”, or “B:FUEL_Mixture_1_Set”. Alternatively, setting “L:BKSQ_MixtureLeverPosition_1” from 0-100 will also work to set the mixture axis.

I also want to add my vote for this. It would be awesome to see the fokker with the winctrl MCDU.

@s.mellah Did you press "Load aircraft" in the msfs efb after adding the passenger weights? I forgot this the first time and only saw the copilot, but when trying again now and pressing load aircraft and confirming, I had visible passengers too.

Fantastic, thanks Mark. That worked!

That's what I would have thought, but the OP seemed to suggest something different. I was just checking before I purchased ... which I'm delaying for a few days until I'm less busy and can commit the time to what I already know is a marvelous piece of virtual general aviation.

@Mark Thanks, rgr wildo...

@ksmith Wonderful news, Keith! I've been wondering if anyone had read my changelogs regarding updates for compatibility with mysterious online services. I can't wait to hear stories about how my users make use of this feature. Thank you so much for bringing us that opportunity.

Solved! I had to unistall it and reinstall it in a custom folder and then move it to the Community. The installer put everything in a JustFlight folder that my fs2024 does not recognize in the game. @Black-Square [image: e6c0ced4-b49c-402f-b328-7ca4d92b62d6.png]

When creating custom SimBrief Profiles, the only control we have over altitude is a "Service Ceiling" value, which is correctly set to 35,000ft, and a "Cruise Offset" value, which is intentionally set at P0000. The former controls what the aircraft's maximum altitude is, and the latter applies a global offset to that (for example, if we set a Cruise Offset of M2000 to the current profiles, then the maximum possible cruise altitude would be 33,000ft, even on 5-hour flights). Using a combination of the default SimBrief profile for the aircraft, as well as the values in the custom SimBrief Profiles, SimBrief then calculates what it believes is the ideal cruise altitude. We have no control over what cruise altitude SimBrief generates, other than what the maximum cruise altitude can be. The OPT/MAX altitudes in the CDU will always be a more accurate indication of the aircraft's optimum and maximum cruise altitudes, and if a cruise altitude generated by SimBrief is greater than those values, the SimBrief OFP can always be regenerated after manually lowering the cruise altitude. Mark - Just Flight

I'll give it a try. I like a good challenge (hence I bought this plane ;-))

@Black-Square No problem!

@SadBucket said in Awesome Release | minor bug/ Requests: Would be awesome if you could make engine start work from Mixture ICO I second that. It would make a great plane even more realistic!