The datalink and the way itâs presented both on JHMCS and displays is truly incredible within the context of DCS. Wags having referred to the Viper as a slightly ghetto Hornet is most true in this area.
I wholeheartedly agree that the Hornet, although incomplete, has depth and layers that encourage continuous learning.
@chipwich when you set into mastering bullseye, a couple notes:
-the jet will come preloaded with WP59 set to the bulls location, if set by the mission planner (BD does)
-you still must tell the jet to use WP59 (or any WP, for that matter) as the bullseye by following HSI-DATA-desired WP-A/A WPT
Once selected; the following will occur:
-SA Page, w/TDC Assigned - will display cursor OR TUC (target under cursor) bearing and range from Bulls at top left. Useful trick here, you can gain the same functionality on a datalink track when TDC is not assigned to SA by using the STEP function.
-SA Page, bulls WP will be permanently displayed with a fixed North reference arrow
-ATTK RDR Page WITH TDC assigned, cursor will display cursor OR TUC bearing and range from bulls at top left. Important note: when TDC is not assigned to ATTK RDR and a track is not set as L&S, the bulls display in top left will default to the âstowedâ cursor position (the upper left quadrant default position), this can be deceiving because of course nothing useful is usually at that location.
Off the top of my head, ownship B&R from bulls is displayed at bottom left on ATTK RDR.
Edit-oh, and bulls WP location will now be displayed on ATTK RDR with a north reference arrow.
When navigating using Bulls, note that the cursor on both pages is not ground stabilized, i.e. as you turn towards the area of interest your cursor will rotate with the motion of the jet. It takes manipulation of the cursor to maintain indication of desired location. This can be overcome by setting an offset point from the bulls WP, or by slewing the TGP to desired location and designating a target point.
Hopefully that all makes sense, Iâm posting before coffee