14 replies to this topic

[Sader325]

So I've fired my ERPPC enough to know that theres a bit of an issue here.

So here is the question: What does the server consider to be the position of the Mech I'm firing at? The MECHS body? or the Targeting box reticle?

Because I'm getting a little tired of watching a ERPPC shot go through my target.

[Dirkdaring]

Could be lag. I play on fios with a low ping and have not seen a shot go through a mech since beta.

[Johnny Z]

Try the training grounds. The best way to check out your mechs and a few others.

[Felio]

If I understand your question:

The "box reticle" is just to highlight the target for you. You have to actually strike the mech itself.

Actually every mech has invisible hitboxes, but they approximate the shape of the mech. It's not a big rectangular box. Just aim for the robot.

[N0MAD]

Dirkdaring, on 10 May 2015 - 02:49 PM, said:

Could be lag. I play on fios with a low ping and have not seen a shot go through a mech since beta.

I thought HSR was meant to negate lag effect.
Yes i know some weapons need to be led, but thats nothing to do with lag, right? and since HSR is in there should be no lag shooting issues. You with your low ping and me with my Aussie ping should have the same result if we shoot at the same spot .

Johnny Z, on 10 May 2015 - 03:39 PM, said:

Try the training grounds. The best way to check out your mechs and a few others.

Training grounds is really useless when trying to work out why things happen ingame, as TG runs local (your computer) and therefore no lag/network issues, every hit/shot not affected by the internet..

Edited by N0MAD, 10 May 2015 - 03:59 PM.

[Sader325]

Felio, on 10 May 2015 - 03:58 PM, said:

If I understand your question:

The "box reticle" is just to highlight the target for you. You have to actually strike the mech itself.

Actually every mech has invisible hitboxes, but they approximate the shape of the mech. It's not a big rectangular box. Just aim for the robot.

There are times where the Reticle is not where the mech is.

[Felio]

Sader325, on 10 May 2015 - 04:03 PM, said:

There are times where the Reticle is not where the mech is.

It might help clear up any confusion if we use the same language. The targeting reticle is the crosshair in the center of your screen. There are two reticules: the tiny circle for where your arms are aiming and the + for where your torso is aiming.

The red box that surrounds your target is... well, it's a red box. Part of the HUD (heads-up display).

[Sader325]

Felio, on 10 May 2015 - 04:06 PM, said:

It might help clear up any confusion if we use the same language. The targeting reticle is the crosshair in the center of your screen. There are two reticules: the tiny circle for where your arms are aiming and the + for where your torso is aiming.

The red box that surrounds your target is... well, it's a red box. Part of the HUD (heads-up display).

How about you read my first post where I clearly said "The Targeting Box Reticle".

[Tarogato]

There is no such thing as a "targeting box reticle"

There is a reticle (this is another name for your crosshairs), then there is the targeting box (the red box that surround a mech that you've targeted).

Anyways, back on topic: you could be completely missing your PPCs shots - very often I think I should have hit my mark, when in reality the PPC projectile whizzed between the mech's legs or between its torso and its arm. This is compounded by the fact that the visual particle/graphic used to represent a PPC is bigger than the actual physical projectile hitbox used for the hit detection. It may look like part of the blue "whoosh" actually hit the mech, when in fact the projectile did miss by a narrow margin.

Depending on the environment, you could also be hitting invisible terrain geometry. There are some places on some maps where the terrain is buggy and counts as a physical obstruction even though you can see through it. It gets worse at longer distances because your computer is asked to render so much information, so it has to simplify some polygons and visible geometry may start to differ from physical geometry.

Edited by Tarogato, 10 May 2015 - 04:41 PM.

[AEgg]

Tarogato, on 10 May 2015 - 04:36 PM, said:

There is no such thing as a "targeting box reticle"

There is a reticle (this is another name for your crosshairs), then there is the targeting box (the red box that surround a mech that you've targeted).

Anyways, back on topic: you could be completely missing your PPCs shots - very often I think I should have hit my mark, when in reality the PPC projectile whizzed between the mech's legs or between its torso and its arm. This is compounded by the fact that the visual particle/graphic used to represent a PPC is bigger than the actual physical projectile hitbox used for the hit detection. It may look like part of the blue "whoosh" actually hit the mech, when in fact the projectile did miss by a narrow margin.

Depending on the environment, you could also be hitting invisible terrain geometry. There are some places on some maps where the terrain is buggy and counts as a physical obstruction even though you can see through it. It gets worse at longer distances because your computer is asked to render so much information, so it has to simplify some polygons and visible geometry may start to differ from physical geometry.

I wonder if the visual aspect is used to calculate collisions with geometry, though. Seems to me that PPC shots hit invisible edges of world geometry far more often than any other weapon does.

[Tarogato]

AEgg, on 10 May 2015 - 05:09 PM, said:

I wonder if the visual aspect is used to calculate collisions with geometry, though. Seems to me that PPC shots hit invisible edges of world geometry far more often than any other weapon does.

Feel free to test it in the training grounds. Mount a PPC and some lasers in the same place and see if the PPC hits stuff where the laser goes through. I doubt that will be the case, but it's worth a test, I haven't tried it myself.

[Troutmonkey]

N0MAD, on 10 May 2015 - 03:58 PM, said:

I thought HSR was meant to negate lag effect.
since HSR is in there should be no lag shooting issues. You with your low ping and me with my Aussie ping should have the same result if we shoot at the same

Should and do are different things.
Lag will always affect high ping players at least a bit, as HSR isn't perfect in any game, and certainly not when it was PGI who wrote it.

[LordNothing]

i cant hit a pixel at 1200 meters in less than a second. but what i can do is lead fast targets. ppc is probibly one of the hardest weapons to do this with though. gauss is kind of tricky to lead with because of the charging mechanic you not only have to fire where your target is gonna be, but you got to do it and time it with the charge cycle. though the the projectile speed kind of makes up for it. ppcs are kind of tricky because of their being really slow and being really visible and therefore really easy to dodge.

i usually just aim for the center at range, i will only try to pick off parts at moderate ranges. id rather score a hit that miss trying to shoot a leg.

Edited by LordNothing, 10 May 2015 - 08:00 PM.

[Alistair Winter]

Felio, on 10 May 2015 - 03:58 PM, said:

Just aim for the robot.

This thread actually ended here.

Sader325, on 10 May 2015 - 04:08 PM, said:

How about you read my first post where I clearly said "The Targeting Box Reticle".

Relax, take a deep breath. These people are here to help you. Don't be rude.

[grendeldog]

PPCs seem to go through mechs' legs or between an arm and a torso a lot more than other projectiles. My thought is that it may be calculated as a point by hit registration instead of as a reasonably-sized sphere, and so when it is rendered as a sphere but hit calculations use a point object the visual effect and the actual thing in the engine aren't a perfect match.

Edited by grendeldog, 10 May 2015 - 09:02 PM.