This is a suggested idea for how controlling other crafts can be managed:
add a block in messages named "Master" and another called "Slave" , knida like the "On start" . the slave block has an empty space to input a code (letters/numbers) of your choice and that's it. while for the master craft the block "Master" besides having the same space as a control pass, will be the start of the full script that's meant to run on the slave craft to perform what you want from it while in full control of your craft (either manually or by vizzy) . the main craft shouldn't recognize whatever under the block "Slave". so now when i perform auto docking i can tell the station (the slave craft) to orient in prograde or whatever that needs to be done. That can be performed without accidentally affecting other crafts that has a slave block since there's a communication code

Tags
Discussion

2 Comments

  • Log in to leave a comment
  • Profile image
    8,458 crowxe

    @NoIDontWanna
    i thought this term (slave/master) is still being used in computers, particularly when connecting 2 hard disks together. Or maybe that's an obsolete now, i don't know it's been long since i done any hardware task

    4.7 years ago
  • Profile image
    8,458 crowxe

    i'm willing to sacrifice some physics, visualization and frame rate in the course of having such option.

    4.7 years ago

4 Upvotes

Log in in to upvote this post.