Another odd problem

Well, I decided to dump that general data packet when its sent. SetLocation to Client. Here's the dump when a female logs in.

And for males

What would cause the buffer to be different because of a different mesh logging in?

Quote:

Originally Posted by Arco. Well, I decided to dump that general data packet when its sent. SetLocation to Client. Here's the dump when a female logs in.  Spoiler Code: 24 00 1A 27 41 42 0F 00 EA 03 00 00 00 00 00 00 $..'AB.......... 92 D1 11 00 4A 00 00 00 B6 01 79 01 00 00 00 00 ....J.....y..... 00 00 00 00 54 51 43 6C 69 65 6E 74 50 00 7F 04 ....TQClientP... 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 54 51 53 65 ............TQSe 72 76 65 72 rver And for males  Spoiler Code: 24 00 1A 27 42 42 0F 00 EA 03 00 00 00 00 00 00 $..'BB.......... DA 08 12 00 4A 00 00 00 B6 01 79 01 00 00 00 00 ....J.....y..... 00 00 00 00 54 51 53 65 72 76 65 72 ....TQServer What would cause the buffer to be different because of a different mesh logging in?

Ohhh!!!!! Your server is sending the flower packet with the set location packet - but it's never changing the "TQClient" (which is sent from the client in the general data / set location packet) to "TQServer"! That's what's causing the client to hang / disconnect!!

Quote:

Originally Posted by Fаng Ohhh!!!!! Your server is sending the flower packet with the set location packet - but it's never changing the "TQClient" (which is sent from the client in the general data / set location packet) to "TQServer"! That's what's causing the client to hang / disconnect!!

Well, we finally came to the source of the problem. Thanks alot Fang.

#Problem fixed.
My packet splitter had one small flaw in it, and I fixed it. Thanks everybody, and especially Fang and Lateralus.