[Bug Report] ForEachLoop can't read from an array of wildcards inside a macro library!!

Hi guys.

I have created a macro library and put a ‘For Each Loop’ inside it. Then When I create an array of wildcards for the input of my macro library and plug it into the array pin of the loop, I noticed that ‘For Each Loop’ doesn’t read the wild array which I have determined its type outside of the macro. I have tried other array types and it seems the loop inside the macro has no problem in reading from specified arrays. It only can’t read from a wild array, which is so disappointing, because actually I specify the wild array type but just outside of the macro. Here take a look at my pictures. I have created a very simple graph to show you where the bug is.

This is my main graph inside level blueprint.

This is the Test macro.

Random array

139856-randomarray.png

For each loop

Compiler results

139855-compilerresults.png

I hope you guys will find a solution soon to this issue.

Regards.

The problem is Unreal Engine doesn’t let us use Wildcards

I’ve recreated the macro and got the same problem. The only way I fixed it was to change the parameter from wildcard to integer. When that happened, the ForEach turned into an integer one, and all was fixed.

When you go to create a variable, you notice that you cannot type in wildcard and have it show up. Dragging a wildcard wire into the parameter isn’t going to trick the engine into letting you using it.

The tough reality is you’re probably going to have to make one for integers, floats, vectors, but as far as objects go, you can always cover all your bases and have a foreach for objects.

But just add the foreach’s for each type as you need them, just to prevent making 5,000 macros all at once.
Its sucky, I know :confused:

I think there’s nothing wrong with macro, ForEachLoop is already a macro, if you try ForEachLoop directly, you won’t get any errors.

Hello Navid100,

I believe the issue you are experiencing is a known issue, which you can view here:

You can track the report’s status as the issue is reviewed by our development staff. Please be aware that this issue may not be prioritized or fixed soon.