[vid] 3 Lethal Arrows 1 Animation, is this acceptable PvP performance?

Taylor_MB

https://www.youtube.com/watch?v=FGiEgMdiny4

~10sec: FTC registers 1st Lethal Arrow (no animation, no HP lost)
~12sec: FTC registers 2nd Lethal Arrow (no animation, HP 1st hit lost + burning embers heal)
~13sec: FTC registers 3rd Lethal Arrow (animation displays, HP lost for this hit and 2nd hit combined)

Just preemptively covering a few points:
Lag: Everything else apart from the Lethal Arrows were performing smoothly. FTC picked up on the damage as it occurred (in combat log). So no unregistered lag spike.
FTC HP Bar Bugging: It pulls straight from the game. If it did calculate your HP separately it would've actually been real time accurate (as it registers in the combat log correctly).
PvP Performance Been Constantly Neglected: Yes. Probably yes.

Edit: The reason I'm so heavily inclined to blame performance over lag, is simply because of the desync between FTC registering damage and the game failing to animate and adjust HP bar. I don't see how lag can be responsible for the damage being registered, but no animation or adjustment to HP bar. If it was simply lag that would imply ZoS needs to send at least 3 different messages; 1) animation 2) damage 3) adjust HP bar accordingly. That just doesn't make sense to me.

Vizier

Ummm. **** happens?

Jade1986

That was lag, and no addon wouldve helped you there. Or it could have been packet loss, no add on shows you that.

VaranisArano

Acceptable PVP Performance? Not really. Just the way the game is? Yep.

I've taken 5 cliff racers in the back in 1 second, shrugged it off as lag, rezzed up and kept going. Until ZOS fixes the lag or I move out of the cornfields, the lag isn't going to get better. SInce I'm not moving and ZOS doesn't seem to be able to fix the lag on their end, I'm resolved to not let the lag and its issues ruin my enjoyment of PVP.

WuffyCerulei

Taylor_MB

Jade1986 wrote: »

That was lag, and no addon wouldve helped you there. Or it could have been packet loss, no add on shows you that.

WuffyCerulei wrote: »

Did you both miss the part where FTC Combat Log (in the bottom right) registered the damage as it happened, but no animation or no lost HP (for the first hit)? That's not lag, that's the game being broke.

Betsararie

Why not just use it. At this point so many people use it in PvP it's basically become a part of the game.

eso_lags

I know people that do it on purpose.. There is a way to glitch it, it would be nice to hear from @ZOS_GinaBruno or @ZOS_JessicaFolsom if this is something we should report people for.

Elusiin

itzTJ wrote: »

I know people that do it on purpose.. There is a way to glitch it, it would be nice to hear from @ZOS_GinaBruno or @ZOS_JessicaFolsom if this is something we should report people for.

There's many different protocols for communicating over the internet, some are very reliable but slow, others faster but less reliable, and somewhere along those lines in addition to your own ISP and router, something went wrong. It's most likely not the way the game is programmed, but rather how the internet works. Please quit blaming ZOS.

kendellking_chaosb14_ESO

I hate that Add-on I run a bow as my main and you see nearly everyone shielding and blocking the instant I fire anything off.

If not banned the channel reading should be blocked in the AI setting.

Dorrino

Taylor_MB wrote: »

Edit: The reason I'm so heavily inclined to blame performance over lag, is simply because of the desync between FTC registering damage and the game failing to animate and adjust HP bar. I don't see how lag can be responsible for the damage being registered, but no animation or adjustment to HP bar. If it was simply lag that would imply ZoS needs to send at least 3 different messages; 1) animation 2) damage 3) adjust HP bar accordingly. That just doesn't make sense to me.

Lag has nothing to do with this because your combat log correctly registered the damage when it happened.

The server was perfectly aware about your real hp values and correctly issued EVENT_COMBAT_EVENT's with the correct damage values to the client and correctly updated your char state to 'dead'.

The thing is the server did NOT correctly fire EVENT_POWER_UPDATE events and thus all the addons (like FTC) and ZOS default UI didn't update the hp values.

This is pure ZOS server scripting problem.

That otherwise is called 'health desync' in folk language.

There's almost nothing that can be done client-side to alleviate this.

The only approach that i see is to stop relying on power updates from the server and instead manually calculate current health values taking into account all the taken/healed damage. Somebody might decide to write an addon to try to fix it.

Taylor_MB

Dorrino wrote: »

Taylor_MB wrote: »

Edit: The reason I'm so heavily inclined to blame performance over lag, is simply because of the desync between FTC registering damage and the game failing to animate and adjust HP bar. I don't see how lag can be responsible for the damage being registered, but no animation or adjustment to HP bar. If it was simply lag that would imply ZoS needs to send at least 3 different messages; 1) animation 2) damage 3) adjust HP bar accordingly. That just doesn't make sense to me.

Lag has nothing to do with this because your combat log correctly registered the damage when it happened.

The server was perfectly aware about your real hp values and correctly issued EVENT_COMBAT_EVENT's with the correct damage values to the client and correctly updated your char state to 'dead'.

The thing is the server did NOT correctly fire EVENT_POWER_UPDATE events and thus all the addons (like FTC) and ZOS default UI didn't update the hp values.

This is pure ZOS server scripting problem.

That otherwise is called 'health desync' in folk language.

There's almost nothing that can be done client-side to alleviate this.

The only approach that i see is to stop relying on power updates from the server and instead manually calculate current health values taking into account all the taken/healed damage. Somebody might decide to write an addon to try to fix it.

Thanks mate, I admit my computer knowledge is pretty basic.

idk

Taylor_MB wrote: »

Jade1986 wrote: »

That was lag, and no addon wouldve helped you there. Or it could have been packet loss, no add on shows you that.

WuffyCerulei wrote: »

Did you both miss the part where FTC Combat Log (in the bottom right) registered the damage as it happened, but no animation or no lost HP (for the first hit)? That's not lag, that's the game being broke.

Have not used FTC for probably a year but when I used it I found it to be very imperfect with tracking damage. I understand other's have been updating the add-on since Atropos stopped working on it so this may be fixed.

Regardless, if you are seeing a desync through your client it is reasonable the same desync might show up in a combat log as well so it may not be logging the damage as it happened.

TheYKcid

I've been getting desyncs much more frequently since the CWC patch. Is anyone else experiencing this?

Betsararie

Honestly haven't been following the thread that closely, but if you're getting lag, honestly the reason you're getting lag is probably because of FTC. FTC is garbage. FTC increases your lag in Cyrodiil so much it isn't worth using. It is unfortunate too, because I believe FTC actually has the single best UI elements out of any addon currently out, actually by far, everything about the UI is actually perfect and frankly way better than every other UI addon.

But, it will increase the amount of lag you get by a noticeable amount, so in its current state its unusable for high level competitive PvP. Once I switched to LUI extended (which has way worse UI elements but no real lag), I noticed the amount of lag I get in cyro and BGs to decrease by a noticeable and significant amount.

I will bet you that is the root of your issue.

A_G_G_R_O

I see the issue here, not running MIATS.

Kram8ion

Is this an excuse to use the addon?

Feanor

All the NBs will tell you Snipe is perfectly fine and you ist need to stop potatoing... But I agree with @VaranisArano - shrug it off and keep going. After almost 4 years I don’t think we’ll ever see this fixed.