Kalthanan
03-23-2005, 08:15 PM
From the SOE forums:
Posted March 22:
Hi folks
Sorry for the delay getting back to this thread. I know everyone who has to deal with this bug has been pretty frustrated and justifiably so. Unfortunately given the deep impact that the collision system has to the game as a whole when fundimental code changes are made such as the ones currently on test our QA department (Xieb + crew) has to review every single collision bug previously entered in the system along with all the other items on their checklists related to collision system behavior. It takes a lot of time, and has to be restarted every time they find something wrong and we wind up having to make other changes.
For those wondering, no the changes did not go on live servers with the last update.
The good news is that at this point things are looking pretty good. We haven't had formal sign off on the fixes but so far nothing has been found and I'm optimistic about it. We'll be getting these fixes up as soon as is practical. There are other factors that complicate getting the code up right away and I don't have a schedule for it yet but we have not lost sight of this problem and do intend to get the fixes to you ASAP.
The other thing we are still working on solving is the world server stability. We are making progress but it is also another one of those very difficult problems to solve. For the technically inclined, it is a slow memory leak on the world server and after about a week the process runs out of memory. We're usually able to predict when a world is going to run out and schedule a restart accordingly but not all the time.
Anyways, I just figured folks watching wanted & deserved an update.
Cheers,
---------------------------
Eric Cosky - "Grumbuk"
Assistant Lead Programmer, EverQuest
Sony Online Entertainment
Original thread is here (http://eqforums.station.sony.com/eq/board/message?board.id=testing&message.id=5413&no_redir=true)
Posted March 22:
Hi folks
Sorry for the delay getting back to this thread. I know everyone who has to deal with this bug has been pretty frustrated and justifiably so. Unfortunately given the deep impact that the collision system has to the game as a whole when fundimental code changes are made such as the ones currently on test our QA department (Xieb + crew) has to review every single collision bug previously entered in the system along with all the other items on their checklists related to collision system behavior. It takes a lot of time, and has to be restarted every time they find something wrong and we wind up having to make other changes.
For those wondering, no the changes did not go on live servers with the last update.
The good news is that at this point things are looking pretty good. We haven't had formal sign off on the fixes but so far nothing has been found and I'm optimistic about it. We'll be getting these fixes up as soon as is practical. There are other factors that complicate getting the code up right away and I don't have a schedule for it yet but we have not lost sight of this problem and do intend to get the fixes to you ASAP.
The other thing we are still working on solving is the world server stability. We are making progress but it is also another one of those very difficult problems to solve. For the technically inclined, it is a slow memory leak on the world server and after about a week the process runs out of memory. We're usually able to predict when a world is going to run out and schedule a restart accordingly but not all the time.
Anyways, I just figured folks watching wanted & deserved an update.
Cheers,
---------------------------
Eric Cosky - "Grumbuk"
Assistant Lead Programmer, EverQuest
Sony Online Entertainment
Original thread is here (http://eqforums.station.sony.com/eq/board/message?board.id=testing&message.id=5413&no_redir=true)