Grasshopper styles, beams, etc

Hi,

I am currently trying to make some project using VA 2.0 tool and there are some bugs I have noticed so far.

GH styles problems and suggestions
-Insertion point is very often missing while creating the GH style ( is the only option instead).
-Some internalised breps are missing. This happens unless I apply boolean union to all the objects, but I wish to have them seperately included in the object.
-Would be better in my opinion if we could choose also insertion plane instead of insertion point only. This would make it easier to translate the object that is rotated somewhere in the model and make furniture / object out of it.kabina prysznicowa 90 x 75.gh (32.0 KB)

The beams do not reflect when mirrored vertically

The courtain wall does not trim roperly when boolean subtraction applied

Hi @Tomek_Wloga, thanks for your comments.

What do you mean? VA objects that are inserted from an insert point (like a Column), created from a GH definition, take the coordintates 0,0,0 in the definition as the insert point (unless you select a referenced 3DPoint in the definition to perform as insert point instead).

Right now VA only recognizes 1 piece of geometry of internalised data in GH components. That’s something we need to improve in future releases.

Ok, we will study this option.

That’s a bug. We will fix it for the upcoming releases.

Another bug. We will try to fix that too.

Thanks again for reporting these issues. I’ll notify you when they are fixed.

2 Likes

Ok, I found some workaround for the internalisation of multiple geometries. I connect them to the “data” object and then internalise.

image

1 Like

@Tomek_Wloga Thanks for sharing this workaround!

I see there is an option of creating custom grasshopper stair styles, but what is the supported input? Point? Curve? Polyline?

It’s a polyline, or an arc for spiral stairs.

actually… it’s a line. I’ve created the definition with polyline input and that doesn’t work. Grasshopper style stairs are placed the same way elements and furniture are :(.

You’re right, it’s currently just a line (in fact, probably its a point and a direction). We could improve this by computing the center curve of the stair (a polyline on a regular stair and an arc on a spiral stair).

As I also mentioned on the other thread, stair will be soon changed to a new implementation.

Enric

1 Like

We have fixed these errors in VisualARQ 2.3 (VisualARQ 2 - Version 2.3 released)