Different geometry result in ShapeDiver compared to Grasshopper

Grasshopper ShapeDiver
1

Hi ShapeDiver team,

I’m having an issue with a model that behaves correctly locally in Grasshopper, but gives a different result after uploading it to ShapeDiver.

I originally uploaded a model to ShapeDiver, let’s call it Version 1. Later, I made some corrections to the Grasshopper file and uploaded a new version, Version 2. Since uploading Version 2, I started seeing an issue that does not happen locally in Grasshopper.

image
image1156×865 43 KB

The expected result is shown in the first image, generated with Version 1. However, when I try to recreate the same configuration in Version 2, the geometry appears as a solid black rectangular block instead of the expected inclined panel/backdrop.

image
image1340×836 25.4 KB

When I recreate the exact same configuration locally in Grasshopper, the result looks correct.

image
image624×432 11.8 KB

I also tried uploading Version 1 again, but now the same issue happens there as well. Even when using the first uploaded model again, the result is still incorrect in ShapeDiver.

image
image1843×780 55.8 KB

One important detail is that this problem only seems to happen when the model is set to Imperial units. If I use Metric units, everything works as expected. Because of that, I’m wondering whether this could be related to the model scale, unit conversion, or how ShapeDiver is interpreting the geometry after upload.

image
image971×762 30.4 KB

This is the first time I have encountered this issue, even though I have uploaded several versions of this same model before.

Could you please help me understand what might be causing this difference between the Grasshopper result and the ShapeDiver result?

I have attached screenshots showing:

  1. The expected result in ShapeDiver using the previous version.

  2. The incorrect result in ShapeDiver after uploading the updated version.

  3. The correct result when recreating the same configuration locally in Grasshopper.

  4. The ShapeDiver interface showing the uploaded model and parameters.

Thanks in advance for your help.

2

Your comment about the unit system might be a good hint. Could you try to add the Tolerance Settings component from the ShapeDiver plugin to your definition before you upload it?

That might solve the issue. Otherwise, it would help to have access to a minimal version of the definition so our team can investigate. The next best guess would be backwards compatibility between different versions of Rhino (resp. different Service Release versions).