Using gamepad

[Desu [Hecate]]

Has anyone been able to use non-xbox360 pad in the game? I can't get mine detected by the game and it's so frustrating. Tried with x360ce but it's using xin - 4 so its unable to get it.

Any ideas?

Thanks in advice

[xvl260]

It seems like the game either recognize your gamepad or it doesn't. Just play with mouse and keyboard.

[Tottou]

I managed to fix DS2 controllers with the x360ce untill now - But Transistor is not accepting the x_inputs for me. Guess Im playing with keyboard and mouse.

[ResoluteSpider5]

Originally posted by Tottou:

I managed to fix DS2 controllers with the x360ce untill now - But Transistor is not accepting the x_inputs for me. Guess Im playing with keyboard and mouse.

Its very simple. See darkchaplain's post about x360ce. http://steamcommunity.com/app/237930/discussions/0/540742399427724713/#p1


in transistor/x86 folder you need xinput1_3.dll (32 bit) and x360ce.ini.
in transistor/x64 folder you need xinput1_3.dll (64 bit) and x360ce.ini.

Unless these files are in both folders it wont work.

[Rizlar]

Alright, so I've used x360ce with dozens of games before and always got it working with some trial and error. But Transistor refuses to recognise any controller as being plugged in. And occasionally it causes the controller to no longer be recognised by the x360ce configuration app either (showing a red square until I restart the computer).

I've tried every combination of files that seems like it might work and was suggested here, putting 64bit in the x64 folder, 32bit in the x32 folder etc etc.

The controller is a dualshock 2 with a usb adaptor. With other games I have got x360ce working by just copying across the dinput8.dll , x360ce.gdb and the x360ce application into the game folder then letting the configuration app automatically generate all the other files. In this case it doesn't work, nor does including the xinput1_3.dll, nor does including all the x360ce files.

Help meeeeeeeeeee!

[Rizlar]

Found a solution: just run the application directly from the x84 folder rather than through steam. Yay!

[susluv]

I got Direct Input device (x360ce) working in x86 ver. by adding following to x360ce.gbd

[Transistor.exe]
Name = Transistor
HookMask = 0x00000002

Also Hook Mode setting =>compability.

[Akko_Krirk0137✨]

Originally posted by Fable:

i fixed it by renaming the x360ce dll to xinput1_4.

I LOVE YOU MANNNNNNN
but i set xinput1_3 to 1_4 !!!!!

[The19thFighter]

Uhhh... As far as I can tell you guys don't actually need x360ce as Transistor uses SDL.
You just need to configure it correctly. Try to start Steam in BigPicture mode, set up your controller there and start Transistor. Steam should integrate perfectly with SDL, afaik.

[The19thFighter]

Just tested it.
I had to add "SDL_GamepadBind" to my Steam config located in config/config.vdf followed by my SDL configuration for my non-XInput gamepad as the Steam Wizard doesn't allow me to save it for some reason. Most likely you will not run into this problem. If you do, you can use http://www.generalarcade.com/gamepadtool/
This tool, or if you're on Linux you can use another configuration program (called AnitMicro) or the tool bundled with SDL.
Then you just get the string by pressing on get Mapping String.
And you insert a line into your config.vdf like

"SDL_GamepadBind" "ff00cb01000000000000504944564944,FuSa GamePad,a:b0,b:b1,x:b2,y:b3,back:b6,guide:b8,start:b7,leftshoulder:b4,rightshoulder:b5,dpup:h0.1,dpdown:h0.4,dpleft:h0.8,dpright:h0.2,platform:Windows,"

This one.
While you insert the string into the second part.

"SDL_GamepadBind" "[INSERT HERE]"

Make sure Steam is closed before saving the config, as Steam would just override it, when it closes.

[꧁ঔৣSergioTucuঔৣ꧂]

Is it just me or the controls break when you're using a controller and you press Shift+Tab. It's like I can no longer aim correctly after that. XBOX 360 controller here and that sucks.

[ivpn]

Was figthing with this problem myself, this was my findings:

Steam initialized: True, Steam controller initialized True
Controller 0, Microsoft Microsoft® Nano Transceiver v2.0, will use generic MonoGameJoystick support.
Controller 1, Steam Controller, will use SDL_GameController support.

Controller 0 is actually just wireless keyboard (+touchpad) - and the game tried to use it.
Removing the dongle caused the "correct gamepad" to be selected.

Now if only there was a way to reroute the sound to my headphones (Driver #1) instead of HDMI on the video card (Driver #0) without the same solution (unplugging the cable)... that would be nice edit: nevermind, there is

[brixtoncat]

Originally posted by Fable:

i fixed it by renaming the x360ce dll to xinput1_4.

OMG. thank you!