Eddie

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.

The 4 MELs are stations 3C, 4C, 6C, & 7C. These are not modelled in DCS at present. The real F-15E has 23 weapon stations, the DCS F-15E only has 19. So the only way to load AAM on the CFT stations at present is for them to be loaded on the AG ERUs, which is physically impossible, hence the change.

With the aircraft configured for the air to air role, yes. The DCS Strike Eagle is configured in its air to ground configuration. In which it is not possible to load weapons on the LAU-106 missile ejector launchers. In A/G role config the forward LAU-106 is stowed aft of the forward ERU, and the rear cannot be loaded while the forward ERU is loaded. DCS does not currently support differing role configurations for the aircraft featured. When that changes I'm sure it'll be possible to load weapons on the MELs.

Indeed it would be nice to finally have them modelled. The LUU-19 and M278 have been absent from the A-10C for all too long. The same goes for IR aircraft lighting. Hopefully when EDGE eventually comes along we might see some progress in these areas.

Use of the word edge in a sentence is hardly link to the "EDGE" engine being developed by ED.

The Russians. mmHG is not an appropriate unit for the A-10C, but then nor is QFE, and we're stuck with both in DCS. The fact that DCS doesn't use a uniform system of units depending on the user settings and the aircraft in use has long been a source of frustration for many. Maybe one day it'll change, who knows.

And that's why we released the range targets pack.

That's a good analogy, I might have to steal that one.