J-82 JDAM - In Range Variables?

[Adam]

Hi,

 

A few times now I have launched JDAM's as soon as the 'In Range' prompt shows up, just to have them fall short.

 

I'm guessing that there's other variables at play (maybe wind?), that the targeting computer isn't initially taking into contact.

 

I was just wondering what is the best way to counter this? At present I've been delaying my release by about 10 seconds, however I'm wondering if this is putting me at unnecessary risk when I have hostiles inbound being focused on the delay and was wondering if there's a more accurate way of knowing when JDAM's are truly in range?

 

Thanks in advance.

[Swift.]

Wait for the IN ZONE cue

[Emmy]

JDAM Dynamic Launch Zone is under review by ED

 

A10C2 is also affected by this with extremely narrow drop window.

[Swift.]

I don't think the hornets JDAMs have been affected by that Emmy, at least they weren't on Friday before we used them. This issue seems to be an IRLAR Vs IZLAR thing: the IN RNG cue shows you have reached the theoretical maximum range iirc, but by waiting until you are IN ZONE then you will have more success.

 

Alternatively just use the auto mode as that's works great.

[Harker]

I don't think the hornets JDAMs have been affected by that Emmy, at least they weren't on Friday before we used them. This issue seems to be an IRLAR Vs IZLAR thing: the IN RNG cue shows you have reached the theoretical maximum range iirc, but by waiting until you are IN ZONE then you will have more success.

 

Alternatively just use the auto mode as that's works great.

Doesn't IN RNG mean that the bomb can simply reach the target, while IN ZONE means that it can reach it with the required terminal parameters (bearing, angle, velocity)? In my understanding, bombs showing IN RNG should still reach the target, especially since terminal programming isn't implemented yet in the Hornet.

[Andartu]

Doesn't IN RNG mean that the bomb can simply reach the target, while IN ZONE means that it can reach it with the required terminal parameters (bearing, angle, velocity)? In my understanding, bombs showing IN RNG should still reach the target, especially since terminal programming isn't implemented yet in the Hornet.

 

As Swiftwin9s said IN RNG is the theoretical maximum range. I usually wait another five seconds till release then and have always good results.

 

Also terminal programming isn´t implemented? Never changed velocity yet, but heading and angle (up to 90°) I changed very often and it also worked very well. Actually tried it once with a T-55 in between two higher buildings. Did not want to hit the buildings (or that the bomb hit them and not the tank) and changed bearing. Was very satisfying.

 

Change the angle, release, hit F6 and you´ll see it works.

[Adam]

Thanks all! So I'm doing the right thing by waiting that extra 5 seconds - there are other variables at play and 'In Range' doesn't guarantee the range, it's just a calculated 'guess'.

 

And great info about terminal programming. If that works - that will be very handy!

[dorianR666]

Doesn't IN RNG mean that the bomb can simply reach the target, while IN ZONE means that it can reach it with the required terminal parameters (bearing, angle, velocity)? In my understanding, bombs showing IN RNG should still reach the target, especially since terminal programming isn't implemented yet in the Hornet.

 

correct

[Adam]

correct

 

Maybe that's what it 'should' mean - but it looks like that's not always the case. :)

 

I wasn't sure if I misunderstood, or whether there were other issues at play. Seems like I'm not the only one that's experienced IN RNG actually not quite being in range and falling short. For someone who's locked on and a SAM has launched, with 5 seconds counting down I've normally held out and dropped as soon as IN RNG shows up and then high-tail it out of there.

 

Now I'm taking the approach that I need to calculate for IN RNG + 5 seconds or so before releasing when making my decision to stay on target or get out of dodge sooner and come back another day.

[Harker]

As Swiftwin9s said IN RNG is the theoretical maximum range. I usually wait another five seconds till release then and have always good results.

 

Also terminal programming isn´t implemented? Never changed velocity yet, but heading and angle (up to 90°) I changed very often and it also worked very well. Actually tried it once with a T-55 in between two higher buildings. Did not want to hit the buildings (or that the bomb hit them and not the tank) and changed bearing. Was very satisfying.

 

Change the angle, release, hit F6 and you´ll see it works.

 

Maybe that's what it 'should' mean - but it looks like that's not always the case. :)

 

I wasn't sure if I misunderstood, or whether there were other issues at play. Seems like I'm not the only one that's experienced IN RNG actually not quite being in range and falling short. For someone who's locked on and a SAM has launched, with 5 seconds counting down I've normally held out and dropped as soon as IN RNG shows up and then high-tail it out of there.

 

Now I'm taking the approach that I need to calculate for IN RNG + 5 seconds or so before releasing when making my decision to stay on target or get out of dodge sooner and come back another day.

Just to clarify, I was talking about what IRLAR and IZLAR mean IRL, not what they do in DCS. It's possible that the DLZs are wrong in DCS and they don't correspond to the actual bomb performance. This can happen, if ED changes the JDAM performance but omits to update the code for the DLZ. It's happened before, with the AMRAAM.

 

 

 

Interesting about the terminal parameters, I'll have to try that. Last time I did a few weeks ago, it didn't do anything. Also, if it works, it should change the IZLAR shape/location on the HSI. I'll try it out.

[AvroLanc]

Just to clarify, I was talking about what IRLAR and IZLAR mean IRL, not what they do in DCS. It's possible that the DLZs are wrong in DCS and they don't correspond to the actual bomb performance. This can happen, if ED changes the JDAM performance but omits to update the code for the DLZ. It's happened before, with the AMRAAM.

 

 

 

Interesting about the terminal parameters, I'll have to try that. Last time I did a few weeks ago, it didn't do anything. Also, if it works, it should change the IZLAR shape/location on the HSI. I'll try it out.

 

I'm pretty sure the terminal parameters don't yet work in the Hornet. I tried yesterday, right after I figured out that they do indeed have a limited effect in the new A10.

 

Entering a terminal heading for Hornet JDAM didn't do anything to bomb trajectory. It certainly doesn't change the IZLAR shape or heading. Maybe future.

[Andartu]

I'm pretty sure the terminal parameters don't yet work in the Hornet. I tried yesterday, right after I figured out that they do indeed have a limited effect in the new A10.

 

Entering a terminal heading for Hornet JDAM didn't do anything to bomb trajectory. It certainly doesn't change the IZLAR shape or heading. Maybe future.

 

What should I say, it worked on my side though...:huh: Angle manipulation definitely.

[Adam]

What should I say, it worked on my side though...:huh: Angle manipulation definitely.

 

Is this on Open Beta, or also on Stable Release?

[Andartu]

Is this on Open Beta, or also on Stable Release?

 

I fly in OB only.