EVE Information Portal

Impossible to d-scan now: can't delete the number in range window, and if you do it is impossible to type a new one. V button does not work if you have your cursor in the number window...broken beyond repair.

CCP:

Patch 119.3, release 1.3, seems to have not only affected the nebula lighting, but also the lighting on ships.

They seem to be darker again. When I logged in yesterday, my ship was very well lit and looked amazing. Today, it seems the lighting values have reverted to their previous, very dark setting.

Is there any way you could reset the values? Alternatively, is there a Gamma setting somewhere in the Graphics tab which I have not been able to find?

well i'm not a fan of the new dscan because it changed the scan button to the bottom and then switched its side which is fine and i will get used to it but i think it would be cool where you could change where the buttons are so it could be more customization. another thing that bothers me is the fact that it has a noise that comes with it that isn't so great in my opinion and id like a way to turn it off without turning any of the other sounds off(unless i missed something in the sound menu because i couldnt find a specific turn off dscan sound). though it has some things i didn't like i do love the fact that it has the ship sign so you know if its a frigate or a titan just if you don't know off the top of your head which is super useful plus you can plug the map right in with it which is also super cool and useful but i just wanted to write this as my opinion on it. hopefully the devs look at this ^^

fly safe

nate albush o7

This, please. It's not a game breaker but it's definitely a pain.

Gong. Delete. NOW. Thanks.

As a player who enjoy exploration the most I would like to post my feedback on recent probeing/dscan changes:

1) Please create a new sound category for the newly added probing/dscan sounds so those who doesn't like them can disable them in sound advanced settings without disabling other sounds in UI Interaction category.

2) gong sound is quite annoying and should be removed. Removed, because I think a lot of players including me don't mine other sounds of the new update and dislike only the dscan "gong" sound. Also it seems to me that there is secondary sound that is played at the end of d-scan - this sound should be completely sufficient for some kind of d-scan feedback in my opinion.

3) I often have low fps when I try to move the probes on solar map. Not everytime, but very often. It usually gets self-fixed when the window is open longer but its very annoying to work with when the position indicator is jumping because I have 5 fps.

4) Sometimes, especially when the probe AU is 16 and more when I double click on a signature it won't make the circle around it. Happens randomly it seems, but happens.

5) In old probing system, double-clicking on signature temporarily removed all others from solar map. This wasn't bad idea, why it got removed? I'm not sure it so much needed now as the circle around the signature is enough to choose the right one but perhaps the multiple signatures and their visuals are what causing low fps?

Overall good work. I like that npc ships now shows as NPC and MTU and Depot as Deployables so its easier to find them in all of the structure mess. It also make easier to find drones. Scanning now takes a bit longer as there seems to be some addiional delay but thanks to other changes probing something is still faster than under old system. And this delay adds a window to avoid getting combat-scan ganked.


One extra request for further probing changes: please either reset the probes position when changing a sector to 0,0 (ie sun) automatically or create a button which will do this (which would be even better I suppose as it could then be used to quickly reset probe position in further scanning). This is annoying especially if you are scanning very large system which means that in next system probe position is completely off in dead space and I have to manually reposition it to sun where is usually the highest concentration of signatures.

I saw something about this being fixed in the patch notes. And even if it isn't 100% fixed, I can tell you it's not quite impossible to type a new range in, just difficult. For instance, I tend to use 0.2 AU as my default and as that isn't on the slider, I have to type 0.2 once I'm done scanning at various ranges. Because of last week's patch, typing 0.2 left the range reading "0.0" instead.... If you type 0.2 (or whatever) and then hit the left arrow and then type the 2 again, 0.2 will be restored, however.

It's the "." throwing things off. I guess a coder forgot we might be typical a decimal in the range slot...



I've been doing a lot of combat probe scanning (mostly of lost drones, but ofc some ships as well when it turned out the drones were still active) since the patch day, and I haven't been noticing the 15 second delay before the usual 8 second scan you mention. Your 15 second delay may be indicative of some major lag issues particular to your client. Bug report that, yo.



I'm guessing you have Post Processing on. They've been fiddling with a bit in the past few patches, if your lighting levels are increasing and then decreasing again due to patches, I'll bet it's due to PP.

Try setting it to none.

Improves so much (including turning off horrible sansha incursion visual effect blandness in all 4 empires blotting out the natural beauty of space).

So I have a very weird Dscan behavior now. Sorry if I describe this badly.

Before the patch I had my Dscan set up to move the camera (and scan cone) when I used my Dscan hotkey after selecting an object in the overview (so the Dscan angle would scan that object). After the patch this only works very randomly now. I tried to fill out an in game bug report but it crashed while filling it out (I'll try one again). I managed to get a video of it happening but I'm not sure how to get that to a Dev.

Edit: And my bug report was just 'closed' so I don't know if this random behavior is actually a bug or me doing something wrong.

is there a fix for the launcher?

The dscan and scanning tool continues to feel like s*** to use.

Please fix/revert.