Any hint to solve lofted closed geometry that gets corrupted after trimming
Soliddifferencegh.gh (1.9 MB)
Soliddifferencegh.gh (1.9 MB)
Please check your gh file. It does not look much like your jpg.
PS: After seeing answer from @jessesn I saw I had to zoom in very deep to see what is about.
The problem is when exporting to ifc, the geometry is corrupted. Display is not the issue I’m concerned about
If exported without trimming, it is not corrupted?
Did load it again, to see what happens when I export it.
How can I check if an ifc-file is corrupted?
- I have a standard Rhino/grashopper 8 install. No ifc-export on the list, so you have something for that?
- So I tried some other export-types and imported back in. No errors.
To me it seems there is no corruption in the grashopper process.
So back to checking the input side:
- There are 5 breps in the starting GEO.
A couple seem to be doubles/or copies. When leaving them out, I was able to turn the three others into one “open prep” Not “closed” yet.
So maybe the input has irregularities what cause the problem in the export.
5 closed curves are defined as cross sections with no duplicates and all closed.
IFC:
Cross sections:
Without trimming, geometries are fine. With trimming, they getsdestorted.
Here is the whole GH code:
Soliddifferencegh.gh (64.1 KB)
You also have trouble when exporting/importing to other formats?
Same problem in autocad. The problem is solid difference. Probably not working probably with large geometries.?
Any solution?
- If exported without trimming, it is good/ not distorted.
- There is no doubles. Inputs are 5 cross sections where 2 cross sections have 5mm thickness and above each other.
No, sorry.
I found that the size of these objects is very samll, and the measurement results in Rhino are as follows,
I tried using Rhino.Inside.Revit to import it into Revit, also got the error message indicating that the model size is too small.
Thanks for the effort. I think the only way is to de-extended controlline to short segments before lofting in order to allow boolean/trim operations work properly. Very thin cross-section and 700meter long seems quite tricky to work with.
Do you mean that the unit of this model shoud be meters? When I scaled this model 1000times with millimeters as the unit, restoring it to the same length as in meters, the situation is as follows, and everything seems to look nromal in Rhino.Inside.Revit.
Yes, Rhino model should be in Meters. Cross-section is 5mm thickness (very thin) & controlline is long (>600m).