DWReese -> RE: I can't get an airstrike to target multiple targets (11/15/2017 12:48:52 AM)
|
The LA/NY thing was an extreme exaggeration just so I could make the point about the distance. I hope that you didn't take it literally. In any case, I set up a similar situation to yours. But, instead of 7 miles, I separated the two identical targets (A & B) by 35 miles. I sent a U-2 in the area to find the targets. I purposely placed B closer to MY base than I did A. I then assigned one bomber with two bombs total to the strike mission. I used WRA to tell the bomber to use one weapon per target only, and I included bot targets (separated by 35 miles) on the same target list. The U-2, as expected, found B before it found A. The bombing mission was set to start AFTER the U-2 would have found both targets. In other words, both targets had already been located when the bombing mission was activated. When the bomber took off it immediately plotted a course set to fly to B. The already drawn-out course then had the bomber return to base. There was no mention of A. The bomber flew to B, released its bomb, and destroyed B. The bomber, despite having the aforementioned path which directed it to go back to the base, instead flew directly to A. Once there, the bomber destroyed A, as had been hoped and as expected. At this point, the bomber, which was now out of ordinance, established a new path and flew directly back to base. The bottom line is, everything worked perfectly, although the bomber did go for B before A. I replayed the situation a dozen times and everything happened exactly the same way, with the exception of one. On that occasion, the bomber's first bomb missed Target B. When that happened, the bomber circled around and dropped his second bomb on target B, this time destroying it. With no more ordinance, the bomber then headed back to base using the same plot that had originally been exhibited. Target A, obviously, wasn't attacked in this situation because the bomber did not have any more bombs. Again, everything worked exactly as had been planned, and the bomber did again go for the closer target (B), as opposed to (A). (So, I guess that a bomber would go from Montreal to NY first rather than LA. <g> I did notice that the bomber does adjust its speed and altitude as it moves toward the target. At some point, because the bombing run was so low to the ground, the fuel was listed as only 33 minutes left of flight time at that speed. When the bombing run was finished, it climbed to a higher altitude on the way home, thus saving fuel. I don't know what the distance is from your bomber to your base, back from the target, but it could be that the AI governing your plane may have determined that it did not have enough fuel to go after your second target and, therefore, directed it to go home. That's as much as I have. It seems to work for me in all of my tests, so there are likely some other factors involved. But, as Ragnar pointed out, if it's that important you can always assign two missions, or use lua to assign a second mission to your plane, assuming that he still has the ordinance to make an attack. Good luck. Doug
|
|
|
|