Bug: Explosion trigger not destroying node on startup
Bug #88
Explosion trigger not destroying node on startup
| Status: | Resolved |
| Priority: |
Medium |
| Added by: |
|
| Assigned to: |
Unassigned
|
| Due date: | |
| Reported for: | |
| Fixed In Release: |
SFD 1.5.0m
|
Steps to Reproduce
- Place an explosion trigger next to a destroy node.
- Set the explosion trigger to activate on startup.
- Check whether the destroy node gets destroyed or not.
Explanation
For some reason, when an explosion trigger is placed next to a destroy node and set to "Activate on startup", it does not appear to activate correctly. The trigger seems to do nothing.
However, if a timer is added and the explosion trigger is activated after a short delay, it works as expected and successfully destroys the node.
I recorded a video demonstrating the issue.
This may not be limited to explosion triggers. I have been told that other triggers may also fail to behave correctly when activated immediately on startup, although I have not tested this myself.
Watchers
You don't have permission to comment on this issue.