11/05/03 EQLive breaks SEQ, discuss fixes here.

[Zaphod]

Originally posted by perlmonkey
I realized I had patched opcodes.h, but not picked up the new decode.cpp. I did that, and all was well. I have not had the zooming-out problem again, but that happened in upper Guk, and I have not been back there. Perhaps only certain zones are seeing this problem?

No, from your errors it was obvious that you forgot the decode.cpp.

error on zone-client: size > left (size=74, left=38, opcode=0x0024)
error on zone-client: size > left (size=119, left=38, opcode=0x0024)

These errors are almost exclusively related to having a bad decode.cpp.

Enjoy,
Zaphod (dohpaZ)

[suseuser7341]

And thanks perlmonkey, I knew perl would be great to do it, just I am too rarely using it to figure it out how to do it

[Leetlewon]

Procedure I used to get ShowEQ working again -

Downloaded newest version. Applied patch.

Dropped new decode.cpp and new opcodes.h into src.

Compiled & installed. Works great!

[cbreaker]

It works for me too but seq has crashed twice on me now, whereas before the EQ patch it was rock solid.

I'll run it from a terminal this time and post the details if it crashes again.

Thanks for the patch.

---
Okay here's the last screen of messages:

WARNING: OP_WearChange (0125) (dataLen:0 != sizeof(SpawnUpdateStruct):9)!
error: size > left (size=138, left=74, opcode=0x0024)
error: size > left (size=172, left=154, opcode=0x003b)
error: size > left (size=27399, left=198, opcode=0x0024)
WARNING: OP_WearChange (0125) (dataLen:0 != sizeof(SpawnUpdateStruct):9)!
WARNING: OP_WearChange (0125) (dataLen:0 != sizeof(SpawnUpdateStruct):9)!
error: size > left (size=15111, left=270, opcode=0x0024)
WARNING: OP_WearChange (0125) (dataLen:0 != sizeof(SpawnUpdateStruct):9)!
WARNING: OP_WearChange (0125) (dataLen:0 != sizeof(SpawnUpdateStruct):9)!
error: size > left (size=138, left=92, opcode=0x0024)
error: size > left (size=96, left=84, opcode=0x0024)
error: size > left (size=241, left=46, opcode=0x0024)
error: size > left (size=216, left=83, opcode=0x0024)
error: size > left (size=241, left=77, opcode=0x0024)
error: size > left (size=239, left=62, opcode=0x0024)
error: size > left (size=16650, left=144, opcode=0x0024)
error: size > left (size=239, left=8, opcode=0x5a03)
error: size > left (size=138, left=128, opcode=0x0024)
error: size > left (size=102, left=75, opcode=0x0024)
error: size > left (size=252, left=52, opcode=0x0024)
WARNING: OP_ClientUpdate (0024) (dataLen: 171 != sizeof(playerSpawnPosStruct):18 or sizeof(playerSpawnSelfStruct):30)
Segmentation fault

[JamTune]

LoL wow thought it was just something I did wrong. I zoned into VT and it didn't load the map but all the mobs where there. I loaded the VT map and was ok I can work with this.. Then WOW I was in CS,GE and lots more in a matter of sec. Now I know that wizards can travel fast but man I had no idea I could zone like that

[lildr00d]

Seems stable now.. I downloaded the opcode.h -- I figured I fubared something adding 2 to all the codes myself which is why I was haveing issues.

Everything that I use SEQ work.. skittles, where I am, where my guild is.. and more importantly where my corpse is.. har har

[cbreaker]

Weird. I did the same and it's really unstable. Crashes about every 5 minutes. Oh well I'll wait for the official release.

[CiscoKid]

Are the attached opcodes.h and decode.cpp files that are in this thread now in CVS or we still have to patch 'em in before compiling?

[mirulo]

First thx a lot for the great job !!!!! Thx at Developpers and contributing members for this !!!!

Are the attached opcodes.h and decode.cpp files that are in this thread now in CVS or we still have to patch 'em in before compiling?

These 2 updates appear in cvs -z3 update :

#make distclean
# cvs [...] login
# cvs -z3 update
# cvs [...] logout
# export [...] (if you need to do recomp qt, gcc...)
# make -f Makefile.dist && ./configure && make && make install

For me, with these 2 updates, the errors aren't no more in terminal window but Seq will crash (freez) all times... :/
(i've ATI Radeon 7000 familly's on my Seq computer, PIII 600, 512 Ram, RedHat 9 under Gnome Desktop)

(So sorry for my poor english, but i'm french )


Also i have one question: When i run Seq with root account, no error message appear in terminal but when i start Seq with my user account (with SU command of course) i have this message at begin: "Session Management error: Authentification Rejected, reason: None of the authentification protocoles specified are supported and host-based authentification failed "

It's bad Doc ??? You think i must prefer run Seq in root or this message aren't important ??

Thanks in advance !!

[BlueAdept]

Originally posted by mirulo
For me, with these 2 updates, the errors aren't no more in terminal window but Seq will crash (freez) all times... :/

When you say crash, do you mean that it will just sit there for a while (with the hard drive flashing), but eventually will decode?

When I upgraded to .17 and added the 2 files, I had to revert to using --itemdb-disable added onto the command line. Without it, it would just make my hd flash for about 1-2 minutes every time I zoned. .16 I didnt have this problem (but earlier versions I did).

[mirulo]

it would just make my hd flash for about 1-2 minutes every time I zoned

WOOOOOT Thx BA !!!!! In fact it's that: Seq freez and take about 30 sec/1min for decode each zone !!!! But i've all and he work very good !!!

Happy face !!! That's work !!!! You're the best !!!


So, for my second problem ... !!!??? LOL


Bybye =)

[quackrabbit]

A patch to take bring CVS up to date with EQ as of 11/05/03.

NOTE: DO NOT USE THIS IF YOUR SEQ IS WORKING!

This is just a one stop patch that includes all of the fixes mentioned in this thread.

To install, download CVS then apply this patch to your showeq directory. (patch -p0 < cvstonov05.patch)

EDIT: File removed due to it now being obsolete. Thanks Zaphod!!

[PhoenixZorn]

Originally posted by BlueAdept

It is probably to fix the occasional crashing of the client with Geforce cards when you camp out. Ive had it happen to me last night and several people on EQ's board posted messages about it.

Hopefully no opcodes will change, but it will probably have a new exe file.

Edit:seems there were a few other bugs like spawned mobs killing themselves and a vender who was selling stuff for nothing.

The campout bug was experienced by me for a total of 24 hours, in which time I had dumped my install of Win2k AS for a copy of Win XP Pro. Needless to say, as soon as I realized what was going on, I switched back to 2k AS... with 2 accounts and one windows box... it's a pain in the ass to crash every time you camp.

By the way, those campout crashes that I experienced happened on wednesday... and I reinstalled 2k thursday morning at about 3am...