ptb
CODE
>>TU 232: Start Squadron Orders {No}
   Squadron:
       NameRemoved1 (11111)                 NameRemoved2 (22222)
   
>>TU 232: Jump {149}
   Jumping to system Madonna (149)
   System Message:
       This system is claimed by FET Destiny's Bastion on behalf of the IMP.
   
>>TU 5: Move to Starbase {2653} {Dock - Yes}
   Move to Delta 9
   Movement suspended. You ran out of TU's.
   The following ships have ran out of tus:
       NameRemoved1 (11111)
        NameRemoved2 (22222)
   Total TU cost for this action is 5.


Which is to be expected however, yesterdays update gave this

CODE
>>TU 240: Start Squadron Orders {No}
   No ships found.


Which means it's lost the squad. I later noted that the lead ship started in Delta 9 and the two other ships are currently in Delta 8, which explains why it couldn't find them, but my question is why did they get left behind, or alternativly why didn't the lead ship stop and wait for them at Delta 8.
Steve-Law
Yeah this thing with squadrons splitting up is getting really annoying. I didn't use any squadrons until a few weeks ago, but seeing several bugs fixed with squadrons I thought that the majority of it is all sorted out. But I think every squadron movement I've issued so far has resulted in one or more ships moving off while the rest are left behind due to lack of TUs.

The chances are this is going to happen at some crucial time like the freighters jumping into a nest of pirates while the warships stay behind.

blink.gif

I think every case I've had this so far has been movement involving entering a stargate, perhaps that specific check has been missed? Or is this still a feature of general squadron movement?



ptb
I havn't had this for at least a week now, so i assume your getting a specific case they have missed.

I'm having no problems with wormholes i don't actually have any squads with stargate keys or i'd try it smile.gif
Steve-Law
Hang on here's something else I thought I'd noticed, but it's definately wrong.

Normal jump this time...

CODE

>TU 14: Move to Starbase {9876} {Dock - No}
   Jumping to system System (123)
   Jump aborted. You ran out of TU's.
   Total TU cost for this action is 100.


This lead ship of the squadron (iow the one giving the orders) had 54 tus the day before plus 60 for the day so that makes 114.

It failed to jump because it didn't have enough tus to jump (100) but had 100 tus taken off anyway.

Of the 5 ships in the squad 1 had been left behind at the stargate. Of the remaining 4 1 did nothing having only 74 tus, the other 2 got this:

CODE

Total TU cost for this action is 100.


And had 100 tus removed (also going down to 14tus), but didn't move or do anything.

(Does any of that make sense? It took me a day to get my head around it...)

A couple of the ships were reporting "Crew have not had shore leave for 30 weeks, their efficiency is reduced." including the lead, but they all showed 100% efficiency.

blink.gif

ptb
QUOTE
It failed to jump because it didn't have enough tus to jump (100) but had 100 tus taken off anyway.


I had that exact bug the other day, but with 78 tus taken off (and 40 remaining) i think it's to do with the tu sync between the ships in the squadron, at least i assumed that at the time, might have another look into the numbers.

QUOTE
A couple of the ships were reporting "Crew have not had shore leave for 30 weeks, their efficiency is reduced." including the lead, but they all showed 100% efficiency.


I get that sometimes, i figure it's just that each crew gives less than 100% but you have plenty spare crew so the ship is 100% as well, as i've only seen it on overstaffed (and overpaided.. damn them) ships.