Following on from Sit and Spin Mining Drone? and not wishing to further hijack the thread I have carried out some basic tests on three variations of my small mining drone.
All three are small 5x5x5 ships and consist of the same power, thrust, storage, cargo space and a rail docker. None have any secondary systems slaved to the salvage computer but each one has 25 salvage modules set up in different ways.
The tests were carried out in factioned space (x12 mining bonus) on the main multiplayer server I play on.
The total number of blocks gathered per mission are as follows.
Version 1 - 5 separate beams of 5 modules
Version 1 =6601.4
Version 2 = 7849.2
Version 3 = 7541.4
The single beam version on average performs better than multiple beams. Version 3, while obviously multiple beam is essentially 5 single beams.
In flight, Version 1 tended to reposotion itself after each sweep and I doubt slaving cannons to the salvage array would make this better. Version 3 was less prone to this however it would sometimes sit without firing the beams. Version 2 would more often than not, find a position above the asteroid and carry out methodical right to left sweeps. I would suggest that there was a 65% reduction in movement.
Someone said that multiple beams are currently pointless as only one beam works anyway. Well visually this isn't the case. All beams show they hit and blocks disappear from each one.
The methodical sweeps of Version 2 can be seen below. The plateau was created by this and the beam can be seen coming in from above.
While I admit more testing is required, I am thinking of replacing my Version 1 drones with Version 2 drones. I may also experiment with slaving cannons to the salvage array but this will mean I will have to replace some of the salvage modules with cannon modules, maybe 12 + 12 so I may have to do further tests of this variation compared to the non slaved version.
I hope these tests were of interest.
All three are small 5x5x5 ships and consist of the same power, thrust, storage, cargo space and a rail docker. None have any secondary systems slaved to the salvage computer but each one has 25 salvage modules set up in different ways.
- Version 1 - 5 separate beams of 5 modules
- Version 2 - 1 group of 25 modules
- Version 3 - 5 separate salvage computers each with a single beam of 5 modules
The tests were carried out in factioned space (x12 mining bonus) on the main multiplayer server I play on.
The total number of blocks gathered per mission are as follows.
Version 1 - 5 separate beams of 5 modules
- 3631
- 4249
- 11472
- 5266
- 8389
- 3354
- 3416
- 15381
- 7177
- 9918
- 3522
- 4706
- 13782
- 7441
- 8256
Version 1 =6601.4
Version 2 = 7849.2
Version 3 = 7541.4
The single beam version on average performs better than multiple beams. Version 3, while obviously multiple beam is essentially 5 single beams.
In flight, Version 1 tended to reposotion itself after each sweep and I doubt slaving cannons to the salvage array would make this better. Version 3 was less prone to this however it would sometimes sit without firing the beams. Version 2 would more often than not, find a position above the asteroid and carry out methodical right to left sweeps. I would suggest that there was a 65% reduction in movement.
Someone said that multiple beams are currently pointless as only one beam works anyway. Well visually this isn't the case. All beams show they hit and blocks disappear from each one.
The methodical sweeps of Version 2 can be seen below. The plateau was created by this and the beam can be seen coming in from above.
While I admit more testing is required, I am thinking of replacing my Version 1 drones with Version 2 drones. I may also experiment with slaving cannons to the salvage array but this will mean I will have to replace some of the salvage modules with cannon modules, maybe 12 + 12 so I may have to do further tests of this variation compared to the non slaved version.
I hope these tests were of interest.