This is becoming the norm.

[xadien]

VT Raid tonight 12:00 am CST. Cleared Trash, no issues. opened P1 door, clearing trash to P1 boss, Crash all 7 of my toons. Guildie used COH, zoned her to Forrest. When my group died, one of the corpses was on the far side of the zone. Went after body which was back at the front door, Crashed to Desktop. Everyone was grumpy, so we called it. Cleared CY trash, and 10 Castle trash, and logged because we couldn't keep toons online.

[Vaion]

Just wanted to make a generalized post regarding this stuff. We appreciate all the reports and constant feedback and have been working as fast as possible to get the code merge/revamp completed. It is a major project that involves renovating pretty much every tool and system that we use for the server. Right now we are still working on getting the EQEmu and THF codes merged coherently together and then we will start the process of testing/debugging the system.

Please continue to provide feedback and reports of crashes, but understand that if we do not respond to each one, it doesn't mean that we are not working on fixing them

[Dred]

Last night experienced what seemed to be 2 zone crashes in HoH. Guildies and myself all lagged completely out at the same time and had to /q out. None of us could cast spells, attack mobs, etc. I had to use the stuck character mover to get my toons out. Went back in about 10 or 15 minutes later and within about 5 minutes the same thing happened. It was around maybe 8pm EST. I did not take note of how many were in zone. At around 9pm EST went to Nadox and experienced a good deal of lag there as well. I think we had around 20 toons in zone. I was playing 6 toons and running mq2 but no scripts. My ping is normally around 160ms to 180ms. Ping on 4 accounts was 900ms to 1200ms. Other 2 accounts ping was 500ms to 700ms. Could not camp out so I had to /q on accounts and use stuck character mover again. I got frustrated and logged after that so I don't know if it got better in Nadox or if other zones were better.

[Vaion]

Thanks for the report as always. Just wanted to give another update on code status and let everyone know that it is nearly finished now. We have about 3,000 more lines of custom code to integrate with EQEmu (started around 45,000). Then it's just a few days of internal debugging to make everything line up perfectly and we should be able to start public testing.

The game plan is to throw the new code on the test server and run a few "bug contests" where the community can help us narrow down the bugs in the merged code (bound to be some) on the test server and get rewards on the live server. After we feel the code is ready to roll we will drop it on live and fix these crashes/stability issues once and for all.

Just a reminder of what the merged code brings:
- Exploit fixes
- Desync and memory leak fixes
- Numerous optimizations to performance
- Support for the latest building tools (the Dev team is very happy about this one!!)
- RoF2 client support! (Some features may remain disabled until we get time to fully scope out what they do)

So again, we just ask for patience in allowing us the time required to make this as smooth of a transition as possible

[Nizzy]

Thanks for the report as always. Just wanted to give another update on code status and let everyone know that it is nearly finished now. We have about 3,000 more lines of custom code to integrate with EQEmu (started around 45,000). Then it's just a few days of internal debugging to make everything line up perfectly and we should be able to start public testing.

The game plan is to throw the new code on the test server and run a few "bug contests" where the community can help us narrow down the bugs in the merged code (bound to be some) on the test server and get rewards on the live server. After we feel the code is ready to roll we will drop it on live and fix these crashes/stability issues once and for all.

Just a reminder of what the merged code brings:
- Exploit fixes
- Desync and memory leak fixes
- Numerous optimizations to performance
- Support for the latest building tools (the Dev team is very happy about this one!!)
- RoF2 client support! (Some features may remain disabled until we get time to fully scope out what they do)

So again, we just ask for patience in allowing us the time required to make this as smooth of a transition as possible

Couple things...
Wow I started a popular thread.

Vaion you need a hug. Huge thanks you you and the rest of the dev team with the exception of Noren because he's a gimp.

To anyone that has not tested RoF2 client on another server. You will be amazed at how smooth it runs. It is like going from a 286 with 1 meg of ram to some fancy quad core duo thingy with 16 gigs of ram. One thing I like the most when I launch my characters. It "locks" them in the order they are loaded on task bar. Only negative if you have one crash it ends up on the far right. This with and with out 3rd party programs there may be a way to rearrange them but I was only using 3 toons to test it so being out of order didn't bother me.

[Nizzy]

Tonight exactly 9:30pm CDT Alloran, Niix and I attempting Masture Vule in DSK3. All 38 toons in raid ALL went out of sync at the exact same time.

We could still see in our HOTT that damage was being done to the current mobs we were on. We could also tell our gimpastic half-elf wannabe tank died and another tank was summoned by Vule.

[intelliclint]

Tonight exactly 9:30pm CDT Alloran, Niix and I attempting Masture Vule in DSK3. All 38 toons in raid ALL went out of sync at the exact same time.

We could still see in our HOTT that damage was being done to the current mobs we were on. We could also tell our gimpastic half-elf wannabe tank died and another tank was summoned by Vule.

He is only mostly gimp and keeps better agro then some frog I could name, who seems to always rezzing his wizard.

Seriously though, short of the battle spam lagging a client, which it can do even when I am soloing, the whole zone seem to stall. I finally had to restart EQ to get logged back in.

Over all zoning is still slow in groups it is about 3 to 5 seconds after zoning that my group will fill back in.

PLEASE keep working on it, we are so close to VT.

[Noren]

Over all zoning is still slow in groups it is about 3 to 5 seconds after zoning that my group will fill back in.

PLEASE keep working on it, we are so close to VT.

We're on it. Currently investigating packet and database handling for some performance/stability fixes. The tank and wizzy issues... I'm not so optimistic about

[Nizzy]

Over all zoning is still slow in groups it is about 3 to 5 seconds after zoning that my group will fill back in.

PLEASE keep working on it, we are so close to VT.

We're on it. Currently investigating packet and database handling for some performance/stability fixes. The tank and wizzy issues... I'm not so optimistic about

That wizzys name is Norrenn or should be.

[Vaion]

Since I've been updating here:

Server code merge is complete as of this morning! Now step two comes into play where we (The Devs) begin setting up all the new tools and software requirements to properly run the new code and begin internal testing.

Stay tuned for updates on when the Test Server will be open for public testing!