License Delivery maintenance is expected to occur on Saturday, November 30, between 8 AM and 11 AM CET. This may cause a short 3-hours outage in which license-related tasks: license key upload, download, update, SSA validation, access to the license pool and Graphisoft ID authentication may not function properly. We apologize for any inconvenience.
GDL
About building parametric objects with GDL.

Is there a tool / object for making a mesh with a specified thickness?

gedzior84
Booster
Hello.

As in the topic, I wanted to ask you guys if there exists any tool that would allow me to create a mesh with a specified thickness, or layers.
For example, I have a terrain to model, but the ground has layers: 3cm of grass, 10cm of ground, and some other layers. The terrain is not flat - it has some holes and bumps. Is it possible to create this with one tool/object, not using layered slabs, roofs, and shells?
 
Przechwytywanie.JPG

60 REPLIES 60
vistasp
Advisor
I wouldn't call them bugs, but there are a few quirks with easy workarounds:

[list=]
  • Mesh type needs to be solid. Using "with skirt" or "surface only" doesn't give the desired results.
  • [list=]
  • If there is no top surface override for the original mesh, the final composite ignores the surface setting and displays the material properties instead. That's because the parameter (materialAttribute_1) isn't created when you save the mesh as an object.
  • [list=]
  • The same is the case for the bottom surface.
  • [list=]
  • However, if you override the sides of the mesh, the final composite will display that override on the sides (in 3D), no matter what settings you use.
  • Hope this helps.

    EDIT: This is for version-1
    = v i s t a s p =
    bT Square Peg
    https://archicadstuff.blogspot.com
    https://www.btsquarepeg.com
    | AC 9-27 INT | Win11 | Ryzen 5700 | 32 GB | RTX 3050 |
    Anonymous
    Not applicable
    Mesh type needs to be solid. Using "with skirt" or "surface only" doesn't give the desired results.
    I will put a note for this in the instructions.
    The intended behavior was that if there is no top surface override (Mesh Model Setting) then it will assume the BM surface. Also I don't see any need to override the Side/Bottom surface of the original Mesh as they usually are related to the BMSurface. Do you think it is needed?

    I will also describe the workflow on the 2d text empty object:
    1. Create the desired Mesh shape with solid construction method and correspondent Building Material;
    2. Override the top Surface (on the Mesh Dialog Setting/Model) to the Surface of the first skin;
    3. Set the 2d view settings to "Cover Fill" and "Use Fill from Surface";
    4. Set the Fill origin as needed;
    5. Place a hotspot on a Mesh node to better place the Object in 2d view;
    6. Select both the Mesh and the hotspot and save it as an Object inside the Library (External or Embedded);
    7. Reload and Apply the Library every time you save or resave the original Mesh.

    What do you think?
    vistasp
    Advisor
    Braza wrote:
    Also I don't see any need to override the Side/Bottom surface of the original Mesh as they usually are related to the BMSurface. Do you think it is needed?
    I can't think of a use for it. Yet. 😉

    You never know, though, what someone might use the object for, and the functionality is already built-in, so all good.

    BTW, the option for showing the original mesh in Version.2 makes it even more fantastic!
    = v i s t a s p =
    bT Square Peg
    https://archicadstuff.blogspot.com
    https://www.btsquarepeg.com
    | AC 9-27 INT | Win11 | Ryzen 5700 | 32 GB | RTX 3050 |
    Anonymous
    Not applicable
    vistasp wrote:
    I can't think of a use for it. Yet. 😉
    You never know, though, what someone might use the object for, and the functionality is already built-in, so all good.

    Thanks for the feedback vistasp.
    I did some changes to better control custom surfaces, increased the number of skins to 10 (Just in case ), and improved the 2d instructions.
    Cheers,

     

    Screen01.jpg

    rjwilden
    Booster
    I notice that SEO subtract with upward extrusion does not seem to work. OK with the other options.
    Thanks for the object
    Richard Wilden Design. Ltd
    Dunedin, New Zealand.
    Imac 27" i9 3.6GHz; 32GB Ram Mac OS 11.3
    Archicad V23:V24
    Laszlo Nagy
    Community Admin
    Community Admin
    Braza,

    Great and useful object.
    Would it be possible to script 3D hotspots to useful points of the generated object, like nodes of the top surface? This could be useful when trying to position it vertically.
    Loving Archicad since 1995 - Find Archicad Tips at x.com/laszlonagy
    AMD Ryzen9 5900X CPU, 64 GB RAM 3600 MHz, Nvidia GTX 1060 6GB, 500 GB NVMe SSD
    2x28" (2560x1440), Windows 10 PRO ENG, Ac20-Ac27
    rjwilden
    Booster
    Sorry SEO upwards extrusion works just fine, my test slab wasn't thick enough?
    Richard Wilden Design. Ltd
    Dunedin, New Zealand.
    Imac 27" i9 3.6GHz; 32GB Ram Mac OS 11.3
    Archicad V23:V24
    Anonymous
    Not applicable
    This is a great addition and pretty straightforward to use. One suggestion for improvement could be that the hotspots added to the object are placed on the top of the mesh in 3D, this would help greatly in properly aligning the element in 3D.
    lopezfigueroa
    Enthusiast
    I took the audacity to translate the entire object into Spanish.

    I hope that soon we can have this type of improvement in the mesh tool. They are necessary for earthmoving and terrain shaping tasks. Besides the fact that the mesh tool is very old, it would not hurt if they incorporated the visualization of contour lines as well.

    Great job Braza
    Thanks for sharing.
    Anonymous
    Not applicable
    Thanks everybody for the feedback!

    I did some tweaks to address some of your points. The updated version is attached.

    @ LaszloNagy
    Unfortunately it is not possible to have the original mesh hotspots on the object. I tried to solve this creating a parameter where the user insert the original mesh skirt height. But this approach could create some inconsistency for some unusual mesh node heights. So I decided to eliminate the skirt height parameter and use the base of the mesh as the reference level to match the object with the original mesh. What do you think?


    @ lopezfigueroa
    No audacity at all lopezfigueroa!
    Feel free to edit as you wish.
    Just make sure to make it available to the community.