Wave Scanner Bug: how to live with it until it's fixed

Dear fellow CMDRs,

with 2.2, the wave scanner is bugged for many of us. I've seen countless of bug reports. Until it's fixed, here's some advice how I cope with it. I just need that elusive Arsenic and can't wait for the bug fix!

My hypothesis: with the announced 'improvements for visibility' of the SRV wave scanner, FDev has introduced some annoying unwanted behaviour. Instead all signals being additive, they are now exclusive. I.e.: one signal can hide the other. You can compare it with an XOR function. This can be seen in the following:
- Clear signals suddenly disappearing when you are getting closer.
- Overlapping signals changing the resulting combined signal to something that doesn't make sense any more
- Really bad are planetary POIs that are very far away. They hide basically most of your foreground signals

How do I cope: I now try separating the signal that I'm after from the other signals by changing my POV angle, so that all signals on my wave scanner are separated. That's tricky sometimes, and requires a lot of spatial 'feeling', but it's working for me now in the majority of cases

Some picture to explain:

gPBZOwI.jpg


In this picture, I move my point of view (POV, basically my SRV), so that the signals split on the wave scanner.

@FDev: I hope this helps fixing this. And I consider this a bug. So pretty please?
 
Last edited:
That isn't the only problem. There are literally ghost signals that are pointing to nothing. The wave scanner shows objects that simply do not exist. Have tested multiple times from multiple angles.

Whatever they did to the wave scanner needs to be fixed ASAP.
 
Last edited:
For me, it's easier. The audio component of the scanner doesn't seem to be affected by the ongoing bugs. Even if the audio is bugged to some degree, it's nowhere near as bad as the visual scanner. My solution: listen, don't look. I may not be able to discern the difference between meteorites and outcrops, but at least I don't waste time on the really common junk.
 
I haven't used SRV's much outside the tutorial (still haven't gotten around to messing with engineer's quite yet), and wasn't aware of this bug. Just responding to say thanks for the heads up and slight work around!
 
Yes, I too have found that "Listen don't Look" works.
But still.... fix it FD!
This far in to ED! what is going on?? (this is for Mr Braben or MB).
 
That isn't the only problem. There are literally ghost signals that are pointing to nothing. The wave scanner shows objects that simply do not exist. Have tested multiple times from multiple angles.

Whatever they did to the wave scanner needs to be fixed ASAP.

I cannot confirm any ghost signals. The rocks are scattered widely over the planet's surface, so it's next to impossibe to find them just visually (w/o wave scanner, I mean). So what you call 'ghost signals' are signals that get hidden by other, far away signals at certain angles.

- - - Updated - - -

For me, it's easier. The audio component of the scanner doesn't seem to be affected by the ongoing bugs. Even if the audio is bugged to some degree, it's nowhere near as bad as the visual scanner. My solution: listen, don't look. I may not be able to discern the difference between meteorites and outcrops, but at least I don't waste time on the really common junk.

Funnily, when trying to search for Arsenic, this 'common junk' is far more valuable that e.g. metallic meteorites. FDev also seems to have touched the spawn tables, and I have not been able to find any Arsenic in metallic meteorites in the last 5 hours. Only Polonium and Tin (and that in huge amounts).
 
What really irritates me about this bug is that it is so fundamental to just about all planetary gameplay and yet I haven't seen any acknowledgement from FDev that they are working on it. I've actually stopped playing for the time being because its just so time consuming finding anything....I mean SRV prospecting wasn't the most exciting pastime anyway but now it takes 2 or 3 times longer to find what you are looking for. I understand that things sometimes get broken when applying an update, but its been quite a while now (2 or 3 weeks??) and its still busted. For crying out loud fix it!!
 

Achilles7

Banned
The lighter the planet surface, the better! As others have said listen to the scanner..& focus on the metallic meteorite because once you find one you know there are another two nearby! I always go to turret mode & do a 360 scan of the terrain when I recognise the signal!

At the weekend I found 15 Technetium, 21 Chromium & 12 Cadmium in about 25 mins - the three mats I was looking for! Also left about 15 Antimony because I already have 34!

It is still a pain though! Get your act together Frontier!
 
The bug is worse than described. How does this theory explain the ping reducing below minimum size as you get close, then totally vanishing almost as if it were behind you ?No fixes mentioned in the 2.2.02 release notes. It still isn't worth planetary gathering unless you are a sucker for punishment.
 
The bug is worse than described. How does this theory explain the ping reducing below minimum size as you get close, then totally vanishing almost as if it were behind you ?No fixes mentioned in the 2.2.02 release notes. It still isn't worth planetary gathering unless you are a sucker for punishment.

With *ping* you mean the audio cue or the visual? If you refer to visual: if you get closer, other signal sources further away might suddenly get into range of your scanner. Especially bad are the planetary POIs: far away, it's mostly noise, but very wide angled, so it basically wipes out all closer signal sources.
 
Last edited:
For me, it's easier. The audio component of the scanner doesn't seem to be affected by the ongoing bugs. Even if the audio is bugged to some degree, it's nowhere near as bad as the visual scanner. My solution: listen, don't look. I may not be able to discern the difference between meteorites and outcrops, but at least I don't waste time on the really common junk.

I agree with the above but I have a different problem with having to rely on the audio - my hearing isn't the best and I really struggle to hear the wave scanner over the SRV engine if I go anything above 10ms (and even sometimes less).

I recently posted into the feedback/suggestions about this because although the wave scanner has it's own audio slider in the options, because it is not independent to the overall FX slider, it's only possible to turn the wave scanner down relative to the engine, and not up.
 
I agree with the above but I have a different problem with having to rely on the audio - my hearing isn't the best and I really struggle to hear the wave scanner over the SRV engine if I go anything above 10ms (and even sometimes less).

I recently posted into the feedback/suggestions about this because although the wave scanner has it's own audio slider in the options, because it is not independent to the overall FX slider, it's only possible to turn the wave scanner down relative to the engine, and not up.

This quantifies my point earlier, hearing impaired CMDRs are losing out.
 
Wow, I'd never though of that, hearing impairment!

I had said a while back (but quickly gave up with the amount of sheer vitriol returned) that it seemed more audio based, but man, I really feel for you folks with hearing impairments! what an oversight! obviously not intentional but still, I do feel for you
 
Although I too am currently relying on audio to detect what I'm trying to find, I know there are a few hearing impaired CMDRs here and I'm sympathetic for them.

This is my trouble also. I have a few frequency gaps in my hearing and regular sinus trouble that affects my hearing. While, yes, the audio scanner still works, it's a gigantic pain in the anatomy to use it.
 
I took a break for a couple months related to always being torqued about things. 2.2 out, I bought a Paintjob for my Vette, thanks there. Came back to do SRV mining to work up my engineers.

Thanks for the heads up on the wave scanner things, I thot I just was losing my mind regarding how things were behaving.

Back to the purchase boycott. Wish I could see the paintjob for the crap still on the windscreen still. Please fix the Wave scanner, I am hearing impaired, so it is either headphones at screaming volume (as engine and effects are also increased) or running buggies blind. I did tech support for several years so headsets blow chunks. A separate slider for wave scanner effects control separate over engine / other effects would save what is left of my eardrums.

See you again next year FDEV. Not going to suffer further.
 
Back
Top Bottom