Optimizations for Switch, Mux, and LogicalOr

[hdarren]

@Chad

Based on fps numbers, I’m assuming that Genome doesn’t optimize for Switch, Mux, or LogicalOr. Meaning, if we wanted to apply some complicated effect only on the vertices/faces that were either selected or actually mattered to the effect, we wouldn’t make anything faster, and could actually make it slower?

This is true. In the current implementation Magma/Genome will always execute every node, and Switch/Mux will just select a branch after the fact. At some point we will address this, but it complicated the algorithm enough to not warrant it in version 1.0.

@Chad

Also, but much much much less important, Power doesn’t appear to optimize based on the Exponent being connected to a Integer.

It does actually. The implementation of std::pow(float, int) provided by the MSVC C++ standard libraries has a different codepath compared to std::pow(float,float). Perhaps the implementation is similar in cost anyways.

[hdarren]

Genome nodes can have their properties changed without a license. This includes things like setting the Texmap or spinning a spinner. The major operations that are restricted are creating nodes and changing inputs.

[hdarren]

The license is checked in after all the Genome mods that have been edited are destroyed. Scene reset should do the trick.