The point is that as it stands these changes are being performed quite obviously to avoid having a Phoenix be capable of hitting a subcap. The point of showing that the others CAN is to point out that the effort to avoid this is absurd given that all other dreads are capable of doing so.

Ignore the subcap ****, it is irrelevant. It makes no difference if a Moros can hit a BS harder than a Phoenix.

When dreadnoughts are a not-uncommon source of anti-cruiser DPS, it matters. Breaking through triage reps on a deadspace fit armor T3 requires a lot of DPS; since battleships are practically unusable due to crappy resists & vulnerability to blap dreads, something has to kill those cruisers.

Battlecruisers. Carrier Sentry Drones. Other Cruisers. Bombers. Frigates. Ignore subcaps. They are irrelevant. They are taken care of by other subcaps, and by carriers.

The best thing CCP could do to boost the never-not moros problem, is nerf XL blaster range into oblivion where it should be. I get it that they want you to hit pos's with AM for full damage, but that arbitrary point means pushing the ranges to absurd and silly levels.

Question... why does the Caldari ships have lower scan res than their Mimatar counterparts? Isn't lore wise, Caldari suppose to be second only to Jove in technology. So you factor in lower base scan res with the flight time of missiles- it gimps the application of dps a bit.
And yes, i found out that the Phoon is potentially a much better torp boat than the Raven... Nice balance CCP.

When are those missile TC/TE modules coming?

Just don't use phoneix's in a wolf-rayet wormhole.

Fun fact, by increasing the sig of all dreads all dreads become easier to hit and lock all other dreads... So all dreads just got a tracking bonus, and a scan res bonus vs other dreads. Win win.

Now that you're here, did they run this change past you guys? How on earth did none of you object? I voted for you dude god damn it.

Why not just put a Signature Radius Penalty on the Triage module while it is active, for example,+50% signature. Then Triage Carriers will take full application from the Phoenix, the signature radius penalty won't affect gameplay in any other meaningful way.

I've posted that proposal mean a-times in this thread. Thanks for the +1

why cant i find the downvote button

If anyone is interested, I have graphed the new vs. old phoenix numbers here

To see the full reddit discussion of these graphs, see here (my reddit user name is deepandabear fyi)

It is quite clear that the higher DPS is not substantial enough to overcome sig tanking capitals.

the problem with this s that it doesn't show the targets velocity.

If you check out the discussion, different velocities are analysed. The short story is, the explosion radius nerf is so significant, that velocity of the target is now far less important. Some one else made a (somewhat dodgy) graph that also shows velocity in that thread fyi.

So basically the missile velocity buff is not that useful. It will only help more when the target has a huge sig and is going 40-60ms (so a pretty marginal amount of cases).

Here's an analysis on subcap application I made. I only considered two ships, but the results can be extrapolated quite well. Essentially the Phoenix becomes better at hitting things that would've both speed and signature tanked both the old and the new torpedo, while becoming worse at hitting things that couldn't signature tank the old torp but can signature tank the new one.

I'm yet to see an argument against my suggestion of just buffing the Explosion Velocity by 20% and leaving the Explosion Radius alone. I'm also yet to see any dev replies to any of the problems people have pointed out in this thread, aside from the one on page 12 or something which denied the existence of those problems despite there being quite concrete proof for them.

Was there any thought to increasing cargohold size, as the rate-of-fire bonus means the Phoenix requires more missiles now?