Harker

The AWG-9 is also a much older radar than the APG-68(V)5 or APG-73 though, so it's likely to be much less capable in ECCM, whereas the -73 has dedicated options and modes for ECCM, for example. Radar power is not that relevant here, since a more advanced jammer can just manipulate the incoming radar signal's other characteristics and transmit a false return. Based on that logic alone (and without knowing more about the specifics of the AWG-9), HB's approach is reasonable.

INTL just alternates between HI and MED though, it's not a separate PRF. At least according to public docs and the way it's modeled in DCS.

I agree with this line of thinking. We only care about the system's output, not its inner workings, in DCS. An IRST seeker can very well be programmed like a radar, just with different parameters. So, we can certainly get an IRST that is capable of TWS-like operation and trackfile generation (the ATFLIR in the Hornet should also have that capability for A/A and contribute to MSI). Razbam already has a pretty nice hotspot tracker on the AV-8BNA, which can also give false positives. Did they program it like a radar, more or less? Probably. As for other limitations, Razbam again has showed that it's possible to model effects on sensors. Adding a detection coefficient based on LOS, to account for clouds between the player and the attempted target aircraft is not impossible. This is the same reason why people ask for MSI in the Hornet. We don't have the capability of such interactions in DCS now, but it's something that can be added, if the developer wants it to.

For the first part, the way DCS works, is that, if you have set WPs in the Mission Editor, then they'll be included in SEQ1 (up to the first 15 WPs). WPs that aren't set, aren't included in SEQ1. WPs that aren't set in the Editor aren't empty, they have Lat/Long values of N0 E0, which has a Grid reference in Grid 31N AA, so the Grid part should indeed not be zero for unused WPs. I think it's possible that you set up WPs 4-7 without having SEQ1 boxed and boxed it later, in order to navigate, thus losing access to WPs 4-7. It's a thing that anyone can do. I don't know of course, but this is my guess. For the second part, if 6 digits is all you're given, then of course that's all you can use, no argument there. If you want to get better coordinates yourself via the F10 map, you can switch the coordinate type displayed by LAlt+Y, if I'm not mistaken. This will cycle between LL in DDMM.mmm and DDMMSS.ss formats, as well as MGRS, so you can pick the one you want to use.

Sounds like your WP0-3 are in SEQ1, but WP4-6 are not. If you have SEQ boxed on the HSI/SA, then you can only access the WPs of that Sequence. Unbox SEQ (button press will unbox the current SEQ and present the next one, unboxed - you can cycle through the three available sequences like that). Or you can select SEQUFC on the HSI->DATA->WYPT page, then INS on the UFC and then select the WP you want to add to the current Sequence and hit Enter. Lastly, consider that 6-digit MGRS might be not sufficient for JDAM targeting. Consider providing a 10-digit input (if you have it). You can switch over to the precise coordinate format by boxing the relevant option at the bottom of the same page as mentioned above.

Clearly there's a large number of people who don't consider modern aircraft dull or requiring less skill. The amount of time you spend on learning how to operate the jet, its systems and weapons is arguably more than the time you'd need to become competent in flying a non-FBW aircraft (in DCS). The "learning phase" of a modern aircraft module is much longer than, say, a WW2 one. And that's very important for people who like focusing on the "study sim" aspect of DCS. You can make the capability overlap argument for most modules. Most aircraft of the same period are capable of doing the same things. With the amount of Cold War aircraft currently in DCS, plus those recently announced, the overlap in capabilities will be huge. People like various aircraft for various reasons. Lastly, you mention the blufor vs redfor balance, which is not really a concern in DCS and shouldn't really be. If a server owner doesn't want to include the Rhino (or the upcoming F-15E and EF Typhoon, for that matter), they don't have to.

The 746-100 describes the function of the TDC for the ATFLIR. The behavior discussed here is not mentioned anywhere in that document. The TDC is supposed to slew the pod, slew the offset reticle, and when depressed, create designations and bring up the offset cursor, when applicable. Slewing the TDC before depressing it and having the pod drift towards that direction is not mentioned anywhere. I can PM the relevant part, if needed.

The manual seems outdated on this one. Reset is not used to reset the radar settings for the current weapon. It's used to: Clear the L&S and DT2 target designations. Clear any trackfile ranking biases and resume normal trackfile ranking. Unbox the HITS option in TWS. It should also return the L&S to the highest ranked trackfile in TWS (TWS should always have an L&S and ranking should not be affected by designation, but this doesn't work in DCS now). Exit TWS BIAS, SCAN RAID and EXP.

Your INS alignment steps seem correct, considering you're flying with GPS available (post 1994 in DCS). The BIT status is probably a placeholder and not implemented fully. A lot of BIT items remain marked as not ready, with the corresponding systems working as intended. The BIT implementation will be updated at a later date, probably. As for why your JDAMs missed, it's hard to tell without a video or a track.

Yeah, sounds like the best solution. Just have a list in Module Manager, next to the module. Easy to use and everyone's happy.

Synthetic targets in SEA and GMT are correct for the Hornet, based on publicly available info.

Same. In general, I find that modules have way too many liveries in the vanilla game, that users are forced to install, even if they don't own the module and are never in missions with it. IMO, livery packs for modules should be optional downloads, like maps.

I also have the Super Taurus. You only need to set it up once in the software and save it, you can then close the WW software. You don't need it running every time you play. I did that and I no longer run it every time, but I have both axis and button functionality on that switch now. So I use the axis option in the Hornet and the buttons in the Viper. For the Viper, remember to hold the wheel up/down, as you assign the control, since the middle position also registers a button press (so DCS will register that, if you just flick it and let it go before confirming the assignment).

It should be able to perform NCTR using jet engine modulation, if your radar is able to look into the turbine blades from either the front or the rear. If the aircraft type is present in the opposing coalition only, it'll contribute towards declaring the target as a Hostile, via the ROE matrix. IFF works separately. If you run an interrogation and you receive no reply, it's also contributing towards a Hostile status. If you have two separate sources contributing towards a Hostile status, then the ROE matrix Hostile criterion is satisfied and the HAFU turns to Hostile. (If donors are present, the usual two contributing sources are a donor marking them as Hostile and your own IFF interrogation getting no reply, so getting an NCTR print is not required.)

You can circumvent that problem by not using the axis setting. Just use the antenna elevation Up and Down keybinds in the non-axis list.

They're just static "icons" added during the mission planning phase, based on available intel. Just drawings, if you will. Their position does not update based on RWR data or any other sensor. Sure, you can attempt to triangulate an emitter with multiple RWRs, but the IRL azimuth resolution is not as good as in DCS, so it's unlikely that the resulting position will be much of an improvement. It's also a risky endeavor, since SAM operators don't generally stay with their radars on, waiting for you to pinpoint their location. You can very well accidentally fly into a SAMs WEZ, if you're flying around or be ambushed by one. In DCS, as stated above, they'll show up for enemy air defense units that aren't Hidden by the mission maker. Their location is based on the unit's location at the time of you spawning in your aircraft. So, if a SAM moves after you spawn, its position will not update and that's correct. In some of my missions for our group, I like giving "imperfect" intel, so I might place a SAM group with Late Activation, that I never activate. It'll still populate the SA page with a ring (seems like a bug, but I take advantage of it). At the same time, I'll place the "real" SAM group somewhere close by and make it Hidden.

Options -> Special -> F/A-18C. The option is called "Realistic TDC Slew". To work realistically, you have to enable it.

Glad to hear it's working!

IFF gives a range estimate based on the time between the emission of the interrogation pulse and the receipt of the first framing pulse. Not as accurate as a primary radar, but oftentimes close enough to be correlated with a radar contact. As for the APG-73, it's not a PESA, it's a normal mech radar and an upgrade to the older APG-65. Also, the 742-100 clearly states that the CIT is a contributor to MSI and that IFF data is used to classify MSI trackfiles. It wouldn't be able to do that if it couldn't perform at least some basic ranging.

Hi, Out of the box, mods that are installed via the Saved Games method are incompatible with each other. But you can combine them quite easily into one mod. I'll go over the process of combining two mods, A and B, in mod B's folder. 1. Take the texture files from mod A, place them in the folder of the mod B and overwrite if prompted. 2. Open mods' B description.lua and make sure the lines from mod A's description.lua are also present there. If not, copy them over. 3. Select mod B from the drop down list, in Special options. For my mod to work, make sure to select the correct Reflection option as well. That's it. You might also want to rename mod B's folder into something else, since it's not representative of the original mod anymore. With the above method, you can have something like a full cockpit mod that uses my display textures, for example. As for the font and sensor video color, those still go into the main DCS folder as normal. If anything weird occurs, I'd double check that you did 1 and 2 correctly, that's where the problem will be, if there is one. Hope this helps.

To go back to the original question (since I typed this hours ago and forgot to post it), IRL, PP coordinates are loaded in the jet, they're usually not entered by the pilot via the UFC. I don't know how that loading process works, but it's possible that you can load up to 6 PP targets and they populate all stations (even if the different stations *can* hold different PPs, maybe they're loaded with the same at the beginning), so you need to select your desired PP target for each station. Another, better reason, is that you might want to drop two bombs from the same station at different targets, so bomb A to PP1 and bomb B to PP2. Or you might want to load multiple different targets at the beginning of the mission and then choose, based on the situation. Of course, I don't consider it reasonable for a pilot to manually enter 6 PPs for 4 stations, but if you consider that targets are loaded to the jet IRL, then the system makes more sense.

You can use any PP number, there's no difference between them. You just have 6 options for different coordinates. Target coordinates (PP and TOO) are individual for every station. You cannot copy PP coordinates from station 3 to station 7, for example. So, PP1 for station 3 is different from PP1 for station 7. Each station has its own set of PP/TOO coordinates. As for having two bombs on the station, they'll work the same, all that matters is the station programming at the time of release. You treat the two bombs separately, in terms of programming.

Looks like it'll be added, as per the last mini-update!

It should be, as long as we get correct Wind speed and direction data (HSI -> DATA ->A/C). It should be given based on a database generated pre-mission or entered manually by the pilot. In DCS, we can manually enter values, but AFAIK they do not affect the CCIP pipper. Since we're on the subject, the pipper should also be motion-corrected if you're tracking a moving target with the radar. The radar can provide lead calculation. Not implemented yet.

Your laser isn't firing (no LTD/R cue) and it's not even armed (no L ARM cue). Check the laser arm switch, next to the FLIR power switch. You can only arm the laser in the A/G mode and it'll be automatically disarmed after each use, so you need to flick the switch to Arm again. As others said, check that the laser code on the missile and the designation code on the FLIR as the same. Easiest thing is to leave the pod at 1688 and input that code on the missile.