Booted again today. Now back to 60q

Wait in 30 q.
Kicked error 307
Unexpected internal error
Back to q I guess

SkaraMinoc wrote: »

Genfe wrote: »

Log into 15q go to BRK Crash

I'm convinced there's something programmatically wrong with BRK. Anytime I go near it, I get a loading screen for a split second. This is the only place in Cyrodiil this happens. During tri-faction sieges, I can't even go near BRK because my game freezes and crashes. Then I get "Unexpected Error" for the next 10 minutes trying to log back in.

This happens to me occasionally and I've discovered that disabling my VPN and then rebooting the client shortens the downtime dramatically.

This may only be useful in my instance, however, I hope it helps.

For years, this has been managed by players going to get some nearby resource, then waiting for the tick, and if it was huge, the second likely defence tick as well, before approaching a keep.

It's easier now to predict those crashes -100 swords 60 swords 40 swords < stay away

One does not simply ride up to Mordor.

For those who might come across this post here's how to avoid such crashes (or at least limit them)

1) Set your view distance to at least 37 or higher - This helps if you do crash to be able to get back in
2) Approach the keep slowly, don't ride up to a large fight, get off and walk as you start to get into visual range of the keep - ideally from the side it is being sieged by, you are aiming to load the players sieging in before the defenders in the keep / potentially other attackers on the other side.
3) If you feel your game start to stutter / ping goes up then stop and wait for it to return to normal - this ping fluctuation is representative of the players being loaded.
4) if you do crash wait at least 1m before trying to log back in. Ideally have a friend message you on an external app such as discord that your character has 'gone offline' before trying to log in. IF you try and log in before your character is offline you will get stuck in an endless loop of server errors and almost 100% be outside of Cyrodiil when the game finally decides you can play again.
5) If you have 'gone offline' and manage to get the character select screen at this point set your view distance to 0 before logging in with that character. This will give the game chance to load the fewest amount of players. then repeat from step 1 once you are back in.

6) If you are in a long keep fight like this DO NOT respawn at a camp outside of the keep range and run straight back in. Try and wait for a res instead. Players are not cached so you can easily hit the 'loading limit' again and crash if you ignore this.

Additionally setting the following in user settings can also help: SET PlayerStandInsMaxPerFrame "16"

For ZOS devs (@ZOS_Kevin) - The problem which happens is that all the players, structures, guards, siege are loading at the same time and causing some error in bandwidth. If this fails the game will crash rather than delay load players based on distance. The game needs to stagger the loading of players. This is easily dev testable by having a number of bot accounts run up to a player at the same time from a distance on mounts. Once you get to about 40+ players riding together the player trying to load them is likely to crash if they all appear at once. (it seems to be dependant on ping and bandwidth though).