Found a way to make a 'Pure' switch - sort of.

[Dannington]

Hi, I’ve just worked this out and wanted to share it!

This might be common practice or obvious to some people, but for me it’s going to revolutionise the way I blueprint!

I hate making temporary variables for transforms and other values - I always wanted there to be some kind of bool switch for variables. In this example I have 2 target transforms for an object in my game. Before this revelation I had my 2 targets as transform vars - when it came to choosing which one I wanted based on a bool, i’d set a new temporary transform var to one or the other of these.

I could have forked my exec path to 2 duplicate paths with one or the other, but it’s not neat to do that - enter the Lerp! Using a bool converted to a float I can put my 2 vars into a transform lerper and effectively have a ‘pure’ switcher to select one or the other without any messyness!

Yay!

[xulture]

Why not use built-in select? It automatically sets types of inputs based on where output is connected. And it automatically sets type of ‘Index’ depending on what you plug into it…

[Dannington]

Bum - and because that’s too short to post… Bums.

[Dannington]

God, i’m such a div! I’ve just found all of the select nodes. Can any of these switch more than 2 options?

[CriErr]

yes, its called SWITCH
on %enum name](http://puu.sh/ml6zG.png)
or on int, string, name

[xulture]

If you run Integer into Select, you can add option pins with right click:

If you get enum (or custom enum) and create select from it, it will already populate options for you:

[Dannington]

That’s cool - thanks for the info, i didn’t spot the add option pin.

[Nicat]

xulture, I had no idea you could add pins to select node :o. Thanks for sharing