11 replies to this topic

[FaT4Li7y]

I am sorry if this has been asked several times by now, but I really couldn't find the info myself and I am not very familiar with networking and the like.
So basicly my router/modem has two kinds of pings when I play MW:O and I couldn't find out what causes the difference. Once I am online the latency is stable but it is hard to get the better of the two ping-types. One is approx. 35ms to EU servers and the other which I get everytime since a few days is 50ms. Doesn't seem like a lot of difference but it IS. With the 50 ping my hitreg is terrible to the point that I don't wanna play anymore and withe the 35ms ping hitreg is perfectly fine. So it is a big deal for me.
At this time I am trying to priorize the internet traffic my router handles in favor of MW:O to get back to the 35ms on EU servers. I am playing from AT if that helps.
So can anyone tell me the ports MW:O uses or where I can find said information.
Any other tip or suggestions regarding my different pings is also much appreciated.

[Torezu]

Your ping is ridiculously low, and hitreg doesn't break that fast. Something else may be going on, but a 15ms ping difference will absolutely not break hitreg.

[Durant Carlyle]

It is not humanly possible to tell the difference between a 35ms ping and a 50ms ping. That's fifteen thousandths of a second difference. The fastest human reaction time is roughly 100ms.

If we didn't have a ping display available, we wouldn't be able to tell the difference between a 50ms ping and a 150ms ping when playing MWO.

Edited by Durant Carlyle, 09 October 2015 - 10:16 AM.

[xWiredx]

Durant Carlyle, on 09 October 2015 - 10:14 AM, said:

It is not humanly possible to tell the difference between a 35ms ping and a 50ms ping. That's fifteen thousandths of a second difference. The fastest human reaction time is roughly 100ms.

If we didn't have a ping display available, we wouldn't be able to tell the difference between a 50ms ping and a 150ms ping when playing MWO.

I'm fairly certain that last part is incorrect. I can tell the difference pretty quickly between 35 and 95. Reaction time != perception time.

[Durant Carlyle]

Then you are unusually gifted.

Especially since visual perceptions and reactions to them are the slowest. Audio perceptions and reactions to them are much faster.

[Torezu]

Durant Carlyle, on 09 October 2015 - 10:14 AM, said:

It is not humanly possible to tell the difference between a 35ms ping and a 50ms ping. That's fifteen thousandths of a second difference. The fastest human reaction time is roughly 100ms.

If we didn't have a ping display available, we wouldn't be able to tell the difference between a 50ms ping and a 150ms ping when playing MWO.

I'm not sure where you're getting the "fastest human reaction time" thing. I can easily pick up on a 100ms difference in timing. 15ms would be...harder, but there are air force pilots that can actually see what plane is shown when it's flashed on a screen for 5 ms, let alone just recognize that something is present. So registering 15ms isn't that hard. Now, most monitors refresh at 60-75 Hz, which is a 13-17ms period between screen refreshes.

My point is that 15ms ping difference might be noticeable, but it will certainly not be hitreg- or performance-affecting.

[xWiredx]

Basically, this^

Something to add: ping issues and network-related latency are more noticeable if they are constantly and/or drastically changing, even if they are well within typical response times due to how much faster base perception is compared to reaction times. Consistent latency is much more manageable and less noticeable than variable latency.

[Vlad Striker]

You can perform well at ping <300.

[TheCaptainJZ]

Press f9 to get a constant ping counter in the top left and check if it is actually stable. There could be a networking issue but it's not ping. Could be traffic being optimized wrong for you and causing instabilities while ping traffic isn't optimized and is staying relatively stable for you. They are different types of traffic after all. Maybe this is causing jitter in mwo traffic only.

[FaT4Li7y]

So does anyone know the ports MW:O is using?
The info would really be much appreciated.

[Golrar]

That small a difference in ping is definitely not going to cause hitreg issues. However, the increase in ping may denote or allude to other network issues. What will definitely cause hitreg issues is packet loss. It could be the higher ping an indicator that your network is suffering from packet loss, or if on a wireless connection, signal degradation. Wireless signal degradation is usually as easy as checking your little bars in Windows. But if you are playing a game, you really should NOT be using a wireless connection. As for the packet loss:

http://www.techfleec...ter-connection/

Read that for help on tracking down the issue.

Another thing you can try if the packet loss is not coming from your local connection but somewhere in your route is to change your DNS servers. This can sometimes alter your route to the server to a better performing path. Some DNS servers, although highly popular, can go belly up, especially during peak hours due to traffic.

https://www.opennicp...s-in-windows-7/

[EgoSlayer]

Faktype, on 10 October 2015 - 06:30 AM, said:

So does anyone know the ports MW:O is using?
The info would really be much appreciated.

MechWarrior Online uses the following port:
TCP 45461
TCP 45464
UDP 21000 to 30000

But there is nothing you are going to be able to do on your router to change the ping. The time from your machine, to your router to the Internet is going to be 1 or 2ms. Everything else is outside of your control, it's the Internet itself. A difference that is alternating between two consistent values like that most likely is an alternate path chosen by your ISP or one of their trunk providers.


And frankly, as many have said - at either of those ping levels you've got nothing to complain about. It's barely game affecting, and by no means game breaking.