Mac OS X / can't get controller to work

[MrBurns]

Hi!
Im using a steam controller under os x, but pyre won't recognise that the controller is there.
No matter if I connect via usb, dongle or even start the game via steamlink.
The controller is working in big picture mode and I can get the steam overlay in-game pressing the steam button but beyond the game ignores that there is a controller available completely.

Playing in Windows everything works as it is supposed.

My System is a mid2014 mbpro running sierra 10.12.6

Is there even controller support under os x or is it just broken at the moment?
Please Troubleshoot.

Kind regards
Christian

[borogove]

Supergiant Steam Controller Bindings Empty on Mac

The official Supergiant Steam controller bindings are completely empty on my Mac. 3rd party bindings work. As far as I can tell, the game is up to date as of today (August 23). I noticed that an issue of similar description was fixed in Patch v1.49780, so I'm not sure whats going on. Any ideas?

[MrBurns]

Also I reinstalled Transistor where the controller works just fine and I'm not having the problem in any other steam game, so I guess it is pyre related.


Anybody else having this problem?

[reverendloc]

Hey there's a suggestion here:

http://steamcommunity.com/app/462770/discussions/2/1471967615842758441/

What type of controller are you using?

If you turn config support on/off does it help?

It seems like other people reported that the bindings were blown away somehow, so it may help if you update your key mappings to Generic Game Pad or something similar.

[MrBurns]

Hi, thanks for the reply and moving this discussion to the right subforum.

The controller I use is the standard steam controller, but I also tried a playstation ds3 with no success.

Also I tried turning generic input on/off in preferences as well as the check mark to use the configuration for generic controllers in the steam game settings.

Switching between custom and the official supergiant config, doesnt help either. In game in the controls settings the gamepad is greyed out, so I'm guessing the game doesn't know there is a gamepad at all.

Any further advice would be great.

[MrBurns]

Update:
In the meantime I went as far as completely removing steam from my mac and reinstalling it.
Still no change.
But I noticed when using Community Controller Configuration "Two Action Sets..." I could at least use the controller in game. Though the game still doesn't detect that a controller is used as it shows hints only for keyboard and not controller buttons, because the mentioned community config is mapped to keyboard and mouse actions.

Maybe there is a launcher option to force gamepad? Also I'm wondering if somebody else has the exact same problem or if you guys at supergiant can reproduce the error? Otherwise maybe I'm having some software or something else interfering with my steam controller...

but right now I'm a bit at a loss what else I can do.

[MrBurns]

Steam Controller under OS X still not working, please investigate!

Dear Supergiant Tech Support,

I already posted about this before but except an proposed solution which didn't work I haven't heard from you again for a few weeks now.

As I mentionend before something is wrong with the controller detection of pyre under os x.
My steam controller (like the one you can order from steam) won't be detected by the game no matter what I try:

completly removing steam and all game preferences from disk - didn't work

resetting steam controller firmware - didn't work

having it plugged in via usb / reconnecting controller - didn't work

trying all the different controller related checkboxes in steam settings and the one in manage your game - didn't work

playing via steamlink - didn't work

switching away and back from supergiant controller config - didn't work.

Only thing that worked so far is using a user config which maps mouse and keyboard commands to the steam controller instead of using the official supergiant config. But then of course the game detects I'm playing with mouse and keyboard, showing only keyboard bindings in dialogue and ui.

I am not having any controller problems in bastion or transistor, which are also amazing by the way.

Also tried using an Playstation DS3 controller over bluetooth, which works fine, even displaying playstation buttons in game.

I would be very happy if you could check out this problem and get back to me.

If there is anything else I can do: posting you any debug logs or something like that, just give me some instructions and I'll gladly help.

So all I can ask of you, please investigate this.

Kind regards

Christian

[flibitijibibo]

I just took a look at this and it appears to be a problem with not just Pyre, but EVERY game that uses standard controller APIs! I can't get a single one of my games to work with my Steam Controller anymore... the controller works fine with other operating systems with the same games, and even different controllers with the same games on macOS work! So we're looking at either a Steam issue or a macOS issue.

Please report this to Valve so they can investigate the issue further:

https://help.steampowered.com/en/

[flibitijibibo]

Originally posted by flibitijibibo:

I just took a look at this and it appears to be a problem with not just Pyre, but EVERY game that uses standard controller APIs! I can't get a single one of my games to work with my Steam Controller anymore... the controller works fine with other operating systems with the same games, and even different controllers with the same games on macOS work! So we're looking at either a Steam issue or a macOS issue.

Please report this to Valve so they can investigate the issue further:

https://help.steampowered.com/en/

As a follow-up, this may be a regression with how they compensate for third-party controllers using the Steam Input system - for example, a 360 controller with Steam Controller config support turned on. Previously turning this on with GamePad mode enabled caused the device to show up as two separate devices; this has been fixed with the latest versions of Steam and SDL 2.0.6. There's a chance that, on macOS only for some reason, it's doing the same compensation but for Steam Controllers as well, causing the gamepad implementation to be completely ignored. This means that it will only show up if you use keyboard/mouse input to control the game.

[flibitijibibo]

I've posted a report to the Steam Controller bug report forum, please contribute any data you can provide:

http://steamcommunity.com/app/353370/discussions/1/1520386297684952083/

[MrBurns]

Thanks for the reply, flibitijibibo!
I wasn't expecting anybody looking into this any more, but if it isn't game but seems to be steam related it is clear why the developers can't actually provide a solution.

I'll gladly provide some data if I can. Can you give me any instructions or a post link on how to create log files or read out the relevant data for this controller issue.


Cheers

[Armillary]

It looks as though this was recently (hopefully) patched in libsdl. Devs, is there a plan to integrate an update to the library soon? At present steam controller support is still dead on OSX.

https://bugzilla.libsdl.org/show_bug.cgi?id=3951

[flibitijibibo]

I’ll be posting the fix as a gamecontrollerdb.txt update this week, which should let us keep the stable lib and fix the problem at the same time.

[flibitijibibo]

The update might take longer than I thought, so here's a fix that'll also fix the rest of your games:

echo "export SDL_GAMECONTROLLERCONFIG=\"030000005e0400008e02000001000000,Steam Virtual GamePad,a:b0,b:b1,x:b2,y:b3,back:b9,start:b8,leftstick:b6,rightstick:b7,leftshoulder:b4,rightshoulder:b5,dpup:b11,dpdown:b12,dpleft:b13,dpright:b14,leftx:a0,lefty:a1,rightx:a3,righty:a4,lefttrigger:a2,righttrigger:a5,\"" >> ~/.bashrc

Log out then log back in and it should work after that.

[Armillary]

Thanks! Adding that environment variable did the trick. Keep up the great work.

[Gecko]

I was having the same issue, and adding the environment variable to my .bashrc or .bash_profile didn't seem to work for some reason, but then I got the latest Steam Beta client patch and now it works! Thank you for fixing this! :)