Project Reality Forums

WNxKenwayy wrote:Ahhhhh But you can knife the tank, 1 hit kill I swear. Just have to hit it in the super sekret spot.

...don`t talk about the secret spot!

'[BF2 wrote:Bonsai;473868'] ...don`t talk about the secret spot!

t'is what she said

'[R-DEV wrote:Jaymz;473869']t'is what she said

I would fix that, but I quite like my current unbanned status.

Ah, how I am reminded of the love between the two r-dev's

Katarn & Jaymz

Or how the paparazzi like to refer to them "Jatarn & Kaymz" PR's odd couple.

'[R-DEV wrote:Jaymz;473869']t'is what she said

LOL

one thing I overuse way too much

mammikoura wrote:Just wondering since yesterday I realized that the Us sniper rifle (m40?) doesn't kill people from 1 shot. Now I'm guessing this is because of the range I was shooting from. Must have been something like 300m, or what ever is the view distance on daquing (sp?) oilfields.

And yes, I'm 99% sure I hit the targets since they were almost always stationary. Headshots seemed to kill them just fine, and 2 shots to the center mass took care of them. But weren't snipers supposed to be 1 shot 1 kill even to the center mass against guys who have body armor? And IRC I've never had this problem before. Though then again I don't snipe that often.

Even managed to shoot a squad mate once from that range, they were moving to the flag and I accidentially shot one of them. The team damage message came etc and I just said sorry and he was like "no problem, I'll survive" and he just used a field dressing and he was back in action.

So, how much does the range affect the damage? And is the effect the same with all weapons or does it depend on the weapon used?

M40a3

ObjectTemplate.minDamage 0.4
ObjectTemplate.damage 62
ObjectTemplate.DistToStartLoseDamage 600
ObjectTemplate.DistToMinDamage 1000

MinDamage and damage values are modifiers of an overall damage dealt equation. The calculation takes into account the mindamage, damage, distance, angle and the 'material' that it's hitting (another damage modifier).

So taking in your example of 300m and a dead on shot, there should be no damage lost over distance because the damage fall off only begins at 600m. So, now the calculation is depending on the material modifier, damage, and angle.

Here is a little chart that applies to the above mentioned weapon vs 'human materials' that is valid from 1-599m distance:

(Chart shows how many shots to kill. Angle numbers are in degrees)

Angle dead-on 30 45 60 90
Head 1 1 1 1 0
Body 1 1 2 2 0
Armored 2 2 2 3 0
(body)
Limbs 2 2 2 3 0

Now I'm sure some of you may argue how it's possible to shoot someone seemingly dead-on center mass but still need more than 1 shot to kill (example non-armored soldier) just remember that even if it looks that way, the soldier models are not perfectly flat. So at distance, it looks like you are shooting a 2-d model in the side, however, think about how round your rib cage is on the side of your body.

Note: As mentioned earlier, the ObjectTemplate.damage 62 does not mean that it will do 62 points of damage. Using the information above, a dead-on headshot from 1-600m will do 930 points of damage. Soldiers have 100 HP.

NOTE2: Damage only drops between the 600-1000m range. The damage will be the same at ranges closer than 600m. The damage drops from 600-1000m, where the damage will be at it's lowest point at 1000m. Damage at 1000m and beyond is the same.

1-600m
930 pts of damage

700m
790 pts of damage

800m
651 pts of damage

900m
512 pts of damage

1000m and beyond
372 pts of damage

WNxKenwayy wrote:Ahhhhh But you can knife the tank, 1 hit kill I swear. Just have to hit it in the super sekret spot.

You mean the Big red Button?
http://www.youtube.com/watch?v=C7hHKN7wWO0[/youtube]

thanks paladin-x. That explains a lot.
Guess it's time to activate only-aim-for-head mode.

A hit is not always a hit. On your screen you can see blood from the hit but in reality that person was never hit due to lag.

nicoliani wrote:A hit is not always a hit. On your screen you can see blood from the hit but in reality that person was never hit due to lag.

but as I said in the original post most of the targets were not moving. So lag won't cause a miss.

El_Vikingo wrote:... or "it's a game".

lolpwnt

mammikoura wrote:but as I said in the original post most of the targets were not moving. So lag won't cause a miss.

Not a miss. The hit just doesn't register.

KP wrote:Not a miss. The hit just doesn't register.

hits not registering is because the hit box is not where it seems to be because of lag. While an object (a player in this case) is not moving, hitboxes are also not moving. So the hitbox won't move anywhere between the 100ms (or so) which it takes for the info of my shot to reach the server, therefore the shot will hit the hitbox, and it will register as a hit.

Or at least I think that is how it goes.