Can confirm I get this with an array of timeline components as well
You always get a Pointer from UObject types (even before 4.16). Why do you need a Ref to Pointer in Blueprints? There ainĀ“t much you can do with them in BPs. You wont get a Copy of a new Component/Actort to be Clear just in case there is a general missunderstanding here.
Epic Staff probably coded the Get nodes in a very Generic way and the āCopyā part should not be there as part of the Description for UObject based Types.
Correct me someone if Im wrong but I havent encountered any different behaviour from what we had before.
Greetings,
It just doesnāt work anymore. Before 4.16 Get always returns a ref. Now if I click āChange to return a referenceā it fails. If I uncheck context sensitive and choose Get (a ref) it converts to Get (a copy) automatically.
It works on basic types (Integer arrays etc.) but not on actors or components.
Please save me!
Ash
I just noticed the same and made a bug reportā¦ itās not this alone either. Arrays of BP classes inheriting from Object have the same behavior, possibly others as well.
Glad to know itās a bug. Thought I missed something.
Well, Iām not 100% sure either, but it should be. Iām pretty sure in 4.15 they returned references and I donāt see any reason at all why you should only be able to get copies.
Hey youāre right. Been working with blueprint for so long that Iāve forgotten it has to be a pointer. I was confused why would I want a duplicated copy of the entire instance