open All Channels
seplocked Ships and Modules
blankseplocked Missile range - calculated vs. actual ... why is it different in game?
This thread is older than 90 days and has been locked due to inactivity.

Author Topic

Operator XIII
Posted - 2011.08.17 00:47:00 - [1]

My calculated missile range - 22km (verified in EFT and in game)

However, in game, my missiles will not hit anything outside of 18km...??? What gives?

Eon Raptor
Posted - 2011.08.17 00:59:00 - [2]

There is an acceleration time that is a hidden factor. Missiles take time to get up to top speed. As a personal practice I usually subtract 10% from calculated distance to account for the acceleration.

Operator XIII
Posted - 2011.08.17 01:01:00 - [3]

dang... good to know, thanks man

Ines Tegator
Posted - 2011.08.17 01:09:00 - [4]

It's more complicated that, because the missile is a separate entity from your ship. This means you have to account for the relative movements of the firing platform and the target as well. A missile will travel a certain distance, and that distance is guarunteed. However the target may easily move out of that distance while remaining close to your ship, so the missile does not it and giving the illusion that you were in range.

In effect, a missiles range is the distance from the firing point (which your ship can then leave) and the target at time of impact (not at time of firing). This will make firing range against a ship moving away from you much shorter, and against a ship moving towards you much longer.

Posted - 2011.08.17 01:14:00 - [5]

Go here and look for "TRUE Missile Range".

Gorey details and testing thread.

As mentioned previously, the missiles continually accelerate until they run out of fuel. (You can never achieve top speed, a ship or missile in Eve will go 99.9999999...9% of max speed, but will never actually hit max speed (except through rounding.))

There's also an issue where at the edge of your effective missile range, you'll sometimes hit and sometimes miss even with a stationary target and stationary shooter. The theory is that the server tick causes the hit/miss issue. IIRC, the server only updates once a second, yet launcher cycles could have fractional seconds, which could give or deny you an extra fractional second of flight time.

PI Beretta
Posted - 2011.08.17 07:58:00 - [6]

Don't forget your target can be moving as well. In the time it takes for the missile to hit, unless it has been sitting still, it has moved some distance the missile needs to travel. In some cases this will lead to reduced effective range but in others the opponent might actually be coming closer and you'll be able to hit outside your calculated range at the time you launch a missile.

Posted - 2011.08.17 08:50:00 - [7]

For what it's worth, the Python Fitting Assistant does attempt to calculate the maximum missile range, rather than providing an upper bound like EFT does.

It's generally pretty spot on. Give it a try.

Hestia Mar
Posted - 2011.08.17 09:14:00 - [8]

As a USAF pilot once said on a TV show, they are called 'missiles', not 'hittiles'


H Rolling Eyes


This thread is older than 90 days and has been locked due to inactivity.


The new forums are live

Please adjust your bookmarks to

These forums are archived and read-only