These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE New Citizens Q&A

 
  • Topic is locked indefinitely.
Previous page12
 

scan a ship out of 14.3 direct scan range

First post
Author
Cara Forelli
State War Academy
Caldari State
#21 - 2016-01-21 02:15:36 UTC
Sabriz Adoudel wrote:
IIRC D-scan has a 6 second cooldown and probing can be brought down to 7.5 seconds plus the time the probes are in warp. So the advantage is with the person running the mission, but it is very small.

D-scan cooldown is quite a bit lower than 6 seconds. It does look like the "recalibrating" message stays on-screen for about 6 seconds though.

Still pretty easy to miss a skilled prober unless you are a D-scan addict.

Want to talk? Join my channel in game: House Forelli

Titan's Lament

Fat Buddah
Federal Navy Academy
Gallente Federation
#22 - 2016-01-21 04:37:26 UTC
another possibility is that you were d-scanning with a wrong filter.
Blood Flint
Hedion University
Amarr Empire
#23 - 2016-01-21 12:44:03 UTC
no, the filter was right, i have special for that with NPCs and probes just.
well, it's clear now, i need to make an experiment with myself and try to scan me with an alt Smile
Donnachadh
United Allegiance of Undesirables
#24 - 2016-01-21 15:54:09 UTC
Ralph King-Griffin wrote:
as memphis said, this was a killed prober who figured out roughly where you were and hit you with one pass of probes
if done correctly the probes are only in space for a couple of seconds.

Not to pick on Ralph specifically he just offers a good place to start with my thoughts.
I hear these magical claims of probes being visible on D-Scan for a second or two all the time and all of them fail miserably at accounting for the realities of the scan mechanics. So here are some basics that anyone can check by doing the relative math.

Minimum scan cycle possible using the best of everything last time I calculated it was around 5 to 6 seconds so the probes are visible on D-Scan for at least that long.

Travel time to the scan location and then back to the ship, or off grid will add an additional 2-4 seconds to that and the probes are visible while they are traveling to and from.

So we have a window of roughly 7-10 seconds where the probes will be visible. In theory there are some specific cases where travel time for the probes could be reduced and that would shorten the time they are visible by maybe another second, so worst case for you the target is that you would have about 6-8 seconds where the probes were visible.
Ralph King-Griffin
New Eden Tech Support
#25 - 2016-01-21 17:21:15 UTC
Donnachadh wrote:
Ralph King-Griffin wrote:
as memphis said, this was a killed prober who figured out roughly where you were and hit you with one pass of probes
if done correctly the probes are only in space for a couple of seconds.

Not to pick on Ralph specifically he just offers a good place to start with my thoughts.
I hear these magical claims of probes being visible on D-Scan for a second or two all the time and all of them fail miserably at accounting for the realities of the scan mechanics. So here are some basics that anyone can check by doing the relative math.

Minimum scan cycle possible using the best of everything last time I calculated it was around 5 to 6 seconds so the probes are visible on D-Scan for at least that long.

Travel time to the scan location and then back to the ship, or off grid will add an additional 2-4 seconds to that and the probes are visible while they are traveling to and from.

So we have a window of roughly 7-10 seconds where the probes will be visible. In theory there are some specific cases where travel time for the probes could be reduced and that would shorten the time they are visible by maybe another second, so worst case for you the target is that you would have about 6-8 seconds where the probes were visible.

6-10 secons is what i would class a a couple of seconds, granted it's not a literal couple but its still i minute amount of time to catch on there is a bloodthirsty savaged about to descend upon you

Bumblefck
Kerensky Initiatives
#26 - 2016-01-21 19:08:36 UTC
I laugh my little socks off when people scan me down in low sec when I run Burner missions, only to be either I) confronted with an acceleration gate that they can't operate or, if they can fit through it, II) when the Burner targets them and blasts them to smithereens

Perfection is a dish best served like wasabi .

Bumble's Space Log

ISD Fractal
ISD Community Communications Liaisons
ISD Alliance
#27 - 2016-01-22 15:51:55 UTC
I find 6-10 seconds is easy to lose track of when you're running a PvE site. You start targeting some NPCs, start moving towards whoever, drop your MTU, turn on your stuff and next thing you know 10 seconds have passed.

ISD Fractal

Lieutenant

Community Communication Liaisons (CCLs)

Interstellar Services Department

Donnachadh
United Allegiance of Undesirables
#28 - 2016-01-23 15:16:51 UTC
Ralph King-Griffin wrote:
6-10 secons is what i would class a a couple of seconds, granted it's not a literal couple but its still i minute amount of time to catch on there is a bloodthirsty savaged about to descend upon you

So true.
I deal with new players a lot and they hear or read these 1 or 2 second claims and because they do not know better they actually believe them. It was simply my intent to clarify the situation with something that resembles a real in game possibility istead of fiction.

ISD Fractal wrote:
I find 6-10 seconds is easy to lose track of when you're running a PvE site. You start targeting some NPCs, start moving towards whoever, drop your MTU, turn on your stuff and next thing you know 10 seconds have passed.

Thank you for posting this it is a component of my thoughts that never made it into my post.
Previous page12