Bounding box not displaying 'u' input

Hi, I'm new to grasshopper and I was trying to use the bounding box tool and input something into input 'u' because on all the demonstrations the left hand side of the box has 'C' U' P' but mine is missing the 'u' input. COuld some please tell me how I can fix this or if I'm using the wrong setting or tool?

Thanks heaps!

Replies to This Discussion

Permalink Reply by Mateusz Zwierzycki on September 28, 2012 at 6:47pm

Thats just new GUI. U input was used to change if bounding box is created one per each object or one for all objects. Now you have same option avaible within component menu (this property is exposed as label adjacent to component).

Permalink Reply by Aishwarya on February 26, 2013 at 10:53pm

Hi - I still havent been able to place where it is exactly ..... Are you indicating the union box option - if so i tried that but hasnt made a uniform box.

Permalink Reply by Michael Pryor on February 26, 2013 at 11:07pm

yes union box, and it depends how your data is structured. suggest posting a file.

Permalink Reply by Aishwarya on February 27, 2013 at 3:19am

Hi Micheal ,

I am trying to generate a perforated surface - I have attached my rhino and GH file

Thanks Ash

Attachments:

FACADE 3.3dm, 25 KB
FACADE 3 - Doubt.gh, 6 KB

Permalink Reply by David Stasiuk on February 27, 2013 at 4:06am

Hi there...Michael's right that it's a data structure issue. when you build from a grid of points, it splits them out into lists of lists...so with your setup you have 12 columns (Ex) and 10 rows (Ey). This will give you 12 lists of 10 grid cells...which is why your bounding box was generating 12 unique strips. If you flatten your data, you'll have one list of 120 grid cells, which is better for what you're trying to do, which is find the bounding box for all of them. By the way, the same goes for your circle radius based on point proximity. It's a nice move to do the remap, and I actually like the effect of the attractor operating on each column a little differently...but if you want your radius to vary evenly across the entire field, you should flatten your data right out of the point grid. I'd also recommend just splitting your bounding surface with your circle profiles.

Last thing...if you haven't already, in order to better understand how data structures work (and in general anyway) you should set your "display fancy wires" to on. The different appearance of the wires (single wire/ double wire/ double-dashed wire) denotes the kind of data coming out of an input (single item/ list of items/ data structure of items).

Attachments:

FACADE3Doubt.gh, 5 KB

Permalink Reply by Aishwarya on February 27, 2013 at 4:26am

Thank You David !!! Knowing this sure helps a lot :)

Is there any particular reason the perforations are squares and not circular perforation..... Could it be different grasshopper versions trouble??

ash

Permalink Reply by David Stasiuk on February 27, 2013 at 4:36am

hmm...not sure exactly. I have circles over here. can you post a screenshot?

Permalink Reply by Aishwarya on February 27, 2013 at 5:36am

When I follow the script i get a complete surface with the perforation outline as in this image and not perforations as expected :(

Attachments:

grasshopper_perforated facade 1.jpg, 436 KB

Permalink Reply by Hannes Löschke on February 27, 2013 at 12:09pm

Your problem is very common and actually just a display glitch.

To draw a lot of preview geometry very fast, GH uses very rough meshes. This will result in jagged edges and holes. sometimes small holes will appear to be closed. You can either bake the surfaces to see them in full Rhino resolution. Or you can use (finer) custom mesh settings in GH.

Note: a finer preview will not change anything in the solution.

Permalink Reply by Kory on March 14, 2013 at 11:04am

Hi, I am extremely new to grasshopper and for class we are having to come up with a definition to present in class. For the definition i need a bounding box with the C' U' P' input and connect a toogle, true into the u input.. but since I have the newer version and only have C' P' input.. please explain how to get that to work. thanks!!!!

Permalink Reply by Michael Pryor on March 14, 2013 at 11:45am

Right click. Select union

Permalink Reply by David Rutten on March 14, 2013 at 11:52am

Can't. That input is gone. In my infinite wisdom I figured that per-item or per-list boundingboxes were not something that was going to be subject to variability within a single solution. The U input is now a component-setting and can be set through the component menu.

If you want to impress your teacher you can use two [Bounding Box] components (one set to Per Object and the other to Union Box) then plug them both into a [Weave] component with the [Boolean Toggle] as the weave pattern input. I'd post a picture but that would be cheating.

David Rutten

david@mcneel.com

Poprad, Slovakia