Hm, if the unreliable messages are important, and you're sending updated packets if not acknowledged, it sounds like: 1. You're thinking they really ought to be reliable 2. You're handling them as unreliable, since you're resending with new information anyway. Why not skip checking ACK's, since you're not really using that anyway? And just send out info every 0.5 seconds? Not sure about the 6 secs delay; perhaps by default a reliable re-send timeout is 5000 ms. Although if you get unack'd packets upon packets you might overflow the pipe (but that won't happen quickly). Cheers, Ruud
_____ Van: [email protected] [mailto:[email protected]] Namens Joel Anderson Verzonden: Monday, May 25, 2009 07:13 Aan: [email protected] Onderwerp: [ENet-discuss] Packet loss, unreliable packets Hi, I'm wondering if people can share there experiences with packet loss or large delays in transmission they've had with enet and how they solved it? >From here on I'm going to try provide as much info as possible in case someone can spot something wrong. Currently I've been seeing delays up to 6 seconds on some messages we are sending. It doesn't happen all the time however it happens sporadically. We have enet's flow control turned off. Note the unreliable messages are just as important as the reliable messages. When we see it roundtriptime will spike for a second and then go back to normal when it finishes. We use roundtriptime from enet to resend unreliable packets (with updated information) when we don't get an acc back. We cap this to .5seconds (ie if latency is above this then we send it again anyway). I've a feeling its related to message flooding. Normally our transmission is about 4kbits per second but can spike to 10kbits per second (note the data I have is averaged so I don't know the worst case). We use both unreliable and reliable messages. Our unreliable messages are set to a maximum packet size of 1kbytes which can be hit some times. Is 1kbyte a good size? What size have people found to be optimal for lowest latency sending of messages. Also what is a good rate to send/receive the packets at? Is it possible tht enet is throwing away unreliable packets if it can't send them? Is it possible to know when this happens so I can handle it? Out users machines are standard everyday PCs with standard internet connections (ie 256down and 64up). However we even see problems on faster connections as well. On really high bandwidth/low latency connections we don't see the issue. Any tips?
_______________________________________________ ENet-discuss mailing list [email protected] http://lists.cubik.org/mailman/listinfo/enet-discuss
