OOW problem after zoneing

[lildr00d]

Useing latest beta with most recient patches on RH9

Problem with SEQ looseing sync with OOW zones upon zoneing.

This usually happens when I zone from one Omens of War zone to another.


Map will come up when I zone but bottom of SEQ screen shows -Busy Zoneing- Player zones over no skittles. If I do a Succor it will decode.

While in the -Busy Zoneing- mode it will show my location on the map but no skittles or unknowns. Just me.

Only seems to happen in OOW zones.

Usually always in Proveing Grounds, Ruined City of Dranik, Nobles Causeway

Or it could just be cause these are every other zone



Anyone else experienceing this or have a work arround. Currently before I am zoneing now I push "Wait for new EQ session" on the SEQ box

[Cryonic]

helps if you post any of the output from the terminal....

[lildr00d]

Zone: ChangeCode: Client, Zone: provinggrounds
Info: Loaded map: '/root/.showeq/maps/provinggrounds.map'
Info: Saved spawn points: /root/.showeq/spawnpoints/wallofslaughter.sp
Info: Loaded spawn points: /root/.showeq/spawnpoints/provinggrounds.sp
Info: Loading Zone Filter File: /root/.showeq/filters/provinggrounds.xml
Zone: Zoning, Please Wait... (Zone: 'provinggrounds')
Zone: ChangeCode: Server, Zone:provinggrounds
Zone: LogoutCode: Client logged out of server
Info: EQPacket: SEQClosing detected, awaiting next zone session, pcap filter: EQ Client 192.168.11.2
Info: Your player's id is 1469

[CeleSEQ]

Could you please paste in the output from this command?


# showeq --version

I haven't had a problem in OoW like this... maybe we can track yours down though.

[lildr00d]

Could you please paste in the output from this command?


# showeq --version

I haven't had a problem in OoW like this... maybe we can track yours down though.


[root@MYSEQBOX showeq]# showeq --version
ShowEQ 5.0.0.15, released under the GPL.
SINS 0.5, released under the GPL.
All ShowEQ source code is Copyright (C) 2000-2004 by the respective ShowEQ Developers
ShowEQ comes with NO WARRANTY.

You may redistribute copies of ShowEQ under the terms of
The GNU General Public License.
See: http://www.gnu.org/copyleft/gpl.html for more details...

For updates and information, please visit http://seq.sourceforge.net/
ShowEQ 5.0.0.15, Built from 'main.cpp' on Oct 15 2004 at 12:24:58
CVS: @(#) $Id: main.cpp,v 1.33.6.5 2004/09/24 04:25:53 dohpaz Exp $ $Name: pre_5_0_beta $
Using GCC version: 3.2.3
Using glibc version: 2.3
Using Qt version: 3.3.2
Using headers from linux version: 2.4.20
Using EQItemDB: @(#) $Id: itemdb.cpp,v 1.10.6.3 2004/09/24 04:25:53 dohpaz Exp $ $Name: pre_5_0_beta $
Using GDBM: This is GDBM version 1.8.0, as of May 19, 1999.
Running on Linux release 2.4.21-20.EL for processor i686

Using config file '/root/.showeq/showeq.xml'
Loaded preferences file: /usr/local/share/showeq/seqdef.xml!
Loaded preferences file: /root/.showeq/showeq.xml!

[Cryonic]

with or without fixes for the Oct 13th patch? Do you have session tracking turned on?

[lildr00d]

with or without fixes for the Oct 13th patch? Do you have session tracking turned on?


With the Oct 13 patches. Session tracking on

Problem occurs if I hard code IP address or use the 127.0.0.0 to autosearch.

Only happens in OOW zones. 1st zone will load, 2nd zone will display map and show my location but will not decode and shows --busy loading-- in status bar, 3rd zone decodes normally, 4th zone will display map and show my location but will not decode and shows --buzy zoneing--

If I use ''monitor next session" command before I zone it will decode normally and works fine.

Additional information. If I Succor (any spell line like it) into a zone already decoded it will not decode. The reverse is true also. If I succor in a zone that will not decode when succor is complete the zone will appear as normal with full decode.

Please let me know if you need any more info or need me to provide some sort of output from my console.

[Cryonic]

Try turning off Session Tracking

[lildr00d]

Try turning off Session Tracking



Thanks Cryonic that fixed it.. Unsure why it only errored out like that in OOW. I always have session tracking on since I never know when Im going to have to log in a bot.

Figured it was something silly stupid on my part