You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am having issues with pokemon games, specifically an emerald rom hack, throwing the dry battery error on steamdeck. I can save and such so I am not sure why this is happening as another issue seemed to imply the rtc data is stored in the .Sav file and it seems to be able to edit that. I have tried adding a year to the offset and changing the rtc setting in options to gba from auto but the error persists.
The text was updated successfully, but these errors were encountered:
xy172
changed the title
Issue with etc on steamdeck
Issue with rtc on steamdeck
Jan 12, 2024
Do you know the name of the Pokemon Emerald ROM hack? I would probably need access to it in order to debug any issues.
Keep in mind that I'm not involved with any pre-packaged version of GBE+ on the Steam Deck. I know it's available for download in SteamOS's desktop mode on the Steam Deck, but I have no role in that. If there's an issue with GBE+ due to the way others have packaged it for the Steam Deck, you'd probably have to talk to them.
However, I would like to verify this issue and see what's causing it before anything else.
Sure, sorry I ment to say it in the original post, pokemon quetzal is the rom hack. It doesn't matter in the end anyways because we were hoping for link cable support since it has multiplayer but I realized your link cable support was not for gba so we couldn't use your emulator anyways.
I am having issues with pokemon games, specifically an emerald rom hack, throwing the dry battery error on steamdeck. I can save and such so I am not sure why this is happening as another issue seemed to imply the rtc data is stored in the .Sav file and it seems to be able to edit that. I have tried adding a year to the offset and changing the rtc setting in options to gba from auto but the error persists.
The text was updated successfully, but these errors were encountered: