Jak525

TDC depress makes a TGT designation which the Maverick seeker slaves to.

Must be a Growler thing. Unfortunate because I can't begin to fathom the tactical advantage we'd get from such a feature.

Quite sure it was only introduced with the Super Hornet, or maybe very late lot Legacy Hornets.

yeah, the CCIP mode is complete. The only thing not done yet for the 'original' weapons - guns, rockets, dumb/laser bombs - is Flight Director (FD) bombing mode and the ability to slave the gun/rocket CCIP reticle to 5,000ft range with Cage/Uncage.

Just because you know it's a bandit doesn't mean your aircraft does. You will need BOTH a) a negative IFF response, achieved by: 1. cursoring over the trackfile and Sensor Control Switch depressing 2. simply cursoring over when in Range While Search 3. by SCS depressing when in Single Target Track b) one of these: b1) offboard hostile identification b2) NCTR print of hostile aircraft Alternatively, you can cursor over the trackfile on the SA, press Pilot Identification (PLID), and manually assign hostile status.

When not in A/A master mode - in other words no A/A weapon is selected - Launch Acceptable Region cues are still shown on the RDR ATTK format for trackfiles (the last selected missile it seems). I would assume it should show no LAR at all outside of A/A master mode. Track attached. LAR bug.miz.trk

Track is now attached

Note that if your helmet is on, Helmet Acquisition (basically boresight) is only 5nm too. You can press the Sensor Control Switch up for more than 0.8 seconds to get Long Helmet Acq which goes out to 10nm.

See my explanation on thread page 2

@Moafuleum Yeah this is just about the TDC not working with those functions. @Don The figure I mentioned, 67 on page 168, does illustrate the fact you should be able to use it with these options. You can see the control zones and the 3 PRF options displaying as if the TDC was over them.

When the TDC cursor is slewed outside te tactical region the BRA indication on the RDR ATTK format still updates. I am pretty sure it should disappear or just show the last valid BRA. RDR ATTK BRA bug.miz.trk

I think in some way. Might not be coordinates but I think you'll be able to show your TGT designation on eachothers SA format. That "TXDSG" option has something to do with it. Wags spoke of it briefly.

This has been reported before, you can actually always access the FLIR format by pressing the corresponding button even if the FLIR text doesn't show. Probably will be fixed when the TGP is actually in, at the latest.

In the end your SA page is just a "trackfile viewer" presented more intuitively than your RDR ATTK format, with some extra features such as SAMs.

From what I can determine SA is designed for A/A stuff, HSI is for navigational or A/G stuff. SA, of course, has some navigational capability too.

No, if a trackfile is both ownship and DL or just DL, then it's shown as a HAFU. Otherwise, the trackfile isn't shown and only the corresponding raw bricks are.

I do not think the former is correct. Pretty sure you have to use the DDI pushbuttons. As for the laser, it can be fired automatically but yeah there is also a manual option that allows you to use the trigger. You can see the trigger option on the screenshot Wags posted, actually, in the Mini-Updates.

I believe this indicates the laser is being inhibited from firing.

The RDR ATTK format has a handy feature where you can use the TDC cursor to select some options. This is outlined on figure 6 7 in the DCS F/A-18C manual [pg. 168]. However, a couple options do not work as illustrated. All functions work except the pulse repetition frequency option and the RSET option. This is demonstrated in the .trk: when hovering over the PRF option, the three available options of HI, MED, and INTL should display similar to how it works with the bar and azimuth setting (as shown in the manual). Additionally, the RSET button does not work with the TDC - this is demonstrated after I designated a Launch & Steering trackfile and then tried hitting the RSET button with my TDC cursor, and the L&S remained designated. RDR ATTK HOTAS bug.miz.trk

Yup that was the main source of my research. And yeah; most cases just use the main reticle to point and shoot. But the FORESIGHT is still kinda cool for maximizing the range of the gun.

Correct. I'm talking about an indication on the radar format that tells you which mode you'll go to when you press Undesignate.

Aa far as I know there is no declutter option. The horizontal lines just give you an idea of how far the target could maneuver. The lines move as the target does so no, you can't really aim with it. It's just to prepare you for how potentially far the target could get away. They indicate how far he would be by the time one bullet would take to reach him if fired then.

Based off some stuff I've found and even some illustrations in the DCS Hornet manual, I believe there should be a "RTS" (return to search) option while the radar is in Single Target Track, just like there is in ACM mode. Under RTS should be the mode that the radar will return to - normally the last entered search mode RWS/TWS/VS, or if the gun is selected, GACQ (GACQ is one example illustrated in the DCS manual; this ties into another bug thread I made on GACQ behavior). EDIT: some more detail. see figure 7 1 on page 181 Point 3 "Return To Search (RTS) Indication. When the RADAR is in STT mode, the search mode that is entered when an STT lock is disengaged is displayed." (in this case, GACQ is displayed since the A/A gun is selected. Again, this ties into the other bug I reported.) figure 7 5 on page 189 Point 3 "Return to Search (RTS) with RWS to be the return mode." figure 7 7 on page 197 Point 1 "Return to Search (RTS) Indication. Single Target Track (STT) mode with Return to Search (RTS) indication."

LTOD doesn't function the same way as ZTOD. It just sets the LTOD in the IFEI, it doesn't pop it up on the HUD like the ZTOD does.

OK. Here's the deal. The FORESIGHT and the circle reticle are entirely separate. They are used separately, not in conjunction. The reticle is "point and shoot". Based off the information on the target it computes the lead angle required to hit it. Regardless of what the target is doing, if you place the dot on the target you should hit the target if the trigger is pulled while the dot is on the target. (Assuming the target doesn't change its maneuvering while the bullets are flying) The FORESIGHT, on the other hand, is another way of aiming entirely. It is designed for long-range (for the gun) engagement. Essentially: - when the target is on your own plane of motion (as in following your own path of travel), the 1G "+" symbol should be placed over the target to hit it if the target is pulling 1.0G. The same applies for the 9G symbol, if the target is pulling 9.0G. If the target is pulling in between 1 and 9G, then the right place to aim is somewhere between the 1G and 9G symbols. In other words, these provide fixed lead angle indications based on what G the target is pulling assuming it is on your own plane of motion. The FORESIGHT is no good if the target is not in the same plane - e.g., not heading more or less directly away or at you. In other words, the 1.0G pipper only works if the target is on your own plane of motion pulling 1G. This is opposite to the other non-FORESIGHT reticle which computes the lead angle dynamically, and so regardless of the target being on your own plane of motion or not, and regardless of the G's it's pulling, the dot should be accurate. As mentioned, the FORESIGHT doesn't jitter as much because the lead angle isn't computed. The long lines part of the FORESIGHT cue are the maneuver lines. These indicates the maneuver potential of the target to maneuver outside your own plane of motion at 9G; essentially, if it were to roll 90 degrees left or right and pull 9G. The line length is based off of how far the target could maneuver at 9G at the time of one bullet in flight. Hope that makes sense... I will be updating the wiki with the correct info.