Auto-Save function not working properly on console?

Four_Fingers · June 27

Yep, deleting the saved game data file, (you know the one that doesn't exist lol), and rebuilding the PS database usually fixes problems with the file as it gets recreated. Downside is you have to set al your characters options again.
Caused by file corruption or worst case failing SSD.

festegios · June 27

fizl101 wrote: »

festegios wrote: »

The solution is to delete your game data (not the game itself)

This doesn’t affect anything to do with your actual eso account.

Source: me; had the same issue. Also second source; me, a PlayStation expert.

Unfortunately I have done, a few times. I think it is related to saving settings in addons as it only started happening after we could use addons for me

And you’ve removed your add ons?

katanagirl1 · June 28

Is this a message about the cloud storage autosave for PS? It sounds similar to something I had happen with another game.

Hotdog_23 · June 28

demonology89 wrote: »

Yes, I have also deleted my saved game data 3x now and this error keeps coming back.

Same here, the number of saved errors did decrease but after a day or two they are back to happening all the time now. Really hope someone at ZOS looks into this and offers some kind of solution. Deleting our saved data daily does not seem like a real solution.

Stay safe

BuffNukem · June 28

For me these things below aren't being saved and reappear every time I log back into any character. I'm on XBox-NA. These issues are occurring on all my accounts regardless if they have ever touched add-ons or not.

- Guild trader recent searches - All searches lost every time I log out of a character.
- Notifications that have previously been acknowledged/cleared. Example: a notification that a house is in Home Tours
- Notification Pop-up at the character select screen that the Zeal of Zenithar event is active
- (For my accounts that don't have the 2025 Content Pass) Notification Pop-up to enter a code or skip

I'm sure there are more, but these have been the most frustrating items that keep occurring over and over.

lasseb16_ESO4 · June 28

The issue is with one or more of the addons. You will have to kill and restart the game, then on character selection go into options and disable all addons, then enable one addon at a time, log into a character and then immediately back out, this will trigger the auto save and you will get the error immediately if the addon you enabled is causing this issue. You will eventually get the error in-game as well, but it is triggered immediately upon logging out. Right now, the behavior if I have a problematic addon enabled is that I log back out, I get the Zenithar event popup, and when I dismiss it I immediately get the save error. This is a much quicker way to figure out which addon is the culprit than to stay in-game and wait for it to happen ... or not.

Currently I have this error if Quest Mover is enabled, but there have been others. I have not found any other way to completely fix the issue other than to kill and restart the game, and then to disable the offending addon.

Enabling the "Advanced UI Errors" in the addon meny does not give any more information either.

This on PS5 though, my brother on Xbox does not have the issue with the Quest Mover addon, so it might either be yet another platform difference, or the combination of Quest Mover + another addon or two might be the issue here.

lillybit · June 29

lasseb16_ESO4 wrote: »

The issue is with one or more of the addons. You will have to kill and restart the game, then on character selection go into options and disable all addons, then enable one addon at a time, log into a character and then immediately back out, this will trigger the auto save and you will get the error immediately if the addon you enabled is causing this issue. You will eventually get the error in-game as well, but it is triggered immediately upon logging out. Right now, the behavior if I have a problematic addon enabled is that I log back out, I get the Zenithar event popup, and when I dismiss it I immediately get the save error. This is a much quicker way to figure out which addon is the culprit than to stay in-game and wait for it to happen ... or not.

Currently I have this error if Quest Mover is enabled, but there have been others. I have not found any other way to completely fix the issue other than to kill and restart the game, and then to disable the offending addon.

Enabling the "Advanced UI Errors" in the addon meny does not give any more information either.

This on PS5 though, my brother on Xbox does not have the issue with the Quest Mover addon, so it might either be yet another platform difference, or the combination of Quest Mover + another addon or two might be the issue here.

I've never installed quest mover so this isn't my problem (I'm on PS5 too). I've managed to stop the error and reinstalled most of my addons and the culprit for me definitely seems to be Auto recharge and Repair and/or LibChatMessage. I've got guildies who can’t use the mini map tho but that's fine for me.

There seems to be things that are more likely to trigger it but I do feel like it's random conflicts, probably combined with base game issues - even before addons were enabled there were saving problems such as the 'quest only' crafting setting not being saved, popups like the one for the content pass on login happening every time when they'd usually only pop up once, missing guild trader histories. Hopefully we'll get an incremental patch to fix these soon and with a little luck the addons will be more stable then too!

Charden2016 · June 30

lasseb16_ESO4 wrote: »

The issue is with one or more of the addons. You will have to kill and restart the game, then on character selection go into options and disable all addons, then enable one addon at a time, log into a character and then immediately back out, this will trigger the auto save and you will get the error immediately if the addon you enabled is causing this issue. You will eventually get the error in-game as well, but it is triggered immediately upon logging out. Right now, the behavior if I have a problematic addon enabled is that I log back out, I get the Zenithar event popup, and when I dismiss it I immediately get the save error. This is a much quicker way to figure out which addon is the culprit than to stay in-game and wait for it to happen ... or not.

Currently I have this error if Quest Mover is enabled, but there have been others. I have not found any other way to completely fix the issue other than to kill and restart the game, and then to disable the offending addon.

Enabling the "Advanced UI Errors" in the addon meny does not give any more information either.

This on PS5 though, my brother on Xbox does not have the issue with the Quest Mover addon, so it might either be yet another platform difference, or the combination of Quest Mover + another addon or two might be the issue here.

I have disabled and uninstalled all addons before deleting saved date, and then reinstalling the game as a whole. Immediately after logging, without even touching addons, trying to switch my in game settings, I get the autosave error. NOTHING is working for me. This is not a 'PS5' issue, as Zos likes to state in their technical support. This is an issue on ZOS's end of things. The fact that they haven't even acknowledged it is kind of abysmal

Brossin · June 30

So my experience so far is that I was getting this error on the character select screen and logged into pretty much all of my characters as far as I could tell. Once it occurs on a character, I was able to reproduce it by opening the in game map and closing it (other actions triggered it as well). I uninstalled ALL ADDONS and completely closed / reopened the game and the issue still occurred. My take is that the addon functionality seems to have caused it, but it seems like it's corrupting the save data in cloud storage and local.

I took the nuclear option Friday and completely uninstalled the game, deleted cloud and local save data, then reinstalled it. All has been fine until probably 15 minutes ago when I just received the error again. I don't feel like it's causing the issue, but probably worth mentioning that I was on my ps portal when I received it this last time. I also have 2 other people in my relatively small guild experiencing the same issue.

I get that we just received addon support, but this really does need to have some ZOS feedback at least acknowledging it, as it is very disruptive to receive this issue non-stop while doing end game content.

Edit: Changed scope, as it happens at character select and logged into characters.

demonology89 · June 30

Yes some acknowledgement from ZOS would be great. I'm really tired of deleting and resetting only for the error to keep coming back.

DenverRalphy · July 2

lillybit wrote: »

lasseb16_ESO4 wrote: »

The issue is with one or more of the addons. You will have to kill and restart the game, then on character selection go into options and disable all addons, then enable one addon at a time, log into a character and then immediately back out, this will trigger the auto save and you will get the error immediately if the addon you enabled is causing this issue. You will eventually get the error in-game as well, but it is triggered immediately upon logging out. Right now, the behavior if I have a problematic addon enabled is that I log back out, I get the Zenithar event popup, and when I dismiss it I immediately get the save error. This is a much quicker way to figure out which addon is the culprit than to stay in-game and wait for it to happen ... or not.

Currently I have this error if Quest Mover is enabled, but there have been others. I have not found any other way to completely fix the issue other than to kill and restart the game, and then to disable the offending addon.

Enabling the "Advanced UI Errors" in the addon meny does not give any more information either.

This on PS5 though, my brother on Xbox does not have the issue with the Quest Mover addon, so it might either be yet another platform difference, or the combination of Quest Mover + another addon or two might be the issue here.

I've never installed quest mover so this isn't my problem (I'm on PS5 too). I've managed to stop the error and reinstalled most of my addons and the culprit for me definitely seems to be Auto recharge and Repair and/or LibChatMessage. I've got guildies who can’t use the mini map tho but that's fine for me.

There seems to be things that are more likely to trigger it but I do feel like it's random conflicts, probably combined with base game issues - even before addons were enabled there were saving problems such as the 'quest only' crafting setting not being saved, popups like the one for the content pass on login happening every time when they'd usually only pop up once, missing guild trader histories. Hopefully we'll get an incremental patch to fix these soon and with a little luck the addons will be more stable then too!

Yeah, I think perhaps it's the framework to allow addons itself that is at fault here. The crafting tables and map settings stopped remembering their states between character logins the moment U46 landed, even when addons were not yet enabled. After they flipped the switch and turned the addons framework on so to speak, the addons themselves now simply highlight an underlying issue.

Perhaps @ZOS_Kevin can find an update on this issue.

Dwedan · July 4

I am also having this issue, I have deleted the game, the save data, cleared the console cache, rebuilt the data base; the issue is persistent.

DenverRalphy · July 4

It's getting worse each day for me. Today I've even disabled all add-ons, and it's still happening. Often enough now that I dread any action that requires using the main UI menu because there's a good chance it'll pop again.

blckrose · July 6

how is this still an ongoing issue that is heavily reported yet still no fix or even an acknowledgement from ZOS?

it most definitely is affecting game play as i get tired of not being able to immediately play the game. for every single toon swap, im having to redo setting, even account wide every single time. SOS

lillybit · July 6

blckrose wrote: »

how is this still an ongoing issue that is heavily reported yet still no fix or even an acknowledgement from ZOS?

it most definitely is affecting game play as i get tired of not being able to immediately play the game. for every single toon swap, im having to redo setting, even account wide every single time. SOS

There's a patch on Wednesday so we'll see how it is after that

DenverRalphy · July 6

lillybit wrote: »

blckrose wrote: »

how is this still an ongoing issue that is heavily reported yet still no fix or even an acknowledgement from ZOS?

it most definitely is affecting game play as i get tired of not being able to immediately play the game. for every single toon swap, im having to redo setting, even account wide every single time. SOS

There's a patch on Wednesday so we'll see how it is after that

Wednesday's patch is primarily for removing the Vengeance campaign from Cyrodiil. Whether it has bug fixes remains to be seen.

lillybit · July 6

DenverRalphy wrote: »

lillybit wrote: »

blckrose wrote: »

how is this still an ongoing issue that is heavily reported yet still no fix or even an acknowledgement from ZOS?

it most definitely is affecting game play as i get tired of not being able to immediately play the game. for every single toon swap, im having to redo setting, even account wide every single time. SOS

There's a patch on Wednesday so we'll see how it is after that

Wednesday's patch is primarily for removing the Vengeance campaign from Cyrodiil. Whether it has bug fixes remains to be seen.

I'd be surprised if that's all it is as they didn't need a patch to start it and that was adding something totally new, not just reverting to the same old same old

Charden2016 · July 8

blckrose wrote: »

how is this still an ongoing issue that is heavily reported yet still no fix or even an acknowledgement from ZOS?

it most definitely is affecting game play as i get tired of not being able to immediately play the game. for every single toon swap, im having to redo setting, even account wide every single time. SOS

Same. I've gotten to the point that ive basically memorized the slider positions for everything. It's ridiculous. And some things are reverting even when I swap characters not when I log out. It's bad. @ZOS_Icy @ZOS_Phoenix @ZOS_Kevin is this issue being investigated? It seems to be a back end issue with ESO, not with addons, ass the issue persists even with addons disabled and it began when update 46 hit. Also, as it is happening across different consoles, it is not solely a Playstation issue.

redlink1979 · July 8

I got this error once on PS NA. I have nothing and it fixed itself.

lillybit · July 8

redlink1979 wrote: »

I got this error once on PS NA. I have nothing and it fixed itself.

I've had it a couple of times randomly when I haven't changed/installed anything, a restart will fix it then. When it's after an addon being installed it doesn't seem to just go away again

DenverRalphy · July 10

Sooo... no joy on yesterday's patch.

Has anybody tried to compile a list of addons that will trigger the autosave error messages? I've learned the hard way that if you get the error when you're at the character select, or initial game client window, don't accidentally click the back button. Because otherwise all of your in-game options settings will be restored to its virgin state. Leaving you with having to configure and set all of your options all over again.

blckrose · July 11

lillybit wrote: »

blckrose wrote: »

how is this still an ongoing issue that is heavily reported yet still no fix or even an acknowledgement from ZOS?

it most definitely is affecting game play as i get tired of not being able to immediately play the game. for every single toon swap, im having to redo setting, even account wide every single time. SOS

There's a patch on Wednesday so we'll see how it is after that

well it’s friday & still having the auto save crap happening. this is unbelievable 😩

MasterOfWisdom1618 · July 11

Is there any updates from the ESO staffs here besides the complains about the players?

The solutions on the support page (https://help.elderscrollsonline.com/#en/answer/57626) didn't work out for me and refering instead to Playstation Customer Service is not helpful at all.

DenverRalphy · July 11

MasterOfWisdom1618 wrote: »

Is there any updates from the ESO staffs here besides the complains about the players?

The solutions on the support page (https://help.elderscrollsonline.com/#en/answer/57626) didn't work out for me and refering instead to Playstation Customer Service is not helpful at all.

As of yet, we haven't even had a response from anybody at ZOS even acknowledging that they're aware of the bug. Playstatoin customer support wouldn't be of any use since it's a game flaw, not a console flaw. As well it affects both Xbox and PS.

And given that it's not really feasible that they're not aware of it, the total silence is likely intentional.

MasterOfWisdom1618 · July 11

DenverRalphy wrote: »

MasterOfWisdom1618 wrote: »

Is there any updates from the ESO staffs here besides the complains about the players?

The solutions on the support page (https://help.elderscrollsonline.com/#en/answer/57626) didn't work out for me and refering instead to Playstation Customer Service is not helpful at all.

As of yet, we haven't even had a response from anybody at ZOS even acknowledging that they're aware of the bug. Playstatoin customer support wouldn't be of any use since it's a game flaw, not a console flaw. As well it affects both Xbox and PS.

And given that it's not really feasible that they're not aware of it, the total silence is likely intentional.

I heard from various sources that ZOS is not good at all at communication but let's see how they will handle that problem.

ZOS_Kevin · July 14

Hi all, just wanted to follow up on this. We are working on getting some additional reporting tools to help the team resolve this issue. The team is aware and working toward a solution here. We’ll follow up once we have more information.

Timing wise, earliest we are looking at a fix is in U47. But that depends on some tracking factors.

allochthons · July 14

ZOS_Kevin wrote: »

Hi all, just wanted to follow up on this. We are working on getting some additional reporting tools to help the team resolve this issue. The team is aware and working toward a solution here. We’ll follow up once we have more information.

Timing wise, earliest we are looking at a fix is in U47. But that depends on some tracking factors.

Thank you for the response, @ZOS_Kevin.

But we've been dealing with this for 3 weeks. We've made
Multiple
Posts
About it.

We've put in tickets, we've put trouble-shooting info in these threads. We're doing our part.

And this is the first time we've gotten acknowledgement that this was a new, impactful issue, and not the old issue, for which the fix does not work.

ZoS has said it's trying to improve communication. This is exactly what we're talking about. We need acknowledgement of issues like this much faster. My guilds are beyond frustrated with this error. We've been waiting for add-ons for literal years, and to have them malfunction like this is heart-breaking.

ZOS_Icy · July 14

Greetings,

This thread has been moved to the Bug Reports section, as it is better suited there.

The Elder Scrolls Online Team

katanagirl1 · July 14

This may take some work to figure out which addon might be causing the problem or what to do about it. I only have two addons installed and haven’t had any problems yet, so it is not everyone.

allochthons · July 14

katanagirl1 wrote: »

This may take some work to figure out which addon might be causing the problem or what to do about it. I only have two addons installed and haven’t had any problems yet, so it is not everyone.

Yeah, I understand. I have been part of the quality control of software products, and I know some bugs are harder to track down and fix than others. That's not why I'm speaking up.

Prior to the console add-on update, I had gotten the save error maybe twice in 5-6 years of playing. Now I'm getting it at least every other day, and once I got it twice in one day. I've now written down every change I need to make after deleting the local save file, not to mention all the customizations I'm making to the add-ons. I've pulled the power plug on my PS5 to do a reset. I've deleted the cache, and rebuild the data-base, and I've sent in multiple tickets through in-game bug reporting. All trying to figure out what's going on. I've gone through my add-ons enabling and disabling them systematicaly trhing to figure out if it's one particular one causing the problem. (It's not.) Because we had no feedback.

Now that there's feedback, we can spend our time more productively. We can just disable/uninstall add-ons until there's a fix, or leave them enabled but not saving any changes, or choose to go through deleting the local save file, because it does fix the problem. For a few hours or a day, maybe. But now we know, and can make informed choices.

That's all I want. The acknowledgment that the issue is known, it's being worked on, and it's not on us or the add-on authors.