Retroarch Vulkan without VSync, frozen when there's no mouse movement

RetroArch Linux devices
#1

Hello, have had Retroarch on my system for a bit. After a system update a while back, Vulkan broke in a weird way. Without VSync active, Retroarch is frozen unless there’s mouse movement occurring. This applies to the menu and in cores. Also only occurs with Vulkan as the active video driver.

With VSync enabled in the menu, it’s normal unless fast forward is enabled, where the specific freezing conditions stated earlier occur, I assume this is because fast forward disables VSync so it can speed up the game. Anyone know any potential fixes? PC specs and OS/related drivers are listed in my about me. Would upload my config, but currently only allowed to upload image files here.

1 Like
#2

I just experience the same issue as well, since updating the system (after over a month no update). I am also on an Arch based system with newest Kernel 6.16. Someone else made a bug report and is also on an Arch based system… so there could be a pattern: https://github.com/libretro/RetroArch/issues/18217

Edit: Oh a developer responded and told us the issue was already fixed in current code base. So then we need to wait for an update from Arch team… which can take even months. I might finally switch to the Flatpak version that is always up to date and provided by the RetroArch team.

#3

Hey there,

Dont know if it’ll help, but I went back to using gnome with X instead of Plasma Wayland on my Arch install when using Retroarch on that machine. Last update I did a week or two ago made the games stuttering, but since that wasnt the first time I had problem with Wayland and other softwares like OBS, I already had X reinstalled and log off and then back on with the other compositor.

But I admit I didnt search thoroughly about the issue, so take that with a pinch of salt. Thanks for hinting at the flatpak package being a bit more up to date, I need to take a look at that as well!

#4

I’m not going back to X at all, so that is not an option for me. It would help in this case though, because this is an issue with Wayland, not on X (as far as I know).

For the Flatpak however I am not sure how its actually handled. Do they update it with minor versions? Or is it only updated when having a big release maybe? In Flathub it says version “1.21.0”, so the problem might be there still. Developer recommends instead to build from source to see if the problem persists. So I just wanted to clarify this (or mystify if it was clear before).

1 Like
#5

Crystal clear, will try to build from source on Arch at some point if the problem persists on the next updates.

1 Like