Can ArchiTerra handle much larger meshes than AC?

[Mats_Knutsson]

Dearest forum members,

Sometimes a dwg terrain model is not very nice to magic-wand into an ArchiCAD mesh because AC sometimes can't use the magic wand settings and makes far too many nodes which makes the terrain mesh literally choke (at least I haven't managed to fix this...I've tried pretty much every magic wand setting but if the dwg polylines have a zillion of nodes so will my AC mesh).

I wonder if I can get an AC mesh with much fewer nodes if I use ArchiTerra instead=

saturday-night-cheers,
Mats

[Dwight]

This is a manual technique.

Place an adaptive grid over the plan view to build a new matrix of elevation nodes.

An adaptive grid is larger over flat areas and smaller over steep areas.
This could be as large as 100x100 m and as small as 2x2m.

Interpolate the nearest higher contour for each new node elevation. This will only take a few minutes and will result in many fewer nodes that all contribute to the land profile.

[Anonymous]

Dwight,

I´m not really sure what kind of tools you use, can you please elucidate?

Thank you!
/David

[Dwight]

This is a manual way to minimize nodes in a mesh while maintaining a meaningful contour.

The problem is that conventional auto-tracing of site contours creates many redundant nodes that slow 3D imaging without improving the description of landfall. This is because contours are calculated interpolations of a satellite or survey plan that themselves are based in a sample grid.

With a site plan in the model view at the correct scale, place a matrix of hotspots over it. Since there is art and skill involved in this, you must learn how fine to make the matrix in order to satisfy the needs of the model. Node density should adapt to the slope - fewer nodes in flatter areas, more in steep areas. Specific outcroppings might have many nodes.

You will then manually elevate the nodes to the height of the closest higher contour line.

This method produces believable landfall with a minimum of nodes.

Okay?

[Anonymous]

I would say there is a big problem in ArchiCad and it is the way about how it handle modells with alot of vertex. It is so slow that you think their code is made by a hardware reseller.
There are three ways to handle big maps, use Dwights technic, buy a better computer, or buy a software that use another technic to handle alot of vertex, make your terrain there and then import it as a dead object. Even in 2d these meshes slow down your computer so much you could take a coffebreak everytime you pan your view or touch anything on screen

[Anonymous]

I think Dwight technique is quite good , or for me ... i just change the Magic wand options , coz i don't need the Mesh to be that Accurate , and i think its ok .. once i modeled a small town , with roads and so ... with the 90 villas detailed and a two towers .


Didn't have much troubles ... exactly as mentioned .. in the end computers have limitations and we have to find a balance between what we need , and what the computer can handle .

I mean.... i guess?