Any able to post a compiled fix here ? Please ?

hehe I'm compiling as fast as I can.. :-) Wife made dinner so...

hummmm fooooood...... lol

edit: depending on what your having, you could post that here too
i'm hungry....
vRandom

I am running the lastest peq velious rc1 database. all I did was run gthe following in a cmd window: "mysql -u[user] -p[password]" this brings up your mysql window. In it I typed "CREATE DATABSE eq;" followed by "USE eq;" next I sourced two of the four files from the website. by typing "source load_system.sql;" once it finished, took awhile to do I did the next file "source load_empty_users.sql;" after that nothing else have I changed.

after that I just configured the three ini files and I was good to go.

I can load the server, only errors I see are the missing opcodes everyone else is getting, and the no attacking thing which if reading thru here is right is a translation problem.

I am also having a router issue where to login on my network I have to set all the ips in the ini files to localhost, but when configured for public play anyone else but my local lan can play including th computer hosting the server.

If I must.. =)

This is JUST World.exe & Zone.exe

Mike

http://www.asrc.info/beta/EQEmuFixed.zip

bah I am stuck on a farkin linker error... See my posthere if anyone has seen this one and knows what I didnt include correctly.

http://www.eqemulator.net/forums/sho...078#post113078

MickeyUSC, do you happen to have a zoneperl.exe as well? Or better yet, know what I need to add so I can generate my own bins?

Just downloaded and tested it, I can now run around and attack, Well done.

yep, can run around and kill stuff :) thanks to all

vRandom

I used the above fix and it solved the melee out of range but spells still say I cannot see my target. I used #summon on a mob and tried casting and still get the error.

make sure you have download the map files with out them in your eqemu folder you will not have line of sight. Therefor causeing the you can not see the target.

Thanks Mike :grin: now i just have to stop everything from chasing me down like a wild dog lol

I got it to work by just loading load_empty_users before load_system. Very odd. :P

is this normal???

Ceerke: Large position change: 61.826026 units
Coords: (592.4846, 3252.9341, -61.3056) -> (616.4312, 3195.9385, -60.5851)
Deltas: (2.38, -6.20, -1.31) -> (2.42, -6.21, 0.00)
Message: Hail, Talin O`Donal
Ceerke: Large position change: 105.569448 units
Coords: (620.9136, 3159.3523, -60.7372) -> (607.6788, 3054.6328, -58.8456)
Deltas: (-0.72, -6.61, 0.00) -> (-0.82, -6.62, 0.00)
Ceerke: Large position change: 53.924070 units
Coords: (607.6788, 3054.6328, -58.8456) -> (600.6883, 3001.2468, -55.8666)
Deltas: (-0.82, -6.62, 0.00) -> (-1.18, -6.56, 0.00)
[Error] OP size error: OP_ClientUpdate expected:36 got:37
[Error] OP size error: OP_ClientUpdate expected:36 got:37
[Error] OP size error: OP_ClientUpdate expected:36 got:37
[Error] OP size error: OP_ClientUpdate expected:36 got:37
[Error] OP size error: OP_ClientUpdate expected:36 got:37
[Error] OP size error: OP_ClientUpdate expected:36 got:37
[Error] OP size error: OP_ClientUpdate expected:36 got:37
[Error] OP size error: OP_ClientUpdate expected:36 got:37
[Error] OP size error: OP_ClientUpdate expected:36 got:37
[Error] OP size error: OP_ClientUpdate expected:36 got:37
[Error] OP size error: OP_ClientUpdate expected:36 got:37
[Error] OP size error: OP_ClientUpdate expected:36 got:37
[Error] OP size error: OP_ClientUpdate expected:36 got:37
Ceerke: Large position change: 64.509332 units
Coords: (592.1464, 3280.5466, -59.2402) -> (584.3849, 3344.1687, -51.9296)
Deltas: (-0.98, 6.59, 0.00) -> (-0.57, 6.64, 0.00)
[Error] OP size error: OP_ClientUpdate expected:36 got:37
Ceerke: Large position change: 62.741442 units
Coords: (576.5767, 3319.5452, -54.3136) -> (578.0970, 3381.5046, -44.5565)
Deltas: (0.06, 2.50, 0.00) -> (0.16, 6.64, 0.00)
[Error] OP size error: OP_ClientUpdate expected:36 got:37
[Error] OP size error: OP_ClientUpdate expected:36 got:37
[Error] OP size error: OP_ClientUpdate expected:36 got:37
[Error] OP size error: OP_ClientUpdate expected:36 got:37
[Error] OP size error: OP_ClientUpdate expected:36 got:37
[Error] OP size error: OP_ClientUpdate expected:36 got:37
[Error] OP size error: OP_ClientUpdate expected:36 got:37
[Error] OP size error: OP_ClientUpdate expected:36 got:37
[Error] OP size error: OP_ClientUpdate expected:36 got:37
[Error] OP size error: OP_ClientUpdate expected:36 got:37


i was running through everfrost and noticed zone was saying something diff then OP_ClientUpdate expected:36 got:37 when i walked in a curtain spot
i took a screen capture so you know where i was at the time

http://img372.imageshack.us/my.php?i...erfrost6sn.jpg

http://img372.imageshack.us/my.php?image=front6tk.jpg

I noticed that too last night. If its having an effect in the game, I havent noticed it, but I think those messages only appear when you turn right or left. They didn't seem to pile up in my log for not moving, backing up or going forward.

those op size error can be ignored as they do only show when turning. only thing that might happen is someoneelse on your server might see you looking another way on there screen when your faceing them till you walk foward or reverse.

Aargh!! I think I need this fix. Everything seems to work now. Except my position(Server)remains at zonepoint. I also need to make the correct DB as mine is missing the correct Items table.

Well..On to the fixing DB problems. I hope I can get the rest soon.

his link is down for me but if you need to get it you can get it here while it last. don't know how long it will stay up sooo.

http://www.rapidsharing.com/out.php/...EQEmuFixed.zip

I did compile a new zoneperl.exe last night, but it has another problem and I haven't had time to look into it, yet. It kicks out a run-time error from the perl quests and crashes the zoneperl.exe that generated it.

I was just doing a little reading of ActiveState perl's README and I see in there a blurb about Perl 5.8 not being compatible with earlier releases of Perl and "You have to recompile your XS modules." I believe the quest subsystem uses these XS modules, right? So either I need to recompile those or I need to back down to a previous release of ActiveState Perl? Like 5.6? I wonder if thats not what was tossing that runtime exception in my updated zoneperl.exe last night... My server does have ActiveState Perl 5.8 installed and I think thats a relatively recent release of ActiveState Perl. Anyone else running ActiveState Perl 5.8? Anyone have this working ok with ActiveState Perl 5.6?

for my 6.0 and 6.1 i used ActiveState Perl 5.8 and had no issues. for 6.2 i dunno i don't have a working zoneperl for 6.2 nor do i have perl installed yet from having to do a reformat.

Cool then I guess it must be a real bug in the zone.exe code. I was hoping it was the Perl 5.8 though when I read that README.. :-)

sorry for my noob question but how do i get those error logs to work?? with world and zone, the only logs going it to the logs folder are zone commands .txt

Anyone get a working Zoneperl.exe compiled successfully yet with the ClientUpdate fix? Loving attacking mobs on the server but hoping to start working on that huge collection of PERL quests I downloaded!

Thx
J

Thanks..That worked. At first world.exe was crashing when I try to zone. So I put the original world.exe back in and now it seems to work a treat!
I also am using a new database so now the only errors I get are the opcode thingies.

I noone whats to see another post here
 

Well i have been playing around and well i found another issue. The world.exe in the EQEMUfix zip that mikeusc did has an issue with it (for me at least). If you try to use the command #zone you get a loving M$ error window. when i am in BB and type #zone firiona the zone will bootup all looks normal till the error window pops up saying world.exe has encounterd an error and needs to be closed. Fix for was i went back to the original world.exe from the ninaries and i can sit here and bounce from BB to firiona via the #zone command.

not sure anyone else encountered this or not seems some files work better on other pc's and some pc's the files hate them heh. so if you encounter this you can replace the fixed world.exe with the original one or worlddebug.exe from binaries.


/me runs and hides from the mob for finding another bug

That might be because when he released the "fix" he only released a changed world.exe and a zone.exe, however the source code file he edited is used in EmuMemShare.dll as well! I might be wrong about that causing the problem you describe, but I was thinking it might lead to some instability since the EQEmuShareMem now expects a Player struct that is "different" than what world and zone will offer up.. Anyway, When I get home maybe I can give you a new fix you can try out. Right now I'm working on a project for my employer and I'm looking at zoneperl issues when I'm bored.

I haven't run into this one yet. When I get home today I'll try the specific zones you've referenced. I'm using both World and Zone that MikeyUSC provided.

well i have nomore M$ error by just replacing the zone file from his fix and by useing the original worl or worlddebug. now i'm just trying to find which arangement of files will work best together to try and make it alitter easier for a first timer to get started.

I have compiled a working zoneperl.exe along with a world.exe and a EmuMemShare.dll that looks good. Quests work and I can attack stuff, well, kinda.. While attacking stuff I found a new error message in my zoneperl.exe.. "Catching Mob Crash". It happens everytime my char "strikes" a mob in melee. Not sure whats causing this yet, but spell attacks do work so, thats good.. hehe As soon as I figure out the "catching mob crash" error, I'll be happy to share my patches with anyone interested.

me interested :)
vRandom

I found this article posted back in 11/04. Maybe there's a note in a changelog somewhere that might help?

http://www.eqemulator.net/forums/sho...catching+crash

Its only like that post in that it is the same error message, but its not "continuous" or "spammed" in zoneperl.exe. You really do get 1 error message for each tiem your char "strikes" a mob in melee. I'm trying my newest zone.exe now to see what thats like so I know if this really is isolated to only zoneperl.exe.

EDIT: I just tried my latest zone.exe which should match MickeyUSC's patch and i can melee and spell attack mobs no prob, so that mob crash is isolated only in the perl code within zone.exe (zoneperl.exe). I'll looking to it...

only reference i found to "Catching Mob Crash" was in net.cpp around line 419

printf("Catching Mob Crash...\n");

if that helps
vRandom

edit:
could just be there for debugging, its wrapped in an if

#ifdef CATCH_CRASH
try{
entity_list.MobProcess();
}
catch(...){
printf("Catching Mob Crash...\n");
}
#else
entity_list.MobProcess();
#endif

only difference is the message....

I'd like to think that's there for a good reason. Obviously, that line is tossing an exception, but since i'm getting ready for bed I'm commenting that out for the sake of a test and I'm going to try it out quick before I go to sleep. I'll post back here in a minute or two and update if its "workable" for now.

As I feared, simply commenting that out for a quick fast just leaves an unhandled exception that crashes zoneperl.exe. I did search the source quick and it looks like the only good that can toss an exception is limited to the perl subsystem, which explains why only zoneperl.exe is producing this error. The good news is, its just an unhandled exception. Shouldnt take me too long to locate the where and why of it. Maybe I'll stay up for another hour... :-)

Such dedication ;)
vRandom

Can I trade "dedication" points for a simple answer to the question that is just driving me nutz? Why oh why is this source code not allowing me to debug it with breakpoints? Its crazy! If I could place breakpoints and debug it like I've done with any other source code since 1992 I'd probably have more bugs fixed. It's totally slowing me down.

Anyway, I'm recompiling now. I'm going to see exactly what this exception message is and then hopefully I'll be able to offer a patch soonish.

Good question on the breakpoints, they are quite helpfull. Sorry I can't offer any suggestions, maybe its solar flares (http://www.tbnweekly.com/content_art...105_fpg-02.txt) lol ;)

I just now got my .net installed...But thats as far as i've gotten atm... had to go back to work... grrr

vRandom

When you can next, give it a try. lay a breakpoint, recompile in debug config and watch it never stop... Or just try to "step into instance".. that doesnt work either.

Ohh boy sounds like tons of fun.... lol that will drive a person nuts....

vRandom