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? |
Quote:
|
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.
|
Quote:
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
|
Quote:
|
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.
|
Quote:
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.
|
All times are GMT -4. The time now is 02:51 AM. |
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.