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.
 

Little things in Rubicon 1.3

First post
Author
Previous Topic Next Topic
Edward Olmops
Gunboat Commando
#81 - 2014-02-28 14:06:28 UTC
CCP karkur wrote:

Edward Olmops wrote:
The D-Scan changes are certainly cool.
But in terms of usability... would it be possible to make the buttons on the range/angle rulers a bit bigger?
I always have trouble grabbing them quick enough.
(they are about the same size as the overheat rack buttons and everyone agreed those are too small)
To be honest, we don't really have the space for it. However, when you click on the slider, the handle will move there... or to the closest option (you see where it will land when you mouse over it because the tick lights up a little bit)


Ok... that in combination with the even increments sounds like a good solution.
Chris Roberts
Mind Games.
Suddenly Spaceships.
#82 - 2014-02-28 14:56:26 UTC
All seesms good. One little bit of negative feedback though. On the new fitting info window the calibration bar is white text on a white back ground and is very hard to see. Could we get the text changed to a different colour?
Jinn Aideron
#83 - 2014-02-28 15:53:34 UTC
Finally had time to go over all the shiny new DScan goodness en detail. Thanks to CCP Merc and CCP karkur I'm one happy scanning capsuleer now.

Praise:
  • slider markers light-up on hover, smart!
  • handle isn't fully opaque, good change!
  • different sized markers for boundaries and interim steps, visually appealing twist
  • reshuffled elements so slider views stack aligned - the above.
  • former tooltip degrees readout moved into permanently visible label, practical.
  • opting for 1 decimal in AU field, not 2, seems to be accuracy/usability sweetspot, yay!
  • ❤ Mousewheel + AU input field is all I ever hoped for! Fine-grained and quick control of range! ❤ You rock. ❤

---
The following is in direct response to OP feedback request. I'm indifferent to all the observations below, but see this list as a sign of appreciation, honoring aforementioned request, for the responsible parties to think on or discard at will.

  • Slider handle's mouse-sensitive area extends beyond visuals-enclosing rectangle; specifically a large amount to the left. One consequence is obstructing selection of 0.0 AU on the slider when currently at 1.0 AU.
  • Slider handle image isn't centered over slider markers. (Nobody cares that it isn't! :) But might be in cahoots with above item. So, there.)
  • Scan button not trailing, but right-aligned.
  • Angle slider change triggers auto-execute scan, range slider does not.
  • Max selectable range in slider/and AU field effectively smaller than max selectable range via text input in km.

And this last item, which is at least somewhat interesting: There are some funny turnouts when entering numbers directly into the AU field.
  • entered (shown) > converted-to km value
  • ,1 (0,1) > 14.595.787
  • ,149 (0,1) > 14.959.787
  • ,15 (0,2) > 14.959.787
  • ,151(0,2) > 29.919.574
  • ,155(0,2) > 29.919.574
  • ,2 (0,2) > 29.919.574

So, while the texfield will allow you to enter up to 5(?) chars, and retains your original input for more than 1 decimal, rounding applies before conversion into km. (Which isn't immediately obvious bc of the retention of original input.) But with input of ,15 the formatting field rounds up and displays 0,2, while the km value still derives from 0,1*(1AU). (Another weird example, 1,45 vs 1,46.)
Then there is also the immediate-update parser not including last entered char, but everything up till last entered instead.

Maybe three views for the same modeled value carries too many constraints? (0.0 in slider, conversion, rounding.) I wouldn't know... that's really your area. :)
---

Now, I feel perfectly terrible for listing these because I dearly, dearly love everything the new DScan panel is. I want to make a stuffed animal from it and take it everywhere I go! Big smile

From where I stand, the DScan as is on Sisi at time of writing/testing can remain untouched and would deliver a VAST improvement over TQ DScan in every relevant way. Thank you again, for having spent time on this change!

Stealth deletes are bad.
CCP karkur
C C P
C C P Alliance
#84 - 2014-02-28 16:07:27 UTC
Jinn Aideron wrote:
Now, I feel perfectly terrible for listing these because I dearly, dearly love everything the new DScan panel is. I want to make a stuffed animal from it and take it everywhere I go! Big smile

From where I stand, the DScan as is on Sisi at time of writing/testing can remain untouched and would deliver a VAST improvement over TQ DScan in every relevant way. Thank you again, for having spent time on this change!
Thank you for the kind wordsBig smile
Please don't feel terrible! These are great points, and I will go over them and make sure things are the way we want them to be Smile

In the original post I mentioned that the "Entering numbers in the AU field in D-scan is a bit broken", so I believe that's the issue in your last point. I have already fixed it(this is fallout from some last minute change I made before checking it in), but i'm not sure when Sisi will be updated with the fix. If it's still the case when using the mousewheel to select those AU numbers, then we have another issueP
The max value of the KM field is set to be 14.3 AU, so I would find it strange if it was higher than the slider or the AU field, but i'll make sure I set it correctly

CCP karkur | Programmer | Team Five 0 | @CCP_karkur
Jinn Aideron
#85 - 2014-02-28 16:16:13 UTC  |  Edited by: Jinn Aideron
hydraSlav wrote:
On the new DScan, when you set input to the AU field, you can use the scroll wheel to adjust it, however it goes in 0.1 intervals.... so this can take a while.
Vary your speed! Slow mousewheel change vs fast one. Smile

Domanique Altares wrote:
The field for 'AU' is a text entry field. I don't know if this is intended, or not.
It's intended. And in combination with the mousewheel up/down very powerful. Keep in mind that speed of the mousewheel 'flip' affects how quickly the value steps up or down! So one has even more control, and can adjust slowly to be exact, or all-out spin the wheel for go quickly up or down.

Stealth deletes are bad.
Jinn Aideron
#86 - 2014-02-28 16:23:13 UTC
CCP karkur wrote:
Please don't feel terrible! ... Smile
Thanks for easing my conscience. You guys are the best! Big smile

CCP karkur wrote:
The max value of the KM field is set to be 14.3 AU, so I would find it strange if it was higher than the slider or the AU field, but i'll make sure I set it correctly
I believe it could be because
Quote:
(2^31 -1)km / 1 AU = 14.355 > 14.3

Stealth deletes are bad.
CCP karkur
C C P
C C P Alliance
#87 - 2014-02-28 16:34:10 UTC
Jinn Aideron wrote:
CCP karkur wrote:
Please don't feel terrible! ... Smile
Thanks for easing my conscience. You guys are the best! Big smile

CCP karkur wrote:
The max value of the KM field is set to be 14.3 AU, so I would find it strange if it was higher than the slider or the AU field, but i'll make sure I set it correctly
I believe it could be because
Quote:
(2^31 -1)km / 1 AU = 14.355 > 14.3
that was the case before, but now the km field should literally be maxed at 14.3 * 149598... no longer the max int Smile

CCP karkur | Programmer | Team Five 0 | @CCP_karkur
Valterra Craven
#88 - 2014-02-28 16:51:50 UTC
CCP karkur,

I don't know if you guys are aware of this, but when mousing over systems and getting a list of objects (such as asteroid belts and stations) in the map, there's really weird lag time and sometimes fields will display at once when only one should display.

For example a system I want to look at has two NPC stations and in the menu you can look at what these stations have. Sometimes you mouse over one and nothing comes up, then you mouse to another and it comes up fine, but then all of a sudden the other station comes up and they overlap now! This is very frustrating. Also sometimes the menus seem to "timeout" really fast or seem to misunderstand that I don't want it to go away yet. Any chances on you looking at that?
Jinn Aideron
#89 - 2014-02-28 17:15:24 UTC  |  Edited by: Jinn Aideron
CCP karkur wrote:
that was the case before, but now the km field should literally be maxed at 14.3 * 149598... no longer the max int Smile
*returns from quick visit to Sisi w/ a clarification* ;)

It is true that you cannot exceed the km field by slider or entering AU directly. But you can do this (steps to reproduce):

  1. Max out slider
  2. Enter a leading 9 into the km textfield
  3. Remove keyboard focus from km textfield
  4. Fallback mechanism caps at 2^31-1, with traditional warning sound

Now, if this ~8m km higher value for range later takes effect in the scan, I couldn't not verify, because I could not readily find anything to scan for at just the right distance D, 2.139.249.551 km < D < 2.147.483.647 km. :)

Stealth deletes are bad.
CCP karkur
C C P
C C P Alliance
#90 - 2014-02-28 17:45:38 UTC
Jinn Aideron wrote:
CCP karkur wrote:
that was the case before, but now the km field should literally be maxed at 14.3 * 149598... no longer the max int Smile
*returns from quick visit to Sisi w/ a clarification* ;)

It is true that you cannot exceed the km field by slider or entering AU directly. But you can do this (steps to reproduce):

  1. Max out slider
  2. Enter a leading 9 into the km textfield
  3. Remove keyboard focus from km textfield
  4. Fallback mechanism caps at 2^31-1, with traditional warning sound

Now, if this ~8m km higher value for range later takes effect in the scan, I couldn't not verify, because I could not readily find anything to scan for at just the right distance D, 2.139.249.551 km < D < 2.147.483.647 km. :)

Thank youSmile You're absolutely correct... I was setting the max value to m instead of km so it was way too high and capped at max int, will fix Smile

CCP karkur | Programmer | Team Five 0 | @CCP_karkur
Jinn Aideron
#91 - 2014-02-28 18:15:07 UTC
\o/ Yay! Yw, and in return thanks for allowing a nitty-gritty impl detail shine through to this curious party. Smile I hope you'll have a wonderful week-end off! Take care.

Stealth deletes are bad.
Galphii
Caldari Provisions
Caldari State
#92 - 2014-03-01 03:31:28 UTC
Finally fixing the D-scan, I can scarcely believe it. Woohoo!

"Wow, that internet argument completely changed my fundamental belief system," said no one, ever.
Rowells
Blackwater USA Inc.
Pandemic Horde
#93 - 2014-03-01 05:53:27 UTC
CCP karkur wrote:
The Directional Scanner has now 2 input fields (km and AU) and a slider for range input. The 3 inputs are connected so when one is changed, the other ones update.

WOOOOOOOOOOOOOOOOOO!!!!!
Rowells
Blackwater USA Inc.
Pandemic Horde
#94 - 2014-03-01 06:17:23 UTC
CCP Punkturis wrote:
Gosti Kahanid wrote:
I realy appreciate these little things.
But why aren´t you posting this in Features & Ideas? It´s there where the Team posts the upcoming changes, and I´m always looking there to see the them.
I only occasionally look into the Test Server Feedback-Area and I´m sure a lot of other people miss this part of the Forum


I added a link to this thread in the little things thread in F&I so hopefully most people will see this Blink

Good, considering I've seen like three different threads regarding the d-scan change and i bet they had no idea lol
Vivi Udan
Caldari Provisions
Caldari State
#95 - 2014-03-02 03:41:46 UTC
Janine Ibanez wrote:
Since you're messing around with ways to display player names, I would like to suggest the following:

Allow for sorting of Local in a tree view filtered by standings. In scenarios where there are hundreds of pilots in system, it's difficult, if not impossible, to get an accurate estimate of the number of friendly/hostile pilots in system without guestimating based on fleet numbers (imprecise since it may include pilots out of the system) or manually scrolling the entire list to count blues, reds, and neutrals.

It's also silly that when jumping into a crowded highsec system, I need to spend several seconds scrolling through the local list trying to see if there are any war targets in system.

I propose a collapsible tree structure that, at the top level, shows you the number of each standings type, with a control to allow for expansion of the node to view individual pilot names. For example:

[+] Red (130)
[+] Blue (100)
[+] Alliance (30)
[+] War Targets (3)
[-] Corp (5)
|----Pilot A
|----Pilot B
|----Pilot C
|----Pilot D
|----Pilot E


ShockedBig smileBig smileBig smileBig smileBig smileBig smileBig smileBig smile

The Mittani of House GoonWaffe, First of His name, King of the Goons and VFK, Master of griefing, Lord of the CFC, Warden of the West, and Protector of Deklein.
Rivr Luzade
Coreli Corporation
Pandemic Legion
#96 - 2014-03-02 23:11:53 UTC
I find it very awkward to have the scan button in the redesigned Dscan window to the right of the window. Could this button be moved back to the center, below the AU text box?

UI Improvement Collective

My ridicule, heavy criticism and general pale outlook about your or CCP's ideas is nothing but an encouragement to prove me wrong. Give it a try.
Caviar Liberta
The Scope
Gallente Federation
#97 - 2014-03-03 00:10:27 UTC  |  Edited by: Caviar Liberta
Just got this message on the test server when I tried to jump a gate or dock in a station.

Last time I was on SiSi I logged out in space.

Cargo space

How did I get more m3 into it than it can hold.
Highfield
Vanishing Point.
The Initiative.
#98 - 2014-03-03 14:59:15 UTC
Caviar Liberta wrote:
Just got this message on the test server when I tried to jump a gate or dock in a station.

Last time I was on SiSi I logged out in space.

Cargo space

How did I get more m3 into it than it can hold.


Happens when you load a ship, and then fit modules that adversely influence cargo capacity (like overdrive injectors) or remove expanders.
CCP Punkturis
C C P
C C P Alliance
#99 - 2014-03-03 15:42:16 UTC
look at all the happy people ITT!

love it!

♥ EVE Brogrammer ♥ Team Five 0 ♥ @CCP_Punkturis ♥
Xercodo
Cruor Angelicus
#100 - 2014-03-03 18:40:12 UTC
CCP Punkturis wrote:
look at all the happy people ITT!

love it!


We missed you Punky \o/

You and karkur need to co-write the dev blog for this stuff and cover it in pink!

The Drake is a Lie