More experimenting. This time with a bare bones mission, AI only. First flight, positioned F18s right on the WP1, drops eight JSOWs nice and easy.
Second mission, same, but included a long flight back to the carrier. Still worked fine, as they had full fuel tanks.
Third mission, air start at 26k over the carriers. Flew the the waypoint, then aborted mission. On the F10 map, you see the target designators as they attempt the attack and abort. Ironically they dive to the deck for the return to the boat, but that is AI.
Fourth mission. Same but turned on infinite fuel and turn off RTB on Bingo. They fly the distance and then drop the JSOWs.
Fifth mission. I took off infinite fuel, and added a tanker. They didn't care. They aborted and went for the tanker. Glitched out doing that too.
sixth mission. Added a refueling en-route. Flew to the tanker, got the fuel, made the attack run.
Conclusion. The issue is totally related to generous expectation of fuel for the return flight to the boat. Even knowing a tanker is waiting for them doesn't change their decision. Use of AI infinite fuel is a partial remedy. It still expects to see a lot of fuel for the return to the boat. This is despite that I am generally very cautious about not running to short on fuel.
Thanks guys for mentioning the infinite fuel. I didn't know that was a thing. And for suggesting it was fuel related.
icecold951's post in Mission 5 was marked as the answer
Okay...on 3rd attempt went fine. I don't know why it had problems before. Maybe beaming the plane so didn't pick up on radar, though I am sure I was within visual range a couple times. Was driving me nuts.
Was fun with Knight. Go away! You're crazy.
"I'll shoot you"
