RetroArch
RetroArch copied to clipboard
Next version 1.19.2 will be released before of december ?
Hello. Not demanding to release the next version. Only want information when will be released Retroarch next version. Thus avoid to download files all time being the same version with few changes.
Have an nice week.
Sorry, no ETA.
Hey, not asking for an ETA if there isn't one tucked away that I've missed. However, 1.19.1 was released in June and the best I can tell is that it's completely broken on the Steam Deck. I can't make it more than 15 seconds or so without getting hammered with the Vulkan swapchain issue. If I'm super fast, I can get into a game but if I bring up the core menu I have to force close the app. I know there's a commit to fix that... It'd be nice to get a fix rolled out for it, considering it appears to be a major breaking bug on the SD platform.
There will likely be a new version in December.
Out of interest though how to reproduce this issue you speak of? I switched to the Vulkan renderer on a Steam Deck OLED, I started up the ScummVM core, I selected 'Start Core' and it seems to work just fine.
This is with version 1.19.1, git version 0792144fe3
I've tried about every config variation that could have an impact on rendering (minus switching the menu) and nothing appears to alleviate it, I'll get you a config file and debug log. Cores seem to run fine, xmb seems to stall constantly.
I'm trying to set up a new Steam Deck OLED Limited Edition I just received. RetroArch installed from flatpak using Discover. Wonder if there's a subtle variation in the hardware that makes it more susceptible (or if I'm an idiot and have a misconfig somewhere).
I've tried about every config variation that could have an impact on rendering (minus switching the menu) and nothing appears to alleviate it, I'll get you a config file and debug log. Cores seem to run fine, xmb seems to stall constantly.
I'm trying to set up a new Steam Deck OLED Limited Edition I just received. RetroArch installed from flatpak using Discover. Wonder if there's a subtle variation in the hardware that makes it more susceptible (or if I'm an idiot and have a misconfig somewhere).
Well honestly that is not really the usecase we are aiming for with Steam Deck. I mean you can try the Flatpak version on your own (I don't see why TBH) but we just assume you are installing it through Steam itself. That version at least seems to work for me.
Aren't there weird core limitations via the Steam version? Thought there was something odd about it compared to how RetroArch typically runs on PC. Maybe that was just a long time ago and that's no longer the case.
I dunno why you would go out of your way to use it on your Steam Deck in a non-Steam Store way TBH.
I'm not aware of core limitations per se, if anything I'd imagine the Flatpak version would have more issues just by nature of how it strives for a certain amount of backwards compatibility between several distros.
Welp, can't hurt to try it I guess. Will get you logs and a config for the flatpak install regardless in case it helps with anything else. Can say that I had (probably an older version) RetroArch installed on a release day Steam Deck 512GB via flatpak and it ran great. I'll have to dig it out and see what version it's running.
I dunno why you would go out of your way to use it on your Steam Deck in a non-Steam Store way TBH.
I know my way around Linux, have been using RetroArch for years, and wanted to avoid as many differences between what I run on my PC vs. the Deck. Infrastructure engineer... Huge fan of standardization. Also, and I forgot about this because it was nice not to have to worry about it so I quit thinking about it, running it as a flatpak allows you to run a Steam game on your PC and still run RetroArch on the Deck without kicking you off your game on your PC. Just tried to fire up RetroArch via the Steam Store and it's yelling at me to terminate my PC session.
retroarch__2024_11_28__02_38_56.log retroarch.cfg.txt Logs don't really show anything other than where Vulkan dies. Don't need to be doing anything in particular to trigger it. Moving left, right, up, down, in, or out of any menu seems to be enough to cause it. Will try the Steam version and see what happens.
@DarkRider1768 Is it reproduced in version 1.21.0?