46 replies to this topic

[justcallme A S H]

mad kat, on 18 February 2019 - 02:12 PM, said:

Lol now you're just being condescending. 'Good players' will review it. I suppose your one of them in empyreal.

As a matter of fact I sent support a ticket about a month ago about broken hit reg. So maybe there is an issue with my connection despite having decent ping.

Yeah - I regularly review videos for players who think there are issues in the game.

More often than not, and I'm talking from experience, the case is they are wrong or its easily explained.

Just the reality of the situation. Anyway dude, stop typing, start playing and recording the issues. Come back with proof. I'll gladly take any statements back if you come with unequivocal proof. I am going to say that is however, unlikely.

It is more likely a your issue - not a weapon/game issue. Which I said in my first post.

Edited by justcallme A S H, 18 February 2019 - 02:27 PM.

[VonBruinwald]

mad kat, on 18 February 2019 - 02:12 PM, said:

Lol now you're just being condescending. 'Good players' will review it. I suppose your one of them in empyreal.

INB4 Jarls list!

[justcallme A S H]

Rustyhammer, on 18 February 2019 - 02:19 PM, said:

That's some recent evidence of questionable UAC5 hitreg with shells going through and hitting some targets behind the main target: https://youtu.be/JZP8duTaxdI
However I can't 100% rule out heatvision blurring, my ping or my aim.

Not hitreg - You got the hit. Plus a component destroyed as well.

So I'd say that's just HSR. You can see 2 shells actually go past the TBR and the other 2 did as well (due to HSR). Whatever target is directly behind it you hit and definately got hitreg on.

[Monkey Lover]

Problem with Solaris is the pings. I see 500ms+ pings all the time.

[mad kat]

Ok in summary hit reg/ HSR whatever you may call it is definitely broken and has been proven to by more than one player although it seems random in occurrence but some weapons seem more susceptible to it. Take 30 seconds googling mwo hit reg and see what you find.

Secondly if an UAC20 jams it takes far too long to un-jam for a typical Solaris engagement.

And thirdly the jam chance is either borked at jamming nearly every shot clearly not the 30% iirc. Granted that dice is rolled with every time the trigger is pulled so in theory it could jam 100% of the time not with reduced chance if a jam has just been cleared. And with the time it takes to clear a jam you've lost too much firepower in the process.

Which means as I said originally it works in qp as you have the ability to withdraw from the sticky situation and take cover while the weapon clears. It just takes too damn long to do so in Solaris.

Edited by mad kat, 18 February 2019 - 03:02 PM.

[VonBruinwald]

justcallme A S H, on 18 February 2019 - 02:26 PM, said:

Not hitreg - You got the hit. Plus a component destroyed as well.

So I'd say that's just HSR. You can see 2 shells actually go past the TBR and the other 2 did as well (due to HSR). Whatever target is directly behind it you hit and definately got hitreg on.

Doesn't look like HSR to me:

Spoiler

At this point the Timby starts moving left and doesn't clear the path of the bullets before the damage registers.

HSR works by applying the damage when you see the hit but the server registers a miss. The bullets don't appear to miss from our perspective.

Looks like that Timby has a case of Phantom 'Mech.

[Khobai]

UAC20 doesnt have hit reg issues

its just a bad weapon. like really bad.

UAC20 should be one of the deadliest weapons in MWO like it was in battletech, and its just not...

Edited by Khobai, 18 February 2019 - 03:39 PM.

[Dee Eight]

mad kat, on 17 February 2019 - 10:46 PM, said:

I usually don't have an issue with it. But last night it was a 15t waste.

The usual you can't aim argument is so patronising.

White knights for PGI always be patronizing.

[justcallme A S H]

VonBruinwald, on 18 February 2019 - 03:10 PM, said:

Doesn't look like HSR to me:

Spoiler

At this point the Timby starts moving left and doesn't clear the path of the bullets before the damage registers.

HSR works by applying the damage when you see the hit but the server registers a miss. The bullets don't appear to miss from our perspective.

Looks like that Timby has a case of Phantom 'Mech.

Possibly - not being HSR. Hard to say as it would depend on the ping of both players / who is seeing what.

The rounds hit a mech, the one directly behind. So no hitreg would mean it just disappears. Convergence aside the reticule was just over the nose of the TBR enough with heatvision. The point that two rounds go right past the nose would perhaps mean that heatvision slight plume outside the hitbox.

Either way it's not a hitreg - as it hits - something

[Rustyhammer]

justcallme A S H, on 18 February 2019 - 04:24 PM, said:

Possibly - not being HSR. Hard to say as it would depend on the ping of both players / who is seeing what.


The rounds hit a mech, the one directly behind. So no hitreg would mean it just disappears. Convergence aside the reticule was just over the nose of the TBR enough with heatvision. The point that two rounds go right past the nose would perhaps mean that heatvision slight plume outside the hitbox.


Either way it's not a hitreg - as it hits - something

How would you call shells going through the target dealing 0 damage ? The fact they hit something behind the main target is irrelevant, it was pure luck.

In my case I feel the game decided that shells trajectory went above or below timby's nose due to vertical movements at the time of shooting. Even my game client did not register the hit on Timby, only on some background target, so i think it was my aim

Velocity, convergence and trajectory of the ballistic weapons can be the reason why so many people have perception there are hitreg issues. Recording helps a lot to realise how much potato you are when you replay these "clear hits" and facepalm

[justcallme A S H]

Yeah but going through a target and hitting something else means it is not hitreg. As you hit, something. Even if it was a mountain.

Hitreg would mean that you hit the TBR but dealt 0 damage to it. Which didn't happen, for better or for worse, well debatable.

[panzer1b]

Ive personally seen MANY PPCs hit me straight in teh face and do 0 damage to my mech, but rapid fire weapons that fire bursts seem to be rather consistent if enemy/me aims well with them. I think there is always a small chance of fail hitreg but 90% of teh time its just someone thats either super laggy (which is understandable) or just bad aim that felt like a solid shot (ive had PPCs fly just above someone's face many times despite what feels like bad hitreg).

[mad kat]

I will second PPC hit reg being dubious I think the large projectile clips terrain or an innocent fly going about its business and there you have it. Killed a fly or maybe even a small bird that was in the wrong place at the wrong time as it flew between you and your target.

O.k seriously though I've had lots of PPC hits not register any damage. The paper doll will flash and the reticule turns red but no damage appears.

[B L O O D W I T C H]

justcallme A S H, on 18 February 2019 - 02:20 PM, said:

It is more likely a your issue - not a weapon/game issue. Which I said in my first post.

Lololol. Ash the hitreg police.
Do not complain or report before the Institute of ASH^TM hasn't revisited your complaint beforehand.

justcallme A S H, on 18 February 2019 - 02:20 PM, said:

Anyway dude, stop typing, start playing and recording the issues. Come back with proof. I'll gladly take any statements back if you come with unequivocal proof.

Dude, this is not the ASH show, you don't tell people to stop typing. Noone needs the ASH seal of approval to post here.

justcallme A S H, on 18 February 2019 - 01:31 PM, said:

Good players will review it.

Good players, as in you? So whoever states an issue is a bad player?

Jesus christ, ash. You might want to take a step back because your one foot away from the entitlement zone. It is fine to ask for video proof to keep a discussion going but the way you do it, actually demanding it reeks of a sense of entitlement.
I get that you're a good player, empyrial and all. That doesn't means however that someone has to prove themself to you.
Especially when it's about single flpd, especially in solaris. In 12 vs 12 games it's easy to overlook but in solaris it's painfully obvious.

I lost because my hitreg failed on me, often.
I won because my opponents hitreg failed on them, often.
I actually stopped midgame and had a good laugh chatting with my enemy because both our hitreg was hilariously bad.

It's happening, with or without the Institute of ASH^TM approval.

From my POV, 1 in 10 shots chokes on hitreg, which i think is kinda bad in a shooter game.

OP's claim is legit.
Single tab register as doubletap issue is also legit and has been proven. Although, it sucks when it happens but it's so rare that it is a very minor issue.

[R E X I OS]

Ultras jamming system is way over exaggerated in this game.

[PhoenixFire55]

mad kat, on 18 February 2019 - 10:54 PM, said:

Lots of pointless stuff

Instead of making like three dozen posts about nothing, how about recording one video that clearly displayes the issues?

But of course you won't. Because it'll display quite different issues, that'll make it perfectly clear where the actual problem is.

[mad kat]

PhoenixFire55, on 19 February 2019 - 04:18 AM, said:

Instead of making like three dozen posts about nothing, how about recording one video that clearly displayes the issues?

But of course you won't. Because it'll display quite different issues, that'll make it perfectly clear where the actual problem is.

O.k. I get the point about recording it, but i don't have recording software. While not in itself a problem as i could download one the very nature of random hit reg fails / anomalies and constant jamming would mean i would have to record every match i'm in. Identify when it happens and edit a video and upload it somewhere just to prove something.

As Toha heavy industries above points out the only reason i should do this is so that i can prove it to PGI in a ticket ( for a well circulated problem i might add) and incidentally for anyone else that is interested.

[PhoenixFire55]

mad kat, on 19 February 2019 - 04:36 AM, said:

O.k. I get the point about recording it, but i don't have recording software. While not in itself a problem as i could download one the very nature of random hit reg fails / anomalies and constant jamming would mean i would have to record every match i'm in. Identify when it happens and edit a video and upload it somewhere just to prove something.

Funny, since it clearly contradicts with your initial post about how you had 'a couple matches' and hit reg was 'off pretty much completely'. It takes literally 15 mins to set up the recording software. About five times less time than it took you to make two dozen posts in a single thread.

We all know that you won't deliver anything. But hey, feel free to surprise us.

[arcana75]

Here's a video of hitreg issues. No other mech, 1v1 in QP. Both mechs stationary. His shots hit me, my shots hit dead on but no hits register on the display. The ridiculous part is him taking damage only from the overheat.

https://youtu.be/66zWfbMG5xk?t=253

Edited by arcana75, 19 February 2019 - 05:25 AM.

[PhoenixFire55]

arcana75, on 19 February 2019 - 05:24 AM, said:

Here's a video of hitreg issues. No other mech, 1v1 in QP. Both mechs stationary. His shots hit me, my shots hit dead on but no hits register on the display. The ridiculous part is him taking damage only from the overheat.

https://youtu.be/66zWfbMG5xk?t=253

Thats a great example of a bug ... different bug.

It is clear to me that this is one of those 'stuck in terrain to become unhittable' bugs you see often enough too, especially so on Mining Collective when a mech jumps off from a building along the wall and gets stuck in it, becoming literally invincible to all but lock-on weapons, since its not actually where game shows it is. From what I can see on the video, at 4:14 Linebacker starts falling down and falls into the terrain, thus going into server coordinates limbo. You can clearly see that it 'stands in the air' at around 4:39. But apparently after it comes up from shutdown it is able to backpedal its way out of terrain on 4:42-4:43, as displayed by his instant teleportation from where it stood 'in the air' unto the top of the canyon wall.

It can be classified as hit-reg issue, but this is in fact an entirely separate issue. If I were you, I'd mail this link to PGI with a ticket, unless you've already done so.