I keep reading “you should always be hitting D-scan,” but in practice I am not sure what information I am actually supposed to be acting on.
For example, if I see combat probes or ships on D-scan, but they are not at my anomaly yet, what is the correct response? Do experienced players leave immediately, reposition, or wait for more confirmation?
It also feels like D-scan gives too much information without context ( ships, probes, structures ) and I’m not sure how much of it is signal versus noise. Is the real skill just pattern recognition over time, or are there specific “this means you’re about to die” indicators that players usually miss?
I guess what I am asking: is D-scan more about reaction speed, interpretation, or just habit, and which one should a player focus on first?
Combat Probes on DScan are a strong warning, so if you don’t bait or wait for a fight, you should get into cloak on a safespot.
Any ship on DScan is information. But of course you have to interprete what to do - some are just travelling, others look for easy prey, and there’s baiting of course, they want you to to see them and encourage engagement.
There’s many use cases for Dscan, you can check if a gate is clear to travel, if someone is scanning in your system or even if an event site is already occupied.
Depends on where you are and what you’re doing. Mostly you’re looking for what doesn’t belong there. For example, wormhole corps have their people put specific symbols into their ship names, so they know at a glance if something shouldn’t be there. This is more difficult in highsec, but if you’re mining and you see Catalysts on short d-scan, something’s up.
Most pre-made overview settings have multiple presets for d-scan, use them if you have them available. If you use your own overview settings, setup a few saved tab custom presets to limit the information overload will help a lot. Change which overview tab setting you use with the drop-down menu in the upper right corner of the d-scan window.
A couple basic things to look for.
When you’re doing sites that have gates to enter them, like FW or DED sites, you can look down the gate, shorten the range to minimum, and see if anyone’s in it before going in. Also will let you know when someone is potentially on the gate and coming into your site.
If you see combat probes on the max scan, shorten to 1 AU. When you see all 8 combat probes on d-scan again, whoever was looking for you is in warp to your location, and you’d better be moving already if you’re not in a gated site. You’re about to have a visitor.
You can make filters for dscan like for the overview and filter out results that are noise for your current activity.
My defensive dscan has:
- ships
- probes
- bubbles (both anchored and launched)
In other words, anything that could pose a threat. So no structures, NPCs, wrecks etc.
On the other hand when you’re trying to hunt a certain NPC it can help to make a dscan filter with also that NPC type visible. Or a dscan filter that shows nothing but that NPC type to minimize noise.
Or if you’re trying to find MTUs to kill, put those on a separate dscxn filter.
Or wrecks can be a nice indication someone is or recently was ratting there and if the site is still active, someone may be warping back there to continue once you leave system so you could get out, jump back in and warp straight to that site if you’re hunting players.
Dscan are your eyes and how you use your eyes is up to you and depends on your role, your threats and what you’re looking for.
Regardless of your current role it helps to get used to dscan your surroundings as practice and to get a feeling for what is happening in system with you.
Depends.
If I’m in null, non-allied players are in local and I’m not looking for a fight with them I’d be getting safe even before seeing those probes.
If I’m at a site they cannot warp straight at, like an escalation, then I’m pretty safe at least until combat probes are launched, which are the signal to cloak up and/or start warping to a safe to not give them access to my site.
Combat probes or hostile ships on dscan generally are a sign to get away.
Everyone claims D-Scan is the best thing since WD-40. I seldom use it in the way I play this game. Please understand the following is from the perspective of a miner and not a PvPer.
When I enter my mining system, I look at local chat. If no one is here, what is the point of scanning? Otherwise I head to my safe point and get to looking for gas clouds. If I find a gas cloud, I need to be within 14 AU to scan it for ships. Narrow the scan and point the camera ( not the ship ) at the cloud. Nothing found? Warp in and get to mining.
People put too much faith in D-Scan, it can be easily avoided by certain warships. I could get there to find some covert ship cloaked inside the cloud. Let’s assuming I find no one and get to mining. Hopefully the gate and stations are greater then 14 AU. If not point the camera at the gate and watch local chat for new arrivals. Press D-Scan, I can see what ship they are flying.
Scanning for combat probes is a problem too. They can launch them out to the 32 AU distance and you won’t see them. Paying far too much attention to D-Scan will just get you blown apart. It is a tool better used to peak ahead of warp to point. If I were hunting ships, I would use the normal core probes to find all the anomalies, Then a narrow scan on each to find the ships I want to explode. You would never see combat probes in that scenario.
Pounding D-Scan is a waste of time. The tool works but has serious limitations. Remember the directional beam is where the camera is pointed.
Mine Safe ![]()
This, ladies and gentlemen, is why you never listen to miners in Eve, unless you’re asking a question about mining. They literally know nothing about the game, outside their tiny little bubble of risk aversion.
You’ll see me in local but not on D-Scan because I’m probably in a Rook, scouting.
Dscan is always useful. Before you go outside you check for the weather. The temperature, the wind, rain, hurricane, whatever is pertinent. Dscan is the equivalent of that. But if you’re the type who prefers to wear shorts in a snowstorm, then it’s not for you.
That’s why you filter irrelevant stuff out. There is no ‘noise’ in the results if you use it right.