Rhino Solid Mesh to cuttable Revit solid

I am looking to convert the the solid mesh rockwork imported from Rhino to a solid geometry in dynamo and get union and difference with other geometries for rock work excavation

@Ben_Osborne looking through topics, i thought you might have some ideas about this? Thank you

Voxel analysis with the VASA package might be sufficient - how accurate do you need it to be?

Thank you for your reply, but Vasa Package wouldnt provide required output, it need to be very precise and totally similar to original mesh from rhino.

I’m curious to learn why land excavation needs to such a precise output?

1 Like

This is a very imprecise description. I don’t imagine that point clouds of a cliff face like that will be accurate to the dimension you are after due to the impact of nature over the time between the scan and the construction. I have gotten point cloud accuracy to 3/8 of an inch on interior scans with VASA so far - depending on the scale of your cliff face you could go lower or higher. It’s likely that with earthwork of any type an extra 3/8” over the full face is sufficient.

Can you tell me how big that model is in overall width, length and height?

That said, if you REALLY want you could make a family from the geometry (FamilyInstance.ByGeometry from the springs node), as a first step. Then add in a family with the geometry for the cutting data as a second step. You might be able to cut/join the original family to get a volumetric offset directly in Revit, but if not Element.Geometry for both into Solid.Intersect will get the overlapping geometry in Dynamo.

The strength of Revit is really not with complex meshes, or in calculating cut/fill volumes.
The topography tools in Revit are very basic (that is being polite)
I would use either Rhino or an application like Civil3D which are better suited.

I also agree with comments on precision- earthworks is an inexact science, and factors such as bulking factor (the volume of stuff you dig up is greater than the original volume) means that nothing is ‘very precise’

2 Likes

So you mean once you open it up it doesn’t pack as nicely? Sounds a lot like my luggage on return trip… :slight_smile:

Exactly
Same with a sleeping bag or a tent- it never goes back into the very bag it came out of

1 Like

@MOhie , i have some workflow.
I can test it and share. Can you attach your Rhino file? I can be more specific than.

I would really appreciate it. I attached 3dm, OBJ,STL files for your reference.

https://we.tl/t-LFvUkwaxIN

I tried using the method you showing above, but it just keep running forever. The mesh is Quadrimesh, and its very detailed and heavy.

Thank you for your input. Actually the case i have is about multiple buildings are created in a mountain, partially/fully and this is an ongoing process i have to deal with to cut the mountain geometry for building masses we create, very high requirement i understand, but its the project requirements after all

Would appreciate if you have a look on files i sent in the comment below and let me know if you have a solution in mind

@MOhie , are you shure about Quadrimesh? I see just triangle mesh.

Can’t confirm, but this what I’ve been told, sorry!

I’d suggest looking into Rhino Inside as well as packages in Grasshopper like Weaverbird which have mesh approximation algorithms like Catmull-Clark. From here the outcome can be exported/imported, or you could even take in the void forms using Rhino Inside then bake the result from Rhino Inside back to Revit as a round trip workflow.

I know this is a Dynamo forum, but as you’re finding out, Dynamo can’t really work with high face count meshes quickly without resorting to workarounds (e.g. voxels) or complex packages that are far less intuitive than basic mesh operations Grasshopper provides. Square pegs and round holes if you do it all in Dynamo in my experience.

1 Like

I think it is more a Revit slow down more than a Dynamo one. I’ll try to have a look at the files but it is a tight week for me.

@MOhie how large is the bounding box of the sample? I’m traveling today so I can’t check any of the details.

@JacobSmall Would really appreciate your input to this.
I will check for boundingbox size and let you know soon.
Below you can find what been imported from rhino to Revit, we need to take over this exercise into Revit and keep updating the rockwork as models update (weekly basis)


it takes about 30-40min to convert…
Home2.dyn (23.3 KB)

Use v.5 when save Rhino file.

Rhynamo installer: http://provingground-rhynamo.s3-website-us-west-2.amazonaws.com/ProvingGround.Rhynamo.installer.application

2 Likes

Thanks a lot @Vladimir for your time, i had tried almost similar approach, just using the exported STL file rather than using Rhynamo, but it was taking pretty long time (Solid.ByJoinedSurfaces node specifically), do you thing that makes a difference in running time, or its just my machine?
and moving further from this point, would the created solid be cuttable or it would show troubles from your insight. Thanks again.

@MOhie , i feel times will be about same.

Maybe you can do same thing in Rhino and export SAT? It will be much faster, i believe.

2 Likes

yes, but with MOhie method you dont need have rhino installed as i think with rhynamo