Page MenuHomeFeedback Tracker

AI diver can't disarm moored mine while in water, but he can do it on land
Closed, ResolvedPublic

Description

While underwater, I've ordered AI teammate diver demolitions expert to disarm nearby moored mine. He acknowledged receiving the order, but did nothing to execute it. Then (in editor) I've moved both of us and a mine to a land location and revieved the mission again. I've ordered disarming the mine and the AI diver crawled to it and disarmed it.

Details

Legacy ID
1084844426
Severity
None
Resolution
Open
Reproducibility
Always
Category
Swimming and Diving
Steps To Reproduce

Editor:

  1. Place a diver over the water and make it a player's character.
  2. Place a demolitions expert diver nearby.
  3. Place a moored mine (Empty/Mines/Naval mine) close to both of them.

Ingame:

  1. Make sure that the mine was spotted. Swim closer to it if necessary.
  2. Aim at the mine and press tilde for a quick menu
  3. Select "Disable mine"
  1. The diver will say "roger" but won't do anything.
  2. Get back to editor

Editor:

  1. Place both divers and a mine exactly like before, but over the airfield's runway.
  2. Use the same method to order the diver to disarm the mine.
  1. Observe, that he acknowledges, crawls to the mine and disarms it.
Additional Information

AI needs to enter a crawl, in order to safely disarm the mine and it's correct. But it can't "crawl" underwater, so the disarming routine blocks itself.

Event Timeline

armapirx edited Steps To Reproduce. (Show Details)Apr 22 2013, 2:55 PM
armapirx edited Additional Information. (Show Details)
armapirx set Category to Swimming and Diving.
armapirx set Reproducibility to Always.
armapirx set Severity to None.
armapirx set Resolution to Open.
armapirx set Legacy ID to 1084844426.May 7 2016, 1:48 PM

I've had the exact same trouble, the diver will orient towards the moored naval mine, their status actually changes to "fire" and they acknowledge, but do nothing.

MadDogX added a subscriber: MadDogX.May 7 2016, 1:48 PM

Mass closing ancient tickets with no activity for > 12 months; assume fixed or too trivial.

If this issue is still relevant in current dev build, please re-post.