Thanks! Just moved it over to the correct section now. Bit of an oversight on my part
Note that this claim could be potentially be misleading, calculating the result of a two-way trip by just multiplying a one-way trip is kind of a heuristic at best.
The best comparison I can think of would be if you were a package deliverer and you need to to get a relatively precise amount of time that it takes to go to and from your destination. If you just take how long it took to get to your goal, that doesn’t account for traffic stops, red lights, other distractions, etc. on the way back.
Delivering packets is a very similar idea, mostly due to sudden slowdowns. So a multiplied version of this function to determine the player’s round-trip latency wouldn’t be very accurate overall. instead you would probably be better off only using this as a measure of the client’s outgoing latency.
4 Likes
Are you in a game?
Try doing game.Players.LocalPlayer instead of your username (it might be a lock thing)
Got it to work. Thanks a lot!(character limit)
Not to mentiontion it is clearly stated that this is “Isolated Ping” in the dev docs:
GetNetworkPing returns the isolated network latency of the Player.
Which does NOT include time spent during compression/decompression, serialisation/deserialisation, data processing and hardware latency. This is the latency purely from the latency caused by internet signals.
If you think about it it actually makes more sense in a asynchronous enviroment like roblox engine. You dont want to compensate for the lag that doesn’t bother the current system/script you are working at.
Also I know this thread is old but maybe people might find the explanation useful. Basically normally your ping is 0 in roblox studio because roblox just uses you as the server. When you run the game the roblox creates a local host (again using your machine) and creates artificial latency to simulate real world scenario.