Did something change? I can’t figure a way around this.
What do you mean?
Must be an Actor to call GetWorld().
Sorry was having conflicts… And Was reading a forum which had me thinking about something else all good now…Geez those conflicts would have you thinking a whole different route my mistake none the less… I though unreal would automatically resolve and such
An Actor cannot call GetWorld from blueprints. Think that’s what they mean given the question here. Bumping because I too would like to know why GetWorld() is not a BlueprintCallable UFUNCTION by default - it’s very inconvenient.
1 Like