15 replies to this topic

[Jimmy Page]

The fact this game is built on a house of cards concerns me. PGI seems only interested in making new mechs for money when many of the same issues (bugs) are still here over 1.5 years later, namely HIT DETECTION. The fact you can fire on a rear torso and it registers in the front is bad. The fact that lights (Spiders) are almost immune to ballistics is very bad. The list goes on and on. They spend 4 months on 3PV that nobody uses. They proclaim a big patch that only has window glass updates. (LOL) Can this really be considered a valid FPS game with hit detection so borked?? Thinking man's shooter? Hardly. I love big stompy robots, but patience grows very thin on game breaking issues that never get resolved.

[Kaldor]

Jimmy Page, on 02 February 2014 - 03:09 AM, said:

The fact this game is built on a house of cards concerns me. PGI seems only interested in making new mechs for money when many of the same issues (bugs) are still here over 1.5 years later, namely HIT DETECTION. The fact you can fire on a rear torso and it registers in the front is bad. The fact that lights (Spiders) are almost immune to ballistics is very bad. The list goes on and on. They spend 4 months on 3PV that nobody uses. They proclaim a big patch that only has window glass updates. (LOL) Can this really be considered a valid FPS game with hit detection so borked?? Thinking man's shooter? Hardly. I love big stompy robots, but patience grows very thin on game breaking issues that never get resolved.

Youre not the only one...

[Nicholas Carlyle]

The hardest part about this issue is it doesn't seem to effect everyone. And it may also depend on which PGI server cluster you land on when you drop.

So you'll have people swearing up and down there are no problems.

And then you'll have people saying they shot 5 alpha's into a prone Atlas and did no damage.

In the end though, even if it's split 50/50, and half the players have Hit Reg issues and half don't, that should be enough that PGI takes it very seriously...

Which I'm not sure they do, because their communication is still dismal, and as far as I can tell they are focused on adding a bunch of stuff to counter/help LRM's that don't fix the core problem's with LRM's.

[Scryed]

Jimmy Page, on 02 February 2014 - 03:09 AM, said:

The fact this game is built on a house of cards concerns me. PGI seems only interested in making new mechs for money when many of the same issues (bugs) are still here over 1.5 years later, namely HIT DETECTION. The fact you can fire on a rear torso and it registers in the front is bad. The fact that lights (Spiders) are almost immune to ballistics is very bad. The list goes on and on. They spend 4 months on 3PV that nobody uses. They proclaim a big patch that only has window glass updates. (LOL) Can this really be considered a valid FPS game with hit detection so borked?? Thinking man's shooter? Hardly. I love big stompy robots, but patience grows very thin on game breaking issues that never get resolved.

This game is not a FPS, but that is how they are treating it. In their words the game was supposed to be a simulator but they keep adding these FPS mechanics that don't work, al they need to do is take all that was used for Mechwarrior 3 and apply it, but then they would have to admit they were wrong about everything.

[PhoenixFire55]

Nicholas Carlyle, on 02 February 2014 - 06:49 AM, said:

The hardest part about this issue is it doesn't seem to effect everyone.

People who don't know how to target enemy mechs and that mechs have 'different parts' are haveing absolutely no problems with hit detection. People who buy a mech that hasn't even been released for 500$ are also haveing absolutely no problems with hit detection. They are golden, they don't care.

[Alcom Isst]

PhoenixFire55, on 03 February 2014 - 04:22 AM, said:

People who don't know how to target enemy mechs and that mechs have 'different parts' are having absolutely no problems with hit detection. People who buy a mech that hasn't even been released for 500$ are also having absolutely no problems with hit detection. They are golden, they don't care.

The disgruntlement is strong in this one.

Edit: The lowest tiers still have hit detection issues, they may notice it as much among their reduced accuracy and overall reduced awareness.

Edited by Alcom Isst, 03 February 2014 - 07:58 AM.

[PhoenixFire55]

Alcom Isst, on 03 February 2014 - 06:23 AM, said:

The disgruntlement is strong in this one.

Even the highest competitive tiered MWO players have hit detection issues.

And where did I say otherwise?

[Joseph Mallan]

I do remember the "old days" when I could fire a 60+ point alpha at a stationary Raven 4 times and see no result, It has not happened in quite some time for me. That does not mean others are not still seeing this happen. It IS a serious problem if players are being "cheated" out of kills cause of internet physics.

[NRP]

PhoenixFire55, on 03 February 2014 - 04:22 AM, said:

People who buy a mech that hasn't even been released for 500$ are also haveing absolutely no problems with hit detection. They are golden, they don't care.

Umm, yes we are (mainly with PPCs). And yes we do.

PGI has acknowledged the issues with hit detection and HSR, but last I heard they are having trouble isolating and reproducing the issue. Since I havent heard an update, I assume they are still working in it.

[Mycrus]

Jimmy Page, on 02 February 2014 - 03:09 AM, said:

The fact this game is built on a house of cards concerns me. PGI seems only interested in making new mechs for money when many of the same issues (bugs) are still here over 1.5 years later, namely HIT DETECTION. The fact you can fire on a rear torso and it registers in the front is bad. The fact that lights (Spiders) are almost immune to ballistics is very bad. The list goes on and on. They spend 4 months on 3PV that nobody uses. They proclaim a big patch that only has window glass updates. (LOL) Can this really be considered a valid FPS game with hit detection so borked?? Thinking man's shooter? Hardly. I love big stompy robots, but patience grows very thin on game breaking issues that never get resolved.

they can't monetize hit detection...

[PhoenixFire55]

NRP, on 03 February 2014 - 07:09 AM, said:

Umm, yes we are (mainly with PPCs). And yes we do.

PGI has acknowledged the issues with hit detection and HSR, but last I heard they are having trouble isolating and reproducing the issue. Since I havent heard an update, I assume they are still working in it.

Yeah, same way they are working on collisions etc.

[Joseph Mallan]

PhoenixFire55, on 03 February 2014 - 07:25 AM, said:

Yeah, same way they are working on collisions etc.

Slowly?

[Alcom Isst]

PhoenixFire55, on 03 February 2014 - 06:47 AM, said:

And where did I say otherwise?

I misread your double negation there. My bad.

Edited by Alcom Isst, 03 February 2014 - 07:54 AM.

[Mechteric]

UI2.0 is (was) holding up many a things we need also, like CW, lobbies and whatnot. Its also coming tomorrow, so there's no reason now they can't move on to other things as well.

[Joseph Mallan]

CapperDeluxe, on 03 February 2014 - 08:13 AM, said:

UI2.0 is (was) holding up many a things we need also, like CW, lobbies and whatnot. Its also coming tomorrow, so there's no reason now they can't move on to other things as well.

That is unless PGI decides to listen to the Silent majority again.

[MeiSooHaityu]

Hit detection will never be perfect, so this might have to be something that people will have to try and accept.

The game uses server side verification heavily to make sure cheating and hacking is difficult if not impossible (the server makes sure the client isn't trying to report false info that breaks the rules of the game).

This takes some time and that combined with connection latency and higher pings means many clients will be seeing old out of date data (hence the..I hit him, why isn't he damaged) situations. The server has to double check the position and speed of mechs, weapons fire, hit locations, etc...

If you have a high ping, or even low ping with packet loss, you will be seeing an enemy mech where it was a quarter of a second ago, and not really where it is according to the server.

This server side check is going to cause hit detection wonkiness to some extent. They can tweak their net code to try and improve this, but they can only do so much, plus they can't control a client's connection quality.

They could get a rid of the heavy server side policing, but then we would have Crysis 1 multiplayer issues like mechs that are invincible, cruising around at 180kph, with infinite ammo and 10 A/C20s, etc...

Just a nature of the beast.