| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0003021 | Spring engine | General | public | 2012-03-16 05:25 | 2012-03-16 12:52 |
|
| Reporter | Google_Frog | |
| Assigned To | Kloot | |
| Priority | normal | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | fixed | |
| Product Version | 87.0.1+git | |
| Target Version | | Fixed in Version | 87.0.1+git | |
|
| Summary | 0003021: pushResistant units built sequentially become stuck |
| Description | When pushResistant units are built sequentially in a factory the nanoframe for the second unit is created before the first unit clears the placement area. This results in a clogged factory.
The bug does not occur if one of the units is not pushResistant. As far as I am aware it occurs between all pushResistant units. In the replay Ravager is not pushResistant and Slasher is pushResistant. |
| Additional Information | ZK v1.0.3.5
87.0.1-58-gf130e97 |
| Tags | No tags attached. |
|
| Attached Files |  20120316_151728_Comet Catcher Redux_87.0.1-58-gf130e97 develop.sdf [^] (21,873 bytes) 2012-03-16 05:25 |
|
Relationships 
Relationships