Opened 5 years ago

Closed 4 years ago

#5569 closed defect (fixed)

INDIVIDUAL.GATHER.APPROACHING but idling

Reported by: elexis Owned by: wraitii
Priority: Release Blocker Milestone: Alpha 24
Component: Simulation Keywords: regression
Cc: Patch: Phab:2239

Description

In this match with r22777, there were idle units in various instances that were standing in front of resources and in INDIVIDUAL.GATHER.APPROACHING state but not gathering nor trying to get to the resource.

Attachments (4)

commands.txt (1.4 MB ) - added by elexis 5 years ago.
screenshot0655.jpg (549.0 KB ) - added by elexis 5 years ago.
screenshot0657.jpg (662.9 KB ) - added by elexis 5 years ago.
screenshot0672.jpg (595.5 KB ) - added by elexis 5 years ago.

Change History (10)

by elexis, 5 years ago

Attachment: commands.txt added

by elexis, 5 years ago

Attachment: screenshot0655.jpg added

by elexis, 5 years ago

Attachment: screenshot0657.jpg added

by elexis, 5 years ago

Attachment: screenshot0672.jpg added

comment:1 by elexis, 5 years ago

In screenshot 655 there is similarly a unit standing in front of a building to build that it cant immediately reach and doesnt try a new path, but seems to have given up, if I'm not recollecting incorrectly without having changed the UnitAI state, because it IIRC continued to do something after the building was finished.

comment:2 by Minohaka, 5 years ago

I don't know if units getting stuck in the forest, next to buildings, not capturing, not helping when constructing buildings is related to it. Often happens when units are carrying resources and you instruct a large group to build a new barracks for example (this one is maybe related to how many units are allowed to build at once)

comment:3 by wraitii, 5 years ago

Owner: set to wraitii
Patch: Phab:2239

This might not be entirely fixed by Phab:D2239 (since replaying with the fix changes the state), but from the screenshots all issues seem similar (short distances stuckness in non-idle states), and the issue definitely exists. I'll leave this open for a while after committing that patch so that people can say if it still happens.

comment:4 by wraitii, 5 years ago

In 22815:

Unit Motion - make sure units don't get stuck in the special long-path computation step.

In some rare cases, units could be stuck in the special state of 3 failed path computations, making them always compute long paths instead of trying short paths again. This can happen when they compute a long path successfully, but the unit cannot actually move as it gets obstructed right away.
Make sure this state is never kept for more than one turn to fix this problem.

Refs #5569 (probable fix but kept open for further investigating).

Differential Revision: https://code.wildfiregames.com/D2239

comment:5 by elexis, 5 years ago

Keywords: regression added

comment:6 by wraitii, 4 years ago

Resolution: fixed
Status: newclosed

Per the above, I assume this was fixed by rP22815 . Will re-open if necessary.

Note: See TracTickets for help on using tickets.