Throttle not responding to any controller input

[Dental1]

Hi
I just installed the c182 in p3d v3.4 and everything works fine except the throttle. It does work with the mouse but thats it. I use the saitek pro tpm and the prop and mixture work fine but not the throttle. It's calibrated and there are no conflicts with other devices. I also tried mapping throttle to hotas warthog throttle and nothing. These devices work perfectly with all other aircraft. All sim connect files have been installed. What am I missing.
Thx Lee

[Oracle427]

Firstly, download and install the current patch. http://a2asimulations.com/forum/viewtop ... 21&t=41279

Without it, you are missing all the latest and greatest features.

Next, ensure you are mapping to the Throttle axis and not Engine 1 Throttle.

You can also try to open up the A2A Input Configuration for your 182, found in the A2A Simulations folder of your start menu. You should be able to map the throttle axis in there. Some of the A2A customizations that override the default simulation conflict with standard mapping methods. I don't believe the throttle axis is one of them however.

[Nick - A2A]

Lee - if you can let us know how you're assigning the throttle (i.e in the P3D controls menu, FSUIPC or other third-party software) it may help find the culprit. Hopefully running the Accu-Sim update as Oracle suggests will fix it though.

You can also try to open up the A2A Input Configuration for your 182 [...] You should be able to map the throttle axis in there.

Just to avoid any confusion, there's actually no option in the input configurator for the throttle axis.

Cheers,
Nick

[Dental1]

Hi
I am just using the p3d controls menu and not fsuipc. And mapping to the plain throttle and not engine 1 throttle. I just ran update and still the mouse is the only device the moves the throttle. Prop and mixture work fine
Thx Lee

[Nick - A2A]

Maybe still worth checking in the A2A Input Configurator Lee, just to make sure your throttle axis isn't assigned to something else in there (e.g. elevator trim or something).

You could also try deleting the entire contents of the following two folders to 'reset' the aircraft and any assignments.

My Documents\A2A\P3D\Cessna182
My Documents\A2A\FSX\Cessna182

Nick

[Dental1]

Hi
I erased those files as recommended and restarted. Something is holding the throttle back. When I push the I see the aircraft bob slightly but throttle doesn't move. I can drag throttle fine but when I try the mouse wheel ,same result as saitek throttle. I even connected a ch throttle quad with same results. Sorry this is so complicated but I really hope you can help.
Thx Lee

[Nick - A2A]

Hmm - it really sounds like a control conflict, yet you say the throttle axis works normally in other aircraft...

Have you checked the status of the aircraft in the maintenance hangar to try and rule out any SimConnect issues?

Also, is it the proper P3D version of the Skylane which you've got installed?

Thanks,
Nick

...One other question: do you have any any Saitek drivers and/or software installed which could be causing a conflict?

[Dental1]

Hi Nick
I think I know what the problem is. I use the flight1 tech g1000 pro hardware and software. After doing some reading it appears that a2a is not compatible with this software. It's too bad, there are no aircraft like the a2a series for really learning and experiencing. Since i spent about 5000 dollars for the flight1 tech g1000, it's hard to put it aside to be able to use the a2a aircraft. Maybe some time soon it will be possible.
I really appreciate your willingness to help me
Thx Lee

[Nick - A2A]

Yeah, I'm afraid it might be pretty tricky to get the F1 TECH 1000 to work with the A2A 182 Lee - both are pretty specialised products in their own right. A2A have added support for the F1 GTN GPS units, but I'd guess you'd need to turn to F1 for advice on integrating the G1000 hardware. I don't recall posts here from anyone who uses it successfully with the A2A products.

Cheers,
Nick

[Lewis - A2A]

Yes, the F1 product is solely for the default FSX code, because we use our own simulation engine to get around inherent FS simulation limitations the F1 product will not work correctly with our 182.

thanks,
Lewis