Page MenuHomeSchine - Phabricator

Starmade | Big enough mining drones don't salvage
Resolved, needs quality check / confirm fix, HighPublic

Description

Unless there is something I am very much missing, all attempts to make the Fleet Mining work have pretty much failed with medium sized vessels made prior to the update. Each of them can function as their own miner perfectly fine.


Commencing mining, yet nothing happens with simplest ship as possible that was available


Odd mining, 1 output is aiming, yet the others do not hit

Details

Task Type
Bug
Testing Results
Affected Gamemode(s)
Single and Multi
Reproducible
Yes
Last tested (version)
0.199.223
Category
Fleets
First occurrence (version)
0.19624
Hardware/Software/System
OS-Specific
No
Hardware-Specific
No
Video Card Vendor
NVIDIA
Video Card Model
GT530
Steps to reproduce

Either using own mining ships, or using any combination of the ones inside this BP:

(Place inside blueprints to access)

  1. Spawn ships and set up the fleet in any combination or number
  1. Go to a sector containing at least 1 asteroid, Tell fleet to "Mine This Sector"
  1. Notice the AI react and move, but fail to ever begin mining operations in almost all cases. They will tend to sit in one place, unmoving. Note that there is odd behaviour with their salvage beams when there is any mining.
Tester information (Internal use only)

Using a drone that's any decent enough size will result into 2 things:

  1. the drone having issues moving into position to mine the asteroid, it will usually orbit the point it has to sit on. Could be caused by their center of mass being too different from the ship core resulting in unexpected turning circles.
  2. the drone flying towards the asteroid (sometimes even ramming it) only to proceed going back to its starting position. It constantly loops between going back and forth rapidly without actually salvaging. The drone does seem to aim correctly, just not fire.

Small drones seems to work fine, the bigger ones (60-100m in length) do not.

Serverconfig (server.cfg)
<replace this line with the file content>
Clientconfig (settings.cfg)
<replace this line with the file content>

Event Timeline

Napther updated the task description. (Show Details)Mar 20 2016, 6:54 PM
Napther set First occurrence (version) to 0.19624.
Napther changed Video Card Vendor from uncertain to NVIDIA.
Napther set Video Card Model to GT530.
Napther edited Serverconfig (server.cfg). (Show Details)
Napther edited Clientconfig (settings.cfg). (Show Details)
Napther set Last tested (version) to 0.19624.
Napther edited Steps to reproduce. (Show Details)
Napther edited Tester information (Internal use only). (Show Details)
Napther added a subscriber: Napther.
Napther created this task.
Restricted Application added a project: Issue Navigation. · View Herald TranscriptMar 20 2016, 6:54 PM
lancake claimed this task.

-Validated-

Medium to large ships have issues aiming their salvager, or getting to face the ship correctly.

I'm unsure why those 2 ships don't want to fire though, I'm guessing their salvager isn't linked to a chest, or there is no room left in that chest. Both will disable salvaging. Please provide a blueprint of that smaller ship too so I can test that out too.

In case it's not user error, I'll make a new task for it, this one is reserved for the ship spinning/salvage issues with medium-large ships.

lancake shifted this object from the S1 Public space to the S3 Starmade space.Mar 27 2016, 12:02 AM
lancake changed the visibility from "Custom Policy" to "Public (No Login Required)".
lancake changed the edit policy from "Task Author" to "Starmade (Project)".
lancake set Task Type to Bug.
lancake set Category to Fleets.
lancake set OS-Specific to No.
lancake set Hardware-Specific to No.
lancake set Affected Gamemode(s) to Single and Multi.
lancake set Reproducible to Yes.
lancake edited Tester information (Internal use only). (Show Details)
lancake triaged this task as High priority.
Restricted Application added a subscriber: AndyP. · View Herald TranscriptMar 27 2016, 12:02 AM

I can say that a slight user-oversight meant that the smaller brick-with-cockpit drones indeed dont have their salvage computer connected with a storage block. Didnt realise this was the behaviour at the time of creating and testing, as my larger vessels were not mining too well at all.

I can say it works "ok" for smaller ships on the scale of 25x21x21, but not appropriately using their mining arrays is a real drag, and wont see much use untill they can be told to mine a whole system without player input. Especially since there is a salvage cap of 100 modules/output in terms of salvage power.

Also, They will collide with Asteroids, and they cannot mine a moving asteroid, significantly reducing their mining speed over a player purely mining themself

I have performed some fleet mining tests today,

  1. Mining drones 53 mass, L 56 x W 11 x H 9 (9 drones)

All nine drones will mine.
Add a Drone, mass 1.1k L 120

All drones stop mining, larger drone rams the asteroid repeatedly.

  1. Increase 56 mass drone to 240.9 Mass, L 70 x W11 x H9 (Single Drone)

Drone approached asteroid rams and retreats then rams again.
Manual piloting the drone and salvage beams will not remove blocks from the asteroid.
Relog
Manual mining works again
Exit Drone and issue mining command, drone rams the asteroid.

  1. Reduce Drone mass to 191.2, L 56 x W11 x H9

    Drone mines with command.
  1. Increase Drone mass to 627.4, L63m

    Drone refuses to mine. Decrease length back to 56, drone still refuses to mine. Disband Fleet and relog, make a new fleet now drone mines again.
  1. Add more drones of the same mass and length to the fleet, some drones try to mine with beams one drone rams the asteroid sporadically.

Last point to confirm again is that asteroid selection is random and most of the time asteroids on nav are totally ignored.

Restricted Application added a project: Starmade. · View Herald TranscriptSep 12 2016, 1:31 PM
lancake edited Tester information (Internal use only). (Show Details)Sep 21 2016, 12:02 PM
lancake changed Last tested (version) from 0.19624 to 0.199.223.
lancake moved this task from Open / Validated to Confirmed on the Issue Navigation board.
lancake renamed this task from "Mine this sector" causes AI to move, but not to Mine to Big enough mining drones don't salvage.
lancake changed the task status from Open to In Queue (Game).
Restricted Application edited projects, added Game Development; removed Issue Navigation. · View Herald TranscriptSep 21 2016, 12:02 PM
Genar added a subscriber: Genar.Oct 18 2016, 11:20 PM

I really Hope this is going to be Fixed soon... Got the same damn Bug . Tested it with 2 K Ships and higher Mass ones. Didn't worked as expected

schema added a subscriber: schema.Dec 2 2016, 2:43 AM
schema changed the task status from In Queue (Game) to Resolved.

Should be better now

Restricted Application edited projects, added Quality Assurance; removed Game Development. · View Herald TranscriptDec 2 2016, 2:43 AM
Restricted Application added a project: Fleets. · View Herald TranscriptMar 10 2017, 6:15 PM
AndyP moved this task from Backlog / Unclassed to Alpha on the Fleets board.Mar 11 2017, 11:03 PM

We've been having problems with fleets refusing to mine on LvD as well. I tested with some 3k miners. The salvage computers had salvage beams and a storage attached. Plenty of power and thrust. When issuing the command, nothing happens.

Seconded, tried to perform a test (I have an idea as to what the issue might be) but couldn't do so due to drones just refusing to aknowledge any mining order.

Potentially related, recently noticed that the behaviour of AI is affected by the relative locations of the COM and the core with behaviour becomming less reliable the further apart these two are. Could be that with larger mining drones the distance between the COM and core is causing the issue. This also may be worth looking into as its own issue.