AI Offensive (Combat) 'Stay At Range' not working

Mozo shared this bug 17 days ago
Not a Bug

I'm trying to use the 'Stay At Range' function of the AI Offensive (Combat) block to grind enemy (or neutral) grids using vanilla AI.

I have built a drone that flies to the target using this block, when the grid comes into range a sensor switches the Offensive and Move AI Off (Move is toggled by the sensors)


I have a Test setup using my vanilla save (it's a space drone with ions so in space, ignore the ground based drones from another bug report !)

Jump in the 'Salvager Mk1" and press 4 to disconnect the connector.

The drone will fly up using override but then it just sits there, the offensive block says "Attacking Enemy Test Base" but it never does.

The range is deliberately set to 0m so that when the sensor has switched the AI Off the drone will still have momentum.

Save game attached.

Replies (3)

photo
1

Hello, Engineer!


We're sorry to hear you're experiencing issues.

We've noticed a few issues with the setup you currently have. Could you please try following things for us:

  • Disable collision avoidance on the AI Flight block
  • Increase the minimum distance on the AI Offensive block

We can also recommend using the Intercept pattern instead, this one is created for the purposes you've described and should suit your purposes better. In addition it has an Override Collision Avoidance setting which you could use.

Please let us know if this resolves your issue.


Kind Regards,

Keen Software House: QA Department

photo
1

I have circumvented the problem by increasing the maximum distance to 45 and the minimum distance to 1 however i see no reason why the stay-at-range would allow me to set a value that it cannot work from ?

Hence the bug report, i can set the min/max to 0/1 but it won't work with those settings.

photo
1

Hello, Engineer!


This setting is taking the size of the grid into account, as well as the ability of the grid to reach a possible waypoint within the set range. As your specific grid was larger than the set values as well as having collision avoidance enabled, grid was unable to find a possible waypoint.

We'd like to reiterate that we recommend using the Intercept pattern for this purpose.

As this is not a bug, we will close this ticket.


Kind Regards,

Keen Software House: QA Department


Leave a Comment
 
Attach a file