View Issue Details
| ID | Project | Category | Date Submitted | Last Update | |
|---|---|---|---|---|---|
| 0018996 | AI War 2 | Bug - Gameplay | Mar 2, 2017 10:16 pm | Mar 6, 2017 1:51 pm | |
| Reporter | BadgerBadger | Assigned To | keith.lamothe | ||
| Status | resolved | Resolution | fixed | ||
| Product Version | 0.103 | ||||
| Fixed in Version | 0.105 and 0.106 | ||||
| Summary | 0018996: Strange issues with non looping building from ark | ||||
| Description | I have my Ark set to build fleet ships in a non looping fashion. I see some quite odd behaviour. When clicking for the first time since setting it to non looping a ship it seems to not work, I have to click several times. Also there are some other weirdnesses where sometimes it stops adding ships at all; this only occurred after starting with Bomber though. At other times, it seemed that you couldn't stack non looping build orders; this i noticed from both the space dock and the ark. If you had a single fighter queued and asked it to also produce a bomber it would replace the fighter order with the bomber. In many cases, after clicking a few times non looping started to work in a more sensible situation. The issues were most visible for the first couple clicks after setting the arc to build non looping. When things started working though I could always reproduce it by switching between looping and nonlooping a couple of times, until landing on nonlooping. Sometimes I would also click away from the ark before changing it to nonlooping the final time before beginning my experiment. I saw this on both linux and OSX | ||||
| Tags | No tags attached. | ||||
|
|
For 0.105: * Fixed an issue preventing the build queue from updating when a non-looping queue finished an item (so the item would just keep showing on the interface, despite being completed and thus removed). * Fixed an issue causing a "cannot build this now" situation to remove non-looping queue items; for instance if you hit the cap it would just remove the item even if it wasn't complete. The item should not continue producing in that case, obviously, but it should stick around to be fulfilled if/when there's room in the cap. * Reworked how button-set elements in the UI (like on the build menu) work so that they don't flicker as much and don't let mouse-clicks "through" if you click right as they're updating in response to you queuing something new, etc. Thanks :) |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| Mar 2, 2017 10:16 pm | BadgerBadger | New Issue | |
| Mar 6, 2017 8:07 am | keith.lamothe | Assigned To | => keith.lamothe |
| Mar 6, 2017 8:07 am | keith.lamothe | Status | new => assigned |
| Mar 6, 2017 1:51 pm | keith.lamothe | Note Added: 0045899 | |
| Mar 6, 2017 1:51 pm | keith.lamothe | Status | assigned => resolved |
| Mar 6, 2017 1:51 pm | keith.lamothe | Fixed in Version | => 0.105 and 0.106 |
| Mar 6, 2017 1:51 pm | keith.lamothe | Resolution | open => fixed |
