I don't get it, millisecs() returns the CPUclock in millisecound. But who say that my clock ain't going 2h 34min 3days 23sec and 123ms Wrong. Then the client will think the packet has an Enormous lag. Or should I set the computer clock somehow? If I do A=millisecs() A gets the value of 36632413. Now let say I send and receive a package I can check millisecs() again to see how it took for the client to reply, this is the latency,right? But this is not the same as a timestamp. So what I should sent in each packet is my A=millisecs()+LastpackedDelay?? But what should the client do with this millisecs_int. If the client substracts his millisecs() from the millisecs()_int received in the last package then he'll get a huge number or?, it seems like I'm walking in circles =)
If you have any good reasourses/links I'll be happy to read about the subject,I have searched, but I haven't found anything really useful.
Still trying// Wave~
If you have any good reasourses/links I'll be happy to read about the subject,I have searched, but I haven't found anything really useful.
Still trying// Wave~