Offensive Engagement

[DWReese]

I have mentioned this in two other threads, and I believe that it is associated with the other issues that were reported there, but just to make sure that it doesn't get lost, here is a reminder:

Aircraft are sent on a air-to-ground missile attack.

Shortly after launch, the planes are listed as Offense Engaged.

The planes abandon their pre-designed path from the Flight Planner, drop down to minimum altitude, and fly straight toward the target.

Many times the planes are too low to launch their ordinance.

But, many times they reach their launch point, but refuse to launch. Their weapons are green, and can be launched manually.

If left unaltered, the planes continue to fly straight toward the target, eventually being shot down.

If you manually fire the weapons, then the planes go into some kind of circle pattern that lasts until the plane needs to RTB due to fuel.

Again, I believe that this has been reported several times, and is likely related to everything else that is being discussed.

[Raptorx7_slith]

Save or scenario with more details please, I'm not seeing this behavior in strike missions. If that's what you mean?

[DWReese]

Kushan1.zip

(237.23 KiB) Downloaded 13 times

Three groups of planes will take off. All three go to Engaged Offensive immediately, and go to 2k feet, as they proceed to the target.

The first is armed with Delilah missiles. It flies to, and beyond the launch point without launching. If you change it to Opportunity, then it will fire. After firing, the planes fly around in a circle as I described. As the missiles get close you keep receiving messages (like 32 at a time) indicating that the missiles are locked on.

The second group is armed with GBU-39s. The also dive down to 2k feet, and when they reach the launch point they won't launch because they are too low. they need to be a 10k and above.

The third group is the same.

NOTE: All of the units IMMEDIATELY switch to ENGAGED OFFENSIVE upon launch, are flying at LOITER SPEED and 2000 feet, regardless of the loadout.

These are all of the same type of units used in Broken Shield 300. I ran that scenario and watched. The planes in that scenario would not launch either unless I made the changes to them just like here. So, it's not the scenario.

[Raptorx7_slith]

From what I can tell this scenario is very old, the DB its using is from a few years ago. It does happen in broken shields but recreating the missions fixes the behavior which leads me to believe it has the same problem. If I use these weapons on other more recent scenarios with 1328.18 it doesn't happen.

Logged as 0015759 just incase

[DWReese]

I ran it using the updated db as well. In fact, I ran it using several different dbs.

And, as I said, I ran Broken Arrow 300, which has been updated and uses the same platforms in this scenario, and it performs the exact same way. Previous versions played fine, but this version does not. Broken Arrow 300 has been updated. Use that one and watch the Israeli attack. The same thing happens.

Thanks for looking into it.

[DWReese]

UPDATE: I created a brand new scenario and everything seemed to work fine as far as the attack is concerned.

There is one issue, however. I continue to get hundreds of messages about the weapon being "locked on" to the target. It repeats every few seconds. The same messages, over and over again. Since the weapon was traveling a long distance, there were hundreds over and over again. Is there a way to turn these off?

On a side note, can you tell me why my original issue occurred? The scenario had been updated, as was Operation Broken Shield, but the weapons seemed to have he same issues that my scenario had. Why? Is there a cut off with regard to what what db must be used? Does this mean that almost ALL of the old scenarios are going to have the same issue? It would be helpful to know this because it would mean that almost all of the scenarios would need to be rebuilt.

Thanks again for your attention to this matter.

[blu3s]

This is probably related to the Ignore Plotted Course set to Yes, we're checking and fixing this issue with flight plans but a workaround it will be set it to No for strike missions.