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

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

Test Server Feedback

 
  • Topic is locked indefinitely.
 

Issues scanning down wormholes?
Author
Previous Topic Next Topic
BeanBagKing
The Order of Atlas
#1 - 2014-03-27 21:38:31 UTC
Besides the fact that they are just hard to find....

I get them to a certain percentage, and then they go to 0% and it tells me nothing is found. The signature is still there in my scanner window, it's not being filtered out.

I made a video: https://www.youtube.com/watch?v=r3N5NCNfN80

Am I just doing something crazy weird/wrong? I scan wormholes every day, but I don't know how old the SISI mirror is right now so maybe I have some old settings? Skills are the usual 5/4/4/4 you can see the fit (except the 2x gravity capacitor rigs).

Bug report has been opened, but I figured some more eyes on this might tell me if something on SISI is broken since most people don't scan on the test server.
Ronald Jeremiah
Doomheim
#2 - 2014-03-28 02:15:39 UTC
Yeah... I'm having the same issues on both my characters at the moment, one with near perfect scanning skills and the other with somewhat questionable skills - enough to find their way out but not in a hurry sort of thing.

I get most sigs to around 50 - 60% and adjust the probes accordingly once I hit scan again I get the message 'No signatures detected' I readjust the probes back out a level and end up with the 50 - 60% thing again. The closest I have come so far to scanning something down is 91% and that's it.

I tried scanning on wormholes, gas and data/relic sites and ended up with the same issues.
BeanBagKing
The Order of Atlas
#3 - 2014-03-28 04:04:04 UTC
I hope they fix it before rolling anything out live, it would put quite a dent in our wormhole life...
BeanBagKing
The Order of Atlas
#4 - 2014-03-28 14:26:25 UTC  |  Edited by: BeanBagKing
Tried it again this morning and it seems to work.

http://i.imgur.com/2jNWpEf.png

Edit: Is there a way to amend bug reports created in game?
Sable Moran
Moran Light Industries
#5 - 2014-03-28 16:50:55 UTC
This has already been dealt with in a thread (includes a dev post) a few rows down the page: https://forums.eveonline.com/default.aspx?g=posts&t=328895

Sable's Ammo Shop at Alentene V - Moon 4 - Duvolle Labs Factory. Hybrid charges, Projectile ammo, Missiles, Drones, Ships, Need'em? We have'em, at affordable prices. Pop in at our Ammo Shop in sunny Alentene.
BeanBagKing
The Order of Atlas
#6 - 2014-03-28 19:33:27 UTC  |  Edited by: BeanBagKing
Sable Moran wrote:
This has already been dealt with in a thread (includes a dev post) a few rows down the page: https://forums.eveonline.com/default.aspx?g=posts&t=328895

No, it hadn't. Read posts before responding to them, even the title gives away that it's a separate issue.

The issue he is having is finding one, period. The issue I was having (which is fixed now, as noted above) was that once one was found (and I did find them) they were impossible to scan down. Two very different things. Once is a result of the test server not having people spawn the k162 exits. The other is the result of a bug that won't allow a signature to be completely scanned down. i.e. I can find it, I can't warp to it.
Darkblad
Doomheim
#7 - 2014-03-28 22:19:53 UTC
BeanBagKing wrote:
Edit: Is there a way to amend bug reports created in game?
There isn't, unfortunately. The "new" Bug reporting system is nice and shiny but lacks the option to edit anything (from the creator's side) once submitted.

The issue with Signatures changing to 0 % signal strength once scanned down to a certain degree exists on TQ also, and isn't limited to wormholes. Let's hope, the devs will get their hands on that one in time.

NPE – ISD – RIP
Ronald Jeremiah
Doomheim
#8 - 2014-03-28 23:46:52 UTC  |  Edited by: Ronald Jeremiah
Darkblad wrote:

The issue with Signatures changing to 0 % signal strength once scanned down to a certain degree exists on TQ also, and isn't limited to wormholes. Let's hope, the devs will get their hands on that one in time.


I've never experienced it on TQ (not to say that it doesn't happen as I'm sure it does) but I can happily confirm that scanning is now working as intended on the TS.