Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
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?