67 replies to this topic

[UXB]

The game's current condition is disgraceful. PGI needs to take a long hard look at their processes 'cause the game is broken right now. Badly broken.

[Calamus]

The other day I had a Highlander try to hug it out with me. All I could see was his CT when I fired the AC/20 from my Misery. It destroyed the last of his armour... on his rear left torso. Which would have been great if I were the Jenner behind him. His entire front torso (all three of em) didn't even blink.

[Coryphee]

Got lot of probs here too :
- lot of rubber-banding
- Lot of bad hit detection (Alpha a non-moving mecha and he don't take damage, or very low // Beeing shot in my back and it make my Front armor lost).

[Skorrn]

You guys broke the game...I just rage quit a game where I smacked a non-moving jenner 4 times with a full alpha consisting of dual lbx 10s and triple srm 6s, he went slightly yellow. These were SOLID hits, full lbx groupings on CT and a good spread of SRMs on top of it, barely any registered damage. Looks like I'm going back to my light mechs...

Edited by Skorrn, 26 July 2013 - 12:33 PM.

[Britane]

agree, Hit Detection has relapsed in the last patch.

bet some old code got put back in by accident.

[DeaconW]

Sigh...so tired of invincible spiders.

[Nauht]

This is getting beyond a joke. A shooter game where your shots don't register.

I've been supportive of PGI but the current state of hit detection is far too frustrating for me to actually play the game.

This is a fundamental flaw. Forget heat, forget hero mechs, forget fluff, forget weapon balance, forget movement.
This is as basic as you can get for a shooter game. ALL relevant resources should be on it.

[Wieland]

Its getting worse and worse.
I have hits that i see hit but dont register.
Hits that register but dont seem to do damage.
Shots that go through the enemy mech.

[ImagineDwagons]

HSR is broken again that's the fact and I noticed that I have the hardest time to hit fast targets whith low ping. The same light mech with high ping is less problematic to hit.

[StormDll]

+1 on the general "somethings broken with hit detection"

Edited by StormDll, 27 July 2013 - 07:12 AM.

[JayKay17]

I was on leave the last week, so I had the chance to play a lot.
And hit detection was somewhat a problem the whole week, but not so harsh as today.
I hit a shutdown Quickdraw dead center in the rear with two salvos of 2 LL and 4 ML, after this the QKD woke up from shutdown and its rear armor (not the internal structure) were red. Even if my aim would have been bad, all rear torsos should not have any armor left after two salvos and probably the mech should have been dead at least all internal structure from the torso should have bee severely damaged. Frustrating is the in the same time I got cored front center torso from another mech, this one doesn't seem to have a problem with hit detection.

Since it was not so bad the last days as today, could it be that it has something to do with the server load and HSR ?
Could it be that the load on the servers calculating the hits via HSR is so high that the routine fails and puts out an "non hit" ?
Another Argument would be, that it seems with fewer people in the game (several dead already) the non-detection issue gets a bit better.

[Name140704]

Bump. Really HORRIBLE for weeks now. It seems like Gauss Rifles are the worst for me.

[FREDtheDEAD]

The number of light mechs has increased recently - probably as people are catching on that some enemies have trouble hitting them. It's very much a combination of shooter and target that determines how wonky damage will be. Some targets I seem have no issues with.

[mack sabbath]

My gauss now registers hits even point blank, at 33%. I have sent in multiple support tickets.

They are "working on it" and have been going on their second year. They either can't fix it, or or preoccupied with new money grabs to give it their full attention. If I hadn't stupidly forked over $80 for PP, I'd be uninstalled by now.

As it is, I'm done playing till October and not one more dime goes into this broken mess until it's fixed.


Funny, all my weapons hit just fine in the testing grounds, but in an actual match where it MATTERS?

Trust me, they can't / won't fix this or it wouldn't take over a year. In a podcast, Sean Lang's AC 20 failed to register 5-6 times and he asked Garth, who was on his team when this would be fixed....he joked "NEVER!"

Methinks he wasn't joking....enjoy all that Phoenix money PGI, a lot of us won't be shelling out any more.

Edited by Die Primate Die, 28 July 2013 - 08:53 AM.

[Jasen]

Die Primate Die, on 28 July 2013 - 08:46 AM, said:

My gauss now registers hits even point blank, at 33%. I have sent in multiple support tickets.

They are "working on it" and have been going on their second year. They either can't fix it, or or preoccupied with new money grabs to give it their full attention. If I hadn't stupidly forked over $80 for PP, I'd be uninstalled by now.

As it is, I'm done playing till October and not one more dime goes into this broken mess until it's fixed.


Funny, all my weapons hit just fine in the testing grounds, but in an actual match where it MATTERS?

Trust me, they can't / won't fix this or it wouldn't take over a year. In a podcast, Sean Lang's AC 20 failed to register 5-6 times and he asked Garth, who was on his team when this would be fixed....he joked "NEVER!"

Methinks he wasn't joking....enjoy all that Phoenix money PGI, a lot of us won't be shelling out any more.

In fairness a ton of people were telling you not to buy PP... your own fault really.

[DeathofSelf]

Decided to play for a bit the other night, had to stop after 2 matches cause it was so bad. I hit a raven probably 5 or 6 times with an AC20 I think 2 of the registered.... Keep up the good work PGI! I'm sure it will be figured out by launch!

[Roland]

Information regarding this issue, for any developers who are interested:

There appears to be some linkage in HSR between the shooter's movement and the HSR's prediction of where the shot is going.

I was recently in a game where I was repeatedly shooting at a legged K2, which was really only barely moving, while I too was moving in the same direction as he.

On my screen, my shots (which were leading him by just a slight ammount) were impacting directly on his CT. However, no damage was registering.

On his end, after the game when I asked him, my shots appeared to be missing in front of him (that is, in the direction of his movement).

I suspect that this missing was due to the HSR system taking into account my own movement vector, in addition to his, when trying to calculate whether I was hitting or not. This would explain a lot of missed hit detection issues in close range fighting, as both shooter and target are changing their vectors rapidly.

[mack sabbath]

Point blank with a Highlander's chest filling my entire view screen.

3 Gauss hits, all red reticle hits, NO damage, I get alph'd down as a result...not even worth playing now, since my Misery relies on a ballistic weapon for 1/3 of it's firepower.

[Ronstar]

I just played a game on forest coloney, shot a spider in the chest that was standing still tagging me and pumped 2ppcs then another 2 ppcs into his chest. He brushed it off like nothing happend. Then I died to LRMS.

PGI fix your game! HSR is clearly not working!

Edited by Ronstar, 28 July 2013 - 10:59 AM.

[DeaconW]

Either the hit detection is really borked or some kind of armor h**k is at play. I just had a match where i put 7-8 56 pt damage shots into a moving HBK at close range...after he lost an arm and a side, his CT could not be critted. Armor never went away. Something fishy or broken there.