|
|
What are you talking about? O.o Both Alpha and Zeta are cued to depart, and the nebula storm code has positively *nothing* to do with the sexp code.
If I don't hear a good explanation soon, this bug will be closed with extreme prejudice. |
|
|
|
Zeta has departure conditions also. Why they do not depart frequently then? |
|
|
|
If they still have orders in their order queue, they will not depart until the orders are finished. This depends on the mission, the number of enemies present, and on the orders you give them. It's not a bug. |
|
|
|
Reopening this just in case, but I have serious doubts it's a legitimate bug. |
|
|
|
Departure condition execution must not depend on current orders. It is not an order to depart, but internal command. Check Failure to Communicate mission in FS1 port. Last wing of Nephilim departs when Hope reaches the station though they have order to attack the station. So either it is storm bug or it is departure cue bug, which is unlikely because in other missions all is fine. |
|
|
|
Can you recreate the same problems in retail? If so then I doubt that this is something we should try to "fix". If not then go back through all of the FSO builds until you find the last one which doesn't demonstrate the problem, and let us know what build that was. |
|
|
|
Unfortunatly this present since retail. |
|
|
|
I'll wait for Goober to comment, but I don't think that we'll do anything about this. |
|
|
|
Yeah. On rare occasions (such as in one STR mission) I have had trouble with a wing not departing when they're supposed to, but I can usually FRED around it. In the vast majority of cases however it works fine.
I doubt think we'll do anything about this either, unless it becomes a serious problem in somebody's campaign. |
|
