Santi871

The track is corrupted for me, the view just shows the airfield. Could you try to reproduce it in a quick mission? One thing I think might be happening is that your scan volume settings (azimuth/bars) are making the update rate on the TWS tracks too slow and they are timing out.

I'm checking in today's OB and only seeing the friendly 15E. Can you check if it's still happening?

Do you have a track replay so I can see what's happening? Also, for the cage/uncage behavior, it's still being tweaked :)

If it happens again, could you show the issue with a track? thanks!

Lost will flash when firing outside of Rmax, although now we can hit some shots outside of Rmax due to the new amraam loft mechanics and so on and the DLZ having not been tuned to account for that yet, as far as I understand.

Lost is an assessment that the missile isn't going to hit the target, whatever the reason may be. There's a lot of reasons for that, not sure which ones are modeled and which ones aren't, but right now it's a bit buggy due to the 120 in particular getting FM changes and the DLZ not having been tweaked to account for it.

Please make a new report, this one will get marked as reported and then separate stuff like that will get buried. Cheers.

The issues with not being able to release bombs in AUTO PP and the missing IZLAR in the HSI are reported, cheers. As for the FLT time calculation being off, when I test in the dev build it's accurate down to the second in all of your examples, so I think it's safe to say it's fixed internally.

I'll look into this, thanks for the detailed report, just been having a relatively busy week.

Yes, the VVSLV option is only available when no target is designated.

You're right, I meant aging targets not being updated by the radar. Same thing. The other issues are reported as well.

Okay, I'll write it again in hopes of getting my point across more clearly. I don't know if it's possible, or rather, if it's a simple bug fix or an "overhaul" type of thing, to have an amraam (or any fox3 or other missiles that have INS for that matter), to guide to where the radar thinks the target is. I've never seen any behavior in DCS that shows it's possible. All I've seen is that either: - the radar sees the target and the missile guides to the real position of the target, or - the radar doesn't see the target and the missile guides to where the target was last seen Currently, the Hornet's track memory is counting as the radar seeing the target. With the Hornet's (and Tomcat's) track memory, we're introducing a 3rd possible state: - the radar doesn't see the target, but is estimating the position of the target (as a position that may or may not be the real target's position), and the missile needs to be guided to this position And that's what I don't know is possible or not. Hopefully I make more sense now.

You misunderstood what I meant - please re-read. I'll edit to make it a bit clearer.

I need to ask if it's possible to fix this currently - ie if it's possible to make the amraam guide to an arbitrary point in space, as a middle point between guiding to the real target location and completely losing midcourse updates. No idea if the engine supports something like this.

The functions of undesignate shouldn't change regardless of what screen the TDC priority is on, it depends only on mastermode and wow/woffw

Indeed, it's reported. Thanks!

this bug was already there before wednesday's update (reported)

The correct (and WIP) function for cage/uncage is LST mode toggle. What do you mean like IRL?

What Nineline said seems pretty clear to me. They wanted to model a Litening before the ATFLIR, and the best available Litening docs were for the Spanish Litening, and then the ATFLIR will be made with US docs. Like other people said, cheek mounting the Litening is already wrong as far as USMC service is concerned, but I don't think snowballing that into a huge argument that the entire ED Hornet is all sorts of wrong and that it should get tons of other export weapons/systems makes much sense.

When in undesignated condition (no TGT), the targeting pod should be in snowplow mode. In that case, double clicking undesignate button within 1 second is a HOTAS way to toggle VVSLV mode (WIP)

The correct cage/uncage behavior is toggling LST mode. What is the designate/undesignate confusion?

As an aside, if you look in the video falcon_br posted yesterday, there is a north arrow :) it is just the coordinates readout that is missing

It is accurate behavior. The MC will de-arm the laser after passing the target to prevent unnecessary/accidental laser fire.

Considering AFAIK the US is the only major user of the ATFLIR, I assume the ATFLIR symbology will match USN Hornet videos better

reported the wonky bars behavior after using GACQ, cheers