[CP5670]

There seems to be a potentially problematic bug in fs2_open versions 3.51 and 3.53. I was testing one of the PI missions last night and found that one of the events was not working correctly. I wanted to script a certain warship battle and have the anti-capital beams fire between longer intervals than usual, so this event uses several instances of the fire-beam operator and is a repeating event. It is chained to another event so it just uses the true conditional. Now what happens in the mission is that the event works fine the first time and the beams fire as they should, but it never repeats at all.

I first thought that this might be some freak thing with that particular event, but when the same thing happened in two other missions that used to work fine I started wondering what was going on. I created a basic test mission with just a chained fire-beam having a repeat count and interval similar to those used in the missions with the problem. Strangely, it worked perfectly fine this time. This leads to me to suspect that there might be some conflict with other events or that perhaps some event limit is being exceeded in the other missions. However, I don't recall having any trouble with this with the Volition version (and with the same missions).

I have only seen this problem occur with fire-beam but have not really tried out other operators. Also, everything works fine if the event is not chained (it repeats as it should), so it is always possible to get around this by using is-event-true-delay, but it could cause problems with missions that have already been released.

[Goober5000]

*peers at code*

Nothing seems to be amiss - it doesn't look like anyone has messed with that section.  Can you be more specific?  What is the precise sequence of events?  Do they work in 3.4?  Do they work in 1.2?

I've had trouble with chained events in conjunction with repeats before; usually a bit of messing around and reordering solved the problem.

[CP5670]

I haven't tried it in 3.4 but it works fine with 1.2. These are the events used for one of the missions:  (‡ denotes a chained event)

Code: [Select]


•MSGL/AI: Delphi arrive 1-6      (standard event)
‡BF: Amenemhet      (repeat count 1, chain delay 32)
‡BF Amenemhet 2      (repeat count 10, repeat interval 50, chain delay 1)
--when
----true
----fire-beam
------Amenemhet
------turret03
------Delphi
----fire-beam
------Amenemhet
------turret04
------Delphi
‡BF: Delphi      (repeat count 10, repeat interval 50, chain delay 3)
--when
----true
----fire-beam
------Delphi
------turret20
------Amenemhet
----fire-beam
------Delphi
------turret26
------Amenemhet


Pretty standard stuff, but the two BF events only work once. It works fine if is-event-true-delay is used instead of the chains, so it is really not too much of a problem except for missions that have already been released.

[Goober5000]

Eh.  I see no reason why that would be changed.  Try it in 3.4.