[BUG] MultiMovements and destroy action

[Sphax]

I've just found a bug with multiple movements and destroy object action.

An example is better than explanations...

In brief, if we destroy an object and then we set a new movement to it, it will not be destroyed and some weird behaviors will occurs if it had some qualifiers...

[LB]

I don't really see what you mean... It just plays the destroy animation and is still there... I looked at the events and I don't quite understand whay and what you did...

[Sphax]

_LB, it's an example to show the bug.

In the event editor, at the start of frame I destroy the object, so the object should be destroyed but it is canceled by changing the movement of the object. That abnormal, that's a bug.

[strat59]

Sphax you are right, Strange if you make the red square invisible
at the start of frame the end application condition works.
strat59

[Sphax]

if you make an object invisible, it's still here, so the overlapping condition works. But if there is no object, the overlapping condition don't works...

[strat59]

He he just my convoluted way of saying you were right
strat59

[Sphax]

It could be useful to have an action like "Instant destroy" for all objects which will instantly destroy the object without playing "destroy animation" and without waiting the end of the frame...