[ENet-discuss] Two back-to-back send calls not allowed?

[Jay Sprenkle]

Ah. sounds like you already thought of the problem I was imagining.
You might also consider installing Wireshark. With it you can trace what is
actually being sent.
Then you can verify if it's the sender or the receiver that's the problem.

On Wed, Aug 11, 2010 at 4:57 PM, Richard Becker <richard_3d at hotmail.com>wrote:

>  It shouldn't over write the first message that makes no sense. The
> function is an abstraction and I am passing it the data to send not an eNet
> packet itself. Inside of the function a new packet is created and the data
> for the packet is set. I have debugged and traced all the way into
> enet_peer_send (which gets called from broadcast). Everything seems to be
> making it. I still dont understand why the client never receives the first
> message though and only the second one. Does this have something to do with
> enet internal queue for sending messages? Thanks - Richard
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cubik.org/pipermail/enet-discuss/attachments/20100811/834ca4cc/attachment.html>