Harker

RSET now resumes automatic ranking and moves the L&S to the trackfile with rank 1. So it does work as intended for now, since this was the intention when it was modeled. And until very recently, I also thought it was correct, I only discovered that particular detail very recently, after carefully reviewing some documents and discussing with an SME. I will report this as well. As for the different targeting behavior, this is normal and correct. If you only have the L&S, you can step it down the ranks with NWS/Undesignate, but if you also designate a second trackfile as DT2, then you are limited between them. This is intended, as designating a DT2 means that the pilot wants to focus on a particular pair of targets, and ignore (or de-prioritize) the rest. This makes much more sense if you consider IRL tactics, where pilots have specific designated targets and only shoot those, at least at the beginning of a BVR engagement. If you want to be able to designate more than two specific trackfiles, then you can either have only an L&S and step it, or you can use the TDC to designate a DT2 and then make it the L&S by using TDC Depress on it again (TDC Depress on DT2 makes it the L&S, without making the previous L&S the DT2 - if you want to keep both the L&S and DT2 and swap between them, make the DT2 and then use Undesignate).

There are different behaviors here, that can be correct depending on the OFP in question. The "an L&S must always exist" behavior is true for the software present on the F/A-18A, but not the F/A-18C (at least circa 2005). According to info I've found, our Hornet's MC should automatically designate the highest ranked MSI trackfile as the L&S upon entering TWS. But the official documentation is unclear on whether it should continue to do so, if that particular L&S is lost (as in, move the L&S to the next highest), while you are in TWS. I think that's the part discussed here. Also, RSET in TWS should definitely remove the L&S completely, not reset it to the highest ranked trackfile. This is an important difference between our OFP, and the OFP present on -A models, and it should help with airspace management.

The relevant info I've found does not indicate that setting someone as a Member should do anything for them. This is you, selecting a PPLI to display as MEMB2, in this case. Even if there was syncing, the only way for their jet to know you're actually MEMB1 (instead of 3 or 4), is to be able to sync the entire group. As I understand it, each pilot can set their MEMB list as they want. The Lead can also be distinguished by marking themselves as a Lead in the TGT DATA page, which will show an "L" next to their PPLI (that way, other flights can see all leads, and better keep track of different flights).

Hi, as I said in the mod page, I cannot see anything wrong, it works for me straight from the website. Can you say what the exact problem is? Which part of the mod isn't working?

Yes, the number values seem to have right text alignment, and both be at fixed positions, respectively. That way, the / between bearing and range always remains at the same place and it's easier to read the values at a glance.

Yes, both issues are related to STT with either 1 LOOK RAID or RAID enabled.

I've seen the 0 altitude thing show up when 1 LOOK RAID is selected in the DATA sub-page. Is that the case here?

The radar page at 19:10 also shows the Bullseye legend moved to the right compared to DCS.

@Tholozor is right. The TDC Bullseye data window should be moved to the right, to make space for the acquisition cues (AACQ, ACM modes). This is a picture from a recent Super Hornet professional simulator (not a game), so not at all the same, but the position of the cursor Bullseye data is clearly shown, and that part has not changed.

@Lord Vader I checked again. Ranking is based the threat the target represents. Regarding priorities, it goes: ROE identification (Hostiles > Unknowns) Inverse Time-To-Go (based on closing rate, ranks are determined based on the expected time to intercept) Angle-Off-Boresight, for AOTs (targets closer to ownship boresight are ranked higher) This order does not mean that a Hostile at 100 nmi will be ranked higher than an Unknown at 20 nmi. These elements represent weights in the ranking algorithm, but the main logic is "higher threat to ownship is ranked higher".

What I see here is the MC ranking hostiles higher, and then ranking by range. The ranking by range part is wrong it should be TTG), and has been reported. The ranking hostiles higher than unknowns part, I'm not sure.

With the latest OB update, detection probability (PD) was implemented. It's possible to not detect a target in a particular sweep, even if the probability is high. Based on the new trackfile memory scheme, you need 6 seconds without any target detections to enter memory, so you can miss a detection, and still have the trackfile remain perfectly fine.

You need to be in afterburner. It won't register the command if you're only in MIL.

Yes, TWS AUTO will now center the scan (azimuth and elevation) on the track centroid, and attempt to maintain as many radar trackfiles as possible. In its current state, it should always keep the L&S in the scan, and other than that, take into account the DT2 and trackfile ranks. It can also choose to convert a 4B scan to a 3 bar scan, or a 6B scan to a 5 bar scan, if it doesn't need the full elevation coverage.

The trackfile's position on the display is extrapolated between detections, using the stored target velocity, to present a smooth and continuous picture to the pilot. It's reasonable to assume that even if the target is detected in a closer bin, the MC knows the target didn't physically jump there, given a stable velocity. An alternative would be to present the trackfile always in the bin in which was detected, but that would disregard the extrapolation. That disagrees with the data I've found. However, the third option, that I have observed in one video of the Viper's radar (can't find any videos of the Hornet's), is to have the trackfile be extrapolated in its current bin, and once the target is detected in the next bin, the trackfile jumps to the center of that bin and begins its extrapolated movement there. That way, you only have jumps when the target enters another bin, but a smooth presentation otherwise. This might be the best of both worlds, as it leans towards the side of caution. Ultimately though, I've found no public info other than "the MC extrapolates between detections to give a smooth target presentation". NB. The same behavior happens in MPRF, but is harder to see, because the MPRF bins are smaller.

At least the default model shouldn't have the "ears", because it's not compatible/not used with the JHMCS, at least looking at pics online.

Hi, while Option 1 and Option 2 are optional adjustments for anyone installing the mod, both are necessary to pass IC. It was bad wording on my part, I updated the post to reflect that. Essentially, you shouldn't change anything in the main DCS World install directory, only do the part in Saved Games.

The GSPD entry refers to the last leg of the Sequence, e.g. if WP5 is the TGT, the GSPD entry refers to the ground speed you wish to fly between WP4 and WP5. If you have SEQ boxed, it should adjust the desired speed between the previous WPs in the sequence, so you can arrive at WP4 and then fly at the set GSPD, to arrive at TGT, at the desired TOT.

You assume everyone wants to use the AI. In my group, we follow realistic procedures, but we never contact the AI in the process. Most of the time, we have a human LSO and/or Marshal, on different frequencies. The last thing I want to experience is my hook not catching, or getting WO lights or a message, because I didn't contact the AI and flew in a way it recognized. The way people behave around the boat should be up to the server's moderators to enforce.

The radar is still operational and working normally, just doesn't radiate when the WonW interlock is engaged.

Reproduced following the steps in the video.

Yep. If you want to re-designate and you don't have a WP on it, drop a Markpoint by pressing the MK button on the HSI or SA, while you're still designated.

You're not doing anything wrong. The previous behavior was wrong and has since been corrected. CCIP should always turn to AUTO while a designation is present.

The OP is right, this behavior is described in the A1-F18AC-742-100, section 011 03, page 8, paragraph 64. To be precise, changing Bar setting should select the largest azimuth scan option, unless the pilot has previously selected a smaller azimuth setting manually. In that case, the manually selected setting is maintained, if it's possible to do so. Example: 4B scan starts with 40 degrees, pilot selects 20 degrees. Pilot switches to 2B, the 20 degree setting is maintained. If the pilot had not manually selected the 20 degree setting, then upon selecting 2B, the azimuth setting should automatically go to 80 degrees.

Yes, this has been corrected between the time the video was recorded and today.