This scenario will now only occur if the collapsed nodes aren't currently linked to any other nodes outside of the ones being collapsed.
Unfortunately this issue isn't entirely solvable due to the ambiguous nature of traversing execution path coupled with macros; however there should be significantly less occurrences.
When you create a blueprint setup with a For Each loop and attempt to use Collapse to Function, the return node is connected to the loop body as well as the completed pin. This causes an issue because the execution of the loop ends after the first loop.
Found in 4.9.2, reproduced in 4.10 binary and Main CL 2765475.
1. Open the editor
2. Create a new blueprint
3. Add a ForEach loop
4. Right click on the ForEach node and select Collapse to Function
Result: In the function, the ForEach node is hooked up to the return node from both the Completed pin and the Loop Body pin, which causes it to end after the first execution.
Expected: Only the completed pin would connect to the return node.
How does TextureRenderTarget2D get TArray<uint8> type data?
Why does the REMOVE method of map container remove elements have memory leaks?
How do I set a material as a post-processing material?
How to delete some elements correctly when deleting an array loop?
UMG RichText not appear image when packaged
What is the cause of the packaging error falling back to 'GameUserSettings' in ue5?
What controls of umg have mouse wheel events in UE4.27?
Why RevisionControl connect failed in Unreal5.4 but Unreal5.3 success
Head over to the existing Questions & Answers thread and let us know what's up.
0 |
Component | UE - Gameplay - Blueprint |
---|---|
Affects Versions | 4.9.2, 4.10, 4.11 |
Created | Nov 16, 2015 |
---|---|
Resolved | Nov 2, 2016 |
Updated | Apr 27, 2018 |