Set members doesn't work with array element

This question has been asked before, but no good answers were given and they said it’d be fixed in later versions of the engine. I can tell you, it’s not. It’s still broken. I posted a new question instead of on the old one because that thread is dead, no one’s posted on it in months.

The problem is when I use the node “Set members in struct name” on a struct in an array, it doesn’t set the values at all. It’s as if the node is never called.

The other thread.

There were some answers in there, but all the solutions given were incredibly ugly and pain-in-the-■■■ work-a-rounds. I’m wondering if anyone has come up with a better solution to it.

Hello ,

I’m sure this isn’t exactly what you want to hear since you mentioned it yourself, but this will be fixed in a future version. As Adam mentioned in the other thread, he placed a bug report in for it. While it wasn’t a high priority bug (due to other things such as crashes and the sort) a fix has gone in for the issue. It’s been quite a while since that bug report was put in (Back in 4.6 / 4.7 it looks like) but the fix was actually made just 3 days ago. Due to the timing, it most likely won’t make it into the 4.11 release but may be included in 4.12, although I can’t make any promises.

The fix itself isn’t available on GitHub as of yet so I can’t give you a commit yet but once it comes available on GitHub, I’ll be sure to let you know so that you can integrate it into your own engine if you’re building from source, to get the fix earlier.

After some fiddling around, I found a solution that isn’t quite as ugly as some of the people suggested on the other thread.

Shove the reference into a variable in the blueprint. Do what you want to it (set its variables as you please). Then set the element in the array at its index. The ugly solution that I saw in the previous thread was to basically make a copy of the struct, linking every single one of the variables from the old to the new copy. I didn’t like that, so I figured this out.

Okay, thanks for the quick reply. I found a better work-a-round for myself then the previous post could give me.

Look forward to the fix becoming live!

P.S. My name’s , not . How could you possibly get those confused?!