PA-28R Turbo Arrow III/IV

Hey,

if this problem is regarding the same question you asked at: https://community.justflight.com/topic/2362/ap-doesnt-pick-up-data-from-nav2

The HSI is only coupled with NAV1, you see NAV2 from the VOR NAV2 source.
But with the Hotfix it should intercept the course from the NAV2 VOR as long as you switch the source to NAV2

@weptburrito Oh thank you so much! Now I feel stupid.

Do I feel stupid now :D
Thanks

@ElKebek Glad you're enjoying it and that's a great video. Happy flying!!

Ok some update. I was flying the Arrow IV yesterday and initially everything was fine. Suddenly the animations on the plane froze. The prop animation didn’t “spin” anymore and the strobes stopped flashing the plane continued to move over the ground normally though. No stuttering or anything else that looked like it was sim related. More like it was only related to the arrow IV. When the animations started again 10-20 seconds later the autopilot spun out of control. Hard bank and nose over.

I then disengaged the autopilot and reset my heading and altitude. After re-engaging the autopilot everything was fine again.

Does that help in finding the issue?

@Delta558

Okay, I think I found something. I noticed that the ignition switch, after start, upon returning to BOTH, that's when the engine died. I tried the maintenance button for the engine, problem gone. I didn't realize that there must have been some engine damage from previous flights...good to know!

Lee

@majorswitcher okay, here is just my opinion. I have flown the version in both X-Plane and Microsoft. I've also been very lucky to fly the airplane in the real world. Yes, X-Plane does have a more accurate flight model. Microsoft has the scenery and the eye candy like no other and, they are improving the flight model all the time. I spent many years flying X-Plane, developing sceneries and really enjoying it. But honestly I haven't flown it for quite a while since I feel Microsoft has done a great job on the flight model side. It comes down to personal choice.

@Martyn And in the Arrow III too please :-)

@Martyn I am doing a flight right now with the turboarrow folder from the hotfix file pasted in the package folder (before I launched MSFS) (replacing 2 files, the .WASM in /panel) but switching the coupler switch to NAV2 still does not couple the HSI/ autopilot to my NAV2..
When switched to NAV2, turning the HSI direction knob also rotates the compass card of NAV1 CDI
Could I be doing something wrong?

@Sting

I have not had this issue since the update, and I was curious if it was “officially” fixed. Thanks @weptburrito . With the update though, the throttle lever has changed and now, for me, only about 60% of throttle advance gets me to overboost so you need to be careful how you apply throttle now.

Check my post in this thread:

https://community.justflight.com/topic/2360/v0-2-1-throttle/7

It's a nuisance, but for now there arrears to be no way around it unfortunately.

@jake_mazar I, too, can confirm that @Martyn's post is correct. With the most recent update, it is working properly on both airframes, which is good because I find with the IV, I have to have a LOT of nose up trim dialed in or I won't have enough elevator authority to flare properly. (Which is a polite way of saying I crash every time, even with my stick as far back as she goes, and I'm a RL pilot who generally makes perfect landings.)

I haven't quite decided if it's my imagination on the III, or because of the added propwash on the elevator due to no T-tail, or maybe I simply have had enough nose up trim dialed in without even trying to, but it doesn't seem to be an issue vs. the IV.

Hey, it turns out it WASN'T the deadzones! Cause the issue has returned on ALL GA aircraft. It turns out that SOMEHOW (perhaps with the Windows Update), Windows 10 has checked a Beta Encoding option under Control Panel/Region/Administrative/Locale option... I stumbled upon this on the official MSFS forums - that box should always be unchecked otherwise AP will just fly north. So just a heads up for anyone that encounters it.

The 0.2.1 version fixed my problem as well.

@Delta558
Thanks for explaining this. I was wondering if it was some kind of bug or a real thing.