Instalar Steam
iniciar sesión
|
idioma
简体中文 (Chino simplificado)
繁體中文 (Chino tradicional)
日本語 (Japonés)
한국어 (Coreano)
ไทย (Tailandés)
български (Búlgaro)
Čeština (Checo)
Dansk (Danés)
Deutsch (Alemán)
English (Inglés)
Español - España
Ελληνικά (Griego)
Français (Francés)
Italiano
Bahasa Indonesia (indonesio)
Magyar (Húngaro)
Nederlands (Holandés)
Norsk (Noruego)
Polski (Polaco)
Português (Portugués de Portugal)
Português - Brasil (Portugués - Brasil)
Română (Rumano)
Русский (Ruso)
Suomi (Finés)
Svenska (Sueco)
Türkçe (Turco)
Tiếng Việt (Vietnamita)
Українська (Ucraniano)
Informar de un error de traducción
Thanks, glad you guys enjoying the ship!
You have two easy solutions to your problem:
1. lower the work speed to allow the drills enough time to properly clear voxels.
2. change the "overlap" setting in the PAM script (Although I have not ever had to use this).
All the miners have been thoroughly tested without any issues, (also I have 1 Anguilla running an automated mining job right now). By that I mean I ran several copies of each variant through several different mining jobs each before uploading them to make sure this does not happen.
The only time I have encountered an issue anything like the one you are describing was when we left a miner with a PAM job that was far too large on a dedicated server (which may have also needed a restart) and it started leaving pillars between some rows, but even that ship never got locked on any voxels.
So, how wide/high was your mining job, and was it on a DS?