UI Error

SonOfSoma

This is so frustrating!
How are we supposed to enjoy the upcoming undaunted event when everytime we log into a dungeon the error appears. Which can't even be removed without exiting the game and reloading!!!

Totally depressed!

markulrich1966

I get it using a wayshrine and teleporting to homes (xbox EU and NA).

Well, not "totally depressing" as you just have to press 1 button to dismiss the message, but looks pretty "beta".

mzprx

this happens to me when i accept the random normal and have the controller UI switched on (i play on a PC using controller). so when i'm queued for a random normal dungeon (or any dungeon for that matter) i switch back to "normal PC UI". it doesn't happen any more. i do believe it's the controller UI that does this (in my case), as there is a mention of controller in that UI Error note. maybe it's the same for you. if it is switching the controller off for the duration of the queue should fix it..

but yeah, another "new and exciting feature". i fear it's going to get the same treatment as the "weapon surfing". you know, when your weapons appear below your feet instead of in your hands. we've had that one for how many years and it's been reported how many times? but since we, the players, have found a "hotfix" (switching the Polymorph helmet off) no one cares to fix it. this UI error (if it's the controller "version") is fixable by switching the controllef UI off, so they will probably never fix it either..

Gray_howling_parrot

markulrich1966 wrote: »

I get it using a wayshrine and teleporting to homes (xbox EU and NA).

Well, not "totally depressing" as you just have to press 1 button to dismiss the message, but looks pretty "beta".

I've only gotten it a couple times now after the update and it doesnt allow me to hit any buttons to dismiss it - have to close out the game and relog

SonOfSoma

I'm on XBox and there is no way of removing the message, unless logging out.

I'm getting it using wayshrines, tping to dungeons, actually just travelling anywhere.

TragedyOA

I'm getting too.
Last night the UI disappeared, had to force close game.

TragedyOA

TragedyOA wrote: »

I'm getting this too.
Last night the UI disappeared, had to force close game.

markulrich1966

today I no longer got the UI error at shrines and teleporting, seems it was an xbox cache issue.

kmcaj

I get this error on xbox and ps5 after any load screen after character is logged in. Can't clear without closing game down.

Veinblood1965

I started getting an error on PS4 this weekend when zoning into Moongrave Fane each and every time and a few other zones. Nothing worked, no buttons, nothing. I did have my UI sort of invisible so I could see things behind the error and found a way to get it to disappear. I moved to the exit in MF and selected X or if at a Wayshrine I selected X on the wayshrine. After about 30 seconds the UI error would go away.

Raammzzaa

I’ve had the UI error several times now, and I always spam A (on Xbox) to exit the message so I goes away. Once I’ve had it it usually keeps coming back though until I close the game and clear the save data.

Diundriel

SonOfSoma wrote: »

I'm on XBox and there is no way of removing the message, unless logging out.

I'm getting it using wayshrines, tping to dungeons, actually just travelling anywhere.

rip probably gotta switch to pc to install an add-on that stops it ... haven't had one in 8 years

xosaara137ox

markulrich1966 wrote: »

today I no longer got the UI error at shrines and teleporting, seems it was an xbox cache issue.

It’ll be back. It clears it for some time, but it doesn’t stop it from happening.

Kavar162

I get the error basically every zone change (PS4 NA). I noticed that getting into combat usually removes the window, and repeatedly pressing X also removes it. Waiting is usually a long wait for me (5+ mins to disappear on its own). Just wanted to through this out there for anyone looking for ways to get rid of the error message without logging.

ZOS_Hadeostry

Hey there,

Due to there already being a thread discussing UI errors in the Bug Report Category, we are going to close this down so that you may continue the discussion here. Thank you for your understanding.