Harker

The buttons I'm talking about, in the SETUP sub-menu, do nothing, they're not implemented. But they still shouldn't activate functions not assigned to them, they should just produce zero output.

When you enter the ATFLIR SETUP menu, there are a number of options that do nothing. Pressing the OSB's next to them will activate the function that corresponds to that OSB in the main ATFLIR page. In my example, I am in A/A mode and I switch the ATFLIR between L+S and BST slave, while in the SETUP menu. DCS 2.7.0.4625 Open Beta. Track attached. FA-18C_ATFLIR_SETUP_Buttons.trk

Both you and Nicola are correct, there isn't and never was a contrast-based system in place. Same as radars, there isn't an actual radar simulation. It's all tables and parameters, that if tuned correctly, they give the correct results. The problem here is that, in the last update, some rework was done in the Hornet (that wasn't done in other modules - at least not the same) and those parameters got messed up.

I would assume your radio volume knobs in the cockpit.

Tested with both 512 and 1024, no difference.

That did it, thanks for the suggestion. At least I know it's working on my system. It's strange though, the contrast was really good before and it was in IR, so it should be picking it up just fine (I know DCS doesn't actually use contrast, but it seems they added a very restrictive filter for successful track). What's more, it appears to only be an issue with the Hornet, other modules track fine in the same conditions. EDIT: This doesn't make any sense. Clear sky, noon, IR auto-tracks from more than 12 NM away. Same conditions, midnight, it doesn't track at all, no matter the distance. The FLIR picture is equally clear, with good contrast, in both cases. This looks like a filter that was applied for the TV mode, working in IR mode as well.

The boxes are a scale, used to tune the image. They show up when you have SETUP selected. Deselect it and they'll go away. As for using AUTO in A/G mode, I had zero success, both TV and IR, all down to 2 NM. Works fine for A/A. LITENING PTRK doesn't work either... Other modules work fine (tested A-10C II, AV-8B).

Painstakingly recreated the airflow pattern and its effect on the FM

I don't think so. I've been flying with random failures enabled for years and I haven't experienced any in the Hornet.

Oh wow that's fast! I assume the real TDC is pressure-sensitive, or changes its speed a lot after a point of deflection (like, lower gain until 80%, much faster gain after 80%)? How is it possible to make small adjustments in order to select contacts etc otherwise?

I can't check right now, but I don't think it resets at all. It's very handy, actually, you can bump and smoothly continue doing whatever you were doing. You can also change the range by depressing the TDC when it's over the increment/decrement arrows, although I never use that. For reference, I have a pretty fast TDC speed, so it's easy to move the TDC across the display and bump quickly. OTOH, it makes slewing the A/G designation with TDC to the HUD, extremely inaccurate, but I don't really use the latter.

Not like the Viper. You need to move the TDC out of the tactical area and back inside in less than 0.8 seconds, IIRC.

Genuine question, why not use the TDC bump to increment/decrement the radar scope range? I see a lot of people do exactly what you do, bind the range to HOTAS buttons and I'm just curious. I actually have become very comfortable with adjusting the range with the TDC bump. Do people find it difficult and/or annoying that they have to do a quick out+in, instead of just going out, like the Viper?

I recall ED commenting that the new prop effects actually improve performance, I think it was either a YT comment or a FB comment.

If you start it early enough, CPL should fly the jet to intercept and settle on the courseline, towards the waypoint. AFAIK, you don't get to choose the distance this will happen, unless you are in a position that will make it happen, when you engage CPL. If you want to arrive exactly 10 NM from the waypoint, on the courseline, you should either use another WP or an OAP (offset), which will come after 2.7, and fly towards that first, with CPL.

This is correct, according to everything I've read about the AMRAAM and according to a discussion I've had with an actively serving pilot. What's more, the fighter-missile datalink does not get severed at any point (by design, it can still happen if the fighter loses the target or the datalink is severed unexpectedly), and the missile can use it to help refine the expected position of the target, alongside its gates. Which means that a notch becomes extremely difficult, since you'll have to notch both the launch platform and the missile, in order for it to completely lose you, potentially increasing Pk. In DCS, as soon as the missile goes active, the datalink connection is severed.

Are you sure your WPs are on ground level? If not, the TPOD will just look at a point in the air. The default waypoint elevation is 2000 meters, in the Editor. You can easily set ground elevation by inputting zero and it'll automatically correct it to match the ground.

You might want to take a look at this, might help answer some of your questions. https://forums.eagle.ru/topic/242391-investigating-baro-altitude-value-for-calculations-not-taken-from-cockpit-altimeter/

Keep in mind that if you delete extra liveries from CoreMods, every time you update or repair DCS, it'll re-download them.

No argument there.

Reproduced. Track attached. FA-18C_TOT_midnight_ZULU bug.trk

I'm in favor of this. Like the OP, there are liveries on aircraft that I never use and never see. The CE, Yak-52, F-14A, Sabre, MiG-15, MiG-19, I've never either flown or flown against. I'd only be interested in the Iranian F-14A skins, for the appropriate variant. SSD are cheap, sure, but that's still no reason to bloat them with unnecessary data that'll never be used. Leave livery packs as an additional installation option in the Module Manger, everyone's happy. As for MP servers, everyone can use whatever livery they want, but if other people don't care about the aircraft, they also won't care about its livery. I imagine people flying in the Cold War server would install all of the liveries I don't want, for example, so that solves the issue with MP servers.

Hey BN, what do you mean by considered? It's a standard mode of the radar and integral to low level IFR. Even the older APG-65 had it. Is there a chance that we won't see it before the Hornet is completed? (I'm not talking about exiting EA, I'm talking about the Hornet being considered complete). If it's an issue of being unsure about our radar supporting it, I can PM info.

TA is part of the radar suite, it should definitely come (along with VS and PVU). It was also available with the older APG-65.

DCS doesn't simulate shrapnel at all, unfortunately.