AvroLanc

Upload a track if you've got time. It's been reported many times, but I'm not sure that this very obvious problem has been officially accepted by ED yet.

It looks like there's a new bug with F/F only datalink contacts. When an AWACS is absent or SURV deselected, no bottom HAFU for F/F radar contacts shows up on the SA/RDR page. Wingmen and donors have said contacts on radar, yet HAFU's don't display. Or they aren't transmitting properly. Please watch first few minutes of track as I play around with SA page F/F and SURV options. Thanks FF Datalink Contacts.trk

It's a feature as you've described. Anti-col on means no flash available.

That’s still very possible. A non interactive symbol. The SA page we’ve got probably represents an early iteration anyway. Comparing ours to more recent references shows differences. More advanced features, comparable to very good F-16 and A10 integration may have come later.

That’s a question that I’ve asked before, and same response. No one seems to know at the moment. However, the Hornet is not the A10, the A to G datalink functions are I suspect a little more limited. My prediction is that at best, we’ll be able to create our own TGT point at the location of the transmitted point. And maybe possibly view the target under cursor on the JHMCS. But I’m guessing in the absence of other info.

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.

Well, that's the thing. Any pickle press with the pod set to Ripple should fire the whole pod (not sure of the exact interval between rockets). With the single setting, one press is one rocket.

Yep, but it doesn't work. I'm happy with the workaround, it just needs to function correctly. Ideally move the 'switching' to the ME / Rearming window.

It would be nice to have the proper options for rocket ripple. The rocket settings should work exactly like the Hornet/Viper/F5 set up. You should only have a pod set up to either fire a single rocket or ripple the whole pod at once. The INV page has a setting for Single or Double....although I'm sure the 'double' option is a typo and should be 'Ripple'. Indeed if you set 'Double' in INVENTORY the DSMS profiles page shows 'Ripple' in the settings. In any case, Double/Ripple does nothing. It should fire off the whole pod with one pickle. AFAIK, the DSMS Single Ripple setting is not a thing in real life. One pickle press should be a single rocket or the whole pod. Probably easy to change if ED have the inclination.

Just as an add on to this thread.... The JDAM terminal parameters do actually work in the A10. The Impact Azimuth is respected, the bomb will attempt a terminal maneuver to impact at the correct setting. There is a bit of a margin, often it will impact +-5 degrees either side... I've not seen a major difference in Impact angle, but needs testing more. The GBU-54 release/standoff range is still really low. (Reported) Even so, this is cool, and good news. Bodes well for implementation on Hornet and Viper.

Making different profiles would be useful once (if) terminal options get done. That way each bomb/target can get different attach azimuth and angle. Possible use.

Yep sorry DMS long Right. Yeah, it would seem strange if you can't HMCS slave direct from a steerpoint slave, without the little separate TGP slew. Good chance it's a little error, but not 100%

On the CDU, turn the waypoint dial to 'Flightplan'. The lines should show up. Alternatively, on the UFC press 'FUNC' then '7'.

It looks like, from my quick test today, that the issue is when TGP is in a slaved state. I.e. slaved to a steerpoint. When slaved the DMS Long Left Command doesn’t work. Slew away from the steerpoint a little and it does. Not sure if intentional. Sort of see the argument both ways.

I know. But it's the best we have I guess.

If you use the STAT/HMCS page settings, you can change the symbols you want from OCCLD to ON. This way you can have the required symbols overlaid in the HUD FOV. Essentially the same as being on the HUD itself. Very useful.

I've stumbled across new Profile Settings for JDAM and IAMs. When you change settings, there's new options for 'Target' and 'Waypoint ID', along with Impact AZ and Angle. There's also a new HUD symbol. The target settings are presumably used for pre-planned targets. In my screen shot below I've entered Waypoint 6 as the target, which is accepted. This also generates a new HUD symbol. A small circle with a dot is placed at the location of WP6. The problem/question is that the steering commands for the GBU-38 LAR are still towards the SPI, which is not WP6.... I would expect the LAR etc to jump to WP6 (Entered Target location), instead of the SPI in my case. This might not be implemented, but is there another step I'm missing? Is this a hint of further additional functionality to come? The addition of the HUD symbol indicates maybe........hopefully.

It’s not a bug. Real A10 manual has the exact same HOTAS functions table as the one posted in the sticky. Use TWS AFT long to set SP as SPI. The CHINA AFT long to set TGP to SPI. Just requires a bit of relearning.

Saves a still image from the TGP. It can then be sent as part of a message to another unit on the datalink. Either back to the JTAC for target confirmation, or as a FAC(A) to another A10 etc for directing a CAS mission. I don't think we'll see it implemented. But it would be awesome.

Not accurate in the sense I was being over dramatic? Ok, maybe not overhaul, but significant additions. Some small, some harder to integrate with other systems.

Yeah but it requires a whole TAD overhaul. TAD first then the data gets pushed to HMCS to also display there I believe. Having the air surveillance tracks on the HMCS/TAD would be a major plus. So would Waypoint labels on TAD, datalink markpoints, emergency points, theat rings etc. The fact we’ve only paid §10 concerns me a little though.

I don't imagine it's implemented. It's clearly a function of the real GBU-54 used to attack pre-planned targets. Also, you can see options to set attack impact azimuth and impact angle. Not implemented either. Personally I would love to see this get added. Especially if the coding for azimuth and angle gets done for the Hornet. Why not add here too?

I guess the question being asked is whether the CCIP reticle is always correct beyond its 12000ft range limit? All the way to the rockets ballastic range? How much energy/speed does the rocket need to still manoeuvre/guide at its max range? How much off bore sight can the rocket seeker deal with and how does this effect max range? Does a higher altitude release give the rocket better terminal performance, especially at max range or moving target. What’s the rule of thumb for best case optimum altitude versus range etc?

I don’t think it’s a training flare. It’s the same smaller flare that means the Hornet should carry 60 flares instead of the 30 it was originally designed for. The same smaller flare that the DCS Viper apparently (a bit inexplicably) already has, since it has 60 + 60 chaff and flares. Go figure.

AUTO has been in for a while. Works well. The AUTO 15/30/45 loft cues should be coming soon. Flight Director is the third mode. Nothings been mentioned for it. Little used (even prohibited for JDAM use?) IRL.