This also solves other input problems. IIRC, certain key combinations give bugged input results, unless you use proton.

I am glad you found a solution to your problem, but I feel the need to note that in my experience, Xinput works fine with the native Linux build without searching for drivers or fiddling with the command line. Right now I'm on a Kubuntu 23.10 and tested it with a Hori Fighting Commander PS4-044. I recollect using it with a Logitech F310 and a Retroflag Classic U.S.B. controller too. It just works, provided that I have those controllers set to their respective x-input compatibility modes.

Although the game only has two presets for button-bindings, and no further configurability.

Originally posted by Tonepoet:

I am glad you found a solution to your problem, but I feel the need to note that in my experience, Xinput works fine with the native Linux build without searching for drivers or fiddling with the command line. Right now I'm on a Kubuntu 23.10 and tested it with a Hori Fighting Commander PS4-044. I recollect using it with a Logitech F310 and a Retroflag Classic U.S.B. controller too. It just works, provided that I have those controllers set to their respective x-input compatibility modes.

Although the game only has two presets for button-bindings, and no further configurability.

I would guess that's because KDE comes preinstalled with a driver that's compatible with the old xinput standard.
Over here in GNOMEland that's not the case. I actually have that Logitech F310 and switching over do the xinput mode didn't do anything at all for me. RIP GNOME users.

I kind of doubt that it is the desktop environment myself, because I vaguely remember using the game on regular Canonical Ubuntu 22.04, which does not use K.D.E. as the default desktop environment, and I usually play games like this with a controller. It is just not the Linux distribution I have on hand to double check in the moment or to see how I had the system configured to be sure my memory is not just playing tricks on me, and my uncertainty regarding those matters is why I did not want to report that initially.

Originally posted by Tonepoet:

I kind of doubt that it is the desktop environment myself, because I vaguely remember using the game on regular Canonical Ubuntu 22.04, which does not use K.D.E. as the default desktop environment, and I usually play games like this with a controller. It is just not the Linux distribution I have on hand to double check in the moment or to see how I had the system configured to be sure my memory is not just playing tricks on me, and my uncertainty regarding those matters is why I did not want to report that initially.

I'm on Pop OS currently and Budgie before that, and neither one worked out of the box with neither of the native Linux builds of Momodora RUTM and Nuclear Throne, both of which had the exact same issue of being a ye olde Gayme Mayker gayme what was only compatible with xinput.
I assumed it had something to do with KDE because different distros have different tweaks and software packages installed by default. I've had one distro work just fine out of the box but another run into things not working when installed on the same PC, even though they were both Ubuntu distros. Of course I'm not really in the know on any of this, I'm just guessing.

Originally posted by RonaldKun:

If you're a Linux user, you're simply better off forcing Momodora RUTM to run with Proton, everything Just Werks out of the box and AFAIK it runs flawlessly.

I ended up with the same conclusion. It's kinda sad to give up on the native Linux version after all that effort from rdein and PLAYISM, but GameMaker on Linux just doesn't seem to be good enough. Looks like it can't be helped.

Well, I'm able to make Momodora (and other GameMaker games) recognize my controller via a set of quite odd actions, and make it permanent using that official guide, but even after that, force feedback still doesn't work. And seems like achievements doesn't work either (though I'm not sure). But with Proton, all of these things works flawlessly. Thanks Valve, I guess. (And of course thanks to Wine devs too.)



But just out of curiosity... What "old xinput drivers" and "preinstalled drivers from DE" are you talking about? I don't get it. AFAIK, there is only two things that affects Xinput controllers: one is a built-in kernel module xpad.ko, and another is an udev rules for setting correct permissions for controllers' nodes in /dev. And the second usually comes with the Steam package if installed via the system package manager. Both are independent of any DE. Am I missing something?

Originally posted by Tonepoet:

I am glad you found a solution to your problem, but I feel the need to note that in my experience, Xinput works fine with the native Linux build without searching for drivers or fiddling with the command line. Right now I'm on a Kubuntu 23.10 and tested it with a Hori Fighting Commander PS4-044. I recollect using it with a Logitech F310 and a Retroflag Classic U.S.B. controller too. It just works, provided that I have those controllers set to their respective x-input compatibility modes.

Could you check the force feedback with your controller? E.g. go to this spot...
https://gtm.steamproxy.vip/sharedfiles/filedetails/?id=3288673943
...and meet that (literally) stunning crimson blob?
https://gtm.steamproxy.vip/sharedfiles/filedetails/?id=3288677172

Also are achievements working for you?

Originally posted by Chaotic Slow:

Could you check the force feedback with your controller? E.g. go to this spot...
https://gtm.steamproxy.vip/sharedfiles/filedetails/?id=3288673943
...and meet that (literally) stunning crimson blob?
https://gtm.steamproxy.vip/sharedfiles/filedetails/?id=3288677172

Also are achievements working for you?

I've never used force feedback with Momodora. Most of my controllers don't even support force feedback, and especially not the ones I like using with Momodora. I treat this as if it's an S.N.E.S. game, and Rumble wasn't a thing until the Nintendo 64 Rumble Pak, and so I use earlier retro controllers.

I'm not even sure if the game supports force feedback, since I don't see a toggle for it. Normally games that support force feedback allow players to turn it off. I own a few force feedback controllers, but none that are readily available. They're stashed away somewhere.

Achievements are working on Linux. I got Faithful, Explorer, Pacifist, Healthy! True Ending and P-pleasegiveitome! in may of last year. I was using Ubuntu then if it makes a difference to anybody.

I did get all of the Ivory bugs, but the first time I played the game, I played it via the Humble Bundle executable on Windows 7, not the Steam version on Linux, so the achievement associated with that is still locked. So are the other two.

Originally posted by Tonepoet:

I've never used force feedback with Momodora. Most of my controllers don't even support force feedback, and especially not the ones I like using with Momodora. I treat this as if it's an S.N.E.S. game, and Rumble wasn't a thing until the Nintendo 64 Rumble Pak, and so I use earlier retro controllers.

I'm not even sure if the game supports force feedback, since I don't see a toggle for it. Normally games that support force feedback allow players to turn it off. I own a few force feedback controllers, but none that are readily available. They're stashed away somewhere.

Achievements are working on Linux. I got Faithful, Explorer, Pacifist, Healthy! True Ending and P-pleasegiveitome! in may of last year. I was using Ubuntu then if it makes a difference to anybody.

I did get all of the Ivory bugs, but the first time I played the game, I played it via the Humble Bundle executable on Windows 7, not the Steam version on Linux, so the achievement associated with that is still locked. So are the other two.

That's interesting. I'm completely lacking that retro console experience, so I had no idea that for experienced retro gamers, some modern games could be so tightly bound to a certain console generation! And yes, Momodora supports rumble (without any toggles tho), and IMHO does it in a rather immersive way. But for me, it works only on Proton version.

At least achievements are fine, so it's not an another GameMaker issue. Thank you for sharing your experience!