Test Server Feedback

Agreed, but to know the strenght of a sig you should have probes out. Know the strenght without probes doesn't sound right.

Ok, I'll asume that th DS is a DSP. I don't agree that you should know what type of sig is without core probes or combats. It makes things easier. I dont like it as it screw a couple of mechanics in wspace. With the rest I
dont have an issue.

Its like serving your meal already digested.

Are we using the same Discovery Scanner? Things either show up as warpable green anoms just like they did with the old Onboard Scanner (or a single scan pass of a DSP) or they show up as red gibberish-named "Cosmic Signals" that don't tell you what type they are until you deploy probes and scan them to at least 25%.

Maybe the difficulty here is in what "Anoms" and "Sigs" are defined as.

"Guristas Forsaken Hub" is an Anom. You should absolutely see the name of that, because they always come up as 100% green and warpable.

"Serpentis Data Fortress" is a Data-type Cosmic Sig. You should see it come up via Discovery Scanner as a red bracket in space that just tells you the signature ID (Ex: QOV-361) and the distance (23.4 AU) and the base signal strength (8%), where only probing can reveal what type it is (Data) at 25% and finally the name at 75%.


That's the Discovery Scanner I've been using. As for myself, I've never seen it tell me what type of site it is (Data, Relic, Combat) without probes.

It wont tell you the name or what site, but if you have the scanning window up it will show you the base str instantly. What the issue is for one there is no delay when entering in the system and knowing what is in the system(there should be a 5-10sec delay similar to the visual aspect). Also the base str from the overlay can be used to determine what type of site it is. Now if the last part is intended or not is up in the air, since it gives a similar ability that DSP gives(even though CCP said they wanted to remove that) just now without the skill req.

Also the overlay gives a dotted readout on sigs when in the solar system map, which should only be possible with triangulation. Not sure if that is intended or not, since it should be a bubble(single probe hit). The deviation is about the same as a bubble so it's a bit deceiving.

You are making me very happy with what are you saying. Though I remember seeing it, could be the day that they broke it with a patch and overlay was messy. I have no problems with the overlay as it is then.



I could also drop a probe as soon as I enter the system and get the same effect. But is a double-edge sword. You could enter a system and know how many sigs are if you are a hunter which is helpful. Instead, if you are doing sig-watch, you know when a new sig appears.

Yeah, would like to know if that's intentional or still a bug. Even with the overlay sweeping, the list doesn't update when there is a new sig unless you change your filters to something and back.

Hey everyone,

I've been meaning to catch up with this thread for a while, but I went on vacation for a week the day after it was posted, and didn't manage to make time last week to sit down and have a nice long read

What's on SiSi now is (unsurprisingly) pretty close to being final, and it's been nice to see reading through this thread that at least some of the initial concerns have been resolved. Some of those we even planned to do all along The one remaining substantial change is that, as Masterplan just mentioned, we're always initially setting the "signal strength %" in the tooltip to either 0% (signatures) or 100% (anomalies).

This achieves two things. Firstly, we remove the confusion caused by the initial probe scan on higher-strength sites invariably resulting in a signal strength decrease, which is ugly and unintuitive. Secondly, it allows us to claw back some of the efficiency gains inherent in the new system.

Clearly, this makes the sort of DSP look-up tables that advanced explorers are used to somewhat more difficult to leverage, as there's no longer a handily-exposed variable for this (the information can still be largely derived from the [clamped] range deviation visible in the tooltip, but you'll have to do a bit of math in your head to figure it out). The new "spread formation" allows this to be somewhat mitigated by acting as a poor man's DSP, but it's nevertheless a reduction in available information at this specific stage of the process. Given the efficiency gains elsewhere, though, we're of the belief that this shouldn't, in practice significantly disadvantage probers relative to the current TQ system.


There are some elements of the feedback to date that we're not currently planning to address.

The first is the impact on wormhole intel. Obviously this is a change to the status quo, but it's still not obviously a particularly destructive one. The intel that this system provides can already be obtained by launching a bunch of probes and regularly mashing "scan", and we're not huge fans of systems that require tedious and repetitive manual busy work (yes, the d-scanner, we know), so on the face of it we regard this as a straight-up improvement. We are of course waiting to see how this pans out in practice, and if it ends up making wormhole space materially less interesting, we'll make changes. We'd like to give the more creative members of the community the chance to play around with it in a live environment before jumping the gun, though.

The second is the jump-in scan and lack of options surrounding it. There'll hopefully be a blog on this feature soon that goes into more detail, but a major part of the feature brief was to find a way to make exploration possibilities more naturally visible to players of all ages (including new ones, obviously). The jump-in scan is one of the main ways we're hoping to meet that goal, by opening a permanent window into the hidden world of EVE. We're also, as a general goal, trying to gently cut back on the number of options that we expose in the client, both because it allows us to spend our "user complexity budget" more efficiently and because it's expensive in terms of development and maintenance. Our goal, rather, is to tune and target the jump-in scan so that it becomes a natural part of the jump sequence, rather than some outlandish imposition. We're going to be evaluating its intrusiveness on an ongoing basis both prior to and after release, to try and ensure that we hit that goal.

(Frellicus is also trying to find time to make the always-on sweep more intermittent, but it's not clear yet whether that'll make it in prior to release.)


Finally, there's obviously a lot of other things that seem like reasonable fits to show up in the overlay (bookmarks, mission locations, the directional scanner...), and we have sketch plans for various extensions to the feature in the future that may or may not see the light of day. If it gets expanded significantly we may even need to invest in some more robust filtering options.


If anyone has any outstanding questions not covered here, please ask

-Greyscale

So am I understanding this correctly? The greatness that is currently on sisi where the base signal strength shows up in the scanner window is going away. However, that information is still going to be available by hovering over the in space icons? If so I am so sad now. I was tired of getting dizzy spinning my camera around to exclude signatures I didn't want to scan down and it was such a relief when that information was put is an easy and accessible place. What is the point of making the information less accessible?

Still curious if it's a bug or feature that the list doesn't update until you change your filter settings. It's been repeated that the intel is instant, but it's not instant if the window doesn't update.
Example: stomp your WH static, and the old sig stays on the list, and the new one doesn't show up. once you switch your filter to something else, then back, the list populates correctly.