Harker

There is a brightness knob on the lower part of the UFC, labeled AOA, under the HUD brightness knob.

It's not correct, NWS must be disengaged, it's clearly stated.

The HUD cursor is fairly precise IRL, as it can be used for targeting and INS updating. Not every Hornet carries a targeting pod all the time and they can employ dumb bombs in AUTO just fine. It may not be accurate enough for JDAM employment, but the FLIR isn't either for the most part, IRL. But its sensitivity is not the point here, it should always point exactly at the designation, since the MC draws it exactly where it determines the designation to be, using the INS and perhaps other sensors, such as the FLIR or A/G radar. The limiting factor, if applicable, should be the HUD resolution.

Try to keep the crosses aligned as much as possible and *press and hold* the Cage/Uncage button, in case you're not doing so.

You'll be able to create a full WP by slewing it on the HSI, once Waypoint Slew becomes implemented. (DATA->WP->Actuate and hold TDC->Slew over desired position->Release TDC).

Yeah, it has become really easy to notch both missiles and radars (at least the F-18's) in look down conditions, even if the target is at high altitude, but below the horizon.

We do, in the Harrier. Well, it's the G4 only by name, a lot of the options aren't implemented, they don't do anything.

It's a bug introduced a couple of patches ago, all units and statics do not show up on MAP mode.

In your Users\(username)\Saved Games\DCS (or DCS.openbeta)\Tracks\Multiplayer. But do consider submitting a short single player track instead. Longer tracks, especially MP ones, are both unreliable and very time consuming to go through.

I'm thinking the same, leaning heavily towards the -X% per look-down degree. This needs to be revised, our radar should have a look-down, shoot-down capability, after all.

I appreciate the input here. I do not disagree with you one bit, but we're talking about different things. How the jammer works (in terms of signal processing and transmission) is not the point here, we're talking about the lack of a feature that determines whether the radar or the jammer gets transmission priority. ED does not need to understand anything about the actual operational principles of these systems (although it'd be good if they did), they simply need to program the implementation a little different and add functionality to an option in the RDR ATTK page.

The Hornet's radar should definitely have look-down capability, it's just that ED has modeled an unrealistic detection range drop for look-down, that only takes how much below the horizon the target is. In DCS, it doesn't matter if the target is flying at 20,000 ft or 5 ft above the ground. As long as it's below the horizon for your radar, you'll have a very hard time picking them up and it'll often be impossible, which is very unrealistic. So, right now, I can't offer good advice on how to stay high and detect low. Maybe consider going to a medium altitude, so the above "feature" has a lower impact.

I mean, I'd prefer to see that detail on units that will actually be seen up close, such as aircraft whose models are 15 years old. A WW2 SPG that will most likely be just a target does not need to have that amount of detail. I just hope the LODs are good, for the sake of performance.

Agree, the radar should attempt STT with the mini-raster, upon TDC Depress, only if the TDC is over an MSI trackfile (with or without radar contribution).

While you're not wrong, in the specific case of the Su-30, the RCS is pretty big.

The OP has a point, the MFDs and canopy, for that matter, could do with a facelift on the Roughmet side. Since 2.7, good reflection effects are actually possible. I might also try my hand at modding them myself, in the meantime.

I'm also adding my own findings to this. It appears that the issue only affects the MAP video. Both AI Units and Statics are not shown. FA-18C_AG MAP radar does not see user placed units and statics.trk GMT and SEA work correctly and will display synthetic bricks for moving vehicles and stationary+moving ships, respectively. FA-18C_AG GMT radar works normally.trkFA-18C_AG MAP does not see moving units.trk So, the radar sees stuff, they just don't appear on the A/G MAP video. Seems like it's only showing the unaltered map and disregarding any additions by the user. Same behavior is observed on the JF-17. Note that I removed all mods in both the install dir and the Saved Games folder and ran a Repair, in order to test this. DCS was as vanilla as can be. Open Beta 2.7.6.12852. Tested on the Caucasus map. Tracks and screenshots attached.

I had this, but it's only a problem in the ME, both in top down view and livery viewer. In-game, it shows up correctly.

As of DCS Open Beta 2.7.6.12852, any changes in files present inside the \Mods\aircraft\... directory will lead to a failed Integrity Check for Multiplayer. As such, if you want to pass IC, you cannot use the white DDI font and the grayscale FLIR/MAV/AG radar video. Please perform the steps outlined in Options 1 and 2, below. Updated the OP as well.

You can designate an MSI trackfile (with or without radar contribution) as the L&S, so you can already get all related targeting info. But at that stage, the MC does not pass on data to the missile (you have a NO RDR cue under the TD box on the HUD). Radar contribution is necessary in order to enable a radar guided missile launch. So, the radar becomes a necessary part of the MSI system, only if you intend to launch a radar guided missile. There is both video evidence of the NO RDR cue, as well as multiple distinctions between MSI trackfiles with or without radar contribution and L&S/DT2 with or without radar contribution in the 742-100. You don't need the radar to build a full MSI trackfile, this is only a thing in DCS. In fact, one thing we're missing in DCS is the radar contribution circle for MSI trackfiles that your own radar also contributes to. Visually, our trackfiles look like the IRL ones *without* radar contribution. So you still need to detect a target yourself to launch at it, but you can build full SA on it and position yourself correctly, before you detect it. By the time you do, you can launch immediately, if you wish.

Given the same target RCS, the Hornet's radar in HPRF should have an appreciably better detection range over the Viper's. And if MSI is properly added, it'll be possible to designate a target for launch and perform all necessary maneuvering, without needing to actually detect the target yourself, detection becoming necessary only for shot convent and missile guidance. One thing the Viper might be better at is MPRF detection, which becomes more important as you're entering shot ranges, as it's less susceptible to break locks and provides more accurate target range. But, admittedly, I don't know much about the Viper's MPRF modes, so there might not be a difference there, in the end.

You have access to two "Altitude, Altitude" warnings, a BARO and a RADAR one (max setting is 5,000 ft), accessible from the A/C page. The BARO is set to 5,000 ft by default and the RADAR is set to 0. The RADAR one will also default to 0 automatically when you land, upon WoW. There's a longstanding issue in DCS though, where it'll continously default to 0 while you're on the ground (it should do so once upon first detecting WoW, not continuously), so it can only be set in the air.

Radar altimeter, using the knob, by your right knee. Just to the right of the wing fold handle and the BuNo plate. When you start from cold, it's off, so you have to turn it on. When you start from hot, it's already set at 500 ft by default.

Good thing this is the F- 18 then and trackfile processing happens all the time. This is well reported. Even more, MSI processing should not stop between RWS/TWS and STT so any transition should be seamless (and you should be able to select a different MSI trackfile as the L&S, while in STT). Processing should only stop in ACM.

Reviewed new data and this report still stands. New track for the Maverick, with some more attempts and slewing. FA-18C_Maverick does not slave to Offset_2.trk