Same on KLAX. Could it be because of excersive clutter on some mayor 3th part airports?

Many thanks !!!

@sender46 I totally agree that the best thing to do in the real aircraft, or in the sim, is to avoid flying in icing conditions, by closely watching the forcast weather along your planned route and not flying into clouds. And, if you do encounter icing conditions, to get out of it as quickly as possible by either climbing, descending or turning around... Meanwhile, you should also turn on the Cabin Heat.

@delta558 thank you. Preliminary testing since the update and the issue seems to have been fixed. Thank you.

I will let you know if it pops up again, but I am pretty sure it is fixed. I do need to fly the Arrow more to be sure.

@jf-john said in Please give us some info and best practice about destination:

@cbcdesign Both conditions have to be met for the flight plans to be processed. It's linked to the groundspeed so with any altitude and weather dependant you're likely meeting the conditions.

I see, that makes sense then as to why its all working for me. Thanks John.

@meh195, knowing this is an older topic, were ever able to find this: [SWITCH_ENGINE (Device)] in spad? I am trying to get the avionics switch assigned to my Honeycomb Alpha and not having success so far.

@Bert-Pieke Roger, no worries!

In my BKSQ Caravan using PMS50 GTN750 (latest version as of the time of this post) with the extra WTT-package 1.0.7 for AP/flight plan installed. A few updates ago, PMS50 stated that the WT-layer had a major update. Ever since then the AP remains lit when disabled. (i.e. ROL mode shown, etc.) However, the AP is not engaged in roll or pitch, just that some of the lights on the KAP140 display and the AP annunciator panel remain lit. I do have the systems.cfg and KAP140.js changes applied. Before the aforementioned PMS50 update and with your recommended bug-workarounds, the AP worked most of the time flawlessly, including no lights when disabled. It appears to just be a visual problem, AP works as expected (some bugs perhaps occasionally with weird altitude tracking overshoots still but that's another issue). I'm still on SU14, maybe SU15 will change something.

@Avionic Disable AUTO CREW in EFB settings. The stairs and doors won't extend/open automatically.

I've done a couple of flights in the Piston Duke now and I love it. I was struggling to fly it accurately but I think this was related to MSFS weather / turbulence because the aircraft was all over the place, the nose constantly dropping then bucking and the ASI gaining and losing 10 to 15 knots every ten seconds or so - with 'normal' / offline weather it was better...

I found some power settings to help fly the approach which is where I was really struggling and found that approach flaps, max RPM and around 15-16 in. MP gave a nice descent rate and approach speed and likewise with full flap bumping up the power to around 21-22 in. MP also worked nicely.

I've upped my failure rate now and look forward to diagnosing some issues soon. I did get a vapour locked engine recently and didn't manage to get it cleared and started but I was very pushed for time.

I'm struggling to find the desire to fly anything else right now :-)

Oops disregard I just read above that some valves are push to open and others are pull to open.

@Creech23 said in Turbine Duke Range:

MAJOR ISSUE. UNFLYABLE.

When I am in the duke throttle levers work yet I don't gain any RPM. From idle to full is just 1200 RPM.

I have my throttles set up so that full travel is normally from 0 to 100, in this case full beta to max power, and when I want to slow down after landing I have a hardware switch that toggles the reversers on and full travel becomes 0 to -100.

When what you've described happens to me it's invariably because I've knocked the physical switch and the plane is trying to go backwards. Try toggling your reversers.

@lilycrose I’m using my throttle to set the power to the proper setting within the power charts. I’m demonstrating that the turbocharger is overperforming at high altitudes because when the proper power settings are achieved, the aircraft behaves as expected per the manual. TLDR: Turbocharger issue, not Flight Model Issue.

In the King Air, the condition levers use the native bindings, so any of the following should work:

>K:AXIS_CONDITION_LEVER_1_SET >K:CONDITION_LEVER_1_SET >K:CONDITION_LEVER_1_INC >K:CONDITION_LEVER_1_DEC

@Derek,
well, I cannot wait for that so the JF store it is then. :)

Thanks for the quick reply!

@derek Raised a ticket this morning, and a couple of different options were given. In the end it turned out to be Fuel Valve assignments that caused the issue as the fuel valves are used in the Hawk to switch from Idle to HP Off. If I don't switch the fuel valves on with my HOTAS and manually click on the levers instead, it all works. Thank you for your help. Thought I'd post this response incase any one in the future experiences the same issue.

@jmarkows No I haven't seen this one yet I'll check it out. Thanks v much!

I did a 4h flight from Zurich to Gran Canaria and all worked well. Will report if anything doesn‘t but seems to be fixed for me (had issues on longer flights). Also had some en route traffic.

We spotted a small controller issue with the Xbox version of the 146 that prevented us from releasing the Xbox version this week. A new Xbox build has been resubmitted and should be released next Thursday.

Mark - Just Flight

Wonderful! It's been bothering me all day thinking about this, since there was nothing I could do to quickly fix it for you on my end. Thank you for sharing.