2025-05-22
03:47 AM
- last edited on
2025-05-23
12:54 PM
by
Laszlo Nagy
We have been developing a site model, and we have completed ⅓ of the site, including roads, walks, and driveways. Things were working, albeit slowly, when transitioning to 3D, but they were working. We have now added the other ⅔ of objects to the SEO of the intersection, then subtract upward. The file will not open a 3D view. We let it run overnight, and it is still running. So the question is, where is the information with red flares that states do not create more SEO than a certain amount? We will now need to enter the 2D view and determine how to remove all these SEO elements, which could be done one by one, unfortunately, since we do not have a method to view a list of these SEO elements and eliminate them. I'm not sure what the answer is here, but for Site work and in many instances, building work, we need SEO not to slow down the application the way it presently does, and make the 3D unusable.
2025-05-24 06:57 PM
these "boolean operations" make software do more calculations, hence it is inevitable that the bigger they grow the slower everything gets.
moderation is the key, and only when modeling with other tools doesnt make it.
2025-05-24 09:34 PM
Archicad does'nt have to calculate the seo operations when you convert them to morphs. With large terrains like this I keep a backup of the 'full' mesh model but convert the 'work' model to morphs..
2025-05-25 02:48 PM
We fully understand the calculation issue. Vectorworks incorporated Parasolids into their code, and these types of operations had minor impacts, indicating that it is possible to speed up the process. I am sure other applications can handle this history-based model editing, which allows for just adjusting the original operator to affect the final form. With iterative design, this is a key issue; thus, the power of Object- and material-based effects built into Archicad.
For this process of site area design, which includes streets, walks, plazas, and other hardscape elements, the shapes will continue to evolve over the project's life cycle. So, while converting to morphs is an option, it then creates the burden of recreating objects when the design changes. And with a morph, you still have to boolean out the site mesh to get your result, unless you fudge dimensions and raise them ever so slightly.