Steam Deck : Buttons response very weird

[goliom]

Describe the bug
I've installed AMD64 version of grout for Batocera on Steam Deck.
No problem on running it after modifying the rights of the files.
When i try to select langages, dpad and buttons don't answer very well. I have to press many times right dpad to select the langage, maybe 30 times, not very responsive ! On htop, grout process is taking 12% cpu, like a loop .

Reproduction Steps
Install Grout on Batocera OS on steam deck, then run it in PORT section

Expected Behavior
Button would answer well.

Information

• CFW: BATOCERA
• CFW Version: v42
• Handheld Device: Steam Deck
• Grout Version: [v4.8.1.1-beta.3] AMD64
• RomM Version: Last one, on docker.

[goliom]

I tryed with previous version v4.8.1.0 but same behaviour

[pawndev]

Hey ! Thanks for your feedback!

I don't have a steam deck (I would like), so it'll be complicated to replicate this behavior

If you don't mind tinkering a little bit, you can add
export INPUT_CAPTURE="true" in the Grout.sh file, juste after the line export CFW=....`

An input wizard will show on the screen asking you to press the correct button for your device

After that tell me if it was smooth, and a file should be created custom_input_mapping.json or something like this, you can link it to this issue

[goliom]

Mapping is very smooth, no problem !
here is the generated file
[root@BATOCERA /userdata/roms/ports/Grout]# cat custom_input_mapping.json
{
"keyboard_map": {},
"controller_button_map": {
"0": 5,
"1": 6,
"10": 11,
"11": 1,
"12": 2,
"13": 3,
"14": 4,
"2": 7,
"3": 8,
"4": 14,
"6": 13,
"9": 9
},
"controller_hat_map": {},
"joystick_axis_map": {},
"joystick_button_map": {
"20": 10,
"21": 12,
"22": 15
},
"joystick_hat_map": {}

[pawndev]

Okay nice to hear (or read) !
It would be complicated to do the check for the many controller out there for batocera so we can't actually make custom mapping for each of them

You can remove the line export INPUT_CAPTURE="true" in the Grout.sh
And rename the file custom_input_mapping.json to input_mapping.json and remove the 3 lines under the object joystick_button_map in the json, result to

{
  "keyboard_map": {},
  "controller_button_map": {
    "0": 5,
    "1": 6,
    "10": 11,
    "11": 1,
    "12": 2,
    "13": 3,
    "14": 4,
    "2": 7,
    "3": 8,
    "4": 14,
    "6": 13,
    "9": 9
  },
  "controller_hat_map": {},
  "joystick_axis_map": {},
  "joystick_button_map": {},
  "joystick_hat_map": {}
}

And see if it's smoother for you

[goliom]

I followed your instructions, the mapping seems good (it was before too) but it's still laggy and unresponsive. As if the apps were 0.001 frame by second

[goliom]

With perseverance, i managed to connect to my romm server. Another strange behavior, when using dpad, it click for 2 on the direction, not one. 2 up or 2 bottom, so I can't select what i need.

[pawndev]

Okay, if you're on the latest grout beta ( v4.8.1.1-beta.3 ), can you try adding this in the Grout.sh ?

export DISABLE_KEYBOARD_INPUT="true"
export DISABLE_JOYSTICK_INPUT="true"

just after the export CFW=BATOCERA like before

If it's not that, then I don't understand why 🙈

[pawndev]

Sorry for not being able help you more than that, since I don't have this device I can't try to reproduce it on my own

[goliom]

I tryed to put the 2 variables in the startup script but no changes, too bad...

Thank you anyway for your help.
Here is a screenshot of the CPU taken when grout is running since 10 min, i think something is off because too much cpu eaten for a waiting program.

[pawndev]

Usually grout don't have that much power on our little Linux handhelds 😂
But yeah, definitely we should profiling it to analyze CPU consumption at some time

[RegisMK5]

I'm experiencing similar issues.
Old Gen1 Surface Go running Batocera and Grout via the PORTS section.
Inputs will be very laggy, non-responsive, then suddenly slingshot.

ex. I'll be on the Grout homescreen with all systems listed, I'll tap down and nothing will happen for 1-5 seconds. Suddenly the selector will jump 3-15 spaces down the list. I'll tap down again and it may move one space correctly, or it may jump another 3 spaces, or it may do nothing. It feel like the system is lagging and playing catchup.

This has been occurring on all versions I've tested so far, v4.8.1.1 and multiple beta updates.

Side note: Great program, keep up the good work.