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

Amazing customer support and nick is cool as hell

The script from my last post I assigned to my switch position in AAO with "Assigned Buttons" and there via a key down event. For "MAN" I use the script: 2 (>L:var_surfaceDeiceSwitch, Number 1000 (>L:var_surfaceDeiceTimer, Number) 3 (>L:var_surfaceDeiceSwitch, Number) and I assigned it to the other position of my switch with another button assignment via key down event. For the centered off position I use the script 0·(>L:var_surfaceDeiceTimer,·Number) 1·(>L:var_surfaceDeiceSwitch,·Number) and I added two seperate button assignments via key up event to this script for the upper and the lower switch position.

The customer account and the forum account are not related. If you can't submit a ticket, you could always email support. There are links on the Support page at www.justflight.com

my issue is i fly alot bush airports, unfortunately some are not in simbreif but more importantly they require steep drops and maneuvering and with the forced night schedules good luck flying into an unlit strip cut in the trees. and If i am say not at my home airport i should be at a hotel on the company dime right? so why do i have to say sleep on the floor in the weeks schedule thing ?

I cannot even generate routes its been froze for an hour i tried many times, i can't log in to make a support ticket because it says i do not exist....

@Iconography Thanks, that makes sense! I treat them gently.

I noticed an oil pressure increase instead of decrease too. Thanks bksq!

Glad you're enjoying it Happy New Year!!

Hi guys, fixed with help from Dan and a JF ticket. I checked all the button mapping for the Honeycomb Bravo. Nothing for fuel cutoff, but I did find this in my mixture button mapping: DECREASE_MIXTURE 1 - set to number 28 DECREASE_MIXTURE 2 - set to number 33 I had been using number 28 for Set Starter 1 (Hold) and button 32 for starter 2. Clearly button 28 hit both the starter and mixture decrease, then when engine number 2 started, I rocked the switch back to number 33 and mixture again decreased. I saw no conflicts when I mapped this, but I think that was on another mapping profile. I had no idea about these bindings until I searched the Controls for 'Mixture'. I've cleared the mixture button mapping and now have a dedicated Baron Pro profile. So happy to have the Baron back in the sky! Thanks for all your replies and help. Happy New Year everyone!

Thanks Derek, sad but there we are. I can't resolve the broadband issues, only Open Reach can do that

I would greatly appreciate this too. Been having a blast this last couple of days with the PMDG 737 and the wing flex is very nice. The Cows DA42 has very nice wing flex too, as do others. It would make the RJ and 146 is even better!

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.

It's the EFB tablet itself that has been updated, i.e. the 'physical' device. It's now black, has a smaller bezel, extra buttons, higher detail etc.

yup, it was....I'm stupid...thanks ^^"

The camera's bounding box is baked into the model, so it would not be something you can adjust on your end, unfortunately. You could set a camera preset for this location, or use the native "toggle landing view" control in MSFS, both of which should ignore the bounding box. I try to create the bounding box to give as much vertical height as possible, so I suspect that there isn't much I can do in that respect without the camera beginning to clip through the geometry. I hope that answers your question. You know where to find me if you have any more!

@hughesj2