PA-28R Turbo Arrow III/IV

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

I guess I've made around 10 flights with turbo and never had a problem like this. As @Martyn said, it sounds like this was caused by turbo detonation.

Thanks!

Happy flying

@Ron-Attwood Yesterday researching the files inside the texture folder I realized that using the Arrow NA and and renaming them for both turbo III and IV, they solved that aesthetic problem

@mrbogster said in Glass of rear lamp is shifted down:

@Martyn I thought I saw this one already but didn’t see it in the pending release notes. Are you guys aware that the lamp on top of the tail is pointed left instead of straight? It’s only noticeable in darkness on the turbo IV.

That should also be fixed in the update.

@Martyn said in Sounds... seems so 'flat':

The MSFS sound settings menu:

Sound.JPG

Ah thanks!!

Yes, Flightsim.to for me. I can't believe how easy it is to upload. Screenshots that I dont have to resize, bring the size down to less than 200mb and so on.
Incidentally, I was about to have a moan about the IV paint kit but I see it's being sorted. Crikey, I thought I was going potty!

I think I've got this working as much as possible within the sim limitations. Hopefully Asobo will address the ADF volume being controlled by the NAV volume control but in the meantime I've added some workarounds.