Hi, I’m trying to create a new slab style n grasshopper however it doesn’t seem to have kept the “parametric” side of it. Does anyone knows why the slab dimension stays regular? Also adding an example from visualarq site to compare.
R+1-PLANCHER TERASSE.gh (34.5 KB)
composite-slab-mm.gh (25.4 KB)
Hi @sleau,
This happens because slabs created from Grasshopper styles doesn’t have a boundary as input geometry as slabs created from regular slab styles. This improvement is already reported for future development; I’'ll keep you updated about it.
You can change this slab width and span by creating these two parameters in the Grasshopper definition, as in the VisualARQ example you posted:
I do have both though, or they have to be actually called as such? (“Width & span”)
For me, aside for the difference of the array of a brep, the definition is comparable to the example I’ve posted. But stll in my case, it only stays the dimensions i set in GH, whilst in the case of the example i could create a slab from surface I believe.
Hi @sleau,
I have been looking at your Grasshopper definition and, as you say, you have two parameters created to modify width & span. I think they are working fine just as you have them; you just need to modify the value from the style or the object properties:
Hi @sleau we have implemented this feature in VisualARQ 3, which has been already published. So now it is possible to use a boundary curve as input geometry for roofs and slabs created as Grasshopper Styles. In this video you can see an example of it: https://youtu.be/789JeSaVKeY?si=yz7UuOhYxoBfN8Yg
The functionality works when you create an object using the Rhino interface, but not when you use the slab component in grasshopper. It seems there are a number of other options not related to grasshopper styles that are perhaps causing issues.
I’m trying to define the style with the define options component in visualArq. I couldn’t see another way to do this. It seems that there are a number of options that don’t relate to the creation of a grasshopper style like thickness that are causing the slab component to revert to a default?
slab-test.zip (59.0 KB)
I uploaded the files I used to create this test if that is helpful to trouble shoot.
Hi @Benjamin_Paolo_Fortu thanks for reporting this. We are aware of this problem (another user also reported it here: GH slab style doesn't work when using VA slab style components in gh )
I’ll let you know when we fix it.
Thanks!
