When creating a unit, switch to another tab and do any action - create or modify a Formation Template, for example. Go back to the creation window and click the “Create” button. Any other action in this window will return the unit to its normal state.
SJW: The code specifically returns ships without a current mothership (not in a hangar) for detection. Are you sure it is in the hangar and not just in the same fleet as the carrier?
Ground Forces Organizations tab:
Formation Templates marked as obsolete then un-marked do not show up again for selection in the Organizations tab in the center column.
Renaming a formation template does not propagate through to the Organizations tab center column, it will keep the original name forever.
No I haven’t seen anything unusual about it at all beyond the popup. I’ve been able to capture ships and fight their crew with my boarders and I think I’ve been seeing are of the relevant events and I have been able to capture both raider and NPR ships so beyond the popup, no I haven’t noticed anything unusual about boarding.
seems like if you tractor a parasite directly out of a carrier, the parasite and carrier both don’t realize it, and the maint and deploy clocks remain zeroed.
Here’s the timeline of the tug, the parasite showing that it is still in the carrier back in the original fleet, and that carrier showing that it still thinks it is carrying a 3rd ship, despite only having two docked.
I lost contact with an NPR fleet less than a month ago.
Just now I regained contact with some of the ships in the fleet.
(The ships with the hottest engines. I have every confidence that all of the ships previously detected in the fleet remain in the fleet.)
The apparent bug is that for one of the ship designs, the sensor range is not displayed with the lost contact on the map.
Here’s the current contact group (on the right) and the two groups of lost contacts from the fleet (on the left).
Here’s a closeup of the two groups on the left. (I lost contact with the Servals slightly sooner than with the Balkans, which makes sense because the Serval engines aren’t as hot.)
Only the Balkan Lynx is showing the sensor range, but the Serval has the exact same sensor. (I have captured multiples of both types; I know the design specs.)
(Sidenote: nor is the range of the Serval sensor displayed with the new contact group. Which it should not be, since I have not detected the Servals. The Cougar does not have that R1 sensor. Only the R20 and R116 shown.)
Interesting addendum:
As I closed range, I first detected the Balkans with the Cougars.
As soon as I did, the lost contact for the Servals showed their sensor range.
Conclusion:
It seems like display of sensor range for lost contacts might be looping through sensor types for all lost ships in a given current fleet (or at a given current location), rather than looping through sensor types for all lost ships at a given lost contact location.
Not sure if it’s a bug or WAI.
I have tens of Decoy Launchers, salvaged from NPRs wrecks. I researched them too. But, in the View Technology window, no Decoy Launcher appears. Is it correct?
Take an ELINT ship, add a box launcher to it, and now auto-assignment doesn’t care about Intel bonus when assigning a commander.
BUG: Auto-assignment should consider a ship that is mostly just an ELINT module with an engine to be an intel ship, and assign intel commanders, no matter what ancillary components have been added.
