Maintenance for the week of December 2:
• [IN PROGRESS] PC/Mac: NA and EU megaservers for patch maintenance – December 2, 4:00AM EST (9:00 UTC) - 9:00AM EST (14:00 UTC)
• Xbox: NA and EU megaservers for patch maintenance – December 4, 6:00AM EST (11:00 UTC) - 12:00PM EST (17:00 UTC)
• PlayStation®: NA and EU megaservers for patch maintenance – December 4, 6:00AM EST (11:00 UTC) - 12:00PM EST (17:00 UTC)
• [IN PROGRESS] PC/Mac: NA and EU megaservers for patch maintenance – December 2, 4:00AM EST (9:00 UTC) - 9:00AM EST (14:00 UTC)
• Xbox: NA and EU megaservers for patch maintenance – December 4, 6:00AM EST (11:00 UTC) - 12:00PM EST (17:00 UTC)
• PlayStation®: NA and EU megaservers for patch maintenance – December 4, 6:00AM EST (11:00 UTC) - 12:00PM EST (17:00 UTC)
First person freeze/crash
Necoriban
✭✭
It's been over 3 months since Greymoor, there are a lot of discussions about this, yet this is getting ignored.
Other that explaining another time i don't know what to do.
Since greymoor, not only on pc but consoles too, if you play in first person and engage in combat with "necromancer type" enemies and get hit by specific abilities (the most frequent cause of crash is the flaming skull), the game will freeze forcing you to close it.
Most common examples: Shade of naemon, Vma first boss, battlegrounds/pvp against a necromancer class, some dolmen bosses , some dungeons with liches like craglorn's, trials, etc.
(almost everywhere).
Half of the crashes/freezes discussions in the last 3 months are related to this. As i said, it happens almost everywhere, so every discussion will have a different name/location, just read and you'll see it's almost every time related to this.
Can you please do something?
It's literally over 3 months that the game is unplayable for me and others.
Thanks.
Edited by ZOS_Bill on September 15, 2020 5:15PM Other that explaining another time i don't know what to do.
Since greymoor, not only on pc but consoles too, if you play in first person and engage in combat with "necromancer type" enemies and get hit by specific abilities (the most frequent cause of crash is the flaming skull), the game will freeze forcing you to close it.
Most common examples: Shade of naemon, Vma first boss, battlegrounds/pvp against a necromancer class, some dolmen bosses , some dungeons with liches like craglorn's, trials, etc.
(almost everywhere).
Half of the crashes/freezes discussions in the last 3 months are related to this. As i said, it happens almost everywhere, so every discussion will have a different name/location, just read and you'll see it's almost every time related to this.
Can you please do something?
It's literally over 3 months that the game is unplayable for me and others.
Thanks.
Do you know how long i've been looking for you?
0
-
Adel_SnoopsSoul ShrivenYep still happening, Fang Lair is another one that causes game freeze in 1st person every time you face necromancer bosses with flaming skull. I've also encountered it at the examples you listed as well.
Just shows how little testing they must do in 1st person when they release a new class and skill that it causes a game crash every time and this was not picked up by testers.
Either they need to fix the problem, or remover the skill, or remove 1st person fro m the game. How many ppl have quit the game over this issue alone? I have read numerous complaints on these forums as well as reddit with ppl cancelling the ESO subs or rage quitting the game all together.
There are many ppl that enjoy playing in 1st person, and this issue is an absolute game breaker for all of them. I myself always swap between 1st and 3rd person view when playing so I will keep going in 3rd person for now which does not see these game freezes.0 -
EmilySophieRoseSoul ShrivenThis is a big problem that needs to be fixed. So much of the game is unplayable. Missed out on many arena plunder skulls during witches event purely because I couldn’t get past the first boss in Maelstrom. So disappointing that this has been going on for so long. Makes it worse that their last update was meant to fix this and it definitely didn’t0