Many path markers crash.

#1 It's possible that you exceeded a hardcoded count limit. Try upping the constants. :)

#2 That's what I had guessed, but I couldn't find any constant in the path manager. :(

#3 Ah, it's related to the size of the network packet. Too long of a path makes the packet overrun, giving the out of range write error.

I've added an assrt to catch this, so that you'll at least be warned when you're in the neighbor hood of an error. It's naive so it won't catch all error situations.

#4 I get an out of range read error when trying some rw servers, and sometimes in torque...

#5 Out of range read means that the network code read past the end of the packet, usually.

#6 Woot! Ben, 1 minute, counted with the irc timestamps, after you left, I had fixed it :P
It works perfectly, tested it in a stock TGE build with a 100+ path and it worked perfectly.

For the rest, what I've done, thanks to Ben's suggestion and introduction, was to modify the PathManager to use several NetEvents to send the data, since a single packet wasn't enough to send all the path markers I had. So I ended adding 2 NetEvent types, one for the path info, sent only once and one for each chunk of data. So it sends one with the info and many chunks of 10 nodes each until it has sent all the nodes.

Thanks Ben, you saved my potatoes on this one :)

#7 You'll be submitting that as a resource, right? :)

#8 Mmmm I will have to think of it :P

Sure I will, It's the least I can do.

Edit: Typo, just woke up :)

#9 Thanks Xavier :)