18 replies to this topic

[Ayenn]

The post title pretty much says it all. I get button recognition but the actual throttle slide is not working. It works in other games but not MWO.

Am I missing something here?

Thanks!

[Foust]

Have you tried rebinding the throttle axis in MWO to the throttle?
On the X-55, is the throttle treated as a separate joystick?
Have you sacrificed a locust to the mech gods?

[Warblood]

Does ur X-55 come with software like Logitech's does?
If so you can try to config. a profile within the software an tie that to MechWarrior.

[Ayenn]

Foust, on 05 July 2014 - 01:40 PM, said:

Have you tried rebinding the throttle axis in MWO to the throttle?
On the X-55, is the throttle treated as a separate joystick?
Have you sacrificed a locust to the mech gods?

If you are talking about creating a unique mapping in the actionmap file... I poked at it but I do not know what the map code would be and I cannot find any information on that or what it would be. This makes the most sense as this is how the key/stick mapping is generated by the MWO client.

It looks like it is a separate joystick. the actual control stick is designated Joy0 and the throttle is designated joy1. This tells me there should be some way to bind the joy1 axis in actionmapping.

Every time I use a locust is it not a sacrifice to the mech gods? I undertake the piloting of the Locust with this in mind.

Locust for the Mech God!

Warblood, on 05 July 2014 - 01:49 PM, said:

Does ur X-55 come with software like Logitech's does?
If so you can try to config. a profile within the software an tie that to MechWarrior.

The X-55 does come with configuration software like my Logitech 3D Pro. I have tried to dink with configuring it via the H.U.D. software but, after an unmeasured amount of time (more than an hour less than 4 hours) I was not able to find a way to configure the throttle for MWO with it.


Thank you both for the replies!

[Foust]

I wouldn't mess with the actionmap file, sounds as if you have already tried binding it from the in game options?

You could also try EvilC's UJR program linked in my sig. Should let your setup show in MWO as a single controller.

All that said, MWO has been very good at handling multiple joysticks through the in game interface. In regard to axis assignments anyway.

[Ayenn]

So I looked at EvilC's UJR program. there are two problems with it. The first is the x55 throttle itself has 32 "buttons" (I actually have almost all of them bound to MWO functions), which isn't including three dials. The second is EvilC's UJR program does not recognize the X55 throttle. It throws up an error saying that it is "not configured/recognized/sxet up/made of yellow Twinkies cake" or something of the like.

And that is where it is strange. MWO recognizes every single button on the throttle but does not recognize the throttle function itself.

I know the throttle itself is fine. I use it with Star Citizen's Dog Fighting Module and it is a beautiful thing to experience.

I see that several people have visited this new thread or are looking at it already. I hope I can find a solution and I can't imagine I am the only person having this problem as it seems to be an issue native to support specifically for the x55 HOTAS in MWO. Perhaps this will become "the" x55 work thread for the lack of one already.

[Foust]

Alright next few questions.

When you are trying to assign the throttle in MWO do you have the two throttles linked such that they move at the same time?
If so could you try unlinking the halves and try assigning throttle to just one half?

[Ayenn]

I tried disabling each independently AND both (in case of code shenaniganry... stranger things have happened). I am coming to the conclusion PG has not actually added any kind of support for this HOTOS yet. This seems to be a case where in it might be picking up on another HOTOS driver link or even a dual stick setup but it cannot see the throttle slider or, because there are actually two, it may not know which to activate.

[Foust]

You did that in the X55 software?

Just to beat a dead locust a bit more, have you physically uncoupled the two halves and tried binding them in game by moving only one?

From what I gather the throttle reports x axis on the left half and Y axis on the right. if they are moving at the same time maybe cryengine just ignores it?

[Warblood]

found this... don't know if it will help


when he pushes forward on the stick he moves forwards.

he is also left hand driving n I assume he has his mouse in his right hand?

like I said not sure if it will help.. but if you do figure it out make a new post with your ur settings for others to check out.

[evilC]

Ayenn Destiny, on 05 July 2014 - 04:34 PM, said:

So I looked at EvilC's UJR program. there are two problems with it. The first is the x55 throttle itself has 32 "buttons" (I actually have almost all of them bound to MWO functions), which isn't including three dials.

UJR supports 32 buttons.
To map all 32 buttons straight through takes 4 clicks (Use the Auto Configure option).
Yeah, UJR would not support any of the dials, but as long as the game can recognize input from multiple sticks, you could bind to the physical stick not the virtual stick.

Ayenn Destiny, on 05 July 2014 - 04:34 PM, said:

The second is EvilC's UJR program does not recognize the X55 throttle. It throws up an error saying that it is "not configured/recognized/sxet up/made of yellow Twinkies cake" or something of the like.

The only error dialog it "throws up" is to do with selecting the vJoy ID.
This is NOT the same as the ID of your throttle.
It is perfectly possible to select a nonexistent joystick ID and it will never throw an error. Are you perchance using the "vJoy Stick ID" selector instead?

If you still have problems, please feel free to post on the UJR thread.

[Sentinel Stone]

I too have a new x55 throttle and had to separate or deadzone out one of the x and y axis to each half of it with the software. Looks like by default both axis are fully mapped to each half of the throttle. This fixed all my problems with its function in full or half range. It used to function in reverse order no matter what I did.

Edited by Clan Merc, 26 August 2014 - 12:49 PM.

[Lotan]

im having an issue with my rhino i am unable to map anything to the trigger

[AKNINJA]

Any updates to this? Can't get throttle to work in MWO with a X55.

[Rardain]

My apologies firstly for reviving what pretty much looks like a dead thread, however, after doing a lot of searching on a solution for this it looks like no-one has come up with a satisfactory remedy.

I was all set to give up on this when I noticed that when trying to set the throttle axis the software was detecting the two rotary switches on the throttle (Joy2 Rot X and Joy2 Axis Z) instead of the throttle axis itself. I temporarily assigned these rotaries to the torso twist and pitch fields and tried the throttle again and this time it worked.

A little later I discovered that if you unlink the throttles and use just one of them ( I used the left throttle which is Joy2 Axis X) the software correctly detects the throttle axis. All you have to do then is ensure Full throttle is selected and Invert throttle.

[Napoleon_Blownapart]

welcome fellow joystick user

Edited by Gorantir, 29 December 2015 - 08:34 AM.

[Rardain]

Thanks Gorantir...last time I played MW was back in the days of MW4 Black Knights and Mercs so looking forward to trying this online

[M A S E]

Ayenn Destiny, on 05 July 2014 - 08:50 AM, said:

The post title pretty much says it all. I get button recognition but the actual throttle slide is not working. It works in other games but not MWO.

Am I missing something here?

Thanks!

Paul made a note of this in the forums about a couple functions not being completely coded into the game. For example Z axis is a 1/0 and has no analog function yet..

Video games have been made since the 80's and joysticks have been around before Mechwarrior ever got its first title so I don't understand how difficult it is for PGI to write once of the most basic pieces of code. You're stick isn't broken, Paul is.

[Rardain]

Being brand new to playing MWO I ran into the exact same problem as the OP...if you look at the date of the original question you will see it is July 2014, however, several people since then have also posted requesting info on how to cure the problem.

I think the issue is because the dual throttles on the X55 are confusing the software, maybe it only wants to see a single axis input but with both throttles linked it will be getting both the X and Y axis inputs.

As I said earlier - fix appears to be to simply physically unlink the two throttles and use one or the other to register the axis. The Throttles can then be linked again and will work together correctly.