Page 1 of 1

Port "overstacking" bug

Posted: Wed Aug 05, 2009 8:07 pm
by erstad
The importance of this one depends on whether it is just a one time issue related to a scenario setup issue or representative of something that can happen at any time.

Scenario 1, grand campaign, started head-to-head, hot fix not yet loaded

Check Samah. Most (all?) of the TFs start docked at Samah, which is wildly beyond the port capacity. Now create a small TF from the disbanded ships. For example, make one with the two large tankers. The TF also starts docked! (My general experience is that new TFs stat undocked but something is making this different). I haven't fully characterized everything, but small TFs created start docked, if you make a really big one it doesn't.

One might ask if the TF is really docked, or just shows as docked. I ran a simple test by ordering the two-tanker TF to load fuel. When it showed as docked, it loaded 12070 fuel. I then ran a second test where I undocked the TF. Then, it loaded 0 fuel.

Again, if this is just a turn 1 issue, it may not be too big a deal. But if there's something that is letting created TFs start docked that could happen at other times, that could be a problem.

RE: Port "overstacking" bug

Posted: Wed Aug 05, 2009 8:26 pm
by Don Bowen
ORIGINAL: erstad

The importance of this one depends on whether it is just a one time issue related to a scenario setup issue or representative of something that can happen at any time.

Scenario 1, grand campaign, started head-to-head, hot fix not yet loaded

Check Samah. Most (all?) of the TFs start docked at Samah, which is wildly beyond the port capacity. Now create a small TF from the disbanded ships. For example, make one with the two large tankers. The TF also starts docked! (My general experience is that new TFs stat undocked but something is making this different). I haven't fully characterized everything, but small TFs created start docked, if you make a really big one it doesn't.

One might ask if the TF is really docked, or just shows as docked. I ran a simple test by ordering the two-tanker TF to load fuel. When it showed as docked, it loaded 12070 fuel. I then ran a second test where I undocked the TF. Then, it loaded 0 fuel.

Again, if this is just a turn 1 issue, it may not be too big a deal. But if there's something that is letting created TFs start docked that could happen at other times, that could be a problem.

Ports can be overstocked by data from the editor. Lots of other "in game" controls can be overridden by the editor. You could put a carrier in a sub TF if you wanted.

RE: Port "overstacking" bug

Posted: Thu Aug 06, 2009 2:38 am
by erstad
I understand that the TFs that are set up in the editor will be whatever they were set up as. My concern was more that I can create additional TFs which start out docked, even though the port is already far over capacity.