Is there a way to monitor packet loss while playing??
- Thread starter Arjin
- Start date
Why would you want to monitor packet loss while playing? It wouldn't serve any purpose. Do a ping test to yahoo for 100 times - that'll show you packet loss. Edit: If there is any
Second edit: Do this while playing.. Open CMD -> ping -n 1000 www.yahoo.com
Second edit: Do this while playing.. Open CMD -> ping -n 1000 www.yahoo.com
Last edited:
Becuase if i we can determine if significant packet loss is occurring it may help solve the stuttering issues. I don't care about Yahoo, I care about my connection the Elite's servers.
It won't. It's nothing to do with the network nor your CPU/GPU. It's the software. Packet loss won't cause stuttering like you're experiencing - trust me it happens to me to. If you want you can trace route to FDs servers or continually ping the server (if it even responds to ICMP requests). If there was packet loss on the servers end, well there would be a bigger problem at hand. If the packet loss is on your end, you can determine that by performing a variety of tests not involving Frontier's servers (or just call your ISP)
if you have java installed you can use pingtest.net to test for packet loss too.
if youre using a cable modem, be aware that there could be issues outside that could cause a lot of packet loss. i used Dayman's method a couple days ago but used 200
discovered that i may have a bad port my cable modem/router.
if youre using a cable modem, be aware that there could be issues outside that could cause a lot of packet loss. i used Dayman's method a couple days ago but used 200
discovered that i may have a bad port my cable modem/router.Yea I understand all that, just wanted to check while the game is in use to see if any links, outside my home network could be congested. I do have a crap router but for the most part i don't get packet loss, or bandwidth issues. Just trying to think of everything that would/could cause stuttering..
Tanks for the replies!
Tanks for the replies!
There are all sorts of ways of going about this. Net limiter might be the easiest to get to grips with.
Heya Arjin, I can give some suggestions to you later....
Well yup, with UDP there's no receipt check, the packets are shot out and left to their own devices. My understanding was that he was wanting to test his network for dropped packets, maybe I read that completely wrong.
As far as I know, there's no direct way to measure packet loss at the moment in Elite.
Even if you could measure it, the figure would be useless by itself. It wouldn't show you where the loss was occurring - at your end, at the server's end, or en route. Only if you could also see the average figure for all other users would it mean anything. For example, on Teamspeak there's a facility to display a smoothed version of your packet loss. I know that if it's 5% or more I will likely lose contact with my FSX server. But if (as a sys-op) I monitor other people's packet loss as well, I can tell if it's just me or if everyone is experiencing it, and I'll know whether the problem is at my end or at the server's end.
If you think you are experiencing packet loss, ensure you are on a hard wire connection to the internet and not a wireless link. If you can't avoid using wireless, change your router channel to one that is relatively unused in your vicinity.
Packet loss can be devastating to multiplayer gaming. The most severe effects of packet loss are server disconnects. However, only some kinds of stutters are due to packet loss, and these include positional lag/snap-back and some object rezzing delays. By contrast, stuttering of cut scenes such as hyperspace jumps is nothing to do with packet loss; it's due to poor game design, poor machine performance, or both.
I would gladly trade half my 125 Mb/s bandwidth for better guaranteed packet loss, but my carrier (Comcast) is not interested is promoting such abstruse concepts with the public!
Even if you could measure it, the figure would be useless by itself. It wouldn't show you where the loss was occurring - at your end, at the server's end, or en route. Only if you could also see the average figure for all other users would it mean anything. For example, on Teamspeak there's a facility to display a smoothed version of your packet loss. I know that if it's 5% or more I will likely lose contact with my FSX server. But if (as a sys-op) I monitor other people's packet loss as well, I can tell if it's just me or if everyone is experiencing it, and I'll know whether the problem is at my end or at the server's end.
If you think you are experiencing packet loss, ensure you are on a hard wire connection to the internet and not a wireless link. If you can't avoid using wireless, change your router channel to one that is relatively unused in your vicinity.
Packet loss can be devastating to multiplayer gaming. The most severe effects of packet loss are server disconnects. However, only some kinds of stutters are due to packet loss, and these include positional lag/snap-back and some object rezzing delays. By contrast, stuttering of cut scenes such as hyperspace jumps is nothing to do with packet loss; it's due to poor game design, poor machine performance, or both.
I would gladly trade half my 125 Mb/s bandwidth for better guaranteed packet loss, but my carrier (Comcast) is not interested is promoting such abstruse concepts with the public!
I run a couple dos boxes with pings going to my home router, my ISP's router and a good local site such as news.bbc.co.uk. The command is
ping -t news.bbc.co.uk
if the latency goes up then there are network issues.
ping -t news.bbc.co.uk
if the latency goes up then there are network issues.
I suppose it would be good to ping the ED servers too, anyone know the hostname the client connects to?
Trouble is, if everybody starts pinging the servers. then the latency will go up as the bandwidth used will increase!!!
However, the IP address is shown in the bottom left of the menu screen before you Connect to open /group/solo.
Last edited:
Should be able to find it by running netstat once the game is running.
control freakery but with no control i suspect he wants to use it as an excuse relex when he messes up at a later date
Last edited:
Don't worry about that ICMP packets are tiny.
Don't bother with WireShark or any other network analytical tools. Experts use them for specific fault finding and the average person will be overwhelmed with even a few seconds of collected data.
http://www.internettrafficreport.com/ tracks key routers globally to give you a real time representation of Internet health.
As for maximizing your connection to the Internet, you can use this:
http://www.speedguide.net/downloads.php
It can change MTU and various other networking parameters to tweak your connection. BE WARNED. Make sure you note what you have before changing it. You can screw things up royally by making the wrong mods.
More here:
https://ttcshelbyville.wordpress.co...mal-mtu-setting-to-improve-your-connectivity/
Make sure you can roll changes back.
PS. Don't game over a WiFi connection. Use a hard wired Ethernet plug.
http://www.internettrafficreport.com/ tracks key routers globally to give you a real time representation of Internet health.
As for maximizing your connection to the Internet, you can use this:
http://www.speedguide.net/downloads.php
It can change MTU and various other networking parameters to tweak your connection. BE WARNED. Make sure you note what you have before changing it. You can screw things up royally by making the wrong mods.
More here:
https://ttcshelbyville.wordpress.co...mal-mtu-setting-to-improve-your-connectivity/
Make sure you can roll changes back.
PS. Don't game over a WiFi connection. Use a hard wired Ethernet plug.
Last edited:
You could do all that but, honestly, a simple ping gives you all the info you need. I am a network engineer and would use wireshark only for serious issues. The websites don't give you the full picture either.