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.
 

Introduce Normalized Angular Velocity as selectable column in overview

Author
Soltys
Brutor Tribe
Minmatar Republic
#1 - 2016-10-09 16:19:32 UTC
Now that we have "WAS" values - which are still good old rad/s but now scaled up to match unified 40km scan resolution.

Obvious effects:


  • good: the tracking is directly comparable between the guns / drones
  • bad: the tracking value is no longer easily comparable to angular velocity in overview - in the past small guns roughly matched small ships, medium - mediums and so on. ITOW - sig_res of the target and scan_res of the gun were similar enough for angular velocity to be directly comparable to tracking values (against similarly sized targets). Size differences between different ship classes could be easily compensated for as well - on the fly. One could say - you can do the same with 40km scan res - but it's notable more PITA now with bloated 40km scan_res to compensate for (and now has to be done against every target, whether same size or not)


But the situation can be trivially improved. In the same way as guns/drones' tracking is scaled to match 40km "resolution" - angular velocity (as displayed in the overview) can be scaled to match 40km signature radius. Essentially:

NAV = AV * 40,000 / sig_radius

This way, well known tracking part of chance-to-hit equation:

(AV / sig_radius) / (tracking / scan_res)

which is now:

(AV / sig_radius) / (WAS / 40000)

would become:

(NAV / 40000) / (WAS / 40000) => NAV / WAS

Now that's even better than what we had in pre-WAS time, as we would always get meaningful directly comparable values.

Emphasis on word: introduce. Don't just throw away old AV, add NAV as a selectable option.

Jita Flipping Inc.: Kovl & Kuvl

Brokk Witgenstein
Sebiestor Tribe
Minmatar Republic
#2 - 2016-10-09 22:02:59 UTC
I don't want you to know my sigradius. It gives away too much information.
Soltys
Brutor Tribe
Minmatar Republic
#3 - 2016-10-11 01:09:46 UTC
I already know your ship's precise signature radius from "size" overview column. And I know how much you can eventually lower it by halos (not exactly popular implant) / x-instinct (not exactly popular booster) / [soon to be dead] ogb. And one can guesstimate your sig radius penalites rather quickly as well (module/rig penalties) . ITOW - your best case sig radius and realistic sig radius are known momentarily.

So, your sig is barely a secret, and even less relevant when tracking component is considered (as the math for final hit chance is a bit more involved and in no way exposed). Considering good enough estimation from the above, do you think anyone will bother calculating your precise sig radius, in combat, from 2 separate overview columns ? Even if that was "realistic" we /could/ replace AV with NAV, instead of adding it (which would remove any indirect exposure).

Other than that, well set overview and new tactical overview is far bigger enemy than angular velocity in one column normalized to 40km (new cute blue lines in particular - their lengths, projections on overview plane, precise distances to ships ....).

Jita Flipping Inc.: Kovl & Kuvl

Brokk Witgenstein
Sebiestor Tribe
Minmatar Republic
#4 - 2016-10-11 02:05:33 UTC
Soltys wrote:
I already know your ship's precise signature radius from "size" overview column.

Wrong.