UppGRAYxDD wrote: »Honestly after all the deleted threads, ignored feedback, and aimless direction pertaining to customer needs....
I really love this game. And I know that they can do better with quality. Because I have seen perfect systems in the game.
So do that.
Edit: Call it an investment.
Czekoludek wrote: »So just to clarify, players for years now complains about cyro performance and you just now created special team to analyse the root of the problems there? After 3+ years of cyro bad performance and more then a year of cyro unplayable performance during prime time?
Czekoludek wrote: »So just to clarify, players for years now complains about cyro performance and you just now created special team to analyse the root of the problems there? After 3+ years of cyro bad performance and more then a year of cyro unplayable performance during prime time?
Apparently, this team has been in place for a while. (This is not the first they have mentioned it)
It's fascinating how all this time has gone by and there's not as much as a breakdown of where the issues are. Is it lack of server (physical) capacity? Is it net code? Something else?
Sargesgaming wrote: »Still no link and still no word on what they are doing here.... hmmm @ZOS_JessicaFolsom
Lambert described it as an onion. They peel back one layer, then start working on the next. I guess when the onion is gone, they are either successful, or they give up.
stefan.gustavsonb16_ESO wrote: »Lambert described it as an onion. They peel back one layer, then start working on the next. I guess when the onion is gone, they are either successful, or they give up.
Sadly, that's a bad analogy. I hope that was just something he said to explain that it takes time, and that they are being thorough. However, I certainly hope that the work as a whole is not actually being performed as if they were figuratively peeling an onion, because that would be bad.
To identify the weak points of a complex system, you need to look at the big picture right from the start. "Peeling it", i.e. dealing with each layer separately in a predetermined order, improving one system at a time to see whether it makes things any better, is a potential huge waste of time, where you might end up spending lots of time and effort on trying to fix things that already work just fine. If, say, the core is rotten (not saying it is, just keeping with the onion analogy), you need to determine that early in the process and focus most of your effort on that. The "layers" here are not physical layers, it's just a set of connected systems. One layer does not hide another, and there is nothing that actually prevents you from changing the "core" without touching the "surface".
From our point of view as end users, everything but the outermost layer, the user interface, is indeed hidden, and we have to make more or less educated guesses as to what might be the actual underlying problem. However, from the point of view of the system designers, every layer should be equally visible and accessible at all times. Large IT systems should be designed with profiling and monitoring capabilities built into them, and I'm not inclined to think that a game as complex as ESO was designed entirely without consideration to best practices. While game programmers tend to be less disciplined and less reined-in by formal process than in many other parts of the software industry (and I'm speaking from broad personal experience here), I doubt that a "coding like it's 1995" approach would have resulted in a functioning product. (And before you take a cheap shot and say that ESO isn't "a functioning product", it is. It may not work quite as well as we would want it to, but it most certainly isn't completely broken.)
Well, that was a rant. Sorry. I blame my job. Now I'm back to playing the game.
stefan.gustavsonb16_ESO wrote: »Lambert described it as an onion. They peel back one layer, then start working on the next. I guess when the onion is gone, they are either successful, or they give up.
Sadly, that's a bad analogy. I hope that was just something he said to explain that it takes time, and that they are being thorough. However, I certainly hope that the work as a whole is not actually being performed as if they were figuratively peeling an onion, because that would be bad.
To identify the weak points of a complex system, you need to look at the big picture right from the start. "Peeling it", i.e. dealing with each layer separately in a predetermined order, improving one system at a time to see whether it makes things any better, is a potential huge waste of time, where you might end up spending lots of time and effort on trying to fix things that already work just fine.
stefan.gustavsonb16_ESO wrote: »Lambert described it as an onion. They peel back one layer, then start working on the next. I guess when the onion is gone, they are either successful, or they give up.
Sadly, that's a bad analogy. I hope that was just something he said to explain that it takes time, and that they are being thorough. However, I certainly hope that the work as a whole is not actually being performed as if they were figuratively peeling an onion, because that would be bad.
To identify the weak points of a complex system, you need to look at the big picture right from the start. "Peeling it", i.e. dealing with each layer separately in a predetermined order, improving one system at a time to see whether it makes things any better, is a potential huge waste of time, where you might end up spending lots of time and effort on trying to fix things that already work just fine.
Well, you have to remember that it is an analogy. In this case, it is a means of expressing a complicated technical situation in terms that can be understood by people who don't have the background to understand the complicated technical situation. A lot gets lost in the analogy, which is sort of the point. To the people who might be able to understand, they can determine that ZOS is probably doing X, Y, and Z. For everyone else, they wonder why Lambert is talking about vegetables.
I will not bother to read anything because i probably read them again FOR THE PAST 6 YEARS!!!PERFORMANCE WORK COMMUNICATION? You have got to be joking!!! The forum is full of "work comunication comments FOR 6 YEARS NOW! Have you entered Cyrodil any time this weekend??????? Did you manage to press a skill??? It has been 6 YEARS ! WE ARE NOT IN THE BETA ANYMORE!!! [snip]