Try turning the plane towards your first GPS waypoint. Once it’s orientated to the direction of your waypoint, NAV GPS steering should take over. In previous iterations of MS Flight Simulator, NAV GPS steering would work no matter which way your plane was facing, but with the Working Title updates you need to have your plane facing within (I think) 45 degree angle towards the active leg for the NAV GPS steering to engage.
Generally with the Arrows I find it better to pretty much manually start following the flight path before engaging NAV.
Also make sure you have activated the current leg. If for some reason you overshot the last waypoint without passing over it the AP can still think you are on the past leg and never lock onto what you think is the current waypoint.
Final hint with the Arrows, always shutdown the AP after landing as state saving , at least in the past, has been known to do weird things next flight if you do not.
Is this plane like others who’s in marketplace dev/testing limbo? I got the marketplace version and it seems like it’s an older version: 0.5.1. compared to the much more recent 0.5.6 on the JF website.
0.5.1 is pretty buggy…
Heard from JF support. They are working on a Marketplace update in a couple weeks. Just need to be patient as these 3rd party devs deal with the new pipeline process and are trying to catch all the changes from the AAUs.
I feel for them, it’s been a lot of changes to the sim.
The new turbocharger logic coming with the next piston engine update in the sim is going to be excellent with the Turbo Arrow. I can’t wait for that to be implemented, eventually (I hope!), so I no longer have to lean during climb.
The updates are out.
I took the Turbo III up for a quick flight and during the climb manifold pressure remained constant, but I still had to reduce mixture during the climb otherwise the engine would sputter out. I was under the impression that turbocharged pistons kept the mixture full rich during climb and only leaned when reaching cruise altitude. At least that’s my experience with the Flysimware C414. Do real life Turbo Arrows need to be leaned during the climb?
This is incorrect on our Turbo Arrow in the sim. It’s a core sim limitation, although several developers like FSW and Black Square have worked around it with custom code now. The mixture should remain full throughout the climb.
The next sim update will include piston engine improvements including proper turbocharger manifold pressure with altitude. So Just Flight won’t have to add any custom code once that’s in the game.
Well, up to critical altitude, at which point you do need to adjust mixture above that.
beacon light still not working… wow that is lame (Turbo Arrow III)
It’s working for me with this latest update, so you probably have a conflict somewhere.
Personally, I’m now having trouble with the updated GPS and autopilot that doesn’t want to engage NAV mode.
reinstalled now works fine… must have been something on my end sorry
Are you trying to use NAV mode to follow the GPS flight plan? Are you using the GNS 530, and if so, is the CDI needle/bar centred when you attempt to engage NAV mode?
One of the limitations/features of the WT GNS 530 is that you can’t engage NAV mode if the CDI needle/bar is out of limits, i.e. is at the extreme left/right deflection position.
Martyn - Just Flight
Hi Martyn,
Thanks for chiming in. I’m aware of how to use the WT GNS units, I didn’t mean to imply there was a problem with your implementation, but more to do with my hardware/peripheral setup and possible conflicts.
The problem lies with the autopilot mode selector switch. Every time I tried to change it from HDG to NAV or OMNI, the switch clicked back to HDG. I’ve got it working fine in the cockpit now using the mouse, just need to isolate what causes the conflict, as it worked OK previously with my logitech panels and spad.next.
Thanks for the response though. BTW, any info on when to expect the Hawk update?
Same thing here. All three planes. AP on and locked to HDG mode when spawned. Can’t select any other nav mode. Did not happen before these updates and I’m not using any binding software like spad or A&Os, just default bindings.
Planes are currently bricked for me and unflyable. I have a ticket open with JF for this also, any insight u might have Martin is appreciated.
-A
99% of the time, this is a binding conflict. Create empty control config and work from there.
How do you clear spark plug fouling while on the ground?
I couldn’t start the engine. Repair engine does nothing for the spark plugs on my install
Only way I was able to clear it was by disabling engine failures, flying up to altitude, re-enabling failures and allowing the engine to start/stop/start by windmilling until it cleared.
I think that you are supposed to crank the engine with throttle full and mixture cutoff/full lean for about 30 secs. Sometimes works for me.
Rev the engine at high RPM for a few minutes. At least this works on the Comanche.
Hi…your not the only one. I’m experiencing the same problem.
I’ve had the same problem
It’s a real PITA🙄