Best way to reference native rhino geometry

Hi, I am going to be using ShapeDiver to construct a boat configurator. What is the recommended work flow for referencing my original rhino model? The configurator will only turn elements on and off and will throw in some logic for combinations. My rhino files are per today are up in 1gb, 3 outboard engines, seats, cleats etc all adds up. I’ve been using blocks to improve performance in the construction phase, is there any thing simular in grasshopper? Finally our models will be pretty complex, is their a roof of what ShapeDiver can handle?

To sum up. way to reference native rhino model in grasshopper. Note its groups of objects I want to reference not just one polysurface.
2. Performance, block equivalents.
3. What is the file Size limit for ShapeDiver?

Any help will be much appreciated.

@liam to answer your questions:

  1. You need to internalized the geometry you have in Rhino into Grasshopper. You can find an explanation about this here.
  2. You dont need to group elements but just input them in the same list or branch. For example, if you want to hide geometry, you can use the Stream Filter component and input all your “group” in the int 1 in the component so that when you go to false, nothing will be shown and when you go to true, all the list/“group” will be taken.
  3. The allowed file size goes from 50 MB to 200 MB or more depending on your ShapeDiver plan. However, it is very uncommon for somebody to have such huge files. If you have such huge files, it means that your geometry is not optimized for visualization, especially a boat model should never get to such size. To optimize your model you need to create a low poly version of it without affecting the look of your model, get rid of geometry that is not important or not visible for the user and use normal or bump maps to create textures realism without the need of using actual geometry. What makes a model heavy is the amount of mesh faces that it contains and that is the main aspect that you need to bring down. You can learn more about this here and some optimization tricks here.

Thanks for the reply, cleared up allot of questions :+1:t2: