Patch 2.0.6, UI Error on game mail

Ageless

When going from Mail to Send I get a UI error.

assertion failed
stack traceback:
	[C]: in function 'assert'
	EsoUI/Libraries/ZO_KeybindStrip/ZO_KeybindStrip.lua:174: in function 'ZO_KeybindStrip:AddKeybindButton'
	EsoUI/Libraries/ZO_KeybindStrip/ZO_KeybindStrip.lua:287: in function 'ZO_KeybindStrip:AddKeybindButtonGroup'
	EsoUI/Ingame/Mail/MailInbox.lua:33: in function 'callback'
	EsoUI/Libraries/Utility/ZO_CallbackObject.lua:104: in function 'ZO_CallbackObject:FireCallbacks'
	EsoUI/Libraries/ZO_Scene/ZO_Scene.lua:248: in function 'ZO_Scene:SetState'
	EsoUI/Libraries/ZO_Scene/ZO_SceneManager.lua:155: in function 'ZO_SceneManager:ShowScene'
	EsoUI/Libraries/ZO_Scene/ZO_SceneManager.lua:430: in function 'ZO_SceneManager:OnSceneStateChange'
	EsoUI/Ingame/Scenes/IngameSceneManager.lua:278: in function 'ZO_IngameSceneManager:OnSceneStateChange'
	EsoUI/Libraries/ZO_Scene/ZO_Scene.lua:249: in function 'ZO_Scene:SetState'

I get this same error when I move back to the Inbox. After that I cannot use either the Inbox or the Send window, they're both empty.
Exiting and restarting the mail fixes that.

I've had these errors back in 2.0.4 as well.

ZOS_MollyH

Hi @Ageless ! Have you tried running a repair on your game client?

Ageless

ZOS_MollyH wrote: »

Have you tried running a repair on your game client?

Is that the standard question, the standard solution, when after an update things go wrong that people should run a repair on their game? To answer you, no, I have not run a repair on the game and I am not going to run a repair on the game either.

For the past 4 weeks, I've run 17 repairs on the game to try to fix the various Manifest errors. I fixed those simply by not starting the game with the Launcher. I solely use the Launcher to update the game, then it's exit Launcher, start Eso with the shortcut on my desktop to Eso.exe in the NA directory.

Aside from the 17 repairs, I have also been sitting through a complete redownload of all 40 gigabytes of the game and reinstall of the game, this due to the launcher not liking me deleting what appeared to be key files, while following one of the ZOS FAQs on how to fix the Manifest errors.

I must say, downloading and installing the 40GB again was faster than installing GTA 5 PC from 7 DVDs and then sitting waiting for 7 hours for its launcher to download the last 5 GB and patches. But then launch day of Eso wasn't so spotless either.

I have no problem with the UI error. When I get it, I exit the mail and restart it. That usually fixes it, until a next time that I run into that UI error again. I merely reported it in a ticket and here on the forums to point out that things may not all be hunky dory in this piece of software's code. Why you give us a UI error and option to copy the code, when the standard is always to repair the game, is beyond me.

But point taken: any next error I get I won't post on the forums.

ZOS_MollyH

Greetings!

When there is an error that could potentially be due to missing textures, or corrupt data, a repair refreshes the files in your system to ensure they're up to date. For errors like these, that is the first recommendation to make sure you have a clean installation to work with before any further troubleshooting advice continues. As always, the best way to ensure that errors are reported to Customer Support or to our engineers, please be sure to use /bug or /help in game. While we can provide basic troubleshooting on the forums, if you do require more in-depth support both of those options are your best way to receive it.

Ageless

ZOS_MollyH wrote: »

When there is an error that could potentially be due to missing textures, or corrupt data, a repair refreshes the files in your system to ensure they're up to date.

Which in normal circumstances would be fine, but it always happens directly after a game patch update. Which would then mean that the corruption happens due to the patch code.

One option you could force through is for the launcher to auto-repair the game after each patch. Because really, when such an error happens on one build, not on the next, but again on the build thereafter, it's highly unlikely it's something that the user did.

I assume that when repairing the game the same patch files are used that are installed during the patch day, not that earlier or the very first game files are used? If so, then why not have some users who have these problems test out various patches prior to Patch Day to see what in the patches causes this from your end? I'd be willing to sign up for that. If it betters the game and makes sure that others don't have to repair their game after each forced update they get?