no bug AI Wingmen Always Go WP 1 First (Update)

[icecold951]

Mission breaking. AI wingmen now return to WP 1, starting the whole cycle of WPs from 1. Now any mission in which you have an order "Wingman, execute mission and rejoin" is broken by this bug. They will always return to WP 1. I even tried creating a change WP trigger action and it didn't fix it. How did this not get seen in beta?

Specifically WP1 was always Push, 2, ingress, with the designated target via WP2. And though WP1 has no objective, they returned to WP 1.

1.miz

Edited January 2, 2023 by icecold951

[icecold951]

Semi fix so far. It still won't behave correctly in ME, but flown as a mission I am able to order my wingman as normal. It is inconvenient to mission editing, but going to the missions option seems to work. My test is a single mission so far though.

[icecold951]

Okay, it still seems to do it even with using Missions instead of Mission Editor.

Here is the track and miz of the event that happens. In it, 3 waypoints with a ship at WP3 to the east. When I tell my wingman engage the objective, he turns back to the original waypoint.

1.trk 1.miz

Edited January 2, 2023 by icecold951

[NineLine]

Thanks, will take a look. 

[NineLine]

The command to attack target only works on the leg of the mission the Task is set up on, I believe this is correct as is. So when I am on my way to WP3, I issue the command and the start to orbit. The AI proceeds, kills the ship then rejoins.

I think issuing it earlier the AI doesnt know there is a target yet so the mission at the time is to follow waypoints and that is what he does. 

What I did was add the attack target to the first WP, then at any point you can tell the AI to attack the target and rejoin and it works.

I hope this helps, if not let me know. Thanks!

[icecold951]

On 1/11/2023 at 12:51 PM, NineLine said:

The command to attack target only works on the leg of the mission the Task is set up on, I believe this is correct as is. So when I am on my way to WP3, I issue the command and the start to orbit. The AI proceeds, kills the ship then rejoins.

I think issuing it earlier the AI doesnt know there is a target yet so the mission at the time is to follow waypoints and that is what he does. 

What I did was add the attack target to the first WP, then at any point you can tell the AI to attack the target and rejoin and it works.

I hope this helps, if not let me know. Thanks!

 

I'm not sure I follow. Having them do it on the leg you are currently on would be great. I orginally had issues of this over a year ago that they returned to a refueling waypoint first. We already refueled. But unless I missed something in the last couple years....The player leg never advances to the next one. Even if I fly right through the waypoint as closely as possible, I have never seen it advance from WP 1 to WP2 for the player. Is there a way to trigger the player waypoint to advance in the map mode? I don't mean switching the waypoint on the HSI or SA. I do that, but that doesn't change what the map shows.

[icecold951]

On 1/11/2023 at 12:51 PM, NineLine said:

The command to attack target only works on the leg of the mission the Task is set up on, I believe this is correct as is. So when I am on my way to WP3, I issue the command and the start to orbit. The AI proceeds, kills the ship then rejoins.

I think issuing it earlier the AI doesnt know there is a target yet so the mission at the time is to follow waypoints and that is what he does. 

What I did was add the attack target to the first WP, then at any point you can tell the AI to attack the target and rejoin and it works.

I hope this helps, if not let me know. Thanks!

 

Okay. I think I know what is going on. Traditionally I was able to tell them at any distance from the waypoint, to do this. They would fly to WP 2, Ingress then execute. Now I either have to be closer to the WP, and I suspect that isn't true, or much closer to the target that I had to be before. In the past it wasn't so picky. So missions that work don't now. That would explain why some missions work fine and others don't. Their Ingress WP where the mission order is may now be to far from the recognized distance.  I'll experiment with it some, using that mission. Move the target farther away and see what happens.

Edited January 13, 2023 by icecold951

[icecold951]

Can confirm it seems tied to the target. Pre 2.8 it would go to the WP first.