Quote:
|
Originally Posted by cbodmer
First of all, try optimizing your database, of course.
If that doesn't help, open world/client.cpp and jump to line 59:
Code:
...
Client::Client(EQStreamInterface* ieqs)
: autobootup_timeout(10000),
CLE_keepalive_timer(15000),
connect(1000),
eqs(ieqs)
{
...
Change the two timers, I set them to 60000 and 65000 respectively:
Code:
...
Client::Client(EQStreamInterface* ieqs)
: autobootup_timeout(60000),
CLE_keepalive_timer(65000),
connect(1000),
eqs(ieqs)
{
...
Recompile and go.
That way, even if your server is under some load with lots of DB queries, there should be enough time to boot your dynamic zones (they can now take 1 minute before a timeout happens). Best tell your players that zoning may be slow occasionally when the server is active.
These settings should be made configurable via XML in a future release.
Cheers
-Chris |
This looks like a good idea - I'm glad you pm'd me else I would have never seen this post ( i manage to somehow miss some of the new posts).
I know my problem is, I run my EqEmu on older, slow machines. At first, it didn't matter and zones worked fine, but the more content I put into the zones, the more I see this problem while logging in and zoning. when I say "old" I mean as in P3, under 1gig MhZ machines. I do have faster machines - but don't want to commit them to an EqEmu server if i can avoid it. One solution is to load the zone "static" - this is good if you're playing alone or doing work. But hopefully, you're solution will be better.
Threaded Mode
