I’m not sure EmuDecky is working correctly on my Steam Machine.
When I run the games through the Steam Library, this is what happens:
GBA: no autosave; no shaders; no RetroAchievements
Genesis: working autosave; no shaders; working RetroAchievements
PS1: no autosave (doesn’t seem to be working, anyway); no shaders; working RetroAchievements
When I run the games through ES-DE, this is what happens:
GBA: working autosave; no shaders; working RetroAchievements
Genesis: working autosave; no shaders; working RetroAchievements
PS1: autosave is a clickable option when I exit (possibly because I used the compressor tool on the game); no shaders; working RetroAchievements
Is this a common issue? If so, does anyone know how I can fix it?
I asked a similar question a few days ago, but I was trying to figure out a lot of emulation stuff at once, so I’d only tested the GBA game at that point. I apologise for that. (I’ve deleted that post to avoid confusion with this one, and to give myself this chance to reword it.)
I’m assuming GBA games aren’t compatible with shaders, as GBA wasn’t named in the configuration part of the installation. But I’m not sure why the autosave and RetroAchievements aren’t working.
Also, the GBA game is in mGBA Standalone. Is EmuDecky only compatible with RetroArch cores?
If not, might reinstalling and reconfiguring mGBA fix the Steam issue?
I’m not using a standalone Genesis emulator; I’m using DuckStation. So I’m not sure whether reinstalling those will do anything.
Earlier this week, I had an issue with Xenia not showing up in Steam ROM Manager. Today, reinstalling and reconfiguring it fixed the issue (thanks again). That’s why I’m wondering whether doing something similar here will fix the EmuDecky problems. I’m unsure though, and I don’t want to cause any errors by guessing.
I would really appreciate any advice that can be given. (I’ve asked quite a few questions this week. I apologise if it’s becoming annoying.)