UI Error

MorninStar

Can't figure out what this UI error belongs to. I tried disabling addons but, it wasn't any of them.

Necrotech_Master

usually when the error comes from the /EsoUI/* directory, that is a base game built in thing that is messing up

it looks related to the activity finder, but i dont think ive seen this one come up myself, is this something that is consistently happening for you?

MorninStar

This started with the last patch. It won't go away and if I try to play through it, I can't move, exit game or anything. I end up hard closing the game. I've tried a repair on the client through the launcher and that didn't help either.

Necrotech_Master

do you know what you were trying to do when the error would come up?

MorninStar

I wasn't doing anything, it pops up as soon as I load any character.

Necrotech_Master

i have no idea then, but can confirm that this UI error is from the base game stuff and not addon related (especially if you already tried disabling addons)

ill ping @ZOS_Kevin @ZOS_GinaBruno to pass this along

MorninStar

ok so after disabling all addons( again) and painfully turning them back on one by one I found the problem to be Group & Activity finder extensions. Disabled it until it's fixed. Thank you for the help.

Necrotech_Master

funny that you mention it, i was using this addon for awhile because i liked it, but i noticed it stopped working with the lost depths dlc (U35) because it had not been updated to account for the new dungeons, so if you went to the dungeon queue and tried to change to go to the select individual dungeons, the list would be cut off before it even finished going through all the normal dungeons, effectively making it impossible to queue for individual dungeons

i ended up just getting rid of it when it went 2 full updates without getting any updates because it was unusable outside of the auto accept queue functionality

edit: i also find it odd that it was triggering a base game UI error instead of an error related to this specific addon

ZOS_Bill

Thank you for the update and that this issue was add-on related. With the issue now resolved, we are going to close this discussion.