BATTLEFIELD
VIETNAM weapons GUIDE
-
Everything you need about Battlefield Vietnam weaponry -
Final Edition 31 August 04
Written by LappyTHT
a note regarding the v1.1 patch and this faq
After spending last spring tweaking
and editing this FAQ to perfection,
I come back to school this summer (i.e. back to the free internet) to
find that those bastards at EA Games patched the game, and a substantial
amount of this FAQ was no longer accurate. I was also getting a good
number of emails from confused, albeit well-meaning BF:V beginners.
So here I am to straighten everything
out. Don't worry, I've retested
all the weapons that were effected by the patch (A patch that, honestly,
was very necessary.) I'll note where changes in weapon performance and
packages were made as a result of the patch both in the Table O' Contents
and in the body of the FAQ.
Second to Lastly, I am not going
to give you a full changelog of the
patch here, you can find that on almost any website that offers it.
However, it's these following changes that I'm gonna talk about in here
(As well as everything else)
-Lowered 44 Magnum rate of fire
to better sync with the animation.
-M60 removed from the LAW kit
and replaced with M14.
-M60 and RPD min/max bullet deviation increased when standing/moving.
-M60 and RPD max bullet deviation decreased slightly when prone.
-Rate of fire and velocity of M60/RPD adjusted.
-Player movement speeds on Heavy Assault kits reduced slightly.
And Lastly, try to remember that
I'm not looking at the code while I
test these things, everything you read is the opinion of a guy playing
the game, not a guy reading a bunch of numbers on the screen. So,
don't email me saying "Lappy you're wrong, because the Vietnamese tanks
take X amount of damage in the water against Y weapon, so you shouldn't
have to fire 4 rounds at it"....I did, it happens, I'm sure it'll
happen to you too. :) On with the FAQ!
[previous] [next]
Table of contents
Please read a quick note on this edition of my faq regarding the v1.1 patch here. Note that the "**" indicate areas of my FAQ affected by the v1.1 patch.
|