47 replies to this topic

[Johnny Z]

Against 3 different mechs no damage registered at all in a match I was just in. I think the entire team wasn't doing damage.

Just a heads up.

[9thDeathscream]

Been running for about 1.5hrs. No problems in solo or group queue!

[Johnny Z]

Second match doing no damage again.

[Exilyth]

You should try and capture some vids.

[Johnny Z]

Third match doing damage.

Sometimes this can go on for more than 10 matches in a row at this time. All servers.

Exilyth, on 24 September 2017 - 02:07 AM, said:

You should try and capture some vids.

The match log will show no problem. I just don't feel like waiting for that to play out this time is all.

Edited by Johnny Z, 24 September 2017 - 03:37 AM.

[9thDeathscream]

Johnny Z, on 24 September 2017 - 02:12 AM, said:

Third match doing damage.

Sometimes this can go on for more than 10 matches in a row at this time. All servers.

just did 700+ in an Anh

[Antares102]

Can we please lock this nonsense thread especially without a video being provided?
What is next Johnny?
You report every match you lose because it must not happen?

Edited by Antares102, 24 September 2017 - 02:59 AM.

[Johnny Z]

Kharonn, on 24 September 2017 - 02:13 AM, said:

just did 700+ in an Anh

The Anni is awesome. Walks like a Godzilla movie.

[Appogee]

Videos would definitely help...

I have matches occasionally where there is a notable lack of damage registration. In those matches I expect - and this is based on the experience of 10,000 matches - that I've done about triple the damage that shows up on the end score screen. Ie, I feel like I've done 500+ damage but the end screen shows 150.

In an experiment I did, a team mate and I took identical S-SRM Kintaros into matches and fired exactly the same salvos at exactly the same targets. He consistently recorded 30% more damage than I did... with a weapon that mostly removes 'aiming' from the variables. (Yes, there will be differences based on who killed the component. And maybe the odd missile might hit the terrain. But that should mostly even out over the course of several matches.)

So, something was going on.

I have seen more comments about absent hitreg in the past few weeks than previously. It's hard to know for sure, other than those glaring obvious 'why the hell isn't the Mech in front of me dead yet?' moments which I hope to capture on video, Nvidia permitting.

(The night before last I put five 48-point alphas into the CT of a Mad Dog but it didn't even turn his armor red. Sadly, my GEForce Experience software had crapped out during that match. So I reinstalled GEForce Experience and am waiting to catch the evidence next time and share it with PGI.)

Edited by Appogee, 24 September 2017 - 03:13 AM.

[Magnus Santini]

That sounds like a lag problem. There is no damage because you are shooting at a target that was there in the past, you are seeing the past, but the server knows he is not there now. It can be such a time warp that you could be dead and the game over, but you are still moving around shooting frozen targets!

[Bombast]

Maybe the enemy is just better than you.

[Willard Phule]

Not a glitch, it's a new "feature" of the HSR since the last patch. Probably to "balance" damage between the T1s against the T5s they're not supposed to be dropping against.

[Zergling]

Willard Phule, on 24 September 2017 - 04:25 AM, said:

Not a glitch, it's a new "feature" of the HSR since the last patch. Probably to "balance" damage between the T1s against the T5s they're not supposed to be dropping against.

Proof needed.

[Willard Phule]

Zergling, on 24 September 2017 - 04:30 AM, said:

Proof needed.

PGI coded it without outside help. There's your proof.

[Ghogiel]

Willard Phule, on 24 September 2017 - 05:20 AM, said:

PGI coded it without outside help. There's your proof.

So what you are saying is it doesn't work... so that there is effectively no hidden mechanic that makes T1 players do less dmg than underhive spuds? ok gotcha.

Edited by Ghogiel, 24 September 2017 - 05:35 AM.

[Asym]

Even if a dozen people show any of you proof of: "pass throughs"; impossible or non-existant head shot hit boxes; non hit registration caused by any of the frame rate issues; hit mathematics calculation errors (cause by weapons errors that are compounding); or, that the code PGI is using is flawed beyond repair, many of you would find fault and doubt.....

I've seen it. Entire 12 person teams have experienced it and lost matches because of what "it" is and there have been several good articles of game expereinces of weapons simply not registering data....

It takes the fun out of the game and fun, is at an all time low for me and, there's almost no one left...........

[Mystere]

Willard Phule, on 24 September 2017 - 04:25 AM, said:

Not a glitch, it's a new "feature" of the HSR since the last patch. Probably to "balance" damage between the T1s against the T5s they're not supposed to be dropping against.

[Bombast]

Asym, on 24 September 2017 - 06:06 AM, said:

Even if a dozen people show any of you proof of: "pass throughs"; impossible or non-existant head shot hit boxes; non hit registration caused by any of the frame rate issues; hit mathematics calculation errors (cause by weapons errors that are compounding); or, that the code PGI is using is flawed beyond repair, many of you would find fault and doubt.....

I've seen it. Entire 12 person teams have experienced it and lost matches because of what "it" is and there have been several good articles of game expereinces of weapons simply not registering data....

It takes the fun out of the game and fun, is at an all time low for me and, there's almost no one left...........

So entire matches, with 24 people in them, frequently experience no damage matches, and yet none of them can be bothered to show any proof.

We're running into the Bigfoot/Ghost problem here - As access to cellphone cameras (Or in the case of MWO, from-manufacturer screencap software) becomes more and more mainstream, it becomes increasingly harder to believe someone when they say 'Trust me.' Particularly when its the same exact people, making the same exact claims, the exact same way, over and over and over again, and using the same exact excuse every time someone asks for proof - It's obvious, why should I bother?

Well, because it's not obvious, most of us aren't seeing this, and we aren't going to take your word for it.

[Willard Phule]

Ghogiel, on 24 September 2017 - 05:35 AM, said:

So what you are saying is it doesn't work... so that there is effectively no hidden mechanic that makes T1 players do less dmg than underhive spuds? ok gotcha.

No, I'm being sarcastic. HSR always has issues following a patch or update. Back before the skill tree, the trick was to figure out what was hitting and what wasn't, then alter your builds accordingly. A little hard with all the SP/GXP expendatures on the tree now.

[oldradagast]

This thread is nonsense.

I've played probably way too many MWO games over the years, and while there have been a few memorable instances in a few matches of damage not registering obviously - mostly because of feathering jumpjets - it is NOT some wide-spread problem that "makes it so nobody can deal damage," nor is it some magical issue that was suddenly "added to the game as part of some super-secret conspiracy that only random people on the internet have discovered." Good lord, people - is THIS what passes for reasoning these days?

Yes, some damage here and there is often lost because of network or HSR issues. It's not huge, it's rarely obvious, and it works as much for you as against you since sometimes somebody shoots you but little damage registers.

Yes, damage against disconnected mechs is spotty. We know that, and it doesn't impact matches because the target isn't participating.

And, yes, now and then - probably less often than once a year - I've had a surreal match where the server loses it and mechs freeze in place or teleport around now and then, and damage doesn't register. But those matches are unwinnable because everyone is being affected and nobody can really aim or move properly anymore. If it happens, disconnect and send a support ticket.