Инсталирайте Steam
вход
|
език
Опростен китайски (简体中文)
Традиционен китайски (繁體中文)
Японски (日本語)
Корейски (한국어)
Тайландски (ไทย)
Чешки (Čeština)
Датски (Dansk)
Немски (Deutsch)
Английски (English)
Испански — Испания (Español — España)
Испански — Латинска Америка (Español — Latinoamérica)
Гръцки (Ελληνικά)
Френски (Français)
Италиански (Italiano)
Индонезийски (Bahasa Indonesia)
Унгарски (Magyar)
Холандски (Nederlands)
Норвежки (Norsk)
Полски (Polski)
Португалски (Português)
Бразилски португалски (Português — Brasil)
Румънски (Română)
Руски (Русский)
Финландски (Suomi)
Шведски (Svenska)
Турски (Türkçe)
Виетнамски (Tiếng Việt)
Украински (Українська)
Докладване на проблем с превода
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?