DC in zones VT/DSK3

[Hazardousdrunk]

So we started out with 39 in VT, everything was going well until we got to Jyseric Kor Narthu, not sure why that one but it will DC the entire zone once everyone is attacking. This use to not happen with just around 36 characters (Only on luclin it would happen occasionally)

#2 (DC zone twice, not the first time either)This one happens a lot, But with Luclin we were DCing the zone with even 37, but it was much worse with 39.. ended up logging enough out to get to 34 in zone, and was able to kill Luclin without DC.


#3 DSK3, 45 in raid, first boss went fine, mostly pets attacking.
Maestro DC zone once only happens when all start attacking, Dropped down to 30 players and issues went away.

Is the server having trouble keeping up registering all the hits and procs or is it just the amount of players in the zone??

Isn't (that) big of a deal we have chosen to scale back the amount of characters for raids at this point, but be nice to be looked into.

[Lillu]

There were only 4 zone crashes in Feb. and none in March so I'm not sure what's going on. Did you guys try to filter out battle spam and such? Can you reproduce the desync with exact numbers or does it vary when you get desynced?

[Hazardousdrunk]

it kinda varies here and there..

I myself block out the damage/spell spam, sure they do as well.

it was just today that we had a lot more issues but because we brought more character then usual..

When we run our normal amount things work out ok, sometimes luclin will DC us but not that often with 35 or so.


I am almost positive we can DC the zone again with luclin though if I bring my extra characters

[Lillu]

It's definitely not a zone wide restriction but we'll take a look on the scripts.

[Lillu]

I've checked some of these scripts and there's no reason to get desynced past 36 clients in combat. Not sure why would this happen to you guys (is it happening to everyone or just some?).

There's however a connection limitation to the server and that's 36 clients per IP. Are you guys all from the same IP? Could that be the issue? That shouldn't disconnect everyone from the zone either though.

[Hazardousdrunk]

No, we are seperate IPs, he does 18, i do 12, she does 6-8.

It happens to everyone, we all see the black screen saying you have been disconnected and then puts us into character selection.

[Beatboxin]

I did VT this morning solo not 1 DC, when there are more toons the above happens and it happens right about the time we all attack the mob. Dc's happened on Jantarx Kor Voinyx, Jantarx Kor Voinyx, and Luclin, the Avatar of Darkness in VT not all mobs did it to us just these 3 IIRC.

In DSK3 boss one as he said we just attacked with pets and no DC's, on Maestro one attacked boss other 2 on adds np soon as first wave of adds where did we all 3 then attacked the boss, shortly after attacking boss like VT we DC'd. After that kill Kitty left zone with her 6-8 toons and Nek and I continued through dsk3 with no more dc's. Though none of the bosses after Maestro we both attacked at the same time with all toons full burn.

It feels like this only happens with we have 36-45 in zone and right as everyone attacks mob at the same time.

[Hazardousdrunk]

Did VT and currently doing DSK3 with 36.. doesn't seem to be an issue today.

[peterigz]

Hope to do some profiling on this soon. I might create a dummy and plonk it somewhere and invite a crowd to start beating on it, and once it has 30+ on the hatelist it switches on the profiling and then depops after enough data is collected. That data would be interesting to view.

I think that Hazardousdrunk makes a good point about THF having players that have a ton of potential to hit, proc, pets, casts etc, more so then most other servers I think. So the server has a ton of "You hit x for" packets to send out, and it might even be made worse by the fact that one PC running 20+ clients has to recieve all those packets and ping back that it received it ok, then the potential for packet loss and having to resend the packets again, all adds up.

It doesn't really matter if you have filtering all turned off, the server will still send the packets regardless unfortunatetly.

Edit: I take that back about the filtering, looking at the code it should be preventing those packets, so I guess it does just need profiling to start with and figure out where the bottle necks are.

[Shylar]

I've checked some of these scripts and there's no reason to get desynced past 36 clients in combat. Not sure why would this happen to you guys (is it happening to everyone or just some?).

There's however a connection limitation to the server and that's 36 clients per IP. Are you guys all from the same IP? Could that be the issue? That shouldn't disconnect everyone from the zone either though.

Years ago we'd desync/crash if we had above 30 in the zone (three players). We have just recently started up again and haven't been back to the zones that used to desync for us (especially on vistindra). I also recall taking ~36 to an epic 3.0 fight and completely desyncing.

Also the IP limit is 24/25 (36 would be great!!!).