Issue with Volume Component Output Not Displaying Correctly in ShapeDiver

[Bhaumik_Solanki]

Hi everyone,

I’ve created a configurator and I’m hosting it through ShapeDiver. Everything is working well overall. I have around 10 direct data outputs using the ShapeDiver Direct Data Output component, and all of them display correctly — including numeric and text values.

However, there’s one issue with the component that calculates the weight of the configured product.

Here’s my setup:

• All geometries are connected to a Volume component.

• I extract the volumes, sum them up, multiply by the material density, and calculate the total weight using mass addition. Than convert them in text and send it in Direct Data Output component of shapediver.

The issue:

When the definition is dynamic (not internalized), the Volume component produces inconsistent results.

• Sometimes it outputs nothing.

• Sometimes it shows “1” or “0”.

• If I internalize the data after the volume calculation, it works correctly.

Inside Grasshopper, the calculated volume and resulting weight appear correct (even when connected properly). But when uploaded to ShapeDiver, the output for weight is wrong or missing — even though the input data seems fine inside the ShapeDiver Data Output component.

Has anyone encountered this issue or knows why the Volume calculation behaves differently on ShapeDiver? Is there a known limitation or specific workaround for using the Volume component in this context?

Thanks in advance for any help.

[mathieu1 (Mathieu Huard)]

Which version of Rhino are you using, and does it match the version of the ShapeDiver servers that you are uploading to?

Are you able to create and share a minimal definition which shows the different result between the local definition and the ShapeDiver model?

[Bhaumik_Solanki]

I have checked my current backend settings, and it shows Rhino version 6.19.19295.1001. The system is prompting me to upgrade in order to use Rhino 7 or 8, even though I am on a Pro | Yearly (Legacy Plan).

Until now, everything was working fine with Rhino 7, but after updating from Rhino 7.26 to Rhino 7.36, this issue appeared.

Several direct output components still work correctly, but the volume component, which was updated in this Rhino release, no longer outputs proper values.

If the backend version is the cause, is there any way to switch the Rhino/Grasshopper version within ShapeDiver, or enable support for my current setup?

[mathieu1 (Mathieu Huard)]

You can switch to one of the current plans in order to access Rhino 7 and 8 backends. You can complete this directly from your billing dashboard and contact our team if you have any questions or issues.

[Bhaumik_Solanki]

I have already paid plan. In this plan is Rhino 7 not supported?

[mathieu1 (Mathieu Huard)]

The Pro plan is an old, legacy option which does not exist anymore, and as such it does not include all the more recent features that come with the new plans. I recommend you get in touch to evaluate your needs and check which of the newer options would work best for your application.

[Bhaumik_Solanki]

Starting next year, we plan to transition from the Legacy Plan to the Starter Plan. We currently have two questions:

1. How does credit calculation differ between the Legacy Plan and the Starter Plan?

2. Is it possible to purchase additional credits if we are on the Starter Plan and we need extrac credits?

[ezequiel (Ezequiel Lopez)]

Hi Bhaumik,

1. We explain the new credit system here and the legacy credit system here. We also have an FAQ section here.
2. Yes, you can purchase extra credits at €0.04/credit. This is billable at the end of each calendar month.

Let me know if you have any other questions, or you can email me directly.

Best,