The textures do not change the model, so they have the same issue and thus the resolution doesn’t change.
The model defines the way the textures are placed, you can’t modify this by swapping textures.
You could provide a higher resolution to mitigate this to some extent, but they didn’t.
Hello,
I have stumbled upon an issue with the coupler radio selector switch for the autopilot in the arrow (both 3 and 4).
When switching the coupler to NAV2, nothing happens.
NAV1 works as it should, with the OBS working in both the VOR1/ILS indicator and in the HSI, and the autopilot responding accordingly.
My assumption is that when selecting NAV2 on the coupler radio selector switch, the radio signal from the NAV2 radio should be used by the autopilot, and visually checkable by looking and turning the OBS knob from the VOR2 indicator.
Am I right in thinking it should work this way, or is the NAV2 not capable of transmitting to the autopilot (since the HSI also only works with the NAV1 RADIO)?
Thanks in advance for shining a little light on this.
There’s a hot fix for this
Thank you for the link, page is boorkmarked!
Hotfix tested and confirmed working, and what a lovely plane!
I’ll collate the info and pass it on internally. It has been discussed previously so we might look at doing something to improve how this works and appears. Thanks for the nudge on this.
yesterday I tried to bind the NAV autopilot to NAV2 and it was not working (was using Arrow III, latest version). I double checked the NAV2 selector right below the autopilot selector and it was indeed set to NAV2. I tried using the rotary selector to NAV or OMNI but neither worked.
Probably something to check on JF’s side.
Adding a static link to the release notes page which is containing the most recent version and changelog might be the easiest approach and would have the benefit of having the changelog available right where it is of interest ![]()
Searching the forums or support pages is not the best approach for every customer.
It is literally two posts above yours. They fixed it already and if you don’t want to wait for the update, there is even a hotfix.
Hopefully sending the Turbo Arrow out later this week or start of next week to all third parties.
I have unbound the nav switch in the FS controller settings - problem solved (have to remember to turn on nav lights for all aircraft in the virtual cockpit now)
thanks, I didn’t notice it. ![]()
Thanks for the reply, Scott. And good news! ![]()
Hi all, just did my first takeoff with the turbo arrow IV since the latest update. Not sure if it’s the result of updates or lucky live weather with no crosswind, but my takeoff roll felt right for the first time. Stayed on the ground up to 70 knots without the “swerve”. Yay
Anyone still getting the fishtail effect on approach, in version 0.7.1?
Never had it on approach.
I do get fish tailing on take-off if the elevator trim is set to nose down or neutral. Part of my pre-flight is add a degree of right rudder trim and a degree of nose up trim.
In the same vein, I tend to fill up the right tank slightly more before take off (and then balance them mid-flight) . I’ll see what a degree or two of right rudder trim does to compensate this effect on approach.
Thanks ![]()
Unlike your average Cessna, most Pipers emulate the flying characteristics of a house brick when descending dirty with Power Off, so you do tend to need a bit more power applied on approach than a Cessna and hence potentially rudder trim.
The rudder trim needed for take-off should be similar to what your climb out trim will be.
The trim required on approach should be more like what you need for economy cruise, maybe a touch less. Some people recommend just leaving rudder trim at your cruise setting.
Just bought the bundle, and did a few short flights.
The persistent cockpit doesn’t seem to work for me, for some reason. It’s green in the tablet, but everything is back to default, and the battery is recharged when I come back to the plane.
Any tips on that?
Some things persist some do not. The trim seems to reset for example however fuel usage is retained and if you land with almost no fuel you will be empty at the next take-off. Not sure about the battery status.
Wasn’t there a project for the higher resolution panel for the Turbo Arrow? There was a mod like that for the NA Arrow but haven’t seen one for the Turbo.
This is the creator of the Arrow III high resolution mod:
https://flightsim.to/profile/alanlj44
And they commented in the mod that they are working on a version for the Turbos. But that was a month ago already.