-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Firearm Magazine Size Audit #70784
Comments
Also relevant: #70715 One thing I would like to ask of you is: if possible, provide dimensions (and, if available, online sources) for the audit data. Some of the magazines I'd audited for my own mod took hours to source online. I can only imagine that much of it is rounded or imprecise; which, still better than the regular N × 250 ml, may require re-auditing in the future, should better data become available. To have all this effort run through without leaving a crumb of data for the future devs (and modders like myself) to rely on seems like a waste. |
You're completely correct about that, would leaving it as comments in the JSON work alright? |
Comments in JSON should work fine. Alternatively, should you wish for a cleaner JSON, you can also leave all the sources and dimensions in the body of the PR. When I need to figure out what's the thing supposed to be in the base game (e.g. heavy load bearing vest), I also go through Git blame and find the PR that added it. |
There is pros and cons of both methods: despite i didn't put sources in #70715, i regret it a bit, and think i need to actually add them - they aren't that bulky, when styled with our linter |
Okay, so what I've decided on is to leave commenting within the JSON indicating the magazine has been audited, and what method was used (IRL Measurements, ImageJ, Comparison). Within the PR will be detailed notes of how the calculations were done. That way, anyone checking blame just has to check the line with the comment to find the information. (Not that most of these files have many changes anyways, but this should future-proof) |
Wonderful. Is there any chance that, after you're done actually auditing all the stuff, you can add the same info for the .22 LR mags? |
The .22lr stuff was actually from the few years old PR so I wasn't keeping track of any sourcing at that time. From what I remember the 10/22 stuff was personally dunked, and I think most of the rest was ImageJ. I can go through and revisit it once I've hit some of the bigger culprits. I do remember the American-180 being the biggest pain in the rear. |
@Hyperseeker |
You can take anything you want. (If you check #70715, you will find a screen capture of my written approval from the community Discord server.) That said, odds are that everything related to magazine volumes has been ported already. If you find anything, though, do as you please! |
By 0.H, those will likely make it into the base game already; see CleverRaven/Cataclysm-DDA#70784
Just wanted to check in on the progress of this. I'm looking to continue working on Armory, which relies on these measurements (among others) to correctly model the pockets. My hope is that by seeing this effort through before the 0.H release, the measurements will then be in the base game, and I wouldn't have to re-create them on my (mod) end. (This isn't a guarantee, of course, but I remain hopeful for now.) Is there anything I can do to help speed this up? Research, image references? |
The biggest hit to productivity is the sheer amount of magazines in the .223/9mm/.308 categories. If you want to take over 9mm, at my current pace I can likely get through .223 and .308 by February 11th. Resources are typically not as hard to find as the other categories, but the sheer number of them still slows me down tremendously. There's also weirdness where magazines are using the "copy_from" function when they really, really shouldn't and this slows me down too. |
If you open a draft PR for what calibers are left to audit, I can contribute my research to the comments. I won't author a PR or a commit myself, but I'm perfectly eager to donate my time to this effort. |
I'll tag you when I open up something. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. Please do not bump or comment on this issue unless you are actively working on it. Stale issues, and stale issues that are closed are still considered. |
The bot reminded me: @ANickelN, I think you might have missed .450 Bushmaster mags. I did some quick maths, and I think those mags should be about 25% smaller, or thereabouts. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. Please do not bump or comment on this issue unless you are actively working on it. Stale issues, and stale issues that are closed are still considered. |
Is your feature request related to a problem? Please describe.
A few years ago, when pockets and object length were introduced there was an effort to get items and pockets up to par. While there was a lot of initial enthusiasm, it is a lot of work and a lot of people (including me) burned out trying to chug through pages and pages of measurements.
While the size of firearms themselves are in a pretty good state due to their large impact on the game, their magazines have unfortunately been left in the dust. The magazines of smaller firearms are in many cases treated as the same or similar bulk and weight of much larger firearms, negating a distinct advantage of opting for a smaller caliber (the ability to carry more magazines in a smaller space).
Solution you would like.
This issue will be used for keeping track of the magazine audits that have been completed.
I'm doing it this way instead of making everything a single PR as I previously attempted, because quite frankly if I burn out part of the way through I want at least some of the work to make it to the player base instead of languishing in Github hell.
There are two ways I've been doing this so far.
All of the previous work I've done in this regard still holds up, so there will be one or multiple pull requests to quickly merge the work I've already done.
For transparency, the methods I've used to ensure accuracy are here from greatest to least:
IRL Measurements -> ImageJ -> Comparison
For any future work, corrections should probably only be done with a triumphing measure of accuracy, unless there is an obvious error with a previous measurement. In other words, an audit done through ImageJ should be corrected with IRL measurement, not through comparison.
Describe alternatives you have considered.
No response
Additional context
Relevant PRs include my previous attempt #60038, #37374 (seems to have mainly focused on firearms, which are in an okay place right now) and information from @Hyperseeker added with #70715.
If anyone else is interested in doing this, there are relevant instructions in #37374 for the usage of ImageJ for this project.
This is also a good page: https://serc.carleton.edu/eyesinthesky2/week2/get_to_know_imagej.html
The text was updated successfully, but these errors were encountered: