Puper Cherokee 180 - Control issues

[Nick - A2A]

Okay, thanks Rolf. Could I ask you to try another clean install as Lewis mentioned earlier (i.e. deleting any leftover A2A folders in "My Documents\Prepar3D v4 Add-ons") but this time run both the installer and updater as administrator by right clicking as selecting "run as administrator". Also, please can you turn off your antivirus and antispyware software before reinstalling. If you prefer, you can disconnect from the internet for whole install process.

Afraid I don't know much about Windows 10 (I'm still on 7), but I gather recent updates can cause issues as mentioned here.

Regards,
Nick

[Rolfspan]

Hi Nick,
I did as requested but no luck. We are still heading straight forward and are unable to turn. I tested other aircrafts and they turn without hesitation.
I have my MS updates turned to manual after having read Nick's comments in the ORBX forum some time ago. So I have not had any updates for a while.
I recall that some aircraft have a setting on their instrument panel that allows for Nosewheel steering. The Majestic Q400 comes to mind. Is there such a setting available in the 180?
Rolf

[Lewis - A2A]

Hello Rolf,

just to confirm the exact issue at this point is no control surfaces at all for you?

thanks,
Lewis

[Nick - A2A]

Hi Rolf,

Thanks for that. There's no special setting for nosewheel steering in the Cherokee: the nosewheel has a direct mechanical connected to the rudder system so should turn when you press the pedals.

just to confirm the exact issue at this point is no control surfaces at all for you?

Just lack of nosewheel steering on the ground Lewis. In other words, exactly the same symptom as if the latest Accu-Sim update wasn't installed, except this is obviously the first thing we verified.

I wonder if the issue lies deeper in the P3D installation itself. Rolf - please can you double-check the installed version numbers as shown here and here?

Cheers,
Nick

[Rolfspan]

Nick,
Your support is incredible.
Both numbers are 4.1.7.22841 -
Thank you very much.
Rolf

[Nick - A2A]

Well thanks Rolf but I still haven't managed to figure-out a solution!

The only other suggestion I can come up with at present is to try another verification of the SimConnect client. I know this was tried on the first page, but maybe worth another shot just in case.

If you go to the following directory...

C:\Program Files\\Lockheed Martin\Prepar3D v4\redist\Interface\FSX-SP2-XPACK\retail\lib

...Try right-clicking the "SimConnect.msi" and selecting "repair" ("Install" should work too.)

If that doesn't work, could you try disconnecting your rudder hardware and steering the plane with keyboard rudder inputs to see if there's any change in behaviour?

Cheers,
Nick

[Rolfspan]

Hi Nick,
I tried as suggested but still no luck. All other controls work except for the Nosewheel.
Sorry!
Rolf

[Nick - A2A]

Okay, thanks anyway. Can't think of anything else at the moment I'm afraid Rolf, apart from a clean reinstall of P3Dv4.1 itself. Two quick questions though:

1. Does the rudder move when you're taxiing?
2. Does the nosewheel move when you're in flight and apply rudder inputs?

Cheers,
Nick

P.S. Having thought about this a bit more, the symptoms are actually different to the ground physics issue introduced by P3Dv4.1 because in that case the nosewheel would still steer left and right, it just wouldn't alter the aircraft's course much.

[Rolfspan]

Hi Nick,
The rudder moves when taxiing but the nosewheel does not turn.
In flight the plane responds beautifully but the nosewheel does not turn.
Rolf

[Nick - A2A]

Thanks - that's what I assumed but just wanted to check. I've tried everything I can think of to reproduce the behaviour including enabling/disabling functions like autorudder, tailwheel lock and yaw damper but whatever I do, the nosewheel responds as it should with my P3Dv4.1 installation.

If I think of anything else, I'll let you know Rolf. In the meantime, hopefully someone else will have a good idea...

Best regards,
Nick

[Rolfspan]

Hi Nick,
Thank you for your help.
Rolf

[Lewis - A2A]

Hello Rolf,

can you let us know exactly how you are installing P3Dv4.1?

I'd wager a corrupt install at this point that your P3D is still in fact v4 and not 4.1 hence the bug.

Thanks,
Lewis

[Rolfspan]

Hi Lewis,
I deleted the P3D Client and replaced it withe version 4.1 when it came out 2017-10-11. The replaced version is 4.1.7.22841 -
Thank you for getting involved.
Rolf
p.s. I am heading out of town for a few days and will not have access to my computer but will follow the discussion via my IPad.

[Lewis - A2A]

Was it just the client or the entire install?

Did you first reinstall P3D as described here?
https://www.avsim.com/forums/topic/4951 ... nstallers/

It sounds like you installed without first a correct removal of the old one.

thanks,
Lewis

[Rolfspan]

Hi Lewis,
I updated v4 to v4.1 by uninstalling the client and then by installing the new client (4.1) as per instructions offered by Elaine. Thanks,
Rolf