PA-28R Arrow III

603 Topics 3.8k Posts
  • This topic is deleted!

    Pinned Locked
    1
    5 Votes
    1 Posts
    1k Views
    No one has replied
  • Piper Arrow III Tutorial series

    Pinned
    10
    17 Votes
    10 Posts
    3k Views

    Updated the list with Full Autopilot guide. Happy flying folks :)

  • This topic is deleted!

    Pinned Locked
    1
    5 Votes
    1 Posts
    1k Views
    No one has replied
  • 16 Votes
    4 Posts
    27k Views

    Updated - v0.10.8 information added

  • Product Support

    Pinned Locked
    1
    0 Votes
    1 Posts
    2k Views
    No one has replied
  • HSI needle GPS issue

    2
    0 Votes
    2 Posts
    44 Views

    This appears to be the same issue described here: https://community.justflight.com/topic/5503/hsi-gps-mode-not-working/9?_=1732622244363

    I have already installed the latest version of all official packages. I have tried removing the Working Title official packages, but they are automatically re-downloaded when I start the game.

  • This topic is deleted!

    1
    0 Votes
    1 Posts
    1 Views
    No one has replied
  • Disable Altitude Hold

    5
    1 Votes
    5 Posts
    218 Views

    @Tensim The altitude hold click spot you refer to has been implemented in the Arrow since its original release in 2021, and therefore, we can confidently say that its implementation has not affected the autopilot behaviour in any way. The hidden vertical speed click spot was added in a post-release update based on feedback we received from the community and uses a similar logic to the altitude hold click spot. These clickspots use very basic logic and simply trigger the default MSFS autopilot modes when clicked, so any issues experienced with these features are likely related to controller conflicts with one of the default MSFS autopilot modes being triggered by external hardware.

    One thing that has changed significantly since the Arrow's original release is the updates to the GPS units. Each of the GPS units that can be selected in the Arrow has received significant updates by their respective developers since the Arrow's original release, and in some cases, this has resulted in effectively entirely new GPS units with enhanced simulation. Each of these GPS units does attempt to overrule the Arrow autopilot code with their own custom autopilot code which can cause autopilot quirks depending on which GPS is selected.

    If you would like to experience the Arrow with our autopilot code, please select the NO GPS option on the EFB, otherwise, the autopilot will be controlled by a mixture of our code and the selected GPSs code.

    As Derek has said above, if you are having any issues please open a support ticket with Just Flight support we will be able to assist with troubleshooting this further: https://www.justflight.com/support

    Mark - Just Flight

  • Piper Arrow III JF - autopilot nav issue

    10
    1 Votes
    10 Posts
    603 Views

    @Tensim

    https://support.justflight.com/support/solutions/articles/17000115071-pa-28r-arrow-iii-msfs-changelog

    v0.10.8 2023/08/18

    TDS GTNXi autopilot compatibility fixes

    Missing cockpit glass effects (including rain) - fixed

    v0.10.7 - 2023/08/04

    Working Title GNS autopilot issues - fixed

    KR85 ADF ANT mode logic added

    Storm window not animated when using exterior camera – fixed

    Autopilot panel texture issues – fixed

    Dome light texture improved

    Cockpit camera can no longer be moved outside cockpit area

    Tweaks to autopilot roll and navigation hold accuracy

    NAV/GPS switch logic changes for improved compatibility with WT GNS, PMS-50 GTN and TDS GTNXi

  • Heading Bug Broken

    14
    0 Votes
    14 Posts
    847 Views

    Bumping this because it is still broken. This issue only affects the Arrow and Turbo Arrow(s), the Warrior works normally. AUTOPILOT HEADING LOCK DIR is no longer referenced/changed with the heading bug.

  • 0 Votes
    1 Posts
    69 Views
    No one has replied
  • HDG Bug doesn’t work on msfs2020

    2
    0 Votes
    2 Posts
    130 Views

    I have just tested this and the heading bug appears to be working correctly with the controls on my Honeycomb Bravo. I do recall this was something that we fixed in a previous update to each of our PA28s though, so could you kindly double-check that you are running the latest version of each of the PA28s?

    Arrow III Changelog (latest v0.10.8): https://support.justflight.com/en/support/solutions/articles/17000115071-pa-28r-arrow-iii-msfs-changelog
    Turbo Arrow III/IV Changelog (latest v0.5.8): https://support.justflight.com/en/support/solutions/articles/17000117209-pa-28r-turbo-arrow-iii-iv-msfs-changelog
    Warrior II Changelog (latest v0.3.8): https://support.justflight.com/en/support/solutions/articles/17000118189-pa-28-161-warrior-msfs-changelog

    I have also attached a couple of screenshots of the control assignments I am using for my Honeycomb bravo in case they are of any assistance (they should just be the default control assignments):

    Screenshot (37857).jpg

    Screenshot (37858).jpg

    Hope that helps.

    Mark - Just Flight

  • Fuel planning

    3
    0 Votes
    3 Posts
    146 Views

    Hi, thank you for this info. Seems like a lot of calculating, I will give it a try though :) Thanks a lot

  • Lots of CTDs with all of the PA28's.

    2
    0 Votes
    2 Posts
    129 Views

    @niiloLehtinen128 said in Lots of CTDs with all of the PA28's.:

    I thought writing this post is my final attempt at ever resolving these issues.

    Have you been in touch with Just Flight support? I don't think it's possible to sort this type of issue in a forum but JF Support could certainly look into it.

    https://community.justflight.com/topic/2/product-support

  • Simbrief Profile?

    4
    0 Votes
    4 Posts
    1k Views

    One possible solution (if none forthcoming from elsewhere) is to modify an existing SimBrief a/c profile to match the Arrow III essentials. Then just use that profile. At present I have been using the Commanche, but I think the C172 is more suitable. Also, remember to edit the aircraft type when filing the flight plan.
    The problem is that it no longer seems possible to edit the cruise TAS when doing this. Thus ETE's, ETA's and fuel consumption are never correct.

  • 0 Votes
    6 Posts
    497 Views

    @clarkac Go to MSFS 2020 general settings. Click on the accessibility tab then choose Legacy controls and not locked. Now when you mouse over the vertical speed your mouse wheel should make it change. That's what I did and it works now.

  • This topic is deleted!

    1
    0 Votes
    1 Posts
    6 Views
    No one has replied
  • Can not install PA-28R Arrow III

    1
    0 Votes
    1 Posts
    83 Views
    No one has replied
  • Heading Bug Not Working Again

    3
    0 Votes
    3 Posts
    164 Views

    @Mark
    Hi Mark.
    I already created a support ticket after I posted this message.
    Thanks

  • How to load Little Navmap flight plan

    2
    1 Votes
    2 Posts
    937 Views

    Hello, in LNM you can create a PLN file. Via the File menu and then Export to MSFS 2020. Save it somewhere.
    In MSFS in the World Map you can Load it and voila...