sabresandiego_ESO wrote: »Today I noticed there was a lot less lag on Azuras for a period of time during primetime. I took a look at the map and noticed that no keeps on the entire map were under siege. About 30 minutes later, azuras was unplayable lag as usual, and I looked on the map again and 2 keeps were marked as being sieged.
If you want playable pvp during prime time hours, be respectful and do not siege any keeps.
sabresandiego_ESO wrote: »The lag has something to do with keeps and siege weapons. Zergs contribute immensely, but when these same zergs fight away from keeps and without using siege weapons the lag is noticeably improved.
Bridge farm FTW.sabresandiego_ESO wrote: »The lag has something to do with keeps and siege weapons. Zergs contribute immensely, but when these same zergs fight away from keeps and without using siege weapons the lag is noticeably improved.
It might just be me, but I have noticed a lot more lag around anything that has a tick.
Mentioned this 8 or so months ago.
Teargrants wrote: »Bridge farm FTW.sabresandiego_ESO wrote: »The lag has something to do with keeps and siege weapons. Zergs contribute immensely, but when these same zergs fight away from keeps and without using siege weapons the lag is noticeably improved.
It might just be me, but I have noticed a lot more lag around anything that has a tick.
Mentioned this 8 or so months ago.
This thread is ridiculous. Keeps themselves and tick ranges have nothing to do with the latency itself. It is just pure logical that people work toward objectives *cough keeps* which will obviously bring more latency issues if more people merge into the same area because there are more chances to see players exchanging damage / heal to each other.
This thread is ridiculous. Keeps themselves and tick ranges have nothing to do with the latency itself. It is just pure logical that people work toward objectives *cough keeps* which will obviously bring more latency issues if more people merge into the same area because there are more chances to see players exchanging damage / heal to each other.
I am going to have to disagree with you here.
Not saying it is the cause or it isn't, but there are a lot more things going on server side around a keep.
The same fights I used to have at keeps that caused massive lag would be playable away from the keep.
Not to mention, say a random guild whom we will call KPN, has 100 dudes in nikel. Everything is all fine and dandy, but the moment you come within the tick range of nikel you get hit by a large fps drop and obvious latency issues before you ever see the other players. Same idea with keep sieges, you can telling roughly how many people are there just by your latency even though they aren't fighting and no one is in sight. Just an observation.
sabresandiego_ESO wrote: »Today I noticed there was a lot less lag on Azuras for a period of time during primetime. I took a look at the map and noticed that no keeps on the entire map were under siege. About 30 minutes later, azuras was unplayable lag as usual, and I looked on the map again and 2 keeps were marked as being sieged.
If you want playable pvp during prime time hours, be respectful and do not siege any keeps.
Wrong. You're not experiencing the same fights in the open field that you are in keeps. Anyone that was there can attest to this. A few days ago I grabbed a scroll from a DC home keep and started running it south. Just before that Daniel had grabbed a scroll from an AD home keep. We ended up running into each other, and what happened was the game completely *** itself. It was actually worse than pretty much any keep fight I've experienced since the changes to LoS checks.
Wrong. You're not experiencing the same fights in the open field that you are in keeps. Anyone that was there can attest to this. A few days ago I grabbed a scroll from a DC home keep and started running it south. Just before that Daniel had grabbed a scroll from an AD home keep. We ended up running into each other, and what happened was the game completely *** itself. It was actually worse than pretty much any keep fight I've experienced since the changes to LoS checks.
spenc_cathb16_ESO wrote: »Wrong. You're not experiencing the same fights in the open field that you are in keeps. Anyone that was there can attest to this. A few days ago I grabbed a scroll from a DC home keep and started running it south. Just before that Daniel had grabbed a scroll from an AD home keep. We ended up running into each other, and what happened was the game completely *** itself. It was actually worse than pretty much any keep fight I've experienced since the changes to LoS checks.
Yeah it's too bad, that was actually going to be a really really good fight too. Some of us got footage of that fight, but there's just way too much latency spiking to be enjoyable. There was also 2 AD guilds, an EP group, Daniels group, and 3/4 a raid of VE all in the same area. Which should be fine, but ZOS.
Wrong. You're not experiencing the same fights in the open field that you are in keeps. Anyone that was there can attest to this. A few days ago I grabbed a scroll from a DC home keep and started running it south. Just before that Daniel had grabbed a scroll from an AD home keep. We ended up running into each other, and what happened was the game completely *** itself. It was actually worse than pretty much any keep fight I've experienced since the changes to LoS checks.
Of course that will still cause a lot of lag. I was with you, and no exaggeration there was maybe 120 people at that fight, with all 3 factions. Its going to lag.
What I am suggesting is the fights that are ~30 vs ~30 are more playable away from keeps and it appears that tick range plays at least a part in latency. Not saying to avoid keeps or its the only issue, but it does play a role in my opinion.
This thread is ridiculous. Keeps themselves and tick ranges have nothing to do with the latency itself. It is just pure logical that people work toward objectives *cough keeps* which will obviously bring more latency issues if more people merge into the same area because there are more chances to see players exchanging damage / heal to each other.
I am going to have to disagree with you here.
Not saying it is the cause or it isn't, but there are a lot more things going on server side around a keep.
The same fights I used to have at keeps that caused massive lag would be playable away from the keep.
Not to mention, say a random guild whom we will call KPN, has 100 dudes in nikel. Everything is all fine and dandy, but the moment you come within the tick range of nikel you get hit by a large fps drop and obvious latency issues before you ever see the other players. Same idea with keep sieges, you can telling roughly how many people are there just by your latency even though they aren't fighting and no one is in sight. Just an observation.
This thread is ridiculous. Keeps themselves and tick ranges have nothing to do with the latency itself. It is just pure logical that people work toward objectives *cough keeps* which will obviously bring more latency issues if more people merge into the same area because there are more chances to see players exchanging damage / heal to each other.
I am going to have to disagree with you here.
Not saying it is the cause or it isn't, but there are a lot more things going on server side around a keep.
The same fights I used to have at keeps that caused massive lag would be playable away from the keep.
Not to mention, say a random guild whom we will call KPN, has 100 dudes in nikel. Everything is all fine and dandy, but the moment you come within the tick range of nikel you get hit by a large fps drop and obvious latency issues before you ever see the other players. Same idea with keep sieges, you can telling roughly how many people are there just by your latency even though they aren't fighting and no one is in sight. Just an observation.
Doesn't explain my experience in the Districts with a 30 man zerg lagging it out just as bad as cyrodiil.
I think there are *some* latency issues with ticks as I've experienced that myself when I was the only player at a stronghold and my FPS went to crap when I got a random tick for about 10 seconds.