Eddie

As long as you're dropping on to a steer point, how you generate that steer point is irrelevant.

Why on earth should I repeat things that have already been said and explained by others in this very thread? It's all here already, you're just either choosing to ignore the points that have been presented or failing to understand them. You're just not appreciating the facts and elements at play here. The overtake being referred to isn't fifty knots, it's one or two knots. And being just a fraction of a second slower or faster on the throttles, or having a couple of hundred pounds of weight difference will produce that. Lead should be at just one or two percent less than max during a formation takeoff.

Well I would respond, but frankly even after reading your post six times, I still can't work out what on earth you are talking about or what point(s) you are trying to make.

Sorry, but that is utter rubbish.

Well that's nice for you. However, the real world TTPs are exactly as PFunk has described.

A bit of JDAM background for anyone who's interested. Hopefully it'll illustrate how different the DCS JDAM and real JDAM are. JDAM employment uses what is known as a LAR (Launch Acceptability Region), not max/min range. The LAR is entirely dynamic and varies depending on things such as launch aircraft speed, altitude, heading, winds, desired impact heading, desired impact angle, and desired impact speed. The LAR surrounds the target and is essentially a circle in which if the weapon is released under the current flight conditions it will be able to hit the target with a minim impact angle of 35 degrees and a minimum impact speed of 300 ft/sec. Being in the LAR doesn't imply that the weapon can meet any specific chosen impact parameters. You then have a smaller area of sky within the LAR in which releasing the weapon will enable it to satisfy any chosen impact parameters. Parameters that can be specified include impact heading, impact angle, and impact speed. If for any reason the weapon determines it cannot hit the target and meet the specified parameters it will sacrifice impact speed in the first instance, followed by impact angle and heading. The release aircraft also doesn't need to be pointing at the target, you can release a JDAM on a target 90 degrees off your nose if you want to, you'll just see a significant reduction in range. You can release a JDAM at any airspeed between 165 knots and mach 1.5 depending on the variant, with it being recommended to release at as high and altitude and airspeed as the tactical situation will allow. Winds are taken into account by the launch aircraft when determining the LAR. After release the weapon performs a clearing manoeuvre to ensure safe separation from the launch aircraft and then begins flying to the desired impact position. For approx. the first 10 seconds of flight a JDAM is running purely on INS guidance and after that time and as it begins to acquire GPS satellites its accuracy increases, with the CEP dropping to 15 metres after about 30 seconds of flight. If the GPS system is being jammed the weapon will guide to target using INS only. In the last second before impact the weapon reduces its angle of attack to zero. While you can release a JDAM using a dive or a loft, doing so doesn't really offer any big advantages and in most cases actually reduces range. There are several other features as well such as pattern releases, pre-plan targets, and others. Some stuff is used by the A-10C, some stuff isn't. But as far as DCS goes, not even the cockpit symbology matches the real thing. JDAM is one of the areas where DCS differs most from reality, in fact aside from countermeasures, RWR, & MWS, I'd say it's the most different.

The (real) JDAM does compute its VV and AoA and a lot else besides. It also doesn't have any issue at all hitting its target with wind. Again, don't have time right now to type a lengthy post about the operation of JDAM, but II will summarise by swaying that the DCS JDAM shares its appearance with the real JDAM, and that's pretty much it. If I remember I'll address a few other points that have been brought up later on when I'm at home on the PC with an actual keyboard.

Make it your steer point, then set steer point as SPI.

Perhaps he should try closing his left eye and hopping on his right leg while shouting "I am a potato" in mandarin? It would be just as effective.

Not at all. The only time point track is required is if you want the pod to track a moving object. Otherwise area track or, subject to a few limitations, inertial rates are fine. Area track is actually preferable in most cases. I can't go into detail on how the different track types work as I'm at work and typing long replies on the phone is not easy.

At 12NM you're outside the effective range of the LASER. Both in reality and in DCS. Counter question for you, in that situation why are you using point track? Had you just used area track centered on the base of the intended target everything would have worked fine.

Ah but it can. TMS aft short with a weapon profile selected and CCIP aiming active. The SPI will be latched to the IFFCC computed impact point for the selected weapon. Be careful you know of what you speak before so hastily jumping to claim someone else is wrong or confused. ;)

Why? What about his post made him appear confused. His suggestion perfectly illustrates how the SPI works.

That says exactly the same thing. However as it does not clearly state the SPI is a constantly updated point, it could be misunderstood.

http://forums.eagle.ru/showpost.php?p=1992503&postcount=40 Read it, think about it, absorb it. You're suffering from the same, apparently common, misunderstanding. And there was me thinking that the SPI concept was simple. :huh:

The coordinates are transferred when you press the pickle button, then repeated back by the weapon for confirmation, and then the weapon is released. So yes, if you had the LASER firing when the pickle button was pressed then, of course it would be those coordinates that are passed to the weapon because that is your SPI.

And that is the misunderstanding I referred to yesterday. A SPI is NOT a fixed point, it is a constantly updated position taken in real time from which ever sensor you have set as the SPI generator. In you example above, you point the TGP at a target and get position A which is looking at the terrain "through" the target, then you fire the LASER and you set the SPI with your LASER on and it gives you position B as your SPI location, now this is where you think it stops yes? Wrong, the second you turn the LASER off the SPI will update to position A once again.

Even if you did have the laser active throughout that "attack" you'd have the same problem. The only situation in which using the LASER would have helped is if you had made a mark point from your TGP generated SPI at point 1 of your test.

A LOT of "common knowledge" around here comes from an initial misunderstanding of the mechanics of a system and/or it's intended use. Or to put it another way, there are an awful lot of solutions to problems that don't actually exist.

And that whole concept comes from a fundamental misunderstanding of how the SPI/SPI generating SOI work. If you are using the TGP to generate a SPI on which to drop a JDAM, there is no reason whatsoever to employ the LASER. It can make some sense if you're creating a mark point from a TGP generated SPI at a low angle and high slant range from which you will later generate a SPI for a JDAM, but in such a situation it's likely that you'd be beyond the effective range off the LASER anyway, and simply being aware of how the SPI works and adjusting the aim point would be more effective. By the time you're at a range from which the A-10 is able to release a JDAM on target, the slant angle will be such that any error caused by looking though the target with a TGP generated SPI will be nonexistent.

There is no particular real world TTP when it comes to ripple settings for rockets. The reason for this is simple, you can't set a ripple setting for rocket in reality. IRL you have a choice, either one rocket per press of the pickle button, or the whole pod. And that is set on the ground. The only thing you'd do in the jet is set the prior to match the physical pod settings. If you were carrying two pods you could decide if you want to fire one or both pods by using single/pairs, but that's it.

It is not a TTRN, it's the required climb/dive angle in order for rockets fired at that point o hit the desired impact point.

The toss deliveries of visual level deliveries like every type do not require a specific targeting method, just like every other type. CCRP or CCIP, it doesn't really matter. For example you could perform a 30/10 MAT using CCIP CR to designate the target, but equally you could use the TDC and CCRP. VLD would normally use CCIP, but again there is no real reason you couldn't use CCRP. You are correct regarding LAT/MAT.

Missile Ejector Launcher.

Did you copy/keep your control config from 1.2.6 by any chance? If so you may need to remap NWS.