Xbox 360 arcade stick wireless

[lasborg]

I have the xbox wireless dongle and have no problem using a regular x360 controller with fs-uae. But my Hori Tekken 6 arcade stick is not identified.

It is identified in windows as "Arcade Stick (Xbox 360 Wireless Receiver For Windows)", and I tried making a custom ini file called:
arcade_stick_xbox_360_wireless_receiver_for_windows.ini
(not sure this is the right way do do this)

but it does not work, can anybody help me.

I use fs-uae version 2.5.40dev and I use fs-uae portable (not installed)
and I am running windows 8.1 (x64)

[FrodeSolheim]

Does the joystick appear in FS-UAE Launcher -> Settings -> Joysticks?

The easiest way is to configure it there (double-click the joystick entry).
(Remember to delete the manually created arcade_stick_xbox_360_wireless_receiver_for_windows.ini first)

[lasborg]

No it does not show up in settings. (The regular controller does)

[FrodeSolheim]

Can you start FS-UAE with the joystick connected, quit FS-UAE, and send Cache/Logs/fs-uae.log.txt to frode@fs-uae.net?

[lasborg]

Will do

[FrodeSolheim]

Got the log, according to FS-UAE/SDL2 (I expected this, but wanted to be sure):

num joystick devices: 0

Does the joystick device work in other software/game/emulator on your computer?

[lasborg]

Just tried it in my windows 10 machine. same problem.

The joystick works in retroarch.

[lasborg]

Hi again Frode
Is there anything I can supply you with in order to get it to work?
Retroarch screenshots or anything else?

[lasborg]

Been trying to mess arround with an ini file for the controller, but can't get it to work.

Am I correct in assuming that if a controller is not supported natively, it then needs an .ini file with the same name as windows reports it, and that it should be put in the CONTROLLER folder.

Is there any other ini-files that needs changing?

[FrodeSolheim]

@lasborg No, there is nothing you can do right now. If FS-UAE (SDL 2) does not see the controller at all, no input config file is going to change that.

I *may* have something you can test in the next development version (I can try to force SDL2 to ignore XInput and only use DirectInput, and then we can see if this helps).

[FrodeSolheim]

Hi, please download and install FS-UAE version 2.5.41dev, then go into FS-UAE Launcher settings (Advanced Settings) and write (use capital letters!):

SDL_XINPUT_ENABLED = 0

- and then restart FS-UAE Launcher. Does this help?

[lasborg]

Haven't been home for the last couple of days but I will check it tonight, hopefully.

[lasborg]

Originally Posted by FrodeSolheim

Hi, please download and install FS-UAE version 2.5.41dev, then go into FS-UAE Launcher settings (Advanced Settings) and write (use capital letters!):

SDL_XINPUT_ENABLED = 0

- and then restart FS-UAE Launcher. Does this help?

Now it works like a charm, with the Hori stick.

[FrodeSolheim]

Great, my "hunch" was correct

There should not be any negative effects of using this option (exceptthat the "menu" button on Xbox controllers will not work).

[lasborg]

Well that is hardly a problem. It might be a good idea to make it an option in settings.

[FrodeSolheim]

Well, for now it is better to keep it as an "advanced feature", I know what to suggest if other people report similar problems. I guess most people will have XInput controllers (such as the Xbox 360 controller) which work out of the box.

[lasborg]

Does strike me as quite odd that it it does not work with xinput, as it is for the xbox and uses the wireless receiver. Could be because it has no analogue inputs but it is strange to me.

[FrodeSolheim]

My guess is this (this was also my "hunch"):

XInput controllers also appear as DirectInput controllers in Windows. In SDL2, when direct support for XInput was added, this would have caused XInput controllers to effectively appear twice. So, SDL checks if the DirectInput device is also really an XInput device, and if so, hides it.

What I then guess happens is that the XInput code in SDL2 decides that this is not a proper controller (for some reason), and removes this entry as well. If I had this device, and debugged the SDL code, I would probably have found the reason.

What the option SDL_XINPUT_ENABLED = 0 does is that the XInput code in SDL2 is disabled, so SDL2 just lists all the DirectInput controllers (including the XInput ones Windows emulates as DirectInput devices).

Disclaimer: This post is based on guessing and may contain inaccuracies

[lasborg]

I wasn't actually aware that Xinput existed before i began reading up on it a couple of days ago. I was under the expression that it was all just Directinput - seems like i have been out of the PC loop for a good while.

Just getting an idea here, what if the launcher would accept xinput devices as standard, and then if no joysticks were detected in the joystick window, there would be a text describing the solution, or, if possible, a button to search for directinput controllers.