Project Reality Forums

Hi!

Where can i find information about the damage from weapons.

I mean exact Values,for example: Weapon_damage 1.2 ; Is there a documentation ? Or do i have to search in the weapon.configs?

5.56 mm will wound you, 7.62 mm will blast your guts out. AT weapons will shred you apart, and so will the jet's gattling guns.

There.

Yeah, pretty much no need for weapon stats for PR but I would like to see rate of fire, recoil and all the other useless information on the weapons.
Here are the vBF2 weapon stats though, these stats show the rate of fire, recoil, etc.

cant find the weapon damage info

i think general rule of is:

556 = 3 shots to kill

762 = 2 shots to kill

Sniper = 1 shot to kill

headshot from any weapon = kill

Depends on body armour and the actual round.

7.62x51 (in the G3) can cause a really fast bleed out on an unarmoured target with only 1 hit, while the 7.62x39 (AK-47) wont. But they both kill in 2 hits.

I'm pretty sure the sniper still takes 2 torso shots to kill.

BetterDeadThanRed wrote:I'm pretty sure the sniper still takes 2 torso shots to kill.

You're confusing marksmen and sniper methinks.

'[R-PUB wrote:GeZe']You're confusing marksmen and sniper methinks.

x2

Occasionally it takes 2 sniper rounds against armored targets - aim for the thigh - it yields 100% kill rate and is easier to hit than the head.

'[R-DEV wrote:Katarn']Occasionally it takes 2 sniper rounds against armored targets - aim for the thigh - it yields 100% kill rate and is easier to hit than the head.

Noted.

'[R-DEV wrote:Katarn']Occasionally it takes 2 sniper rounds against armored targets - aim for the thigh - it yields 100% kill rate and is easier to hit than the head.

Really? Suppose theres that big fat artery in the thigh so makes sense. I always go for the heart area... Will try this out next time i manage to get a sniper kit.

youm0nt wrote:Yeah, pretty much no need for weapon stats for PR but I would like to see rate of fire, recoil and all the other useless information on the weapons.
Here are the vBF2 weapon stats though, these stats show the rate of fire, recoil, etc.

Yes this is what i am looking for.

i've hit a guy with several in the torso, just to watch him sprint off, apparently not dazed. i guess it could have been a ping issue, but if you see the dust (armor) then blood, you assume the *******'s hurt. same for a knife hit in the torso, where it may take 2 in the chest or side. no matter what, i just bead the torso on habit, head if he's static. i'd actually rather knock the guy down as opposed to head shot for a kill where possible, only to have his camera pan to your cover.

also, if your range is decent, take the hit and don't move for a period. your cover and draw distance can still prevent him from pulling your location off the death cam. the worst is killing a guy and having him spawn in on one of the gazillion spawn cars parked behind, under and above you. i sware to god, sometimes you'll hit one guy and insurgents repel from the heavens

Mr.Nicklebe wrote:Really? Suppose theres that big fat artery in the thigh so makes sense. I always go for the heart area... Will try this out next time i manage to get a sniper kit.

Chest area has body armor, that's why. Except if the target is spec ops.


@dysin

Well, this is BF2. You have to compensate for 2 things.

One is hit box lag; the hit boxes actually lag behind the player. The second is lag in general, that means that you have to shot ahead. So it's complicated. The blood is client side, so you may see it, but in reality not hit the player, as the hit boxes lag behind.

'[R-PUB wrote:GeZe']Chest area has body armor, that's why. Except if the target is spec ops.


@dysin

Well, this is BF2. You have to compensate for 2 things.

One is hit box lag; the hit boxes actually lag behind the player. The second is lag in general, that means that you have to shot ahead. So it's complicated. The blood is client side, so you may see it, but in reality not hit the player, as the hit boxes lag behind.

i figured as much, but wasn't sure if it was actually client side