1
Substance Designer - Technical Support - bad performance when using input value for switch nodes
on: February 08, 2021, 02:56:19 pm
Im currently working on a filter which uses a number of iterations. More iterations increases rendering time as you would expect. So I have a switch set up to select a number of iterations. However, the selection is calculated by a value processor which sets the selection of a multi-switch.

I noticed that performance is always worst-case, as if all iterations are rendered no matter what selection is set by the input value.
I set up a simplified example to demonstrate the issue.

(direct gif link, in case it wont load https://i.imgur.com/mnbmRzJ.mp4)
As you can see, I have the exact same graph except the multi-switch is exposed through a value input on the 'bad' version, and gives always worst-case performance.
I attached the example graphs below.

I noticed that performance is always worst-case, as if all iterations are rendered no matter what selection is set by the input value.
I set up a simplified example to demonstrate the issue.

(direct gif link, in case it wont load https://i.imgur.com/mnbmRzJ.mp4)
As you can see, I have the exact same graph except the multi-switch is exposed through a value input on the 'bad' version, and gives always worst-case performance.
I attached the example graphs below.