About 90% of the time, when I'm flying around in a mission scanning for anomalies, it will tell me something like "there are 4 anomalies in the area", but the beam that's supposed to point to the closest anomaly points way off past the edge of the zone.
Could you pretty please code it so that the scanner ignores "unreachable" anomalies in it's count?
About 90% of the time, when I'm flying around in a mission scanning for anomalies, it will tell me something like "there are 4 anomalies in the area", but the beam that's supposed to point to the closest anomaly points way off past the edge of the zone.
Could you pretty please code it so that the scanner ignores "unreachable" anomalies in it's count?
This usually only happens on those multi-part mission where you might jump into one instance and then have to go to a second as a continuation. One in particular is the one where you provide delithium crystals to the USS Valor. I think it is 2 or three are in the first instance and two more in the next which can show up on your scan. It isn't a HUGE issue as far as I am concerned. I would suggest you just BUG it and Cryptic will fix it when time permits.
Comments
This usually only happens on those multi-part mission where you might jump into one instance and then have to go to a second as a continuation. One in particular is the one where you provide delithium crystals to the USS Valor. I think it is 2 or three are in the first instance and two more in the next which can show up on your scan. It isn't a HUGE issue as far as I am concerned. I would suggest you just BUG it and Cryptic will fix it when time permits.