Swift.

Currently you are able to enter two different codes for Mode3 and ModeC IFF, this should be the same code carried between the two settings. Mode3bug.trk

Correction, disregard. It was my lack of understanding of the IBIT process. Impalor, did you try going into the BIT format and pressing STOP (OSB 10), maybe even going into the Displays sub menu (PB 11 iirc) and then STOP (PB 10)?

Anecdotally, I saw this same failure state when testing the BIT modelling the other day. I will try and repro.

I'm curious, having never seen what you describe happen, what does it look like in the HUD when the ghost L&S is present as well as the new L&S that you generated with the H/LACQ?

Ghost cursor, whats that?

Oh BTW, that 'decrease approach speed by 1 kt per wingtip aim9 loaded' doesnt apply to DCS.

Interesting, did you have a chance to test with HACQ? I'm wondering whether this is specific to the acquisition mode.

With anything AG related in hornet, all you have to do is create a TGT designation and all the sensors will slave to that point. TGT designation can be made with any of the sensors; TPOD, HUD, JHMCS, INS, Radar, etc.

Slaving to the FLIR? You sure you don't mean slaving the FLIR to those tracks?

Interesting, I thought it should automatically designate the TGT assigned waypoint when you approach it. You have a track or something we can take a look at?

Are you assigning wpt 2 as the TGT in the SEQUFC menu?

A neutral F/A-18C is being ID'd as hostile, presumably by the mode4 IFF response. Tracks attached, NCTR off and NCTR on. NCTRoff.trk NCTRon.trk

The way GSPD used to work at least, is that it sets a fixed target GS for the waypoint sequence leg immediately preceding the target waypoint. What you might be seeing is what happens when you dont have a preceding leg? Do you have more than one or two waypoints in this flight plan?

When entering the ACM radar modes from TWS whilst having a pre-existing L&S, the L&S will be maintained as a 'ghost track' that appears at a fixed location from aircraft. This Ghost Track will prevent the ACM modes from creating another proper L&S, essentially bricking the radar. Track attached with neutral aircraft located off the nose with an aspect of about 150, crossing right to left, range 30NM. NB, this bug is also exhibited with an L&S generated from RWS, track attached. TWSbug.trk RWSbug.trk

This is correct, and iirc its with weight on wheels, not rearm.

Out of curiosity, are you comparing to tracers in DCS?

These work, at least partially, in SRS. Just FYI

This is something I'm very curious about too. I do hope the the new weather engine will affect ground radar performance.

Are you on the red coalition perhaps?

Clouds eh? Aren't they those things that show up on AG radar, QED would hinder any kind of targeting one might attempt through them?

Don't feel the need to justify the existence of AG radar for APG73 by devising convoluted scenarios to use it in, they certainly don't bother IRL.

Is the MIDS on?

Not yet, and it works slightly differently to how hog does it.

The furthest away track is a speedboat fyi. http://skysailtraining.co.uk/dipping_distance.htm Take dipping heights as a simplified example. At 10ft (shown), an object would have to be 95m tall to be seen at 24NM. Obviously with radar you get lensing and such but it serves as an example I think.

Youve been able to put multiple player groups down for at least as long as hornet has had MIDS. What I don't think you can do is have an AI lead and Human wingman, but I havent tried that.