I’m finding in my control rig blueprint that I’m having to disconnect execute in the Backwards Solve, and as the rig gets more complex I’m having to peal back execution in the Forwards Solve. I’m finding if I can find optimization in my functions to execute less nodes overall that it helps reduce the amount of peal back that I have to do. Is there a way to increase the overall amount of execution?
Its seems to stop somewhere after 65000 in the execution stack. I’m generating control naming procedurally and have other procedural elements for a bird wing. I’m finding this limit to be too constrictive. I think I can simplify but not sure if I can simplify enough to accommodate backwards solve.
seems similar to this issue
I’m finding the pattern of using switch to control if the rig function builds Construct, Forward, and Backwards causes the execution stack to triple. If I create a function per Construct, Forward, and Backwards instead of all 3 living in one function (using the switch), I’m getting significantly less executions.
Just chiming in to say using switch node seems to cause the evaluation to double not triple. I’m hoping that breaking my functions into Construct, Forward and Backward solve will help reduce my execution stack. This instead of doing all 3 in one function using a switch.