15 replies to this topic

[Delas Ting Usee]

Hit registration, rubber banding, teleporting...it's all back and lends itself to a frustrating time.
There's no point playing unit it's FIXED.
Really, who wants to spend time getting frustrated, I ask you?
Please let us know when this 'fix' will occur.
Thanks.

[Psyker]

Since the last hotfix my ping is 50-70 ms higher than it usually is (80 was pretty much where it sat before, now it's 130-150). I'm in Western US with a 100mb connection.

[DaZur]

I've fluctuated between 25 and 40 since day one closed-beta...

[Ghogiel]

It's unplayable for me as well since friday. Just constant teleporting every 3-5secs.

[OuttaAmmo NoWai]

I've had a silky-smooth 30-something ping since closed beta. No lag issues, hitreg problems, nothing.

Yeah, I'm spoiled.

[Wiley Coyote]

No issues with my connection. Regular sub 20 ping on a 25MB connection.

[Kiiyor]

My ping is better, but my hitreg, especially with ballistics is abysmal.

[Sorbic]

Psyker, on 25 October 2014 - 08:37 PM, said:

Since the last hotfix my ping is 50-70 ms higher than it usually is (80 was pretty much where it sat before, now it's 130-150). I'm in Western US with a 100mb connection.

That's odd, I'm in Western WA (Lacey) as well and my ping still sits around 80 on a 50mb connection. Who's your provider?

[Psyker]

Sorbic, on 25 October 2014 - 10:42 PM, said:

That's odd, I'm in Western WA (Lacey) as well and my ping still sits around 80 on a 50mb connection. Who's your provider?

A fiber provider here in Utah in the Utopia network called Xmission. I ran a trace and didn't look good:


C:\WINDOWS\system32>tracert mwomercs.com

Tracing route to mwomercs.com [192.99.109.192]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms [192.168.1.1]
2 1 ms 1 ms 1 ms lo0.mar1.slc.xmission.net [166.70.255.53]
3 2 ms 1 ms 1 ms br2.core.xmission.net [166.70.1.3]
4 1 ms 1 ms 1 ms xe-1-1-0.cr2.slc1.us.nlayer.net [69.22.153.153]

5 65 ms 15 ms 15 ms 89.149.187.246
6 16 ms 16 ms 16 ms ix-12-0.tcore1.LVW-Los-Angeles.as6453.net [66.11
0.59.101]
7 24 ms 22 ms 25 ms if-2-2.tcore2.LVW-Los-Angeles.as6453.net [66.110
.59.2]
8 28 ms 25 ms 25 ms if-3-2.tcore1.SQN-San-Jose.as6453.net [63.243.20
5.13]
9 27 ms 38 ms 42 ms if-1-2.tcore2.SQN-San-Jose.as6453.net [63.243.20
5.2]
10 * 102 ms * snj-2-6k.ca.us [178.32.135.166]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * 102 ms 104 ms bhs-g2-6k.qc.ca [198.27.73.7]
15 * * 103 ms 198.27.73.233
16 102 ms 102 ms 102 ms mwomercs.com [192.99.109.192]

Trace complete.

[B0oN]

My ping went from 95-115 in CB to up about 160ms with various patches until now from CET .
Hitregitration was flawless in CB (albeit hitboxes were linear speed-dependant and dis-located from visual model AKA LAGSHOOTING) and went to randomn-mode since introduction of HSR-sillyness .

As a pointer : I used to use laser-heavy lights and was doing not bad, introducton of HSR made playing these mechs impossible :
-stand behind shutdown Atlas in 42 meters distance, firing at his crit red-glowing rear CT twice with 6 Medium lasers (=30 damage) only to see ... NOTHING happend .

-Have a duel with another laser Jenner, permanently shoot his face while circling (yes, I am keeping that reticule on targt for the whole duration, dont worry^^) and just see him taking absolutely neglibile and superficial damage (as if I was just bumping into him Oo)

-Run past someboy with a glowing red CT,firing a 30dmg alpha at it, keeping the reticule on center spot smoothly as you could only hope for and see ... horray NO EFFIN DAMAGE FOR THE 7millionth time

Stopped counting all the deaths induced by jittery, laggy, overloaded, ******, shoddy or non-existing hitregistration OR the missed kills because I seemingly shot at a whole different universe instead of somthing quite easily trackable IN FRONT OF ME .

So, once again, my question to PGI goes out :

WHEN WILL YOU FIX OR EVEN BETTER RELIEVE US FROM THIS MESS CALLED HSR ?
You´ve been kitty-jumping round this unpleasant thematic for a very long time, dont´cha think ?

[Alakan]

Wow. You guys don't know how good you have it.

My ping has jumped between roughly 500 to 6000 over the past few days.

And no. I did not mistakenly add extra zeros to those numbers.

Edited by Alakan, 26 October 2014 - 03:10 PM.

[Troutmonkey]

[xeromynd]

DaZur, on 25 October 2014 - 08:56 PM, said:

I've fluctuated between 25 and 40 since day one closed-beta...

Same here, connecting from NY, USA. Always been a-ok. And i believe their servers are on the West Coast, no?

[Durant Carlyle]

DaZur, on 25 October 2014 - 08:56 PM, said:

I've fluctuated between 25 and 40 since day one closed-beta...

This, most of the time. During peak hours on weekends, it jumps to 80-90 ms. I don't notice a difference in game play either way -- no lagging at all.

That's on Comcast 50Mb cable and I'm in the midwestern U.S.

[Grendel408]

Delas Ting Usee, on 25 October 2014 - 07:49 PM, said:

Hit registration, rubber banding, teleporting...it's all back and lends itself to a frustrating time.
There's no point playing unit it's FIXED.
Really, who wants to spend time getting frustrated, I ask you?
Please let us know when this 'fix' will occur.
Thanks.

Have you (or anyone else with this issue) filed a support ticket? How much troubleshooting can be done from this post lacking in detail... like, where do you live in the world and what type of connection are you running with your ISP? Those little tidbits of information help players help troubleshoot issues... and the Devs will need that info too.

File a Support Ticket...

[Herzog]

Hitreg issues might explain it; I noticed it immediately after patch. Had plenty of hits in-range... final damage was 20-30 points. Happened several matches in a row. Will have to check my ping next time but no rubberbanding; just wasn't registering hits.