[BUG][LINUX] Unable to dash, right trigger brings up menu

[Hlatbern]

System: Linux Mint 18.1 Cinnamon 64-bit
Graphics: GTX 970
Controller: Xbox360 wireless w/ "ZettaGuard" reciever

I'll start off by saying that this game is EXACTLY what I've been looking for lately and brings back very fond memories of Symphony of the Night.

However, after playing up to the fight with Hornet in one sitting II've encountered a few controller bugs: left trigger brings up the inventory (select/back does nothing), right trigger brings up the menu (start does nothing), dpad left and right are mapped to up/down while dpad up/down do nothing, and the right stick does nothing.

I've tried launching from big picture mode and changing the configs with no luck and have had some success using "antimicro" to remap the controller buttons to the keyboard, but the erroneous inputs seem to take precedence.

Please let me know if more info is needed.

**EDIT**

I was able to finally get this working by removing all gamepad drivers and reinstalling only xboxdrv. Double check to make sure that you don't have the SteamOS DKMS module installed, as that will make the problems continue.

https://wiki.archlinux.org/index.php/Gamepad#Xbox_360_controller

Here is the config file I am using: https://pastebin.com/YMqYMCs2
It's located at /etc/default/xboxdrv

[Kight]

I am having the same problem with my PS4 controller. Right trigger is pulling up the menu instead of dashing. If I close the menu and hit right trigger, it will dash and then open the menu on the next press. This makes playing the game with a controller rather difficult.

[Suros:/#]

Having this problem sometimes when using the Steam controller. Controls will map all funny but analog inputs continue to work. Sometimes the controls will double bind and cause two actions at once. It's only happened about 4 times around the point of the hardmode of broken vessel, but can be very frustrating when you're too crippled to go reach a bench to save your spot.

Edit: Forgot to mention that this can persist even while restarting both Steam (relevant for the controller handling) and Hollow Knight. I've even powered off the controller and removed the dongle to be sure something didn't temporarily break. Other games behave normally.

Edit2: Now it's just not detecting the controller at all and using it like I need desktop mode. Maybe I'll just bypass Steam's control of it and use SC Controller instead. Apparently the game isn't calling for a control set anymore. (This one was on me. I disabled the overlay which is required for Steam controller use.)

[Have@NiceDay]

I'm having the same issue on Linux with PS4 controller. I've used 2 different controllers, restarted steam/PC

[PastyPilgrim]

I have this issue as well. With native controller support turned off, the knight's default state is walking to the right. If I enable native controller support that problem is fixed. Further, the default controls don't correspond with the Dualshock buttons (e.g. it suggests Y, which should be triangle on a dualshock, but it might actually be square that triggers the action).

That problem can be fixed with control rebinding (though the prompts will still be wrong), but what can't be fixed is that there are actions (such as the pause menu) which cannot be rebound, so pressing RT opens the pause menu and there's nothing I can do about that.

The simplest solution on the developer side would just be to allow every action to be rebound.

OS: Mint 18.3
CPU: i9-7900X
GPU: 1080 ti
Controller: DS4 over USB

[PastyPilgrim]

After more tinkering with the controls I've found the issue to be beyond just remapping problems. The triggers will register whatever button was last pressed. If I go into control rebinding and rebind jump to 'RB' and then try and rebind it to 'RT', 'RT' will be interpreted as 'RB'. Same results when attempted with face buttons, etc. Trying to bind something to start, select, touchpad, or a directional button results in a null signal being interpreted.

This makes the game entirely unplayable with a controller because the results of buttons are unpredictable.

[anachoret]

Interesting. No problems here on SteamOS with Steam Controller in gamepad mode. Does turning the experimental/beta controller mode in game settings do anything?

[PastyPilgrim]

I've tried everything. I also tried big picture mode with its native controller drivers. By default, big picture mode won't recognize my controller so I had to add custom udev rules for it to recognize it. However, once it was recognized and registered within steam, no game would detect my controller, even though I could navigate steam with it.

[Rei Scarlette]

Edit: I was a bit slow in writing my post as I walked away in the middle of it,
but I'll leave it here anyways. I see you replied before I sent it. Please just answer whatever you find is still relevant, then.

PastyPilgrim님이 먼저 게시:

-a bunch of stuff, clipped to save space-

Are you using an official or third-party DS4 controller? What are your settings for Steam's native controller support? Can you connect your controller through Bluetooth at all, or does your PC not support it? I'd like to know if that last bit in particular makes a difference for you if possible.

For the last bit I mentioned anyway, I noticed recently Steam itself has been doubling or garbling inputs for my games while plugged in via USB. Not all games, it seems to be hit or miss. It looks like most games which have their own native support for controllers are the ones that are affected. Outside of Steam I can verify my controller works properly either over Bluetooth or USB, but in Steam I am getting too many inputs from my controller over USB, and some of them don't match the buttons I am actually pressing.

[PastyPilgrim]

Ok, I finally got it working with a controller in big picture mode. This was the solution:

https://www.gamingonlinux.com/articles/you-will-need-to-update-your-udev-rules-for-the-steam-controller.8593

Hollow Knight still interprets the RT as a signal to open the pause menu even through Steam, which should be sending a RT signal, but at least now I think I can mess with configurations and hopefully fix it.

To answer your questions Scarlet: it's an official DS4 and I do not have a bluetooth receiver so I cannot test it with BT. The current settings for my controller in steam are the default. I also tried the WASD mode config and it still registered RT as pause menu.

I should also add that this is the only game that I have ever had controller issues with on Linux.

[Rei Scarlette]

PastyPilgrim님이 먼저 게시:

To answer your questions Scarlet: it's an official DS4 and I do not have a bluetooth receiver so I cannot test it with BT. The current settings for my controller in steam are the default. I also tried the WASD mode config and it still registered RT as pause menu.

I should also add that this is the only game that I have ever had controller issues with on Linux.

Thanks for the response. I don't have much experience with Linux first-hand unfortunately, so I'm not sure I have any other advice I can give, myself, but I thought it'd be worth checking out anyways if possible. Anything else I say would be guessing into areas I don't know about, so I think that's all I could say that might be really useful.

Good to see that you've found something though, in any case. Hopefully from there you can get it working on a satisfactory level.

[dwarf_dustin]

I am also having this *exact* issue; I couldn't have explained it better.

It wasn't game-breaking until I unlocked the DASH skill. My right trigger opens the inventory so ... yea I can't dash.

Editing the keyboard configuration allows remapping of the inventory and map buttons, but editing of the gamepad lacks the inventory button. So I can't remap the one button I need too lol.

I am currently on Win7 (not linux) and I am using an old but still working AirFlo EX gamepad; essentially it's a vanilla Xbox controller knockoff. I ordered an Xbox 360 controller but that wont arrive for a week or so. I'm going to see if I can find another work-around in the meantime. Is there no ini file where the controls can be set professionally?

[Hlatbern]

I was able to finally get this working by removing all gamepad drivers and reinstalling only xboxdrv. Double check to make sure that you don't have the SteamOS DKMS module installed, as that will make the problems continue.

https://wiki.archlinux.org/index.php/Gamepad#Xbox_360_controller

Here is the config file I am using: https://pastebin.com/YMqYMCs2
It's located at /etc/default/xboxdrv

[PastyPilgrim]

I should add that using steam's controller configurator didn't help. Even if the triggers weren't bound to any actions at all, they still triggered the menus.

Here is the complete solution that I found (now playing the game properly without any issues):

https://www.reddit.com/r/HollowKnight/comments/6m1a7w/steam_controller_mapping_wrong/dksgk15/

[Francesco]

necrobumping but this bug still exists to me :/

[Viech]

This issue still exists and people find this old thread looking for it, so I'll update with a solution that worked for me.

My situation is the following: I'm using a PS5 controller under Linux > 5.12. I mention the version because the PS5 controller has official Linux drivers as part of the kernel since then. My problem was the same as reported in this post: The LT/RT buttons open the inventory/menu respectively and this couldn't be changed.

Here is a workaround. It's not clear if it works for other OS but GNU/Linux, but it should work for additional controllers other than the PS5 one. It is not clear if this will work with future HK versions if any are released (this could invalidate the patched DLL).

1. Obtain the modified DLL from https://steamcommunity.com/sharedfiles/filedetails/?id=2525497719
2. Backup and replace ~/.local/share/Steam/steamapps/common/Hollow Knight/hollow_knight_Data/Managed/Assembly-CSharp.dll (or wherever your file with that name is found) with the modified one.
3. In the Steam settings for HK, add the `--exo` launch option.
4. In the Steam controller settings for HK, set "OVERRIDE FOR HOLLOW KNIGHT" to "Enable Steam Input". (Make sure your controller is listed there and configured adequately within Steam.)