[Bug]: Regression - wiimote (sideways) not working correctly

[fekir]

Platform

Linux

Renderer

Vulkan

Game exhibiting the issue

New Super Mario Bros

Describe the issue

I used to play "New Super Mario Bros" (and "Newer Super Mario Bros") with the device type under controls set to "wiimote sideways".

With the current version with "wiimote sideways", the button 2 works as expected, but the arrows are wrong.

For example, clicking on the left arrow (on a classic controller, or on a real wiimote put sideways) behaves as if I've clicked on the down arrow.
Clicking right, moves up
And so on.

Thus, it seems that "wiimote sideways" works exactly like "wiimote".

I did not change any configuration, both the original wiimote and another controller (a dualshock) have the correct mapping and work as expected in the retroarch menu (up moves up, down moves down) and with games on other cores.

A workaround for those particular titles is to use "Wiimote+classic controller" as controller, in that case, the arrow behave correctly, both with an original wiimote and the dualshock.

Unfortunately I do not play that often, so I do not know since which version this functionality broke.

Log Output

[INFO] [Config] Looking for config in: "/home/fekir/.config/retroarch/retroarch.cfg".
[INFO] RetroArch 1.22.2 (Git 5f23e85)
[INFO] === Build =======================================
[INFO] CPU Model Name: Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz
[INFO] Capabilities: MMX MMXEXT SSE SSE2 SSE3 SSSE3 SSE4 SSE42 AES AVX AVX2 
[INFO] Version: 1.22.2
[INFO] Git: 5f23e85
[INFO] Built: Apr 27 2026
[INFO] =================================================
[INFO] [Input] Found input driver: "x".
[INFO] [Environ] SET_PIXEL_FORMAT: RGB565.
[INFO] [Core] Version of libretro API: 1, Compiled against API: 1
[INFO] [Core] Geometry: 320x240, Aspect: 1.333, FPS: 60.00, Sample rate: 48000.00 Hz.
[INFO] [Video] Set video size to: fullscreen.
[INFO] [Wayland] Registered interface wl_compositor at version 6.
[INFO] [Wayland] Registered interface zxdg_decoration_manager_v1 at version 1.
[INFO] [Wayland] Registered interface wp_viewporter at version 1.
[INFO] [Wayland] Registered interface wp_fractional_scale_manager_v1 at version 1.
[INFO] [Wayland] Registered interface wl_shm at version 2.
[INFO] [Wayland] Registered interface wl_seat at version 10.
[INFO] [Wayland] Registered interface zwp_pointer_constraints_v1 at version 1.
[INFO] [Wayland] Registered interface zwp_relative_pointer_manager_v1 at version 1.
[INFO] [Wayland] Registered interface wl_data_device_manager at version 3.
[INFO] [Wayland] Registered interface wp_cursor_shape_manager_v1 at version 2.
[INFO] [Wayland] Registered interface zwp_idle_inhibit_manager_v1 at version 1.
[INFO] [Wayland] Registered interface wp_content_type_manager_v1 at version 1.
[INFO] [Wayland] Registered interface xdg_toplevel_icon_manager_v1 at version 1.
[INFO] [Wayland] Registered interface wp_single_pixel_buffer_manager_v1 at version 1.
[INFO] [Wayland] Registered interface xdg_wm_base at version 6.
[INFO] [Wayland] Registered interface wl_output at version 4.
[INFO] [Vulkan] Vulkan dynamic library loaded.
[INFO] [Vulkan] Found GPU #0: "Intel(R) UHD Graphics 620 (WHL GT2)".
[INFO] [Vulkan] Found GPU #1: "llvmpipe (LLVM 21.1.8, 256 bits)".
[INFO] [Vulkan] Using GPU #0: "Intel(R) UHD Graphics 620 (WHL GT2)".
[INFO] [Vulkan] Using semaphores for WSI acquire.
[INFO] [Vulkan] Queue family 0 supports 1 sub-queues.
[INFO] [Vulkan] Got 3 swapchain images.
[INFO] [Wayland] Failed to specify monitor for fullscreen, letting compositor decide.
[INFO] [Vulkan] Using resolution 1920x1080.
[INFO] [Vulkan] Using RGB565 format.
[INFO] [Vulkan] Loading stock shader.
[INFO] [udev] Pad #0: found sensor at /dev/input/event20 (accel=yes, gyro=yes).
[INFO] [udev] Pad #0 (/dev/input/event19) supports force feedback.
[INFO] [udev] Pad #0 (/dev/input/event19) supports 16 force feedback effects.
[INFO] [Autoconf] Sony Computer Entertainment Wireless (DualShock 4 v1) configured in port 1.
[INFO] [udev] Pad #1: found sensor at /dev/input/event22 (accel=yes[RX/RY/RZ], gyro=no).
[INFO] [udev] Pad #1 (/dev/input/event24) supports force feedback.
[INFO] [udev] Pad #1 (/dev/input/event24) supports 16 force feedback effects.
[INFO] [Autoconf] Nintendo Wii Remote configured in port 2.
[INFO] [Input] Found joypad driver: "udev".
[INFO] [Wayland] Enabling idle inhibitor.
[INFO] [Video] Found display server: "null".
[INFO] [Audio] Set audio input rate to: 48000.00 Hz.
[INFO] [PulseAudio] Requested 24576 bytes buffer, got 18432.
[INFO] [Audio] Started synchronous audio driver.
[INFO] [ALSA] Using ALSA version 1.2.15.3
[INFO] [Microphone] Initialized microphone driver.
[INFO] [Display] Found display driver: "vulkan".
[INFO] [Playlist] Loading favorites file: "/home/fekir/.config/retroarch/playlists/builtin/content_favorites.lpl".
[INFO] [Playlist] Loading history file: "/home/fekir/.config/retroarch/playlists/builtin/content_history.lpl".
[INFO] [Playlist] Loading history file: "/home/fekir/.config/retroarch/playlists/builtin/content_image_history.lpl".
[INFO] [Playlist] Loading history file: "/home/fekir/.config/retroarch/playlists/builtin/content_music_history.lpl".

[fekir]

Just tested Super Smash Bros Brawl; I can reproduce the same issue

[matheuswillder]

I can't reproduce this issue, I'm also using Linux with Vulkan as video driver.

However, I can reproduce the behavior if I select Quick Menu>Controls>Port 1 Controls>Device Type>Wiimote (sideways) and then, during gameplay, I press L3.

This happens because the Dolphin core introduced in #398 a shortcut to sideways toggle by pressing L3, which was the only key not mapped by default until then.

But every time the shortcut is activated, the Dolphin core shows a notification about it in the upper left corner, in yellow text, in the same way the standalone Dolphin does (it also allows mapping a shortcut to sideways toggle).

Perhaps that's what's happening?

[fekir]

Hi

No; I'm not pressing L3 (unclear to me button it is on the wiimote) and there is no notification.

I've also ensured that there is no remap file (I had one before where I configured the wiimote to be automatically sideways), so I'm not sure what else it could be.

Is there any further logging I can activate to investigate the issue?

From settings->retropad binds->port 1 I've also clicked on "Reset to Default Controls" (just to be sure)

Holding the wiimote sideays:

• wiimote sideway down seems to be mapped to right
• wiimote sideway up seems to be mapped to left
• wiimote sideway left seems to be mapped to down
• wiimote sideway right seems to be mapped to up

and it is the same mapping when holding it non-sideways

• wiimote sideway down -> wiimote left -> seems to be mapped to right
• wiimote sideway up -> wiimote right ->seems to be mapped to left
• wiimote sideway left -> wiimote up ->seems to be mapped to down
• wiimote sideway right -> wiimote down ->seems to be mapped to up

I did not notice it when reporting the bug the first time

I've also removed the whole ~/.config/retroarch directory; downloaded the dolphin core, autoconfig... and can still reproduce the described behavior.

Just FYI, after removing ~/.config/retroarch, in the retroarch UI the button 1 and 2 seem to work differently (button 1 for selecting instead of button 2, and button 2 acts as back, even if the udev/Nintendo_Wii_Remote.cfg files are the same), but I think it makes more sense to make a different issue/it might have nothing to do with the dolphin core and this issue.
I'm just mentioning it in case it helps to find the root cause.

EDIT: forget about the button 1 and 2 in the UI, the setting menu_swap_ok_cancel_buttons is responsible for it

[fekir]

Either I test it incorrectly the first time, or recreating ~/.config/retroarch changed something else.

Now I can reproduce the same issue with other controllers (for example a dualshock).

So it does not seem to be specific to the wiimote controller

[matheuswillder]

Is there any further logging I can activate to investigate the issue?

Not that I'm aware of.

Just out of curiosity, you seem to be using a real Wii Remote and a DualShock controller. Have you tried using just a keyboard? I'm not suggesting this as a workaround, but rather because, from the screenshots, there's no way to know if "Button 2" should actually be "Up", "Button 1" be "Down" and so on, it could be the other way around.

Without any game loaded, just go to Settings>Input>RetroPad Binds>Port 1 Control, and use the keyboard arrows to set Up, Down, Right, Left, A and B (these will be needed to start the game). Then load the game and see if it works correctly or if you have the same issue.

If it's normal with the keyboard, maybe something is happening with the autoconfig and it could be something to report in the RetroArch repository. If there's the same issue, I really don't know how to help you, so you'll have to wait for a developer to look into it (currently, the Dolphin core appears to be maintained by only one developer, so it may take some time and that's why I commented, thinking it was the shortcut on L3).

By the way,

No; I'm not pressing L3 (unclear to me button it is on the wiimote) and there is no notification.

L3 is one of the RetroPad keys, you also map it in Settings>Input>RetroPad Binds>Port 1 Control. When the Dolphin core starts, it uses the keys mapped there for the GameCube and Wii keys. L3 wasn't being used by either, so it as added as a shortcut to sideways toggle.

[fekir]

Just out of curiosity, you seem to be using a real Wii Remote and a DualShock controller. Have you tried using just a keyboard? I'm not suggesting this as a workaround, but rather because, from the screenshots, there's no way to know if "Button 2" should actually be "Up", "Button 1" be "Down" and so on, it could be the other way around.

just tried out; I can reproduce the issue also with a keyboard. Sorry for not testing it immediately.

Without any game loaded, just go to Settings>Input>RetroPad Binds>Port 1 Control, and use the keyboard arrows to set Up, Down, Right, Left, A and B (these will be needed to start the game). Then load the game and see if it works correctly or if you have the same issue.

This is the first screenshots; all buttons work as expected in the retroarch UI, even with the keyboard.

In the first screenshot D-PAD 2 is mapped to button 2, and in the second screenshot (mapping for the game) button 2 is mapped to up.
So it seems consistent, and is consistent when using other games (like nes games)

[matheuswillder]

I see. So it's really something you'll need to wait until a developer looks at it. There's nothing else I can think of, and since you mentioned that everything works correctly outside the core, it really must be an issue in the core itself rather than the frontend or autoconfig files.

Just a quick note: I mentioned that I'm also using Linux and Vulkan, but I forgot to mention that I'm using RetroArch installed via Flatpak, and that the stable AppImage downloaded from the official website also works without this issue (I tried it to confirm). There have been a handful of changes happening in the upstream recently, so if you're on a rolling release distro, I'd recommend stick with the stable versions offered on the official website (Flatpak, Snap, AppImage).

Good luck.

[fekir]

Thank you for the support @matheuswillder

I did not mention it, I'm using the AppImage too.
In case it matters, the Linux system is Debian.

[fekir]

I managed to recover a dolphin_libretro.so from another PC where I did not update the cores/retroarch installation for a longer timeframe (April 2023 if the timestamp is correct!).

I replaced just the core; did not touch any settings, started the game, set the remove to wiimote sideways, and it works (I'm testing just the keyboard).

file dolphin_libretro.so reports dolphin_libretro.so: ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked, BuildID[sha1]=09e8d495458358d5740d120f19299c650451150a, stripped

When loading the core in retroarch, it is labeled as 2f4b0f7.

I'm sure that the change that causes this regression in my environment is much more recent.

[fekir]

Just found out I can download retroarch appimage 1.22.2 with all cores; the packaged core works correctly.

Thus

# packaged with 1.22.2
# https://buildbot.libretro.com/stable/1.22.2/linux/x86_64/RetroArch_cores.7z
# wiimote sideways works
# retroarch reports version fd1aca3a
dolphin_libretro.so: ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked, BuildID[sha1]=0c693b7863fb713d45c41b54e7715111d77da1fb, stripped

# downloaded from retroarch UI
# wiimote sidewas does not(!) work
# retroarch reports version 2603a.0.56+0cd3bb89c2
dolphin_libretro.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=8b0078b95323bcf53ffe36c53f18e2d692d83660, stripped

@matheuswillder could it be that you tested the packaged core? It would explain why you are not able to reproduce my issue.

[matheuswillder]

@matheuswillder could it be that you tested the packaged core? It would explain why you are not able to reproduce my issue.

No, I downloaded the most up-to-date build directly from the Online Updater>Core Downloader just to try to reproduce the issue. But it was a fresh "installation", without any configuration files, remaps, etc. I just downloaded the stable AppImage package (RetroArch.7z), extracted it, opened RetroArch, downloaded the Dolphin core, downloaded the Core System Files, and then I just loaded the game (I don't have controllers, I always play using a keyboard due to health issues). It works correctly.

Just found out I can download retroarch appimage 1.22.2 with all cores; the packaged core works correctly.

This means it was some change after the last stable update on 2025-11-20. If you want, you can compile directly from the source in the merged PRs to try and find the culprit. But of course, it's up to you whether you have the free time to do that or not.

In case it matters, the Linux system is Debian.

I'm also a Debian user lol

Edit: I have a strong feeling. Download the nightly build of RetroArch from http://buildbot.libretro.com/nightly/linux/x86_64/, open it, go to Settings>Input>Motion/Light Sensors, disable Auxiliary Sensors Input, go back to the Main Menu and Quit RetroArch just to be sure, open it again and download the updated core build (Online Updater>Core Downloader), download the Core System Files (Online Updater>Core System Files Downloader, the Dolphin core doesn't work correctly without this), then load the game, change the Wiimote to sideways and see if you can still reproduce the issue.

[fekir]

@matheuswillder I've disabled "Auxiliary Sensors Input" as you suggested, and now Wiimote sideways works as it used to be.

If I enable it again, then wiimote sideways is broken again.

I did not need to download the nightly version.

Still unclear why I have this issue and you do not.

[matheuswillder]

As I suspected.

Still unclear why I have this issue and you do not.

Either your system is seeing a sensor that doesn't exist, or your hardware actually has a sensor that mine doesn't (or at least, that my system doesn't see).

But in any case, I think it's safe to say that this isn't a bug in the Dolphin core, but in RetroArch. Support to real sensors was added when #414 was merged (that's why the archived version of the core works correctly, since it predates this PR), but it depends on support from the drivers on the frontend/RetroArch, so I think the best way to investigate and fix ths would be to open an issue there.

Good luck.

[fekir]

But in any case, I think it's safe to say that this isn't a bug in the Dolphin core, but in RetroArch.

I'll try to open a bug there, but isn't there the possibility that it has been integrated incorrectly (granted I know nothing about the codebase/architecture).

If I'm using a real wiimote, which has a sensor, I would expect Wiimote sideways to work correctly if I select it as option.