Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Games launched with proton do not detect controllers #1549

Open
Tuerai opened this issue Sep 22, 2018 · 29 comments

Comments

Projects
None yet
@Tuerai
Copy link

commented Sep 22, 2018

Compatibility Report

  • Name of the game with compatibility issues:
    Burnout Paradise
    Dragon Quest XI
  • Steam AppID of the game:
    24740
    742120

System Information

I confirm:

  • that I haven't found an existing compatibility report for this game.
  • that I have checked whether there are updates for my system available.

steam-742120.log

Symptoms

Tested with an Xbox One S controller, and a PS Dual Shock 4 controller, both connected wired. They work in native steam games. They work in games where I use Lutris with WINE. They work in Steam Big Picture Mode. They are not detected at all in games I launch through proton. Have tested in Burnout Paradise and Dragon Quest XI.

Reproduction

I have steam installed on Arch Linux. I have launched it as both "Steam Native" and as "Steam Runtime" with the same behavior on both (works in BPM and not detected by Proton-launched game).

I tried both with and without xboxdrv/ds4drv installed, and had the same behavior as well.

@unomar

This comment has been minimized.

Copy link

commented Oct 1, 2018

Same issues here. Tried both a Steam Controller and wired Xbox 360 gamepad. Running Fedora 28 with the latest beta steam client. No controller inputs detected in Burnout Paradise. Both controllers work fine in big picture mode and native Linux games.

@dearlygparted

This comment has been minimized.

Copy link

commented Oct 1, 2018

I have steam installed on Arch Linux. I have launched it as both "Steam Native" and as "Steam Runtime" with the same behavior on both (works in BPM and not detected by Proton-launched game).

Similar issue here. Xbox 360 wired controller works in Steam BPM and in native Steam for Linux games, but not in Final Fantasy VII, however it works in Kingdom Come Deliverance.

@grahammitchell

This comment has been minimized.

Copy link

commented Oct 2, 2018

Same issue here. Trying to play Tales from the Borderlands through Proton 3.7-6 using my Steam Controller and the game only shows options for keyboard and mouse. It doesn't matter what config I load in.

It's a shame, because the game works great through Proton otherwise; it would be really nice to sit on the couch and play through it finally.

@junglerobba

This comment has been minimized.

Copy link

commented Oct 3, 2018

The latest Steam Client Beta Update seems to fix this. I had the same issue with Monster Hunter World, both with Steam and Xbox One Controller, and those work fine now.

@grahammitchell

This comment has been minimized.

Copy link

commented Oct 3, 2018

I just updated to the latest Steam Client Beta, and this still isn't fixed for me. Tales from the Borderlands still doesn't detect that a controller is plugged in.

@jonathansty

This comment has been minimized.

Copy link

commented Oct 5, 2018

Experience this issue when launching monster hunter world although this issue doesn't seem to be happening with Castlevania: Lords of shadows.

@z0z0z

This comment has been minimized.

Copy link

commented Oct 7, 2018

Right click on the game in your library and make sure your mapping is configured correctly for your controller. Also check "Controller Settings" in Steam.

@grahammitchell

This comment has been minimized.

Copy link

commented Oct 7, 2018

make sure your mapping is configured correctly for your controller

What?

@Utopanic

This comment has been minimized.

Copy link

commented Oct 21, 2018

I'm having the same problem here on multiple games(Monster Hunter World, Darksiders Warmaster edition and Nier Automata)

@Rabcor

This comment has been minimized.

Copy link

commented Nov 3, 2018

Hmm my logitech rumblepad set to xinput mode works fine.

@bradleypariah

This comment has been minimized.

Copy link

commented Dec 16, 2018

Having the same problem with an official wireless 360 controller.

Controller still works perfectly in SteamOS games, it works in Big Picture, but it doesn't work in Proton games anymore.

When I first installed Fallout: New Vegas, I had opted for Proton v3.14 (I think?) in Steam Play settings, but the controller didn't work, so I fell back to an older version (3.7-8, I believe), and the controller started working. It worked for The Witcher 3 and Fallout 3, as well. A Steam update came out, and now it doesn't matter if I'm in the Steam beta update or not. It doesn't matter which version of Proton I choose. None of the controller configurations/templates work, except for one - if I choose the template that emulates a keyboard and mouse.

Kubuntu 18.04 64-bit, i7-2600S octa-core CPU, 8GB DDR3 RAM, Nvidia gtx680

@bradleypariah

This comment has been minimized.

Copy link

commented Dec 16, 2018

Interesting revelation. Found a fix.

Step One: Open Big Picture mode, then navigate to Settings > Controller Settings. Check Xbox Configuration Support

Step Two: (Still in BPM) Navigate to Fallout: New Vegas > Manage Game > Controller Options > Steam Input Per-Game Setting > Set to: "Forced Off"

Profit. Still running Proton 3.7-8. I'll check back on the topic if the fix is only temporary.

@200Puls

This comment has been minimized.

Copy link

commented Jan 1, 2019

@bradleypariah
I just had the same problem.

My setup is a bit different. I am using a PS4 controller, Ubuntu 18.10, Proton 3.16.6 beta and NBA 2K Playgrounds 2 is the game in which the controller was not recognized.

Your suggested workaround fixed it also for me. So it seems to be a Steam problem.

@grahammitchell

This comment has been minimized.

Copy link

commented Jan 1, 2019

I just tried bradleypariah's workaround and it didn't make any difference. Controller still not recognized for me in Tales from the Borderlands.

Using an Xbox One controller wirelessly using xpadneo and Proton 3.7-8 (non-beta).

These Proton games work out-of-the-box with the controller:

The Xbox controller also works great with Linux native titles (not using Proton):

The controller is not detected in the following game under Steam Play/Proton:

It won't detect the controller using bradleypariah's workaround or without. It also doesn't seem to matter whether I use the Xbox One controller or my Steam Controller.

@bradleypariah

This comment has been minimized.

Copy link

commented Jan 2, 2019

grahammitchell - Question, just to move the conversation forward - If you turn on XBox Configuration Support in BPM settings, and Force On Steam Input Per-Game Setting on the game, then download and apply a template, does that work? What if you choose the keyboard and mouse template? I'm thinking the devs might be curious to know which hand-off is getting dropped.

@grahammitchell

This comment has been minimized.

Copy link

commented Jan 4, 2019

Thanks for the suggestions.

If you download and apply a template, does that work?

No. Tales from the Borderlands still behaves like no controller is detected.

What if you choose the keyboard and mouse template?

That does work, in the sense that it allows me to move the mouse around using the right stick and click using right trigger. It's a fairly unpleasant gaming experience but I guess it could be made to work if one were desperate to play it with a controller.

@MartinDueren

This comment has been minimized.

Copy link

commented Jan 6, 2019

I can confirm this. No proton launched game works with Steam controllers so far for me. Using the keyboard and mouse template works, but this is a tedious workaround. All native ones work flawlessly. The Steam overlay (and navigation in the overlay menus) works with the controller without problems.

@aroskuski

This comment has been minimized.

Copy link

commented Jan 6, 2019

I was having some issues like this with NieR: Automata a while ago. I think I eventually worked around it by adding my user account to the input group, but it's been a while so I'm not 100% sure.

@Britaliope

This comment has been minimized.

Copy link

commented Jan 7, 2019

I can confirm that Steam Controller does not work (as a controller) for proton-launched games. Steam Controller works correctly on Big Picture and steam overlay menu but the game does not detetect the presence of a controller.

Here is the log for Ori and the Blind Forest Definite Edition
steam-387290.log

@DanMan

This comment has been minimized.

Copy link

commented Jan 14, 2019

In Shadow of War it's also only detected, if you turn off the XBox Configuration Support in BPM settings. Proton 3.16-6B, Ubuntu 18.04.

Edit: in Dead Or Alive 6 it doesn't react to any input once I'm past the start screen, which I am able to dismiss by pressing the enter key. Doesn't matter if Steam Input is enabled or not. Forcing it off makes the XB1 pad work though.

@reifnotreef

This comment has been minimized.

Copy link

commented Mar 14, 2019

Has there been any update on this?
Want to make the switch to Linux only on my desktop, but I want to make sure I can use Proton for a couple games with my steam controllers. Specifically Death Squared, Lost Castle and Overcooked(1, haven't bought 2 yet).

@kparal

This comment has been minimized.

Copy link

commented Mar 14, 2019

Overcooked 1 works perfectly for me out of the box with both Steam Controller and Xbox One controller on Fedora 29.

@grahammitchell

This comment has been minimized.

Copy link

commented Mar 14, 2019

The vast majority of games work perfectly fine with controllers under Proton, which is why this bug hasn't been fixed yet. Only a very few games fail, and it's not clear why when so many others work.

In my comment from January 1, I list several other games that do work fine for me. Just not Tales from the Borderlands, in my case.

@esotericDisciple

This comment has been minimized.

Copy link

commented Mar 14, 2019

"Shooty Skies" doesn't work either, but it does in the native Linux version. Has anyone looked into this as being a directx issue rather than a proton issue? Why can't games just be rewritten in opengl instead of trying to get directx to work on linux?

@reifnotreef

This comment has been minimized.

Copy link

commented Mar 14, 2019

@rmanosuthi

This comment has been minimized.

Copy link

commented Mar 15, 2019

I had this problem a while ago and fixed it by disabling kernel modules that handle controllers. Steam doesn't seem to like those modules.

I'm using Gentoo and I compiled my kernel manually, and games launched through Steam (i.e. Witcher 3) didn't detect my XB1S controller until I did that.

Not sure if this will solve anyone's problem though, I didn't test it with native Linux games.

@Azarilh

This comment has been minimized.

Copy link

commented Mar 23, 2019

Interesting revelation. Found a fix.

Step One: Open Big Picture mode, then navigate to Settings > Controller Settings. Check Xbox Configuration Support

Step Two: (Still in BPM) Navigate to Fallout: New Vegas > Manage Game > Controller Options > Steam Input Per-Game Setting > Set to: "Forced Off"

Profit. Still running Proton 3.7-8. I'll check back on the topic if the fix is only temporary.

That worked for me on Monster Hunter World. Thank you!

@ekthomson

This comment has been minimized.

Copy link

commented Apr 14, 2019

Forced Off on the controller options also worked for Vessel.

@schmidtbag

This comment has been minimized.

Copy link

commented Apr 20, 2019

This is a pretty weird problem, because not only does this not affect every game, but it also seems to depend on your version of Proton. For example, I tried playing the game Gas Guzzlers Extreme, and in Proton 4.2-3, none of the suggestions listed above work, whether I enable or disable them, in any combination. But, if I downgrade to Proton 3.16, my controller works just fine.
I have a DS4 that I connect through Bluetooth, if that makes any difference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.