Oh I see your point now. I was thinking of using the barrel funtion to generate the initial damage then plug the initial damage into a falloff curve, not having them both as one.

引用自 Blueshy：

引用自 1 share = 1 prayer：

While the polynomials do fit, the behavior I think we're looking for is a large initial increase and slow approach to a horizontal asymptote. You can easily standardize the exponent style to just two variables one max damage and one "growth" constant.

Is it though? I think you've confused one of the graphs into the end result. This graph is barrel length vs muzzle velocity and it gives us the damage at 1m (initial damage), but does not provide the damage falloff curve. I think the damage falloff curve would actually be exponential decay based off the ballistic coefficient for the bullet from what I've read so far. I think that if we paired these two equations together we might be getting closer to a final equation.

lazy graph i threw together to show the exponential form
https://docs.google.com/spreadsheets/d/1h03NM75ovKm8ZolRNByNy05Vmjn3Qk9_gx8ABxoPCy0/edit?usp=sharing
i dont think we need NS because it considers a decay term which i dont really see happpening in the bbti data

While the polynomials do fit, the behavior I think we're looking for is a large initial increase and slow approach to a horizontal asymptote. You can easily standardize the exponent style to just two variables one max damage and one "growth" constant.

Interestingly, the relation between muzzle velocity and barrel length also follows an exponential equation something like 1-exp(-x)

I used values from http://ballisticsbytheinch.com/ and if we use this model the glock will have about 80% the damage of the mp5a4. Thoughts?

引用自 Blueshy：

http://www.jbmballistics.com/ballistics/calculators/calculators.shtml

https://www.youtube.com/watch?v=nsBByTiKfyY

We could use the maximum distance and recoil formulae to automate those values. The others seem irrelevant for hitscan weapons. Does power factor correlate to damage?

"Alpha" release of Python 3 script:
https://drive.google.com/open?id=0B-mv4PuuSfrjU0pHckMyUnJzQ3c
I'm done staring at code for today so feel free to look through and test.

引用自 Mad Monkey：

I think excel can get the job done for the most part. Import the data and use spaces for delimiter. It stacks everything pretty accordingly. Define the ranges, create a bunch of macros to execute scripts and voila.

Maybe I'm dumb, but I can't get excel to frame the data the way I want without having to do a lot of manual work.

Let's say I want to visualise all the damage falloff curves on one chart, in a format that google docs will accept (so that I can share the link with yall). This means that you can only have one X column and multiple Y columns. If your damage falloff curves all have different X values you can have a GREAT time manually pasting that shit into google docs. Right now I can write a script to get this arrangement and re-run it every time there is an update without having to find the changes.

Oh yeah the suppression sway is pretty bad. I think the simulated suppression is only meant for games with high TTK where they need to give some deterrent to bumrushing. Sernix is a bit more bullet spongey but I think the TTK is still low enough that we don't really need this feature.

-I think the frame, barrel, and stock options should have more subtle effects. Kinda ridiculous how fast you can put away the heavier guns if you select all the light options, for example.

-I like the intermediate ammo type as a balance between HP and AP. I'm not sure what's going on with the new damage values being slightly different between ammo types but it doesn't feel "off"

-The .357 shotshell is fun to use. Can we get a shotshell for the m203?