Muchocracker

There was. It's left crtl + shft + alt + S now. It used to be only alt + S i think.

This is the F/A-18C bugs forum. F-16 bug reporting forum is over here https://forum.dcs.world/forum/333-bugs-and-problems/

Known issue

ED has the "timeframe" standard. We can all argue about that standard for as long we want. But that's what it is. To that standard, the GBU-54 did not even exist within that date and wasnt introduced onto the legacy hornets till 2012. This is a pretty cut and dry discussion. I don't understand why this keeps coming up.

Observed in your track and reproduced in my own. Internal reports made. FACQ seems to work okay and will command STT on TUC's so i would reccomend using that for now or TWS until fixed. For future reference please make tracks in caucasus. That is the preferred map for the devs to use for debugging.

Its's known issue that currenthill has confirmed elsewhere.

There is a known bug with the undesignate logic in MP. It effects RSET as well effectively paralyizing you from switching targets

been using TDC depress today with no issues. What map is this the trk doesnt appear for me in the replay list.

i am well aware of TWS centroiding. His question was specifically in the context of the SURV tracks which you can only have 2 at maximum designated at this time.

AUTO should be centering the volume on the L&S At all times, no matter if the trackfile has radar contribution or not. As long as the radar is on and transmitting (not in SILENT) it should still provide command link's to the amraam. If it's not it needs to be reported what conditions is causing it not to.

find a SURV track on the RDR ATTK page, and TDC depress to designate as Launch and Steering

It was added a long time ago i dont even remember when.

I dont really understand what the issue is here. What are you meaning when the missile does reach its target?

FLIR trackfiles are pretty explicity not MSI trackfiles if you read the sources. You can desigate them to slave other sources to them to create MSI trackfiles. They are not MSI trackfiles onto themselves. It applies just the same to AOT's.

This is by design and is how the TA mode works, it's not meant to be a terrain following system stabilized to the horizon like LANTIRN or other TFR systems. The antenna is roll stabilized to the horizon but is aircraft stabilized in pitch and will depress with the velocity vector during dives. This is so the antenna has visibility of terrain protrusions when diving down.