Windows [BUG] Game doesn't recognise keys, leads to issue with key-bindings/hotkeys

[aili]

Hi!
I'm gonna try my best to explain this confusing issue. I have a problem with the hotkeys, and I'm pretty sure the issue started with the 1.5.5 patch. My game is fully updated to 1.5.6, I launch it through Steam. I'm on Windows 10, my game is set in English but my system and my keyboard are German (setting the game language to German doesn't fix the issue though). My game is modded but the issue persists even in a new save with all my mods taken out.

So I'm trying to set my inventory hotkeys, I always used the numbers 1-0 and the two following keys, which are the ß and ´ key on a German keyboard - I'm gonna add a picture to explain it, I usually use the whole blue row but the ones I marked in red are the problem now.

Since the update, when I try to use those two keys for keybinds, the game tells me "NONE" keys were selected - so the game simply doesn't seem to recognise those keys at all anymore? I've always played with the same language settings for my game and my system/keyboard, nothing about that changed and it always used to work before.
It's really inconvenient cause I suddenly can't use the hotkeys I've been using for years anymore. I liked having my 12 inventory slots mapped to 12 keys in a row, now i have to use two random ones that are far away from the others for the last two slots.

I hope I explained this well enough. If I missed anything please let me know!
Thanks :)

 

[aili]

Still having this issue... :(

 

[EscaJ]

What I can think of is a workaround rather than a fix. Using something like a joypad key mapper you could make a setup where those keys gives a different output, only for stardew valley. Essentially changing them to two keys you aren't using that the game recognises. It's not a fix but it might help...?

 

[aili]

2 years and one major update later, different pc and different keyboard and I'm still having this issue. Again, it was never a problem before the 1.5.5 patch and I never have issues with other games not recognising any key input :/

 

[yamina]

I unfortunately can't help you with this problem, but I can confirm that I have the exact same issue; also with a German keyboard.
And it's confirmed not a fault of that, as I've tried it with two other, new keyboards and up to date drivers. So it's not a problem uniquely to you. I've been trying to fix this for days with no luck, but should I find a way to resolve this I'll absolutely share.

 

[aili]

I unfortunately can't help you with this problem, but I can confirm that I have the exact same issue; also with a German keyboard.
And it's confirmed not a fault of that, as I've tried it with two other, new keyboards and up to date drivers. So it's not a problem uniquely to you. I've been trying to fix this for days with no luck, but should I find a way to resolve this I'll absolutely share.

Thank you!!
I've also tried it with the game in German, keyboard in English, different keyboards and different installations, nothing. And since it wasn't an issue before the 1.5.5 patch I knew it couldn't really be a problem on my end, but I haven't found anything about this anywhere in two years - so I'm kinda glad to hear that I'm not the only one! (sorry you're experiencing it too though). Hopefully we can figure it out :)

 

[yamina]

Fingers crossed! And yeah, your thread was the only really documented instance of this issue I was able to find when trying to research this. Hopefully a solution can be found.

 

[MithranArkanere]

I am having this issue with several keys in an es-ES keyboard set up like this:

The [ º ], [ ¡ ], [ ´ ], [ ñ ] and [ ç ] keys are not being recognized, and the game says that key has been pressed already when trying to use them for a keybinding.

This only affects key bindings. These keys work when used in texboxes, like when naming an animal.

This creates further issues for mods, as the key is recognized as (None) and any key bound to "None", which mods use to disable keys, will trigger when pressing any of these keys that are not recognized, when the expected behavior is, well, nothing happening.

The only way I found around this issue, other than externally rebinding keys with applications like autohotkey, was to switch the keyboard language to English, which has to be done every time the game starts as windows does not have a way to make an application always start with a different keyboard layout, only to change them when the application is running, and to keep different layouts on running applications.

I have this issue in Stardew and Mercenary Kings, but not in other Monogame games like Transistor and Dwarfs!? So it has to be solvable.
I searched about this, and found threads like this one talking about having this issue and how to fix it, so the issue has to be defintely solvable.

---

Also, the game is supposed to open the chat with a slash / to quickly input commands when pressing the key where the slash goes in the keyboard, which is - in es-ES keyboards, and the game has no way to set a separate key for that. So for other languages, it just won't work. I can't set [ - ] for this on my keyboard.

Oh, and the game does not recognize additional mouse buttons in my mouse other than buttons past the third. So, for example, the mouse tilt buttons (mouse 4 and mouse 5) aren't working. But unlike the bugged keyboard keys, it doesn't say they are already bound to another key. They just don't work.

 

[yamina]

I've since had a friend find some information about this on a different forum and it seems to be very likely that this is a core issue of the current XNA Framework itself.
Meaning it's not something that canbe fixed on this end and would have to be patched in that one.

 

[Pathoschild]

This would mainly need a fix in MonoGame (see issue #8033), since Stardew Valley just uses the input codes it provides. I don't think trying to fix it separately in Stardew Valley would be a good idea, since (a) the problem is more complex than it appears and (b) any fix we implement would conflict with a future fix in MonoGame.

 

[aili]

This would mainly need a fix in MonoGame (see issue #8033), since Stardew Valley just uses the input codes it provides. I don't think trying to fix it separately in Stardew Valley would be a good idea, since (a) the problem is more complex than it appears and (b) any fix we implement would conflict with a future fix in MonoGame.

I don't know anything about frameworks and programming and whatnot, so I don't really understand what MonoGame is or what any of this means for us - but did this problem appear with an update in MonoGame? Cause again, I've played sdv for years and never had this issue before.
And do you think a fix to MonoGame could possibly come in the future?
Thank you! :)