Is this going to stop a third of my fleet mates DCing in fights with 500 in local when fighters are launched?
Is CCP ever actually planning on addressing the obvious performance issues with fighters and AOE weapons? Are you planning on addressing the obvious increase in DCs over the past year?
These particular changes very likely not. Unfortunately we could not find any proper correlation yet with client disconnects (in contrast to client crashes, where a major contributor to memory related client crashes was fixed 10 days ago).
While I understand that you have more profiling information than us, I would like to restate that “simply” having 100 carriers launch fighters during an uncontested structure bash brought 50% tidi to the system a month ago.
This wasn’t even a proper battle. Doing something to improve fighter performance would definitely enhance the experience EVE players enjoy during large scale fights that pop up in the news.
Launching 300 fighters will for sure cause a CPU spike and I would for sure prefer if the load would be a bit less, but my point was that I have so far not found any data, which proofs that launching fighters causes disconnects - but I am looking further into this. Maybe we’ll also have a mass test at some point about it, but it would be detrimental to combine it with this one.
I hope the changes make a difference because the general attitude of my alliance to spending hours in TIDI trying to get supercapital characters logged back in is very negative. Even in “small” fights with minimal TIDI we have been having multiple supers DC/crash.
It isn’t very fun to get these “end game” ships and then lose them to a DC/crash.
How does fighter CPU use compare to drones? Because just anecdotally it seems using drones doesn’t cause as many issues as using fighters. And one of the reasons for switching carriers to the new fighter mechanics was to reduce server load.
I don’t have accurate numbers at hand, but in a very quick check with only one client it looks like launching 3 fighters causes less load than launching 5 drones (even 1 fighter seems to be less load than 1 drone) - but yeah, these are not reliable numbers, but they look at least better than I expected.
Does CCP test for such things as the effects random lost packets might have, when 100 clients launch 300 fighters and attack something? Real-world clients have different distances, latencies to the server - an in-house lab bench has practically none of that.
Only if there are indications that network latency or packet loss play any role and never at this scale. Mass tests are our primary tool for testing such real life influences on such a scale.
So all in all that means mass tests are precisely for that issue (the one Circumstantial Evidence is pointing out) to be tested out, just in case… Good thinking.
Just a question to see if I got that right: there will be no mirror to be able to log in to SiSi during/after this mass test? How long should I expect to wait to be finally able to log in to SiSi then? (considering I’m playing since early July) And does that mean that I won’t be able to join the mass test?
yes I have . I first sent a but report 6 months ago . I was also told by you ever so helpful support team thes was being worked on and I should just go away and wait . Senior GM Archduke seems to think you all know about this and are “While I still cannot comment on when this may be resolved, I can again confirm that we’re working on fixing this.”
EBR-153351 is the last one I sent but have sent 3 or 4 over the last 6 months
Вот зачем звать людей на тестовый сервер, если даже вы не потрудились обновить зеркало с новым паролем меня на ваш тестовый сервер не пускает.
Такое наплевательское отношение к игрокам очень дискредитируют вашу организацию.
Could I suggest posting the mass test announcements a bit earlier on the Eve client? A lot of us normally don’t check the forums too often for announcements so giving the headline at least a day’s span helps us plan out to attend the tests. I would’ve been on if I had heard of it, cause I’d be getting closer to be able to run a carrier on the test server.
