Matrix Games Forums

Blue aircrafts have unguided bomb, assinged to ground strike mission, and about to bomb Red airfield (runway). However, they just circling around the target and won't drop bombs.

I checked their flightplan: altitude from IP to target said 800AGL, but they actually flying 300AGL (which is lower than bomb's minimum altitude). I suspect there is something wrong in flightplan adaption to units. Thanks in advance.

I wrote for about one solid month about this issue. That was about three months ago. As far as I know, it was never fixed. It never appeared on the change log.

In the mean time, you might want to play around with checking and unchecking the AGL box in the Altitude/Speed menu. I've noticed that this is often something that can be done to force the game to work.

Also, you may find that the leader might be checked, but the rest of the flight isn't, when you look at them individually. They aren't always synced up.

Also, you can try with just one plane, or setting the attack altitude a little higher. Individual planes seem to work much better than groups.

This problem occurred right after they introduced their ground/tower/altitude thing, which was about three or four months ago. It hasn't worked correctly since then. It does seem to work better over water than terrain that has different elevations.

Good luck.

In 1328.7, a few mentions were made in the release notes that might impact this. I ran your save in 1328.7 unaltered and it ran with no issues. All bombs dropped by all units in the group. Just to make sure, you might want to try it yourself and see if that solves it.

This is his thread, not mine, but your response to him made me curious.

The OP specifically states in the headline that it is 1307.19 that he is talking about.

You seem to be indicating that it works fine in the 64-bit beta, but how does that resolve his issue in 1307.19? Does the beta fix somehow have anything to do with 1307.19? If so, can you explain it so that we would all know how it works for the future? If so, then why doesn't it work in 1307.19 for him?

You suggested that he should run the test in the beta, but it doesn't sound like he is using the beta, so he obviously wouldn't know. Remember, he's reporting the problem in 1307.19.

Thanks

Its a data point is all. I happened to see a comment in the release note about it. Confirmed it worked. Suggested he check it out. Is this a problem for you?

Is this a problem for you?

No, it's not a problem, but to me, I fail to see the relevance. Your response reminds me of someone having the CHECK ENGINE light come on on their car, and then they go and check the tire pressure of their right front tire. The two are unrelated. I simply fail to see how reporting on the functionality of the beta does anything to resolve the concerns of the OP, which pertained to 1307.19.

Rather than test the scenario using the beta, I believe that it would have been much more beneficial for you to conduct the test it using the same game engine (1307.19) that the OP was using. Perhaps his settings were wrong, and by having you test his situation using 1307.19 you possibly could have discovered the reason for the problematic behavior, and then you could have provided him with some actual beneficial advice as to how he could resolve HIS issue.

But, no, I don't have any issue with you saying anything at all.

I did test it in .19 and it had the issue. I remembered seeing something related in the release notes. The point was to show its being worked on and recognized. Not sure what you wanted me to do.

It works fine in Build 1328.8. Move along.

Is this one fixed, then?

It seems to me that it doesn't work fine in build 1328.8

Attached is test scenario where a flight of 4 aircrafts is set to launch from airport and attack target which is group comprising of two fixed installations with unquided bombs.

The flight starts normally till it reaches target. Then for a long time circles over the target. At some point the bombs are dropped but afer quite a lot of time.

Hi, thanks for highlighting the issue.
it should now be gone for good.

A possible workaround that you might try while waiting for the next update release is to create the flightplans, save and then reload the scenario.

Thanks again, do not hesitate to update me if any issue persists, this proved to be very nuanced and variable dependent issue.