Corsair FG-1D Throttle Axis [Resolved-Hardware issue]

[davidpf051]

I can no longer map the Corsairs throttle axis to my flight controller. It worked fine in the past and all my other Milviz products work normally. I've tried uninstalling and reinstalling the product and that didn't work. All other control axis work fine. I am running it in P3dv4.5 (latest version) and using CH Pro Throttle. I move the throttle manually with the mouse, however, it will not map to the controller. Strange one!

[Slayer]

Are you using FSUIPC or any utility that changes the axis? Which mode are you using for controls? Directinput or RAW?

For some reason you aren't showing up as a FG-1D owner and therefore you can't see the support section. Did you purchase through us or ?

[davidpf051]

Slayer,

Purchased through you. In fact, I downloaded product from your site again to make sure I had latest version for reinstall. Not using FSUIPC. Stress that the odd thing is that it worked from original purchase when it first came out and then suddenly stopped. All other Milviz--and other--products work normally. In fact, I was flying the DHC-2 And Pilatus PC-6 yesterday with no difficulty. I set up the axis through the controls option in P3dv4.5. The other axis--pitch and roll--work fine. Just the throttle axis. I program it through the controls axis option and it shows up fine. It just doesn't move in the plane although I can drag it with the mouse. Strange one I admit.

[davidpf051]

Slayer,

Problem solved. Making sure to use direct input and then reload solved it. Funny that it only affected that controller.

[davidpf051]

Cancel my last, problem is not solved. Somehow it worked once. However, just started up again and same problem. I have tried using direct mode and raw mode. Same issue, throttle will not respond. Everything works except the throttle axis. AARRRGGGHHHH!!

[Slayer]

May I suggest making a new profile in P3D with working settings and then saving it? It may be something is not saving your control settings or overwriting them.

[davidpf051]

Slayer,

Finally solved the problem but it was subtle. Turned out to be a conflict between the CH Controls software and P3D programming. Hard to diagnose since it only affected the throttle axis. If it had affected all axis it would have been easier to understand. When you mentioned direct mode for the controls, I thought that had to be direct mode for both CH Controls and P3D. Once I tried leaving it out of direct mode in CH Controls and only in P3D, the problem went away. Can't say I understand why but now it works. Thanks for the help and notice you cleared up the support forums issue since I now see the FG1D forum. Glad to have the Corsair back operable. Looking forward to the Skyraider. A navy pilot I knew started his career in Skyraiders. Survived a cold catapult shot it one!

[Slayer]

Glad you're sorted. The Skyraider should be soon..