Settings Issue that I can't seem to figure out

[DWReese]

This type of situation occurs often for me, and I can't seem to figure out why. I happens in almost every scenario, so the scenario has nothing to do with the issue. Here's the observation:

I have a group of four planes, for this example, let's say F-15Is, each armed with one GBU-28C. I have assigned the group a mission. (I like missions, but perhaps it would work better without them.) In any case, my desire is to have ALL FOUR planes launch their single missile at an underground target. That would be four missiles. I know from practice that to kill this particular target it will take at least 5, possible 6 hits, so these four will not be able to get the job done.

I have tried various settings. I have tried "Fire ALL WEAPONS", and I have tried "Fire 1 Weapon" (even though the plane only has one weapon), and then I have set it to FOUR planes should fire.

So, what happens? The first approaches and fires. The second, and the rest, do not fire. They seem to be waiting for the outcome of the first attack to be resolved. (Is there a "wait until" setting that I don't know about?)

I tried spacing them out. The first does attack, and the second then fires at the last second as the results of the first attack are finally resolved. Unfortunately, after that, planes 3 and 4 are too close to fire any additional shots because they now seem to be waiting for the outcome of the second plane's attack.

After any of the planes have turned and begin following the leader out of the area, then there is no chance of them going back and attacking. They merely go home with a full package of weapons.

So, is a formation the answer? Is there some other setting? I believe that I have tried everything. I even tried a two-plane group, and the second plane did get off its shot at the last second because the first attack was finally resolved, but I've never been able to get more than two planes to fire.

What setting or formation can I try to make this work? Any suggestions will be welcome.

Attached is an example. I tried the INHERITED amount, but it still didn't work. The file shows the first plane fired and the second just flew right on by.

New Battle 1.7z

(215.46 KiB) Downloaded 6 times

[Mark352]

Maybe you did this already - In WRA > Weapons per Salvo: Use all weapons against target, Shooters per Salvo: 4 Units. Used F-15I with he same loadout and all the weapons launched against an underground bunker. I'm still using v1.07 Build 1567.6.

[DWReese]

Thanks for responding. Yes, I did do that.

But, I did notice one thing. Look at the two planes INDIVIDUALLY. The one that has launched indicates that it is proceeding to Waypoint Point 6. The other one, the one that hasn't fired, indicates that it is proceeding to Waypoint 2, which is Hold Start. This is not the case because he is obviously following the lead.

I believe that he is not firing because he has technically not cleared Waypoint 2, and therefore can not fire, as far as his path is concerned. If this is the case, then this is a bug.

I followed the planes all the way back home. The second plane was always listed as proceeding to Waypoint 2. It wasn't until the group broke up did that status message go away. I sincerely believe that this has something to do with it.

Perhaps someone with lots of knowledge about groups and paths, etc., can weigh in to determine if this is the case.

[DWReese]

The issue is definitely has to do with GROUPS.

I ran every scenario once again, but this time I placed every individual plane on its own mission. I spread each of them, giving each a ToT one minute later than the previous plane. Every attack was perfect, and the planes all performed as expected.

Which brings me back to what I think is the problem. It's a bug. The second plane in a GROUP seems to be STUCK at Waypoint #2, at least as far as its instructions are concerned. So, even though it flies on its designed path, it can't perform any attack when it is time because its instructions are stuck on Waypoint #2.

This is an obvious bug, and it needs to be moved to the Tech Support section. It's probably a simple fix, as everything else seems to work properly.

[DWReese]

Notice the STATUS bar (far right) of the second unit. It indicates that it is "On Plotted Course" toward Waypoint 2 (Hold Start). It appears to have never cleared that, even though it has actually moved to where it is (which is past Waypoint #5), and that the position where it should be preparing to attack, just as the first unit has already done. I believe that this is what is causing the unit to not fire.

Screenshot (3).png (2.16 MiB) Viewed 403 times

[Raptorx7_slith]

Thanks, logged as 0016823

[Deserere]

Hi DWReese, the issue should be fixed and it will bei n the next update release

[DWReese]

Thank you for the new release.

This issue WAS NOT fixed, however. The same issue remains.

The second plane in a group is still showing headed to WP #2 (Hold Start), therefore he cannot (will not) fire, even though he is physically right with the LEAD over the target.

[blu3s]

Just in case, if you're loading a save with aircrafts already on air, or using the same FP that was saved, yes, it's probably that you see the same issue. With the aircrafts on land, regenerate the FP and give it a try.

All flightplan related issues need to regenerate the FP with the new version in order to check if the issue is still present or not.

If you still see the same behavior, I'll reopen the ticket on Monday.

Thank you

[Nikel]

But is this not the same "problem"?

It cannot be fixed in build 1676 because this build is one month old and the fix is posterior.

[blu3s]

Ahh that's right, but the above explanation is valid for any FP issues.

[DWReese]

blu3s,

No, it's not an in-flight rehash. This is a brand new scenario. It still has the same thing.

The planes are not starting while in the air. They are launched brand new from a base. There are no predesigned flight plans.

Keep in mind, this works fine for single planes. The problem arises with groups. The lead works fine, but the second plane gets stuck on WP2, (Hold Start), at least that is what the status indicates.

[blu3s]

As noted above by Nikel this issue was fixed for a build after 1676, that's why the issue is there. You'll need to wait for the next beta release to check.

[DWReese]

Okay, thank you.

[DWReese]

FIXED: #16823: Wingmen aircraft getting "stuck" at WP 2 during strike mission, do not follow WP parameters of subsequent WP's

I'm sorry to say, but this still is NOT FIXED.

The second plane of the group still shows as being stuck on Hold 2, and will not release its weapon. It will follow along with the leader, but will not release its weapon.

[DWReese]

Addendum:

Trying different scenarios with different planes and different ordinance seems to work better.

Things to notice: Whenever the game decides to make the LEAD some other plane rather than the first plane numerically listed is when the problem occurs. For example, Apple 1 and Apple 2 are part of a Group Tree. If Apple 1 is the LEAD, then it works correctly. But, if Apple 2 is the LEAD, then Apple 1 will not fire. If there are four planes, whenever the program makes the #4 plane the LEAD, then the other three do not fire.

Most of the problems occur when the planes are carrying just one bomb, such as a single GBU-28 and you desire ALL of the planes to fire at the target which is an Underground Bunker. The first unit's status shows as going to attack the bunker, and the second shows as Hold #2. This is odd, but it doesn't always result in the planes not firing.

Perhaps it's the specific ordinance; or perhaps it's the Hold 2 issue; or perhaps LEAD issue; or perhaps it's the underground bunker thing. I don't know.