Maps zooming out on zoning

[rasthan]

Most of the time when I zone, the maps will zoom out to sometimes max distance. I then have to zoom in to see whats around me.

As an aside, there is usually some kind of junk spawn in the spawn list as well. (Which is probably causing the above)

Is this a known problem and is there a workaround for it?

Thanks. :)

[BlueAdept]

What version are you using. It sounds like you could be running an old version. I haven't had this happen on the current build.

[rasthan]

Heres some output from the terminal:

ShowEQ 5.0.0.24, Built from 'main.cpp' on Jul 17 2005 at 17:59:33
CVS: @(#) $Id: main.cpp,v 1.33.6.8 2005/05/28 16:12:44 cmmalone Exp $ $Name: $
Using GCC version: 3.3.5
Using glibc version: 2.3
Using Qt version: 3.3.4
Using headers from linux version: 2.6.11
Using EQItemDB: @(#) $Id: itemdb.cpp,v 1.10.6.5 2005/04/18 03:16:22 dohpaz Exp $ $Name: pre_5_0_beta $
Using GDBM: GDBM version 1.8.3. 10/15/2002 (built Apr 18 2005 15:10:33)
Running on Linux release 2.6.11-gentoo-r6 for processor i686

Thanks. :)

[purple]

I've seen that a lot in the guild lobby with corpses. It's not some garbage in the spawn list though for me, it's a valid spawn whose position is just out in the middle of nowhere. I haven't really seen it anywhere else.

But anyways, seq has to trust what it sees snooping the eq session and it draws what it sees. If a spawn is listed in the middle of nowhere in the zone spawns, then it gets drawn in the middle of nowhere.

If you're not exaggerating with your "most of the time" then I'd wager something is up. Are you on a localized server? Is there anything weird with your setup? If you're comfortable sending me a tcpdump, I'd take one. You'd have to login to EQ, do character select, zone in, then on your linux box type "tcpdump -i eth0 -s0 -w collect.log 'udp && host 192.168.1.100'" (replace 192.168.1.100 with the IP on your EQ client). Then you just need to zone around until you see the garbage. Once you do, control-C the tcpdump, gzip collect.log, and figure out someway to get it to me. Either PM me a web URL or you can email to [email protected] or whatever. Note that I can see your character and guild info from a dump, so only do this if you are comfortable with me having that information. As long as you start tcpdump AFTER you've logged in, I won't have any access to your login password.

[rasthan]

Check your mail, purple! :)

[purple]

Reproduced with your dumps. That's a really odd problem. I'll see what I can do, though. Thanks for getting back to me so quickly.

[rasthan]

Sure. Let me know if you need more dumps.

[purple]

I think I've got this tracked down. Thanks a lot for the dump. It's the only thing that made fixing this possible.

This should be effecting anyone with a really bad connection. You were using the packet cache pretty extensively and exposed a problem with the way the net layer reacts when the same packet is seen twice. The code that updates the cache with the newer packet with the same sequence number was broken. So one packet in your zone spawns was corrupt causing one or two bogus mobs of varying degree depending on where that packet feel in ZoneSpawns.

[rasthan]

Ah good, that would explain it. I'm on a networked dialup connection and I also usually have other net applications going at the same time while playing EQ.

Thanks a lot for your help. :)