Dropping column bases to mesh below

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā2009-01-08
07:09 AM
- last edited on
ā2023-05-25
05:09 PM
by
Rubia Torres
I have many, many,many columns, previously set on top of of flat slab that has now changed to a mesh,with slopes going in several directions.
Dropping all the oolumns to the lowest mesh elevation and then performing a collective "substraction with downwards extrusion" will work, however,I was wondering if there is an equally collective way to have the columns selected and then "gravitate" to the mesh.
Also, what effect have the intensive use of Boolean Ops in the size of a file?
Conrado

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā2009-01-08 11:26 AM
Conrado wrote:Unfortunately, Gravity works only when placing stuff, but does not when moving/modifying it. This would make a great wish. If you make the wish I promise to vote 'essential'.
Greetings to allin this new year
I have many, many,many columns, previously set on top of of flat slab that has now changed to a mesh,with slopes going in several directions.
Dropping all the oolumns to the lowest mesh elevation and then performing a collective "substraction with downwards extrusion" will work, however,I was wondering if there is an equally collective way to have the columns selected and then "gravitate" to the mesh.
Also, what effect have the intensive use of Boolean Ops in the size of a file?
Conrado

I am sure storing SEO relation and operations takes memory but I would not think it takes too much.
I really do not know the limitations of SEO as far as number of operation performed is concerned. I think cutting a couple of dozen Columns out of a Mesh should not cause any problems.
AMD Ryzen9 5900X CPU, 64 GB RAM 3600 MHz, Nvidia GTX 1060 6GB, 500 GB NVMe SSD
2x28" (2560x1440), Windows 10 PRO ENG, Ac20-Ac28

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā2009-01-08 04:36 PM
I will post this as a wish. However, for a really powerfull function, it will be great if we have the columns Trim top or bottom to slabs and mesh, the same way they now trim to a roof. I allways use a flat roof instead of a slab, to take advantage of the Trim to foof function.
Conrado
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā2009-01-08 05:15 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā2009-01-08 06:45 PM
_________________
Kliment Ivanov
Hmm. No Goodies folder in AC 12. I'll search my previous versions and try it.
Thanks for the tip.
Conrado

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā2009-01-08 07:32 PM
Conrado wrote:Goodies are a download for all recent versions. Go to your Help menu to find the download page.
Hmm. No Goodies folder in AC 12.
Cheers,
karl
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā2009-01-08 08:03 PM
Conrado wrote:There is no appreciable effect on file size as far as I know, but there can be significant effects on 3D performance. I have found SEOs to be pretty robust and use them quite extensively. The main things to watch for are:
Also, what effect have the intensive use of Boolean Ops in the size of a file?
1. Don't make reciprocal relationships. An example would be to intersect a roadway slab with a site model and then subtract the result from the site. Better to make a copy of the site to work as a hidden operator.
2. Don't involve parts that don't need to be in the operations. For example, subtracting light fixtures from ceiling slabs should be done room by room (one reason I
In your case, unless you have thousands of columns (or hundreds of complex ones) the performance is probably not much of an issue as long as you have a fairly modern machine.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā2009-01-09 04:30 PM
Matthew wrote:I created a wish based on this. Would be nice if the SEO relationship was created only between physically intersection light fixture-slab pair. This way the whole thing could be done in one step.
2. Don't involve parts that don't need to be in the operations. For example, subtracting light fixtures from ceiling slabs should be done room by room (one reason Ireallywant a proper ceiling tool) rather than by selecting all the fixtures and subtracting them from all the ceilings.
AMD Ryzen9 5900X CPU, 64 GB RAM 3600 MHz, Nvidia GTX 1060 6GB, 500 GB NVMe SSD
2x28" (2560x1440), Windows 10 PRO ENG, Ac20-Ac28
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā2009-01-09 05:02 PM
Or not?...


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā2009-01-10 01:39 AM
Braza wrote:I would say not - for columns at least. Element Information still lists the trimmed volume and a schedule can list the (net) volume.
The only problem that I see with the utilization of SEO in this kind of situation is that quantities are compromised...
Or not?...
Cheers,
Link.