So I have of course written my own macros to offer me arithmetic selects with 10, 20 or 30 options. However I found out today when using nested generators that I'm losing quite a lot of performance by having select options with more options that required.

In a bid to future proof my graph I had added select 30 options, unaware of just how much they would decimate performance (graph build time was around 4 seconds pre-optimization, I now got it down to 1.3s after change 6 or 7 select 30s to select 10s).

It would be really nice to have a native node which was correctly optimized and allowed you to add basically infinite selections. Editing long nested if / else arithmetic macros is not very nice. And when you wish to change a parameter based on another parameter integer value.

For example you have a drop down with a bunch of modes, and you want to change various other parameters based on the mode set.

Anyway here are my macros for reference.

In a bid to future proof my graph I had added select 30 options, unaware of just how much they would decimate performance (graph build time was around 4 seconds pre-optimization, I now got it down to 1.3s after change 6 or 7 select 30s to select 10s).

It would be really nice to have a native node which was correctly optimized and allowed you to add basically infinite selections. Editing long nested if / else arithmetic macros is not very nice. And when you wish to change a parameter based on another parameter integer value.

For example you have a drop down with a bunch of modes, and you want to change various other parameters based on the mode set.

Anyway here are my macros for reference.