While using a ram, the /control release command won't be effective unless you have successfully used the /arm command
When you are using a ram, you get to :
- build or /control (ram is in a previous state : i.e. armed, aimed, not ready...)
- /aim (if necessary, ram gets to state aiming/aimed)
- /arm (if necessary, ram gets to state arming/armed)
- /fire (if ready, ram gets to state aimed)
If you double /fire, ram auto reloads itself (i.e. as it would with /arm command) and cycles fine through the arming/firing process but even if you can /control release and /control another ram, the other ram will be deemed "not controlled" => "you are not controlling any siege weapon" even with the siege weapon window opened
you need to /control release again, get back to first ram, /fire and /arm properly (with the exact commands and in order) the first one, /control release it than the second ram gets accepted as usable
This issue might be related to all siege weapons (haven't tried them all)
Others can't gain control of the first ram until you process as stated to /control release properly and gain yourself access to the second
1. Try building 2 rams
2. use the first one according to the cycle and "forget" to /arm, using /fire instead
3. /control release while it's loading
4. /control another ram
5. get the command window and no control on it
6. get back to first ram and use the commands each once in the right order
7. you can use the second ram
I think that the control and release of siege weapons should be related to the actual state of the weapon not to the specific order of some last used macro blocking the weapon release to be efficient
You should be able to release the ram by simply using the appropriate intended command/button and/or distance yourself from the weapon
here are some ingame screenshots
http://imgur.com/a/yCQnN
issue is new, and needs confirmation |
requires 3 more confirmations |
votes (priority): 1 |
| 0 players say this report is valid, 0 disagree |