Matrix Games Forums

Hey guys,

Not sure if Herman already reported this but looks like the generic strike missions (as in sub strike, ship strike, ground sans specifying the specific target in the mission editor) have a hard time clearing old targets and gaining new ones if their assigned target is destroyed or is a lost contact. So the target will remain as the assigned target in the unit status dialog and it will not pick up a new one etc. Have had a few aircraft orbiting aimlessly assigned a target that was already destroyed.

So game needs to clear destroyed targets from the mission queues when its no longer a target and pick up a new one.

Thanks

MM

Mik

I can confirm your BUG report, I have been developing a viable system to limit iron bomb loadouts. While testing I observed this behavoir while testing my "limiter".

The aspect of the game engine controlling say a ground strike mission will work through the viable ground targets in a base. If my aircraft is attacking a given hangar and the hangar was destroyed before my aircaft expended all it's weapons it would suddenly start flying the, "aimless circles" you described so well Mik.

I could still fire the remaining weapons manually at any other targets, but it was obvious the mission "controller" wasn't going to reassign the inflight aircraft to the next target. It only seems to apply to aircraft that are within range of the target. I have had other aircraft return to base if one of my other airgroups has destroyed the assigned target. They are then reassigned to the next viable target while on the ground under going the 30 min standard turn - around time.

Good pick up Mik

Darren Buckley

Thanks Darren[:)]

Hi Mike,

Done a little testing, and it appears that selected targets in strike missions are cleared when destroyed.

Moving on to the generic strike missions next.

Just wanted to let you know I'm working on this one.

Thanks

I wasn't worried about that Jeff and not to worried about the when. You've done a great job thus far.

Yeah generic mission seems to be where I saw the problem.

Thanks for the time.