It loads infinitely despite being built on the same logic of other scripts that have run just fine on Shapediver. A few additions: the use of pufferfish components and a more complex script.
Not clear in the documentation, but I reuploaded a simplified version to do my testing and got an error first around shapediver denying groups (it works fine in rhino but doesn’t work with shapediver output) and then after fixing that the number of components per output component was limited.
Make sure to flatten the trees that go to the ShapeDiver Display components in order to limit the number of parts per component, which is limited once you upload your definition. Let me know if you encounter any other issues.
Hello! Working on the same script in which at first the number of parts per component did seem to be the issue. After solving for this and getting the script to work once, I am getting an issue where it is only showing a small portion of the total lines. Functions great locally and shapediver does seem to be doing all the calculations on the backend but only a small portion ended up being visible in the portal.
I am not sure what did it, but it may have been recreating and relinking everything relating to the upload component but I am all good now. Thank you for taking the time to look,