It’s not the by-ref specifically; i sense it’s the Select
node acting up. Does it work if you set it directly?
welp select does work with blueprints variables at least… first time facing this issue
It does yeah
Right until you use a null object ref. In the past, it would just crash. But you’re right, it does work with BPs vars, indeed.
It does yeah
So C++ var does not enjoy being piped through the Select node?
I found the solution. Blueprints automatically convert float variables into doubles. If you connect a C++ variable to a select node for the first time, the output will be a ref of FLOAT type, so set by ref will be a FLOAT type as well, and will NOT set your blueprint vars. But when you connect a blueprint var first, the output of the select node will be DOUBLE, and set by ref will be DOUBLE as well, and it will NOT set your C++ vars.
Be careful, all the vars must be the exact same type, otherwise this wont work.
2 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.