Set up and verify a ballistic profile

Start from the active profile. Open Ballistic profile and read the current projectile, muzzle velocity, drag model and coefficient, zero, distance and angle units, and engine-readiness state before editing. Name one reproducible configuration. Use a name that distinguishes the rifle, ammunition or lot, barrel or upper, suppressor or brake, and intended use. Create a separate profile when a change can alter velocity, zero, or drag behavior. Confirm projectile and drag model together. Enter the projectile identity and its ballistic coefficient using the matching G1 or G7 drag model. A coefficient has meaning only with the model under which it was published or measured. Enter the geometry, velocity, and zero actually in use. Use measured sight geometry when the profile requires it, a trusted muzzle velocity, and the confirmed zero distance for this configuration. Check distance and angle units against the source material before comparing results. Save the durable profile. Use Save local profile. The profile input is now preserved, but existing solution rows are still the previously accepted snapshot. Recalculate and verify. Return to Live HUD, recalculate, and compare several representative distances with verified range data. Confirm the workspace summary names the intended profile before field use.

Muzzle velocity, zero distance, and ballistic coefficient must be positive numeric values. G1 and G7 coefficients are not interchangeable; changing the model without matching coefficient data changes the solve. A profile marked Ready means required solver inputs are present. It does not mean the configuration has been proven on target.

Saved is not the same as solved or verified. Saving preserves the profile input. Recalculation creates a new accepted solution snapshot. Range confirmation establishes whether the inputs describe the real rifle and ammunition.

If The profile cannot be edited or says it needs review.: The saved record may not contain complete raw solver inputs. Replace it with a complete profile or use the canonical profile workflow to repair the missing projectile, velocity, zero, coefficient, or drag-model data.

Expected result. The active workspace names the intended profile, reports the solver as ready, and shows a newly accepted solution that agrees with known data at representative distances.