[Flatpak](Steam Deck) no response to controller input in game even though input plugin sees controller input

[randomname42]

I'm playing on a Steam Deck in desktop mode, docked with a TV. I can't get M64py (Flatpak) to respond to my 8BitDo (Ultimate 2C Wired, if it makes a difference) controller. In game, nothing happens no matter what is pressed.

The SDL input plugin sees and assigns controls if on Controller 1 I choose:
Device: Joystick 1 (Generic X-Box Pad)
Mode: Fully Manual
Plugged is also checked

The displayed default controls are correct by the way, for example digital pad is all hat(0) and start is button(7). In other words when reassigning, the same controls show as what was already there by default.

Even after reassigning them, and the SDL input plugin seeing the presses, in game nothing happens when pressing anything.

I have also tried (Steam settings) disabling the desktop config, disabling Steam input, and disabling both at the same time. Nothing has worked. In game there is no response to the controller.

I have no idea what's wrong or what to do about it.

Here's the log:
Frontend: INFO: attached to library 'Mupen64Plus Core' version 2.6.0
Frontend: INFO: includes support for Dynamic Recompiler.
Core: Using full mem base
Frontend: INFO: video extension enabled
Input: get_hat_pos_by_name(): direction '&Right' unknown
Input: get_hat_pos_by_name(): direction '&Left' unknown
Input: get_hat_pos_by_name(): direction '&Down' unknown
Input: parsing error in button() parameter of button 'Start' for controller 1
Input: parsing error in axis() parameter of button 'Z Trig' for controller 1
Input: parsing error in axis() parameter of button 'C Button R' for controller 1
Input: parsing error in axis() parameter of button 'C Button D' for controller 1
Input: parsing error in button() parameter of button 'R Trig' for controller 1
Input: parsing error in axis() parameter of axis 'X Axis' for controller 1
Input: parsing error in axis() parameter of axis 'Y Axis' for controller 1
Input: Using auto-config file at: '/app/share/mupen64plus/InputAutoCfg.ini'
Core: Goodname: Resident Evil 2 (U) (V1.1) [!]
Core: Name: Resident Evil II
Core: MD5: 1ADD2C0217662B307CDFD876B35FBF7A
Core: CRC: AA18B1A5 07DB6AEB
Core: Imagetype: .z64 (native)
Core: Rom size: 67108864 bytes (or 64 Mb or 512 Megabits)
Core: Version: 1444
Core: Manufacturer: Nintendo
Core: Country: USA
Frontend: INFO: using Video plugin: 'GLideN64' v2.0.0
Frontend: INFO: using Audio plugin: 'Mupen64Plus SDL Audio Plugin' v2.6.0
Core: Input plugin does not contain VRU support.
Core: input plugin did not specify a render callback; there will be no on screen display by the input plugin.
Input: 2 SDL joysticks were found.
Input: get_hat_pos_by_name(): direction '&Right' unknown
Input: get_hat_pos_by_name(): direction '&Left' unknown
Input: get_hat_pos_by_name(): direction '&Down' unknown
Input: parsing error in button() parameter of button 'Start' for controller 1
Input: parsing error in axis() parameter of button 'Z Trig' for controller 1
Input: parsing error in axis() parameter of button 'C Button R' for controller 1
Input: parsing error in axis() parameter of button 'C Button D' for controller 1
Input: parsing error in button() parameter of button 'R Trig' for controller 1
Input: parsing error in axis() parameter of axis 'X Axis' for controller 1
Input: parsing error in axis() parameter of axis 'Y Axis' for controller 1
Input: N64 Controller #1: Using manual config for SDL joystick 1
Input: Using auto-config file at: '/app/share/mupen64plus/InputAutoCfg.ini'
Input: N64 Controller #2: Using auto-config with SDL joystick 0 ('Microsoft X-Box 360 pad 1')
Input: 2 controller(s) found, 2 plugged in and usable in the emulator
Input: Rumble activated on N64 joystick #1
Input: Rumble activated on N64 joystick #2
Input: Joystick #3 doesn't support rumble effect
Input: Joystick #4 doesn't support rumble effect
Input: Mupen64Plus SDL Input Plugin version 2.6.0 initialized.
Frontend: INFO: using Input plugin: 'Mupen64Plus SDL Input Plugin' v2.6.0
RSP: RSP Fallback disabled !
Frontend: INFO: using RSP plugin: 'Hacktarux/Azimer High-Level Emulation RSP Plugin' v2.6.0
Core: Using video capture backend: dummy
Core: Game controller 0 (Standard controller) has a Memory pak plugged in
Core: Game controller 1 (Standard controller) has a Memory pak plugged in
Core: Game controller 2 (Standard controller) has a Memory pak plugged in
Core: Game controller 3 (Standard controller) has a Memory pak plugged in
Core: Using CIC type X102
Audio: Using resampler speex
Audio: Initializing SDL audio subsystem...
Input: Rumble activated on N64 joystick #1
Input: Rumble activated on N64 joystick #2
Input: Joystick #3 doesn't support rumble effect
Input: Joystick #4 doesn't support rumble effect
Core: Initializing 4 RDRAM modules for a total of 8 MB
Core: Starting R4300 emulator: Dynamic Recompiler
Core: Init new dynarec
Audio: Initializing SDL audio subsystem...

[randomname42]

It's the same thing with a Logitech F310, so the problem isn't related to a specific controller. M64py unilaterally isn't responding to controller inputs for some reason.

[gen2brain]

@randomname42 Do you also have parsing errors in log?

[randomname42]

@randomname42 Do you also have parsing errors in log?

What do you mean do i also have parsing errors in the log?

In the log I put in the first post, there are these parts that look wrong:

Input: get_hat_pos_by_name(): direction '&Right' unknown
Input: get_hat_pos_by_name(): direction '&Left' unknown
Input: get_hat_pos_by_name(): direction '&Down' unknown
Input: parsing error in button() parameter of button 'Start' for controller 1
Input: parsing error in axis() parameter of button 'Z Trig' for controller 1
Input: parsing error in axis() parameter of button 'C Button R' for controller 1
Input: parsing error in axis() parameter of button 'C Button D' for controller 1
Input: parsing error in button() parameter of button 'R Trig' for controller 1
Input: parsing error in axis() parameter of axis 'X Axis' for controller 1
Input: parsing error in axis() parameter of axis 'Y Axis' for controller 1

and there's also this section farther in the log:

Input: 2 SDL joysticks were found.
Input: get_hat_pos_by_name(): direction '&Right' unknown
Input: get_hat_pos_by_name(): direction '&Left' unknown
Input: get_hat_pos_by_name(): direction '&Down' unknown
Input: parsing error in button() parameter of button 'Start' for controller 1
Input: parsing error in axis() parameter of button 'Z Trig' for controller 1
Input: parsing error in axis() parameter of button 'C Button R' for controller 1
Input: parsing error in axis() parameter of button 'C Button D' for controller 1
Input: parsing error in button() parameter of button 'R Trig' for controller 1
Input: parsing error in axis() parameter of axis 'X Axis' for controller 1
Input: parsing error in axis() parameter of axis 'Y Axis' for controller 1
Input: N64 Controller #1: Using manual config for SDL joystick 1
Input: Using auto-config file at: '/app/share/mupen64plus/InputAutoCfg.ini'
Input: N64 Controller #2: Using auto-config with SDL joystick 0 ('Microsoft X-Box 360 pad 1')

The last three lines above make it look like M64Py might be using the external controller as controller 2, even though in the Steam client I have the external controller assigned as the first controller.

I don't know why M64Py is doing that, but it looks like that might be the cause of the problem. If it is the cause of the problem I don't know anything I can do on my end to fix it, as the controller order is already set properly in Steam.

M64Py isn't responding to the Steam Deck's built-in controller either, so controller order can't be the only problem.

It also doesn't matter if I run M64Py through Steam, or if it's launched directly. It doesn't respond to controller inputs either way, whether built in controller or an external controller.

To be clear, my goal here is to use an external controller. Trying to use the built in Steam Deck controller is impractical when you're docked with the Steam Deck hooked up to a TV, and that's how I'm trying to play.

[gen2brain]

Yes, the same errors; that is why I was asking. Without the log, I cannot know.