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
I also updated the blueprint with the current version of automatic LCDs
How are you setting the target?
DS or single player?
What's the limit on your server? Sometimes a large grid miner might be better with those limits.
It's tossing a lot of errors on code check/compile
What PBs where having errors?
Likely the LCD PB since it has been updated since I published the blueprint.
maybe BARABAS; that would just effect the automatic unloading of ore when docked.
My only request is a smaller and lighter version - four drills or even 2 drills. Less cargo, less engines etc. Would help early game a lot. Thanks. :)
Large or 'small' asteroid?
Can you publish the world so I can take a loot at it?
I'll see about changing that in the miner so it turns off both.
http://forums.keenswh.com/threads/01-107-008-sp-win10-inconsistent-connector-actions-when-turned-off.7372537/
Afterwards i moved it to my large ships connector and tried to launch it, ok it said i ts have to be docked. Ok been there done that, so i docked the connector and chose again to launch. Well it tried but it does not unlock the connector. Tried around the past few hours but could not figure out whats wrong with it.
Note that mining is changing a lot over the last couple of releases from Keen; I hope it will settle down soon and I'll update the miner to work more optimally.
It does need to stay centered for the autopilot to re-dock correctly (when keen fixes it again).
The current AP collision avoidance is 400meters. I'll have to test with navigation in close proximity.
First step will be to automatically generate the docking waypoints into the remote control. I'll have that added soon.
https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=376166089
BTW: Will the new collision avoidance by AP that Keen has added be used?
I am seeing the whole miner bounce sideways at times, and thanks to last weeks collision particles, its easier to see there are some side impacts. Miner speed is usually around 2+ m/s when this happens.
Also had a couple of strange occurances, which I'll detail separately.
They are on the edge of the clear space created.. if they are a problem, we'll have to cut them off and lose the cargo space provide. Feel free to do this yourself; either grind down the cargo containers and/or create a local blueprint without the problem cargo containers.
I sent two out after posting yesterday, and as long as I interupt their mining before they get too damaged, and send them home using the go home function, both returned, one was unharmed and one even managed to auto-dock.
While looking at the wreckage and survivors that made it back, and the damage they sustain, its highly likely that its the cargo containers taking damage, releasing their ore as a large rock near the middle of the miner thats causing the fatal destruction when it occurs.
Singleplayer, and yes using the Keen autopilot (double checked in precision mode), and using the GPS co-ords from the GPS generated by the programming.
All miners sent to different asteroids, so no chance of Miner vs Miner collision.
The two that never survived were both in pieces, some drill arms removed by damage, and the tail ejector section had floated quite some distance away on one of them. Both of these were sent to very large 'roids.
What happened in the asteroid? Did they explode? run out of power? Not able to move?
Multiplayer or singleplayer?