Fix DCS World weapons not firing by checking Master Arm, combat mode, Trigger versus Weapon Release, bindings, locks, warm-up and ammunition.
Weapons in DCS World usually will not fire because the aircraft is not armed, the wrong command is bound, or the weapon has not met its release conditions. Select a loaded weapon, set Master Arm to ARM, choose the combat mode, confirm a lock or solution, then use Trigger or Weapon Release as required.
What should I check first when DCS weapons will not fire?
Check the complete firing chain in order rather than repeatedly changing controls or avionics.
- Confirm that ammunition is loaded. Check the stores or weapon-status display, not merely the external model. For a gun, verify that the ammunition counter is above zero. If you rearmed on the ground, wait for rearming to finish and refresh the aircraft's stores inventory if that module requires it.
- Use the correct aircraft and seat profile. DCS bindings are module-specific and can also be seat-specific. A command assigned under General, another variant of the aircraft, or the pilot's seat will not necessarily work from the gunner's seat. Our aircraft-specific HOTAS binding method explains how to select the right profile and device column.
- Arm the aircraft. Set Master Arm to ARM or the aircraft's equivalent, close any safety cover and enable separate gun, missile or pylon power switches where fitted. Older jets and warbirds may also require gun charging or additional weapon-safety switches.
- Select the combat mode and weapon. Choose air-to-air or air-to-ground mode as appropriate, select a loaded station and confirm that the expected weapon appears on the stores display or gunsight.
- Wait for the weapon to become ready. Some missiles and guided weapons need seeker cooling, electrical power, alignment or warm-up time. A crossed-out station, SAFE indication or missing ready cue usually means the store is selected but cannot yet launch.
- Use the right firing command. Guns commonly use Trigger or Trigger Second Detent, while bombs and many missiles use Weapon Release. Some aircraft work differently, so follow the command name in that module's Controls menu rather than assuming one button fires everything.
- Hold the control when required. A quick tap may be ignored. Computed bomb modes often treat Weapon Release as consent and release only when the aircraft reaches the calculated point; some missile systems also require a deliberate press rather than a brief pulse.
Should I press Trigger or Weapon Release?
Use the command assigned by the aircraft module: Trigger normally operates the gun, while Weapon Release commonly launches missiles, fires rockets or drops bombs.
| Control | Typical purpose | Common mistake |
|---|---|---|
| Trigger first detent | Activates a preliminary function such as gun stabilisation or sensor logic on aircraft that model a two-stage trigger | Stopping at the first stage and expecting the gun to fire |
| Trigger second detent | Fires the cannon or machine guns on many modules | Binding only a generic trigger command when the module expects a separate second-detent input |
| Weapon Release | Releases many missiles, bombs and rockets; often called the pickle button | Pressing the gun trigger for every weapon |
These are conventions, not universal rules. Simplified aircraft, warbirds and different national designs can use different logic. Check our guide to DCS command names and default inputs, then bind the exact command shown for your module rather than copying another aircraft's profile.
The A-10C shows why this distinction matters: its two-stage gun trigger, Weapon Release button, Master Arm state and stores-management workflow perform separate jobs. Our worked A-10C control and weapons example covers that aircraft's process in context.
Why does the button work but nothing launch?
A recognised button press does not override the aircraft's release interlocks, weapon timing or targeting requirements.
- No valid release solution: In a computed bombing mode, press and hold Weapon Release while following the steering cues. The bomb may remain attached until the calculated release point.
- No required lock or seeker state: A guided weapon may need a radar lock, seeker lock, uncage command, target designation or launch-authorised condition. Merely displaying the weapon symbol does not prove it is ready.
- Station not powered: Some aircraft have individual station, missile or pylon power controls. The weapon can appear loaded while remaining unavailable.
- Ground or gear interlock: Certain weapons cannot fire on the ground or with the aircraft in a protected configuration. Test them in a suitable airborne mission rather than assuming a ramp test is valid.
- Incomplete start-up: Missing electrical, avionics, stores-management or weapon-system steps can inhibit release even though the engine and flight controls work normally.
- Multicrew authority: In two-seat aircraft, the other seat may control weapon selection, consent or targeting. Confirm which crew position owns the relevant function.
- Damage or simulated failure: A damaged station, failed weapon system or jammed gun can stop firing. Reloading the mission with failures disabled helps separate damage from procedure.
If a bomb leaves the aircraft but does not explode, the firing control has worked. Check fuze selection, arming delay, release height and impact conditions instead. Likewise, a missile that launches but fails to guide has an employment or targeting problem, not a Weapon Release problem.
How do I separate a control fault from a weapon setup fault?
Test one known input in an airborne-start mission to isolate the binding from cold-start and avionics errors.
- Open the Controls menu and select the exact aircraft variant and occupied seat.
- Assign one uncomplicated input directly to the required Trigger or Weapon Release command. Temporarily avoid modifiers, mode switches and controller software layers.
- Remove conflicting assignments for that command, especially duplicate bindings created automatically across several connected devices.
- Load an airborne-start training or Instant Action mission whose briefing confirms that the relevant weapon is fitted.
- Try a deliberately assigned keyboard key and the HOTAS button separately. If the keyboard works but the HOTAS does not, the fault is in the binding, modifier or device profile. If neither works, return to Master Arm, weapon selection and release conditions.
A mistake we see constantly is troubleshooting a perfectly good joystick binding while the aircraft is still in SAFE, or changing cockpit switches when the command was assigned to the wrong module. Testing the input and the aircraft configuration separately reveals which side is actually failing.