| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 0005386 | Spring engine | General | public | 2016-11-06 14:40 | 2016-11-06 18:18 | ||||||||
| Reporter | Google_Frog | ||||||||||||
| Assigned To | |||||||||||||
| Priority | normal | Severity | major | Reproducibility | always | ||||||||
| Status | new | Resolution | open | ||||||||||
| Product Version | 103.0 +git | ||||||||||||
| Target Version | Fixed in Version | ||||||||||||
| Summary | 0005386: 103-134 Units stuck on structures | ||||||||||||
| Description | Constructors occasionally become stuck while constructing buildings. All units could become stuck this way but it is less common. There are two different ways for them to become stuck. The first method of becoming stuck is to produce a grid of structures with the gaps between buildings thinner than the footprint of the constructor. The constructors eventually back into an impassible area and become stuck in somewhere that they should never have been able to reach. This method is highly reproducible. The other method of becoming stuck is to produce a grid of structures with gap sufficient to walk through. This can cause constructors to be stuck on the edge of impassible areas and occurs rarely. It is hard to reproduce with construction, however, the same bug can be reproduced reliably with many repeated move orders throughout a preexisting grid of structures. The move orders time out after a short time of being stuck (unlike construction orders) so some attention is required while reproducing. | ||||||||||||
| Additional Information | Zero-K v1.4.11.0 | ||||||||||||
| Tags | No tags attached. | ||||||||||||
| Checked infolog.txt for Errors | |||||||||||||
| Attached Files |
| ||||||||||||
 Relationships |
|
 Relationships |
| Notes |
|
|
Google_Frog (reporter) 2016-11-06 14:43 |
constructionStuck.jpg shows a constructor being stuck in the hard to reproduce configuration. cosntructionApproach.jpg is what the constructor was doing just prior to being stuck. The constructor would sit stuck indefinitely, something moving its legs and sometimes standing still. It was unstuck by giving it a move order. |
|
Google_Frog (reporter) 2016-11-06 14:45 |
thinStuck.jpg and moveStuck.jpg show the bugs as reproduced in the attached replay. |
|
abma (administrator) 2016-11-06 16:01 |
just a guess in /debug output very likely the updatequeue is far away from 0, then such things can happen. |
|
Google_Frog (reporter) 2016-11-06 18:18 |
I highly doubt it. I have not noticed any sluggishness in pathmap updating since the update speed was last boosted. There is very little going on in both the real game (unfortunately run with a sdd) and the attached replay. This is not a new bug, I just noticed a failure case in a real game recently and took the time to report it. |
| Notes |
| Issue History |
|||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-11-06 14:40 | Google_Frog | New Issue | |
| 2016-11-06 14:40 | Google_Frog | File Added: 20161107_002635_TitanDuel_103.0.1-134-g819e5b4 develop.sdfz | |
| 2016-11-06 14:40 | Google_Frog | File Added: cosntructionApproach.jpg | |
| 2016-11-06 14:41 | Google_Frog | File Added: constructionStuck.jpg | |
| 2016-11-06 14:43 | Google_Frog | Note Added: 0016857 | |
| 2016-11-06 14:43 | Google_Frog | File Added: moveStuck.jpg | |
| 2016-11-06 14:44 | Google_Frog | File Added: thinStuck.jpg | |
| 2016-11-06 14:45 | Google_Frog | Note Added: 0016858 | |
| 2016-11-06 16:01 | abma | Note Added: 0016859 | |
| 2016-11-06 18:18 | Google_Frog | Note Added: 0016860 | |
| Issue History |