10 replies to this topic

[Karasuma Akane]

The capabilities of the onboard scanner have been substantially increased. The range is now 64 AU...

What is this I don't even...

EDIT: Okay, this wording was confusing for me upon first look. It sounded to me like directional scan was being changed to 64 AU and could only be run once every ten seconds. Since I never use that other 'onboard scanner' thingy that helps you find PVE stuff...

[Gavin]

I assume that means the on-board scanner, which can currently detect anomalies at 5 AU range, will be able to detect at 64 AU range.

[Sarek Minyatar]

I assume that means the on-board scanner, which can currently detect anomalies at 5 AU range, will be able to detect at 64 AU range.

^^ that, and it only takes 10s instead of 30s to do the scan. So we don't need probe launchers on our interceptors anymore \o/. Also this scan should work while you're still holding gate cloak.

[Carenthor Loon]

Okay, this wording was confusing for me upon first look. It sounded to me like directional scan was being changed to 64 AU and could only be run once every ten seconds. Since I never use that other 'onboard scanner' thingy that helps you find PVE stuff...

Yeah, from earlier talk on the forums I thought they were going to be buffing the directional scanner.

Bear in mind that finding PVE stuff also means finding those people who are themselves doing PVE stuff... Our skirmishers generally fit a probe launcher for this exact reason, so this patch will free up a high slot quite nicely.

[Draelor]

On the other hand, you can run a probe scan while in warp, you can't use the onboard scanner to search for anoms while in warp.

[Los Lecrosis]

actually draelor that is only partially correct. you can INITIATE scan, and then warp. you simply cannot initiate it once you have started warp.

[Varrent]

I personally am loving this change, makes it easier to find the low security faction warfare missioners I love to gank so, so much. Three cheers for no more planet hopping and 20 seconds of my life saved!

[Granger]

actually draelor that is only partially correct.


you can INITIATE scan, and then warp. you simply cannot initiate it once you have started warp.

And when you come out of warp/the scan finishes, you get no result, and a message saying "You cannot do that in warp".

Tested 15 seconds ago FYI.

[Gizznitt]

actually draelor that is only partially correct.


you can INITIATE scan, and then warp. you simply cannot initiate it once you have started warp.

And when you come out of warp/the scan finishes, you get no result, and a message saying "You cannot do that in warp".

Tested 15 seconds ago FYI.

If you warp, you nullify a scan by the onboard scanner..... However, if your using probes, I'm pretty sure it doesn't nullify the scan.... (if it does, this is news to me!)

[Draelor]

It does NOT nullify a scan with probes, which was my point when I mentioned the warping bit And thank you for confirming me, Granger. You're a sexy beast amoungst sexy beasts.

[Othran]

And when you come out of warp/the scan finishes, you get no result, and a message saying "You cannot do that in warp".

Tested 15 seconds ago FYI.

The reason being of course that the onboard scanner is one of those "modules" where the "effect" is at the end of the cycle. Were it the other way around then it'd work.

<Edit> To clarify - in order to scan anything, whether it be using the onboard scanner or probes then the scanning/probing module cannot be in warp as while the cycle completes at the end, the grid location is loaded at the start and that (AFAIK) is the starting point for determining range. In addition to that if you initiate an onboard scan and leave the grid you are on before the scan completes then you will get no results (tested May 2010).