52 replies to this topic

[Pataine]

Host state needs to either be fixed or taken out of the game. So tired of being 2-3 steps into cover and bam a leg is blown off or I am CT'ed in a light. Either have the game fixed so the round checks to see where I am when it comes in to do damage not where I was or take {Scrap} state rewind out. It makes it so low ping player IE 60 and under are always hit by high players no matter what. if I am behind cover the inc rounds need to IMPACT on the terrain not hit me. Don't wanna here that there is no difference between 60 and 120 cause there is as that's double my ping. Or well that's what they see on their screen. I cannot damage players with 150+ unless I use streaks and pulse weapons. Don't tell its cause I am crappy shot either. We had on the forum for 6 months," I cannot hit lights with a low ping so fix it." How about you fix this issue as with it there is no reason to run lights until this major problem is fixed. You have made it so 130-225 ping players win 80%+ of the matches vs players under 100 as we cannot damage them.

[Lorcan Lladd]

Before anyone else says so - you have to provide evidence if you want other players or perhaps even PGI staff members to take your complaints seriously. Even if there is a problem, you might be the only one experiencing it.

[xhrit]

Pataine, on 07 January 2014 - 12:37 PM, said:

I cannot damage players with 150+ unless I use streaks and pulse weapons. Don't tell its cause I am crappy shot either. We had on the forum for 6 months," I cannot hit lights with a low ping so fix it." How about you fix this issue as with it there is no reason to run lights until this major problem is fixed.

I am on a FIOS line. My ping is in the 40-80 range. My KDR is 3.5 in my RVN 3L, and my win / loss ratio is 1.5.

I have not experienced any issues like what you describe. I hate to say "its cause you are a crappy shot"... but...

Edited by xhrit, 12 January 2014 - 09:53 PM.

[Suko]

All I will say is two nights back I had terrible ping (~250 when I'm usually at ~100) and I was doing GREAT. Like, high DMG each game and I wasn't dying nearly as quickly! It could be any number of things that caused this, but the thought did cross my mind; "Is my high ping making it harder for the enemy to core me or hit desired spots as easily?"

[ProtoformX]

State rewind has problems with ping jitter. Ping bouncing up and down will cause all kinds of strange **** to happen.

Edited by ProtoformX, 07 January 2014 - 03:23 PM.

[Alistair Winter]

As a light mech pilot with 150-200 ping on a good night, let me tell you it works both ways.

[Foxfire]

This has been a problem since the inception of the system. Granted, it isn't one you will run into every fight

I think the tolerance for the system needs to be adjusted but the system is needed unless we want to return to the days of lag shield, which is way worse. To the point where a good light pilot could go into a group of heavies and assaults, solo, and take them down(I think my personal best was a 1v4 with my Jenner against an awesome, dragon, cat, and a severely damaged Atlas).

Edited by Foxfire, 11 January 2014 - 05:22 AM.

[Kaspirikay]

290 ping {Dezgra} get on mah level

[A banana in the tailpipe]

Alcohol is the reason low ping players do poorly. The more we drink the lower our ping seems.

Edited by lockwoodx, 11 January 2014 - 05:43 AM.

[Mawai]

Well the current HSR is way way better than without it.

Before HSR you had to lead your opponents mech to have a chance of hitting even at close range. This also meant that your weapons would never converge on the target since you were never aiming at them. It was far worse than the current situation.

There may be issues with HSR ... having a hit register after you reach cover is just par for the course ... it does NOT mean that they hit you through cover ... it means that their shot hit you BEFORE you reached cover. The server tracked your location and the shot location and figured out where you were when the opponent fired ... and you got hit. Deal with it .. you did not reach cover in time and the only delay was in your client letting you know. The server is authoritative ... not your client ... so you just get informed that you were hit within the last 500ms or so and the damage is assigned.

Anyway, they could probably use more work on HSR but it is probably the only way to get 24 people playing relatively fairly on a battlefield with a wide range of ping values.

[A banana in the tailpipe]

Mawai, on 11 January 2014 - 05:47 AM, said:

There may be issues with HSR ... having a hit register after you reach cover is just par for the course ... it does NOT mean that they hit you through cover ... it means that their shot hit you BEFORE you reached cover. The server tracked your location and the shot location and figured out where you were when the opponent fired ... and you got hit.

I've been in this exact situation with 36-40 ping multiple times where due to low latency I should have been fine with the cover I placed myself behind. Low ping doesn't always save you from wonky server issues.

Edited by lockwoodx, 11 January 2014 - 05:50 AM.

[Craig Steele]

Best Ping I ever had is 270, usually 290. I don't win more than I lose (its even btw).

I don't think Ping is the factor.

[R Razor]

The OP is just whining............I was in the same game as he was yesterday, I have the same (or lower ping) than he does, he got killed and immediately starting complaining about the Australians and Europeans on my team that had pings ranging from 150 - 250 and claiming they shouldn't play because they killed him and he couldn't hit them.

I played for 6 months from Afghanistan, and aside from the known issues hitting spiders reliably I never experienced the heart wrenching, ego destroying, soul crushing loss he experienced so I'm not sure where his beef really lies.

[A banana in the tailpipe]

Before people get crazy bent out of shape about latency I'd like to point out that it IS currently an issue being looked into.

http://mwomercs.com/...ost__p__3062894

Matthew Craig, on 10 January 2014 - 09:33 AM, said:

Just wanted to note that we are continuing to investigate the causes behind the increased latency and sudden server slowdowns.

Edited by lockwoodx, 11 January 2014 - 05:59 AM.

[Khobai]

My ping is typically 50, and I win 2/3rds of my matches while pugging.

[Zerberus]

R Razor, on 11 January 2014 - 05:53 AM, said:

The OP is just whining............I was in the same game as he was yesterday, I have the same (or lower ping) than he does, he got killed and immediately starting complaining about the Australians and Europeans on my team that had pings ranging from 150 - 250 and claiming they shouldn't play because they killed him and he couldn't hit them.

I played for 6 months from Afghanistan, and aside from the known issues hitting spiders reliably I never experienced the heart wrenching, ego destroying, soul crushing loss he experienced so I'm not sure where his beef really lies.

I can tell him exactly what his problem is, but I guarantee he won`t like it.

[Abivard]

If you do not have this problem, then you are not a low ping player playing vs high ping players.

When the spread among pings is greater than around 200 ms, the hi ping player gains more and more of an advantage, PGI is well aware of this. The game will adjust in favor of the higher ping, this means many things, from lock on time to hit and miss.

This seems to be far beyond PGI's ability to ever fix and so it isn't going change.

[Thorqemada]

It is common that you get hit in cover by other Mechs as their Client is lagging behind and shows you still in a LOS.
As only their Client and the Server matter for HSR you get hit.
But better that as the "Game of Luck" without HSR.

Edited by Thorqemada, 11 January 2014 - 09:50 AM.

[YueFei]

HSR makes it so you can't reactively defensive maneuver/twist against a high-ping opponent. By the time you see your opponent pop out from cover, he has already popped out and fired a shot sometime in the past.

As an example, if your opponent has a ping of 250 and you have a ping of 100:
000 ms - opponent clears cover and gains LOS on you. He has a ping of 250 so the server hasn't received yet. You see nothing.
125 ms - server has got the information and begins sending to other players.
175 ms - you see the opponent appear.
200 ms - The opponent has had this time to see you and line up his shot, and fires.
325 ms - server receives the shooter's firing command. Rewinds server state to point in time at 200 ms.
375 ms - 200 ms after you saw him appear (human reflexes), you begin to react and twist / dive for cover.
425 ms - Server receives your movement / twist command. Too late, though, since HSR determined that you were sitting around doing nothing at time-index 200 ms, and the shot at 200 ms hits you square in the CT.

From the point of view of the player with high ping, it looks like the people he shoots at have very slow reflexes.

The only way to cope with this is to always assume someone may be lining up a shot on you and try to move erratically. HSR simply doesn't let you wait until you see his face. By the time you see his face on your screen, he's already fired his shot sometime in the past, which HSR will determine hit you in the face.

[Villz]

Alistair Winter, on 07 January 2014 - 03:30 PM, said:

As a light mech pilot with 150-200 ping on a good night, let me tell you it works both ways.

This OP is easily the most Rtarded thing i'v read on these forums in a LONGGGGG time. and thats saying something.