PA-28 Warrior II

I've also seen this. For what it's worth, after reading this topic I double checked that I cannot hear anything on Nav 1 in the Warrior (I can't), but then I loaded up the stock C172 in the same place and confirmed I can't hear anything on Nav 1 in that, either.

@nsconductor said in Stall: I came here to write on this issue, glad to see I'm not the only one. So, no response from the JF team on this issue? Considering the warrior is a training aircraft, it's important that it can simulate real world maneuvers such as stalls... Some acknowledgement from the JF team in wether the aircraft being unable to stall is intentional or not would be nice. Have you been in touch with JF support? If you raise a ticket with us we can see if we can get to the bottom of it. If the issue is not affecting every user it is not easy to resolve without more info. You'll see that Paul has replied about this further up the thread back in July.

@retiredman93231 Thank you, that has worked.

Thanks for the update, that's what I was looking for. As you said, none of the issues is a deal-breaker, love flying the Warrior.

https://flightsim.to/file/20116/vr-friendly-prop-mod-for-jf-warrior-ii

@starflexthe2nd, The inability to recharge the battery from the EFB is a known bug caused by MSFS... But, your battery should be getting constantly charged by the Alternator, if it is ON and working correctly. After starting the engine, increase the throttle to 2000 RPM then verify that the Alternator Ampere gauge shows current flowing. With all of the lights and the fuel pump ON it should be very near full scale.

The GPS100 has never had input functionality, something to do with MSFS's programming. It's pretty much display only. For the external lights, they should be tied to the Anti Collision Light switch, if you have the current Warrior. At one point, they were oddly controlled by the cockpit radio light, but that's been fixed with 0.2.0.

@xaxjon I can help with 2 of those: (3) The ident button not working is a msfs limitation. There's no way (I believe) for the PE client to know when the button is pressed. (6) Re your last point, on the EFB, make sure auto fuel selector is off. In case you are unaware, to show the EFB use the I/COMM switch next to the DME source switch.

I use the Logitech multi panel along with spad.neXt which allows me to adjust the trim wheel. I have each subtle detent on the wheel equal to 1% of trim movement.

@fedar92 said in How to remove the PA-28 Warrior II static plane model from spawning in parking at GA airports?: @steenation you have to edit the "aircaft.cfg" warrior file and find this line: isAirTraffic = 1 Change 1 to 0 Ok, I did this edit and it seemed to work. Been around a few GA airport and haven’t seen the Piper static spawn since. ~ Thank you

Ok... Out of ten flights I had one now were the end screen came up successfully after shutting down. Thats indeed weird. No other change on my side and same steps as usual. Cheers T.

I f***ing love this plane… this a so good… this is real life like. He accidentally pulled a cb and caused the problem. This is only possible because the JF team put so much details in this study level plane.

@sender46 Thats very interesting, I never thought of the weather side of things. I did a fair bit of experimenting yesterday to try and pin it down and came to a different conclusion. Which may mean more than live weather might be at play here. I found this only happened when I had enhanced airport third party scenery installed, in particular EGNH. Also one location on this airfield had a different effect on the engine. It wouldn't start no matter what I tried. Even choosing ready for takeoff. Remove the third party scenery enhancements and the problem disappeared. So it may not only be the weather. But as you think, I am more inclined to think it's an MSFS issue.

@kengou OK yes you have to look carefully - the movement is subtle. In reality it is a lot faster and noticable.

@paulcoy There are mentions of autopilot changes in the changelogs for the Arrow, though I don't see any for the Warrior (it might have been before the warrior was released)

I had the same problem till I ticked the Reverse option in control assignments for left and right Brake. This bought it all back to normal for me

@rene-feijen The external analog elevator trim axis direction assignment on all of the JF MSFS PA28 aircraft for the Saitek Cessna Trim Wheel controller appears to be reversed with respect to its assignment on stock aircraft since SU5. If it set correctly for other aircraft turning the external trim wheel nose up has has the opposite effect in the JF aircraft. It did not change with the latest JF update. Something had to change in SU5 to cause this to happen because one setting worked for all previously. I have found it necessary to create a separate controller profile for the JF aircraft. However a trim switch assignment for nose up and nose down works as expected.