Shapediver Limits

Thank you very much for your feedback. Great to hear that you love ShapeDiver and you got your model to work.

I hear you, the limitations can be frustrating and at times completely unexpected. ShapeDiver strives to provide the best service for sharing amazing Grasshopper models to thousands of users but for that, output limits are necessary evil.

Rendering of interactive models in a web browser is a challenging task and you can’t expect the same as in Rhino on your desktop for two reasons:

  1. ShapeDiver sends meshes over the network and they have to be spit in manageable chunks so they travel fast and the web browser can handle them quickly.
  2. WebGL rendering doesn’t perform as good as rendering in desktop applications due to the technical limitations of a web browser.

You can learn more about what is behind the scenes in following articles:

https://support.shapediver.com/hc/en-us/articles/360023352271-Architecture-of-the-3D-scene-in-the-ShapeDiver-viewer

We are currently working on major plugin and platform upgrades and we will have more information about account types in coming months. When it comes to the errors, ShapeDiver plugin components will give more meaningful messages and you will be able to troubleshoot in Grasshopper. Also, upload errors will be clearer.

With growing number of supported plugins, keeping them all up to date is a challenging task as you can imagine. However, don’t hesitate to give us a shout if we are far behind.

Explode components can behave unpredictably because the order of objects they produce varies between computers due to the tolerances and other factors. See this Forum post for more:

Last but not least, we are committed to continuously improve our service and we appreciate your feedback. Let us know if you have any ideas:

1 Like