Skip to content
This repository has been archived by the owner on May 9, 2023. It is now read-only.

More detailed Ping data #54

Open
voshond opened this issue Dec 10, 2020 · 3 comments
Open

More detailed Ping data #54

voshond opened this issue Dec 10, 2020 · 3 comments
Labels
enhancement New feature or request

Comments

@voshond
Copy link

voshond commented Dec 10, 2020

according to your Website almost all of the ships are displayed with the hardpoint_ping and are all S1

https://www.youtube.com/watch?v=xpvKokenHZA

Based on this youtube video there seems to be greater differences on how these scanners work and which kind of response they have with mining nodes.

In order to make an educated buying decision i'd like to dig deeper and see if there are differences in them, that would explain the results shown in the video.
Did you find any?

@richardthombs richardthombs added the enhancement New feature or request label Dec 15, 2020
@richardthombs
Copy link
Owner

Hi, I liked your video!

Regarding pings, this is what I know so far:

  • There are indeed a whole bunch of parameters that I have not yet surfaced in either the API nor the website yet. That information includes "queryEmissions" which I think describes how visible you become when you release a ping and"pingFocusAngleParams" which describe how signatures get multiplied according to the ping angle.
  • I can see that in the latest website update I'm no longer including scanner or ping information - I'll try and add those back ASAP.
  • There are several pings, all of which are tests: "test_ping", "test_ping_Prospector", "test_ping_S0" and "test_ping_S2".

I'll try to include all this info in the next update.

@richardthombs
Copy link
Owner

richardthombs commented Dec 15, 2020

You just got me digging a little deeper into scanners as well.

It seems like scanners have a SSCItemScannerComponentScanGroupFilter component which determines their performance.

  • scanRange is a property that presumably determines the range of the scanner
  • scanGroupFillter is a property that references a SSCItemScannerComponentScanGroupFilter which can filter object types

Eg, the multi-tool has a scan range of 10. Strangely, the test_scanner that all ships are given has a range of 1. Neither the Terrapin scanner nor the SCNR_TARS_S02_Resonance have got any actual scanner components inside them yet.

@voshond
Copy link
Author

voshond commented Dec 29, 2020

@richardthombs thanks for the update!
This is really interesting, sadly not very concluding

I would like to make a guide based on data:

  • which altitude is best (fo the angle?)
  • what are the "best" scanners / ships
  • at which speed to fly
  • how much ping power to use
  • how to differ between the rocks you look for
  • where to mine (from what i have been told from the sc.tools maintainer rocks off all sorts can spawn everywhere on the planet, something that i would like to show
  • how the spawning of minables work
  • how does respawn work
  • what are the "concentrations" / ususal distances between these

I noticed that the "boxes" that appear once i got a response have different sizes (small, medium, large).
the medium ones for the ROC are easy to distinguish.

thanks for having a look tho 👍

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants