Please Increase parameter limit on Scriptnode custom nodes!
-
There has to be a better solution to this, but I'm not sure what it is.
Nope, that's the way to go. The problem is the intersection between runtime code and compile time code which causes these monstrous switch statements.
@Orvillain if you sign the CLA, I'm happy to accept this beauty of a pull request.
-
@Christoph-Hart Will do!!
-
@Orvillain said in Please Increase parameter limit on Scriptnode custom nodes!:
and for the next guy, he might be a madman and want 128....
okay so the mad man is here
I just found out one of my node with about 100 parameters won't update the internal value and ready to increase this limit to 256 -
I haven't had the chance to revist this yet
@Christoph-Hart Did we ever get an update for the compile time parameter callbacks? A bit higher in this thread, a solution was proposed to accommodate arbitrary parameter counts.
-
@Allen said in Please Increase parameter limit on Scriptnode custom nodes!:
I just found out one of my node with about 100 parameters won't update the internal value and ready to increase this limit to 256
Haven't tested all the params but just wanna comfirm so far it works in both script fx and compiled fx with max 256 params limit! :)
I found there's also a similar param number limit in the rnbo node so don't forget to change that one as well if you're using a rnbo node
