Only the default (TGN Light) theme for now. Dark them is also coming back soon. Then CSN. Then Wrestlin' Nation. A lot of WIP stuff right now. There are a couple of things still not working either. Sorry.
i did test and i still am testing both guns in identical circumstances - kaboom kark. Range - well i used to play ak101 non stop with medic, so i pretty much mastered that gun at one point for range. Ping - same server, even though ping changes, again i played MANY rounds of kark. target type - theres only 2....
Im pretty damn sure ive tested this a lot, im not saying one is more accurate or not, I just seem to hit more with the assault. Ill do some more testing.
When it comes to proving things, especially in Battlefield 2:
Is there some fixed way the math is worked out on determining the overall Deviation the Weapon gets. So prone + moving + zoom = total of all the Devs ? Or is it more complicated. I am working on a small Tech Guide for Snipers and the Deviation thing will be mentioned. I want to portray it as best I can.
I'm not 100% sure of this, since actual code handling firing is pretty well hidden, some hardcore modder could probably give you better answer, but here goes ;
total deviation for shot = (base deviation of weapon + modifiers) * multipliers
it could be basedev*multipliers + modifiers as well, but when testing with 4 crouch multiplier and 20 jump modifier, crouch+jump some of the shots fell *off* the screen, which shouldn't happen with "just" total deviation of 20-something. If somebody knows the correct formula, go ahead and correct me.
All the values can be found in .tweak files in objects_server.zip
base deviation is unique for each weapon, minDev value.
multipliers include stance multipliers, for either standing, crouch, proning and zoom modifier devModStand, devModCrouch, devModLie, devModZoom.
modifiers are added deviation for different actions, setFireDev, setTurnDev, setSpeedDev, setMiscDev. There are 3 to 4 numbers, first one telling what's the max amount of deviation to add from the action, middle ones are how much deviation each action adds, and last one how much of this added deviation is dissipated after each server frame. Servers usually run at 30-33 fps, dictated by bf2_fps command (I think, I'm not server admin).
I don't know what "action" is for moving, if it's "1m. travelled" or just "moved for 1 server frame" or whatever, so if you're making a guide, just give "with max movement modifier" and "with no movement modifier" values, which would represent running and stationary values. This also means, that you don't lose your movement modifier *right* after you stop, but for example in case of M24, it takes 3 server frames, in case of M16, 10 server frames.
FireDev is amount of deviation to add for each shot, first number is the max amount, second the deviation added/shot, last is the dissipation / second. This is pretty irrelevant for sniping (you need to fire ~400 rpm with svd to start building up deviation)
TurnDev is 0 for all the weapons, it represents amount of deviation you get from moving your crosshairs, think they put it there "just in case". Some gun might even have more than 0, I haven't looked through them all.
SpeedDev is deviation to add for moving, first number is the max, second is deviation to add per move forward/back, third is per strafing move, last one is how much you lose it per server frame.
MiscDev is deviation to add for jumping. It was obviously more relevant when you still could jump and shoot, but it still takes roughly 30 server frames for most guns to "settle" once you finish jumping - that should be enough to touch the ground though.
Once you've got all the numbers, for example, when moving around standing, zoomed with svd, you'd get the following deviation
(5 + 3 + 0 + 0)*2*0.01 = 0,16
5 is mindev, 3 is speeddev, 2 is standing modifier, 0.01 is zoom modifier,
prone and zoomed, (5 + 0 + 0 + 0)*0.8*0.01 = 0,04
finally, the deviation *should* be in degrees (as opposed to say, radians) from your original aimpoint. If your deviation is 0,5 , it means that your shot deviates from 0 to 0,5 degrees off your intended target to some random direction. If you dump all possible shots for 1 instance of shooting, they draw a cone to your target, height of the cone being your distance to target.
If you're familiar with trigonometry, you should be able to calculate hit percentages for a given target at certain range for each gun and stance.
the real deal is when you look at the code and see the stats for itself. if the stats are the same then their the same. crosshiar doesnt mean anything.
the real deal is when you look at the code and see the stats for itself. if the stats are the same then their the same. crosshiar doesnt mean anything.
i know your a modder and i know you know what your talking about, but why in the hell would they make unique crosshairs for each gun, when in fact they are theoritically the same??? why do i kick more *** with the gp-30? just me?
somtimes the iron sights on the guns for instance are modeld diffrently . ever seen the m16a2\203 and the 16a2 regular. sights are slighlty differnt. thats my explination. but why would ea do that well comon, they ddnt even finish the m82a1. so its probably just a thing they did and ddnt take the time to work it out. atleast us modders can fix it. sorta.
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Comment