Suggestion: marking blueprint function as pure implies BlueprintThreadSafe

Like the title says, this is more of a suggestion than a question. I have no idea where to post things like this, so it’s going here.

Anyway, I’m having a lot of trouble using functions I create in, say, Blueprint Function Libraries in my Anim BPs because I cannot use them for transitions. A warning is emitted saying that the function is potentially thread-unsafe, which I agree is a reasonable assumption to make. I could obviously just ignore the warning and continue on, but that would be a big hit to my game’s performance to not be able to use multi-threaded animations.

My suggestion is, if I mark a function as pure, then make it also be (internally) marked as BlueprintThreadSafe. This way I can use functions I create without giving up such a big thing and it would make my life a lot easier.

Thanks in advance.

EDIT: Either that or create a different specifier for it, if functions like Random Float (which show up as pure in graphs) end up being affected.

1 Like