Problems with mounts going into "reloading" state while still having weapons

[caelunshun]

Currently, a mount seems to go into the "reloading" state if it is not fully loaded and has not fired for ~5-10 minutes. For example, if a Patriot launcher with 14 missile capacity is attacked and it fires one missile, then 10 minutes later it starts "reloading" despite having 13 missiles left. During this long reloading period, it is unable to fire any missiles and is therefore vulnerable. While this logic could maybe make sense in some contexts, it seems rather silly for the operators to start reloading the launcher in the middle of a hot conflict.

This behavior makes SAMs with magazines very unreliable in some scenarios.

One possible solution is to add a doctrine setting for "reload only when all weapons expended." If enabled, then mounts will not start reloading until they are completely empty.

[Raptorx7_slith]

We're looking into this, thanks. For now you can force or cancel a reload by using the editor