Basically what I want to be able to do is have SAM pilot the mothership to a station and dock with it, without it first undocking the mothership from the drones to do so.

I'm effectively looking for a way to indicate directionality of docking...
That the drones are docked TO the mothership, the mothership isn't docked TO the drones...
If that makes sense?

Is there a way to do something like this already that I'm just not seeing?
I initially tried it by changing the mothership's tag to 'MSAM' but that meant it couldn't see any advertised docks from scripts tagged with 'SAM'.
Then I thought maybe if I have two copies of SAM running on the mothership, one for controlling the mothership itself, and one for advertising docks to the drones.
But I couldn't quite get that to work either, as the second copy seemed to never want to do anything at all, even if it had a different tag, though it did leave the drones docked to the advertising-only tagged connectors when the navigation script ran.

One possible solution I can come up with is to have a dedicated modifier tag on the connectors, (like type=dock|ship) to specify whether SAM should advertise it as a possible place for another ship to dock (and then consider any attached grid a 'child' of itself for the purposes of deciding whether to undock from it before navigating), or use it as part of the ship that would connect to a dock on another grid (and thus consider itself a child of any attached grid when deciding it if should be undocking before navigating).
Where the default would of course be 'any', unless specifically overridden, to maintain the current scheme of things.

Another solution might be to have the dock-seeking code use a separate list of tags, or a wildcard mechanism, to allow for grids to specify their own special SAM tag to navigate themselves without impacting their advertised docks, while still allowing them to advertise potential docks to other grids with different SAM tags.
Though that one I've not 100% thought through, and might not work as I'm expecting.

As PAM is no longer being developed, it would be cool if certain aspects could be integrated into SAM - especially the mining part - as far as I can see the Path Finding of SAM is also superior to that of PAM.

Or maybe we should find a way to make SAM pluginnable in a way, so one can have SAM start other Programmable blocks on arrival at certain stops, let them do their stuff and have them call SAM to continue - sort of a wait for Event system, like you can do with Async and Await.

Link to workshop: https://steamcommunity.com/workshop/filedetails/?id=1507646929

The SAMv2 script (unmodified) is out of date compared to the workshop.

@sugardose - can you please update your source code here so someone can take over your amazing project?

Line 1820 https://github.com/sugardose/SpaceEngineers/blob/af775bebb8fcb8685ec5b4eb295a9dd4ae1299c5/SamsAutopilotManager2.cs#L1820

is probably missing Tags: UNDOCKED, STARTED ?

SendSignals() at least checks for them (Line 2199):
https://github.com/sugardose/SpaceEngineers/blob/af775bebb8fcb8685ec5b4eb295a9dd4ae1299c5/SamsAutopilotManager2.cs#L2199

Unfortunately, uploaded script is ver2.6.7 (current: 2.11.1)

I can't submit a pull request as I already implemented a fix before publishing vMod. What I did was on the docking phase of auto pilot, I had the script continuously scan the connectors to see if they were connectable. If they were, the script would activate a sequence of code to make it appear to SAM to that it's reached its destination so it would send the proper signals.

When I have a ship with multiple connectors and I dedicate one connector as main, other ship log is polluted with message:

"E: Antenna Docks.Listen exception: Input string was not in a correct format."

Does not matter if connector selected as main either by name tagging or in custom data.

Steps to Reproduce

1. Create a SAM enabled Connector and configure an LCD screen to create a path.

• I created one about 10 blocks away at the 3 o'clock position, looking down at the docked ship on the connector.

2. Create an Orientation (ADD STANCE command) in SAM about 300 m away. Orientate it so that it is in a different direction from the ship's nose when it docked to the Connector and the LCD screen.

• I created an Orientation in the 9 o'clock position looking down at the docked ship on the connector.

3. Dock the ship at the SAM enabled Connector

• (using SAM or not doesn't appear to make a difference).

4. Move the cursor in the SAM LCD window to the Orientation and TOGGLE navigation.

Actual Behavior

• SAM status in the LCD goes to "undocking ..." and the ship goes to docking height.
• SAM status goes to "aligning ..." and the ship changes it's orientation to point on the Orientation (destination).
• SAM status goes to "taxiing ... " and the ship changes it's orientation to point to the LCD screen and begins taxiing.
• After taxiing SAM aligns to the destination and heads on it's way.

Expected Behavior

• SAM status in the LCD goes to "undocking ..." and the ship goes to docking height.
• SAM status goes to "taxiing ..." and the ship changes it's orientation to point to the LCD screen and begins taxiing.

What I think is a Bug

SAM shouldn't align to the destination after undocking, then align back to the LCD that makes up the taxiing path. It should transition from Undocking and directly align with the TaxiIng LCD and begin Taxiing.

Additional Information

• SAM version: SAM v2 VMod 9.5.3
• I did try another SAM enabled dock as my destination and observed the same "Actual Behavior". I don't think what type of location SAM is navigating has anything to do with the actual behavior, but didn't test too extensively.
• I don't think orientation of the ship to connector to LCD has anything to do with this behavior, but didn't test too extensively.
• I'm sending this here since I didn't see any other great place to submit a possible bug. I didn't have the chance to validate this on the newest (or any older) version of SAM v2 so I don't know if the same behavior is there as well.

Expected Behavior:

Put [SAM panel0=some tag] on a cockpit and SAM will capitalize the tag and display text to that cockpit.

Actual Behavior:

Put [SAM panel0=any tag] on a cockpit custom name, SAM will modify the custom name in terms of capitalization, but will keep lowercase "panel0".

Hi, until the latest Wasteland update everything has worked just fine, but now i get a constant "E: Update100 Terminal.Tick exception: Index was outside the bounds of the array." Error in the Log screen.
Everything seems to be working, but i just get this error constantly in the log window.