Go Back   EQEmulator Home > EQEmulator Forums > Development > Development::Bug Reports

Development::Bug Reports Post detailed bug reports and what you would like to see next in the emu here.

Reply
 
Thread Tools Display Modes
  #1  
Old 12-05-2006, 03:13 PM
John Adams
Demi-God
 
Join Date: Jul 2006
Posts: 1,552
Default

Nice. Is there anything in the logsys you can turn on to capture what the server is saying to the client? When I kick on logging, I get tons of info - some of it actually makes sense sometimes.
Reply With Quote
  #2  
Old 12-05-2006, 03:18 PM
sfisque
Hill Giant
 
Join Date: Oct 2006
Posts: 248
Default

nothing useful. basically the server isnt complaining and disconnecting the user. which leads me to believe the client is waiting for something from the server and not getting it, or its getting something that confuses it and it disconnects.

i'm not seeing anthing that looks like an exception or error message, just lots of "i'm doing this to that object" stuff type messages.

== sfisque

ps: i'm almost tempted to try running ./zone inside of a debugger, but i'll have to learn how to use gdb first
Reply With Quote
  #3  
Old 12-05-2006, 03:20 PM
cavedude's Avatar
cavedude
The PEQ Dude
 
Join Date: Apr 2003
Location: -
Posts: 1,988
Default

While debugging, you should also keep in mind that the 0.6.2 client does not suffer from this bug, only Titanium so any changes made has to allow both to work.
Reply With Quote
  #4  
Old 12-05-2006, 04:03 PM
sfisque
Hill Giant
 
Join Date: Oct 2006
Posts: 248
Default

how would one acquire this mystical 0.6.2 client? i thought the current evolution of eqemu was designed around titanium compatability?

== sfisque
Reply With Quote
  #5  
Old 12-05-2006, 04:18 PM
cavedude's Avatar
cavedude
The PEQ Dude
 
Join Date: Apr 2003
Location: -
Posts: 1,988
Default

0.6.2 is used by us old-timers. It currently is far more compatible than Titanium. The problem is, we can't give it to you. It violates the forum's policies.
Reply With Quote
  #6  
Old 12-05-2006, 04:45 PM
sfisque
Hill Giant
 
Join Date: Oct 2006
Posts: 248
Default

then i guess my delving is done. i'd put money on the table that something changed in the "death, corpse, move to bind" packets between 062 and titanium and eqemu doesnt grok how to send the correct info to the newer client.

since i dont have a live account, i'm out of the loop now. anyone want to collect the packets and try patching zone to properly update the titanium client upon death?

== sfisque
Reply With Quote
  #7  
Old 12-05-2006, 04:52 PM
cavedude's Avatar
cavedude
The PEQ Dude
 
Join Date: Apr 2003
Location: -
Posts: 1,988
Default

Collecting packets won't work, the Titanium client doesn't work on live. In fact, I don't think it ever did.
Reply With Quote
  #8  
Old 12-06-2006, 05:59 AM
sfisque
Hill Giant
 
Join Date: Oct 2006
Posts: 248
Default

ok.

just so i'm seeing this in the correct light, i perceive the issues are this:

(and chime in if i got it wrong)

1) at some point between 0.6.2 and titanium, something "possibly" changed in death handling on the client.

2) all of the old timers have their "golden" 0.6.2 frozen clients which work fine.

3) at some point, a line was drawn in the sand and titanium compatability was stated as the goal to prevent the constant chase with Sony.

4) there is a reticence or hesitation to fix the "death in bind zone" bug because it might invalidate the 0.6.2 version which eqemu doesnt "officially" support.

5) someone might be working on this besides me, but they havent chimed in yet.

6) my limited knowledge of the eqemu has brought me upto a brick wall.

so, barring anyone stating otherwise on the above points, does anyone want to help me out in fixing this. i chased it a decent way down. from what i can see, the disconnect happens sometime AFTER the ->Death() method returns. i know this because the toon's coords are correct (at bind point) when they respawn after the LD. i'm not an assembler whiz so disassembling the client (which could be considered illegal, i'm not sure on the specifics of that) is technically not an option atm, so i'm not sure where to go from here. there appear to be a few people who are adept at eq packet analysis and are knowledgeable of the underpinnings of the client/server relationship. do any of these people want to help me find a fix for this. i know you all have your pet projects and this is a low priority if you have the magical 0.6.2 client, but i'm sure i can fix it, if i can get a little hand holding. whether we migrate it into the CVS or put it on a branch, i dont care. i just want my server to work with titanium since thats the "communicated" line in the sand.

== sfisque
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

   

All times are GMT -4. The time now is 10:53 PM.


 

Everquest is a registered trademark of Daybreak Game Company LLC.
EQEmulator is not associated or affiliated in any way with Daybreak Game Company LLC.
Except where otherwise noted, this site is licensed under a Creative Commons License.
       
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Template by Bluepearl Design and vBulletin Templates - Ver3.3