Dual throttles not calibrating properly

[strykerpsg]

Anyone else using actual dual throttle configurations? I posted this issue in the Aerosoft forum and don't recall having this issue before, but it seems that only my left throttle moves the full range of motion, while the right throttle moves only in the center range of motion for it's throttle limits. How do you fix this? I have run calibration multiple times and they both show full range of motion but don't utilize it in the game.

I have given consideration to purchasing FSUIPC, but honestly know nothing about the full version versus the free version advantages. Does anyone have a workaround to get both throttles synced together through the full range of motion for the throttles? I'm open to anything at this point.

Thanks in advance,
Matt

BTW, running the Warthog HOTAS.

 

[gigabyte]

Well I will put a plug in for upgrading to the full version of FSUIPC, it is worth every penny and then some. There are plenty of added features besides just additional control over button and Axis assignment, some realy neat weather control, and a slick auto-save function, plus some great additional control over calibration. Aside from that there are only two things I can think of, one is to mess with the in-game Axis settings and see if you can calibrate from there any better, the other thing you can try is to change the USB port you have the controller connected to. Changing the cable to another USB port will reinstall the friver on that port and it will sometimes fix the weirdest little issues.

 

[strykerpsg]

Gig,

Tried changing the USB port...nothing. I tried to tweak the calibration settings in game...nothing. So, final option is looking to be a purchase of FSUIPC. At their webstore's description, it looks like a great utility but can you or anyone else that uses FSUIPC tell me how much better of a tool it is for FSX and are their FSX titles that don't support FSUIPC?

Matt

 

[Skyhawk_310R]

There is really nothing cosmic about a dual throttle. Each lever has its own axis that allows it to control one virtual item on an FSX aircraft. You merely assign that axis to one function via using the built-in FSX controller configuration menus. There are enough axis available to FSX to allow you to assign one axis to each of these functions:

1. Roll
2. Pitch
3. Yaw
4. Left engine throttle
5. Left engine prop condition
6. Left engine mixture
7. Right engine throttle
8. Right engine prop condition
9. Right engine mixture
10. Left toe brake
11. Right toe brake

If one of these axis are failing in the game, then it is most likely one of two causes:

First, the physical controller has a failure, most likely in the servo that converts the mechanical movement to electrical signals used by FSX to render the virtual control.

Second, the axis has not yet been assigned to the FSX function you are wanting that lever to control.

To isolate the first cause, use the built-in controller calibration in FSX to identify and measure the range of motion for the physical controller lever that is having the problem. If you see the red bar and crosshair for that lever moving in its intended range of motion, then the controller lever is working and that is not the problem.

To isolate the second cause, you can open up the FSX controller configuration file using a text editor and inspect all the assignments to ensure that the lever is, in fact, assigned to that desired function. This configuration file is located in the same location as your FSX.cfg file which varies from one O/S to another.

Ken

 

[strykerpsg]

There is really nothing cosmic about a dual throttle. Each lever has its own axis that allows it to control one virtual item on an FSX aircraft. You merely assign that axis to one function via using the built-in FSX controller configuration menus. There are enough axis available to FSX to allow you to assign one axis to each of these functions:

1. Roll
2. Pitch
3. Yaw
4. Left engine throttle
5. Left engine prop condition
6. Left engine mixture
7. Right engine throttle
8. Right engine prop condition
9. Right engine mixture
10. Left toe brake
11. Right toe brake

If one of these axis are failing in the game, then it is most likely one of two causes:

First, the physical controller has a failure, most likely in the servo that converts the mechanical movement to electrical signals used by FSX to render the virtual control.

Second, the axis has not yet been assigned to the FSX function you are wanting that lever to control.

To isolate the first cause, use the built-in controller calibration in FSX to identify and measure the range of motion for the physical controller lever that is having the problem. If you see the red bar and crosshair for that lever moving in its intended range of motion, then the controller lever is working and that is not the problem.

To isolate the second cause, you can open up the FSX controller configuration file using a text editor and inspect all the assignments to ensure that the lever is, in fact, assigned to that desired function. This configuration file is located in the same location as your FSX.cfg file which varies from one O/S to another.

Ken

Ken,

Agreed there's nothing cosmic about assigning the controllers, just not doing something not so obvious. I have checked the controller using the FSX calibration, both axis' work fully.

I like the solution of the second cause and will look at that one next.

What i noticed is when I assigned the left throttle as the primary throttle, ie not engine 1, it has full range of motion. I then assigned the right throttle as engine 2 throttle and it has the limited motion. This is also what happened when I assign one controller as engine 1 and the other as engine 2 throttle. just very frustrating.

More to follow.

Matt

 

[Skyhawk_310R]

Matt,

I am not sure, but by reading your last post, I think I may have identified the source of your issue.

When using controller axis to control multiple engines, you have to assign the axis control to engine 1 and 2 and that means you do NOT assign any axis to control merely throttle, propeller, or mixture axis. In other words, FSX allows you to assign one axis to control all the throttle, prop, or mixture controls, or FSX allows you to assign a single axis to the control of a single engine. In fact, FSX allows you to select individual control for up to four engines, but you have to have an available axis for all the desired control inputs.

So, be sure that you are specifying the controls for the left engine to the throttle, prop, and mixture controls for engine number one, and then specify those functions for the right engine to engine number two. And most important of all (and where I think your issue lies) do NOT assign any axis at all to what FSX labels as "Throttle axis," "Mixture axis," and "Propeller axis."

Ken

 

[strykerpsg]

I still couldn't get the throttles to work correctly and did as Ken suggested, where I assigned an axis to Engine 1 and the other to Engine 2. Not usre if anyone's noticed this or not, but the Warthog assigns only the right throttle as an axis, the left throttle is assigned a rotation prefix, not sure if that matters or not.

I did break down and purchase FSUIPC and I have to say, it's a bit intimidating. Is the only way to access FSUIPC is during actual gameplay while FSX is open?

Anyway, since I have the FSUIPC, guess I will just focus now on using FSUIPC. Anyone know how to just program 2 engine throttles instead of 4? I will print the accompanying pdf file in hopes that it sheds more light.

Matt