Dual throttle assignment

[Navy Chief]

I have had my Warthog Hotas for a couple years now. Last night I decided to configure the control assignments on my Warthog throttle to operate independently as in the DC Phantom.

Prior to doing that, I made sure to calibrate my controller. All indications were correct. I made the assignments to my throttle as Axis 1 and 2.

Once I got in the sim, the Left throttle operated normally. The Right throttle animation moved forward approximately halfway and no further, nor would it move back.

Just hoping someone might have advice.on how to troubleshoot. NC

 

[jmig]

Make sure it isn't set somewhere else, like MSFS's controller settings, or a program like FSUIPC. If any other controller program is also using the throttle you can get conflicts.

 

[Navy Chief]

Thanks John,

I will.check. Although I do have FSUIPC, it is not installed. I made the controller assignments within MSFS. Although I don't see how it could happen; might other MSFS profiles have a effect? Pete

 

[azflyboy]

If you're not running anything like FSUIPC, I don't think the MSF controller profiles should matter, since it only uses one at a time.

Double check you don't have any of the throttle axis variations assigned to anything else (if something is assigned to "throttle axis" it can do weird stuff when independent axis are also assigned), and make sure each of the throttles move through the full range in the MSFS controllers menu.

 

[blanston12]

I had something similar with my X56 throttle. I remapped the throttle on the joystick to something else and then carefully reset and remapped all the buttons on the throttle, then everything worked.

 

[Navy Chief]

Well, much to my surprise, the throttles are working independently as they should (today at least). I did.absolutely nothing differently today than yesterday. I swear, sometimes I feel as though there are little gremlins, conspiring to screw things up for me on a daily basis! NC

 

[modelr]

Well, much to my surprise, the throttles are working independently as they should (today at least). I did.absolutely nothing differently today than yesterday. I swear, sometimes I feel as though there are little gremlins, conspiring to screw things up for me on a daily basis! NC

This happens to me all the time. I did 4 short, around the patch flights today, with a different aircraft each flight, and something different did not work on each one of them.

 

[delta_lima]

Glad you're sorted.

I'm dealing with a similar issue. I bought the DC Harrier, and needed to map the nozzle lever to the prop axis. After making the change, the sim mysteriously mapped the aileron axis to that same prop axis, introducing a completely control-controlling dynamic, making the Harrier unflyable. I can correct it, saving the settings, but they don't persist after I exit the sim and come back on a subsequent session.

Isolating the aileron to the proper axis and remapping nozzle to prop axis is something I have to every time now, until I fix it. I recall having a similar non-persistent bindings problem before, so I'll have to try and remember how I fixed that - but I recall it was something along the lines of saving the changes, going to the place in the sim directory where those were located, copying the key .cfg files and deleting some cache files then repasting in the controller settings. My changes persisted after that, until I made this most recent controller setting change.

Hope I can fix it, because it's getting old!

 

[modelr]

Glad you're sorted.

I'm dealing with a similar issue. I bought the DC Harrier, and needed to map the nozzle lever to the prop axis. After making the change, the sim mysteriously mapped the aileron axis to that same prop axis, introducing a completely control-controlling dynamic, making the Harrier unflyable. I can correct it, saving the settings, but they don't persist after I exit the sim and come back on a subsequent session.

Isolating the aileron to the proper axis and remapping nozzle to prop axis is something I have to every time now, until I fix it. I recall having a similar non-persistent bindings problem before, so I'll have to try and remember how I fixed that - but I recall it was something along the lines of saving the changes, going to the place in the sim directory where those were located, copying the key .cfg files and deleting some cache files then repasting in the controller settings. My changes persisted after that, until I made this most recent controller setting change.

Hope I can fix it, because it's getting old!

Hope it works. My main problem is that every first flight of a session, at a random time between 5 and 10 minutes after takeoff, the engine mysteriously dies. Ignition, fuel, mixture all set and on. Yesterday was the first time I was able to restart in the air, as I had enough altitude. At other times, my controller, whether stick or yoke is attached, just quits working, always resulting in a crash. Restat the flight, and it works again, usually for the entire flight. Getting to be so frustrating I rarely fly anymore. These problems first appeared when I was doing a test flight of the then new, F-5E from Venom.

 

[J.Case]

Hope it works. My main problem is that every first flight of a session, at a random time between 5 and 10 minutes after takeoff, the engine mysteriously dies. Ignition, fuel, mixture all set and on. Yesterday was the first time I was able to restart in the air, as I had enough altitude. At other times, my controller, whether stick or yoke is attached, just quits working, always resulting in a crash. Restat the flight, and it works again, usually for the entire flight. Getting to be so frustrating I rarely fly anymore. These problems first appeared when I was doing a test flight of the then new, F-5E from Venom.

Sounds alot like you're stumbling across some kind of DRM. IF this is the case - a reinstallation of the aircraft in question might do the trick (WAG from half a day away) - just a suggestion..... but it won't cost you anything but a little time

 

[modelr]

Sounds alot like you're stumbling across some kind of DRM. IF this is the case - a reinstallation of the aircraft in question might do the trick (WAG from half a day away) - just a suggestion..... but it won't cost you anything but a little time

Thanks for the advice, except that it happens with EVERY plane, about 10-15 that I have flown since it started, and the sim has been completely uninstalled and reinstalled in a different location.