PA-28R Arrow III

Im having problem with the trim with the Turbo Arrow III but on final approach, I read somewhere that it was impossible to flare with the TCA sidestick, so I tried it out, and at short final I noticed I had the stick all the way pulled down, I was trying to trim up the plane, but it was not reacting as expected, I hit the runway so hard that I damaged the plane.. LOL. I tried then the Turbo Arrow IV, and that was way better, I was adjusting the trim in short final and the plane reacted accordingly and I was flaring nicely.

I need to check this "trim" setting on the EFB and see if it helps.

Hi, uncheck in the EFB -> Aircraft -> Aircraft Options -> Auto Fuel Selector

That's great - thank you very much for letting me know. Even after all this time, she's still one of my favourite GA add-ons.

Some simulators and actual airplanes need the battery or alternator to be on for the navigation lights to work in the right way. In the event that the lights only come on when you start with the engine running, this is probably because the battery isn't providing power during the cold and dark start. You might need to go over your electrical settings, ensure the battery and avionics switches are on, and verify that there are no failures or settings that are causing the navigation lights to work abnormally. Just let me know if you need more help with troubleshooting!

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.

@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

@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

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.

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

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

@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

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.