This issue is still broken in 4.10… I am not using set node. I am using struct to define properties and another struct to create an array of those properties, this is breaking in many unexpected ways, setting values to defaults and outright breaking all connections to blueprints.
This doesn’t work in 4.9??
Hi and TJ Ballard,
I’m on my third day developing with UE and blueprints and already ran into this issue (UE-6451). Seeing that it has been unresolved for more than a year now gives a bad impression of Unreal Engine. When are you going to develop a fix?
Thanks
Another workaround as suggested in is to assign array element (i.e. struct) to a local variable like so:
This works fine for me in 4.10 and doesn’t require breaking an re-building struct instance.
Hey everyone,
devs are still investigating this.
Just adding to Rasterizer’s comment. I tried this in house and it does seem to be a useful workaround for issue.
This is still bugged in 4.10.4, Epic wtf?
I’ve pretty much ended participation in Unreal because of this and many bugs like this. This bug and many others that have never been address proves that Epic is uninterested in actually following through and providing product they promised to community.
Epic, STOP Developing features, stop VR, just STOP and check backlog and give us a few quality stable releases with basic features actually working.
@rasterizer you sir are a bloody genius! That is best thing I have ever read XD Well… not quite but that fix works perfectly!
This is kind of answerhub thread that sucks to stumble upon 
Running into this still in 4.11.1 I suspect that in kismet reference is getting lost? Would love to see discussion surrounding this issue and why it’s such a mystery, i have engine source, just sayin.
This is still broken it 4.13 it seems.
Yes, I just encountered this in 4.13.1 and it was driving me nuts.
Hello,
This is still being investigated. You can follow this link to Public Bug Tracker to see status and vote on JIRA UE-6451.
4.13 struct in array doesnt update.
Im doing same exact thing with another struct in same array and it works.
100% will name my first-born son “rasterizer.” This thread killed my night, and your solution revived it.
Epic Games, any updates? How is this still a thing in 2017?
it still happens in 4.15
In that case you would be more than delighted to hear that this is still an issue in UE 4.15.
Please vote on issue here so it might be resolved sooner than later.
I solved problem by uninstalling unreal engine from my computer. It fixed all errors. Im really happy with results. Now i get stable 60 fps.
This is not a real solution, because you don’t want to set whole struct again. If you are just changing 1 variable of Struct, you want to speak with that variable, you don’t want to set other variables again.
Yep I had this issue as well on my 4.15.1 version so I added my vote to this. Pretty major issue because google has a ton of search results about this with many people getting same problem.
I’m amazed this has not been fixed yet to be honest.