PaulToo

There is just one file different from the one-seater.

bearing = horizontal range = vertical

The 3 positions of the flaps I have bound to slat/flap lever full up, 1/2 flap, full flap. Works for me with a 3 position switch. Gear is only 2 positions, with the additional safety lever, bound U/C control lever -extend/retract for the gear, and U/C safety lever open/close for the safety latch. The latch doesn't really work, at least for me. Radar cursor is radar control stick bearing control and radar control stick range/velocity control. Both are axis.

Coolie left long (outbound) is for IFF, coolie right long is for NCTR. That's for the front cockpit. As others have stated NCTR only works for frontal aspect and at certain ranges. Both methods work for me.

In lines 32 to 36 the "" are not correct.

The G2 cable doesn't fit the G1, different connectors.

The mod works for me in the EE, CE, 2d, or VR with the newest update.

After removing the 4 models show in AdrianL's post from High Digit DCS.log showed sensor conflicts with the "S-300V 9S32 tr", "S-300VM 9S32ME tr", and "S-300PMU2 64H6E2 sr". I commented out the complete sensor definitions for the 3 Sam systems (S-300V, S-300VM, S-300PMU2) in the High Digit sensors.lua and DCS started up. What would be the proper way to remove the conflict without having issues with for example the IADS script or duplicate units?

Try --Liveries instead of Liveries-- in line 2.

After watching the tacview a few more times it almost looks like a predefined response to the deviation from the predicted flight path before the new intercept course is calculated. As soon as you pulled up the missile turns right to cross the previous predicted flight path. Would be interesting to see if the missile turns left if the predicted flight path is to the left of the missile. The accompanying altitude dip might be because you were descending with increasing neg VS before pulling up or it could be part of the predefined response. That's how I would interpret what happened in the tacview. I only tested at high altitudes, but there the missile usually started to fly straight and with some pos VS until it exploded after losing track.

Watched it 5 times and the Phoenix hit the F-16 in each. The missile looked like it was searching at some point. Do you have a tacview? I attached one from the replay. Tacview-20220602-161352-DCS-Aim54trackmiss.trk.zip.acmi

Thanks for the the answer. Not what I was hoping for. Strange decision to tie the acls to the comms menu, I wonder how sqdn with human Marshal/LSO deal with that headache. Hopefully were will be a workaround for airboss in the future or ED makes the hornet's acls compatible with it.

That's why I suggested Moose-Airboss. You can set it to run case 3 traps even if the weather is perfect. Airboss itself has voice overs and extra visual cues (F10 menu). There is also some real-time help/hints and grading to help understand what went wrong/right or is the next step. Only drawback, if you want to call it that, is that the comms are over the F10 menu and not the usual F5-ATC. The discussion with dangerzone was about if airboss can use acls if set to case 3 even in case 1 weather conditions. Just successfully tested that with the F-14 (thanks HB for fixing it) as I don't have the F-18. Attached is the mission I put together to test the aforementioned. The F-14 is all setup (Tacan/icls tuned), didn't found a way to do that in the editor with the F-18. Channel 1 for both aircraft is Marshal and channel 2 is LSO. Autolanding.miz

Good question. I would assume that it would work, if not it doesn't make any sense to have the options in the script. I don't have the Hornet, but I remember that I did let the F-14 autoland on the carrier in Case 1 conditions before it broke. If I have time today I try it out, also to see if the F-14s autopilot is really fixed. Setting up airboss is just a few lines of lua and for the test there don't need to be any bells and whistles in the mission.

You could use Moose and the Airboss script to do all that. https://flightcontrol-master.github.io/MOOSE_DOCS_DEVELOP/Documentation/Ops.Airboss.html