MSFS Products

3.5k Topics 18.2k Posts

  • 602 Topics
    3k Posts

    Even before the latest disappointing news I did wonder whether, if the initial delay was solely due to the ground physics, we could have an initial release with stock and then get the enhanced behaviours in the (likely to be one anyway) patch later.

    I suspect it's not that easy (never is) but I can dream :-)

  • 601 Topics
    4k Posts

    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.

  • 309 Topics
    2k Posts

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

  • 184 Topics
    963 Posts

    @trevor250

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

    https://www.justflight.com/support

  • 153 Topics
    632 Posts

    @jaspar11 I have just tested this and I am seeing the tail plan position indicator move between +5 and -3 by triggering the elevator trim assignments, so that sounds like there may be some other controller conflict that may be preventing the trim from working correctly for you.

    If you could kindly contact Just Flight support via the following link, they will be able to run through some troubleshooting steps with you to get you up and running: https://www.justflight.com/support

    Mark - Just Flight

  • 545 Topics
    3k Posts

    Okay, will be running tests on my side aswell. Thank you

  • 378 Topics
    3k Posts

    @TrailerSwift89 These codes are three-character IATA aircraft type codes as opposed to the four-character ICAO aircraft type codes that you have referenced. FS Traffic uses IATA codes as that is what is used in the databases.

    Mark - Just Flight

  • 253 Topics
    1k Posts

    Hello @Mark :)

    I already sent you an email to the address support gave me.

    Thanks

  • 93 Topics
    396 Posts

    @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

  • 3 Topics
    11 Posts

    Thanks for confirming. This issue did arise during testing and it seems to be an issue with the default ATC system as it's affecting several of our other aircraft as well as default aircraft too.

    I've personally had this exact issue occur (no ATC voices and no ATIS voices) and I've checked all the sound and assistant options are correctly set within MSFS, so I suspect it must be something within the MSFS itself that is causing this issue.

    There are also a few threads on the official MSFS forums with other users having similar issues: https://forums.flightsimulator.com/t/cant-hear-atc-voice/587403

    In the latest MSFS Developer Stream (24th April) the development team did note that ATC improvements are coming with Sim Update 15 (likely released 7th May) so hopefully something can be improved there.

    We'll continue investigating this on our side to see if there are any workarounds we can apply in the meantime.

    Mark - Just Flight