Zasubskrybuj, aby pobrać
XU-3 Auto mining drone

• Preferably adjust any mining job parameters before the job starts. Doing otherwise will apply changes after the finished shaft.
  
• After using the interactive menu on the drone with the mouse control function, press 1 on the toolbar to disable it. Otherwise, you won't be able to fully control the drone.
  
• While installing connectors on your carrier, install them in a line, only on one side of the ship. Doing otherwise will cause collisions.
  
• When starting a new job align the carrier's connectors horizontally with the entry of the shaft.
  
• While starting a new mining job, align the carrier's connectors perpendicular to the shaft.
  
• After changing the mining area or copy/paste in different location, set up a new mining job first. Otherwise while recalling the drones will try to get to the old location first.
  
• If the drone gets damaged during the mining job, after fixing it, recompile a-min3r PB block on the drone
  

  Początkowo opublikowane przez cheerkin:

  That's not needed unless you absolutely lost one of crucial blocks (main gyro, remote, connector). Otherwise the drone would resume work as soon as you fix everything.

• If you see any weird behavior, like a drone just hanging in the air, clear custom data of the empty "docka" connectors, if that won't help execute "command:clear-storage" and "purge locks" (the latter may cause collisions)
  
• If you can't control the drone after undocking it from the station, turn off the gyro override (it's on the toolbar of the drone)
  
• If completely changing the set of drones, recompile the station's PB block. It will update the list of active drones.

• Do not press "resume" or "recall" more than once. It will break the system.
  
• Avoid recalling when some of the drones are docked. There's an issue with that function that may cause problems.
  
• Do not resume while still mining
  
• Do not copy/paste the drones during their task running

The command to take control over the interface is "cc". You need to run the PB a-menucommand with such argument. Running it again will disable the interface and bring back the control over the drone.
Alternatively you can run the same PB (a-menucommand) with the arguments:
- up
- down
- enter
- esc
to navigate through interactive menu.