Game masters may divert aircraft to other areas to maintain mission flow or populate areas without interference. This is due to Arma’s performance limits. Pilots should avoid unprompted engagement and work with mission staff to simulate realistic behaviour instead of acting on everything they see.
If an AO isn’t populated, simulate using radio communications with mission support. Ask what would realistically be seen, then report accordingly. This preserves immersion and supports the scenario. Good pilots enhance the mission by staying in sync with the bigger picture, not exposing technical boundaries.
Fixed-wing aircrew support ground forces and are often a small part of the ORBAT. Missions are built around infantry, not aircraft. Seeing enemy units early (such as game master-spawned threats) doesn’t mean they should be engaged. Only act if the threat is imminent to ground forces or on instruction. Early action can disrupt mission pacing.
Used when anti-air threats are possible. The aircraft approaches, fires ordnance (typically rockets), then immediately turns away before crossing over the target. The distance of the break depends on enemy threat range, reducing exposure to return fire.
Used when enemy anti-air threats are minimal or absent. The aircraft flies directly at the target, fires forward-facing weapons like rockets or cannons, and exits by flying over or near the target. Other ordnance such as bombs may be dropped using this method.
Dive attacks improve accuracy for rockets, bombs, and cannon fire by tightening the impact pattern and reducing timing errors.
Two primary dive attack profiles are used:
Steeper dives increase accuracy but reduce reaction time. Balance dive angle, speed, and weapon type for safe, effective strikes. Laser-guided bombs benefit from altitude; cannon fire spreads more at longer ranges.