EVE General Discussion

You could have the client use default values I suppose. So it would assume MWD with base skills and display that. It wouldn't make much of a difference in the output. The alternative of trying to keep a ship's sig radius a secret doesn't seem like a strong enough reason to hold back something like a turret tracking quality indicator.

While I cannot say for certain if the client knows what a targeted ship's sigRad is, I guarantee the server knows. So it would not be hard to just send that info to your client as part of the overview data. Just enable a sigRad column.

the tl;dr is that its been dumbed down to mush because radians are maths. Sig radius has **** all to do with tracking so stop with that nonsense.

You must be new around here :) Do you have a spreadsheet program?

You need to know four numbers in order to calculate your chance to hit something with turrets (assuming you're in optimal):
Gun signature resolution (meters)
Gun tracking (rad/s)
Target signature radius (meters)
Target angular velocity (rad/s)

These days, gun signature is a constant 40,000 m across all guns. Turret tracking remains rad/s and is displayed in the info panel. CCP actually did the opposite of 'dumbing down' - they made more maths necessary.

maybe i have worded it wrong, but to boil it down... let's assume you have a ship with only M guns (for examples simplicity sakes) and want to try to hit a frigate with it.
The one and only thing you can yourself manipulate is your relative position/velocity which immediately boils down to your guns tracking speed.
Take the readouts you can get from overview and tell me how to turn my ship to have a better chance at hitting when i have a gun accurcy score of 40.

Tracking displayed on guns got standardised, not dumbed down. And sig radius is still right there in the chance to hit formula.



tracking of 40, aiming at a default sized frigate with sig size of 40, you take the tracking on your gun and divide by 1000. Get 0.04 rad/sec. Put angular velocity on overview, if it's 0.04, you'll hit about half the time. If it's lower, you'll hit more. If it's higher, you'll hit less.



I think it's good. You can make an educated guess based on how often you hit, but you can't just read detailed info on their ship. Same as you can make educated guess about their hp based on how fast you're damaging them, but you can't just read off the overview what their resistances and hp total are.

1. Slow down your target as much as possible. Use scram and at least one web.
2. Move in the same direction as your target. Determine this by looking at the target's velocity vector in the tactical overlay.
3. Match your target's speed.

At no point do you need to actually view your target's angular velocity - you simply always maneuver to maximize your chance to hit. Unless your role is tackle instead of DPS, or you are being primaried and want to survive as long as possible, in which case you want to maximize your angular velocity relative to all hostiles on grid, but again you don't care about the actual angular velocity, you just want to maximize it. I mean, if the angular velocity that gives you a 50/50 chance of hitting is 0.12 rad/s, are you really going to fly differently if the actual velocity is either 0.30 rad/s or 0.07 rad/s?

I once was flying a tackle frig trying to get close to some sniping battlecruisers so I spiraled into them - after about four shots that completely missed they all bugged out and I'm 99% sure it's because they saw all their shots missing, not because they looked at my angular velocity and judged it to be higher than their guns' tracking after accounting for their sig resolution compared to my MWD-on sig radius.

Are you talking about when you're flying solo? If so, wouldn't you simply pick the one with the smallest angular velocity regardless of whether it actually is (for example) 0.07 rad/s or 0.22 rad/s? If I'm in a group I simply shoot what the FC calls as primary (or if I'm the FC I pick targets based on what they are, where they are, and what they're doing, not their angular velocity relative to only me.) As for judging effectiveness of my webs, I have the target's regular velocity along with my shot quality to judge that, and as for effectiveness of my maneuvering I certainly can look at the target's angular velocity but I'm not bothering to compare that to my guns' tracking.

In short http://eve.beyondreality.se/pics/TrackingFormula.png

Important part from that is the first part. trans/range is of course target's angular velocity (rad/s), so you have:

angular/tracking * scan_resol/radius

In the past as long as guns and ships were of similar class size (e.g. small guns vs frigates), you could roughly ignore the right part and compare overview data to a gun's tracking value directly (keeping in mind differences coming from occasional ship bonuses / boosters / implants)

In CCP's infinite stubborn nonsense, they took every single gun and scaled it up to 40km scan_resol and renamed it from tracking to "weapon accuracy score" (and also left all drones at 400m becuase **** yea for consistency). Goodness knows what for overall.

So now we have:

angular/tracking * 40km/radius

They of course didn't give much of a damn about updating what overview can show - it should show angular velocity scaled up to 40km radius (ITOW: multiplied by 40km/radius) - that would be directly useful and actually better than what it was before.