Freeze at "initializing"

01/20/2013 19:23 U2_Caparzo#1
Hi everyone, i hope you can help me with this problem.

Well sometime ago i started a "custom source" (using 12Tails's socket system and using impulse's source as reference), i have advanced a little bit like jumping, spawn entitys, but there is a problem wich i still can't figure why it happens:
After receiving the packet 1052, i'm sending the packet 1004 with "ANSWER_OK" for login, then i send the packet 1006 with character's info, here is the problem, the client should send the GeneralData packet, but it isn't sending it so i can't complete the login, what confuses me is that sometimes i can login and others not, i don't get why.

the packets structures are correct, had someone this bug/error w/e it is? or what could be causing this?

thanks
01/20/2013 20:00 _DreadNought_#2
Sure you're splitting the pkts?
01/21/2013 00:56 U2_Caparzo#3
Quote:
Originally Posted by _DreadNought_ View Post
Sure you're splitting the pkts?
in that case, the problem would not happen every time i try login?, but it's kinda random, sometimes i login succesfully at the first try, others i try 2 or 3 after i can login, the GameServer doesn't receive anything while waiting for the GeneralData packet, and after more or less 5 seconds, it receives the packet 1134(i dk what it's used for).
01/21/2013 02:00 Darkstorm101#4
i was having same problem when i was using projectx source 5165 sometimes it would log me in and sometimes it wouldn't
01/21/2013 02:02 _DreadNought_#5
-If you weren't splitting packets sometimes they would come in correctly and sometimes they wouldn't.

The packet 1134 is used for Quests and I'm not entirely sure on your problem, I know in the later patches me and Ultimation experienced a similar issue with getting random dc's on connecting to GameServer with AcidCO and after extensive research concluded it's an issue with CO's client.

However if you are not in the later patches the problem is likely your end.
01/21/2013 18:31 Super Aids#6
In your socket system receive 2 bytes first for the size. Then receive the size you get, if the size is not the same after receiving next bit then you just have to receive the remaining bytes.

That way you won't need to split packets.