With mine, I usually don’t have full functionality until I ESC and restart. The GPS buttons don’t work and the Carb heat slider won’t move. But that’s been true for over a year, and several re-installs.
When I first installed it, I did what I normally do. Copy it from the Community folder to my repository of addons, renamed the folder to include the version number, then use the addon linker to let MSFS see it.
When I did that the plane wouldn’t unlock, and the yokes remained in full left deflection.
When I renamed the folder back to the original it worked properly.
That’s the only issue I have had with it.
I don’t use the linker, I have very little in my community folder to begin with, fsuipc, kap140, gns530, and my current airplane, in this case only the Warrior. I’ve uninstalled the Warrior, removed all of it, going to run MSFS completely vanilla first, then exit and reinstall the Warrior only. Add the others back after I see how the Warrior works.
Short flight with nothing else installed, and… success!? Still a bit of oscillation, but nowhere near like it was before, about like I remember from a long time ago, so I think the reinstall with nothing in the community folder… worked? Sure hope so, going to try after putting the other items back, but not today.
Thanks to all of you for your help, particularly hobangerik and Seven7Tango. Happy flying!
3 Likes
That’s great news!
1 Like
I was wondering if you had an issue with FSUIPC…
I’ve had issues trying to land in the soup with no visibility managing to keep a smooth approach, but, I’ve never experienced what you’re describing and I fly the Warrior all the time.
2 Likes
That’s great to hear! Happy landings! 
2 Likes
So in weird but good news, after my last post, I tried another flight with the Warrior, and it was awful, one of the worst for the windshield wiping VSI. So I decided to reinstall and try big brother Arrow III, also not a good experience at all.
But then I decided I liked too many other things about the Warrior, and someone in their forum gave me a tip to ‘cheat’ the system. I couldn’t get the cheat to work, but for some reason, with the Arrow III installed, the little Warrior works almost perfectly, windshield wiping gone, just some adjustments on the trim wheel, and life is grand, for 2 flights so far anyway.
1 Like
Something strange: I trim the aircraft then engage AP and as soon as I switch on Alt hold, the aircraft climbs with 700 ft/s. Why is that?
Thats odd, I have a key/button assigned to altitude hold and it works fine, you could try that.
What about this ‘up and down’ behavior?
Haven’t seen anything like this in any other aircraft.
Tried other planes with same flight settings, they smoothly raise and lower the nose a bit.
But these ones, bought the bundle, they just ‘jump’
Any ideas?
Doesn’t do that for me… Just took a flight in the warrior last night. Flies great. Must be a binding issue or mod conflict on your end.
2 Likes
Same with hardware key.
I found that with a hardware AP VS down key I can reduce the climb and bring it to zero. This works until my next flight. Not sure why VS commands a 700 ft climb anytime I press Alt hold.
And, if I deactivate state saving this does not happen.
Maybe sensitivity settings of your controller need tweeking? I’ve different profiles for nearly every aircraft.
1 Like
Suffered from this myself, specially the Turbo Arrow and the Warrior. See the pitch jerk topic on their forum. After i bought the C337 from Carenado that plane had the same issue.
However, SU10 largely fixed this due how thermals are done. Now for me they fly as they should again.
If SU10 did not work, a workaround is to fly with non live weather, but use a preset.
1 Like
Just took the non turbo for a spin and yes, seems to be fixed 
Tomorrow I’ll try the turbos.
Thanks guys!
Turbo Arrow is not remotely pitch sensitive - in fact takes a fair bit of movement to do anything in pitch. Then again it was like that before SU10, so I presume what was fixed was some rogue controller…
Thermals are still horrible ,similar to the vid I posted in the Hawk thread, just a bit easier to deal with at 1/4 the speed 
In the Warrior always switch off the AP as part of your shutdown before exiting a session. Quitting with the AP running will cause all sorts of unpredictable randomness because of state saving next session.
Also it is better to leave the AP off until you are airborne for some reason.
1 Like
Presumably it’ll start doing horrible things to trim if you don’t, although there’s not really much it can do in the Warrior at least.
Hi, I am experiencing a couple of issues with the warrior, Firstly the performance seems unrealistic, flying from my home airport to do circuits I can reach circuit height much earlier than in real life, is this common? (also possible that the performance of my knackered old rental in real life has degraded significantly)
I also found that when taxying with a moderate 12-15knt crosswind hitting the portside, it took almost full right rudder to keep a straight track, felt like taxying a free castoring taildragger, not an aircraft with nosewheel steering!
Finally, as a small point, turning off the fuel pump on pre start checks causes the fuel pressure to return to zero?
1 Like
Regarding the first point, there have been several users in this thread that have mentioned that it seems overpowered at the moment. Hopefully this is looked at by JF at some point because it is unrealistic in its current form and takes a little away from what is an otherwise fantastic rendition of the Warrior.