I have seen two instances where the Antarctica moved away from nearby hostile stations (I'm assuming this is why it moved) and then stopped. After this the playership was then unable to dock. In the attached image the CSC had been stopped for several minutes. Only happens if the CSC moves.

antarctica no dock.JPG
antarctica no dock.JPG
zip
Antarctica sav.zip
george moromisato 20 Feb 2018:

I believe this was fixed in 1.8 Beta 1. Please re-test.

relanat 10 Jan 2019:

Had this happen again in 1.8b4. The Antarctica moved away from a Ranx outpost and when it stopped the playership got repeated "No stations in range" messages on pressing 'D'.

Possibly it is because 'fltOrderCheckPosition' is setting the CSC property 'dockingEnabled to Nil while it is moving but it never gets changed back to True when it stops?

george moromisato 8 Feb 2019:

I can't reproduce this in 1.8 Beta 5. We do set 'dockingEnabled to True in <OnOrdersCompleted>, which fires when the CSC is done moving.

If you can reproduce this in 1.8 Beta 5, please attached (or email) a save file.

relanat 12 Feb 2019:

1.8b5 save file attached, not sure if you need the Extensions folder so included. Lucky enough to get a game where the Antarctica was created near a non-Ares enemy station.
Although 'behavior' changed from 'moving' to 'Nil' when she stopped 'dockingEnabled' remained 'Nil'.

Any CSCs, another Antarctica, a task force or hospital CSC (Terra not tested), will show a similar behaviour if created near an enemy station. The new CSC will move away and when it stops the player cannot dock. In this case, however, the debug console shows the object data 'behaviour' remains set at 'moving' even after the CSC has stopped and 'dockingEnabled' remains 'Nil' throughout.

george moromisato 13 Feb 2019:

Thank you, that helped. The Antarctica did not have the fix from 1.8 Beta 1. Fixed in 1.8.