PA-28 Warrior II

@chalwk Better missing it now and learning where it is rather than not being able to find it when you really need it! (In the unlikely event of a virtual cabin fire :P )

@walterbeech I've submitted a ticket for this, they're aware of it for all the Arrow variants.

Martyn just replied in another thread that JF is updating the PA-28s next week and addressing this issue.

@skjjks Which specific autopilot functions aren't working? I am successfully using the default mappings for setting Heading, Course and Altitude using the rotary dial. I don't have any of the toggle switches mapped to autopilot functions... If you do want to map the toggle switches, I recommend using only SET commands or ON/OFF commands, and not TOGGLE commands. SET commands and ON/OFF commands are intended to be used with toggle switches. TOGGLE commands should only be mapped to momentary buttons, and never to toggle switches.

@dillet74 Not at all.

@delta558 said in Little things to add for the next update for realism:
Mention flight dynamics and there is a wall of silence. It's been like that from the start, and I see no sign of it changing unfortunately.

Oh, that really saddens me....I had be hoping for improvements to the flight model.

Alright, thanks for the input guys! I'll make note to start cross checking it more often on my end.

I did eventually change from Modern to Legacy Cockpit Interaction and that solved the issue of being unable to unlock the primer.

@vcapra1 @Sender46 You were both right. I've unbound the switch, now it works fine. Thanks for your help.

@walterbeech

I'd add that a centre marker on the rudder trim would be very useful.

If it doesn't have one in RW... I'd be reaching for the Tipex.

@katchaplin @RetiredMan93231
Yes, it's the IC switch! Thank you, gentlemen!

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.