Sweep2 Shapediver

[locherschmuck (LS)]

Dear Shapediver-crew,

As we see it there is a problem with the Sweep2 command in Shapediver.

When we upload a model to your Platform, it does not generate the same Surface as in our local grasshopper-file. The Boolean ‘’Same Height’’ has no impact what so ever on your Servers. The command never generates a surface with same height.

Maybe a bug on your side?

Thank you for the Fast response.

[pavol]

This might be related to list order, see following forum posts:

Geometry on Shapediver is different from the Rhino

This is a common problem where a list order varies from computer to computer or between Grasshopper version as the tolerances and other factors may have affected the order of your lists. In order to keep the order stable and predictable, you have to create a geometrical or mathematical check and sort the list accordingly. More in this tutorial or video below:

Hole in model becomes solid in Shapediver

Things can go wrong if you use Deconstruct Brep and similar components as the resulting element list order may vary between computers as explained in this blog post or tutorial below: This video can also give you some ideas how to build your model in more reliable and efficient way:

If this is not the case, please share screenshots and a minimal version of your definition replicating this and we will have a look.

[locherschmuck (LS)]

Hi Pavol,

It is not a list order problem.

Green is the gh-generated surface and red is the exported surface from Shapediver.
Here the gh-file for Testing:

1.5.1.2_SD.gh (35.0 KB)

[pavol]

I could reproduce the Sweep 2 options problem and we will look into it.

You can create the geometry as a mesh straight away which gives better performance and control over your model. Creating surfaces and converting them might also result in large meshes and we recommend alternative workflow, see this definition:

1.5.1.2_SD_reviewed.gh (66.8 KB)

[locherschmuck (LS)]

Thank you very much for your help!
We will check if meshing directly will work in our models.

[Chris_Warren]

@pavol Is there a fix for this issue? I am encountering the same problem with my script:

[mathieu1 (Mathieu Huard)]

Please share a minimal file example to help us reproduce the issue.