last night, on cannith (the server i frequent), was running distruptor because my arti build rocks there, to get a bunch of boxes for the +2 loot event. a friend was with me for some of the runs. we succeeded, but it was a lag nightmare. with my friend, i'd estimate 50% of my (granted, summoned) bolts went off target, even when i was manually targetting. no to hit roll, nothing. even in volleys, one or two wouldn't be resolved at all. she had similar issues. i should mention the rubberbanding as well, it was pretty bad. no way to tell where precisely the server thought you were, unless you stood still for a second or two.
i did have a hire out, only to increase the number of starting bosses at the large extractors (that's a different, weird issue, but liveable). she (flower) was getting stuck after every single fight. actually, during most fights she'd just stop. i understand she's "trying to make up her mind" what to do next, but come on. she'll sit there for a full minute before breaking out of it. or i "passive then defensive" her again.
solo the game ran considerably better, even after, say, 2 hours of running in group. only about 20% of my shots were ignored. no hire either. still got bursts of rubber band lag, but not nearly as bad.
now i discover, g-land went down last night. and here i thought they'd "fixed" the server side memory leak and instability issue. guess not.
i don't want to bash the devs. it's not the fault of the developers. it's a programmer issue. the hire thing is just one example. the memory leak another. a third, restarting the client helped. that's a memory leak on the client side.
this game's performance is lousy, especially with risia going. cc is gonna kill these poor servers. it's by far my favorite event, and i've stopped asking for it because of this. the performance issues are a sign of sloppy programming, maybe not the current set of programmers, but memory leaks? really? i've done a little programming, maybe not mmo based, but i can program enough to know how bad memory leaks are. and in my development, the free unix tool electric fence was wonderful in pointing out my shortcomings on that. so, my code didn't have memory leaks. or endless loops (see the hire behavior? endless loop).
there are tools out there. please, please, use them. find these leaks. find these broken loops. fix them. i know it's not glamorous to do, but geez, the game's awful without it. and if i were just trying out this game for the first time, and it was running this badly, do you think i'd even consider subscribing? not durn likely. there's you justification for spending the time on it with the managers/bean counters.
so, to the poor programmers who (i hope) will get to fix this mess, good luck and good hunting.