Opened 9 years ago
Last modified 5 years ago
#3505 closed defect
Pathfinder - Units in formation stuck frequently — at Version 3
Reported by: | elexis | Owned by: | |
---|---|---|---|
Priority: | Release Blocker | Milestone: | Alpha 19 |
Component: | Core engine | Keywords: | pathfinding |
Cc: | Patch: |
Description (last modified by )
Since formations were enabled again in r17028, units in formation are stuck frequently at obstructions, mostly at resources. They seem to become stuck once one of the units are stuck and don't retry finding a path. When using no formation, they are stuck rather rarerly.
Often many walk-orders are required to resolve it.
This is probably the same bug as #3471, there is also a unit stuck without obstruction:
Change History (8)
by , 9 years ago
Attachment: | formation_stuck_in_metal.gif added |
---|
comment:1 by , 9 years ago
Description: | modified (diff) |
---|
by , 9 years ago
Attachment: | commands.txt added |
---|
by , 9 years ago
Attachment: | stuck_without_obstruction.gif added |
---|
comment:2 by , 9 years ago
Description: | modified (diff) |
---|
by , 9 years ago
Attachment: | commands_stuck_without_obstruction.txt added |
---|
The replay where those 5 units of the blue player from the gif got stuck. Notice they are not inside an obstruction and also don't touch one. The entity IDs of the units are 1149-1153 and they were stuck after a command ordered them to move on turn 2080 (17min 19sec).
comment:3 by , 9 years ago
Description: | modified (diff) |
---|
The replay above is for r17131.
This ticket sounds like a duplicate of #3471 as units here are also stuck without touching any obstruction.
If you replace the construct
order with an identical walk
order in the minimal replay (attachment:commands.txt) then the units will not be stuck.
466c466 < cmd 1 {"type":"construct","template":"structures/ptol_house","x":854.0781860351562,"z":361.5915222167969,"angle":2.356194490192345,"actorSeed":34134,"entities":[10090,10091,10109,10110,10111,10112,10113,10114,10115,10116,10117,10118],"autorepair":true,"autocontinue":true,"queued":false} --- > cmd 1 {"type":"walk","x":854.0781860351562,"z":361.5915222167969,"entities":[10090,10091,10109,10110,10111,10112,10113,10114,10115,10116,10117,10118],"queued":false}
So maybe it has something to do with new obstructions not being taken into account correctly.
by , 9 years ago
Attachment: | commands_2_stuck_men.txt added |
---|
Very short replay. Two men stuck after building houses. r17131
Here a fairly small replay for r17117.