MSFS Products

Thanks for pointing this out. I heard about the same issue today though the TDS developer, which I assume you may have initiated too.

I had forgotten that I implemented a fix for this quite some time ago, but it hasn't appeared in any updates for my aircraft yet. If you would like to make the change yourself while you wait, it is very simple.

In ...[You Community Folder]\bksq-aircraft-tbm850\SimObjects\Airplanes\bksq-aircraft-tbm850\model\AnalogTBM.xml

Just search for these two keywords (should be lines 8872, and 8919 in v1.1 of the TBM):

"GTN_750_smallknob" "GTN_750_inknob"

And replace the "ASOBO_GT_Knob_Infinite_Push" lines below each one with the following:

<UseTemplate Name="ASOBO_GT_Knob_Infinite_Push_Timed">

Hopefully that will solve your problem! I've already propogated this change to all my aircraft, so it will be fixed as soon as I publish new updates after I release the Dukes. Thank you!

I am having major issues with the Arrow AP. I don't want its altitude hold feature active, I want to control the trim myself. I don't know if it's my logitech AP unit or what but the plane never seems to want to stop holding altitude. Because there is no switch just a clickspot, I can't tell whether altitude hold is supposed to be on or off, and my bindings for altitude and heading hold seem to do nothing in this plane. I'd like an option in the ipad to disable the clickspot and all the altitude features of the Arrows so they NEVER take control of trim, and the AP works as it would in real life, please. And ideally I'd like the "Heading Hold On" and "Heading Hold Off" bindings to work so I can use my switches instead of the mouse.

I think it might be my logitech AP unit interfering, so I will test with it unplugged, but it seems pot luck whether I can get the AP in the Arrow to release control of trim.

@Mark Thanks for your reply. From that I gleaned that the AP disconnect is not a feature of the aircraft so perhaps something might be wrong on my end.

I did a long testflight during which I unplugged my yoke and throttle quadrant and that seemed to cure the AP disconnect. After reconnecting the AP disconnected again after a while.

I checked the yoke sensivity setting in MSFS and noticed there was a "reactivity" setting I have never touched before. It showed 100 so I changed that to 98, on a hunch that this might filter out these spikes.

I did a long test flight with this setting and did not have a AP disconnect. The funny thing is, when I set it back to 100 I also did not have these AP disconnects anymore.

When I later checked for spikes using VKB Joytester I noticed that the yoke was indeed sending spikes once in a while, very short bursts but off the scale.
These did not lead to AP disconnects since I already touched the reactivity setting in MSFS.

Even after a very, very long flight the AP disconnect did not return except once when I changed GPS instruments on the tablet during a flight.

Perhaps the original value of the reactivity setting was not set properly in MSFS internally so setting it to 98 and then back to 100 reset something in MSFS.
Sorry for the long reply but hopefully someone else with a similar issue might benefit from this.

@trevor250

See this page - there is an email link to submit queries if you have bought products from elsewhere:

https://www.justflight.com/support

Did look but didn't find an earlier post from last year which I have now found through google and can see that this issue related to mixture = 0 setting on controller. Now tested by having Mixture 1 fully rich on my bravo and no engine shut down after pressing the ESC key. Alternative being to set up a separate Bravo profile for the Hawk and delete the mixture axis.

Thank you for reporting this. We have passed this feedback onto the UNS-1 development team to investigate, and we'll aim to get a fix included in the next update to the 146 Professional.

Mark - Just Flight

@Vitold69 FS Traffic doesn't have a way of deleting an entire airline via a single button, but you can unassign liveries for aircraft types, and delete a certain aircraft type from an airline, via the Traffic Control Centre > Aircraft Manager > Liveries page.

For example, if you would like to remove all British Airways A380s from the schedules, you can simply delete the assigned livery on the Liveries page and no British Airways A380s will be generated in the simulation.

If you do this for every aircraft type in an airline, you will still see the airline's flights listed in the flight schedules, but they won't be generated in the simulator as they don't have any assigned liveries.

Hope that helps.

Mark - Just Flight

I searched this when it happened to me and only found a post from 9 months ago where 2 people had the same problem and JF suggested checking for wayward fuel control assignments. So ...

I have 2 screens, with MSFS on the right screen and whatever on the left. When I click into something on the left screen that first click is also registered by MSFS as though the clickable cockpit area extends across my entire desktop even though MSFS is only on one half of it. This only seems to be a problem with the F28.

Long story short, one time when I clicked into navigraph on the left screen the fire switch cover for engine 1 opened on the right screen. I didn't think much of it, when I got back into the sim I just closed it and carried on - BUT opening one of those red covers closes the fuel shutoff valve for that engine. Instead of the fuel valves showing open/open in the white circles, they now showed shut/open. So I turned off the main start switch and tried the reset button conveniently next to the valve, which opened it again and the engine started just fine.

Workaround - don't click straight from MSFS into other programs while flying the F28, start by alt-tabbing out of MSFS to unfocus it, then you can safely click other windows.

Hope this helps someone !

@NickW61 Thanks for letting us know. We've passed this info on to our support team so that they can quickly point users in the right direction if they run into this issue.

Mark - Just Flight

This is unfortunately a quirk of the Working Title GNS430/530 logic.

The logic behind the autopilot controls on the EFB is deliberately very basic to minimise the likelihood of compatibility issues with the various GPS units. We are applying very little (if any) custom logic to the autopilot controls and once they are pressed, they simply trigger the respective autopilot control assignments in the simulator.

Therefore any weird logic quirks like the one you have reported are linked to the GPS units themselves. There are some fixes/improvements expected in Sim Update 15 relating to the Working Title GNS430/530 which may change/improve this behaviour.

Mark - Just Flight