Problem with X-55 Rhino throttle output

[venom1]

Hey guys, got a question for you regarding the X-55 Rhino throttle. I am pretty much a noob at this whole throttle programming business, so excuse me if this is a dumb query with a simple answer (hopefully that is the case!). I have had a peruse through the threads and can't find an issue like mine.

 

For the life of me I cannot get the "throttle" component of the throttle to work properly. When I first installed it, it asked me to do the windows calibration. It looks like from the outset it appears to map the x axis to the left throttle and the y axis to the right throttle. I can map key commands to the throttle and when I test them in the programmer they work fine, however when I get in a game the throttle ends up over riding the mapping with the x-y input.

 

If I push the throttle forward it has the same input as if I had pushed the stick fully up and to the left (diagonal) which seems to equate to x and y inputs at the same time. If I unlock the throttle so I can move each one individually then one does pitch and the other roll which proves the x-y assignment. I have tried both Hawx and DCS and it has the same effect in both. Every other button and switch seems to work perfectly.

 

I am running Windows 7 64 bit if that makes a difference.

 

I cannot for the life of me figure out how to stop this and I am at my wits end. I have had a look online and found nothing. Any suggestions on how to stop this? Would hate to think I have spent all that money for nothing. Hoping someone out there can point me in the right direction.

 

Cheers in advance,

 

Sam :thumbup:

[BigDuke6ixx]

You have some conflicting axis you need to clear from the DCS controls settings. I would clear all axis and reassign again.

[venom1]

Would that be the case even though I have not messed with the default ingame settings? It is doing it in HAWX as well.

 

Nonetheless, I appreciate the feedback and I will go and see if that may be the problem.

 

Cheers,

 

Sam :)

[StandingCow]

Would that be the case even though I have not messed with the default ingame settings? It is doing it in HAWX as well.

 

Nonetheless, I appreciate the feedback and I will go and see if that may be the problem.

 

Cheers,

 

Sam :)

 

Yep, it is absolutely the problem, I don't know why it is default like that... but every new aircraft you have to unbind the axis from things it doesn't belong to.