Build: 3376 Mode: Survival SERVER NAME: N/A SEED-ID: N/A If applicable: MODIFIED PLAYFIELDS: N/A Reproducibility: Always Severity: Trivial Type: POI detection Summary: Detector ranges not matching infocards Description: The Current Range does not seem to match the different detectors infocards. While flying around a planet in a CV I must get within 0.4 mi for the CV to identify an ore deposit. According to the info card the "Current Range" for a CV detector should be 3.73 mi I am seeing this with the HV's 1.55 mi and SV's 2.17 mi Current Range as well, I have to get within 0.2 mi in an SV while on a planet for it to identify an ore deposit. I am playing the game with the Imperial system of measurement enabled, but changing it to Metric does not seem to effect the issue. The Max range does not seem to be effected, only how close you have to get to identify a POI. Steps to Reproduce: Play the game
Think it like the range of the guns. Max range is not the same as shooting range. The range is set to show the player that there is something within the area of coverage. The Discovery Factor i.e. 0.4xMaxRange in specific playfield type, is the value that identifies the previously entity. I would like for convenience reasons, to have discovery range shown per playfield at least in GUI when selecting the detector. Like with guns we have this already. So TLDR there are two values and only the one is shown in the properties of all detectors, the range. The other one is internal. For RP reasons I think discovery value should be variable affected i.e. by atmospheric interference weather and electromagnetic in area. Just my idea.
This is intended as there is a range that a detector can identify a POI and that range is different than the maximum scanning range. I think it even lists this range on the tooltip.
The max range is shown. The current, per playfield, range is shown. Both twice for some reason.But not the detection or if you like the discovery range (not the factor), this is not shown. So I think it is kind of misleading for new players at least.
Beware - he is using the US-System. Therefore Miles instead of Meters. It could well be the case that some Calculations are not right there because of this difference. So lets wait and hear what the Moderators have to say.
He obviously referring to this : See market in photo of ItemsConfig. He clearly typed about the 0.4 close to the entity to detect it. For SV it is set default to 0.12 the maximum detection range.
Ah then it's not shown. What needs to be changed is the discovery range factor should also be shown in the tool tip so it's clear how close you have to be.
I was going by the infocard information on planet when I posted this. Handheld : current .4 mi, max .78 mi HV : current 1.55 mi, max 6.21 mi SV : current 2.17 mi, max 8.7 mi CV : current 3.73 mi, max 14.91 mi But I think that the thing that was annoying me the most was having got get within .2 mi to identify a mining deposit in a SV. You are almost right on top of it. I guess the part that got me thinking it was a bug was that the planetary range for the handheld is .4 mi and I had to get within .4 mi to identify a mining deposit in a CV. Which led me to think that the CV's identification range was the same as the handheld scanner. I guess this was just me complaining that you basically have to get right on top of a POI in order to identify it. I will withdraw the bug report, because this qualifies more as a request to adjust the identification range.
