Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#2095 closed defect (invalid)

[PATCH] Obstructions must be at least 4 m wide before the long-range pathfinder notices them

Reported by: sanderd17 Owned by:
Priority: Should Have Milestone:
Component: UI & Simulation Keywords: patch
Cc: Patch:

Description

When you place a wall of palisades, it's possible that due to the small obstruction size, the long range pathfinder doesn't see them. You can test this in atlas by enabling the pathfinder overlay, and panning your palisades until it makes no squares red.

When you have a long wall, this stops units from moving. The long range pathfinder finds a path through the palisades, but when the short range arrives at the palisades, it can't find a path through, and if the wall is long enough, it can't find a path around either.

A quick fix for this is to set the minimum obstruction to 4m.

Attachments (1)

palisades.diff (3.8 KB ) - added by sanderd17 11 years ago.

Download all attachments as: .zip

Change History (4)

by sanderd17, 11 years ago

Attachment: palisades.diff added

comment:1 by leper, 11 years ago

Component: Core engineUI & Simulation
Milestone: Alpha 14Alpha 15

We should just get the new one in.

comment:2 by sanderd17, 11 years ago

Keywords: review removed
Milestone: Alpha 15Backlog
Resolution: invalid
Status: newclosed

I agree with that, but I also think palisades should work in A14, and not let your units get stuck. Setting the milestone to A15 makes no sense, as the pathfinder should indeed be in. So I'll just close it as invalid.

comment:3 by leper, 11 years ago

Milestone: Backlog
Note: See TracTickets for help on using tickets.