See the notification message produced the correct number of times (nine), but with the final index values.
See the debug log only printed once with the final index values.
Expected behavior
The notification and debug log should both be generated nine times with values increasing from [0,0] to [2,2].
Screenshots
Incorrect Behavior:
Correct Behavior:
Hardware
Device: Laptop
OS: Linux
Browser: Firefox
Additional context
The For Loop node seems to work correctly when no custom events are used.
This bug is also reproducible with a single For Loop node, but I think two For Loop nodes are a more useful test case.
Description When iterating through a
For Loopnode, custom events aren't fired/received properly and maybe variables aren't set properly either.To Reproduce Steps to reproduce the behavior:
Open this blend file: BG-For-Loop-Trigger-Bug.zip
Export the scene to GLB.
Drop it in a behavior graphs room.
See the notification message produced the correct number of times (nine), but with the final index values.
See the debug log only printed once with the final index values.
Expected behavior The notification and debug log should both be generated nine times with values increasing from [0,0] to [2,2].
Screenshots Incorrect Behavior:
Correct Behavior:
Hardware
Additional context The
For Loopnode seems to work correctly when no custom events are used. This bug is also reproducible with a singleFor Loopnode, but I think twoFor Loopnodes are a more useful test case.