View Issue Details
ID | Project | Category | Date Submitted | Last Update | |
---|---|---|---|---|---|
0005882 | AI War 1 / Classic | Bug - Gameplay | Feb 13, 2012 11:15 pm | Feb 14, 2012 1:31 pm | |
Reporter | TechSY730 | Assigned To | keith.lamothe | ||
Status | assigned | Resolution | open | ||
Product Version | 5.024 | ||||
Summary | 0005882: Queing non-move orders or planet move orders broken when using Multi-Planet FRD mode | ||||
Description | (Actually for version 5.025) When the new Multi-Planet FRD mode is on, the ability to queue (aka, shift click) non-move orders on the same planet or cross-planet move orders is broken. The command simply does not get added to the queue. For example, when this is on, you cannot queue up repair commands or FRD to another planet. Giving a direct order works just fine, only shift-click queuing is broken. Also, when you turn the option off, everything works fine again. | ||||
Tags | No tags attached. | ||||
Internal Weight | Fix Before Major Release | ||||
|
I would mark this critical priority, except there is no critical priority in the priority list. |
|
Due to continuing sound issues with Wine and Pulseaudio, I cannot tell if the "squeak" sound of an order confirmation plays or not when the order fails to register. |
|
Manage to get that the squeak sound does play, even though the order is dropped. |
|
"When the new Multi-Planet FRD mode is on, the ability to queue (aka, shift click) non-move orders on the same planet or cross-planet move orders is broken. The command simply does not get added to the queue." I just tried to reproduce this, but couldn't do so: 0) Made sure the new FRD toggle was on 1) Built a bunch of military ships 2) Selected them 3) Shift-right-clicked a point in space; destination lines showed up and they started moving 4) Shift-right-clicked another point in space, another line drew from the first set of lines to this new point, and the ships went to the first waypoint and then to the second. I repeated it several times with a bunch of different points and with using FRD on some points and not on others, and they performed exactly as I expected. Then I did another test where I: 1) queued up some movement points 2) switched to the galaxy map 3) shift-V-right-clicked a neighboring planet 4) switched back to my homeworld and held shift to show the lines; they still had the movement points queued and the last one had a line drawn to the wormhole to the target planet 5) switched to the galaxy map and shift-V-right-clicked another neighboring planet The ships FRD'd to the first neighbor, cleared it out, then moved to the second neighbor and cleared it out. So, if you can give me exact steps to reproduce (and a save, if it doesn't reproduce in a new game), I can take another look, but right now I'm kind of confused :) |
|
Strange, I was able to reproduce it perfectly, even across two seperate sessions. Well, here is something that I found reproduced it reliably. Set some constructor on a large task, like building a starship or something. Then take an engineer: 1. Queue up a move order or two 2. Queue up an assist construction order The move orders queue up just fine, but the assist construction order fails to register. Another example. With a military unit, when its "order queue" is empty, shift V right-click onto a planet (aka, queue up a cross planet FRD move order) That failed to register in my test, even though a V right-click (no shift) worked just fine. |
|
I can give you the save I was playing at the time I observed this later this evening. |
|
"Well, here is something that I found reproduced it reliably. Set some constructor on a large task, like building a starship or something. Then take an engineer: 1. Queue up a move order or two 2. Queue up an assist construction order The move orders queue up just fine, but the assist construction order fails to register." That is true, but it does this regardless of whether the new toggle is on; I think this has been the case for a long, long time. Later I can try reverting to 5.024 to see if so, but I don't think it's going to be different. "Another example. With a military unit, when its "order queue" is empty, shift V right-click onto a planet (aka, queue up a cross planet FRD move order) That failed to register in my test, even though a V right-click (no shift) worked just fine." Those all work fine for me :) I think the AI is playing a little game with us. |
|
Funny, the queue up assist construction order worked fine when the new toggle was off for me, but I could be remembering wrong. I'll try again tonight. |
Date Modified | Username | Field | Change |
---|---|---|---|
Feb 13, 2012 11:15 pm | TechSY730 | New Issue | |
Feb 13, 2012 11:22 pm | TechSY730 | Note Added: 0019065 | |
Feb 13, 2012 11:24 pm | TechSY730 | Note Added: 0019067 | |
Feb 14, 2012 8:20 am | TechSY730 | Note Added: 0019076 | |
Feb 14, 2012 8:21 am | TechSY730 | Note Edited: 0019076 | |
Feb 14, 2012 9:02 am | tigersfan | Internal Weight | => Fix Before Major Release |
Feb 14, 2012 9:02 am | tigersfan | Assigned To | => keith.lamothe |
Feb 14, 2012 9:02 am | tigersfan | Status | new => assigned |
Feb 14, 2012 9:23 am | keith.lamothe | Note Added: 0019085 | |
Feb 14, 2012 9:23 am | keith.lamothe | Status | assigned => feedback |
Feb 14, 2012 9:41 am | TechSY730 | Note Added: 0019087 | |
Feb 14, 2012 9:41 am | TechSY730 | Status | feedback => assigned |
Feb 14, 2012 9:46 am | TechSY730 | Note Added: 0019090 | |
Feb 14, 2012 10:23 am | keith.lamothe | Note Added: 0019097 | |
Feb 14, 2012 10:23 am | keith.lamothe | Status | assigned => feedback |
Feb 14, 2012 1:31 pm | TechSY730 | Note Added: 0019125 | |
Feb 14, 2012 1:31 pm | TechSY730 | Status | feedback => assigned |