Exact firing values are intentionally withheld until current-build in-game testing is complete.
QUICK ANSWER
Group rows by powder charge, increase distance consistently, record in-game elevation and flight time, and publish only cells that have passed repeatable tests.
Operator briefing
A firing table is useful when the mechanical calculator is unavailable or when you need a fast cross-check. The final production table must be generated from a tested model and labelled with the exact game build.
Use the procedure below as a decision sequence, not as a substitute for the live mission order. Random coordinates, balance values, and mod compatibility can change; stable facts and version-sensitive evidence are labelled separately.
Field procedure
- 01
Create separate blocks for each charge count so operators cannot mix solutions.
- 02
Sample regular distance intervals plus both ends of every usable band.
- 03
Record the mechanical calculator reading and observed impact for each row.
- 04
Flag interpolated rows differently from directly tested rows.
- 05
Archive the table when a patch changes ballistics; never silently mix builds.
Checks before you commit
- The visible table on this first release is a verification plan, not invented ballistics.
- Faster access is valuable only when confidence and version are visible.
- Use the experimental calculator to collect discrepancies, then update the test set.
When the live game conflicts with this page, keep the live observation, game build, and source date. That evidence becomes the next revision instead of being silently forced into an old answer.
Sources and evidence
Sources are included for verification, not copied as site content. Official pages establish product facts; community and video sources document tested workflows.