EVE General Discussion

Admittedly I don't know what I'm doing, but there seems to be a discrepancy between the advertised 'tracking' on my turrets, and the angular velocity for ships on my overview (expressed in radians/s). They seem to be unrelated, i.e. a ship on my overview seems extremely 'hit-able' yet I cannot hit it.

Care to explain or point me to a link?

Thanks.

Divide turret tracking by 1000, you'll hit frigates doing that many rad/s 50% of the time.

Multiply by 3.2, you'll hit cruisers doing that many rad/s 50% of the time.

Multiply that by 3.2 (or divide original turret tracking by 100) and you'll hit battleships doing that many rad/s 50% of the time.

That's the rule of thumb you want to start with, it obviously changes a little if the sig sizes aren't exactly 40/125/400.


I didn't like the change at first, but I think it's decent now. My only gripe is the pointless 'multiply by 1000' factor because tracking of 40 or 300 is apparently more aesthetically pleasing than 0.04 or 0.3, even though the latter makes it quicker to calculate/see at a glance.

I thought it was a way to normalize capital turret tracking and its six decimal place figures. I don't think it means much to people either way. Even expert types usually stuck to pyfa damage application charts instead of discussing the formula itself. It just looks better at the very least.

there's a visualized tracking formula suggestion I made two and a half years ago that never really went anywhere. Still valid, since the tracking quality (rating?) figure is a conversion from the underlying formula.

https://forums.eveonline.com/default.aspx?g=posts&m=4474983

Interesting. Your suggestion has been locked, so can't post there. But have a couple of questions about it.

How would you decide on how far that angular velocity arrow stretches for different sized targets? A visual representation can be a good thing for those who prefer visual to numbers. But how does it adjust when you have a cruiser and a frigate locked? I'd be wary about it giving misleading info, e.g. frigate's arrow is inside the cone, so you should be hitting, but you're not. Or cruiser's arrow is outside, so you don't fire even though you'd hit it fine.

How would you work it with multiple targets locked? Have 6 different cones displayed?

The other thing, and I may well be wrong on this, is that there is no way to tell your target's sig radius in game, is there? Only to guess it based on hull size and any other factors? As your display requires sig radius to be known, that'd be an issue.



I disagree, but whatever works for you. There's no requirement for anyone to use them, I find they provide me useful info, particularly data for working out what a fit should have, so I'll keep using them.



I can & do work out the what if numbers with pen & paper. And with the tracking number now standardised for turret size, it's only dependant on sig radius. So easy enough to generate numbers to usefully compare. e.g. Do I want tracking of 30 while orbiting at 20km, or tracking of 50 while orbiting at 8km? Which one will hit more if I assume they're near stationary, which will hit more if I assume they're doing 400m/s in the opposite direction to me? What's the practical minimum range I can shoot frigates doing 500m/s at? And so on.

Use Transversal Velocity in place of the Angular column; it's easier to read at a glance, and through experience you can judge how low your target's transversal needs to be for your guns to land decent hits.

The old un-normalized numbers were only valid in the specific case where the target's sig radius equaled your weapon resolution.

I think that's the biggest barrier to your suggestion. That even if the client does know the info, it doesn't show it to the player, by design. You can know your own sig radius, but you only get to make educated guesses as to the opponent's sig radius. If you have an interceptor targeted, you have no clue if the pilot has it trained to 1 or 5, you can see the MWD is on, but not how much it's changed the sig size.



If I see transversal, then I'm going to convert that to angular in my head based on also looking at the distance, or based on some rule of thumb. Why wouldn't I just look at angular, since that's the stat I want in the first place, the stat my guns care about?

you can totally tell by the ship's speed though. If that interceptor is doing like 4km/s, i mean.

Transversal is meaningless for tracking. For it to have any meaning, you have to do complex trigonometry converting it to angular velocity. Then it becomes useful. Or at least, it used to be useful.

This plus experience will give you great results no real math necessary only thing is its a per weapon type or ship basis. At first its per ship type and then its a per weapon type of the same style mostly where lower is simply better regardless of what your doing.