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 …

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 solv…

seems similar to this issue [image] Control Rig procedural element limit quiet failure Character & Animation Hi all, forgive if posted in the wrong place or format, first time submitting to the forum. I’m running into a kind of silent failure state (no log mes…

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 les…

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.

Testing breaking the single function with switch node into multiple functions with no switch node seems to be working to reduce my execute stack by half. There is a bug there for sure in using switch nodes to switch node graphs between construct, forward and backward. I’m testing in 5.6 and haven’t…

Does Control Rig Blueprints have a limit to the execution count?

Development Character & Animation

lrpvot (lrpvot) January 6, 2026, 8:41pm 3

seems similar to this issue