Alright I've made many sources before, but I've NEVER came across this problem before. Males can login, but females can't. When a female logs in, they either get stuck at initializing or they get disconnected at SetLocation being sent to client. This is for patch 5180.
I login and I check the client's debug log and I see all this.
I actually wrote this response before seeing your immature "inbfangsays" paragraph:
---------------------------------------------------------------------------------
Project Kibou had this problem. I'm pretty sure it was something to do with character info or how I was breaking up the packets. Don't be a ***** and break point it. Where does it hang (not visually, but where does it literally STOP handling the client's login - where and after sending what).
I actually wrote this response before seeing your immature "inbfangsays" paragraph:
---------------------------------------------------------------------------------
Project Kibou had this problem. I'm pretty sure it was something to do with character info or how I was breaking up the packets. Don't be a ***** and break point it. Where does it hang (not visually, but where does it literally STOP handling the client's login - where and after sending what).
Obviously I tried that, how else would I know the client disconnects at SetLocation?
Obviously I tried that, how else would I know the client disconnects at SetLocation?
You said "or", so find out where it hangs / disconnects using a desk check.
Edit: Desk checks are when you follow a variable along as it goes through an algorithm, in this case, follow the client as it goes through the login sequence.
You said "or", so find out where it hangs / disconnects using a desk check.
Edit: Desk checks are when you follow a variable along as it goes through an algorithm, in this case, follow the client as it goes through the login sequence.
I already followed it, when it hangs, its at the same location.
I already followed it, when it hangs, its at the same location.
Before or after you send it? Does it disconnect RIGHT when you send it? You said before that it sometimes just hangs and sometimes it just disconnects. Does it do one... the other... both?
Before or after you send it? Does it disconnect RIGHT when you send it? You said before that it sometimes just hangs and sometimes it just disconnects. Does it do one... the other... both?
RIGHT when its sent server->client.
It varies, sometimes get stuck at init.
Sometimes disconnects.
And also, its odd, Large females can login, but with ****** up mesh, small females can't at all.
RIGHT when its sent server->client.
It varies, sometimes get stuck at init.
Sometimes disconnects.
And also, its odd, Large females can login, but with ****** up mesh, small females can't at all.
If it varies like that, it might have to do with the socket system handling packets incorrectly on another thread. That is a really ****** up error though. Mine wasn't that ****** up - I think it was that my cipher was advancing incorrectly.
When you're doing your desk check, do you follow it to where it stops? If it stops at the end of the receive and doesn't initiate the next receive, then you have a packet / socket problem. If it does the next receive but the length is insane and causes a disconnect, then you know that's obviously a cipher problem.
Edit: Does it really stop RIGHT at the send as you say it does? Or is there another thread behind it? Put a breakpoint on the receive like I said. Hopefully you figure it out.
Quote:
Originally Posted by KraHen
Maybe you`re using the wrong offsets for your patch version? :P
If it were the packet, then it would still advance but show a black screen with the GUI.
If it varies like that, it might have to do with the socket system handling packets incorrectly on another thread. That is a really ****** up error though. Mine wasn't that ****** up - I think it was that my cipher was advancing incorrectly.
When you're doing your desk check, do you follow it to where it stops? If it stops at the end of the receive and doesn't initiate the next receive, then you have a packet / socket problem. If it does the next receive but the length is insane and causes a disconnect, then you know that's obviously a cipher problem.
Edit: Does it really stop RIGHT at the send as you say it does? Or is there another thread behind it? Put a breakpoint on the receive like I said. Hopefully you figure it out.
If it were the packet, then it would still advance but show a black screen with the GUI.
Lemme clarify something;
When the client disconnects, the source still goes on with everything since the client is still an un-null variable. But when its stuck at initializing, its directly onto the sending of the SetLocation, then the source stops processing said client.
Said above. Check if your packet mesh is wrong by 1 offset, that could mean your packetwriter doesn`t work properly neither and causes whatever, like an overflow which could stop the rest of the process.
[Problem]Habe ein Problem und zwar spinnt mein VPC etwas(ohne Grund)?! 07/28/2011 - Metin2 Private Server - 10 Replies Also wie schon gesagt meins Server spinnt wodurch kiks usw. kommen :(
ich lade euch die Screens in den Anhang, mit der Hoffnung, dass ihr mir helfen könnt :) wäre echt sehr nice :)
