Controller detected all wrong.

[TheFeri]

Hi!
I'm on steam deck, this works perfectly, thank you for your hard work!
However, every now and then I play in desktop mode using a PS5 controller with bluetooth, and while the game detects it the mapping is all wrong, in the settings it's all good but in practice it just doesn't. Both bumpers are dodge, the right stick is movement while the left does nothing, the square button is basic attack while the rest don't do anything, and the D-pad is orbs.
I don't know if there's anything I can do myself right now that's why I'm writing this.

[ALEZ-DEV]

Hey, thanks for using the project!

I recently bought a xbox controller (An xbox Series x|s) and so I had the possibility to dive into the world of controller on linux... and things are rough, for example my controller was working just fine when connected via usb but was not working at all via Bluetooth, I needed to do :

1. Install the specific driver for my system (xpadneo for my case)
2. Disable SDL and Force Wine/Proton (or any other app) to use HID instead

This seem straightforward but I had a rough time to find and understand these things
Even if this little story isn't really related to yours, I think that the solution will be really similar to fix

I need to implement the features which let you add environment variables when starting the game, because controller related issue are often fixable by just passing environment variable, the time I implement that you will need to use the CLI version of the launcher, you will just need it to start the game with the special environment variable.

Your issue seems related to SDL configuration, so you will need to specify a new controller config, so for that :

1. Execute the command sudo evtest in your terminal and copy your controller ID (Test every possible event until you find the PS5 controller)
2. Then go to the SDL GameControllerDB, go to the gamecontrollerdb.txt and search your controller ID under the # Linux section, then copy your controller line
3. You need to install the CLI version of the launcher with these steps, if it fail to install use this script
4. Now that the launcher is installed, you can run this command to (maybe) fix your issue :

SDL_GAMECONTROLLERCONFIG="030000005e040000120b00000b050000,Microsoft Xbox Series Controller,a:b0,b:b1,..." babylonia-terminal-cli

I hope that fix your issue until I implement this feature, tell me if anything goes wrong!

[TheFeri]

Ah, that seems to be too much of a hassle. I already had problems with the gui version, from the discover store it didn't even installed, it gave out an error that something is missing (nothing was) so I used "flatpak install moe.celica.BabyloniaTerminal" and it installed with no problems. I only came here because Qu's patch broke the game for me, yes all the way from the PC client launch it worked completely fine as a non steam game until Qu arrived. Not having an option to choose the install path was bad enough, I wanted to copy my already installed and patched game to where this wanted to install it but never found the place.

I'd rather not mess around with CLI I'm pretty sure I'd mess things up. That controller works in everything else, It worked with PGR before Qu borked it. I guess I'll just only play in gaming mode until the GUI version gets updated. I work 12 hour shifts with a whole lot of 1 day breaks, I ain't gonna mess around doing CLI stuff. I'm just gonna be patient. Thank you for your hard work and response!

[ALEZ-DEV]

It's okay, time is valuable, I will let you know when I implement this feature!