Instalează Steam
conectare
|
limbă
简体中文 (chineză simplificată)
繁體中文 (chineză tradițională)
日本語 (japoneză)
한국어 (coreeană)
ไทย (thailandeză)
български (bulgară)
Čeština (cehă)
Dansk (daneză)
Deutsch (germană)
English (engleză)
Español - España (spaniolă - Spania)
Español - Latinoamérica (spaniolă - America Latină)
Ελληνικά (greacă)
Français (franceză)
Italiano (italiană)
Bahasa Indonesia (indoneziană)
Magyar (maghiară)
Nederlands (neerlandeză)
Norsk (norvegiană)
Polski (poloneză)
Português (portugheză - Portugalia)
Português - Brasil (portugheză - Brazilia)
Русский (rusă)
Suomi (finlandeză)
Svenska (suedeză)
Türkçe (turcă)
Tiếng Việt (vietnameză)
Українська (ucraineană)
Raportează o problemă de traducere
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?