Riple fire R27

[wasserfall]

when i riple fire a R27R and a R27T how much time do i have to take between these two to launch, is there a radar contact loss from the R27R or can i change directly to R27T

[britgliderpilot]

Re: Riple fire R27

 

when i riple fire a R27R and a R27T how much time do i have to take between these two to launch, is there a radar contact loss from the R27R or can i change directly to R27T

 

AFAIK, there should be no need to pause at all. Whooshwhoosh . . . . .

 

Of course, the Rmax for the R27T is smaller than that for the R27R . . . . and PK is minimal at extreme range as well. Shrug.

[Octav]

Re: Riple fire R27

 

You should wait until the R's motor burns out, or the T might lock on to it - or fire them in reverse order: T first, R next.

 

Octav

 

EDIT: In real life, of course - in LO it seems there is no problem firing them like click-clik

[Shepski]

Re: Riple fire R27

 

You should wait until the R's motor burns out, or the T might lock on to it - or fire them in reverse order: T first, R next.

 

Octav

 

EDIT: In real life, of course - in LO it seems there is no problem firing them like click-clik

 

I have seen the R-27ET chase down and kill an R-27ER in Lock On v1.0x.

[Guest ruggbutt]

If you're firing at max range, wait 15 seconds before firing a follow up shot. At least that's according to the wonderful Ironhand tutorials. :D

[Shepski]

In v1.1 the IR seeker lock on logic has been changed so the IR seeker of an R-27ET now has much shorter range and is dependant on aspect and heat signature of the target.

[Alfa]

If you're firing at max range, wait 15 seconds before firing a follow up shot. At least that's according to the wonderful Ironhand tutorials. :D

 

If you are firing an R-27R at max range in head-on aspect, you would automatically have to wait some time before being able to fire an R-27T ;)

 

R-27R max engagement range is determined by lock range of launching radar - limited by missile kinetics. R-27T max range is determined by missile kinetics - limited by IR seeker lock range(no radio command link).

 

In a head-on engagement an R-27R could be launched at a range some 3 times that of an R-27T.

 

In rear aspect engagement radar lock range is severely reduced(thus engagement range for R-27R), while IR seeker acquisition range is significantly increased, and IR lock range might exceed that of a radar ditto....depending on the nature of launching radar of course.

 

Conclusion: use R-27R for maximal engagement range head-on to keep the opponent busy and follow up with an R-27T "fire & forget" if the target turns tail to evade the R-27R..... and select R-73(if loaded) for head-on close encounters.

[Sabadin]

In v1.1 the IR seeker lock on logic has been changed so the IR seeker of an R-27ET now has much shorter range and is dependant on aspect and heat signature of the target.

 

If the seeker loses it's target, does it look for a new one, coast, or detontate?

[Octav]

In v1.1 the IR seeker lock on logic has been changed so the IR seeker of an R-27ET now has much shorter range and is dependant on aspect and heat signature of the target.

 

If the seeker loses it's target, does it look for a new one, coast, or detontate?

 

It will NOT detonate - the R-27 has no timer - so it will coast until it finds a target, if not it will loose energy until ut crashes into the ground - ant it will be detonated on ground impact.

 

Octav

[Avimimus]

In v1.1 the IR seeker lock on logic has been changed so the IR seeker of an R-27ET now has much shorter range and is dependant on aspect and heat signature of the target.

 

Sounds very good :D!

[BIOLOG]

In 1.1 you can shoot down missiles with your missiles... Although this is somewhat ineffective against front-aspect engagement. However works like a dream against cruise missiles.

[GGTharos]

Can we shoot them down with AMRAAMs? Currently I believe they fly below the 'radar cut-off' altitude for an AMRAAM.