Joystick axis swap order

Open forum for end-user questions about Wine. Before asking questions, check out the Wiki as a first step.
Forum Rules
Locked
micro
Newbie
Newbie
Posts: 4
Joined: Mon Jun 29, 2009 7:40 pm

Joystick axis swap order

Post by micro »

Hi. Using Wine I found myself in a weird situation. 4-axis flightsticks have different axis order in Windows and Linux. It appears that the throttle is named axis 3 in Windows, while yaw is the one that Linux names as axis 3, giving throttle axis 4 order. So, games like Fighters Anthology that have fixed joystick use can't operate well, while games like Simcopter that support assignment work around this problem. But I need a way to fix this through Wine, so that all games can work. Is there an option to swap the axes 3 and 4?

Thanks :)
vitamin
Moderator
Moderator
Posts: 6605
Joined: Sat Feb 23, 2008 2:29 pm

Re: Joystick axis swap order

Post by vitamin »

micro wrote:Is there an option to swap the axes 3 and 4?
Yes, see DirectInput registry branch: http://wiki.winehq.org/UsefulRegistryKeys
micro
Newbie
Newbie
Posts: 4
Joined: Mon Jun 29, 2009 7:40 pm

Post by micro »

Thanks :)
I will try this and post to this thread as soon as I have results.
micro
Newbie
Newbie
Posts: 4
Joined: Mon Jun 29, 2009 7:40 pm

Post by micro »

Well, i followed the command with the winedebug addition but when running Fighters Anthology, it doesn't give any directinput info for the joystick. I am going to test another game for sure, but is there a chance FA sees the joystick using another method and not directinput? Mind that it is an old game and there was a time we had windows and games b4 the DirectX era.

I am using Slackware 12.2 and Wine 1.1.8 precompiled from the Linuxpackages.net repository.

I know i know you will advise me to compile wine from source :)
micro
Newbie
Newbie
Posts: 4
Joined: Mon Jun 29, 2009 7:40 pm

Post by micro »

It's done!!!
I compiled latest wine (1.1.24) and it seems that the problem is solved by itself, without the registry directinput key. I deleted the key and all is still fine. I imported the key into a Crossover bottle registry and it didn't fix the problem, as I found out running FA in that bottle.

So it seems that the developers did something to the core itself.
Thanx!!!!

So your advice to compile the latest wine worked! Silly me :D
Locked