Harker

A1-F18AC-742-100 does, however. That document describes the entire MSI system in detail and furthermore explains that for an MSI track, the radar can be commanded to "look" for it, based on existing track data. It also differentiates between raw radar hits and MSI tracks, when it comes to acquisition. It states that: The radar system, forward looking infrared (FLIR) system, data link, high-speed antiradiation (HARM) missile, and overlay controlled stores (OCS) are used to provide sensor inputs to MSI. The radar can attempt to acquire a track present in the MSI system, even if it's not detected by the radar yet. We already have this functionality in DCS, with the LITENING Radar Slave function, where you can point a silent radar to an aircraft that is tracked with the TPOD. As far as the radar is concerned, the aircraft tracked with the FLIR is an off-board track. This is because the FLIR is part of the MSI suite (and should be able to create a track file too). So, we're halfway there. All that remains is to expand the same functionality to data-link tracks (alongside the rest of the MSI and radar functionalities).

There is no TPOD to IMAV handoff. When uncaged, the IMAV will simply look at the A/G designation (diamond), that's all. It's simpler than you make it out to be. If the designation is on/close to the target, good. If it's not, you need to update it and make sure it is, by using the TPOD offset cursor (if you want to stay in AUTO/PTRK). Unless I'm mistaken, the ATFLIR should be able to automatically update the designation in AUTO, but we don't have that capability yet in DCS.

Good to know it's working correctly, thanks for checking.

Actually, unless something changed, the criterion was whether the wing handle was locked (in) or unlocked (out). You can have deployed wings, but if you leave the handle unlocked, you can have sticky NWS HI. This is in DCS, I don't remember if it's different in IRL.

Well, yes and no. The way he explained it, the main thing involved is maneuvering in a way that the missile tries to intercept you and then pulling in a way that forces the missile to try to correct very late in the terminal, while simultaneously entering the notch ever so briefly. If timed well, the missile can get confused just enough for it to reacquire too late and be unable to correct enough, causing an overshoot. He did not comment on whether chaff and/or ECM are involved. I'll ask when I get a chance, but given the nature of the conversation and the fact that he's in active service, I might not get any useful details that I can share.

I recently asked an IRL fighter pilot friend of mine "is it possible to survive an AMRAAM shot from 6 NM away? If so, how?" Without getting into much detail, he explained that, if you time your defensive turn perfectly, you can take advantage of the interception logic of the missile and make it overshoot. It's not easy, obviously, and the chances of failure are high, but this was all to say that there is a small chance to survive by kinematically defeating the missile, which sounds exactly like what this MiG did. He cannot comment on ECM, other than to say that its effectiveness depends a lot on the ECM and ECCM used by the two fighters. An ECM technique can have almost zero effect, if it's not the correct one or if the other platform is using the correct ECCM to counter it. Or, if used correctly and without ECCM to counter it, it can render radar useless. Depending on the jammer and the HMI, the operators have to dance around each other's techniques or the jammer does it by itself. For chaff, he simply said that it's only effective in certain circumstances, since target selection algorithms can easily reject chaff in most cases, which is consistent with what people say in this thread.

You can use EXP2 or EXP3 to break out the bricks. Whether you can FTT the one you want is another story, because the radar will still lock on the strongest local return, but you can easily switch TDC priority to the TPOD and use that to refine the designation.

Same here. I actually hit the water once and almost hit it 2-3 times more since 2.7 dropped. All were cases where I couldn't tell how high I was, without referencing instruments. Prior to 2.7, I didn't have that problem.

Trim in the Hornet is much more controllable than in the Viper. No issues there. You can easily find tune the roll trim for asymmetric loadouts (which are common in the Hornet) and the pitch trim for landings.

The TDC showing only on the priority display was already shown in Wags' ATFLIR video, so we can assume it's already implemented in the dev build.

Unless I'm mistaken, SEA should be able to display both static and moving vessels as synthetic bricks. It certainly does so, in DCS. I flew a mission 2 days ago where I found stationary ships with SEA mode.

Wrong, it displays moving and stationary.

The radar works fine for me as well. The detection range is reduced, but it was brought down to realistic levels. The problem with MP is that not all radars are adjusted accordingly, with the biggest offender being the Viper, which has very unrealistic detection ranges. TBH, such things should be handled at a central level and simultaneously for all modules, to ensure that all radars are operating under the same principles and limitations. Even better, ED should just have a general radar code, where they plug radars in, with everything controlled by parameters specific to the radar itself. Unfortunately, that'd mean that third-party devs couldn't implement their own radar code, but if that system is done well, maybe it wouldn't be a problem. Perhaps third-party devs could work with ED and introduce improvements to the code as well. And to go slightly OT here, the above logic could and should be applied to most things in DCS, because all aircraft, sensors etc should be subject to the exact same physical principles and limitations.

TWS MAN does not follow the TDC automatically, like in the Viper. You need to depress the TDC in the new azimuth you want to center it on. Every time you want to change the scan center, you need to depress the TDC. Or you can use SPOT mode, like Tholozor says, which ties the scan center to the TDC, like in the Viper, but limits the scan to 22 degrees. TWS AUTO automatically centers the scan on the L+S target, in both azimuth and elevation. If you depress the TDC while in TWS AUTO, you'll enter BIAS mode, which moves the scan center towards the azimuth you depressed at, but makes sure to keep the L+S and DT2 tracks inside the scan. You can switch back to MAN or AUTO with the pushbutton option. As for the constant pitch up behavior, that's a bug encountered if you take off with flaps to AUTO. If you use HALF or FULL flaps during takeoff, it'll work correctly and the aircraft will automatically trim in pitch for 1G flight, as soon as the gear is up and flaps are set to AUTO in the air.

You can switch between the feeds by selecting the appropriate channel for the datalink pod.

+1

Good to hear, thanks.

Update: I think it only shows for the currently selected WP. But there are videos that show multiple WP symbols visible at the same time, all using the ATFLIR.

For both this and your other issue with the Maverick, make sure that your materials.lua file is the default one, it was updated in the last patch. Remove mods, repair and see if that fixes the problem.

I posted it there. No idea why it was moved to the wishlist. [emoji52] I wasn't asking for the SETUP options to be implemented, I was pointing out a bug.

The Mirage we have should be the S5 variant IIRC, equipped with the RDI J3-13 radar.

Yeah, I also don't use it myself. I made it for fun and figured folks might like it. Thanks! You should be able to just use Verify with Steam.

Could be my mod. I suggest you run a repair, if you didn't save a backup of your FA-18C folder in Mods. The file controlling the TV/IR color (and A/G radar video) is "flir_texture.dds", located in DCS World\Mods\aircraft\FA-18C\Cockpit\IndicationResources\MDG\

I'm having a problem with the ATFLIR waypoint symbol. A lot of the time, it's not showing. Sometimes I'll get the symbol for one waypoint, but not the rest. Sometimes I won't get it for any waypoint. Am I missing something or is everyone having the same problem?

Correct. The options on the setup page aren't working anyway, but the buttons shouldn't be activating options from the previous page, regardless.