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

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

Player Features and Ideas Discussion

 
  • Topic is locked indefinitely.
 

More customisation for angular velocity overview column

Author
Grigg Skjellerup
Pator Tech School
Minmatar Republic
#1 - 2016-12-27 20:24:10 UTC
Since I last played, the tracking stat on guns has had a big change to how it is displayed.

It's now standardised for all guns, I think a good thing.

But instead of the tracking being standardised for a frigate sized target, they've taken that and multiplied by 1000, possibly for aesthetics, because all those leading 0s look bad. This, I don't think is a good thing. But I can cope with it.

Leading 0s are apparently aesthetically displeasing. Having the angular velocity shown on the overview directly relate to the tracking you see when mousing over your gun is a helpful thing, makes for less mental maths.

Which leads to my suggestion: Allow us to customise the angular velocity column, multiplying it by a scalar of our choice.

We're fighting frigates, or primarily concerned about frigates? We'd set the scalar to 1000. Cruisers, 320. BS, 100. Some might even make separate tabs, or 3 different angular velocity columns on overview. Less leading 0s also makes the info quicker to take in at a glance. Spotting the biggest of 1 v 0.4 is very quick. If the overview displays 0.0001 v 0.004, it's not so fast, . Less leading 0s also allows the column to be narrower, making more space for other stuff.

And most importantly, It lets us display on our overview a stat that we can directly check against the gun stats, same as we can for distance to target. We might know the normal gun stat is 20km optimal, 40 tracking. Get disrupted, and now it's 16km, 32 tracking. It's easy to look at overview now and see distance to our cruiser sized target is 30km, so get closer. It's not so easy to look at overview and see a.v. is 0.12, and whether that's ok or terrible for our disrupted guns. But if we'd made effort to set up overview, we'd see 320*a.v., the display would show 38.4. Heaps easier to compare 38.4 to 40, 38.4 to 32.

Or we might set it to show 640*a.v., and know that if the displayed number is below our tracking, we hit 85%+ of the time. Whatever works for each player's preferences, the important thing is important info can be seen at a glance, instead of requiring you to memorise numbers/divide by 3 and a bit in your head.