PA-28R Arrow III

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): [image: 59496c0e-2b6b-48e9-b491-c48c7d7c35c4.jpg] [image: 63e712bd-6de8-4485-9417-b05370a0a816.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.

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

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

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

@derek said in Update 0.10.8 GNS530 issues: @fsf_uk said in Update 0.10.8 GNS530 issues: Am I the only one still with issues? If it's a problem at my end I'd like to know. What did support say? If you have not had a respionse, let us know the ticket number. No, I haven't heard back since the ticket was raised. #74680. Thanks

@martyn Done. #74391. Thank you for your help.

Certainly the autopilot is broken - support say they know about it and are working on it. I find it too twitchy now as well. It certainly doesn't feel as solid and heavy as it used to be. Maybe that will be addressed when the update comes out. Have you filed a ticket with support? If enough of us do then they will address it I'm sure.

Are you using the autopilot at all? It is currently not working properly and they are working on a fix. Asking it to control altitude is causing a dramatic nose up pitch until it stalls. I have found recently the phugoid oscillation (how much the nose goes up and down before settling, after the pilot makes a power/pitch change) to be rather sensitive and if the turbulence setting in the sim is set to anything but "low" it pitches up and down so much I can't really take my hands off the yoke. I can't say I have experienced the violent jerks you are describing though.

The problem is fixed now