Page 1 of 1
[WAD] B1776. Iron Beam unable to stop Shahed-136 drones.
Posted: Tue Dec 02, 2025 10:21 am
by Nikel
Described in the title.
Edit: The problem is that is considered hostile too late, when the target is within minimum range. The laser fires if WCS air is set to free. Bug due to the late classification?

- IB.gif (144.81 KiB) Viewed 338 times
Re: B1776. Iron Beam unable to stop Shahed-136 drones.
Posted: Tue Dec 02, 2025 11:00 am
by Dimitris
The manual alloc window explains it pretty clearly: You have set WCS to "TIGHT" (ie. engage only confirmed hostiles) and the targets are not currently confirmed hostile.
Also, by the time they are detected, the targets are within minimum weapon range.
So, you're both doctrinally and physically unable to engage.
Re: [WAD] B1776. Iron Beam unable to stop Shahed-136 drones.
Posted: Tue Dec 02, 2025 11:05 am
by Nikel
Thanks for the answer.
Sorry, I had edited the report above.
The question was then whether the hostile classification was too late or correct.
Re: [WAD] B1776. Iron Beam unable to stop Shahed-136 drones.
Posted: Tue Dec 16, 2025 12:00 pm
by Dimitris
Added a tweak for the next update: OWA-UAVs like the Shahed-136 are classified as weapon (rather than air) contacts. This allows designating them immediately as hostile and engaging them if possible.