Weird but minor issue immediately after log-in

Iselin2 · September 2020

Not sure if this has been flagged before but I'm experiencing something weird right after log-in and before I get the screenshot on the way to the character select screen:

It kind of hangs after log-in and the blue loading swirl stops dead but if I alt-tab and then alt-tab right back I get the screenshot and then shortly after the character select screen.

The weird part is I can't think of any reason why alt-tab would "fix" this.

Running the game at 4K but then downsampled to 1440P using the Gforce Experience DSR setting.. if that makes a difference.

ZOS_Bill · September 2020

@Iselin2

When did this first start to happen?

Running a repair through the ESO Launcher may help in getting this loading issue to stop happening.

Iselin2 · September 2020

ZOS_BillE wrote: »

@Iselin2

When did this first start to happen?

Running a repair through the ESO Launcher may help in getting this loading issue to stop happening.

I can try that but basically it's a fresh install. I was away from the game for a while and just installed it fresh on a new PC last week.

ZOS_Bill · September 2020

@Iselin2

Thank you for the update and letting us know you're already on a fresh install. You may want to check your anti-virus settings and ensure ESO and the ESO launcher both have exceptions setup.

Iselin · September 2020

ZOS_BillE wrote: »

@Iselin2

Thank you for the update and letting us know you're already on a fresh install. You may want to check your anti-virus settings and ensure ESO and the ESO launcher both have exceptions setup.

That seems to have done the trick.

I remember getting the UAC pop-up from Windows Defender when I first ran the game after install and I allowed it of course. I assumed that set the exception but when I checked neither the launcher nor the game were set-up as permanent exceptions.

Once I did that, the weird hang after log-in went away.

Thanks for your help.

ZOS_Bill · September 2020

Thank you for the update that adding exceptions has help resolve the issue. We will now be closing the thread with the issue already being handled.